on 12-11-2012 3:26 PM
I am running MIGMON toexport a DB
However R3load fails to create CMD files for some packages, whilst creating CMD files for other packages without issu
anyone seen this symptom before during OS/DB migration?
NB error messages are appearing in this format from the migmon tool:
Unloading of 'SAPAPPL1_8' export package: ERROR
Unloading of 'SAPAPPL1_7' export package: ERROR
Unloading of 'SAPAPPL1_1' export package: ERROR
and for each of these packages there is no CMD file generated - only TSK and log files (which don't hold any useful information). For other packages there is no issue.....
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Note we're getting a mixed bag of failed and not failed exports...
e.g.
Unloading of 'SAPAPPL1_8' export package: ERROR
Unloading of 'SAPAPPL1_7' export package: ERROR
Unloading of 'SAPAPPL1_1' export package: ERROR
Unloading of 'SAPAPPL1_2' export package: OK
Unloading of 'SAPAPPL1_6' export package: ERROR
Unloading of 'SAPAPPL1_3' export package: ERROR
Unloading of 'SAPAPPL1_4' export package: OK
Unloading of 'SAPAPPL1_9' export package: ERROR
Unloading of 'SAPSSEXC_2' export package: ERROR
Unloading of 'SAPAPPL0_1' export package: OK
Unloading of 'SAPAPPL0_2' export package: ERROR
Unloading of 'SAPSSEXC_1' export package: ERROR
Unloading of 'SAPSDIC' export package: ERROR
Unloading of 'SAPCLUST' export package: ERROR
Unloading of 'SAPSSEXC_3' export package: ERROR
Unloading of 'SAPNTAB' export package: ERROR
Unloading of 'SAPSPROT' export package: ERROR
Unloading of 'SAPAPPL0_3' export package: OK
Unloading of 'SAPSLEXC' export package: OK
Unloading of 'SAPUSER' export package: ERROR
Unloading of 'SAPPOOL' export package: ERROR
Unloading of 'TST03' export package: OK
Unloading of 'SAPSSRC' export package: OK
Unloading of 'SAPAPPL0_4' export package: OK
Unloading of 'SAPDDIM' export package: ERROR
Unloading of 'SAPSDOCU' export package: OK
Unloading of 'SAPUSER1' export package: ERROR
Unloading of 'SAPSLOAD' export package: OK
Unloading of 'SAPDFACT' export package: ERROR
Unloading of 'SAPDODS' export package: OK
For every package with an ERROR
no CMD file is generated but there are no clear errors in the log.
e.g.
the log from SAPUSER, which errored and has no CMD file generated.....
<server>:bt4267 200> cat SAPUSER.log
/usr/sap/GEA/SYS/exe/run/R3load: START OF LOG: 20121211105238
/usr/sap/GEA/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
/usr/sap/GEA/SYS/exe/run/R3load: version R7.20/V1.4 [UNICODE]
Compiled Jan 15 2012 20:58:35
/usr/sap/GEA/SYS/exe/run/R3load -ctf E /oracle/GEA/O2O/DATA/SAPUSER.STR /oracle/GEA/O2O/DB/DDLORA.TPL SAPUSER.TSK ORA -l SAPUSER.log
/usr/sap/GEA/SYS/exe/run/R3load: job completed
/usr/sap/GEA/SYS/exe/run/R3load: END OF LOG: 20121211105238
For anyone reading this (which it seems now should just have been a blog entry) - here is my finding. Never use NFS!
At least not for the migmon location where you hold your binaries and your TSK/cmd/log files - these must be local.
However you can make your target for DATA/DB files a NFS - this is good for migration across servers.
Hope that helps someone else out there!
User | Count |
---|---|
76 | |
9 | |
8 | |
7 | |
6 | |
5 | |
5 | |
5 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.