cancel
Showing results for 
Search instead for 
Did you mean: 

Migration SapDB 7.3 to MaxDB 7.6 doubts and problems

Former Member
0 Kudos

Hi,

I migrated from SapDB 7.3 version to MaxDB 7.6.2.10 using the follow

process:

commands on dbmcli for version SapDB 7.3:

db_offline

db_cold

util_execute migrate

util_connect

backup_start completeF

db_offline

after copy the compleF media to MaxDB 7.6.2.10 directory and run the follow

commands on dbmcli in this new version:

db_admin

util_execute migrate database

db_connect

db_activate RECOVER completeF

db_online

load_systab -u dba,pwd

sql_recreateindex

util_connect

backup_start completeF

db_offline

db_warm

with these commands i can migrate from 7.3 to 7.6.2.10 all data are in the

new database, but some problems occurs like:

: System error: AK Catalog information not

found:000000000000000000690001

that occurs when i update one table that uses triggers on old versions, in

mail lists i found the solution for this problem on the message

http://lists.mysql.com/maxdb/28223 that in resume says:

RENAME T TO SUSPENDED

CREATE TABLE T LIKE SUSPENDED

INSERT INTO T SELECT * FROM SUSPENDED

DELETE SUSPENDED (if possible)

recreate all views, synonyms, triggers etc. based on T

but, this is a uggly solution and dont a better approach i like to migrate

without get any errors of that kind, then the doubt is, there is a another

way to migrate without getting this errors? exists any sample using repmcli

(SapDB 7.3) and loadercli (MaxDB 7.6) ?

i try another solution, drop all triggers on version SapDB 7.3 before create the

backup for migration, then do backup, restore on 7.6, then recreate manually

the triggers, this is better, but anyone knows because the triggers dont

migrate, like tables and stored procedures?

thanks for any help

Clóvis

Accepted Solutions (0)

Answers (1)

Answers (1)

lbreddemann
Active Contributor
0 Kudos

Dear Clovis,

why didn't you use the standard way to upgrade the database? SDBUPD ?

The Backup/Restore technique is not officially supported and largely untested.

KR Lars

Former Member
0 Kudos

Dear Lars,

i'm migrating all things, i'm installing into a new hardware and O.S., and for this type of change the guys that i chat in past, says that this is the only way to migrate, i dont know how i can do migration with SDBUPD too since on new installation the database dont exists.

what i'm doing here is:

migrate a SapDB 7.3 running in a Dual Xeon 2.8 2GB of RAM with RedHat 9

to

MaxDB 7.6.2.10 running in a Xeon QuadCore 5GB of RAM with Red Hat Enterprise Linux 5 x86_64bit

any idea how to do this migration in a safe way?

best regards

Clóvis

Former Member
0 Kudos

I can migrate, without error and just dropping the triggers, and recreate on the new version.

now the MaxDB is up and running with version 7.6.03.07, just dont use functions, this version have Bugs, but in next release, the Bugs with functions will be solved, about functions Bugs see the thread