Re: again: oracle instance is not running

This is a bit of a guess, because I have never seen this *exact* problem before, but it looks like someone moved the online redo logs before you did the startup. In any case, it looks like the instance is finding the wrong logs to do instance recovery. If you really can't find the right logs, get into server manager and alter the database open with the 'resetlogs' option. If you shut down clean, this should be okay. You will have to do an immediate backup to protect yourself, but the instance should come up. First, bring it up in mount state, then do the "alter database open resetlogs" command.

Before you do any of this, however, figure out what happened to the online logs. Weird.

Roger Snowden
Sr. Systems Engineering Specialist
Oracle Corporation
rsnowden_at_NOTus.oracle.com <-- to reply, remove the obvious

Ruediger Tams wrote:
>
> Hi!
> Here is mor information about my problem from orclALRT.LOG.
> Somebody knows a solution for this problem?
>
> Thanx to: Sybrand Bakker from Netherlands
>
> kindly regards
> Ruediger Tams
> KomTel GmbH
> Flensburg, Germany
>
> #
> Dump file E:\ORANT\RDBMS73\trace\orclALRT.LOG
> Mon Jan 11 09:44:07 1999
> ORACLE V7.3.4.0.0 - Production vsnsta=0
> vsnsql=b vsnxtr=3
> Windows NT V4.0, OS V5.101, CPU type 586
> Starting up ORACLE RDBMS Version: 7.3.4.0.0.
> System parameters with non-default values:
> processes = 50
> shared_pool_size = 6500000
> control_files = E:\ORANT\DATABASE\ctl1orcl.ora,
> E:\ORANT\DATABASE\ctl2orcl.ora
> compatible = 7.3.0.0.0
> log_buffer = 8192
> log_checkpoint_interval = 10000
> db_files = 20
> sequence_cache_hash_buckets= 10
> remote_login_passwordfile= SHARED
> mts_servers = 0
> mts_max_servers = 0
> mts_max_dispatchers = 0
> audit_trail = NONE
> sort_area_retained_size = 65536
> sort_direct_writes = AUTO
> db_name = oracle
> text_enable = TRUE
> snapshot_refresh_processes= 1
> background_dump_dest = %RDBMS73%\trace
> user_dump_dest = %RDBMS73%\trace
> max_dump_file_size = 10240
>
> Mon Jan 11 09:44:07 1999
>
> PMON started
> Mon Jan 11 09:44:07 1999
>
> DBWR started
> Mon Jan 11 09:44:07 1999
>
> LGWR started
> Mon Jan 11 09:44:07 1999
>
> RECO started
> Mon Jan 11 09:44:07 1999
>
> SNP0 started
> Mon Jan 11 09:44:08 1999
> alter database "oracle" mount exclusive
> Mon Jan 11 09:44:08 1999
> Successful mount of redo thread 1.
> Mon Jan 11 09:44:08 1999
> Completed: alter database "oracle" mount exclusive
> Mon Jan 11 09:44:08 1999
> alter database "oracle" open
> Mon Jan 11 09:44:09 1999
> Errors in file E:\ORANT\RDBMS73\trace\orclLGWR.TRC:
> ORA-00314: log 1 of thread 1, expected sequence# 2024 doesn't match 2026
>
> ORA-00312: online log 1 thread 1: 'E:\ORANT\DATABASE\LOG2ORCL.ORA'
> ORA-00314: log 1 of thread 1, expected sequence# 2024 doesn't match 2026
>
> ORA-00312: online log 1 thread 1: 'E:\ORANT\DATABASE\LOG1ORCL.ORA'
>
> Mon Jan 11 09:44:09 1999
> Errors in file E:\ORANT\RDBMS73\trace\orclLGWR.TRC:
> ORA-00314: log 1 of thread 1, expected sequence# 2024 doesn't match 2026
>
> ORA-00312: online log 1 thread 1: 'E:\ORANT\DATABASE\LOG2ORCL.ORA'
> ORA-00314: log 1 of thread 1, expected sequence# 2024 doesn't match 2026
>
> ORA-00312: online log 1 thread 1: 'E:\ORANT\DATABASE\LOG1ORCL.ORA'
>
> ORA-314 signalled during: alter database "oracle" open...
>
> #
> #OLD posting:
>
> Hello!
>
> I have some trouble with our Oracle Workgroup-Server 7.3.4
> on NT4 Server SP3.
>
> We changed our domain an the IP-Adress for our Oracle-Server.
>
> Now Oracle NT Instance Manager shows
> #
> SID Status Startup
> ORCL
> Services Started Automatic
> Instance Stopped Automatic
> #
>
> But Win NT Services shows
>
> OracleServiceORCL Started
> OracleStartORCL Started
>
> In Eventviewer the last correct detail says
> 'Initializing PGA for process SNP0 in instance orcl.'
>
> After this i have the following eventdetail:
> The description of the event ID (0) in source (ORACLE7.orcl)
> could not be found. It contains the following insert character
> string (n): ACTION : 'shutdown'.
>
> Then there are this 3 events:
> Shutdown normal performed on instance orcl.
> All process in instance orcl stopped.
> Instance orcl has been terminated.
>
> Now Oracle isn't availabe an more :-( (ORA-01034)
> So where is the problem?
>
> kindly regards
>
> Ruediger Tams
> KomTel GmbH
> Flensburg, Germany
Received on Mon Jan 11 1999 - 22:42:07 CST