PMON Crashes Instance with ORA-472 after fresh Installation

(Doc ID 392872.1)

Last updated on NOVEMBER 28, 2016

Applies to:

Oracle Database - Enterprise Edition - Version and later
***Checked for relevance on 09-APR-2012***


STARTUP NOMOUNT of an instance fails due to a background process terminating unexpectedly, e.g.:

Wed Sep 6 08:50:41 2006
Errors in file /oracle/admin/orcl/bdump/orcl_pmon_1061040.trc:
ORA-00472: PMON process terminated with error
Wed Sep 6 08:50:41 2006
PMON: terminating instance due to error 472

An ORA-600 [504] error on the 'session allocation' latch may also be observed as follow up effect.


The PMON trace file shows:

skgvtime: process 1061040 unix pid wrap detected 1157525439 1157525441
Background process PMON found dead
Oracle pid = 2
OS pid (from detached process) = 1061040
OS pid (from process state) = 1061040
dtp = 400007df0, proc = 424a54310
skgvtime: process 1061040 unix pid wrap detected 1157525439 1157525442
Exception signal: 11 (SIGSEGV), code: 1 (Address not mapped to object), addr:

So skgvtime() is detecting that the unix pid has wrapped and then PMON core
dumps, thus killing the instance.


New Installation of on HP Tru64.


Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms