ORA-1075 After Receiving ORA-4031 Error (文档 ID 420366.1)
In this Document
|
|
Symptoms |
|
|
Cause |
|
|
Solution |
| This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review. |
Applies to:
Oracle Server - Enterprise Edition - Version 9.2.0.1 to 10.2.0.1 [Release 9.2 to 10.2]Information in this document applies to any platform.
Symptoms
Fact: Instance is getting a lot of ORA-4031 errors.
Fact: After that, any attempt to connect to the instance fails with:
ORA-01075: YOU ARE CURRENTLY LOGGED ON
Killing the Oracle processes / service is required.
Cause
This is a "side effect" that may appear after receiving ORA-4031 error. It is considered a normal behavior as this problem appears only after receiving the ORA-4031 error.
Solution
Solve the ORA-4031 issue. Once the ORA-4031 issue is resolved, the ORA-1075 will be resolved as well.
You may reach a state where you cannot even get on the system as sysdba, connecting as another user only generates another ORA-4031, with no connection at all. The only way you can get around this is to connect as SYSTEM user, not as sysdba, then flush the shared_pool.
在本次处理过程中，由于时间比较紧，且是第一次遇到这种报错，所以采用的是kill oracle进程的方式处理的，这样处理的目的是便于尽快回复生产。
来自 “ ITPUB博客 ” ，链接：https://blog.itpub.net/29967410/viewspace-1310530/ ，如需转载，请注明出处，否则将追究法律责任。
