An earlier attempt at recovery marked it 'suspect' in sybase .Could not make database Online.

[Former Member]

Dear Gurus,

I need suggestion and advice on the below issue facing. I'm trying to restore the database on to the DR site manually which was taken from the HO Production server and did restored the backup successfully .While trying to load one of the transaction log it has thrown me error stating

Msg 926, Level 14, State 2:

Server 'SID', Line 1:

Database 'SID' cannot be opened. An earlier attempt at recovery marked it

'suspect'. Check the ASE errorlog for information as to the cause.

According to the log on the DR server ,it shows log

00:0003:00000:00161:2013/09/03 14:40:48.22 server  Error: 3474, Severity: 21, State: 1

00:0003:00000:00161:2013/09/03 14:40:48.22 server  During redo the page timestamp value is less than old timestamp from log. Page #=9161, object id = 254893940, page timestamp=0000 6032e345. Log old timestamp=0000 663bd9d5. Log record marker = (20026859, 62).

But its strange that i have not missed any transaction log sequence .Now im not able to make the database online also with the previous transaction and back restored .According to the information it states could be the database or transaction logs could be corrupted but if i try to restore the other backup file it gives me same error

Msg 926, Level 14, State 2:

Server 'SID', Line 1:

Database 'SID' cannot be opened. An earlier attempt at recovery marked it

'suspect'

Please suggest me to proceed further.

[former_member188958]

Hi Asim,

The 3474 is the error to focus on.

What version of ASE are you running? (select @@version)

Are you running ASE on a virtual machine?

There are several recent CRs involving 3474 errors:

CR 741898, fixed in 15.7 SP 101 and SP 110 and higher.

CR 736888, fixed in 15.7 SP 100.

I recommend opening a case/message with tech support; the log records will likely need to be analyzed to figure out just what caused the error.

-bret

[Former Member]

Dear Bret,

Ase Version :15.7.0.042 and its a physical machine.And its true the error is 3474 and according to analysis its showing "  During redo the page timestamp value is less than old timestamp from log".

Is it safe way to reset suspect status .

[former_member188958]

There is a safe way to reset the suspect status.  However, it won't help in this case because it doesn't bypass the error.  After the suspect status is reset, the database will go through recovery and presumably will encounter the same 3474 error and be marked suspect again.  Resetting the suspect status is useful in cases where the recovery error won't happen again, the most common example being that one or more disk devices being unavailable when ASE was booted (NFS system not mounted, raw partition not yet powered up) but are now available.

The basic process:

sp_configure "allow updates", 1

go

use master

go

update sysdatabases

set status = status ^ 256

where status & 256 = 256

and name = <dbname>

go

sp_configure "allow updates", 0

go

-- now reboot server / database

-bret