Databases Not Mounting - ORA-09341
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 8 of 8

Thread: Databases Not Mounting - ORA-09341

  1. #1
    Join Date
    Jan 2000
    Location
    Chester, England.
    Posts
    818

    Databases Not Mounting - ORA-09341

    I have two DBs (8.1.5) on a Win 2K server.

    Because the Veritas backup has no Oracle Agent, I execute a simple SQL file at 11pm that connects as sysdba and issues a shutdown immediate. (For both DBs) This works fine.

    At 2am I use another simple SQL script to restart them.

    Both DBs begin to open but hang at the MOUNT stage with:

    ORA-01102: cannot mount database in EXCLUSIVE mode
    ORA-09341: scumnt: unable to mount database
    OSD-04400: unable to acquire internal semaphore for process

    Now I've tracked a bug (855721) that describes this functionality (!) perfectly. It advocated restarting the services as the only way to start an instance that has previously failed at the MOUNT stage before.

    Okay - its a bug, but how can I trace what is causing the DBs to fail to MOUNT in the first place?

    Until very recently the SQL file just stopped and started 1 DB. This worked without problem. I added a startup and shutdown for a 2nd DB and this problem has begun to occur - if intermittently.

    The scripts are very simple:

    CONNECT sys/pwd as sysdba@db1
    shutdown immediate
    CONNECT sys/pwd as sysdba@db2
    shutdown immediate

    and the same for startup. Could the nature of the scripts be causing the DBs to hang at MOUNT stage?

  2. #2
    Join Date
    Feb 2000
    Location
    Singapore
    Posts
    1,758
    Any info in alet log?
    Any trace file in bdump? Give them to oracle support, they might provide some information.
    Sanjay G.
    Oracle Certified Professional 8i, 9i.

    "The degree of normality in a database is inversely proportional to that of its DBA"

  3. #3
    Join Date
    Jan 2000
    Location
    Chester, England.
    Posts
    818
    The alert log isn't very helpful...

    (As the DB starts)

    Tue May 25 02:00:11 2004
    ARC0: changing ARC0 KCRRSTART->KCRRACTIVE
    ARC0 started with pid=8
    Tue May 25 02:00:11 2004
    ARCH: Initializing ARC0
    ARCH: ARC0 invoked
    Tue May 25 02:00:11 2004
    ARCH: STARTING ARCH PROCESSES COMPLETE
    Tue May 25 02:00:11 2004
    ALTER DATABASE MOUNT
    Tue May 25 02:00:11 2004
    ORA-09341: scumnt: unable to mount database
    OSD-04400: unable to acquire internal semaphore for process
    O/S-Error: (OS 183) Cannot create a file when that file already exists.

    Tue May 25 02:00:11 2004
    ORA-1102 signalled during: ALTER DATABASE MOUNT...
    Tue May 25 02:00:12 2004
    ARC0: Archival started


    and it hangs here. Just brute rebooting the server causes both DBs to start fine, with this alert log:

    ue May 25 09:50:28 2004
    ARC0: changing ARC0 KCRRSTART->KCRRACTIVE
    ARC0 started with pid=8
    Tue May 25 09:50:28 2004
    ARCH: Initializing ARC0
    ARCH: ARC0 invoked
    Tue May 25 09:50:28 2004
    ARCH: STARTING ARCH PROCESSES COMPLETE
    Tue May 25 09:50:28 2004
    alter database mount exclusive
    Tue May 25 09:50:29 2004
    ARC0: Archival started
    Tue May 25 09:50:34 2004
    Successful mount of redo thread 1, with mount id 1461560362.
    Tue May 25 09:50:34 2004
    Database mounted in Exclusive Mode.
    Completed: alter database mount exclusive
    Tue May 25 09:50:34 2004
    alter database open
    Picked broadcast on commit scheme to generate SCNs
    Tue May 25 09:50:36 2004
    Thread 1 opened at log sequence 6439
    Current log# 1 seq# 6439 mem# 0: I:\ALPS\ALPSLIVE\ALPL_REDO01.LOG
    Successful open of redo thread 1.
    Tue May 25 09:50:36 2004
    sql: prodding the archiver
    Tue May 25 09:50:36 2004
    SMON: enabling cache recovery
    Tue May 25 09:50:36 2004
    ARC0: received prod
    Tue May 25 09:50:39 2004
    SMON: enabling tx recovery
    Tue May 25 09:50:39 2004
    Completed: alter database open
    Tue May 25 10:00:59 2004
    LGWR: prodding the archiver
    Tue May 25 10:00:59 2004

  4. #4
    Join Date
    Dec 2002
    Location
    Bangalore ( India )
    Posts
    2,434

    Re: Databases Not Mounting - ORA-09341

    Originally posted by JMac
    Could the nature of the scripts be causing the DBs to hang at MOUNT stage?
    Why dont u try changing it..(put exit after first db shuts down)?
    funky...

    "I Dont Want To Follow A Path, I would Rather Go Where There Is No Path And Leave A Trail."

    "Ego is the worst thing many have, try to overcome it & you will be the best, if not good, person on this earth"

  5. #5
    Join Date
    Jan 2000
    Location
    Chester, England.
    Posts
    818
    Done that already - will test it tonight when the scheduled job next comes round.

    I've a master script that calls 2 sub-scripts in turn, each sub-script has a CONNECT as SYSDBA, STARTUP or SHUTDOWN and an EXIT.

    But if that IS the cause of the problem - the question is WHY???

    I'll get back to you on this one.

  6. #6
    Join Date
    Nov 2000
    Location
    greenwich.ct.us
    Posts
    9,095

    Re: Databases Not Mounting - ORA-09341

    Originally posted by JMac

    Because the Veritas backup has no Oracle Agent
    Are you saying you just don't have it?
    Jeff Hunter
    marist89@yahoo.com
    http://marist89.blogspot.com/
    Get Firefox!
    "I pledge to stop eating sharks fin soup and will not do so under any circumstances."

  7. #7
    Join Date
    Feb 2001
    Location
    Bombay,India
    Posts
    530

    Re: Databases Not Mounting - ORA-09341

    Windows is still holding the semaphores for this database.
    Reboot the machine.
    Also this problem occurs when there cannot be 2 instances running with the same db name on the machine
    Thanks and Regards
    Rohit S Nirkhe
    rohitsnirkhe@rediffmail.com

  8. #8
    Join Date
    Jan 2000
    Location
    Chester, England.
    Posts
    818
    Are you saying you just don't have it?
    Nope - we have it, but the IT Manager and the Net Admins say they are too busy to fully test the impact of the Agent (I think, in reality, they don't want to spend a week documenting it and writing up the validation docs and change controls). In the meantime the system crashes and has to be rebooted by support.

    Its frustrating, but the balls firmly in their court. Management know whats happening as I've made it clear whats going on.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width