+ Reply to Thread
Results 1 to 3 of 3

pmon and alert.log database up timing issue

  1. pmon and alert.log database up timing issue

    Hi,
    My pmon showing database is up for 2 months, but alert.log shows
    database shutdown command ran 30 minutes ago. What is the possible
    reason? Is database still trying to shutdown?

    Shutting down instance: further logons disabled
    Tue Aug 5 14:15:56 2008
    Stopping background process QMNC
    Tue Aug 5 14:15:56 2008
    Stopping background process CJQ0
    Tue Aug 5 14:15:58 2008
    Stopping background process MMNL
    Tue Aug 5 14:15:59 2008
    Stopping background process MMON
    Tue Aug 5 14:16:00 2008
    Shutting down instance (normal)
    License high water mark = 411
    Tue Aug 5 14:16:00 2008
    Stopping Job queue slave processes
    Tue Aug 5 14:16:00 2008
    Job queue slave processes stopped
    Tue Aug 5 14:35:45 2008


    ps -ef|grep pmon
    oracle 15095 2367 0 Jun 02 ? 106:16 ora_pmon_DATABASE
    oracle 24568 24318 0 15:01:21 pts/6 0:00 grep pmon

  2. Re: pmon and alert.log database up timing issue

    On Aug 19, 2:40*pm, shamir600 wrote:
    > Hi,
    > My pmon showing database is up for 2 months, but alert.log shows
    > database shutdown command ran 30 minutes ago. What is the possible
    > reason? Is database still trying to shutdown?
    >
    > Shutting down instance: further logons disabled
    > Tue Aug *5 14:15:56 2008
    > Stopping background process QMNC
    > Tue Aug *5 14:15:56 2008
    > Stopping background process CJQ0
    > Tue Aug *5 14:15:58 2008
    > Stopping background process MMNL
    > Tue Aug *5 14:15:59 2008
    > Stopping background process MMON
    > Tue Aug *5 14:16:00 2008
    > Shutting down instance (normal)
    > License high water mark = 411
    > Tue Aug *5 14:16:00 2008
    > Stopping Job queue slave processes
    > Tue Aug *5 14:16:00 2008
    > Job queue slave processes stopped
    > Tue Aug *5 14:35:45 2008
    >
    > ps -ef|grep pmon
    > * oracle 15095 *2367 * 0 * Jun 02 ? * * * * 106:16 ora_pmon_DATABASE
    > * oracle 24568 24318 * 0 15:01:21 pts/6 * * * 0:00 grep pmon


    It's perhaps waiting for everyone to leave. You may want to do a
    shutdown immediate instead of just shutdown in the future. See the
    docs for the difference.

    "Everyone" may include oracle things, see the users that are left when
    all your users are off.

    jg
    --
    @home.com is bogus.
    http://blogs.pcworld.com/gameon/archives/007483.html

  3. Re: pmon and alert.log database up timing issue



    I believe it shows 2 months because It is first started 2 mounts ago.

+ Reply to Thread