ORA-01102: cannot mount database in EXCLUSIVE mode
SQL> startup
ORACLE instance started.
Total System Global Area 5033164800 bytes
Fixed Size 2027672 bytes
Variable Size 905973608 bytes
Database Buffers 4110417920 bytes
Redo Buffers 14745600 bytes
ORA-01102: cannot mount database in EXCLUSIVE mode
alert告警日誌中
sculkget: failed to lock /u01/app/oracle//product/10.2.0/db_1/dbs/lkEPPS exclusive
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<sid>.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<sid>" 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<sid>.dbf" file in the directory "ORACLE_HOME/dbs".
% ls $ORACLE_HOME/dbs/sgadef<sid>.dbf If this file does exist, remove it.
% rm $ORACLE_HOME/dbs/sgadef<sid>.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 <rocess_ID_Number>
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 <Shared_Memory_ID_Number>
and remove the semaphores
% ipcrm -s <Semaphore_ID_Number>
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<sid>" file does not exist
5. Startup the instance
Solution Explanation:
=====================
The "lk<sid>" and "sgadef<sid>.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.
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/31440090/viewspace-2738558/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- cannot mount database in EXCLUSIVE modeDatabase
- ORA-01102 cannot mount database in EXCLUSIVE modeDatabase
- [Oracle] ORA-01102: cannot mount database in EXCLUSIVE modeOracleDatabase
- 關於ORA-01102: cannot mount database in EXCLUSIVE modeDatabase
- Oracle ORA-01102故障: cannot mount database in EXCLUSIVE modeOracleDatabase
- RAC 11.2.0.3 ORA-01102: cannot mount database in EXCLUSIVE mode”Database
- ORA-01102: cannot mount database in EXCLUSIVE mode 的解決辦法Database
- Oracle 11g RAC ORA-01102: cannot mount database in EXCLUSIVE modeOracleDatabase
- Oracle 11g 報錯ORA-01102: cannot mount database in EXCLUSIVE modeOracleDatabase
- 啟動資料庫時 ORA-01102: cannot mount database in EXCLUSIVE mode資料庫Database
- oracle ORA-01102: cannot mount database in EXCLUSIVE mode(無法起到獨佔模式)OracleDatabase模式
- ORA-01102: 不能EXCLUSIVE模式mount資料庫模式資料庫
- Oracle startup mount exclusive作用Oracle
- Oracle blocking issue with lock table in exclusive modeOracleBloC
- Exclusive access could not be obtained because the database is in useAIDatabase
- ORA-01679: database must be mounted EXCLUSIVE and not open to activateDatabase
- How to Start 11gR2 Grid Infrastrucure in Exclusive Mode (Doc ID 1364971.1)AST
- you cannot use this control in design mode。
- PROTECTION_MODE is UNPROTECTED at standby database 分析Database
- ORA-19573: cannot obtain exclusive enqueue for datafile XXX 解決方法AIENQ
- 0506-324 Cannot Mount File System (轉自網路)
- 在alter database mount時的一點收穫Database
- rfs (PID:146054): Database mount ID mismatch案例Database
- 3.2.3 Opening a Database in Read-Only ModeDatabase
- How to Duplicate a Database in NOARCHIVELOG mode (Doc ID 275480.1)DatabaseHive
- RMAN backup validate database on databases in noarchivelog modeDatabaseHive
- ORA-01618: redo thread 2 is not enabled - cannot mountthread
- Open a Database in Read-Only Mode (301)Database
- Seed Database (pdb$seed) - Read Write OR Read Only Mode in Oracle Database 12cDatabaseOracle
- ORA-00265: instance recovery required, cannot set ARCHIVELOG modeUIHive
- MySQL案例01:Last_SQL_Errno: 1755 Cannot execute the current event group in the parallel modeMySqlASTParallel
- 12C-ORA-65086: cannot open/close the pluggable databaseDatabase
- Msg 3702:Cannot drop the database 'gcard' because it is currently in use.DatabaseGC
- Fatal Error: TXK Install Service,Cannot install Oracle Database HomeErrorOracleDatabase
- ORA-01618: redo thread 2 is not enabled - cannot mount 問題處理thread
- OPATCHAUTO-72141: Grid patching cannot be performed in rolling mode on single noORM
- ORA-16433 The database must be opened in read write mode故障解決Database
- oracle9i(9204)dg(data guard)_ place the standby database in manual recovery modeOracleDatabase