Hi,
ASE version 12.5.4, dump from prod and load in test.
after the load successfully completed the online db does not
work with no error:
1> online database db1
Started estimating recovery log boundaries for database
'db1'.
Database 'db1', checkpoint=(1086143, 5), first=(1086143, 5),
last=(435084353, 2).
Completed estimating recovery log boundaries for database
'db1'.
Started ANALYSIS pass for database 'db1'.
Completed ANALYSIS pass for database 'db1'.
Recovery of database 'db1' will undo incomplete nested top
actions.
SQL Server could not bring database 'db1' online.
---
The only problem we have seen is that during dump in prod
the log filled up but when the dump end the log become
empty. dump and load were performed successfully. No error
in ASE or backupserver.
Now we are trying another dump, do you have idea why ASE
cannot bring online the db?

Are there any messages in the ASE error log?

Michael

On Wed, 06 May 2009 08:03:13 -0700, wrote:

Michael Peppler [Team Sybase] wrote:
Also try "select @@error" after the ONLINE command,
does seem like something should be getting raised there.

-bret

completed.
I cannot try again or do some more test like 'select
@@error'.
But, just as document because it is possible there is a bug
here is the log of load:
....
Backup Server: 4.58.1.1: Database db1: 874748348 kilobytes
LOADED.
Backup Server: 3.42.1.1: LOAD is complete (database db1).
Started estimating recovery log boundaries for database
'db1'.
Database 'db1', checkpoint=(1086143, 5), first=(1086143, 5),
last=(435084353, 2).
Completed estimating recovery log boundaries for database
'db1'.
Started ANALYSIS pass for database 'db1'.
Completed ANALYSIS pass for database 'db1'.
Started REDO pass for database 'db1'. The total number of
log records to
process is 21166021.
Redo pass for database 'db1': 1058301 records done (4%);
20107720 records
left.
.....
Redo pass for database 'db1': 21166020 records done (99%); 1
records left.
Redo pass of recovery has processed 932 committed and 1
aborted transactions.
Completed REDO pass for database 'db1'.
Use the ONLINE DATABASE command to bring this database
online; SQL Server will
not bring it online automatically.
1> online database db1
Started estimating recovery log boundaries for database
'db1'.
Database 'db1', checkpoint=(1086143, 5), first=(1086143, 5),
last=(435084353, 2).
Completed estimating recovery log boundaries for database
'db1'.
Started ANALYSIS pass for database 'db1'.
Completed ANALYSIS pass for database 'db1'.
Recovery of database 'db1' will undo incomplete nested top
actions.
SQL Server could not bring database 'db1' online.
-----------------------
One can see here that the message 'SQL Server could not
bring database 'db1' online.' comes when ASE should start
the UNDO operations, the normal message is:
....
Recovery of database 'db1' will undo incomplete nested top
actions.
Started UNDO pass for database 'db1'. The total number of
log records to
process is 7994696.
Undo pass for database 'db1': 399734 records done (4%);
7594962 records
left.
.....
Undo pass for database 'db1': 7994680 records done (99%); 16
records left.
Undo pass of recovery has processed 2 incomplete
transactions.
Completed UNDO pass for database 'db1'.
Database 'db1' is now online.
--------------------------------------
Moreover I can say than the command 'online database db1 for
standby access' worked normally and db was accessible.
Because the dump from production was taken with transaction
log full (error 1105) looks that the problem is that in test
(db with exactly the same size and fragments) ASE was not
able to start UNDO because of low free space in log but this
is just an hipotesys.