VMS: ORA-00443 Process PMON Died When Starting the Instance.
(Doc ID 548910.1)
Last updated on AUGUST 01, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.2 and laterOracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
HP OpenVMS Itanium
HP OpenVMS Alpha
-- Problem Statement:
Instance startup fails with the following error message:
SQL*Plus: Release 10.2.0.2.0 - Production on Tue Jan 29 08:54:10 2008
Copyright (c) 1982, 2005, Oracle. All Rights Reserved.
Connected to an idle instance.
SQL> startup open
ORA-00443: background process "PMON" did not start
The alert log shows:
29-JAN-2008 08:54:14.63:
Process PMON died, see its trace file
USER: terminating instance due to error 443
Instance terminated by USER, pid = 242cd04c
From ora_dump:<node>_<sid>_FG_ORACLE_000.TRC :
The trace file of the foreground process starting the Instance contains these messages:
*** 2008-01-29 08:54:14.635
Process PMON is dead (pid=242cd851, state=3):
*** 2008-01-29 08:54:14.642
KSTDUMP: In-memory trace dump
TIME:SEQ# ORAPID SID EVENT OP DATA
========================================================================
B2D0D048:00000003 149 0 10254 34 KSBS1P: process USER trying to start background PMON
B2E04550:00000008 149 0 10254 51 KSBS1P: out of loop: process did not start
KSTDUMP: End of in-memory trace dump
*** 2008-01-29 08:54:14.644
Changes
OpenVMS logicals had been created in an attempt to control whether a dump file would be created for pmon if the pmon process died. The name of the logical was incorrect.
$ define /sys/exec ORA_<instance name>_PMON false
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 |
| Changes |
| Cause |
| Solution |
| References |