Running db_migratecatalog crashes with SYSERROR -9400 AK Cachedirectory ful

Question

I'd like to upgrade our main instance from 7.6.05.09 to 7.7.06.09. I tried to test the process on a test system where I installed 7.6.05.09 and restored our main instance from a full backup. So far it looked fine and a db check showed no errors.
Now I wanted to migrate the catalog with db_migratecatalog which results in the following:
2009-05-23 15:44:27                          --- Starting GMT 2009-05-23 13:44:27           7.6.05   Build 009-123-191-997
2009-05-23 15:44:55  5141 ERR 51105 AK CACHE AK00001.dmp     written: 0
2009-05-23 15:44:55  5141 ERR 51382 MIGRAT   MIGRATION FAILED WITH ERROR -9400
2009-05-23 15:44:55  5141 ERR 51080 SYSERROR -9400 AK Cachedirectory full
2009-05-23 15:44:56                          ___ Stopping GMT 2009-05-23 13:44:56           7.6.05   Build 009-123-191-997
I'm stuck, I just can't make it work whatever I try
Any help to find out how to go on is greatly appreciated.
Regards,
Simon

Answer 1

Hello Simon,
1. What is the current status of the database upgrade?
     Please update with output of the commands:
      dbmcli -s inst_enum
      dbmcli -s db_enum
    What is the value of the database parameter _UNICODE?
2.
According your knldiag file the _UNICODE parameter is set to YES,
   DEFAULT_CODE set to ASCII, but the catalog migration step was NOT finished. Correct?
  I assumed that you created the complete databackup before you started the database upgrade to the version 7.7.06.09 and before run "db_migratecatalog". And you are running the database version 7.6.05.09.
Please run the following steps:
A) Stop the database. Change database parameter _UNICODE to NO                                                
    For example, using dbm command:                                    
                 param_directput _UNICODE NO                                                                               
Restart the database in the admin mode & check the values of the  database parameters DEFAULT_CODE & _UNICODE  in the knldiag file. 
B) Initialize the database for the restore, for example, using DBMGUI and continue with restore of the databackup created before you run "db_migratecatalog".
C) Restart the database & load system tables.
     Run the database "check data"< Verify >. Check the BAD INDIZES if the new has to be recreated. 
2. If SDBUPD during the upgrade from 7.6.05.09 to 7.7 asked to migrate the catalog to UNICODE first
    ==>
   To perform the migration of the database version 7.6.05.09 please run:
Create the complete databackup;
Bring the database to the offline status;                                                                               
Increase the database parameters CAT_CACHE_SUPPLY to 50000
                                                                 CACHE_SIZE to 125000
Run the database catalog migration using the dbm command db_migratecatalog.
           Please check, that the migration is not terminated.                                              
The database will be in online status after the catalog migration finished successfully.                                                         
please send the knldiag file if the catalog migration failed.
3. You wrote:
     "Please note that this instance has lived since the SAPDB 7.3 or 7.4"
    If you used SDBUPD when migrating from Release 7.3.00 to at least Release 7.4.03, the database catalog is automatically converted to Unicode and  the _UNICODE parameter is then set to "YES" at the end of the process. 
Do you know what version of the database was installed initially? How the database was upgraded to the version 7.6.05.09?
Thank you and best regards, Natalia Khlopina
Edited by: Natalia Khlopina on May 27, 2009 9:20 PM