My Oracle Support Banner

Instance crashes with ORA-00603, ORA-27515 (Doc ID 2700814.1)

Last updated on JANUARY 13, 2022

Applies to:

Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A to N/A
Information in this document applies to any platform.

Symptoms

Instance failure with following errors reported in alert log.

2020-07-14T01:11:58.695144-05:00
Archived Log entry 1275 added for T-1.S-2367 ID 0x2c5d558c LAD:1
2020-07-14T01:13:53.787461-05:00
Errors in file /u02/app/oracle/diag/rdbms/cd1sfm/cd1sfm1/trace/cd1sfm1_ora_167850.trc  (incident=770730) (PDBNAME=CDB$ROOT):
ORA-00603: ORACLE server session terminated by fatal error
ORA-27515: inadequate memlock limit or driver settings
Incident details in: /u02/app/oracle/diag/rdbms/cd1sfm/cd1sfm1/incident/incdir_770730/cd1sfm1_ora_167850_i770730.trc
.....
2020-07-14T01:14:58.631500-05:00
opiodr aborting process unknown ospid (167850) as a result of ORA-603
2020-07-14T01:17:23.410311-05:00
Errors in file /u02/app/oracle/diag/rdbms/cd1sfm/cd1sfm1/trace/cd1sfm1_ora_172703.trc  (incident=770475) (PDBNAME=SFDAT):
ORA-00603: ORACLE server session terminated by fatal error
ORA-27515: inadequate memlock limit or driver settings
SFDAT(3):Incident details in: /u02/app/oracle/diag/rdbms/cd1sfm/cd1sfm1/incident/incdir_770475/cd1sfm1_ora_172703_i770475.trc
2020-07-14T01:17:25.642557-05:00
SFDAT(3):opiodr aborting process unknown ospid (172703) as a result of ORA-603
2020-07-14T01:19:19.671875-05:00

 

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.