![]() | ![]() |
Home |
|
|
Troubleshooting and Error Messages Guide |
|
| Chapter 3 Error Message Writeups |
|
| Recovery Errors |
|
| Error 3470 |
10
SQL Server could not completely upgrade database '%.*s', but the database was online when upgrade began, so it will be left online.
When Adaptive Server tries to bring an already online database to the online state and it finds that some elements of the database have not been upgraded, it tries to complete the database upgrade. Error 3470 occurs when that attempt to upgrade the database fails.
Determine the current upgrade version for the database. For example, to determine the upgrade version of a database called test_db, use the following commands:
1> load database test_db from 'test.dump' with headeronly 2> go
Backup Server session id is: 6. 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 `test_db952820A2F8' section number 0001 mounted on disk file `/remote/solaris/rel1100/install/test.dump'
This is a database dump of database ID 6, name `test_db', from Oct 9 1995 11:35AM. SQL Server version: SQL Server/11.0/B/Sun_svr4/OS5.2/1/OPT/Fri Aug 1805:10:26 PDT 1995. Backup Server version: Backup Server/11.0/B/Sun_svr4/OS5.4/1/OPT/Thu Aug 17 21:54:21 PDT 1995.
Database contains 1536 pages; checkpoint RID=(Rid pageid = 0x405; row num = 0xd); next object ID=3031; sort order ID=50, status=0; charset ID=1.Database log version=2; database upgrade version=1.
Call Sybase Technical Support. Have the following information ready:
Server version and SWR Rollup level
Server error log
Text of all error messages
Output from step 1
Output from sp_configure "upgrade version".
All versions
|
|