Database Administration (MOSC)

MOSC Banner

can I avoid PMON: terminating instance due to error 18 after receiving ORA-00018 errors

edited Oct 31, 2011 5:36PM in Database Administration (MOSC) 1 commentAnswered
From our production database alert log.

... many ORA-0018 errors before this one...

Errors in file /oradata/PRDORA01/admin/bdump/prdora01_pmon_29409.trc:
ORA-00018: maximum number of sessions exceeded
Mon Oct 31 15:17:01 2011
krvxerpt: Errors detected in process 144, role builder.
Mon Oct 31 15:17:01 2011
PMON: terminating instance due to error 18
Mon Oct 31 15:17:32 2011
Instance terminated by PMON, pid = 29409

...Mon Oct 31 15:17:51 2011
Starting ORACLE instance (normal)

Database is restarted with no errors.  The ORA-0018 errors are valid.  While I am working on clearing up that problem, I do not want the database to fail/shutdown.  Is there any way to avoid this?  NOTE:  The ORA-0018 errors are being caused to to some library: cache locks.  I have an SR open for this problem. 

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center