Is there a way to reset USED LOG PAGE?

[Former Member]

Hi Guys

Im running SapDB/MAXDB 7.8.0.2.21

We had a power outage on our standy server and it appears to have lost the position of wher it last retored its logs, so it refuses to continue to allow me to restore logs

Used LOG Page 394

First LOG Page 2147483647

Restartable 1

Id Restart Record sunflower.pha.co.za:P01_20110617_092956

Id LOG Info

Consistent 1

Log Volume Enabled 1

Log Auto Overwrite 0

Master Servernode

Converter Version 7

Oldest Compatible Version 7.8.02.21

Queue Count 1

Repository Imports NO

The used log page is supposed to be a much larger value 36441923 which is compatible with the last log file it(LOG53722) restored

When i do a check of the last log file restore to this standy server this is what i get

backup_history_list -c label,action,stamp1,stamp2,start,stop,firstlog,lastlog -Inverted

CONTINUE

HISTLOST

2011-06-16 07:32:07

2011-06-16 07:32:07

LOG_000053722|RESTORE |2011-06-14 15:57:48|2011-06-14 22:17:10|2011-06-15 10:09:20|2011-06-15 10:09:24| 36441606| 36441923|

LOG_000053721|RESTORE |2011-06-14 15:42:24|2011-06-14 15:57:48|2011-06-15 10:08:20|2011-06-15 10:09:20| 36440924| 36441605|

Is there a way for me to set the logs to continue restoring to this database. or do i have to restore the database entirely and restart the logs from scratch, I hope not as this is quite tedious as the Database is Huge.

Please assist

Thanks

Stuart

[former_member229109]

Hello Stuart,

as you know, there is documentation at

http://maxdb.sap.com/doc/7_8/44/d7b0ca22873ee1e10000000a114a6b/content.htm

1. Did you run "db_activate" in the standby instance after the power outage ?

It will be helpful to review the dbm.prt and dbm.knl files.

Are you SAP customer?

2. Please post the ouput of the dbm command, standby instance:

db_restartinfo

Post all entries in the dbm.prt started from 2011-06-16 01:00:00

Thank you and best regards, Natalia Khlopina

[Former Member]

Hi There. Thanks for taking the time to answer my question

I could not seem to find much info in there about resetting the log position, am i missing it?

We have been using SapDB/MAXdb since 2002

db_Restartinfo

Used LOG Page 394

First LOG Page 2147483647

Restartable 1

Id Restart Record sunflower.pha.co.za:P01_20110617_092956

Id LOG Info

Consistent 1

Log Volume Enabled 1

Log Auto Overwrite 0

Master Servernode

Converter Version 7

Oldest Compatible Version 7.8.02.21

Queue Count 1

Repository Imports NO

I did run db_activate afterwads and it seemed to reset the used logs to a value of 0????

Please assist

[former_member229109]

Hello Stuart,

1. I recommend to reset the standbay database instance using latest successful databackup of the source database instance.

See document for steps:

http://maxdb.sap.com/doc/7_7/44/e9bd51d0112952e10000000a11466f/content.htm

< "Setting Up and Updating Standby Instances" >

2. Did you run "db_activate" in the standby instance after the power outage ?

I asked you if you run it already & what databackup you restored after HISTORY lost on 2011-06-16.

According the "db_Restartinfo" the database was restartable.

< reference: http://maxdb.sap.com/doc/7_7/44/fc2a1fed0641dee10000000a1553f6/content.htm >

Used LOG Page:

Next log page to be used by the system after Restart

You have : Used LOG Page 394

Id Restart Record:

Database ID of the data area of the database instance (stored in the restart information)

You have: Id Restart Record sunflower.pha.co.za:P01_20110617_092956

Is your source database P01 running on sunflower.pha.co.za server?

At that point you could restart the restore of the logbackups of database P01 running on sunflower.pha.co.za server,

which have the LOG Page 394, check interval First LOG Page to Last LOG Page in backup histopy of database P01 running on sunflower.pha.co.za server.

=> Post all entries in the dbm.prt started from 2011-06-16 01:00:00

It will be helpful to check the dbm.knl of the source and standby database.

Are you SAP customer?

Thank you and best regards, Natalia Khlopina

[Former Member]

Thanks. Sorted. I restored a more recent version and the logs restored