Re: Migration SapDB 7.3 to MaxDB 7.6 doubts and problems

Hi,

i found a 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?

On 7/17/07, Clovis Wichoski <[email protected]> wrote:
>
> 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:
>
> [-9205]: 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) ?
>
> thanks for any help.
>
> Clóvis
>
>
>
>