cancel
Showing results for 
Search instead for 
Did you mean: 

ORA-00704: bootstrap process failure, even after recovery

Former Member
0 Kudos

Hello friends,

Unable to open Oracle database due to following error

SQL> startup

ORACLE instance started.

Total System Global Area 3038745176 bytes

Fixed Size 746072 bytes

Variable Size 654311424 bytes

Database Buffers 2382364672 bytes

Redo Buffers 1323008 bytes

Database mounted.

ORA-01092: ORACLE instance terminated. Disconnection forced

<b>Alert Log:</b>

db_domain = WORLD

hash_join_enabled = FALSE

background_dump_dest = /oracle/<SID>/saptrace/background

user_dump_dest = /oracle/<SID>/saptrace/usertrace

core_dump_dest = /oracle/<SID>/saptrace/background

sort_area_size = 2097152

sort_area_retained_size = 0

db_name = <SID>

open_cursors = 800

optimizer_mode = choose

btree_bitmap_plans = FALSE

eliminatecommon_subexpr= FALSE

pushjoin_predicate = FALSE

optimizer_index_cost_adj = 10

optimpeek_user_binds = FALSE

statistics_level = TYPICAL

PMON started with pid=2

DBW0 started with pid=3

LGWR started with pid=4

CKPT started with pid=5

SMON started with pid=6

RECO started with pid=7

Mon Oct 1 23:27:55 2007

ARCH: STARTING ARCH PROCESSES

ARC0 started with pid=8

ARC0: Archival started

ARC1 started with pid=9

ARC1: Archival started

Mon Oct 1 23:27:55 2007

ARCH: STARTING ARCH PROCESSES COMPLETE

Mon Oct 1 23:27:55 2007

ARC0: Becoming the 'no FAL' ARCH

ARC0: Becoming the 'no FAL' ARCHARC0: Thread not mounted

Mon Oct 1 23:27:55 2007

ARC1: Becoming the heartbeat ARCH

ARC1: Becoming the heartbeat ARCHARC1: Thread not mounted

Mon Oct 1 23:27:55 2007

ALTER DATABASE MOUNT

Mon Oct 1 23:27:59 2007

Successful mount of redo thread 1, with mount id 1698519931

Mon Oct 1 23:27:59 2007

Database mounted in Exclusive Mode.

Completed: ALTER DATABASE MOUNT

Mon Oct 1 23:27:59 2007

ALTER DATABASE OPEN

Mon Oct 1 23:27:59 2007

Beginning crash recovery of 1 threads

Mon Oct 1 23:27:59 2007

Started redo scan

Mon Oct 1 23:27:59 2007

Completed redo scan

1 redo blocks read, 0 data blocks need recovery

Mon Oct 1 23:27:59 2007

Started recovery at

Thread 1: logseq 4, block 2, scn 1.538088298

Mon Oct 1 23:27:59 2007

Recovery of Online Redo Log: Thread 1 Group 18 Seq 4 Reading mem 0

Mem# 0 errs 0: /oracle/<SID>/origlogB/log_g18_m1.dbf

Mem# 1 errs 0: /oracle/<SID>/mirrlogB/log_g18_m2.dbf

Mon Oct 1 23:27:59 2007

Completed redo application

Mon Oct 1 23:27:59 2007

Ended recovery at

Thread 1: logseq 4, block 3, scn 1.538108299

0 data blocks read, 0 data blocks written, 1 redo blocks read

Crash recovery completed successfully

Mon Oct 1 23:27:59 2007

LGWR: Primary database is in CLUSTER CONSISTENT mode

Thread 1 advanced to log sequence 5

Thread 1 opened at log sequence 5

Current log# 15 seq# 5 mem# 0: /oracle/<SID>/origlogA/log_g15_m1.dbf

Current log# 15 seq# 5 mem# 1: /oracle/<SID>/mirrlogA/log_g15_m2.dbf

Successful open of redo thread 1

Mon Oct 1 23:27:59 2007

MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set

Mon Oct 1 23:27:59 2007

ARC1: Evaluating archive log 18 thread 1 sequence 4

Mon Oct 1 23:27:59 2007

ARC0: Evaluating archive log 18 thread 1 sequence 4

ARC0: Unable to archive log 18 thread 1 sequence 4

Log actively being archived by another process

Mon Oct 1 23:27:59 2007

SMON: enabling cache recovery

Mon Oct 1 23:27:59 2007

ARC1: Beginning to archive log 18 thread 1 sequence 4

Creating archive destination LOG_ARCHIVE_DEST_1: '/oracle/<SID>/saparch/<SID>arch1_4.dbf'

ARC1: Completed archiving log 18 thread 1 sequence 4

Mon Oct 1 23:27:59 2007

Errors in file /oracle/<SID>/saptrace/usertrace/<sid>_ora_598178.trc:

ORA-00600: internal error code, arguments: [4000], [19], [], [], [], [], [], []

Mon Oct 1 23:28:00 2007

Errors in file /oracle/<SID>/saptrace/usertrace/<sid>_ora_598178.trc:

ORA-00704: bootstrap process failure

ORA-00704: bootstrap process failure

ORA-00600: internal error code, arguments: [4000], [19], [], [], [], [], [], []

Mon Oct 1 23:28:00 2007

Error 704 happened during db open, shutting down database

USER: terminating instance due to error 704

Instance terminated by USER, pid = 598178

ORA-1092 signalled during: ALTER DATABASE OPEN...

Any suggestions?

Regards,

Ammey Kesarkar

Accepted Solutions (0)

Answers (2)

Answers (2)

former_member204746
Active Contributor
0 Kudos

I had the same error a while ago. there was a parameter in init[SID].ora that was bad. it was a parameter with a pathname. please supply this file and check that all paths really exists.

Former Member
0 Kudos

Our junior consultant had performed incorrect recovery & corrupted the database..

We are restoring from last known good backup to solve the problem.

Thank you Fidel Vales & Eric Brunelle for your replies.

Your replies were very helpful

Regards,

Ammey Kesarkar

fidel_vales
Employee
Employee
0 Kudos

Hi,

The error ORA-704 is probably caused by the previous one:

ORA-00600: internal error code, arguments: [4000], [19], [], [], [], [], [], []

There is a note in SAP about this error but it is old ( ORA-00600 [4000] after migration 7.X -> 8.0.6.1 HP ) I assume you are not running any of the mentioned versions.

There is an oracle note explaining what this is:

ORA-600 [4000] "trying to get dba of undo segment header block from usn" and some bugs associated.

My advice is to open a SAP message indicating the ORA-600. Provide the alert log, the trace created ( /oracle/<SID>/saptrace/usertrace/<sid>_ora_598178.trc), information about your OS, DB version and patches applied.