Product

Platform

Operating system

Error

1) Prinergy diagnostics logs shows database errors when starting up: 'E 24Jul00 10:25:04.093-PDT [525.407] LINOSERVER ARAXI PChangeJobShare.main iDBIF_ThrowDBException.cpp(101): A general database failure has occured: [SERVERERROR] Error from Server: ORA-01033: ORACLE initialization or shutdown in progress'.

2) Main Directory and Registered File daemons crash when Workshop is started.

3) Oracle database log file: D:\Orant\RDBMS80\Trace\creoALRT.log (Prinergy1.1) or D:\Ora816\Rdbms\Trace\creoALRT.log (Prinergy 2.0) shows the message: 'ORA-214 signalled during: alter database mount...'.

Symptoms

The database files were backed up then restored.

When starting workshop, Main Directory daemon and Registered File daemon crash.

Cause

For Prinergy 1.1 systems, one is D:\Orant\Oracle\ControlFile\ctl2creo.ora and the other is E:\Orant\Oracle\MirroredControlFile\ctl1creo.ora.

For Prinergy 2.0 systems, one is G:\Orant\Oracle\ControlFile\ctl2creo.ora and the other is E:\Orant\Oracle\MirroredControlFile\ctl1creo.ora.

These files are mirror copies of each other. If the two files do not match, Oracle will fail to start.

Solution

The most recent control file must be replicated in the other location.

To identify which control file is more current, do the following:

1) Open a command prompt window and for Prinergy 1.1 systems, start SVRMGR30, for Prinergy 2.0 systems, start SVRMGRL:

D:\> SVRMGR30 (or SVRMGRL for Prinergy 2.0)

2) In SVRMGR30 (SVRMGRL), enter:

SVRMGR> connect internal/creo

SVRMGR> shutdown immediate;

SVRMGR> startup

If the startup fails with this error message, compare the version number of each control file:

ORA-00214: controlfile 'D:\ORANT\ORACLE\CONTROLFILE\CTL2CREO.ORA' version 7414 inconsistent with file 'E:\ORANT\ORACLE\MIRROREDCONTROLFILE\CTL1CREO.ORA' version 1109

The file with the higher version number is the most recent control file. In this case, D:\Orant\Oracle\ControlFile\ctl2creo.ora is the most recent file (version 7414).

Note: The version number is incremented whenever the control file is written to. Therefore your version numbers may be different than those shown in the example above.

To fix the database, do the following:

1) Move the older control file out of the folder, copy the more recent control file and rename it to be identical to the file removed.

2) Start up the database:

SVRMGR> shutdown immediate;

SVRMGR> startup

A successful startup will display the message 'Database opened' as shown below:

Total System Global Area 18751488 bytes

Fixed Size 49152 bytes

Variable Size 8388608 bytes

Database Buffers 10240000 bytes

Redo Buffers 73728 bytes

Database mounted.

Database opened.

Permanent fix:

See also

Keywords

daemon, oracle, workshop

Technical contact(s)

Stan Yoshida

Submitted by

Date submitted