cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to start Oracle

Former Member
0 Kudos

As part of Solution Manager installation, I have installed Oracle on Linux SLES 10. Installation of Oracle seems to be fine as I was able to execute the following:

sqlplus / as sysdba

SQL> select version from v$instance;

#####

Next, I stopped Oracle DB and installed the patches. I stopped using the commands (at the shell prompt):

> lsnrctl stop

> dbshut

After installing the patches, when i want to restart Oracle DB, I get the following error:

sqlplus / as sysdba

SQL> startup

ORACLE instance started.

Total System Global Area 1157627904 bytes

Fixed Size 2070648 bytes

Variable Size 587204488 bytes

Database Buffers 553648128 bytes

Redo Buffers 14704640 bytes

Database mounted.

ORA-01092: ORACLE instance terminated. Disconnection forced

####

Oracle documentation on ORA-01092 give the following info:

Cause: The instance this process was connected to was terminated abnormally, probably via a shutdown abort. This process was forced to disconnect from the instance.

Action: Examine the alert log for more details. When the instance has been restarted, retry action.

Any help to fix this problem is appreciated

Thanks,

Accepted Solutions (1)

Accepted Solutions (1)

markus_doehr2
Active Contributor
0 Kudos

Check your Oracle alert.log. It´s usually in $ORACLE_HOME/saptrace/background

--

Markus

Answers (1)

Answers (1)

Former Member
0 Kudos

Andrew,

ORA-01092 is some what generic error message. Can you take a look at the alert log file and post what you see there? Your init.ora file would tell you the location of that file (orahome/admin/sid/).

Thank you.

regards,

BMG

Former Member
0 Kudos

I could not find any alert logs. Neither $ORACLE_HOME/saptrace nor $ORACLE_HOME/admin directories exist.

Former Member
0 Kudos

Hello Andrew

It is under /oracle/SID/saptrace/background, please check there

Regards

Andreas

Former Member
0 Kudos

The contents of alert.log

...

...

Starting up ORACLE RDBMS Version: 10.2.0.2.0.

System parameters with non-default values:

processes = 80

sessions = 96

event = 10191 trace name context forever, level 1

sga_max_size = 1157627904

shared_pool_size = 553648128

shared_pool_reserved_size= 54697918

filesystemio_options = setall

control_files = /oracle/SDB/origlogA/cntrl/cntlrSDB.dbf, /oracle/SDB/origlogB/cntrl/cntrlSDB.dbf, /oracle/SDB/sapdata1/cntrl/cntrlSDB.dbf

control_file_record_keep_time= 30

db_block_size = 8192

db_cache_size = 553648128

compatible = 10.2.0

log_archive_dest = /oracle/SDB/oraarch/SDBarch

log_buffer = 14258176

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/SDB/saptrace/background

user_dump_dest = /oracle/SDB/saptrace/usertrace

core_dump_dest = /oracle/SDB/saptrace/background

optimizer_features_enable= 10.2.0.1

sort_area_size = 2097152

sort_area_retained_size = 0

db_name = SDB

open_cursors = 800

optimpeek_user_binds = FALSE

pga_aggregate_target = 729305579

workarea_size_policy = AUTO

statistics_level = typical

PMON started with pid=2, OS id=10465

PSP0 started with pid=3, OS id=10467

MMAN started with pid=4, OS id=10469

DBW0 started with pid=5, OS id=10471

LGWR started with pid=6, OS id=10473

CKPT started with pid=7, OS id=10475

SMON started with pid=8, OS id=10477

RECO started with pid=9, OS id=10479

CJQ0 started with pid=10, OS id=10481

MMON started with pid=11, OS id=10483

MMNL started with pid=12, OS id=10485

Thu Sep 13 09:52:56 2007

ALTER DATABASE MOUNT

Thu Sep 13 09:53:01 2007

Setting recovery target incarnation to 1

Thu Sep 13 09:53:01 2007

Successful mount of redo thread 1, with mount id 2149146488

Thu Sep 13 09:53:01 2007

Database mounted in Exclusive Mode

Completed: ALTER DATABASE MOUNT

Thu Sep 13 09:53:01 2007

ALTER DATABASE OPEN

Thu Sep 13 09:53:01 2007

Beginning crash recovery of 1 threads

parallel recovery started with 2 processes

Thu Sep 13 09:53:01 2007

Started redo scan

Thu Sep 13 09:53:01 2007

Completed redo scan

0 redo blocks read, 0 data blocks need recovery

Thu Sep 13 09:53:01 2007

Started redo application at

Thread 1: logseq 444, block 3, scn 3551197

Thu Sep 13 09:53:01 2007

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

Mem# 0 errs 0: /oracle/SDB/origlogB/log_g14m1.dbf

Mem# 1 errs 0: /oracle/SDB/mirrlogB/log_g14m2.dbf

Thu Sep 13 09:53:01 2007

Completed redo application

Thu Sep 13 09:53:01 2007

Completed crash recovery at

Thread 1: logseq 444, block 3, scn 3571198

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

Thu Sep 13 09:53:02 2007

LGWR: STARTING ARCH PROCESSES

ARC0 started with pid=16, OS id=10493

Thu Sep 13 09:53:02 2007

ARC0: Archival started

ARC1: Archival started

LGWR: STARTING ARCH PROCESSES COMPLETE

ARC1 started with pid=17, OS id=10495

Thu Sep 13 09:53:02 2007

Thread 1 advanced to log sequence 445

Thread 1 opened at log sequence 445

Current log# 1 seq# 445 mem# 0: /oracle/SDB/origlogA/log_g11m1.dbf

Current log# 1 seq# 445 mem# 1: /oracle/SDB/mirrlogA/log_g11m2.dbf

Successful open of redo thread 1

Thu Sep 13 09:53:02 2007

MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set

Thu Sep 13 09:53:02 2007

SMON: enabling cache recovery

Thu Sep 13 09:53:02 2007

ARC1: STARTING ARCH PROCESSES

Thu Sep 13 09:53:02 2007

ARC0: Becoming the 'no FAL' ARCH

ARC0: Becoming the 'no SRL' ARCH

Thu Sep 13 09:53:02 2007

ARC2: Archival started

ARC1: STARTING ARCH PROCESSES COMPLETE

ARC1: Becoming the heartbeat ARCH

ARC2 started with pid=18, OS id=10497

Thu Sep 13 09:53:02 2007

Incremental checkpoint up to RBA [0x1bd.3.0], current log tail at RBA [0x1bd.3.0]

Thu Sep 13 09:53:02 2007

Errors in file /oracle/SDB/saptrace/usertrace/sdb_ora_10487.trc:

ORA-00704: bootstrap process failure

ORA-39700: database must be opened with UPGRADE option

Thu Sep 13 09:53:02 2007

Error 704 happened during db open, shutting down database

USER: terminating instance due to error 704

Instance terminated by USER, pid = 10487

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

Former Member
0 Kudos

Hello again,

Looks like that your Oracle upgrade / installation hasn't been completed properly. The real error is

ORA-39700: database must be opened with UPGRADE option

Please check Note 582427 - Error due to inconsistent Oracle DDIC

Regards

Andreas