Shulou(Shulou.com)05/31 Report--

This article mainly introduces how to do ORA-01102 errors in oracle, has a certain reference value, interested friends can refer to, I hope you can learn a lot after reading this article, the following let Xiaobian take you to understand.

The oracle database in the test environment was shut down abnormally for some reason. After rebooting, the attempt to restore the related application found that it failed to start the database. During that time, I walked a section of winding path over the mountains. Sort out the process first so that it can be resolved quickly when you encounter this kind of thing later.

Begin ↓

I. Database

1. After the machine starts, the login server uses sqlplus / as sysdba to log in to the database to find that the database has not been started before adding the database service to boot self-startup.

two。 An error was reported when starting the database using the startup command

SYS@orcl > startup

The ORACLE routine has been started.

Total System Global Area 2471931904 bytes

Fixed Size 2255752 bytes

Variable Size 671089784 bytes

Database Buffers 1778384896 bytes

Redo Buffers 20201472 bytes

ORA-01102: cannot mount database in EXCLUSIVE mode

3. The same error is reported when you try to start the instance step by step and start it to the mount phase.

4. Searched the Internet for ORA-01102 and found a solution.

This error is mainly caused by the lk file, which is located in the dbs directory under ORALCE_HOME

The main function of this lk is to explain that it is on DATABASE MOUNT, not on MOUNT. DATABASE UNMOUNT will delete it after DATABASE UNMOUNT. If DATABASE really does not have MOUNT, this file is on your MOUNT, and can only be deleted manually.

5. When it comes to specific solutions, introduce another command / sbin/fuser

The main function of / sbin/fuser is to use files or sockets to represent recognition processes. It is often used to view and kill related processes. This is used to clear the lk file

/ sbin/fuser-u / u01/app/oracle/product/11.2.0/db_1/dbs/lkHSDB query the processes pid and username that occupy the temporary file

/ sbin/fuser-k / u01/app/oracle/product/11.2.0/db_1/dbs/lkHSDB directly kill related pid release files lk files

/ sbin/fuser-u / u01/app/oracle/product/11.2.0/db_1/dbs/lkHSDB check again and find that there are no more processes

6. Start everything in the database ok again

Thank you for reading this article carefully. I hope the article "what to do if there are ORA-01102 errors in oracle" shared by the editor will be helpful to everyone. At the same time, I also hope you will support us and pay attention to the industry information channel. More related knowledge is waiting for you to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.