Skip to Content
0

dump database cumulative then dump trans database with no_truncate give me load error Msg 4334

Aug 22, 2017 at 02:43 AM

47

avatar image
Former Member
Did the following backup and load operations before getting MSG 4334 
What did I do wrong? Thank you very much! 

Dump 
dump database pub6 full to '/tmp/pub6_f.dmp'   
some insert 
dump tran pub6 to '/tmp/pub6_t1.lmp'
some insert 
dump database pub6 cumulative to '/tmp/pub_c.dmp'
some insert 
dump tran pub6 to '/tmp/pub6_t2.lmp'
some insert 
dump tran pub6 to '/tmp/pub6_t3.lmp' with no_truncate

Load 
LOAD DATABASE pub6 FROM '/tmp/pub6_f.dmp'
LOAD DATABASE pub6 CUMULATIVE FROM '/tmp/pub_c.dmp'
LOAD TRAN pub6 FROM '/tmp/pub6_t2.lmp'
LOAD TRAN pub6 FROM '/tmp/pub6_t3.lmp'


Generate error like the following.  
Backup Server session id is: 142. Use this value when executing the 'sp_volchanged' system stored procedure after fulfilling any volume change request from the Backup Server.
Backup Server: 6.28.1.1: Dumpfile name 'pub617228123F3   ' section number 1 mounted on disk file '/tmp/pub6_t3.lmp'
Msg 4334, Level 16, State 1:
Server 'SYBASE1', Line 1:
Specified file is out of sequence. The timestamp in this dump '0000 00000000' is smaller than or equal to the database cumulative dump timestamp '0000 00004a64'.







## Load testing Details


1> sp_dboption pub6, "allow incremental dumps" , true
2> go
Database option 'allow incremental dumps' turned ON for database 'pub6'.
Running CHECKPOINT on database 'pub6' for option 'allow incremental dumps' to take effect.
(return status = 0)

1> truncate table moveseg1 
2> go
1> insert into pub6..moveseg1 values ( 1,'1000')
2> go
(1 row affected)
1> insert into pub6..moveseg1 values ( 1,'1000')
2> go 999
(1 row affected)
999 xacts:
1> select count(*) from moveseg1 
2> go
             
 ----------- 
        1000 


(1 row affected)
1> dump database pub6 full to '/tmp/pub6_f.dmp'   
2> go
Backup Server: 4.172.1.4: The value of 'allocated pages threshold' has been set to 40%.
Backup Server session id is: 118. Use this value when executing the 'sp_volchanged' system stored procedure after fulfilling any volume change request from the Backup Server.
Backup Server: 4.41.1.1: Creating new disk file /tmp/pub6_f.dmp.
Backup Server: 6.28.1.1: Dumpfile name 'pub61722812342   ' section number 1 mounted on disk file '/tmp/pub6_f.dmp'
Backup Server: 4.188.1.1: Database pub6: 884 kilobytes (4%) DUMPED.
Backup Server: 4.188.1.1: Database pub6: 1054 kilobytes (43%) DUMPED.
Backup Server: 4.188.1.1: Database pub6: 1728 kilobytes (80%) DUMPED.
Backup Server: 4.188.1.1: Database pub6: 1818 kilobytes (100%) DUMPED.
Backup Server: 3.43.1.1: Dump phase number 1 completed.
Backup Server: 4.188.1.1: Database pub6: 1852 kilobytes (100%) DUMPED.
Backup Server: 3.43.1.1: Dump phase number 2 completed.
Backup Server: 3.43.1.1: Dump phase number 3 completed.
Backup Server: 4.188.1.1: Database pub6: 1862 kilobytes (100%) DUMPED.
Backup Server: 3.42.1.1: DUMP is complete (database pub6).
1>  insert into pub6..moveseg1 values ( 1,'2000')
2> go 1000
go(1 row affected)
1000 xacts:
1  
2> 
3> dump tran pub6 to '/tmp/pub6_t1.lmp'
4> go
Backup Server session id is: 121. Use this value when executing the 'sp_volchanged' system stored procedure after fulfilling any volume change request from the Backup Server.
Backup Server: 4.41.1.1: Creating new disk file /tmp/pub6_t1.lmp.
Backup Server: 6.28.1.1: Dumpfile name 'pub61722812372   ' section number 1 mounted on disk file '/tmp/pub6_t1.lmp'
Backup Server: 4.58.1.1: Database pub6: 376 kilobytes DUMPED.
Backup Server: 4.58.1.1: Database pub6: 380 kilobytes DUMPED.
Backup Server: 3.43.1.1: Dump phase number 3 completed.
Backup Server: 4.58.1.1: Database pub6: 384 kilobytes DUMPED.
Backup Server: 3.42.1.1: DUMP is complete (database pub6).
1> insert into pub6..moveseg1 values ( 1,'3000')
2> go 1000
(1 row affected)
1000 xacts:
1> dump database pub6 cumulative to '/tmp/pub_c.dmp'
2> go 
Backup Server: 4.172.1.4: The value of 'allocated pages threshold' has been set to 40%.
Backup Server session id is: 123. Use this value when executing the 'sp_volchanged' system stored procedure after fulfilling any volume change request from the Backup Server.
Backup Server: 4.41.1.1: Creating new disk file /tmp/pub_c.dmp.
Backup Server: 6.28.1.1: Dumpfile name 'pub61722812389   ' section number 1 mounted on disk file '/tmp/pub_c.dmp'
Backup Server: 4.188.1.1: Database pub6: 918 kilobytes (4%) DUMPED.
Backup Server: 4.188.1.1: Database pub6: 1122 kilobytes (5%) DUMPED.
Backup Server: 3.43.1.1: Dump phase number 1 completed.
Backup Server: 4.188.1.1: Database pub6: 1156 kilobytes (5%) DUMPED.
Backup Server: 4.188.1.1: Database pub6: 1174 kilobytes (5%) DUMPED.
Backup Server: 3.43.1.1: Dump phase number 2 completed.
Backup Server: 3.43.1.1: Dump phase number 3 completed.
Backup Server: 4.188.1.1: Database pub6: 1184 kilobytes (5%) DUMPED.
Backup Server: 3.42.1.1: DUMP is complete (database pub6).
1> insert into pub6..moveseg1 values ( 1,'4000')
2> go 1000
(1 row affected)
1000 xacts:
1> select count(*) from moveseg1
2> go
             
 ----------- 
        4000 


(1 row affected)
1> dump tran pub6 to '/tmp/pub6_t2.lmp'
2> go 
Backup Server session id is: 126. Use this value when executing the 'sp_volchanged' system stored procedure after fulfilling any volume change request from the Backup Server.
Backup Server: 4.41.1.1: Creating new disk file /tmp/pub6_t2.lmp.
Backup Server: 6.28.1.1: Dumpfile name 'pub617228123C7   ' section number 1 mounted on disk file '/tmp/pub6_t2.lmp'
Backup Server: 4.58.1.1: Database pub6: 374 kilobytes DUMPED.
Backup Server: 4.58.1.1: Database pub6: 378 kilobytes DUMPED.
Backup Server: 3.43.1.1: Dump phase number 3 completed.
Backup Server: 4.58.1.1: Database pub6: 382 kilobytes DUMPED.
Backup Server: 3.42.1.1: DUMP is complete (database pub6).
1> insert into pub6..moveseg1 values ( 1,'5000')
2> go 1000
(1 row affected)
1000 xacts:
1> select count(*) from moveseg1
2> go
             
 ----------- 
        5000 


(1 row affected)
1> commit 
2> go
1> dump tran pub6 to '/tmp/pub6_t3.lmp' with no_truncate
2> go
Backup Server session id is: 128. Use this value when executing the 'sp_volchanged' system stored procedure after fulfilling any volume change request from the Backup Server.
Backup Server: 4.41.1.1: Creating new disk file /tmp/pub6_t3.lmp.
Backup Server: 6.28.1.1: Dumpfile name 'pub617228123F3   ' section number 1 mounted on disk file '/tmp/pub6_t3.lmp'
Backup Server: 4.58.1.1: Database pub6: 190 kilobytes DUMPED.
Backup Server: 3.43.1.1: Dump phase number 3 completed.
Backup Server: 4.58.1.1: Database pub6: 194 kilobytes DUMPED.
Backup Server: 3.42.1.1: DUMP is complete (database pub6).
1> select count(*) from moveseg1
2> go
             
 ----------- 
        5000 


(1 row affected)




1> load database pub6 with listonly=load_sql
2> go
LOAD DATABASE pub6 FROM '/tmp/pub6_f.dmp'
go
LOAD DATABASE pub6 CUMULATIVE FROM '/tmp/pub_c.dmp'
go
LOAD TRAN pub6 FROM '/tmp/pub6_t2.lmp'
go
LOAD TRAN pub6 FROM '/tmp/pub6_t3.lmp'
go




1> use master
2> go
1> LOAD DATABASE pub6 FROM '/tmp/pub6_f.dmp'
go2> 
Backup Server session id is: 133. Use this value when executing the 'sp_volchanged' system stored procedure after fulfilling any volume change request from the Backup Server.
Backup Server: 6.28.1.1: Dumpfile name 'pub61722812342   ' section number 1 mounted on disk file '/tmp/pub6_f.dmp'
Backup Server: 4.188.1.1: Database pub6: 3588 kilobytes (3%) LOADED.
Backup Server: 4.188.1.1: Database pub6: 46598 kilobytes (42%) LOADED.
Backup Server: 4.188.1.1: Database pub6: 88072 kilobytes (79%) LOADED.
Backup Server: 4.188.1.1: Database pub6: 110602 kilobytes (100%) LOADED.
Backup Server: 4.188.1.1: Database pub6: 110646 kilobytes (100%) LOADED.
Backup Server: 3.42.1.1: LOAD is complete (database pub6).
Caution:  You have set up this database to include space on disk 7 for both data and the transaction log.  This can make recovery impossible if that disk fails.
Started estimating recovery log boundaries for database 'pub6'.
Database 'pub6', checkpoint=(15744, 19), first=(15744, 19), last=(15745, 5).
Completed estimating recovery log boundaries for database 'pub6'.
Started ANALYSIS pass for database 'pub6'.
Completed ANALYSIS pass for database 'pub6'.
Started REDO pass for database 'pub6'. The total number of log records to process is 12.
Redo pass of recovery has processed 2 committed and 0 aborted transactions.
Completed REDO pass for database 'pub6'.
Use the ONLINE DATABASE command to bring this database online; ASE will not bring it online automatically.
1> LOAD DATABASE pub6 CUMULATIVE FROM '/tmp/pub_c.dmp'
go2> 
Backup Server session id is: 136. Use this value when executing the 'sp_volchanged' system stored procedure after fulfilling any volume change request from the Backup Server.
Backup Server: 6.28.1.1: Dumpfile name 'pub61722812389   ' section number 1 mounted on disk file '/tmp/pub_c.dmp'
Backup Server: 4.188.1.1: Database pub6: 3588 kilobytes (3%) LOADED.
Backup Server: 4.188.1.1: Database pub6: 5126 kilobytes (4%) LOADED.
Backup Server: 4.188.1.1: Database pub6: 5188 kilobytes (100%) LOADED.
Backup Server: 3.42.1.1: LOAD is complete (database pub6).
Caution:  You have set up this database to include space on disk 7 for both data and the transaction log.  This can make recovery impossible if that disk fails.
Started estimating recovery log boundaries for database 'pub6'.
Database 'pub6', checkpoint=(15930, 25), first=(15930, 25), last=(15931, 3).
Completed estimating recovery log boundaries for database 'pub6'.
Started ANALYSIS pass for database 'pub6'.
Completed ANALYSIS pass for database 'pub6'.
Started REDO pass for database 'pub6'. The total number of log records to process is 7.
Redo pass of recovery has processed 1 committed and 0 aborted transactions.
Completed REDO pass for database 'pub6'.
Use the ONLINE DATABASE command to bring this database online; ASE will not bring it online automatically.
1> LOAD TRAN pub6 FROM '/tmp/pub6_t2.lmp'
go2> 
Backup Server session id is: 139. Use this value when executing the 'sp_volchanged' system stored procedure after fulfilling any volume change request from the Backup Server.
Backup Server: 6.28.1.1: Dumpfile name 'pub617228123C7   ' section number 1 mounted on disk file '/tmp/pub6_t2.lmp'
Backup Server: 4.58.1.1: Database pub6: 382 kilobytes LOADED.
Backup Server: 3.42.1.1: LOAD is complete (database pub6).
Started estimating recovery log boundaries for database 'pub6'.
Database 'pub6', checkpoint=(15930, 25), first=(15930, 25), last=(16023, 5).
Completed estimating recovery log boundaries for database 'pub6'.
Started ANALYSIS pass for database 'pub6'.
Completed ANALYSIS pass for database 'pub6'.
Started full REDO pass for database 'pub6'. The total number of log records to process is 3025.
Redo pass of recovery has processed 1002 committed and 0 aborted transactions.
Completed REDO pass for database 'pub6'.
Use the ONLINE DATABASE command to bring this database online; ASE will not bring it online automatically.
1> LOAD TRAN pub6 FROM '/tmp/pub6_t3.lmp'
go2> 
Backup Server session id is: 142. Use this value when executing the 'sp_volchanged' system stored procedure after fulfilling any volume change request from the Backup Server.
Backup Server: 6.28.1.1: Dumpfile name 'pub617228123F3   ' section number 1 mounted on disk file '/tmp/pub6_t3.lmp'
Msg 4334, Level 16, State 1:
Server 'SYBASE1', Line 1:
Specified file is out of sequence. The timestamp in this dump '0000 00000000' is smaller than or equal to the database cumulative dump timestamp '0000 00004a64'.
1> 
10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Maria Victoria NORMAND
Dec 13, 2017 at 04:50 PM
0

Hi Jin,

You have posted this question since some time ago, but it was not on the correct primary tag, as per the sample script provided I would say you are not running ASE for SAP Bussines Suite. I moved it to SAP Adaptive Server Enterprise.

The error you are reporting here is actually a known issue when using the "with no_truncate" during cumulative dumps and after a dump database is done. You may refer to KBA 2269063 - Error 4334: Specified file is out of sequence - after cumulative dump and tran dump with no_truncate - SAP ASE
Best regards,
Victoria.

Share
10 |10000 characters needed characters left characters exceeded