I have done the upgrade from 7.3 to 7.5 here at work, I suggest waiting on
7.6 if you are upgrading a production db server. I wrote and sent a
migration howto to the mailing list some time ago, it's attached for you to
reference. If that doesn't get you there then shoot me a question and I'll
do my best to help but I am in no way an expert. 

Kevin

-----Original Message-----
From: Manuel Reiter [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 13, 2005 2:47 AM
To: maxdb@lists.mysql.com
Subject: SAPDB 7.3 -> MAXDB 7.5/7.6 Upgrade / specialists wanted


We do have a pure Java Client Server Solution (JBOSS/Tomcat) that 
connects to SAPDB 7.3.
We want to upgrade the databases to MAXDB 7.5/7.6 to have better 
performance / tuning possibilities.
So we search for an expert on this issue who could support us in 
upgrading / tuning the databases.

best regards Manuel Reiter / Austria



-- 
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:
http://lists.mysql.com/[EMAIL PROTECTED]

--- Begin Message ---
I figured I would share with those that are still running a 7.3.0.3x
instance a easy method (kind of) to transfer that instance to the latest and
greatest MaxDB running on another server without the need of having to have
a parallel installation and using the DBMGUI interface.

[Execute steps 1 - 8 of the 7.3 to 7.4 migration document]
        open dbmgui (1st edition)
        create a new backup medium target
        take instance offline
        take instance to admin
        menu: Instance->command line
        exec "util_execute migrate"
        exec "util_connect"
        exec "backup_start <newly created medium name>"
        exec "util_release"
        exec "db_offline"

Close the 7.3 dbmgui.

Copy the backup medium to the other server, etc.

Open dbmgui v7.5.0.18 

Create a new instance for restore.
        select "Blank"
        (fill in all the info as usual)
        select restore from backup (Parameter Initialization)
        specify the medium of your fresh backup.
        change any of the paths/etc to fit new system.
        Read the label (if it can't do this that is a bad thing)
        change the file paths of the data and log devices.
        enter in a new backup medium 
        select the migration backup as the medium to restore.
        run 

Once it is done importing and you restart the instance open up the command
line again and issue the following:

        load_systab -u <dbm user>,<dbm pass> -ud <domain user pass>

Take it offline and then bring it back online and you are done. May be a
good idea to run a full backup at this point.

Hopefully this will help someone down the line.


--- End Message ---
-- 
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to