cancel
Showing results for 
Search instead for 
Did you mean: 

ORACLE NOT COMING UP AFTER UPGRADE to 10.0.2.0.4

Former Member
0 Kudos

Hi

In an Oracle upgraded system from 10.0.2.0.2 to 10.0.2.0.4 , ORACLE is not coming up

with following messages

when i type SQL> startup force

ORA-01092: ORACLE instance terminated. Disconnection forced

also

When i type

hostname> ./dbua

am getting

JVMXM008: Error occured while initialising System ClassException in thread "main" Could not create the Java virtual machine.

Regards

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Also find the last 100 lines from alert SID.log**************************

Specified value of sga_max_size is too small, bumping to 616562688

sskgpgetexecname failed to get name

LICENSE_MAX_SESSION = 0

LICENSE_SESSIONS_WARNING = 0

Picked latch-free SCN scheme 3

Autotune of undo retention is turned on.

LICENSE_MAX_USERS = 0

SYS auditing is disabled

ksdpec: called for event 13740 prior to event group initialization

Starting up ORACLE RDBMS Version: 10.2.0.4.0.

System parameters with non-default values:

processes = 400

sessions = 800

event = 10028 trace name context forever, level 1, 10027 trace name context forever, level 1, 10162 trace name context forever, level 1, 38068 trace name context forever, level 100, 10629 trace name context forever, level 1, 38087 trace name context forever, level 1

sga_max_size = 616562688

shared_pool_size = 293601280

filesystemio_options = setall

control_files = /oracle/DBB/origlogA/cntrl/cntlrDBB.dbf, /oracle/DBB/origlogB/cntrl/cntrlDBB.dbf, /oracle/DBB/sapdata1/cntrl/cntrlDBB.dbf

control_file_record_keep_time= 30

db_block_size = 8192

db_cache_size = 293601280

compatible = 10.2.0

log_archive_dest = /oracle/DBB/oraarch/DBBarch

log_buffer = 2040832

log_checkpoint_interval = 0

db_files = 254

log_checkpoints_to_alert = TRUE

dml_locks = 4000

replication_dependency_tracking= FALSE

undo_management = AUTO

undo_tablespace = PSAPUNDO

inmemory_undo = FALSE

undo_retention = 43200

recyclebin = off

remote_os_authent = TRUE

remote_login_passwordfile= EXCLUSIVE

job_queue_processes = 1

parallel_max_servers = 20

parallel_execution_message_size= 16384

background_dump_dest = /oracle/DBB/saptrace/background

user_dump_dest = /oracle/DBB/saptrace/usertrace

max_dump_file_size = 20000

core_dump_dest = /oracle/DBB/saptrace/background

optimizer_features_enable= 10.2.0.1

sort_area_size = 2097152

sort_area_retained_size = 0

db_name = DBB

open_cursors = 800

sortelimination_cost_ratio= 10

btree_bitmap_plans = FALSE

star_transformation_enabled= TRUE

parallel_threads_per_cpu = 1

query_rewrite_enabled = FALSE

indexjoin_enabled = FALSE

optimpeek_user_binds = FALSE

pga_aggregate_target = 386547056

workarea_size_policy = AUTO

statistics_level = typical

optimizermjc_enabled = FALSE

PMON started with pid=2, OS id=1388620

PSP0 started with pid=3, OS id=1282090

MMAN started with pid=4, OS id=1110138

DBW0 started with pid=5, OS id=864434

LGWR started with pid=6, OS id=848030

CKPT started with pid=7, OS id=716928

SMON started with pid=8, OS id=1441840

RECO started with pid=9, OS id=1364174

CJQ0 started with pid=10, OS id=1355930

MMON started with pid=11, OS id=1351838

MMNL started with pid=12, OS id=1413306

Tue Oct 27 13:01:46 2009

ALTER DATABASE MOUNT

Tue Oct 27 13:01:50 2009

Setting recovery target incarnation to 1

Tue Oct 27 13:01:50 2009

Successful mount of redo thread 1, with mount id 1022367290

Tue Oct 27 13:01:50 2009

Database mounted in Exclusive Mode

Completed: ALTER DATABASE MOUNT

Tue Oct 27 13:01:50 2009

ALTER DATABASE OPEN

Tue Oct 27 13:01:50 2009

Thread 1 opened at log sequence 4620

Current log# 4 seq# 4620 mem# 0: /oracle/DBB/origlogB/log_g14m1.dbf

Current log# 4 seq# 4620 mem# 1: /oracle/DBB/mirrlogB/log_g14m2.dbf

Successful open of redo thread 1

Tue Oct 27 13:01:50 2009

MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set

Tue Oct 27 13:01:50 2009

SMON: enabling cache recovery

Tue Oct 27 13:01:50 2009

Errors in file /oracle/DBB/saptrace/usertrace/dbb_ora_1491064.trc:

ORA-00704: bootstrap process failure

ORA-39700: database must be opened with UPGRADE option

Tue Oct 27 13:01:50 2009

Error 704 happened during db open, shutting down database

USER: terminating instance due to error 704

Instance terminated by USER, pid = 1491064

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

sunny_pahuja2
Active Contributor
0 Kudos

Hi,

Check SAP Note 582427 - Error due to inconsistent Oracle DDIC

Thanks

Sunny

Former Member
0 Kudos

Hi,

You need to start the database in upgrade mode e.g startup upgrade

Then you need to run two cat*.sql scripts...these will be located in in $ORACLE_HOME/rdbms/admin ( please check for names in the DB upgrade guide

You will be able to shutdown immediate and startup as normal.

Mark

Edited by: Mark Norman on Oct 27, 2009 10:29 AM

Former Member
0 Kudos

HI,

ORA-00704: bootstrap process failure 
ORA-39700: database must be opened with UPGRADE

I think you have not done the post processing tasks.as suggested by Mark see the Readme file provided with the Patch.

Also see the below steps.

a. Log in as the Oracle software owner user

b. For single-instance installations, start the listener as follows

$ lsnrctl start

c. For single-instance installations, use SQL*Plus to log in to the database as the SYS user with SYSDBA privileges:

$ sqlplus /nolog

SQL> CONNECT SYS AS SYSDBA

Enter password:SYS_password

Enter the following SQL*Plus commands:

SQL> STARTUP UPGRADE

SQL> SPOOL patch.log

SQL> @?/rdbms/admin/catupgrd.sql

SQL> SPOOL OFF

d. Review the patch.log file for errors and inspect the list of components that is displayed at the end of catupgrd.sql script.

e. This list provides the version and status of each SERVER component in the database.

f. If necessary, rerun the catupgrd.sql script after correcting any problems.

g. Restart the database:

SQL> SHUTDOWN IMMEDIATE

SQL> STARTUP

h. Run the utlrp.sql script to recompile all invalid PL/SQL packages now instead of when the packages are accessed for the first time. This step is optional but recommended.

SQL> @?/rdbms/admin/utlrp.sql

i. Run the following command to check the status of all the components after the upgrade:

SQL> SELECT COMP_NAME, VERSION, STATUS FROM SYS.DBA_REGISTRY;

In the output of the preceding command, the status of all the components should be VALID for a successful upgrade

Hope this helps you.

Thanks,

Shambo

Answers (0)