To improve performance, i read this note :
Note 1045847 - ORACLE DIRECT PATH LOAD SUPPORT IN R3LOAD
In this note : it's specified
"
To use this feature one has to add "-loadprocedure fast" (without the
double quotes) to the command line when R3Load is started.
"
How i can added this option while performing a system copy with R3load ?
thanks for reply
This argument "-loadprocedure fast" is to provided in the screen of SAPINST when it asks for R3load load arguments during the import .
In the installation directory during the installation/import you get a migration monitor import properties file named import_monitor_cmd.properties. You can manually edit this file or verify as well the section loadArgs in the file before the ABAP Load phase.If you pass the argument in SAPINST input screen it would be populated in this file.
Typically the file would look like this
********************************************************************************************
importDirs=/exports/db2migrate/P31/ABAP
installDir=/install/P31_DB_import
orderBy=/install/orderby.txt
ddlFile=/exports/db2migrate/P31/ABAP/DB/DDLORA.TPL
ddlMap=
monitorTimeout=30
r3loadExe=/sapmnt/P31/exe/R3load
tskFiles=yes
extFiles=no
dbCodepage=4102
migrationKey=1gqgf5M50Dp01eqtd1M11Qqv
omit=
taskArgs=
loadArgs=-loadprocedure fast -merge_bck -nolog -stop_on_error
jobNum=10
exchangeDir=/exports/db2migrate/P31/xchP31
trace=all
*************************************************************************
Regards
Ratnajit
Dear Ratnajit
I can't find the file import_monitor_cmd.properties.
For your information, we proceed a conversion unicode with system copy of 4.72 system (R/3 enterprise , kernel 6.40 )
This file import_monitor_cmd.properties is migration monitor properties file. In release 640 , the sapinst does not invoke migration monitor by default for export/import (which is default as of NW 700 release) and hence this file will not be available.
You will need to invoke migration monitor manually (select in the dialog screen of sapinst) during the import to get this file available in the migration monitor directory where you can go ahead and edit the file and add the load arguments.
You download the MIGMON.SAR file from the SAP service marketplace . Uncar it . You will get a pdf file which has the details of the usage of the tool.
You will get some good information in the link below
http://www.redbooks.ibm.com/redbooks/pdfs/sg247774.pdf
Regards
Ratnajit
I have re-rexecute sapinst with Migration Monitor Option to create database instance with system copy.
I have change options in file import_monitor_cmd.properties
But when I execute import_monitor.sh, nothing happens. I get
"
# ./import_monitor.sh
+ /sauv/SAPJVM/sapjvm_4/bin/java -showversion -Xmx1024m -cp ./.:./migmon.jar:./activation.jar:./mail.jar com.sap.inst.lib.app.SecureStartup -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -dbType ORA
java version "1.4.2_34"
Java(TM) 2 Runtime Environment, Standard Edition (build 4.1.019)
SAP Java Server VM (build 4.1.019 19.1-b02, Feb 15 2012 00:08:50 - 41_REL - optU - aix ppc64 - 6 - bas2:166760 (mixed mode))
"
I have checked the import_monitor.log without error :
# cat import_monitor.log
INFO: 2012-07-19 23:11:56
Import Monitor is started.
CONFIG: 2012-07-19 23:11:56
Application options:
dbCodepage=4102
dbType=ORA
ddlFile=/sauv/EXPORT/DB/DDLORA.TPL
ddlMap=
exchangeDir=/sauv/MIGMON
extFiles=no
importDirs=/sauv/EXPORT
installDir=/sauv/MASTER
jobNum=5
loadArgs=-loadprocedure fast -merge_bck -nolog -stop_on_error
localhost=
mailFrom=
mailServer=
mailTo=
migrationKey=
monitorTimeout=30
omit=
orderBy=size
port=
r3loadExe=/sapmnt/PR1/exe/R3load
taskArgs=
trace=all
tskFiles=yes
CONFIG: 2012-07-19 23:11:56
List of packages with table structure: 'SAP0000'.
CONFIG: 2012-07-19 23:11:56
List of packages with views: 'SAPVIEW'.
TRACE: 2012-07-19 23:11:56 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of '/sauv/EXPORT/DB/DDLORA.TPL' template file is started.
INFO: 2012-07-19 23:11:56 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of '/sauv/EXPORT/DB/DDLORA.TPL' template file is successfully completed.
Primary key creation: after load.
Index creation: after load.
INFO: 2012-07-19 23:14:02
Import Monitor is started.
CONFIG: 2012-07-19 23:14:02
Application options:
dbCodepage=4102
dbType=ORA
ddlFile=/sauv/EXPORT/DB/DDLORA.TPL
ddlMap=
exchangeDir=/sauv/MIGMON
extFiles=no
importDirs=/sauv/EXPORT
installDir=/sauv/MASTER
jobNum=5
loadArgs=-loadprocedure fast -merge_bck -nolog -stop_on_error
localhost=
mailFrom=
mailServer=
mailTo=
migrationKey=
monitorTimeout=30
omit=
orderBy=size
port=
r3loadExe=/sapmnt/PR1/exe/R3load
taskArgs=
trace=all
tskFiles=yes
CONFIG: 2012-07-19 23:14:02
List of packages with table structure: 'SAP0000'.
CONFIG: 2012-07-19 23:14:02
List of packages with views: 'SAPVIEW'.
TRACE: 2012-07-19 23:14:02 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of '/sauv/EXPORT/DB/DDLORA.TPL' template file is started.
INFO: 2012-07-19 23:14:02 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of '/sauv/EXPORT/DB/DDLORA.TPL' template file is successfully completed.
Primary key creation: after load.
Index creation: after load.
Please login as <sid>adm and set JAVA_HOME (which I believe you have done)
Then start import_monitor.sh
Else you will face issues with the environment as <sid>adm is the user which should run the import monitor.
Regards
Ratnajit
I start the import_monitor.sh with user <sidadm> but i have the same problem. nothing happend
In the import_monitor_cmd.properties ,
change the following :
importDirs=/sauv/EXPORT/ABAP
exchangeDir=
The above should be blank if you are not doing export and import parallely.
Regards
Ratnajit
the same problem . nothing happend
I would like to inform you that sapinst start with any problem.
This should be (you were correct the first time ..its 640 not 700)
importDirs=/sauv/EXPORT/
Please check if R3load processes are running after you start the import_monitor.sh
also check if migmon process is running (ps -ef |grep migmon)
Normally it takes sometime to get started . So just wait for sometime.
Is there any error import_monitor.log at the end . If no , then its running fine.
Regards
Ratnajit
problem solved . thank you