load transaction时的问题

[genius_ly]

用load transaction时，报如下错误：

Backup Server session id is: 44. 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 'test070930C1B8 ' section number 1
mounted on disk file 'd:\dump_log.dmp'
Msg 4305, Level 16, State 1:
Line 1:
Specified file 'dump device' is out of sequence. Current time stamp is Apr 3
2007 1:46PM while dump was from Apr 3 2007 1:46PM.

请问是什么问题，该如何解决？

[zjntche_cn]

请确保你的磁盘空间或者数据库设备空间足够大！

[genius_ly]

磁盘空间和数据库设备空间都是足够大的

[zjntche_cn]

这里有一段关于这个错误的描述：
Error 4305
Severity

16

Error message text
Specified file '%.*s' is out of sequence. Current time stamp is %S_DATE while dump was from %S_DATE.

Explanation
During a load transaction, Adaptive Server checks the timestamp on the dumped database and each dumped transaction log to determine whether the sequence is correct. If the load sequence of the transaction logs is incorrect, Error 4305 occurs and the load fails.

If you are missing a transaction log dump, you can only restore up to the transaction log dump before the missing dump.

In addition, you cannot load multiple transaction log dumps that have been created with the no_truncate option. The no_truncate option assumes that nothing further will be done with the transaction log after that point: it is only useful for up-to-the-minute recovery of a database after failure of the data device. If you have used the no_truncate option and your database is still okay, do a dump database as soon as possible.

This error is serious as the load processing stops and the load transaction fails.

Action
Load the log backups in the same sequence in which they were made. Check your transaction log dumps to determine whether one was loaded out of order. If you find the correct dump, load it and continue with the rest of the dumps, in order.

Additional information
For more information, refer to "load transaction" in the Reference Manual.

Versions in which this error is raised
All versions

我想是增量备份恢复顺序的问题！