Move a MaxDB instance to a server already running a MaxDB

[Former Member]

Hello!

What is the procudure of moving a MaxDB (version 7_6_01_12) from server B to server A that is already installed with another instance of 7_6_01_12?

Both systems on Suse Linux 64bit.

In particular, how do I merge the common /sapdb contents?

What do I consider regarding the hostnames?

Regards,

Fredrik

[markus_doehr2]

Do you want to overwrite the insteance on the second server or do you want to "add" it?

--

Markus

[Former Member]

Both instances of MaxDB shall run on "server A". That is, the currently instance on "server A" will be kept.

Message was edited by:

Fredrik Rosengren

[markus_doehr2]

The easiest way do accomplish this is to create a backup on serverA , create the database instance on serverB (using DBMGui or a script) and restore the backup on serverB.

--

Markus

[Former Member]

Sounds like a good way to do it!

Is there any specific parameters/options to consider when creating the new instance on the target server?

What restore type do you suggest?

Regards,

Fredrik

[markus_doehr2]

I would go for the default setup just changing

MAXCPU

MAXBACKUPDEVS

CACHE_SIZE

initially. After the restore (Restore with initialization) I would go tuning the rest.

--

Markus

[former_member229109]

Hello Fredrik,

If you SAP customer, please see the SAP note:

129352 Homogeneous system copy with MaxDB (SAP DB)

If you are going to do Homogeneous database copy using backup/restore

Procedure < copy of the database MaxDB (version 7_6_01_12) from server B to

server A that is already installed with another database instance of the

Same version 7_6_01_12. And both systems are on Suse Linux 64bit.>, please

pay attention to the following hints:

-> The parameter _UNICODE has to be in the source system and in the

target system of the same value. To avoid the recovery to be failed due of

unicode mismatch, you will see, for example, the message "BErr Assertion of

state _UNICODE must be equal failed!" in the knldiag.err file => I recommend

take over the parameter from the backup by reinstalling the database instance

and edit them directly afterwards, please check the settings of the database

Parameters RUNDIRECTORY & DIAG_HISTORY_PATH, configuration of the data and log

Volumes. Please also check if you have enough OS resources on the target server

for configured MAXCPU, CACHE_SIZE values.

-> You need also to be sure that you have configured the data volumes in the

target database to be able to restore the backup of the source database.

You could review the documents at :

http://maxdb.sap.com/currentdoc/default.htm

< For example, ->Tutorials -> "Creating a Database Copy (Importing a Data Backup into Another Database Instance)" at

http://maxdb.sap.com/currentdoc/87/dba841c0dae234e10000000a1550b0/content.htm

If you would like to use DBMGUI to create the instance for the recovery on

the target server or use Restoring After Initializing a Database Instance,

see the info at

Tools -> Database Manager GUI -> Creating a Database Instance ->

Custom

OR

"Restoring After Initializing a Database Instance" at

http://maxdb.sap.com/currentdoc/30/5ada35596211d4aa83006094b92fad/content.htm >

Thank you and best regards, Natalia Khlopina