Error 4322

Severity

16

Message text

SQL Server cannot load a dump of the master database that was dumped from an older version of SQL Server. The current master database upgrade version is %ld, the dump master database upgrade version is %ld.

Explanation

Error 4322 is raised when you try to load a dump of the master database that was created on an earlier version of Adaptive Server than your currently installed version.

Action

If you know you do not have a dump of master from your current version level because you did not dump master after you upgraded, and your master database is corrupted, call Sybase Technical Support.

Otherwise, check the current upgrade version of the master dump you are trying to load. For example:

1> load database master from 'master.dump' with headeronly 
2> go

Backup Server session id is: 54. 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 'master072670B065 ' section number 1 mounted on disk file '/work/dputz/ase1502/ASE-15_0/install/master.dump' This is a database dump of database ID 1, name 'master', from Sep 24 2007 12:32PM. ASE version: Adaptive Server Enterprise/15.0.2/EBF 14328/P/Sun_svr4/OS 5.8/ase1502/2486/64-bit/FBO/Thu May 24 12:. Backup Server version: Backup Server/15.0/EBF 13443 ESD#2/Sun_svr4/OS 5.8/ase15x/2603/32-bit/OPT/Fri Mar 24 03:05:01 2006. Database page size is 2048. Database contains 6656 pages; checkpoint RID=(Rid pageid = 0x100c; row num = 0x13); next object ID=924527296; sort order ID=50, status=0; charset ID=1. Database log version=7; database upgrade version=35. segmap: 0x00000007 lstart=0 vstart=[vpgdevno=0 vpvpn=4] lsize=6656 unrsvd=2982

The log version and upgrade version have these values:

Version

Database log version

Database upgrade version

12.0 through 12.0.0.8

5

25

12.5 through 12.5.4

6

31

15.0 and later

7

35

Additional information

If you call Sybase Technical Support, have the information on hand that is listed in “Reporting errors”, including the output from the load database...with headeronly command if you have what you thought was a current dump, and the output from sp_configure "upgrade version".

Versions in which this error is raised

All versions