cancel
Showing results for 
Search instead for 
Did you mean: 

Can't restore ASE log

Former Member
0 Kudos

I have ASE backup every day and log backup every hour. then I get the backup file like:

....

-rw-r--r--  1 sybase sybase 5332286485 Apr 12 20:31 mydb.dmp

-rw-r--r--  1 sybase sybase      18048 Apr 12 21:01 my_log_20140412_02.dmp

-rw-r--r--  1 sybase sybase     229836 Apr 12 22:01 my_log_20140412_03.dmp

-rw-r--r--  1 sybase sybase     173399 Apr 12 23:01 my_log_20140412_04.dmp

-rw-r--r--  1 sybase sybase     408999 Apr 13 00:01 my_log_20140412_05.dmp

.....

then I try to restore it on another box. firstly, restore mydb.dmp and it is fine with message:

Backup Server: 3.42.1.1: LOAD is complete (database mydb).

Caution:  You have set up this database to include space on disk 19 for both

data and the transaction log.  This can make recovery impossible if that disk

fails.

Caution:  You have set up this database to include space on disk 20 for both

data and the transaction log.  This can make recovery impossible if that disk

fails.

Started estimating recovery log boundaries for database 'mydb'.

Database 'mydb', checkpoint=(11742880, 11), first=(115975859872, 11),

last=(11742913, 5).

Completed estimating recovery log boundaries for database 'mydb'.

Started ANALYSIS pass for database 'mydb'.

Completed ANALYSIS pass for database 'mydb'.

Started REDO pass for database 'mydb'. The total number of log records to

process is 471.

Redo pass of recovery has processed 30 committed and 5 aborted transactions.

Completed REDO pass for database 'mydb'.

Use the ONLINE DATABASE command to bring this database online; SQL Server will

not bring it online automatically.

then I try to restore next log backup my_log_20140412_02.dmp and got message:

Backup Server session id is:  23.  Use this value when executing the

'sp_volchanged' system stored procedure after fulfilling any volume change

request from the Backup Server.

Backup Server: 4.132.1.1: Attempting to open byte stream device:

'compress::1::/home/mydump/my_log_20140412_02.dmp::00'

Backup Server: 6.28.1.1: Dumpfile name 'mydb14102135A2' section number 1

mounted on byte stream

'compress::1::/home/mydump/my_log_20140412_02.dmp::00'

Msg 4305, Level 16, State 1:

Server 'MYSYB', Line 1:

Specified file 'dump device' is out of sequence. Current time stamp is Apr 12

2014  6:01:01:433PM while dump was from Apr 12 2014  9:19:54:890PM.

Not sure why. It said out of sequence. but  the backup sequence is right. after mydb.dmp, the next backup is my_log_20140412_02.dmp. why have this error? how to resolve it?

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Find out: need to restore a log which is dumped before mydb.dmp. Not sure why.

madhvi_pai
Participant
0 Kudos

Hi Kent,

Yes, a 6pm dump seems to have been loaded in-between - are there automated dump/load processes running alongside? Or just the manual ones you describe? Please see if loading a subsequent full db dump helps clear the issue -- or if there is a recurring load which is causing the out-of-sequence problem.

Thanks,

Madhvi Pai

SAP AGS

Former Member
0 Kudos

Hi Kent,

Please run:

load transaction DB from '/dmpfile' with headeronly

The command will print the timeframes of all the transaction log files.

You should see a message like:

sequence dates: (old=Apr 16 2014  7:25:35:340PM, new=Apr 16 2014  7:26:23:373PM); truncation page=524527; 7 pages deallocated; requires database with 575488 pages.

You can check if you have a full history, or like Madhvi has written - someone else has run dump tran between your dumps and broken the transaction log sequence.

Also you can check the backup server log if there have been other dump tran commands run that you are not aware of.

HTH,

Adam

Answers (0)