Symptom
- Load from a source database where the sysusages has a hole, sometimes hangs on the target when trying to online the database. For example:
- On the target:
- The dump was taken at a quiet time - there were no processes running and the log had been truncated.
- The online process shows:
Started estimating recovery log boundaries for database 'mydb'.
Database 'mydb', checkpoint=(47041159, 2), first=(47041159, 2), last=(47041159, 8).
Completed estimating recovery log boundaries for database 'mydb'.
Started ANALYSIS pass for database 'mydb'.
Completed ANALYSIS pass for database 'myb'.
Recovery of database 'mydb' will undo incomplete nested top actions.
The transaction log in database trading is almost full. Your transaction is being suspended until space is made available in the log.
- On the primary:
- The sysusages looks like:
dbid segmap lstart size vstart location unreservedpgs crdate vdevno
----- --------- ---------- ---------- ----------- -------- ------------- -------------------- -----------
.
.
11 3 98161152 8388608 0 0 8355840 Mar 23 20XX 1:25PM 54
11 0 106549760 23473664 106549760 9 23381970 Mar 23 20XX 1:25PM -11
11 3 130023424 2560 11191296 0 2550 Mar 23 20XX 1:25PM 71
.
. - This database had the shrink run years ago, and the server has been, upgraded and rebooted many times, but the hole is not being reclaimed.
- Most of the time, the hole does not have any impact on the dumps/loads.
Read more...
Environment
- SAP Adaptive Server Enterprise 15.7
- SAP Adaptive Server Enterprise 16.0
Product
SAP Adaptive Server Enterprise 16.0
Keywords
KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , How To
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.