xtrusion0
asked on
Sybase ASE 12.5.4 load database unexplained output
Hello,
I have an archive database server that contains bunch of archive databases on a single Sybase ASE 12.5.4 instance. This instance has been up & running for over a year and in production with no issues. This ASE instance doesn't run anything special such as HA/Replication and the configuration is as basic as it can get. What I'm seeing is after I dump a database and load it onto another ASE instance(same version/os/nothing special) I see the output shown below.
The database 'archivedb01' is currently not available and cannot be checked for
cross-database encryption key references for the keys existing in database
'archivedb02'.
To sum up the messages above... archivedb01 was a recently loaded database dump(never online'd yet) from the archive database server. When I go to load the next archival database(archivedb02) that message appears. If I were to continue loading the remaining archival databases the message continues to grow.
The database 'archivedb02' is currently not available and cannot be checked for
cross-database encryption key references for the keys existing in database
'archivedb06'.
The database 'archivedb03' is currently not available and cannot be checked for
cross-database encryption key references for the keys existing in database
'archivedb06'.
The database 'archivedb04' is currently not available and cannot be checked for
cross-database encryption key references for the keys existing in database
'archivedb06'.
If I online these database and continue to load these dumps the message disappears. I've tried loading them on a different ASE instance and the message still appears. I'm out of ideas and I'm beginning to think this message is just there to waste my time and make me worry over nothing. I've googled, searched sybase, and I can't turn up anything about this message. Anyone have any idea what this message is getting at and if it's a concern?
Thanks.
I have an archive database server that contains bunch of archive databases on a single Sybase ASE 12.5.4 instance. This instance has been up & running for over a year and in production with no issues. This ASE instance doesn't run anything special such as HA/Replication and the configuration is as basic as it can get. What I'm seeing is after I dump a database and load it onto another ASE instance(same version/os/nothing special) I see the output shown below.
The database 'archivedb01' is currently not available and cannot be checked for
cross-database encryption key references for the keys existing in database
'archivedb02'.
To sum up the messages above... archivedb01 was a recently loaded database dump(never online'd yet) from the archive database server. When I go to load the next archival database(archivedb02) that message appears. If I were to continue loading the remaining archival databases the message continues to grow.
The database 'archivedb02' is currently not available and cannot be checked for
cross-database encryption key references for the keys existing in database
'archivedb06'.
The database 'archivedb03' is currently not available and cannot be checked for
cross-database encryption key references for the keys existing in database
'archivedb06'.
The database 'archivedb04' is currently not available and cannot be checked for
cross-database encryption key references for the keys existing in database
'archivedb06'.
If I online these database and continue to load these dumps the message disappears. I've tried loading them on a different ASE instance and the message still appears. I'm out of ideas and I'm beginning to think this message is just there to waste my time and make me worry over nothing. I've googled, searched sybase, and I can't turn up anything about this message. Anyone have any idea what this message is getting at and if it's a concern?
Thanks.
ASKER
Rbride -- thanks for the quick response, but that doesn't explain the error though. My real concern is the integrity of that data. I've dealt with sybase for roughly 5 years and I've never seen that message. In a sense, when have you online'd a database and it referenced other databases? That's my puzzle.
ASKER
Sorry, didn't mean to say online, but instead reference these other databases when loading an entirely different dump.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Now I understand: I agree with Joe Woodhouse.
You have said it yourself. You always need to online the database after it has been loaded to make it available. The reason you need to explicitly online the database is that you have the option of loading transaction logs before making the DB online.
[http://manuals.sybase.com/onlinebooks/group-as/asg1250e/refman/@Generic__BookTextView/63290;pt=28072/*]