DBAsupport.com Forums - Powered by vBulletin
Page 1 of 2 12 LastLast
Results 1 to 10 of 15

Thread: database startup problem

  1. #1
    Join Date
    Oct 2001
    Posts
    127
    Hi ,
    while starting the database i am getting the following error.
    ORA-01102 cannot mount database in EXCLUSIVE mode
    How to resolve this.

  2. #2
    Join Date
    Jun 2001
    Location
    Helsinki. Finland
    Posts
    3,938
    If you are on NT, type first SET ORACLE_SID=DB_SID and then try to startup. On Unix, type ORACLE_SID=DB_SID, then type export ORACLE_SID and then startup.

    OPS or not?

  3. #3
    Join Date
    Oct 2001
    Posts
    127
    I am on NT.I am doing the same thing.
    Set oracle_sid=db_name
    svrmgrl
    connect internal
    startup
    Still i am getting the same error.

  4. #4
    Join Date
    Oct 2001
    Location
    Madrid, Spain
    Posts
    763
    Hi amit,

    Did you try to specify the init.ora for this instance in the startup command:

    set oracle_sid=SID2
    startup pfile=PATH where your pfile is.

    Hope that helps

    Angel

  5. #5
    Join Date
    Nov 2001
    Location
    Turkey
    Posts
    7
    Problem Description:
    ====================

    You are trying to startup the database and you receive the following error:

    ORA-01102: cannot mount database in EXCLUSIVE mode
    Cause: Some other instance has the database mounted exclusive
    or shared.
    Action: Shutdown other instance or mount in a compatible mode.


    Problem Explanation:
    ====================

    A database is started in EXCLUSIVE mode by default. Therefore, the
    ORA-01102 error is misleading and may have occurred due to one of the
    following reasons:

    - there is still an "sgadef.dbf" file in the "ORACLE_HOME/dbs"
    directory
    - the processes for Oracle (pmon, smon, lgwr and dbwr) still exist
    - shared memory segments and semaphores still exist even though the
    database has been shutdown
    - there is a "ORACLE_HOME/dbs/lk" file


    Search Words:
    =============

    ORA-1102, crash, immediate, abort, fail, fails, migration

    Solution Description:
    =====================

    Verify that the database was shutdown cleanly by doing the following:

    1. Verify that there is not a "sgadef.dbf" file in the directory
    "ORACLE_HOME/dbs".

    % ls $ORACLE_HOME/dbs/sgadef.dbf

    If this file does exist, remove it.

    % rm $ORACLE_HOME/dbs/sgadef.dbf

    2. Verify that there are no background processes owned by "oracle"

    % ps -ef | grep ora_ | grep $ORACLE_SID

    If background processes exist, remove them by using the Unix
    command "kill". For example:

    % kill -9

    3. Verify that no shared memory segments and semaphores that are owned
    by "oracle" still exist

    % ipcs -b

    If there are shared memory segments and semaphores owned by "oracle",
    remove the shared memory segments

    % ipcrm -m

    and remove the semaphores

    % ipcrm -s

    NOTE: The example shown above assumes that you only have one
    database on this machine. If you have more than one
    database, you will need to shutdown all other databases
    before proceeding with Step 4.

    4. Verify that the "$ORACLE_HOME/dbs/lk" file does not exist

    5. Startup the instance


    Solution Explanation:
    =====================

    The "lk" and "sgadef.dbf" files are used for locking shared memory.
    It seems that even though no memory is allocated, Oracle thinks memory is
    still locked. By removing the "sgadef" and "lk" files you remove any knowledge
    oracle has of shared memory that is in use. Now the database can start.


    Basri

  6. #6
    Join Date
    Jun 2001
    Location
    Helsinki. Finland
    Posts
    3,938
    connect internal
    startup
    Still i am getting the same error.
    STARTUP PFILE=C:\ORACLE\.... Give the complete init.ora name.


  7. #7
    Join Date
    Oct 2001
    Posts
    127
    Julian,
    I have also tried the same ,giving startup pfile =' '
    ,still the same problem.
    Thanks

  8. #8
    Join Date
    Oct 2001
    Location
    Madrid, Spain
    Posts
    763
    Amits,

    Have you tried to shutdown cleanly (shutdown immediate) and then startup pfile= ..... I think there are background processes crashed on your machine.

    Hope that helps

    Angel

  9. #9
    Join Date
    Jun 2001
    Location
    Helsinki. Finland
    Posts
    3,938
    Originally posted by aarroyob
    Amits,

    Have you tried to shutdown cleanly (shutdown immediate) and then startup pfile= ..... I think there are background processes crashed on your machine.

    Hope that helps

    Angel
    That's very possible. Try that! Shutdown first, even with abort if immediate does not help.


  10. #10
    Join Date
    Oct 2001
    Location
    Madrid, Spain
    Posts
    763
    Amits,

    Could you connect to the instance via sql plus. I think you will continue with error, but which error ?

    Angel

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