Ansicht
Dokumentation

Problems when starting up a DB
Tip-No.: 387 ( INFO387 )

Short text

Problems when starting up a DB
Tip-No.: 387

Symptom

DB cannot be started. No error message after approx. 1/2 hour.
Data base processes do not have a CPU time.

Cause

1. In the archive directlry (default: $ORACLE_HOME/saparch), not
enough space is available to write a required archive file.
2. DB was abnormally shut down while it was in the middle of archiving.
(e.g. shutdown abort). A partially written archive file with the
current archive number exists.

Solution

1. Start brarchive to creat space in the archive directory.
The data base then finishes writing the current archive file (takes
up to 15 min.) and automatically has status "open".

2. Since the archiver has already written a portion of the files,
it finds an existing file with the current name upon startup.

Compare the size of the archive file with the highest sequence
number with the size of the other archive files:
cd $ORACLE_HOME/saparch
ls -l *arch*

Observe whether the size of the file continues to increase.

If it does not grow, save the file under another name:

mv C11arch_<#> C11arch_<#>.bak

The archive process then writes this last file again.
The DB then has open status.