The Oracle database fails to start

[Former Member]

Hi all

My solution manager can't properly start, after server power failure. The comand sapstart is executed without errors, but afterwards I cant log in using sapgui. I have found that instance DVEBMGS00 is not started properly(disp+work is stoped) from Sap management console . And the database is in mount state. From dev_w0 log I find

*** ERROR => CONNECT failed with SQL error '1033'
[dbsloci.c    16104]
B  ***LOG BV3=> severe db error 1033; work process is stopped [dbsh         1241]
B  ***LOG BY2=> sql error 1033   performing CON [dblink       544]
B  ***LOG BY0=> ORA-01033: ORACLE initialization or shutdown in progress [dblink       544]
M  ***LOG R19=> ThInit, db_connect ( DB-Connect 000256) [thxxhead.c   1538]
M  in_ThErrHandle: 1
M  *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c   11614]

When I have tried to change manually(using sqlplus) database state from mount to normal(open), I have got such an error:

ERROR at line 1:
ORA-00742: Log read detects lost write in thread 1 sequence 2370 block 307489
ORA-00312: online log 2 thread 1: '/oracle/DBI/mirrlogB/log_g12m2.dbf'
ORA-00312: online log 2 thread 1: '/oracle/DBI/origlogB/log_g12m1.dbf'

How can I resolve this issue?

Thank you

Best regards

Aram

[tamil_arasan]

Hi,

Could you please let us know if the previous shutdown of DB was clean ? It is trying to recover your DB in the startup phase as the previous shutdown was not clean but unfortunately it is getting crash during the processes of recovery.

Also have you tried to recover the DB manually and see? If nothing works, restore your most recent backup and apply the redo offline logs until the point of issue happened in your DB.

Caution : If it is production DB, point in time recover will lead the data loss as you are recovering the DB until the point when the DB was working fine. If the your SAP system is integrated with multiple other SAP and non SAP systems, point time recovery will lead the inconsistencies in the connected systems. I request you to refer the SAP notes 434645 - Point-in-time recovery: What must I be aware of? and 434647 - Point-in-time recovery in an SAP system group

Thanks,

Pradeep

[Former Member]

Hello Aram,

Kindly check this thread and try to recover system accordingly:

DB is not coming up | SCN

Thanks.

Best Regards,

Anita

[JamesZ]

Hi Aram,

If we check the error code ORA-00742 from oracle online doc:

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

ORA-00742: Log read detects lost write in thread number sequence number block number

Cause: Either a write issued by Oracle was lost by the underlying operating system or storage system or an Oracle internal error occurred.

Action: The trace file shows the lost write location. Dump the problematic log file to see whether it is a real lost write. Contact Oracle Support Services.

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

This looks like a serious error, please attach the alert log and the traces files mentioned in the alert log.

Best regards,
James

[Former Member]

Hello James

Thank you for response.

Here is the alert log

ALTER DATABASE OPEN
Ping without log force is disabled
.
Thu Apr 21 11:13:32 2016
Beginning crash recovery of 1 threads
parallel recovery started with 3 processes
Thu Apr 21 11:13:32 2016
Started redo scan
Thu Apr 21 11:13:32 2016
Slave encountered ORA-10388 exception during crash recovery
Thu Apr 21 11:13:32 2016
Slave encountered ORA-10388 exception during crash recovery
Thu Apr 21 11:13:32 2016
Slave encountered ORA-10388 exception during crash recovery
Thu Apr 21 11:13:32 2016
Aborting crash recovery due to error 742
Thu Apr 21 11:13:32 2016
Errors in file /oracle/DBI/saptrace/diag/rdbms/dbi/DBI/trace/DBI_ora_1851.trc:
ORA-00742: Log read detects lost write in thread 1 sequence 2370 block 307489
ORA-00312: online log 2 thread 1: '/oracle/DBI/mirrlogB/log_g12m2.dbf'
ORA-00312: online log 2 thread 1: '/oracle/DBI/origlogB/log_g12m1.dbf'
Thu Apr 21 11:13:32 2016
Errors in file /oracle/DBI/saptrace/diag/rdbms/dbi/DBI/trace/DBI_ora_1851.trc:
ORA-00742: Log read detects lost write in thread 1 sequence 2370 block 307489
ORA-00312: online log 2 thread 1: '/oracle/DBI/mirrlogB/log_g12m2.dbf'
ORA-00312: online log 2 thread 1: '/oracle/DBI/origlogB/log_g12m1.dbf'
ORA-742 signalled during: ALTER DATABASE OPEN...
Thu Apr 21 11:18:23 2016
Shutting down instance (immediate)
Shutting down instance: further logons disabled
Stopping background process MMNL
Stopping background process MMON
License high water mark = 4

The trace file is attached to this post

DBI_ora_1851.trc.zip

[JamesZ]

This is a serious error, to avoid unnecessary dummy, can you raise a ticket to SAP under component
BC-DB-ORA？