How to repair an Oracle service when corrupted

Printable View

09-23-2003, 07:28 AM
GKramer

How to repair an Oracle service when corrupted

Hi,

Due to a power failure (the server has gone down unexpectedly (no shutdown)) the OMS service has been corrupted.
When starting up the server a warning pops up with a "read" error on the agent and will not start up this service. Trying to start the OMS service by hand gives the following error (translated); "ERROR 1053; can not start service on this computer" .

It is unlikely that I have to reinstall the complete Oracle environment to repair these services but what do I have to do???

regards GKramer.
09-23-2003, 08:13 AM
abhaysk

What does event viewer say?
09-23-2003, 08:38 AM
GKramer

Abhaysk,

The event handler just pointed me into the direction of the logfile C:\oracle\ora92\sysman\log\oms.nohup (just the last part);

--------------------------------------------------------------------

OEMCTL for Windows NT: Version 9.2.0.1.0 Production
Copyright (c) 1998, 2002, Oracle Corporation. All rights reserved.
Starting the Oracle Management Server...VXA-3008 : Starting OMS Services, Wait.

The OMS is now started and ready.
statement =

SELECT EMAIL.email_address "EMAIL_ADDRESS", Email.subject_prefix "EMAIL_SUBJECT_PREFIX", Email.email_length "EMAIL_LENGTH", Email.email_filter "EMAIL_FILTER", Email.subject_format "EMAIL_SUBJECT_FORMAT", Email.body_header_format "EMAIL_BODY_HEADER_FORMAT", Email.body_detail_format "EMAIL_BODY_DETAIL_FORMAT", Page.is_page_to_email "IS_PAGE_TO_EMAIL", Page.carrier "CARRIER" , Page.pin "PIN", Page.page_email_id "PAGE_EMAIL_ID" , Page.page_prefix "PAGE_PREFIX", Page.page_data_length "PAGE_DATA_LENGTH", Page.page_filter "PAGE_FILTER", Page.body_header_format "PAGE_BODY_HEADER_FORMAT", Page.body_detail_format "PAGE_BODY_DETAIL_FORMAT" from SMP_VDV_SMTP_EMAIL Email, SMP_VDV_PAGE Page where Email.user_id = (SELECT user_id FROM SMP_VDV_USER WHERE user_name = ? ) AND Email.user_id = Page.user_id
exception VdnException{long exceptionId=5;wstring reason="VNI-4009 : Cannot contact agent on the node. Agent may be down or network communication to the node has failed.";sequence data={"q1000-ora.testzaal.meursgroep.nl"};}
at oracle.sysman.vdn.VdnTargetNamingService.discover(VdnTargetNamingService.java:10917)
at oracle.sysman.vdn.VdnTargetNamingService.discover(VdnTargetNamingService.java:10737)
at oracle.sysman.vdn._tie_VdnTargetDiscovery.discover(_tie_VdnTargetDiscovery.java:148)
at oracle.sysman.vdn._VdnTargetDiscoveryImplBase._execute(_VdnTargetDiscoveryImplBase.java:162)
at oracle.sysman.vdn._VdnTargetDiscoveryImplBase._execute(_VdnTargetDiscoveryImplBase.java:145)
at com.visigenic.vbroker.orb.SkeletonDelegateImpl.execute(SkeletonDelegateImpl.java:129)
at com.visigenic.vbroker.orb.GiopProtocolAdapter.doRequest(GiopProtocolAdapter.java:290)
at com.visigenic.vbroker.orb.GiopProtocolAdapter.dispatchMessage(GiopProtocolAdapter.java:462)
at com.visigenic.vbroker.orb.ThreadPoolDispatcher.run(ThreadPoolDispatcher.java:155)
at com.visigenic.vbroker.orb.WorkerThread.run(WorkerThread.java:146)
exception VdnException{long exceptionId=5;wstring reason="VNI-4009 : Cannot contact agent on the node. Agent may be down or network communication to the node has failed.";sequence data={"q1000-ora.testzaal.meursgroep.nl"};}
at oracle.sysman.vdn.VdnTargetNamingService.discover(VdnTargetNamingService.java:10917)
at oracle.sysman.vdn.VdnTargetNamingService.discover(VdnTargetNamingService.java:10737)
at oracle.sysman.vdn._tie_VdnTargetDiscovery.discover(_tie_VdnTargetDiscovery.java:148)
at oracle.sysman.vdn._VdnTargetDiscoveryImplBase._execute(_VdnTargetDiscoveryImplBase.java:162)
at oracle.sysman.vdn._VdnTargetDiscoveryImplBase._execute(_VdnTargetDiscoveryImplBase.java:145)
at com.visigenic.vbroker.orb.SkeletonDelegateImpl.execute(SkeletonDelegateImpl.java:108)
at com.visigenic.vbroker.orb.GiopProtocolAdapter.doRequest(GiopProtocolAdapter.java:290)
at com.visigenic.vbroker.orb.GiopProtocolAdapter.dispatchMessage(GiopProtocolAdapter.java:462)
at com.visigenic.vbroker.orb.ThreadPoolDispatcher.run(ThreadPoolDispatcher.java:155)
at com.visigenic.vbroker.orb.WorkerThread.run(WorkerThread.java:146)
OEMCTL for Windows NT: Version 9.2.0.1.0 Production
Copyright (c) 1998, 2002, Oracle Corporation. All rights reserved.
Starting the Oracle Management Server...VXA-3008 : Starting OMS Services, Wait.

The OMS is now started and ready.
*** VDD: INITIATING OMS SHUTDOWN : OMS REPOSITORY SESSION LOST ***
VXA: Doing a shutdown and restart
Restarting the Oracle management Server....
OEMCTL for Windows NT: Version 9.2.0.1.0 Production
Copyright (c) 1998, 2002, Oracle Corporation. All rights reserved.
Starting the Oracle Management Server...VXA-3008 : Starting OMS Services, Wait.

The OMS is now started and ready.
Restarting the Oracle management Server....
OEMCTL for Windows NT: Version 9.2.0.1.0 Production
Copyright (c) 1998, 2002, Oracle Corporation. All rights reserved.
Starting the Oracle Management Server...Restarting the Oracle management Server....
OEMCTL for Windows NT: Version 9.2.0.1.0 Production
Copyright (c) 1998, 2002, Oracle Corporation. All rights reserved.
Starting the Oracle Management Server...VXA-3008 : Starting OMS Services, Wait.

Restarting the Oracle management Server....
OEMCTL for Windows NT: Version 9.2.0.1.0 Production
Copyright (c) 1998, 2002, Oracle Corporation. All rights reserved.
Starting the Oracle Management Server...VXA-3008 : Starting OMS Services, Wait.

The OMS is now started and ready.
*** VDD: INITIATING OMS SHUTDOWN : OMS REPOSITORY SESSION LOST ***
VXA: Doing a shutdown and restart
Restarting the Oracle management Server....
OEMCTL for Windows NT: Version 9.2.0.1.0 Production
Copyright (c) 1998, 2002, Oracle Corporation. All rights reserved.
Starting the Oracle Management Server...java.lang.ExceptionInInitializerError
at
at oracle.sysman.vxa.VxaAppServer.(VxaAppServer.java:770)
at oracle.sysman.vxa.VxaAppServer.main(VxaAppServer.java:3042)
Exception in thread "main" Restarting the Oracle management Server....
OEMCTL for Windows NT: Version 9.2.0.1.0 Production
Copyright (c) 1998, 2002, Oracle Corporation. All rights reserved.
Starting the Oracle Management Server...java.lang.ExceptionInInitializerError
at
at oracle.sysman.vxa.VxaAppServer.(VxaAppServer.java:770)
at oracle.sysman.vxa.VxaAppServer.main(VxaAppServer.java:3042)
Exception in thread "main" "Management server thrashing. Exiting oemctrl.bat"
OEMCTL for Windows NT: Version 9.2.0.1.0 Production
Copyright (c) 1998, 2002, Oracle Corporation. All rights reserved.
Starting the Oracle Management Server... [main][2003-7-7:11:26:45:534] VdbSession.processError: errorCode >1033<
[main][2003-7-7:11:26:45:534] VdbSession.processError: errorMsg >ORA-01033: ORACLE initialization or shutdown in progress
<
[main][2003-7-7:11:26:45:534] VdbSession.processError: database connection error
[main][2003-7-7:11:26:55:728] VdbSession.processError: errorCode >1033<
[main][2003-7-7:11:26:55:728] VdbSession.processError: errorMsg >ORA-01033: ORACLE initialization or shutdown in progress
<
[main][2003-7-7:11:26:55:728] VdbSession.processError: database connection error
[main][2003-7-7:11:27:5:873] VdbSession.processError: errorCode >1033<
[main][2003-7-7:11:27:5:873] VdbSession.processError: errorMsg >ORA-01033: ORACLE initialization or shutdown in progress
<
[main][2003-7-7:11:27:5:873] VdbSession.processError: database connection error
[main][2003-7-7:11:27:16:178] VdbSession.processError: errorCode >1033<
[main][2003-7-7:11:27:16:178] VdbSession.processError: errorMsg >ORA-01033: ORACLE initialization or shutdown in progress
<
[main][2003-7-7:11:27:16:178] VdbSession.processError: database connection error
[main][2003-7-7:11:27:26:312] VdbSession.processError: errorCode >1033<
[main][2003-7-7:11:27:26:312] VdbSession.processError: errorMsg >ORA-01033: ORACLE initialization or shutdown in progress
<
[main][2003-7-7:11:27:26:312] VdbSessio
09-23-2003, 08:58 AM
adewri

Just Check if you OEM repository Database is up and running....
09-23-2003, 09:40 AM
GKramer

Yes it is.....OEM rep is normaly running.

GKramer
09-23-2003, 10:05 AM
adewri

Are you able to login using a sqlplus to your OEMREP DB ?? because the error message says
ORA-01033: ORACLE initialization or shutdown in progress.
09-25-2003, 02:04 AM
GKramer

Adewri,

No I can not !!for one reason or the other I can not logon to all databases on this server but I CAN connect to the databases on another server ( using sqlplus ).

I had to alter the servername ( on disk ( this computer / tab computer name / network-id etc etc.) ) recently. Can this be the problem that I can not connect to the databases on this server anymore ?? If so how to adjust the setting refering to the host name??

GKramer
09-25-2003, 03:21 AM
adewri

On the server where OEMREP resides, do the following.

on the command prompt.

set ORACLE_SID=OEMREP (or whatever is the sid for the OEM repository DB)

Code:

C:\>sqlplus "/ as sysdba" SQL*Plus: Release 9.2.0.3.0 - Production on Jue Sep 25 12:51:38 2003 Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved. Connected to: Oracle9i Enterprise Edition Release 9.2.0.3.0 - Production With the Partitioning, Oracle Label Security, OLAP and Oracle Data Mining options JServer Release 9.2.0.3.0 - Production SQL> select status from v$instance; STATUS ------------ OPEN

What is the status of the database ?

Is it mounted ? If it is then do a shutdown immediate. The do startup and see if it starts, if not then what is the error message.

Or go to ORACLE_BASE/admin/OEMREP/bdump and open the alertlog file and past the last 20 lines over here.
09-25-2003, 05:10 AM
GKramer

Adewri,

Status is OPEN.....What else can I try???

last part of the log .. see bottom.

Regards GKramer

*********************************************************************
Microsoft Windows XP [versie 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

H:\>c:

C:\>set oracle_sid=repoem

C:\>sqlplus "/ as sysdba"

SQL*Plus: Release 9.0.1.3.0 - Production on Do Sep 25 11:05:27 2003

(c) Copyright 2001 Oracle Corporation. All rights reserved.

Verbonden met:
Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.1.0 - Production

SQL> select status from v$instance;

STATUS
------------
OPEN

SQL>
*********************************************************************
Successfully onlined Undo Tablespace 1.
Tue Sep 23 09:46:40 2003
SMON: enabling tx recovery
Tue Sep 23 09:46:41 2003
Database Characterset is WE8MSWIN1252
Tue Sep 23 09:46:53 2003
replication_dependency_tracking turned off (no async multimaster replication found)
Completed: alter database open
Dump file c:\oracle\admin\repoem\bdump\alert_repoem.log
Tue Sep 23 11:23:46 2003
ORACLE V9.2.0.1.0 - Production vsnsta=0
vsnsql=12 vsnxtr=3
Windows 2000 Version 5.1 Service Pack 1, CPU type 586
Tue Sep 23 11:23:46 2003
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
SCN scheme 2
Using log_archive_dest parameter default value
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 9.2.0.1.0.
System parameters with non-default values:
processes = 150
timed_statistics = TRUE
shared_pool_size = 50331648
large_pool_size = 8388608
java_pool_size = 33554432
control_files = C:\oracle\oradata\RepOem\CONTROL01.CTL, C:\oracle\oradata\RepOem\CONTROL02.CTL, C:\oracle\oradata\RepOem\CONTROL03.CTL
db_block_size = 4096
db_cache_size = 33554432
compatible = 9.2.0.0.0
db_file_multiblock_read_count= 8
fast_start_mttr_target = 300
undo_management = AUTO
undo_tablespace = UNDOTBS1
undo_retention = 900
remote_login_passwordfile= EXCLUSIVE
db_domain =
instance_name = RepOem
dispatchers = (PROTOCOL=TCP) (SERVICE=RepOemXDB)
job_queue_processes = 10
hash_join_enabled = FALSE
background_dump_dest = C:\oracle\admin\RepOem\bdump
user_dump_dest = C:\oracle\admin\RepOem\udump
core_dump_dest = C:\oracle\admin\RepOem\cdump
sort_area_size = 524288
db_name = RepOem
open_cursors = 300
star_transformation_enabled= FALSE
query_rewrite_enabled = FALSE
pga_aggregate_target = 16777216
aq_tm_processes = 1
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
CJQ0 started with pid=8
QMN0 started with pid=9
Tue Sep 23 11:23:54 2003
starting up 1 shared server(s) ...
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
Tue Sep 23 11:23:55 2003
alter database mount exclusive
Tue Sep 23 11:24:02 2003
Successful mount of redo thread 1, with mount id 1051265931.
Tue Sep 23 11:24:02 2003
Database mounted in Exclusive Mode.
Completed: alter database mount exclusive
Tue Sep 23 11:24:03 2003
alter database open
Tue Sep 23 11:24:06 2003
Beginning crash recovery of 1 threads
Tue Sep 23 11:24:07 2003
Started first pass scan
Tue Sep 23 11:24:10 2003
Completed first pass scan
658 redo blocks read, 133 data blocks need recovery
Tue Sep 23 11:24:10 2003
Started recovery at
Thread 1: logseq 108, block 9641, scn 0.0
Recovery of Online Redo Log: Thread 1 Group 2 Seq 108 Reading mem 0
Mem# 0 errs 0: C:\ORACLE\ORADATA\REPOEM\REDO02.LOG
Tue Sep 23 11:24:12 2003
Ended recovery at
Thread 1: logseq 108, block 10299, scn 0.30495647
133 data blocks read, 133 data blocks written, 658 redo blocks read
Crash recovery completed successfully
Tue Sep 23 11:24:20 2003
Thread 1 advanced to log sequence 109
Thread 1 opened at log sequence 109
Current log# 3 seq# 109 mem# 0: C:\ORACLE\ORADATA\REPOEM\REDO03.LOG
Successful open of redo thread 1.
Tue Sep 23 11:24:21 2003
SMON: enabling cache recovery
Tue Sep 23 11:24:26 2003
Undo Segment 1 Onlined
Undo Segment 2 Onlined
Undo Segment 3 Onlined
Undo Segment 4 Onlined
Undo Segment 5 Onlined
Undo Segment 6 Onlined
Undo Segment 7 Onlined
Undo Segment 8 Onlined
Undo Segment 9 Onlined
Undo Segment 10 Onlined
Successfully onlined Undo Tablespace 1.
Tue Sep 23 11:24:26 2003
SMON: enabling tx recovery
Tue Sep 23 11:24:26 2003
Database Characterset is WE8MSWIN1252
Tue Sep 23 11:24:52 2003
replication_dependency_tracking turned off (no async multimaster replication found)
Completed: alter database open
Wed Sep 24 15:18:06 2003
Thread 1 advanced to log sequence 110
Current log# 1 seq# 110 mem# 0: C:\ORACLE\ORADATA\REPOEM\REDO01.LOG
*********************************************************************