System migration with Distribution Monitor (Distmon)

[Former Member]

Dear Experts,

I am hoping someone might be able to clear up some doubts I have regarding the Distribution Monitor (distmon) to perform a migration.

I have been working on the procedure for about a week in one of my companies' laboratories, and as of now, I am quite stuck.

I have searched as much information as I can -- I have seen the distribution manager guide (latest from the distmon note), checked the presentation, googled to see as many wikis and scn questions, but there are still some things that are not clear for me, and would be great if someone could help me clear them up.

So:

I have prepared 4 hosts (sourcehostDM, exporthost1, exporthost2, targethostDM). They all have been created with the same template, have SAP installed, and from the names, you can understand which one is which.

I have a shared commDir with all the configuration files, as well as copied those same configuration files onto the local commDir that exist for all machines.

So all systems have the following configuration files accessible in the shared commDir folder + in the local shared folder.

Below are the configuration files that were created from the samples from the distmon.sar:

distribution_monitor_cmd.properties

#
# Distribution Monitor options
#
#
# Main Options
#


# Communication directory shared between all hosts
commDir=/mnt/software/commDir/

# List of involved machines, separator on Windows ; on UNIX :
hostNames=sourcehostDM:exporthost1:exporthost2:targethostDM

# R3szchk arguments
# -s DB -t <dbType> <sid> <rel>
# -l and -p are set automatically
# use <dbType> and <sid> of the source system
# <dbType> is one of:  ada, db2, db4, db6, inf, mss, ora
# for DB2 z/OS: r3szchkArgs=-s DB -q <commDir>/R3ldctl
r3szchkArgs=-s DB -t ora N75 11g

#
# Machine specific information
#
# local directory to store R3load data dump
sourcehostDM.dataDirs=/oracle/localcommDir/
exporthost1.dataDirs=/oracle/localcommDir/
exporthost2.dataDirs=/oracle/localcommDir/
targethostDM.dataDirs=/oracle/localcommDir/

# number of jobs for R3load export
# typical is 2 to 4 per CPU
exporthost1.exportJobNum=2
exporthost2.exportJobNum=2

# number of jobs for R3load import
# typical is 1 to 4 per CPU
exporthost1.importJobNum=2
exporthost2.importJobNum=2

#
# steps to skip
# set when the results of these steps are already available and shall not be repeated
#


# Skip R3ldctl execution; specify path containing STR and TPL files if it
# is different from <commDir>/R3ldctl
# skipR3ldctl=


# Skip R3szchk execution; specify path containing EXT files if it
# is different from <commDir>/R3szchk
# skipR3szchk=


# Skip Package Split execution; specify path containing STR and EXT files
# if it is different from <commDir>/PkgSplit
# skipPkgSplit=

Both export_monitor_cmd.properties & import_monitor_cmd.properties

#
# Distribution Monitor options
#
#
# Main Options
#
# Communication directory shared between all hosts
commDir=/mnt/software/commDir/

Also I have the package_splitter_cmd.properties & package_splitter_tables.txt & distribution.txt which are rather unimportant for my doubts & issues, but I can paste them if needed.

Lastly, after preparation phase is executed, I have modified DDLORA.TPL & DDLORA_LGR.TPL as there's a known issue transforming @SCHEMAID@ onto your SCHEMA, and has to be modified. Otherwise, during import, I will receive some issues.

Now:

1. I understand that you must execute distribution_monitor.sh -p in the sourcehostDM from the local dataDir (in my case /oracle/localcommDir/) which will generate the folder structures and so on in the shared commDir.

Is this correct?

2. I understand that you must execute the distribution_monitor.sh -e in both the exporthost1 & exporthost2 from the local dataDir (in my case /oracle/localcommDir/). This works flawlessly, and it does generate all the export files that are needed, and distributes the load between the hosts as per the distribution.txt file.

Is this correct? And if so, how does it know that it must EXPORT the database or the files from sourcehostDM? Because at no point, I tell the program ANYWHERE in ANY file which is the "sourcehost" apart from the obvious hostname I have set... but distribution_monitor.sh does not speak English.

3. As in the 2 previous points, I will proceed to execute the distribution_monitor.sh -i from the targethostDM in the local communication directory and I *am guessing* it will use the exporthost1 & exporthost2 for the r3load and import the information onto targethostDM. However, once again, program does not speak English, so how is it identifying this information?

Furthermore, if I try to execute the distribution_monitor.sh -i on the targethostDM, it just generates some DDLORA files, and doesn't do anything else that I can see.

--

So, at this point, I am in a sea of doubts, and a bit lost. I have read the distribution monitor guide several times, I have checked notes, the migration course from sap learning hub, and there's nothing to clear this issues.

I would really appreciate if someone could point me onto the right direction!

Thanks in advance,

Kind regards,

PIU

[Former Member]

little bump . . .