Solved: Oracle DB can be opened with "upgrade" only - SAP Community

Gurus:

I am doing a heterogeneous system copy and I am at step "create Database" on the target. I get following errors. I applied many fixed found online but still

cannot solve it. Thanks for help.

SYS auditing is disabled

ksdpec: called for event 13740 prior to event group initialization

Starting up ORACLE RDBMS Version: 10.2.0.5.0.

System parameters with non-default values:

processes = 350

sessions = 700

event = 10191 trace name context forever, level 1

sga_max_size = 167084294144

shared_pool_size = 83483426816

shared_pool_reserved_size= 8346981629

filesystemio_options = setall

control_files = /oracle/DEV/origlogA/cntrl/cntrlDEV.dbf, /oracle/DEV/origlogB/cntrl/cntrlDEV.dbf, /oracle/DEV/sapdata1/cntrl/cntrlDEV.dbf

control_file_record_keep_time= 30

db_block_size = 8192

db_cache_size = 83483426816

compatible = 10.2.0

log_archive_dest = /oracle/DEV/oraarch/DEVarch

log_buffer = 14166016

log_checkpoints_to_alert = TRUE

dml_locks = 17500

replication_dependency_tracking= FALSE

undo_management = AUTO

undo_tablespace = PSAPUNDO

_in_memory_undo = FALSE

undo_retention = 43200

recyclebin = off

remote_os_authent = TRUE

remote_login_passwordfile= EXCLUSIVE

job_queue_processes = 1

parallel_execution_message_size= 16384

_table_lookup_prefetch_size= 0

background_dump_dest = /oracle/DEV/saptrace/background

user_dump_dest = /oracle/DEV/saptrace/usertrace

core_dump_dest = /oracle/DEV/saptrace/background

audit_file_dest = /oracle/DEV/saptrace/usertrace

db_name = DEV

open_cursors = 2000

_sort_elimination_cost_ratio= 10

_b_tree_bitmap_plans = FALSE

star_transformation_enabled= true

query_rewrite_enabled = false

_index_join_enabled = FALSE

_optim_peek_user_binds = FALSE

pga_aggregate_target = 111293088399

_optimizer_mjc_enabled = FALSE

PMON started with pid=2, OS id=3931

PSP0 started with pid=3, OS id=3934

MMAN started with pid=4, OS id=3936

DBW0 started with pid=5, OS id=3938

DBW1 started with pid=6, OS id=3941

DBW2 started with pid=7, OS id=3943

LGWR started with pid=8, OS id=3945

CKPT started with pid=9, OS id=3947

SMON started with pid=10, OS id=3949

RECO started with pid=11, OS id=3951

CJQ0 started with pid=12, OS id=3953

MMON started with pid=13, OS id=3955

MMNL started with pid=14, OS id=3957

Sat Mar 30 20:40:02 UTC 2013

ALTER DATABASE MOUNT

Sat Mar 30 20:40:07 UTC 2013

Setting recovery target incarnation to 1

Sat Mar 30 20:40:07 UTC 2013

Successful mount of redo thread 1, with mount id 3869261602

Sat Mar 30 20:40:07 UTC 2013

Database mounted in Exclusive Mode

Completed: ALTER DATABASE MOUNT

Sat Mar 30 20:40:07 UTC 2013

ALTER DATABASE OPEN

Sat Mar 30 20:40:07 UTC 2013

Beginning crash recovery of 1 threads

parallel recovery started with 16 processes

Sat Mar 30 20:40:08 UTC 2013

Started redo scan

Sat Mar 30 20:40:09 UTC 2013

Completed redo scan

1 redo blocks read, 0 data blocks need recovery

Sat Mar 30 20:40:09 UTC 2013

Warning: recovery process cannot use async I/O

Sat Mar 30 20:40:09 UTC 2013

Warning: recovery process cannot use async I/O

Sat Mar 30 20:40:09 UTC 2013

Warning: recovery process cannot use async I/O

Sat Mar 30 20:40:09 UTC 2013

Warning: recovery process cannot use async I/O

Sat Mar 30 20:40:09 UTC 2013

Warning: recovery process cannot use async I/O

Sat Mar 30 20:40:09 UTC 2013

Warning: recovery process cannot use async I/O

Sat Mar 30 20:40:09 UTC 2013

Warning: recovery process cannot use async I/O

Sat Mar 30 20:40:09 UTC 2013

Warning: recovery process cannot use async I/O

Sat Mar 30 20:40:09 UTC 2013

Warning: recovery process cannot use async I/O

Sat Mar 30 20:40:09 UTC 2013

Warning: recovery process cannot use async I/O

Sat Mar 30 20:40:09 UTC 2013

Warning: recovery process cannot use async I/O

Sat Mar 30 20:40:09 UTC 2013

Warning: recovery process cannot use async I/O

Sat Mar 30 20:40:09 UTC 2013

Warning: recovery process cannot use async I/O

Sat Mar 30 20:40:09 UTC 2013

Warning: recovery process cannot use async I/O

Sat Mar 30 20:40:09 UTC 2013

Warning: recovery process cannot use async I/O

Sat Mar 30 20:40:09 UTC 2013

Warning: recovery process cannot use async I/O

Sat Mar 30 20:40:09 UTC 2013

Started redo application at

Thread 1: logseq 17, block 2, scn 380902

Sat Mar 30 20:40:09 UTC 2013

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

Mem# 0: /oracle/DEV/origlogA/log_g11m1.dbf

Mem# 1: /oracle/DEV/mirrlogA/log_g11m2.dbf

Sat Mar 30 20:40:09 UTC 2013

Completed redo application

Sat Mar 30 20:40:09 UTC 2013

Completed crash recovery at

Thread 1: logseq 17, block 3, scn 400904

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

Sat Mar 30 20:40:09 UTC 2013

Thread 1 advanced to log sequence 18 (thread open)

Thread 1 opened at log sequence 18

Current log# 2 seq# 18 mem# 0: /oracle/DEV/origlogB/log_g12m1.dbf

Current log# 2 seq# 18 mem# 1: /oracle/DEV/mirrlogB/log_g12m2.dbf

Successful open of redo thread 1

Sat Mar 30 20:40:09 UTC 2013

MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set

Sat Mar 30 20:40:09 UTC 2013

SMON: enabling cache recovery

Sat Mar 30 20:40:09 UTC 2013

Errors in file /oracle/DEV/saptrace/usertrace/DEV_ora_4145.trc:

ORA-00704: bootstrap process failure

ORA-39700: database must be opened with UPGRADE option

Sat Mar 30 20:40:09 UTC 2013

Error 704 happened during db open, shutting down database

USER: terminating instance due to error 704

Instance terminated by USER, pid = 4145

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

catcity5:DEV :/oracle/DEV/saptrace/background>

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (1)

Accepted Solutions (1)

Hi,

Please execute the following.

1 . alter database open upgrade;

2.shutdown immediate

Then start the oracle using startup and check whether it is gettnig started correctly.

Please check and provide your feedback.

Thanks and Regards,

Vimal

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Answers (1)

Answers (1)

Vimal:

You are GREAT!! I might have more question today, would you please help more. Best regards!!

catcity5:DEV :/oracle/DEV/saptrace/background> !1
sqlplus "/as sysdba"

SQL*Plus: Release 10.2.0.5.0 - Production on Sun Mar 31 12:32:32 2013

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

Connected to an idle instance.

SQL> alter database open upgrade;

alter database open upgrade
*
ERROR at line 1:
ORA-01034: ORACLE not available

SQL> SQL> alter database open upgrade;
alter database open upgrade
*
ERROR at line 1:
ORA-01034: ORACLE not available

SQL> startup upgrade;
ORACLE instance started.

Total System Global Area 1.6708E+11 bytes
Fixed Size                  2385144 bytes
Variable Size            8.3584E+10 bytes
Database Buffers         8.3483E+10 bytes
Redo Buffers               14389248 bytes
Database mounted.
Database opened.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Sure .

Please let us know the issues you are facing.

Vimal:

I am sorry that I worked overnight so that I was confused.

Actaully what I want is to start it without "upgarde" option. I still cannot make it:

Would you please help?

Thanks a lot!

SQL> startup upgrade;
ORACLE instance started.

Total System Global Area 1.6708E+11 bytes
Fixed Size                  2385144 bytes
Variable Size            8.3584E+10 bytes
Database Buffers         8.3483E+10 bytes
Redo Buffers               14389248 bytes
Database mounted.
Database opened.
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup;
ORACLE instance started.

Total System Global Area 1.6708E+11 bytes
Fixed Size                  2385144 bytes
Variable Size            8.3584E+10 bytes
Database Buffers         8.3483E+10 bytes
Redo Buffers               14389248 bytes
Database mounted.
ORA-01092: ORACLE instance terminated. Disconnection forced

in alert_DEV.log:
ALTER DATABASE OPEN
Sun Mar 31 13:10:19 UTC 2013
Thread 1 opened at log sequence 26
Current log# 2 seq# 26 mem# 0: /oracle/DEV/origlogB/log_g12m1.dbf
Current log# 2 seq# 26 mem# 1: /oracle/DEV/mirrlogB/log_g12m2.dbf
Successful open of redo thread 1
Sun Mar 31 13:10:19 UTC 2013
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Sun Mar 31 13:10:19 UTC 2013
SMON: enabling cache recovery
Sun Mar 31 13:10:19 UTC 2013
Errors in file /oracle/DEV/saptrace/usertrace/DEV_ora_12902.trc:
ORA-00704: bootstrap process failure
ORA-39700: database must be opened with UPGRADE option
Sun Mar 31 13:10:19 UTC 2013
Error 704 happened during db open, shutting down database
USER: terminating instance due to error 704
Instance terminated by USER, pid = 12902
ORA-1092 signalled during: ALTER DATABASE OPEN...

catcity5:DEV :/oracle/DEV/saptrace/background> more /oracle/DEV/saptrace/usertrace/DEV_ora_12902.trc
/oracle/DEV/saptrace/usertrace/DEV_ora_12902.trc
Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bit Production
With the Partitioning, Data Mining and Real Application Testing options
ORACLE_HOME = /oracle/DEV/102_64
System name:    HP-UX
Node name:      catcity5
Release:        B.11.31
Version:        U
Machine:        ia64
Instance name: DEV
Redo thread mounted by this instance: 1
Oracle process number: 0
Unix process pid: 12902, image: oracle@catcity5

Ioctl ASYNC_CONFIG error, errno = 1
*** ACTION NAME:() 2013-03-31 13:10:19.916
*** MODULE NAME:(sqlplus@catcity5 (TNS V1-V3)) 2013-03-31 13:10:19.916
*** SERVICE NAME:(SYS$USERS) 2013-03-31 13:10:19.916
*** SESSION ID:(687.3) 2013-03-31 13:10:19.916
ORA-00704: bootstrap process failure
ORA-39700: database must be opened with UPGRADE option

Okay.. Try this.

Shutdown the DB

1. Please login in as orasid

2. navigate to /oracle/DEV/112_64/rdbms/admin

3. you can see lot of sql files

4. now open the sqlplus "/as sysdba"

5. Execute @catproc.sql

6. startup upgrade

7.shutdown immediate

8.Startup

This should 99% should work.

Please share the feedback.

Vimal:

At step5, DB is still down, how to run that catproc.sql? You mean start DB with "upgrade" first?

i.e. swap step5 and 6?

Will catproc.sql damage DB?

Thanks and best regards.

Ask a Question

Top Q&A Solution Author

User

Count

85

10

10

9

7

6

5

5

4

3