-
Oracle 10.2.0.1.0 Wont Start
I have a server running Oracle 10.2.0.1.0 and ArcSDE 9.1 on SLES 9
Over the weekend the ArcSDE service stopped responding and this morning i rebooted the server.
Trying to manually start the database this morning i got the following error(s):
SQL> connect / as sysdba
Connected to an idle instance.
SQL> startup
ORA-01081: cannot start already-running ORACLE - shut it down first
SQL> shutdown
ORA-24324: service handle not initialized
ORA-24323: value not allowed
ORA-01092: ORACLE instance terminated. Disconnection forced
SQL> startup
ORA-01031: insufficient privileges
SQL>
I am not an Oracle expert (obviously?). Any suggestions would be appreciated.
-
try to start database with pfile option
startup pfile=''
-
SQL> startup
ORA-01081: cannot start already-running ORACLE - shut it down first
Why oracle is saying the database is running? If it is running, why you wanna shutdown and startup again? What are the error messages in alert log with startup?
-
Before starting the database, make sure you have env. variable ORACLE_SID set to right value. It looks like the database is on Windows server, Right? If so, start the Oracle service for the database.
-
Thomasps:
Sorry, i didn't clarify initially. I was getting the error that the database was already started yet the Oracle Enterprise Manager web based console reported the database as being down.
I have since managed to shutdown the database using the "shutdown abort" command. Typing "startup" seems to start the database successfully now:
SQL> startup
ORACLE instance started.
Total System Global Area 608174080 bytes
Fixed Size 1220820 bytes
Variable Size 125833004 bytes
Database Buffers 473956352 bytes
Redo Buffers 7163904 bytes
Database mounted.
Database opened.
Yet now the Oracle Enterprise Manager hangs when trying to connect. It seems the database is not accepting connections? Is it possible that it is doing some sort of recovery? If so, how do i check the progress?
This is the tail of my alert log:
starting up 1 shared server(s) ...
Tue Jul 18 09:48:30 2006
ALTER DATABASE MOUNT
Tue Jul 18 09:48:34 2006
Setting recovery target incarnation to 2
Tue Jul 18 09:48:34 2006
Successful mount of redo thread 1, with mount id 571234606
Tue Jul 18 09:48:34 2006
Database mounted in Exclusive Mode
Completed: ALTER DATABASE MOUNT
Tue Jul 18 09:48:34 2006
ALTER DATABASE OPEN
Tue Jul 18 09:48:34 2006
Beginning crash recovery of 1 threads
parallel recovery started with 3 processes
Tue Jul 18 09:48:34 2006
Started redo scan
Tue Jul 18 09:48:34 2006
Completed redo scan
623 redo blocks read, 44 data blocks need recovery
Tue Jul 18 09:48:34 2006
Started redo application at
Thread 1: logseq 9813, block 1789
Tue Jul 18 09:48:34 2006
Recovery of Online Redo Log: Thread 1 Group 2 Seq 9813 Reading mem 0
Mem# 0 errs 0: /database/geodata/oracle/oradata/geodata/redo02.log
Tue Jul 18 09:48:34 2006
Completed redo application
Tue Jul 18 09:48:34 2006
Completed crash recovery at
Thread 1: logseq 9813, block 2412, scn 50786094
44 data blocks read, 44 data blocks written, 623 redo blocks read
Tue Jul 18 09:48:34 2006
Thread 1 advanced to log sequence 9814
Thread 1 opened at log sequence 9814
Current log# 3 seq# 9814 mem# 0: /database/geodata/oracle/oradata/geodata/redo03.log
Successful open of redo thread 1
Tue Jul 18 09:48:34 2006
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Tue Jul 18 09:48:34 2006
SMON: enabling cache recovery
Tue Jul 18 09:48:35 2006
Successfully onlined Undo Tablespace 1.
Tue Jul 18 09:48:35 2006
SMON: enabling tx recovery
Tue Jul 18 09:48:35 2006
Database Characterset is WE8ISO8859P1
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=19, OS id=28452
Tue Jul 18 09:48:36 2006
db_recovery_file_dest_size of 2048 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Tue Jul 18 09:48:36 2006
Completed: ALTER DATABASE OPEN
oracledata@geoserv:/database/geodata/oracle/product/10gR2/dbs> vi /database/geodata/oracle/admin/geodata/bdump/alert_geodata.log
623 redo blocks read, 44 data blocks need recovery
Tue Jul 18 09:48:34 2006
Started redo application at
Thread 1: logseq 9813, block 1789
Tue Jul 18 09:48:34 2006
Recovery of Online Redo Log: Thread 1 Group 2 Seq 9813 Reading mem 0
Mem# 0 errs 0: /database/geodata/oracle/oradata/geodata/redo02.log
Tue Jul 18 09:48:34 2006
Completed redo application
Tue Jul 18 09:48:34 2006
Completed crash recovery at
Thread 1: logseq 9813, block 2412, scn 50786094
44 data blocks read, 44 data blocks written, 623 redo blocks read
Tue Jul 18 09:48:34 2006
Thread 1 advanced to log sequence 9814
Thread 1 opened at log sequence 9814
Current log# 3 seq# 9814 mem# 0: /database/geodata/oracle/oradata/geodata/redo03.log
Successful open of redo thread 1
Tue Jul 18 09:48:34 2006
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Tue Jul 18 09:48:34 2006
SMON: enabling cache recovery
Tue Jul 18 09:48:35 2006
Successfully onlined Undo Tablespace 1.
Tue Jul 18 09:48:35 2006
SMON: enabling tx recovery
Tue Jul 18 09:48:35 2006
Database Characterset is WE8ISO8859P1
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=19, OS id=28452
Tue Jul 18 09:48:36 2006
db_recovery_file_dest_size of 2048 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Tue Jul 18 09:48:36 2006
Completed: ALTER DATABASE OPEN
-
Your database looks OK and opened normally. Check the listerenr, is started or not. Also, check the web services. Login to the databases using sqlplus to check the connections are going thru or not. It looks the EM problem is out of Database. Sorry, I never use EM rather I work with sqlplus.
-
(I know I'm repeating what Thomasps said in his post, but...)
Yet now the Oracle Enterprise Manager hangs when trying to connect. It seems the database is not accepting connections?
This is rather a "broad brush" statement to make. Check that the database will accept connections by trying to log in using SQL Plus. If you can then the problem is with EM, in which case stop & restart the EM service.
Only if you can't log in using SQL Plus can you say that the database is not accepting connections, in which case a reboot of the server may help to put things right.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|