Oracle database not getting Up after patch upgrade

[Former Member]

Hi,

I have upgraded my oracle database from 10.0.2.1 to 10.0.2.4. after this databse is not coming up. I am able to start/stop listner but while starting SAP it is not able to start databse. Pasting error log below.

-

---

Wed Jun 24 14:56:45 PDT 2009

LOGFILE FOR STARTING ORACLE

Trying to start CRD database ...

-

---

Wed Jun 24 14:56:45 PDT 2009

checking required environment variables

ORACLE_HOME is >/oracle/CRD/102_64<

ORACLE_SID is >CRD<

-

---

Wed Jun 24 14:56:45 PDT 2009

check initora

-

---

Wed Jun 24 14:56:45 PDT 2009

check initora

-

---

Wed Jun 24 14:56:45 PDT 2009

checking V2 connect

TNS Ping Utility for Linux: Version 10.2.0.4.0 - Production on 24-JUN-2009 14:56:45

Copyright (c) 1997, 2007, Oracle. All rights reserved.

Used parameter files:

/usr/sap/CRD/SYS/profile/oracle/sqlnet.ora

Used TNSNAMES adapter to resolve the alias

Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (COMMUNITY = SAP.WORLD) (PROTOCOL = TCP) (HOST = CRM) (PORT = 1527))) (CONNECT_DATA = (SID =

CRD) (GLOBAL_NAME = CRD.WORLD)))

OK (0 msec)

tnsping: V2 connect to CRD

-

---

Wed Jun 24 14:56:45 PDT 2009

Connect to the database to check the database state:

R3trans: connect check finished with return code: 12

Database not available

-

---

Wed Jun 24 14:56:45 PDT 2009

Shutdown database

First trying to shutdown the database - May be,

the database is in the nomount or mount state

-

---

Wed Jun 24 14:56:45 PDT 2009

starting database

SQL*Plus: Release 10.2.0.4.0 - Production on Wed Jun 24 14:56:45 2009

Copyright (c) 1982, 2007, Oracle. All Rights Reserved.

Connected to an idle instance.

ORACLE instance started.

Total System Global Area 1224736768 bytes

Fixed Size 2083560 bytes

Variable Size 620758296 bytes

Database Buffers 587202560 bytes

Redo Buffers 14692352 bytes

Database mounted.

ORA-01092: ORACLE instance terminated. Disconnection forced

Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production

With the Partitioning, Data Mining and Real Application Testing options

-

---

Wed Jun 24 14:56:53 PDT 2009

Connect to the database to verify, that the database is now open

R3trans check finished with return code: 12

• ERROR: Startup of database failed

Notify Database Administrator.

/usr/sap/CRD/SYS/exe/run/startdb: Terminating with error code 12

thanks,

Bhanu

[markus_doehr2]

Did you do all the post processing for the upgrade? It's not enough to just execute the runInstaller and install the software... (means startup migrate etc.)

Markus

[Former Member]

Hi Markus,

I am not DBA so didn't performed any post processing steps. I have only applied the patch using OUI.

Can you please let me know what all the steps required after this.

Thanks,

Bhanu

[Former Member]

Hi,

I have tried to start and stop oracle from SPLplus but no luck. i am pasting alert log file which is saying some block courruption......

Starting up ORACLE RDBMS Version: 10.2.0.4.0.

System parameters with non-default values:

processes = 80

sessions = 96

event = 10191 trace name context forever, level 1

sga_max_size = 1224736768

shared_pool_size = 587202560

shared_pool_reserved_size= 57982058

filesystemio_options = setall

control_files = /oracle/CRD/origlogA/cntrl/cntlrCRD.dbf, /oracle/CRD/origlogB/cntrl/cntrlCRD.dbf, /oracle/CRD/sapdata1/cntrl/cntrlCRD.dbf

control_file_record_keep_time= 30

db_block_size = 8192

db_cache_size = 587202560

compatible = 10.2.0

log_archive_dest = /oracle/CRD/oraarch/CRDarch

log_buffer = 14246912

log_checkpoint_interval = 0

db_files = 254

log_checkpoints_to_alert = TRUE

dml_locks = 4000

undo_management = AUTO

undo_tablespace = PSAPUNDO

undo_retention = 43200

recyclebin = off

remote_os_authent = TRUE

remote_login_passwordfile= EXCLUSIVE

job_queue_processes = 1

background_dump_dest = /oracle/CRD/saptrace/background

user_dump_dest = /oracle/CRD/saptrace/usertrace

core_dump_dest = /oracle/CRD/saptrace/background

optimizer_features_enable= 10.2.0.1

sort_area_size = 2097152

sort_area_retained_size = 0

db_name = CRD

open_cursors = 800

optimpeek_user_binds = FALSE

pga_aggregate_target = 773094113

workarea_size_policy = AUTO

statistics_level = typical

PMON started with pid=2, OS id=25204

PSP0 started with pid=3, OS id=25206

MMAN started with pid=4, OS id=25208

DBW0 started with pid=5, OS id=25210

LGWR started with pid=6, OS id=25212

CKPT started with pid=7, OS id=25214

SMON started with pid=8, OS id=25216

RECO started with pid=9, OS id=25218

CJQ0 started with pid=10, OS id=25220

MMON started with pid=11, OS id=25222

MMNL started with pid=12, OS id=25224

Wed Jun 24 15:06:19 2009

ALTER DATABASE MOUNT

Wed Jun 24 15:06:24 2009

Setting recovery target incarnation to 1

Wed Jun 24 15:06:24 2009

Successful mount of redo thread 1, with mount id 182910572

Wed Jun 24 15:06:24 2009

Database mounted in Exclusive Mode

Completed: ALTER DATABASE MOUNT

Wed Jun 24 15:06:24 2009

ALTER DATABASE OPEN

Wed Jun 24 15:06:24 2009

Beginning crash recovery of 1 threads

parallel recovery started with 2 processes

Wed Jun 24 15:06:24 2009

Started redo scan

Wed Jun 24 15:06:24 2009

Completed redo scan

1 redo blocks read, 0 data blocks need recovery

Wed Jun 24 15:06:24 2009

Started redo application at

Thread 1: logseq 16126, block 2, scn 1104239482

Wed Jun 24 15:06:24 2009

Recovery of Online Redo Log: Thread 1 Group 2 Seq 16126 Reading mem 0

Mem# 0: /oracle/CRD/origlogB/log_g12m1.dbf

Mem# 1: /oracle/CRD/mirrlogB/log_g12m2.dbf

Wed Jun 24 15:06:24 2009

Completed redo application

Wed Jun 24 15:06:24 2009

Completed crash recovery at

Thread 1: logseq 16126, block 3, scn 1104259484

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

Wed Jun 24 15:06:25 2009

LGWR: STARTING ARCH PROCESSES

ARC0 started with pid=16, OS id=25232

Wed Jun 24 15:06:25 2009

ARC0: Archival started

ARC1: Archival started

LGWR: STARTING ARCH PROCESSES COMPLETE

ARC1 started with pid=17, OS id=25234

Wed Jun 24 15:06:25 2009

Thread 1 advanced to log sequence 16127 (thread open)

Thread 1 opened at log sequence 16127

Current log# 3 seq# 16127 mem# 0: /oracle/CRD/origlogA/log_g13m1.dbf

Current log# 3 seq# 16127 mem# 1: /oracle/CRD/mirrlogA/log_g13m2.dbf

Successful open of redo thread 1

Wed Jun 24 15:06:25 2009

MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set

Wed Jun 24 15:06:25 2009

ARC0: Becoming the 'no FAL' ARCH

ARC0: Becoming the 'no SRL' ARCH

Wed Jun 24 15:06:25 2009

ARC1: Becoming the heartbeat ARCH

Wed Jun 24 15:06:25 2009

SMON: enabling cache recovery

Wed Jun 24 15:06:25 2009

Errors in file /oracle/CRD/saptrace/usertrace/crd_ora_25226.trc:

ORA-00704: bootstrap process failure

ORA-39700: database must be opened with UPGRADE option

Wed Jun 24 15:06:25 2009

Error 704 happened during db open, shutting down database

USER: terminating instance due to error 704

Instance terminated by USER, pid = 25226

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

Thanks,

Bhanu

[markus_doehr2]

Just read what you posted:

> ORA-00704: bootstrap process failure

> ORA-39700: database must be opened with UPGRADE option

So that is your problem.

Once advise: Oracle is a complex beast, VERY complex to be exact. It's also not enough to just install the 10.2.0.4 patch but there are interim-/mini-patches on top of it that fix errors you will very likely encounter if you don't apply those. And to install those mini-patches you need to update the program (Opatch), that will install the patches... The central note for that is

Note 1137346 - Oracle 10.2.0: Patches/patch collections for Oracle 10.2.0.4

Not trying to discourage you but without really knowing what you're doing it can be a very frustrating experience. Oracle can not be maintained by clicking only

Now to your problem:

In the directory where runInstaller.exe resides is a "readme.html", it will describe all necessary pre- and postinstallation steps to be done.

Read it and follow it, then open above note, download the patch for OPatch and the latest for your Windows available patch and install it. After that startup your database again and most of the known errors and problems with the database should no more appear.

Markus.

[Former Member]

Bhanu,

bootstrap process failure ORA-39700: database must be opened with UPGRADE option Wed Jun 24 15:06:25 2009

As i early reply start with upgrade option

SQL> startup upgrade

SQL>@<ORACLE_HOME>/rdbms/admin/catupgrade.sql

SQL>Shutdown ;

SQL>startup;

[former_member204746]

read your patch upgrade manual. it will explain steps to be taken. basically, you "startup upgrade" then run or 2 SQL scripts. check the README.html file that came with your patch.

[Former Member]

Hi All,

The problem is resolved after perfroming the post installation task. Thans all of you for your response on this issue.

Regards,

Bhanu

[sunny_pahuja2]

Hi Bhanu.

Please try below things:

1) stop SAP system

2) start database manualy from sql promopt..

3) then start SAP system..

4) if error persists then send trans.log and alert_<sid>.log

Thanks

Sunny

[Former Member]

send alter<sid>.log file

If you used optach in upgrade then you have to startup upgrade option

[Former Member]

Hello Banu,

Were you able to stop and start oracle from sql. Please try the following first

1. Check if oracle completely shutdown and also check no process are running.

2. Then try to bring up from sql

3. If it fails chek the alert log files

If you do not find anything useful in alert og files. Please post the alert log file.

If Oracle is up from sql and you cannot start from SAP. Please post R3trans log.

Thank You,

Praveen