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

This article mainly introduces "how to solve the Oracle database shutdown error ORA-01031". In the daily operation, I believe many people have doubts about how to solve the Oracle database shutdown error ORA-01031 problem. The editor consulted all kinds of information and sorted out a simple and easy-to-use operation method. I hope it will be helpful to answer the doubt of "how to solve the Oracle database shutdown error ORA-01031". Next, please follow the editor to study!

The error is as shown below:

To log in the ip and instance name to the server to see that the pmon process is still there

Ps-ef | grep pmon

It is also normal to check the monitoring situation.

Lsnrctl status

Try logging in to the database, as shown in the following figure:

Students who are familiar with Oracle should be able to feel wrong as soon as they read this prompt message, which is not a prompt for normal library connection.

Query the database status. The statement execution error is as follows

Statement cannot be executed, then transfer to view the alert log

I have been reporting similar information, but no valid information has been found. I found a key point along the log. I tried shutdown database at 16:01:45.

Continue to communicate with pressure testing colleagues, they tried to restart the database in the afternoon, but reported insufficient permissions.

It's strange how the shutdown library doesn't have permission.

I also tried. Shutdown immediate could not be executed and shutdown abort also reported insufficient permissions.

This question is sure to be very strange, I used sqlplus / as sysdba to log in to the database, how can there be no permission, continue to check

View user permissions

This server is installed on a single instance, but there are grid users, which is quite strange.

From the above output, there is no problem with the permissions and groups of oracle users.

There is no problem with the permission to view the oracle file.

I couldn't find any problem at this point, so I transferred to MOS to check if there were any relevant documents.

Find an ORA-1031 While Starting An Instance As SYSDBA immediately After Applying A Patch (document ID 1475357.1) but not quite consistent with the problems encountered here. At the end of the document, there is a reference document ORA-01031 DOING DATABASE STARTUP OR SHUTDOWN (document ID 1008507.6).

It mentions the environment variable TWO_TASK, which is also related to the problems in the database before, so check that the environment variable is not configured.

Following this line of thinking, I looked at the environment variables of the entire oracle user and found the problem.

The original PATH path in oracle users is configured with / u01/app/11.2.0/grid/bin, but the permissions are incorrect.

So modify the PATH in .bash _ profile

Log in to the oracle user again

Log in to the database again with sqlplus / as sysdba, restart, problem solved

At this point, the study on "how to solve the problem of shutdown error ORA-01031 in Oracle database" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

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.