Printable View
AFTER SHUTDOWN IMMEDIATE AND STARTUP THE DATABASE i GOT THE BELOW ERROR:
ARCH: STARTING ARCH PROCESSES COMPLETE
Fri May 09 06:00:04 2003
ALTER DATABASE MOUNT
Fri May 09 06:00:04 2003
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.
PLEASE ADVISE
Hey Mike;
Well I wish I had something to offer here.
Which file is it trying to create?
Does it list the directory?
Can you re-name the old one?
The error says that another instance is mounting the database, if that helps.
MH
Oracle can't get the number of semephores it needs to start. One of three things has happened:
1. You don't have enough semephores defined in your kernal parameters.
2. A previous instance is retaining semephores (use ipcs to find out which).
3. You adjusted some of your init.ora parameters since the database has last been started and now your box is not configured correctly.
Here is how toQuote:
Originally posted by marist89
2. A previous instance is retaining semephores (use ipcs to find out which).
http://www.dbasupport.com/forums/sho...threadid=34262
Hm, Jeff, how about rebooting? I mean the unix box, not the windoze! (coz such a problem is exclusive to unix, it couldn't happened on windoze)!Quote:
Originally posted by marist89
Oracle can't get the number of semephores it needs to start. One of three things has happened:
....
:D (Sorry, couldn't resist):p
Jurij, shhh - I think a patch has been applied, look here http://www.dbasupport.com/forums/sho...threadid=36096 a four posts in a Windows thread and he didn't use the "r" word once!
Just reproducing from Metalink....see this helps u....
RDBMS Version: 8.1.7.4
Operating System and Version: Windows 2000 service pack 2
Error Number (if applicable): osd-04400
Product (i.e. SQL*Loader, Import, etc.):
Product Version:
Instance can not mount ,
Hi ,
We have three instances running in the same machine. We are not able to startup ony instance. The alert file for all the three instances contains following errors.
" 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. "
All the three instances are very new and nobody connected to any databases.
What is the main problem here.
Some background on set up:
The Win 2k server has 1.3 GB RAM, Does this RAM not sufficient to use three instances ? Each of the instance SGA is as given below
instance 1 --->97MB
instance 2 ---> 112 MB.
instance 3 ---> 97 MB.
Appreciate your help on this .
Regards
Srini
--------------------------------------------------------------------------------
From: Oracle, Kathy Ting 14-Nov-02 06:32
Subject: Re : Instance can not mount ,
The errors are generated because the same DBName for the databases are being used in the INITsid.ORA file. It is NOT possible to have two databases up with the same DBName on an NT Box (even with different ORACLE_SIDs).
The name of the semaphore, scumntsem_, is created on mounting the database.
When starting another instance, even with a different ORACLE_SID, the same DBName will cause a conflict with the existing semaphore.
This was done to avoid misusages when creating other databases
on the same box.
Stop all instances. Modify the services to MANUALLY start. Modify the INITsid.ORA file. Reboot the server. Start each instance.
Thank you for using the MetaLink Forum,
Kathy
Oracle Support.
--------------------------------------------------------------------------------
From: srinivasulu kvs 14-Nov-02 07:36
Subject: Re : Instance can not mount ,
Hi Kathy,
The fact here is three instances already have three different "db_name" in their init.ora file. I checked with V$parameter also.
What could be other reasons ??
Regards
Srini
--------------------------------------------------------------------------------
From: Christian Adams 18-Nov-02 15:01
Subject: Re : Instance can not mount ,
Srini,
You are not alone! I had the same thing happen yesterday to one of four databases (8.1.7.3.0) on a server running Windows 2000 Service Pack 2. And like you, these databases have different DB_NAMEs. Stopping and restarting the Oracle service for the instance in question did not fix it for me, so I had to reboot the server.
windoz got semaphores too :)Quote:
Originally posted by jmodic
Hm, Jeff, how about rebooting? I mean the unix box, not the windoze! (coz such a problem is exclusive to unix, it couldn't happened on windoze)!
:D (Sorry, couldn't resist):p
http://search.microsoft.com/default....&siteid=us/dev
and there are some links on metalink facing this semaphore problem on windowz.
So if its windoze, only solution reboot.
if its unix find the process blocking the semaphore using oradebug ipc and ipcrm command to remove them and start the DB.
MOTTO - UNIX grows and thrive ;), Windoze sucks :D
Ouch, that hurts! :o
BTW, I've also done some research on Metalink regarding this isue, and the common solution for this kind of problem on Win$ is to restart the service, not to reboot the box! But then again, I think for Unix crusaders it's easier to push the power switch off/on than to try to find how to stop the appropriate service. :D
kill -9 is my best friend...
Actually, in this case I was going to say reboot the box, but I didn't think you guys would take me seriously...