Shulou(Shulou.com)06/01 Report--

Oracle rac 11.2.0.4 one of the two nodes.

Problem phenomenon:

When a customer response generation database queries the table through PL/SQL, it reports to ORA-12519 (the table should be a view with dblink, and the problem should occur on the target side of dblink, which is not tangled at first); later, try to remotely connect to the problem database and report to ORA-12516.

Analysis:

In the database local machine through TNS to connect library error, it seems that there is a problem with the database.

It is said on the Internet that ORA-12516 or ORA-12519 is caused by setting the parameter values of process and session too small, but there is nothing wrong with these two parameters (no matter the maximum value or the current value).

Deal with:

Restart listening and found that instance is not automatically registered for listening; restart the instance and resume it.

After looking up several documents on MOS, I felt that PMON could not properly monitor process and reported to ORA-12516. But I don't know why this happened.

Later, when I looked at the alert log, I found that the log had not been generated for a long time, and there was no error information in the log.

Summary:

With regard to ORA-12516 or ORA-12519, the first thing to do is to take a look at the parameters process and session, and then you can analyze the PMON monitoring information.

Since I didn't check the problem in person, I'll record it here.

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.