cancel
Showing results for 
Search instead for 
Did you mean: 

Migration problem from SAPDB 7.4.3.32 to MaxDB 7.6.03.15

Former Member
0 Kudos

Hi!

I'm trying to migrate from SAPDB 7.4.3.32 to MaxDB 7.6.03.15 using MaxDb Installation manager 7.6.03.15 on Windows XP Pro SP2. But it fails while migrating catalog to unicode with error -9400. Here's the part of log:

migration of catalog to unicode failed

ERROR: current database state is ONLINE

switch database state to OFFLINE

migrating catalog to unicode...

migration of catalog to unicode failed

db_migratecatalog

ERR

-24988,ERR_SQL: SQL error

-9400,System error: AK Cachedirectory full

3,Database state: OFFLINE

looking for error messages in knldiag

...

2008-05-16 09:16:38 0x258 ERR 51105 AK CACHE AK00001.dmp written: 0

2008-05-16 09:16:38 0x258 ERR 51382 MIGRAT MIGRATION FAILED WITH ERROR -9400

2008-05-16 09:16:38 0x258 ERR 51080 SYSERROR -9400 AK Cachedirectory full

2008-05-16 09:16:38 0x258 3 Admin Database state: OFFLINE

2008-05-16 09:16:38 0x258 19651 CONNECT Connection released, T22

2008-05-16 09:16:38 0x258 19620 DBSTATE Shutdown normal requested

2008-05-16 09:16:38 0x4D4 19684 TASKING Tracewriter termination timeout: 1200 sec

2008-05-16 09:16:38 0x274 20000 Trace Start flush kernel trace

2008-05-16 09:16:38 0x274 19617 VOLUMEIO Single I/O attach, 'knltrace', UKT:1

2008-05-16 09:16:39 0x274 20001 Trace Stop flush kernel trace

2008-05-16 09:16:39 0x274 19619 TASKING Releasing tracewriter

2008-05-16 09:16:39 0x4D4 19600 VERSION 'Kernel 7.6.03 Build 015-123-173-107'

2008-05-16 09:16:39 0x4D4 19654 DBSTATE SERVERDB 'TEST' has stopped

-


current write position -


I've tried to increase CAT_CACHE_SUPPLY value, but it still crashes with 9400.

Can anyone help me?

Edited by: Alex Petrov on May 16, 2008 4:21 AM

Accepted Solutions (0)

Answers (2)

Answers (2)

lbreddemann
Active Contributor
0 Kudos

Hi Alex,

please post the complete knldiag file including the parameter section.

KR Lars

0 Kudos

Hi there,

Sorry for the noise, I just wanted to ask if the problem went away for you and if there is anything in particular that you did for that? I have the same problem, and in the end I used the following link as reference : http://maxdb.sap.com/doc/7_7/44/dc468611096ebee10000000a11466f/content.htm

I used the MaxDb Installation manager 7.6.03.15 only to update the software, and then used dbmcli to perform the steps in the document. It went fine, as it didn't try to migrate to UNICODE, but I have other problems then, like for example a simple query with a where clause now returns data that doesn't comply with the clause condition.

Is it possible that moving to UNICODE is required or recommended when migrating from 7.4.03 to 7.4.03?

Many thanks,

Catalin

lbreddemann
Active Contributor
0 Kudos

Hi Catalin,

the migration of the database catalog (not your application data!) is a must when upgrading to 7.6.

If you're an SAP customer, please do open a support message for that issue.

Otherwise please post the full knldiag file.

best reagards,

Lars

Former Member
0 Kudos

Hi, sorry for too late answer. I decided problem only after complete data export using my own sql export tool. Then I made a clean installation of 7.6 and data import.

Thanks.

Former Member
0 Kudos

Hi Alex,

is autolog switched on?

Is there engough space for generated autologs?

Regards

Manuel

Former Member
0 Kudos

Hi Manuel!

Autolog is off. About 85% of log area is empty, and there's also enough free disk space.