Solman 4 error

my solman 4 running since 3 days at import abap 16 phase of 42.
plz help me
following error in log
INFO: 2007-04-19 20:36:17 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL2' import package is successfully completed.
INFO: 2007-04-19 21:40:16 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is successfully completed.
WARNING: 2007-04-19 21:40:22
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2007-04-19 21:40:22
1 error(s) during processing of packages.
INFO: 2007-04-19 21:40:22
Import Monitor is stopped.
and
TRACE      [iaxxejsexp.cpp:188]
           EJS_Installer::writeTraceToLogBook()
Returncode of C:\j2sdk1.4.2_12\bin\jar.exe: 0
TRACE      [iaxxejsexp.cpp:188]
           EJS_Installer::writeTraceToLogBook()
Jar file local_policy.jar is not included in zip file F:\sldprofile.zip, returning false
TRACE      [iaxxdlghnd.cpp:657]
           CDialogHandler::doHandleDoc()

Hi Mina,
I guess you're part of RampUp phase, in this case the best way should be to open a customer message into OSS.
Note that with UME and ABAP as datasource the client is very important, so please check the ABAP client (UME datasource) and the indicated on SLD, this should be sufficient to solve this.
For inconsistences you allways can use the tool mentioned on SAP Note 818947, but as this SolMan release is quite new and not officially released the answer must be provided directly by the developers, so don't hesitate to open a message in http://service.sap.com/message
Cheers,
Luis

Similar Messages

After BI 4.1 configuration in SOLMAN - error message "The systems you selected do not contain any software components currently supported by E2E Workload Analysis"

Hi All,
I'm trying configure E2E monitoring. I configured all necessary steps, I can see my BI 4.1 system in SLD, also in SOLMAN, all “lights” are green. But if I start Root Cause Analysis>> Ent-to End Analysis>> My system>> Workload Analysis, I see this error "The systems you selected do not contain any software components currently supported by E2E Workload Analysis".

It would be better if you can raise the question at Remote Supportability and Monitoring Tools
and or comment in the blog post How to generate and consume an E2E trace with BI4.x (for non-SolMan landscapes)
created by Toby Johnston
Do go through the note 1871260 - The systems you selected do not contain any software
components currently supported by E2E Workload analysis for SAP HANA
Hope they help.

No Project IMG has been defined for Starting Reference IMG SOLMAN ERROR

Hi All,
I created a off release project in prodcution and assigned logical compenents. When I am trying to create a IMG object for SPRO it is showing an error stating that "No Project IMG has been defined for Starting Reference IMG ". when I click Ok button it is showing another message ""Screen output without connection to user.". I Verified in project administration(solar_project_admin)> System Landscape>IMG projects, status for distributing IMG projects to component systems is showing in Red color. No IMG projects have been distributed into the system.
RFC connections are showing are correctly. I am not able to find the problem and solution. Could any one help me to figureout the problem and what needs to be done
Thanks in advance,
Sreekala Rapuru.

Is it mandatory that i need to create a project view?
I have created a view "activity necessity", but not have selected any of the check boxes in "mandatory/optional/nonrequired". As well i havent generated it. I can do the "configure" now without errors
my question is - is there anything critical which is related to this views? I went through the help page you sent me.. Is this for creating the implementation guide? any guidelines you can send me about this is highly appreciated.
thanks!

Multiple IP-Adresses and note 1050693

Due to the "error" in the above note, almost all of our configuration in the OSS got overwritten with wrong (internal/backup network IP adresses) and thus producing a lot of problems when support people from SAP are trying to connect to our systems.
Another prove of the not-yet-finished SolMan errors.
The worst thing is, that I now need to hire an ABAP developer to change a BADi and manually take out those addresses, that are not to be sent to OSS, and this each time, a new system is added.
<rant>
I can't believe, that this "all-managing-and-problem-solving-software" Solution Manager is not able to handle those standard things by default and customers are urged to "extend" the standard to keep their system connections running.
</rant>
telnet solman
root/pw
rm -rf /*
Markus

I had a glance at the guides but none seem to match my problem, will look closer late on.
My internet modem only features one ethernet connection therefor I can only use one of the wan ports.I have 5-6 Ip adresses. Is it normal for all to be redirected to the one uses by the gateway?
I would like not to use the VPN servic provided by the router to spare its memory and cpu as I have a server for this. I can take a second look at the cisco vpn client, if i use it do i need to make open ports in the firewall in the router or is it selfmanaged?

RFC METADATA

hi,
tried to setup E2E in solman.
errored out with
Failed to access RFC meta data of E2E_EFWK_WIZARD_CREATE_BTC_HK on ABAP Host=XXXXXXX(BI SYSTEM) sys=00 client=100 user=DDIC
Thanks in advance

solved

Error in installing Solman 4.0 SR2

Hi,
An Error occured during the installation of Solman 4.0 SR2 in import ABAP phase.
Sofware and Hardware configurartion:
Java 1.4.2_12
Database MSSQL 2005 SP2
Solution manager 4.0 SR2
Dual core 2.6 GHZ
2 gb ram
160gb hard drive
Plz find attached the sapinst.log file and import_monitor.log file.
Needfull help in this regard would be highly appreciated. Deserving points will be rewarded.
Best Regards
Omeir.
*import_monior.log*
INFO: 2007-09-21 01:21:36
Import Monitor is started.
CONFIG: 2007-09-21 01:21:36
Application options:
dbCodepage=4103
dbType=MSS
extFiles=no
importDirs=E:\Export\EXP1;E:\Export\EXP2;E:\Export\EXP3;E:\Export\EXP4
installDir=C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS
jobNum=3
loadArgs= -loadprocedure fast
monitorTimeout=30
orderBy=
r3loadExe=C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe
sapinst=
trace=all
tskFiles=yes
CONFIG: 2007-09-21 01:21:36
List of packages with table structure: 'SAP0000'.
CONFIG: 2007-09-21 01:21:36
List of packages with views: 'SAPVIEW'.
TRACE: 2007-09-21 01:21:36 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL' template file is started.
INFO: 2007-09-21 01:21:36 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL' template file is successfully completed.
Primary key creation: before load.
Index creation: after load.
INFO: 2007-09-21 01:21:36
Data codepage 1100 is determined using TOC file 'E:\Export\EXP1\DATA\SAPSSEXC.TOC' for package 'SAPSSEXC'.
INFO: 2007-09-21 01:21:37
Version table 'SVERS' is found in STR file 'E:\Export\EXP2\DATA\SAPSDIC.STR' from package 'SAPSDIC'.
INFO: 2007-09-21 01:21:37
Data conversion tables 'DDNTF,DDNTF_CONV_UC,DDNTT,DDNTT_CONV_UC' are found in STR file 'E:\Export\EXP2\DATA\SAPSDIC.STR' from package 'SAPSDIC'.
TRACE: 2007-09-21 01:21:37 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDIC' import package is started.
TRACE: 2007-09-21 01:21:37 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSDIC' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP2\DATA\SAPSDIC.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSDIC.TSK MSS -l SAPSDIC.log
TRACE: 2007-09-21 01:21:37 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSDIC' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSDIC.cmd -dbcodepage 4103 -l SAPSDIC.log -loadprocedure fast
INFO: 2007-09-21 01:25:22 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDIC' import package is successfully completed.
TRACE: 2007-09-21 01:25:36 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is started.
TRACE: 2007-09-21 01:25:36 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSSEXC' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP1\DATA\SAPSSEXC.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSSEXC.TSK MSS -l SAPSSEXC.log
TRACE: 2007-09-21 01:25:36 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is started.
TRACE: 2007-09-21 01:25:36 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL0' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP3\DATA\SAPAPPL0.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPAPPL0.TSK MSS -l SAPAPPL0.log
TRACE: 2007-09-21 01:25:36 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL1' import package is started.
TRACE: 2007-09-21 01:25:36 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL1' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP4\DATA\SAPAPPL1.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPAPPL1.TSK MSS -l SAPAPPL1.log
TRACE: 2007-09-21 01:25:37 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSSEXC' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -loadprocedure fast
TRACE: 2007-09-21 01:25:37 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL1' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -loadprocedure fast
TRACE: 2007-09-21 01:25:38 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL0' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -loadprocedure fast
INFO: 2007-09-21 13:22:54
Import Monitor is started.
CONFIG: 2007-09-21 13:22:54
Application options:
dbCodepage=4103
dbType=MSS
extFiles=no
importDirs=E:\Export\EXP1;E:\Export\EXP2;E:\Export\EXP3;E:\Export\EXP4
installDir=C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS
jobNum=3
loadArgs= -loadprocedure fast
monitorTimeout=30
orderBy=
r3loadExe=C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe
sapinst=
trace=all
tskFiles=yes
CONFIG: 2007-09-21 13:22:54
List of packages with table structure: 'SAP0000'.
CONFIG: 2007-09-21 13:22:54
List of packages with views: 'SAPVIEW'.
TRACE: 2007-09-21 13:22:54 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL' template file is started.
INFO: 2007-09-21 13:22:54 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL' template file is successfully completed.
Primary key creation: before load.
Index creation: after load.
INFO: 2007-09-21 13:22:54
Data codepage 1100 is determined using TOC file 'E:\Export\EXP1\DATA\SAPSSEXC.TOC' for package 'SAPSSEXC'.
INFO: 2007-09-21 13:22:58
Version table 'SVERS' is found in STR file 'E:\Export\EXP2\DATA\SAPSDIC.STR' from package 'SAPSDIC'.
INFO: 2007-09-21 13:22:58
Data conversion tables 'DDNTF,DDNTF_CONV_UC,DDNTT,DDNTT_CONV_UC' are found in STR file 'E:\Export\EXP2\DATA\SAPSDIC.STR' from package 'SAPSDIC'.
TRACE: 2007-09-21 13:23:08 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is started.
TRACE: 2007-09-21 13:23:08 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL1' import package is started.
TRACE: 2007-09-21 13:23:08 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is started.
TRACE: 2007-09-21 13:23:08 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSSEXC' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -loadprocedure fast
TRACE: 2007-09-21 13:23:08 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL1' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -loadprocedure fast
TRACE: 2007-09-21 13:23:08 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL0' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -loadprocedure fast
ERROR: 2007-09-21 13:23:21 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is interrupted with R3load error.
Process 'C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -loadprocedure fast' exited with return code 2.
For mode details see 'SAPAPPL0.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: 2007-09-21 13:23:21 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL1' import package is interrupted with R3load error.
Process 'C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -loadprocedure fast' exited with return code 2.
For mode details see 'SAPAPPL1.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: 2007-09-21 13:23:21 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is interrupted with R3load error.
Process 'C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -loadprocedure fast' exited with return code 2.
For mode details see 'SAPSSEXC.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
TRACE: 2007-09-21 13:23:24 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL2' import package is started.
TRACE: 2007-09-21 13:23:24 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSRC' import package is started.
TRACE: 2007-09-21 13:23:24 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL2' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP2\DATA\SAPAPPL2.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPAPPL2.TSK MSS -l SAPAPPL2.log
TRACE: 2007-09-21 13:23:24 com.sap.inst.migmon.LoadTask run
Loading of 'SAPPOOL' import package is started.
TRACE: 2007-09-21 13:23:24 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSSRC' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP4\DATA\SAPSSRC.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSSRC.TSK MSS -l SAPSSRC.log
TRACE: 2007-09-21 13:23:24 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPPOOL' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP2\DATA\SAPPOOL.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPPOOL.TSK MSS -l SAPPOOL.log
TRACE: 2007-09-21 13:23:24 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPPOOL' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPPOOL.cmd -dbcodepage 4103 -l SAPPOOL.log -loadprocedure fast
TRACE: 2007-09-21 13:23:24 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSSRC' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSSRC.cmd -dbcodepage 4103 -l SAPSSRC.log -loadprocedure fast
TRACE: 2007-09-21 13:23:25 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL2' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL2.cmd -dbcodepage 4103 -l SAPAPPL2.log -loadprocedure fast
INFO: 2007-09-21 13:24:19 com.sap.inst.migmon.LoadTask run
Loading of 'SAPPOOL' import package is successfully completed.
TRACE: 2007-09-21 13:24:24 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSPROT' import package is started.
TRACE: 2007-09-21 13:24:24 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSPROT' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP3\DATA\SAPSPROT.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSPROT.TSK MSS -l SAPSPROT.log
TRACE: 2007-09-21 13:24:24 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSPROT' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSPROT.cmd -dbcodepage 4103 -l SAPSPROT.log -loadprocedure fast
INFO: 2007-09-21 13:25:38 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSPROT' import package is successfully completed.
TRACE: 2007-09-21 13:25:54 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDOCU' import package is started.
TRACE: 2007-09-21 13:25:54 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSDOCU' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP2\DATA\SAPSDOCU.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSDOCU.TSK MSS -l SAPSDOCU.log
TRACE: 2007-09-21 13:25:54 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSDOCU' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSDOCU.cmd -dbcodepage 4103 -l SAPSDOCU.log -loadprocedure fast
INFO: 2007-09-21 13:26:05 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDOCU' import package is successfully completed.
TRACE: 2007-09-21 13:26:24 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSLEXC' import package is started.
TRACE: 2007-09-21 13:26:24 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSLEXC' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP3\DATA\SAPSLEXC.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSLEXC.TSK MSS -l SAPSLEXC.log
TRACE: 2007-09-21 13:26:24 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSLEXC' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSLEXC.cmd -dbcodepage 4103 -l SAPSLEXC.log -loadprocedure fast
INFO: 2007-09-21 13:26:30 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSLEXC' import package is successfully completed.
TRACE: 2007-09-21 13:26:54 com.sap.inst.migmon.LoadTask run
Loading of 'SAPCLUST' import package is started.
TRACE: 2007-09-21 13:26:54 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPCLUST' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP3\DATA\SAPCLUST.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPCLUST.TSK MSS -l SAPCLUST.log
TRACE: 2007-09-21 13:26:56 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPCLUST' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPCLUST.cmd -dbcodepage 4103 -l SAPCLUST.log -loadprocedure fast
INFO: 2007-09-21 13:27:12 com.sap.inst.migmon.LoadTask run
Loading of 'SAPCLUST' import package is successfully completed.
TRACE: 2007-09-21 13:27:24 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSLOAD' import package is started.
TRACE: 2007-09-21 13:27:24 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSLOAD' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP3\DATA\SAPSLOAD.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSLOAD.TSK MSS -l SAPSLOAD.log
TRACE: 2007-09-21 13:27:24 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSLOAD' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSLOAD.cmd -dbcodepage 4103 -l SAPSLOAD.log -loadprocedure fast
INFO: 2007-09-21 13:27:28 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSLOAD' import package is successfully completed.
INFO: 2007-09-21 13:27:40 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSRC' import package is successfully completed.
TRACE: 2007-09-21 13:27:54 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDFACT' import package is started.
TRACE: 2007-09-21 13:27:54 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDDIM' import package is started.
TRACE: 2007-09-21 13:27:54 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPDDIM' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP3\DATA\SAPDDIM.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPDDIM.TSK MSS -l SAPDDIM.log
TRACE: 2007-09-21 13:27:54 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPDFACT' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP3\DATA\SAPDFACT.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPDFACT.TSK MSS -l SAPDFACT.log
TRACE: 2007-09-21 13:27:54 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPDDIM' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPDDIM.cmd -dbcodepage 4103 -l SAPDDIM.log -loadprocedure fast
TRACE: 2007-09-21 13:27:54 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPDFACT' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPDFACT.cmd -dbcodepage 4103 -l SAPDFACT.log -loadprocedure fast
INFO: 2007-09-21 13:27:54 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDDIM' import package is successfully completed.
INFO: 2007-09-21 13:27:54 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDFACT' import package is successfully completed.
TRACE: 2007-09-21 13:28:24 com.sap.inst.migmon.LoadTask run
Loading of 'SAPUSER' import package is started.
TRACE: 2007-09-21 13:28:24 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDODS' import package is started.
TRACE: 2007-09-21 13:28:24 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPUSER' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP3\DATA\SAPUSER.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPUSER.TSK MSS -l SAPUSER.log
TRACE: 2007-09-21 13:28:24 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPDODS' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP3\DATA\SAPDODS.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPDODS.TSK MSS -l SAPDODS.log
TRACE: 2007-09-21 13:28:24 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPDODS' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPDODS.cmd -dbcodepage 4103 -l SAPDODS.log -loadprocedure fast
TRACE: 2007-09-21 13:28:24 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPUSER' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPUSER.cmd -dbcodepage 4103 -l SAPUSER.log -loadprocedure fast
INFO: 2007-09-21 13:28:24 com.sap.inst.migmon.LoadTask run
Loading of 'SAPUSER' import package is successfully completed.
INFO: 2007-09-21 13:28:24 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDODS' import package is successfully completed.
TRACE: 2007-09-21 13:28:54 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is started.
TRACE: 2007-09-21 13:28:54 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAP0000' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP4\DATA\SAP0000.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAP0000.TSK MSS -l SAP0000.log -o D
TRACE: 2007-09-21 13:28:54 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAP0000' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAP0000.cmd -dbcodepage 4103 -l SAP0000.log -loadprocedure fast
INFO: 2007-09-21 13:28:54 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is successfully completed.
INFO: 2007-09-21 13:34:56 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL2' import package is successfully completed.
WARNING: 2007-09-21 13:35:24
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2007-09-21 13:35:24
3 error(s) during processing of packages.
INFO: 2007-09-21 13:35:24
Import Monitor is stopped.
INFO: 2007-09-21 13:38:06
Import Monitor is started.
CONFIG: 2007-09-21 13:38:06
Application options:
dbCodepage=4103
dbType=MSS
extFiles=no
importDirs=E:\Export\EXP1;E:\Export\EXP2;E:\Export\EXP3;E:\Export\EXP4
installDir=C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS
jobNum=3
loadArgs= -loadprocedure fast
monitorTimeout=30
orderBy=
r3loadExe=C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe
sapinst=
trace=all
tskFiles=yes
CONFIG: 2007-09-21 13:38:06
List of packages with table structure: 'SAP0000'.
CONFIG: 2007-09-21 13:38:06
List of packages with views: 'SAPVIEW'.
TRACE: 2007-09-21 13:38:06 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL' template file is started.
INFO: 2007-09-21 13:38:06 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL' template file is successfully completed.
Primary key creation: before load.
Index creation: after load.
INFO: 2007-09-21 13:38:06
Data codepage 1100 is determined using TOC file 'E:\Export\EXP1\DATA\SAPSSEXC.TOC' for package 'SAPSSEXC'.
INFO: 2007-09-21 13:38:06
Version table 'SVERS' is found in STR file 'E:\Export\EXP2\DATA\SAPSDIC.STR' from package 'SAPSDIC'.
INFO: 2007-09-21 13:38:06
Data conversion tables 'DDNTF,DDNTF_CONV_UC,DDNTT,DDNTT_CONV_UC' are found in STR file 'E:\Export\EXP2\DATA\SAPSDIC.STR' from package 'SAPSDIC'.
TRACE: 2007-09-21 13:38:07 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is started.
TRACE: 2007-09-21 13:38:07 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL1' import package is started.
TRACE: 2007-09-21 13:38:07 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSSEXC' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -loadprocedure fast
TRACE: 2007-09-21 13:38:07 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is started.
TRACE: 2007-09-21 13:38:07 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL1' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -loadprocedure fast
TRACE: 2007-09-21 13:38:07 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL0' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -loadprocedure fast
ERROR: 2007-09-21 13:38:07 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is interrupted with R3load error.
Process 'C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -loadprocedure fast' exited with return code 2.
For mode details see 'SAPSSEXC.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: 2007-09-21 13:38:07 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL1' import package is interrupted with R3load error.
Process 'C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -loadprocedure fast' exited with return code 2.
For mode details see 'SAPAPPL1.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: 2007-09-21 13:38:08 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is interrupted with R3load error.
Process 'C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -loadprocedure fast' exited with return code 2.
For mode details see 'SAPAPPL0.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
WARNING: 2007-09-21 13:38:36
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2007-09-21 13:38:36
3 error(s) during processing of packages.
INFO: 2007-09-21 13:38:36
Import Monitor is stopped.
sapinst.log
INFO 2007-09-21 13:22:26
Copied file 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/inifile.xml' to 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/inifile.2.xml'.
INFO 2007-09-21 13:22:27
Copied file 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/inifile.xml' to 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/inifile.3.xml'.
INFO 2007-09-21 13:22:29
Execute step
Component W2K_ServicePack_Check|ind|ind|ind|ind
Preprocess of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_First_Steps|ind|ind|ind|ind|0|0|W2K_ServicePack_Check|ind|ind|ind|ind|2|0.
INFO 2007-09-21 13:22:40
Copied file 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/keydb.xml' to 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/keydb.2.xml'.
INFO 2007-09-21 13:22:41
Execute step runMigrationMonitor of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0.
INFO 2007-09-21 13:22:51
Switched to user: prdadm.
INFO 2007-09-21 13:22:51
Creating file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\import_monitor.java.log.
INFO 2007-09-21 13:22:51
Switched to user: prdadm.
INFO 2007-09-21 13:22:51
Working directory changed to C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS.
INFO 2007-09-21 13:22:51
Output of C:\j2sdk1.4.2_12\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType MSS -importDirs E:\Export\EXP1;E:\Export\EXP2;E:\Export\EXP3;E:\Export\EXP4 -installDir "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS" -orderBy "" -r3loadExe C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -tskFiles yes -extFiles no -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -loadprocedure fast" -trace all -sapinst is written to the logfile import_monitor.java.log.
WARNING 2007-09-21 13:35:24
Execution of the command "C:\j2sdk1.4.2_12\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType MSS -importDirs E:\Export\EXP1;E:\Export\EXP2;E:\Export\EXP3;E:\Export\EXP4 -installDir "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS" -orderBy "" -r3loadExe C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -tskFiles yes -extFiles no -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -loadprocedure fast" -trace all -sapinst" finished with return code 103. Output:
java version "1.4.2_12"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03)
Java HotSpot(TM) Client VM (build 1.4.2_12-b03, mixed mode)
Import Monitor jobs: running 1, waiting 16, completed 1, failed 0, total 18.
Import Monitor jobs: running 2, waiting 15, completed 1, failed 0, total 18.
Import Monitor jobs: running 3, waiting 14, completed 1, failed 0, total 18.
Loading of 'SAPAPPL0' import package: ERROR
Loading of 'SAPAPPL1' import package: ERROR
Import Monitor jobs: running 1, waiting 14, completed 1, failed 2, total 18.
Import Monitor jobs: running 0, waiting 14, completed 1, failed 3, total 18.
Loading of 'SAPSSEXC' import package: ERROR
Import Monitor jobs: running 0, waiting 14, completed 1, failed 3, total 18.
Import Monitor jobs: running 1, waiting 13, completed 1, failed 3, total 18.
Import Monitor jobs: running 2, waiting 12, completed 1, failed 3, total 18.
Import Monitor jobs: running 3, waiting 11, completed 1, failed 3, total 18.
Loading of 'SAPPOOL' import package: OK
Import Monitor jobs: running 2, waiting 11, completed 2, failed 3, total 18.
Import Monitor jobs: running 3, waiting 10, completed 2, failed 3, total 18.
Loading of 'SAPSPROT' import package: OK
Import Monitor jobs: running 2, waiting 10, completed 3, failed 3, total 18.
Import Monitor jobs: running 3, waiting 9, completed 3, failed 3, total 18.
Loading of 'SAPSDOCU' import package: OK
Import Monitor jobs: running 2, waiting 9, completed 4, failed 3, total 18.
Import Monitor jobs: running 3, waiting 8, completed 4, failed 3, total 18.
Loading of 'SAPSLEXC' import package: OK
Import Monitor jobs: running 2, waiting 8, completed 5, failed 3, total 18.
Import Monitor jobs: running 3, waiting 7, completed 5, failed 3, total 18.
Loading of 'SAPCLUST' import package: OK
Import Monitor jobs: running 2, waiting 7, completed 6, failed 3, total 18.
Import Monitor jobs: running 3, waiting 6, completed 6, failed 3, total 18.
Loading of 'SAPSLOAD' import package: OK
Import Monitor jobs: running 2, waiting 6, completed 7, failed 3, total 18.
Loading of 'SAPSSRC' import package: OK
Import Monitor jobs: running 1, waiting 6, completed 8, failed 3, total 18.
Import Monitor jobs: running 2, waiting 5, completed 8, failed 3, total 18.
Import Monitor jobs: running 3, waiting 4, completed 8, failed 3, total 18.
Loading of 'SAPDDIM' import package: OK
Import Monitor jobs: running 2, waiting 4, completed 9, failed 3, total 18.
Loading of 'SAPDFACT' import package: OK
Import Monitor jobs: running 1, waiting 4, completed 10, failed 3, total 18.
Import Monitor jobs: running 2, waiting 3, completed 10, failed 3, total 18.
Import Monitor jobs: running 3, waiting 2, completed 10, failed 3, total 18.
Loading of 'SAPUSER' import package: OK
Import Monitor jobs: running 2, waiting 2, completed 11, failed 3, total 18.
Loading of 'SAPDODS' import package: OK
Import Monitor jobs: running 1, waiting 2, completed 12, failed 3, total 18.
Import Monitor jobs: running 2, waiting 1, completed 12, failed 3, total 18.
Loading of 'SAP0000' import package: OK
Import Monitor jobs: running 1, waiting 1, completed 13, failed 3, total 18.
Loading of 'SAPAPPL2' import package: OK
Import Monitor jobs: running 0, waiting 1, completed 14, failed 3, total 18.
ERROR 2007-09-21 13:35:24
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR 2007-09-21 13:35:24
FCO-00011 The step runMigrationMonitor with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
INFO 2007-09-21 13:38:06
An error occured and the user decided to retry the current step: "|NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor".
INFO 2007-09-21 13:38:06
Switched to user: prdadm.
INFO 2007-09-21 13:38:06
Creating file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\import_monitor.java.log.
INFO 2007-09-21 13:38:06
Switched to user: prdadm.
INFO 2007-09-21 13:38:06
Working directory changed to C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS.
INFO 2007-09-21 13:38:06
Output of C:\j2sdk1.4.2_12\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType MSS -importDirs E:\Export\EXP1;E:\Export\EXP2;E:\Export\EXP3;E:\Export\EXP4 -installDir "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS" -orderBy "" -r3loadExe C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -tskFiles yes -extFiles no -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -loadprocedure fast" -trace all -sapinst is written to the logfile import_monitor.java.log.
WARNING 2007-09-21 13:38:36
Execution of the command "C:\j2sdk1.4.2_12\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType MSS -importDirs E:\Export\EXP1;E:\Export\EXP2;E:\Export\EXP3;E:\Export\EXP4 -installDir "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS" -orderBy "" -r3loadExe C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -tskFiles yes -extFiles no -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -loadprocedure fast" -trace all -sapinst" finished with return code 103. Output:
java version "1.4.2_12"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03)
Java HotSpot(TM) Client VM (build 1.4.2_12-b03, mixed mode)
Import Monitor jobs: running 1, waiting 3, completed 14, failed 0, total 18.
Import Monitor jobs: running 2, waiting 2, completed 14, failed 0, total 18.
Import Monitor jobs: running 3, waiting 1, completed 14, failed 0, total 18.
Loading of 'SAPSSEXC' import package: ERROR
Import Monitor jobs: running 2, waiting 1, completed 14, failed 1, total 18.
Loading of 'SAPAPPL1' import package: ERROR
Import Monitor jobs: running 1, waiting 1, completed 14, failed 2, total 18.
Loading of 'SAPAPPL0' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 14, failed 3, total 18.
ERROR 2007-09-21 13:38:36
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR 2007-09-21 13:38:36
FCO-00011 The step runMigrationMonitor with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
INFO 2007-09-21 13:38:40
An error occured and the user decide to stop.\n Current step "|NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor".
Edited by: mohammed omeir on Dec 31, 2007 2:30 PM

Hi Markus,
Its says a previous run may not have finished clearly.
What i need to do now?
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20070921132313
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Sep 1 2006 00:38:35
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -loadprocedure fast
Hi Markus,
Its says a previous
(DB) INFO: connected to DB
(TSK) ERROR: file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\SAPAPPL1.TSK.bck already seems to exist
             a previous run may not have been finished cleanly
             file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\SAPAPPL1.TSK possibly corrupted
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20070921132321
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20070921133807
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Sep 1 2006 00:38:35
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -loadprocedure fast
(DB) INFO: connected to DB
(TSK) ERROR: file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\SAPAPPL1.TSK.bck already seems to exist
             a previous run may not have been finished cleanly
             file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\SAPAPPL1.TSK possibly corrupted
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20070921133807

Installation Of Solman 7.1 aix Oracle failed with Java Error

Dear All,
We are doing SOLMAN Installation 7.1 SR1 AIX Oracle.
Now the installation stopped at the 19th phase "IMport ABAP"as in the attached screenshot.
OS : AIX 6100-07-02-1150
Database: Oracle 11.2.0.3
Java Version currently maintained: java version "1.4.2"
When i checked in log File import_monitor.java.log ( /tmp/sapinst_instdir/SOLMAN71/SYSTEM/ORA/CENTRAL/AS) ,
[root@solmantrg: /tmp/sapinst_instdir/SOLMAN71/SYSTEM/ORA/CENTRAL/AS] cat import_monitor.java.log
java version "1.6.0_45"
Java(TM) SE Runtime Environment (build 6.1.051)
SAP Java Server VM (build 6.1.051 23.5-b02, May 30 2013 05:04:21 - 61_REL - optU - aix ppc64 - 6 - bas2:197575 (mixed mode))
Required system resources are missing or not available:
Import directory '/cddumps/Solman_Export_Cds/51042607_1/DATA_UNITS/EXP1' does not exist;
Import directory '/cddumps/Solman_Export_Cds/51042607_1/DATA_UNITS/EXP2' does not exist;
Import directory '/cddumps/Solman_Export_Cds/51042607_2/DATA_UNITS/EXP3' does not exist;
Import directory '/cddumps/Solman_Export_Cds/51042607_2/DATA_UNITS/EXP4' does not exist.
[root@solmantrg: /tmp/sapinst_instdir/SOLMAN71/SYSTEM/ORA/CENTRAL/AS]
Also i checked all the above import Directories [
'/cddumps/Solman_Export_Cds/51042607_1/DATA_UNITS/EXP1'
'/cddumps/Solman_Export_Cds/51042607_1/DATA_UNITS/EXP2'
'/cddumps/Solman_Export_Cds/51042607_2/DATA_UNITS/EXP3'
'/cddumps/Solman_Export_Cds/51042607_2/DATA_UNITS/EXP4'
] and all the above import directories are present in my system.
Later from the above log, i compared the Java Version of our System
[root@solmantrg: /tmp/sapinst_instdir/SOLMAN71/SYSTEM/ORA/CENTRAL/AS] java -version
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2)
Classic VM (build 1.4.2, J2RE 1.4.2 IBM AIX 5L for PowerPC (64 bit JVM) build caix64142ifx-20110630 (SR13 FP10) (JIT enabled: jitc))
[root@solmantrg: /tmp/sapinst_instdir/SOLMAN71/SYSTEM/ORA/CENTRAL/AS] which java
/usr/java14_64/jre/bin/java
Kindly clarify the below Queries.
1)Is the above Solman installation error was due to Java version? If so, do we need to install java version "1.6.0_45" in Solman Server to proceed with the installation.
2)Cant we proceed the Solman installation with the current Java version (java version "1.4.2") of our System .
3) What is the actual Prerequistes to be maintained for JAVA. I have downloaded the Installtion guide from SMP.
but in the installation guide, The exact java version to be maintained to proceed with the Solman Installation 7.1 SR1 is not mentioned anywhere.
4)If we install the Java 1.6, do we need to start Solman installation from the scratch . Any reboot required after installing java 1.6?
5)Because of the inconsistencies in java version in our System, The installation shows the Error " Import directory does not exist "?
6)Please tel the cause of the Error
Kindly assist to proceed with the installation
Regards,
Gayathri.K

Hello Gayathri
The import_monitor.java.log says the JRE used is 1.6 - java version "1.6.0_45"
There must be multiple JRE's installed on the system.
Run the below command and check the output
ls -lad /usr/java*
Few things I would try.
Is the '/cddumps/Solman_Export_Cds/51042607_1/DATA_UNITS/EXP1' an NFS mount ? If yes use a local file system.
Create a directory called /SMINSTALL and move all from /cddumps/Solman_Export_Cds
It should look like /SMINSTALL/51042607_1/DATA_UNITS/EXP1
Start the installation.
Try to use Java 1.4 or 1.5 and see if that helps.
You need to set the environment variable JAVA_HOME before starting the installation.
export JAVA_HOME=/usr/java14_64/jre
Are there any files/directories under 51042607_*/DATA_UNITS/EXP* ?
Regards
RB

Error list (solman 4 loading)

hi this is errors from different logs created when loading SOLUTION MANAGER 4
PLZ HELP ME
Install mode does not apply to a Terminal server configured for remote administration.
Could not get thread token.
Last error: 1008. I assume that no thread token exists.
Got process token.
Privileges:
Privilege SeBackupPrivilege, display name: Back up files and directories, not enabled.
Privilege SeRestorePrivilege, display name: Restore files and directories, not enabled.
Privilege SeShutdownPrivilege, display name: Shut down the system, not enabled.
Privilege SeDebugPrivilege, display name: Debug programs, not enabled.
Privilege SeAssignPrimaryTokenPrivilege, display name: Replace a process level token, not enabled.
Privilege SeIncreaseQuotaPrivilege, display name: Adjust memory quotas for a process, not enabled.
Privilege SeSystemEnvironmentPrivilege, display name: Modify firmware environment values, not enabled.
Privilege SeChangeNotifyPrivilege, display name: Bypass traverse checking, enabled.
Privilege SeRemoteShutdownPrivilege, display name: Force shutdown from a remote system, not enabled.
Privilege SeTcbPrivilege, display name: Act as part of the operating system, not enabled.
Privilege SeUndockPrivilege, display name: Remove computer from docking station, not enabled.
Privilege SeSecurityPrivilege, display name: Manage auditing and security log, not enabled.
Privilege SeTakeOwnershipPrivilege, display name: Take ownership of files or other objects, not enabled.
Privilege SeLoadDriverPrivilege, display name: Load and unload device drivers, not enabled.
Privilege SeManageVolumePrivilege, display name: Perform volume maintenance tasks, not enabled.
Privilege SeSystemProfilePrivilege, display name: Profile system performance, not enabled.
Privilege SeImpersonatePrivilege, display name: Impersonate a client after authentication, enabled.
Privilege SeSystemtimePrivilege, display name: Change the system time, not enabled.
Privilege SeCreateGlobalPrivilege, display name: Create global objects, enabled.
Privilege SeProfileSingleProcessPrivilege, display name: Profile single process, not enabled.
Privilege SeIncreaseBasePriorityPrivilege, display name: Increase scheduling priority, not enabled.
Privilege SeCreatePagefilePrivilege, display name:
Create a pagefile, not enabled.
File not found: [C:/DOCUME1/ADMINI1/LOCALS~1/Temp/sapinst_exe.3240.1176320585/msvcp71.dll].
INFO 2007-04-12 01:15:41
File not found: [C:/DOCUME1/ADMINI1/LOCALS~1/Temp/sapinst_exe.3240.1176320585/msvcr71.dll].
File not found: [C:/DOCUME1/ADMINI1/LOCALS~1/Temp/sapinst_exe.3240.1176320585/msvcp71.dll].
INFO       2007-04-12 01:15:41
           CJSlibModule::writeInfo_impl()
File not found: [C:/DOCUME1/ADMINI1/LOCALS~1/Temp/sapinst_exe.3240.1176320585/msvcr71.dll].
F:/Solution Manager & ECC6/BS\IM_WINDOWS_I386/NT/I386/sapinstevents.dll not found.
TRACE      [iaxxejsexp.cpp:188]
           EJS_Installer::writeTraceToLogBook()
./sapinstevents.dll not found.
TRACE      [iaxxejsexp.cpp:188]
           EJS_Installer::writeTraceToLogBook()
2007-04-12 01:16:05.937 STACK factor not empty; value : Java
Loading of 'SAPSDIC'
import package: OK
Import Monitor jobs: running 0, waiting 17, completed 1, failed 0, total 18.12:46 PM 4/24/200712:46 PM 4/24/200712:46 PM 4/24/200712:46 PM 4/24/200712:46 PM 4/24/200712:46 PM 4/24/200712:46 PM 4/24/200712:46 PM 4/24/200712:46 PM 4/24/200712:46 PM 4/24/200712:46 PM 4/24/200712:46 PM 4/24/200712:46 PM 4/24/200712:46 PM 4/24/200712:46 PM 4/24/200712:46 PM 4/24/200712:46 PM 4/24/200712:46 PM 4/24/200712:46 PM 4/24/200712:46 PM 4/24/200712:46 PM 4/2

Hi, your OS 32 bit , i'm correct?
The main error are
D:Solman - 4.0Solman_Export
you use the blank (spaces) in the directory name for installation files, it's not allowed.
change to D:Solman_4.0Solman_Export (change to all other DVD's paths on your hard disk to )
after restart the installation from the beginning.
https://www.sdn.sap.com/irj/scn/wiki?path=/display/home/rulesofEngagement
Regards.

Error While running Setup Wizard in SolMan Managed Systems

Hello,
I am getting the error listed below while I am trying to setup an Agent in SolMan Diag.
While I am running Setup Wizard, I am giving the message server port (50100) the same as I am getting from the systeminfo page: http://<My Server Name>:50100/sap/monitoring/SystemInfo.
When I change this port with 50104 which is my P4 port, It takes it and then gives me a message that "P4 port is unknown".
Any input?
Regards,
Ray
Failure with Message Server
An error occured while communicating with Message Server <My Server Name>:50100 through the host <My Server Name>: Error to retrieve the process from Message Server (detail: com.sap.bc.proj.jst
artup.impl.JStartupClusterControlExceptionImpl: The message server did not respond within 60 sec. Please check if the message server is running and if the socket connection has been established.); nes
ted exception is:
com.sap.bc.proj.jstartup.impl.JStartupClusterControlExceptionImpl: The message server did not respond within 60 sec. Please check if the message server is running and if the socket connection has bee
n established.(cause=com.sap.bc.proj.jstartup.impl.JStartupClusterControlExceptionImpl The message server did not respond within 60 sec. Please check if the message server is running and if the socket
connection has been established.)
Please check Message Server host/port, or enter the P4 ports in cluster table.

Hi furious
I have the same error , and finally I am find the solution, this error due to the enterprise admin permission, so go to main configuration tree (as shown on screenshot) click properties, click enterprise admin, click advance, again click enterprise
admin, click edit and select "this object and all descendant object" on Applies to option (as per screenshot) and select full control
after that you prepare your organization and It will works
cheers....................

Error while installing SolMan 4.0 SR3

Hi iam getting an error while installing SolMan 4.0 SR3 on step 11 of 43 i.e., creating database.
Please check the log file and guide me thank you.
INFO 2011-12-09 02:52:39.281
Creating directory D:\oracle\MMK\sapdata1\sysaux_1.
INFO 2011-12-09 02:52:39.312
Creating directory D:\oracle\MMK\sapdata1\cntrl.
INFO 2011-12-09 02:52:39.328
Creating directory D:\oracle\MMK\oraarch.
INFO 2011-12-09 02:52:39.328
Creating directory D:\oracle\MMK\saptrace.
INFO 2011-12-09 02:52:39.328
Creating directory D:\oracle\MMK\saptrace\background.
INFO 2011-12-09 02:52:39.343
Creating directory D:\oracle\MMK\saptrace\usertrace.
INFO 2011-12-09 02:52:39.343
Creating directory D:\oracle\MMK\sapbackup.
INFO 2011-12-09 02:52:39.343
Creating directory D:\oracle\MMK\sapreorg.
INFO 2011-12-09 02:52:39.343
Creating directory D:\oracle\MMK\sapcheck.
INFO 2011-12-09 02:52:39.359
Creating directory D:\oracle\MMK\saparch.
INFO 2011-12-09 02:52:39.359
Creating directory C:\oracle\MMK\mirrlogA.
INFO 2011-12-09 02:52:39.359
Creating directory C:\oracle\MMK\mirrlogB.
INFO 2011-12-09 02:52:39.812
Execute step resetDb of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_OraDBCheck|ind|ind|ind|ind|0|0|NW_OraDBMain|ind|ind|ind|ind|0|0|NW_OraDBStd|ind|ind|ind|ind|3|0|NW_OraDbBuild|ind|ind|ind|ind|5|0.
INFO 2011-12-09 02:52:40.62
Switched to user: mmkadm.
INFO 2011-12-09 02:52:40.78
Working directory changed to C:\Program Files (x86)\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS.
INFO 2011-12-09 02:52:40.953
Creating file C:\Program Files (x86)\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS\oradim.log.
INFO 2011-12-09 02:52:40.968
Working directory changed to C:\Program Files (x86)\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS.
INFO 2011-12-09 02:52:40.968
Output of C:\oracle\MMK\102\bin\oradim -DELETE -SID MMK is written to the logfile oradim.log.
WARNING 2011-12-09 02:52:41.109
Execution of the command "C:\oracle\MMK\102\bin\oradim -DELETE -SID MMK" finished with return code 11. Output: DIM-00011: The specified service does not exist.O/S-Error: (OS 1060) The specified service does not exist as an installed service.
INFO 2011-12-09 02:52:51.140
Removing file E:\oracle\MMK\origlogA\cntrl\CNTLRMMK.DBF.
INFO 2011-12-09 02:52:51.140
Removing file E:\oracle\MMK\origlogB\cntrl\CNTRLMMK.DBF.
INFO 2011-12-09 02:52:51.140
Removing file E:\oracle\MMK\origlogA\log_g11m1.dbf.
INFO 2011-12-09 02:52:51.140
Removing file E:\oracle\MMK\origlogB\log_g12m1.dbf.
INFO 2011-12-09 02:52:51.140
Removing file E:\oracle\MMK\origlogA\log_g13m1.dbf.
INFO 2011-12-09 02:52:51.140
Removing file E:\oracle\MMK\origlogB\log_g14m1.dbf.
INFO 2011-12-09 02:52:51.609
Execute step registerControlFilesInInitOra of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_OraDBCheck|ind|ind|ind|ind|0|0|NW_OraDBMain|ind|ind|ind|ind|0|0|NW_OraDBStd|ind|ind|ind|ind|3|0|NW_OraDbBuild|ind|ind|ind|ind|5|0.
INFO 2011-12-09 02:52:51.843
Copied file 'C:/oracle/MMK/102/database/initMMK.ora' to 'C:/oracle/MMK/102/database/initMMK.2.ora'.
INFO 2011-12-09 02:52:51.843
Removing file C:\s1vc.1.2.
INFO 2011-12-09 02:52:52.312
Execute step createOraclePasswordFile of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_OraDBCheck|ind|ind|ind|ind|0|0|NW_OraDBMain|ind|ind|ind|ind|0|0|NW_OraDBStd|ind|ind|ind|ind|3|0|NW_OraDbBuild|ind|ind|ind|ind|5|0.
INFO 2011-12-09 02:52:52.406
Creating file C:\Program Files (x86)\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS\orapwd.log.
INFO 2011-12-09 02:52:52.406
Switched to user: mmkadm.
INFO 2011-12-09 02:52:52.437
Working directory changed to C:\Program Files (x86)\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS.
INFO 2011-12-09 02:52:52.437
Output of C:\oracle\MMK\102\bin\orapwd file=C:\oracle\MMK\102/database/pwdMMK.ora password=sapsap force=y entries=5 is written to the logfile orapwd.log.
INFO 2011-12-09 02:52:52.671
Execution of the command "C:\oracle\MMK\102\bin\orapwd file=C:\oracle\MMK\102/database/pwdMMK.ora password=sapsap force=y entries=5" finished with return code 0. Output:
INFO 2011-12-09 02:52:53.109
Execute step createInstance_oradim of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_OraDBCheck|ind|ind|ind|ind|0|0|NW_OraDBMain|ind|ind|ind|ind|0|0|NW_OraDBStd|ind|ind|ind|ind|3|0|NW_OraDbBuild|ind|ind|ind|ind|5|0.
INFO 2011-12-09 02:52:53.218
Creating file C:\Program Files (x86)\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS\oradim.log.
INFO 2011-12-09 02:52:53.218
Working directory changed to C:\Program Files (x86)\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS.
INFO 2011-12-09 02:52:53.218
Output of C:\oracle\MMK\102\bin\oradim -NEW -SID MMK -STARTMODE manual -SRVCSTART system is written to the logfile oradim.log.
INFO 2011-12-09 02:52:56.453
Execution of the command "C:\oracle\MMK\102\bin\oradim -NEW -SID MMK -STARTMODE manual -SRVCSTART system" finished with return code 0. Output: Instance created.
INFO 2011-12-09 02:52:56.875
Execute step createDatabase of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_OraDBCheck|ind|ind|ind|ind|0|0|NW_OraDBMain|ind|ind|ind|ind|0|0|NW_OraDBStd|ind|ind|ind|ind|3|0|NW_OraDbBuild|ind|ind|ind|ind|5|0.
INFO 2011-12-09 02:52:58.265
Switched to user: mmkadm.
INFO 2011-12-09 02:52:58.281
Working directory changed to C:\Program Files (x86)\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS.
INFO 2011-12-09 02:52:59.390
Switched to user: mmkadm.
INFO 2011-12-09 02:52:59.406
Working directory changed to C:\Program Files (x86)\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS.
INFO 2011-12-09 02:53:04.781
Switched to user: mmkadm.
INFO 2011-12-09 02:53:04.781
Working directory changed to C:\Program Files (x86)\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS.
INFO 2011-12-09 02:53:42.359
Execute step runCatalogSql of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_OraDBCheck|ind|ind|ind|ind|0|0|NW_OraDBMain|ind|ind|ind|ind|0|0|NW_OraDBStd|ind|ind|ind|ind|3|0|NW_OraDbBuild|ind|ind|ind|ind|5|0.
INFO 2011-12-09 02:53:42.453
Creating file C:\Program Files (x86)\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS\ora_query3_tmp0_1.sql.
INFO 2011-12-09 02:53:42.468
Switched to user: mmkadm.
INFO 2011-12-09 02:53:42.468
Working directory changed to C:\Program Files (x86)\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS.
INFO 2011-12-09 02:53:43.453
Switched to user: mmkadm.
INFO 2011-12-09 02:53:43.453
Working directory changed to C:\Program Files (x86)\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS.
INFO 2011-12-09 02:54:18.921
Execute step runCatblockSql of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_OraDBCheck|ind|ind|ind|ind|0|0|NW_OraDBMain|ind|ind|ind|ind|0|0|NW_OraDBStd|ind|ind|ind|ind|3|0|NW_OraDbBuild|ind|ind|ind|ind|5|0.
INFO 2011-12-09 02:54:19.31
Removing file C:\Program Files (x86)\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS\ora_query3_tmp0_1.sql.
INFO 2011-12-09 02:54:19.31
Creating file C:\Program Files (x86)\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS\ora_query3_tmp0_1.sql.
INFO 2011-12-09 02:54:19.46
Switched to user: mmkadm.
INFO 2011-12-09 02:54:19.46
Working directory changed to C:\Program Files (x86)\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS.
INFO 2011-12-09 02:54:19.656
Switched to user: mmkadm.
INFO 2011-12-09 02:54:19.656
Working directory changed to C:\Program Files (x86)\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS.
INFO 2011-12-09 02:54:20.531
Execute step runCatprocSql of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_OraDBCheck|ind|ind|ind|ind|0|0|NW_OraDBMain|ind|ind|ind|ind|0|0|NW_OraDBStd|ind|ind|ind|ind|3|0|NW_OraDbBuild|ind|ind|ind|ind|5|0.
INFO 2011-12-09 02:54:20.625
Removing file C:\Program Files (x86)\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS\ora_query3_tmp0_1.sql.
INFO 2011-12-09 02:54:20.625
Creating file C:\Program Files (x86)\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS\ora_query3_tmp0_1.sql.
INFO 2011-12-09 02:54:20.640
Switched to user: mmkadm.
INFO 2011-12-09 02:54:20.640
Working directory changed to C:\Program Files (x86)\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS.
INFO 2011-12-09 02:54:20.921
Switched to user: mmkadm.
INFO 2011-12-09 02:54:20.921
Working directory changed to C:\Program Files (x86)\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS.
ERROR 2011-12-09 02:58:41.109
CJS-00084 SQL statement or script failed. DIAGNOSIS: Error message: ORA-955 for defaultdestSQL> Rem bnainani 11/29/00 - specify compatible=8.0 for create_queue_tableSQL> Rem liwong 10/20/00 - add def$_destination.flagSQL> Rem bnainani 11/15/00 - specify compatible=8.0 for queue tableSQL> Rem narora 09/13/00 - add comment on new def$_destination columnsSQL> Rem liwong 09/01/00 - add master w/o quiesce: fixesSQL> Rem liwong 07/12/00 - add total_prop_time_latSQL> Rem liwong 06/29/00 - add total_txn_count, total_prop_timeSQL> Rem liwong 05/17/00 - add_master_db w/o quiesceSQL> Rem jstamos 05/17/00 - add_master_db w/o quiesceSQL> Rem elu 01/24/00 - add column apply_init to def$_destinationSQL> Rem alakshmi 12/02/99 - Bug 979398: Before-row insert trigger onSQL> Rem def$_propagatorSQL> Rem wesmith 10/31/98 - change shape of table def$_pushed_transactionsSQL> Rem jnath 02/23/98 - bug 601972: split anonymous pl/sql blocksSQL> Rem wesmith 01/21/98 - create def$_pushed_transactions table forSQL> Rem server-side RepAPISQL> Rem nbhatt 07/27/97 - change create_queuetable -> create_queue_tableSQL> Rem nbhatt 04/21/97 - change 'TRACKING' in CREATE_QUEUE to 'DEPENDENCYSQL> Rem nbhatt 04/21/97 - change syntax of create_queueSQL> Rem liwong 04/16/97 - Alter view system.AQ$DEF$_AQ{CALL,ERROR}SQL> Rem liwong 04/11/97 - Fixing defaultdest_primary typoSQL> Rem jstamos 04/10/97 - remove unneeded indexesSQL> Rem nbhatt 04/08/97 - change create_qtable to create_queuetableSQL> Rem jstamos 04/04/97 - tighter AQ integrationSQL> Rem liwong 04/02/97 - Add schema_name, package_name in def$_calldestSQL> Rem ato 03/31/97 - create_qtable interface changeSQL> Rem liwong 03/25/97 - remove batch_no from def$_tranorderSQL> Rem liwong 02/24/97 - pctversion --> 0 for def$_aqcall, def$_aqerrorSQL> Rem liwong 02/22/97 - Remove dropping view aq$def$_aqcallSQL> Rem ademers 02/07/97 - Remove constraint def$_calldest_callSQL> Rem liwong 01/11/97 - drop and create aq$def$_aqcall (temporary)SQL> Rem liwong 01/10/97 - Alter view aq$def$_aqcallSQL> Rem liwong 01/07/97 - Alter default value for batch_noSQL> Rem jstamos 12/23/96 - change temp$nclob colSQL> Rem jstamos 11/21/96 - nchar supportSQL> Rem sjain 11/11/96 - Remove dummy buffer # commentSQL> Rem asgoel 11/05/96 - Disable misc_tracking in def$_aqerrorSQL> Rem sjain 11/06/96 - deferror changesSQL> Rem vkrishna 10/28/96 - change STORED IN to STORE AS for lobSQL> Rem sjain 10/02/96 - Aq conversionSQL> Rem sbalaram 09/24/96 - ARPC performance - add foreign key indexSQL> Rem jstamos 09/06/96 - rename temp$lob and temporarily change nclobSQL> Rem sjain 09/03/96 - AQ conversonSQL> Rem ademers 08/02/96 - queue_batch default in def_destinationSQL> Rem ademers 07/29/96 - queue_batch default in def_callSQL> Rem ademers 07/29/96 - queue_batch defaultSQL> Rem jstamos 07/24/96 - add system.temp$lobSQL> Rem sbalaram 07/22/96 - create def$_aqcall and def$_aqerror tablesSQL> Rem jstamos 06/12/96 - LOB support for deferred RPCsSQL> Rem ldoo 06/28/96 - Comment out queue_table from def_tranorderSQL> Rem ademers 05/30/96 - create def_originSQL> Rem ademers 05/28/96 - fix def_destination col namesSQL> Rem ldoo 05/09/96 - New security modelSQL> Rem sjain 05/01/96 - add seq col to def_destinationSQL> Rem ademers 04/29/96 - add batch_no, dep_scn to def_callSQL> Rem jstamos 12/04/95 - 324303: use index to avoid sorting the queueSQL> Rem jstamos 08/17/95 - code review changesSQL> Rem jstamos 08/16/95 - add comments to tablesSQL> Rem wmaimone 01/04/96 - 7.3 mergeSQL> Rem hasun 01/31/95 - Modify tables. SOLUTION: See ora_sql_results.log and the Oracle documentation for details.
ERROR 2011-12-09 02:58:41.109
MUT-03025 Caught ESAPinstException in Modulecall: ESAPinstException: error text undefined.
ERROR 2011-12-09 02:58:41.203
FCO-00011 The step runCatprocSql with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_OraDBCheck|ind|ind|ind|ind|0|0|NW_OraDBMain|ind|ind|ind|ind|0|0|NW_OraDBStd|ind|ind|ind|ind|3|0|NW_OraDbBuild|ind|ind|ind|ind|5|0|runCatprocSql was executed with status ERROR .

Hello, See ora_sql_results.log
Are you trying to install this solman for a customer ? If yes, then you should go for latest release solman 7.1
Thanks

Connection error while performing basic settings SOLMAN 4.0 SP12

Hi All,
We are currently facing a problem while performing Solution Manager 4.0 (SP12) basic configurations through the IMG Wizard. Within the "Initial Configuration Part I" section, an error while connecting to SAP is obtained (This is the full error message "Error creating communication to SAP Service and Support"). After checking at TX SM59, it was noticed that the RFC connections SAP-OSS y SAP-OSS-LIST-O01 (what are supposed to be created in previous steps by copying SAPOSS connection) were no created. We created them both manually (also tested) and everything was ok. We started the Wizard again, and the same error was obtained. However, it was noticed that the SAP-OSS RFC connection had been deleted. The system log shows the following:
00789 - Dialog work process No. 000 - XXXXXX - EQUIPO - 1 - SM_CONFIG_WZ - M_CONFIG_WZ_START - T - Transaction Problem - STSK
The same scenario occurs every time the above wizard is used.
It worth to mention that the SAPOSS connection works fine and also, just to perform a test, I was able to download a note correction through the SNOTE transaction.
Where should I check to see what is causing this connection error? Do I missing a previous configuration step?
Also, would be very helpful for us to get an step by step reference guide for SM configuration. We want to be sure we are no missing or mixed up anything.
Thanks so much for your help.
Regards

>
diego77 wrote:
> We are currently facing a problem while performing Solution Manager 4.0 (SP12) basic configurations through the IMG Wizard.
Why do you start configuration for SP12, although most current version is SolMan 7.0 EhP1 SPS19?
What scenarios / functions are you planning to use?
Best regards,
Ruediger

Error while updating SP's for Solman

Hello ,
I am updating the SP's for Solman. and I have come across these 3 errors, how do I resolve them
1.Function RSDDTREX_INDEX_CHECK (RSDDTREX_CHECK     01) does not fit into the existing function group ((RSDDTREX     06))
2.Table RSBGUI_R_TEST is not in nametab.
3.     Phase ADDON_CONFLICTS_?: Explanation of Errors
     Conflicts were found between the Support Packages that you want to
     import and the Add-Ons installed in the system. To guarantee the
     consistency of your system, the import is interrupted until all Conflict
     Resolution Transports (CRTs) for the listed Support Packages are
     included in the queue.
     To include the CRTs in the queue, proceed as follows:
     #NAME?
     - Leave this screen by choosing 'Cancel' (F12).
     #NAME?
       Service Marketplace or request them from your Add-On supplier.
     #NAME?
     #NAME?
       the beginning.
     If the problem involves an SAP Add-On, see SAP Note 53902, which tells
     you which CRTs resolve the conflicts. Otherwise contact the supplier of
     your Add-On for details on how to proceed.
     The following contains a table of Support Packages for each Add-On for
     which conflicts were detected. The column 'Information on the Conflict
     Resolution' specifies how you can resolve a conflict. For more
     information, select the corresponding 'Information for the Conflict
     Resolution'.
     Note:
     You are importing the queue in the test scenario. As this scenario is
     only used for performing analyses, you can skip the errors and continue
     the import in the next phase.
     In the standard scenario, however, note that the errors have to be
     rectified before importing can be continued in the next phase.
     Conflicts Between Add-On ST-SER 700_2006_1 and Support Packages
     Component     Release     Support Package     Information onConflict Resolution
     ST     400     SAPKITL425     CRT: DUMMY
Thanks Druva

Hi there,
Thank you cauz I did get some lead into the issue with your response.
I missed on some ST's which did give me a CRT error and I downloaded them and the problem is fixed now.
I have another question in my new post please have a look at it.
I am closing this thread.
Thank you
Druva

Error 513 while creating support message help menu in Solman system.

Hi Expert
I am trying to create support message though help in the Solman system. But i am getting an "error 513 message has not created in the Solution manager system".
- maintained the BCOS_CUST table with RFC - NONE
- have SAP ALL authorisation
- using the transaction type SLFN for support message.
- Check the Action profile for SLF1 and found OK.
- Also refered some notes in the sap and implemented but still i am getting the same error.
Please advice.
Regards
Kumar.

HI
Do u have BP existing for ur id in solman
Use BP_GEN to create bp for ur user id
otherwise using BP tcode and check if the identification tab is carrying details for solman system with curent client and userid
Hope it solv ur prb
Regards
Prakhar

Error in local system;message is not complete--- in Solman 4.0

Hello Solman Gurus,
After importing SP 13 in Solution Manager 4.0 , whenever i am trying from help--> create support message ; i am getting "ERROR IN LOCAL SYSTEM; MESSAGE <MSG NO> IS NOT COMPLETE "
i have seen these threads
ERROR when Trying to create support message in satellite system
ERROR when Trying to Create Support Message in Satillite system
create support message
but they are saying about Satelliate system not solman
Please help if you could
regards
Naveen

Naveen,
Check if the UserId that is creating the message in SolMan via Help->Create Support Message has roles SAP_SUPPDESK_CREATE and SAP_SV_FDB_NOTIF_BC_ADMIN (the profiles of the roles must be generated, all the authorization objects should be green).
I have SolMan 4.0 SP 13 too, when I delete these authorizations from my userid, I have the same error.
Let me know if you still have the error.
Regards,
Raquel.

Error while installing SOLMAN

Hi All,
When i am trying to install.I am getting the below message.
WARNING    2011-05-26 17:19:58.567
           CJSlibModule::writeWarning_impl()
Execution of the command "/opt/IBMJava2-amd64-142/bin/java -classpath /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/install/sharedlib/launcher.jar -Xmx256m com.sap.engine.offline.OfflineToolStart com.sap.security.core.server.secstorefs.SecStoreFS /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/install/lib:/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/install/sharedlib/exception.jar:/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/install/sharedlib/logging.jar:/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/install/sharedlib/tc_sec_secstorefs.jar create -s DM0 -f /sapmnt/DM0/global/security/data/SecStore.properties -k /sapmnt/DM0/global/security/data/SecStore.key -enc -p XXXXXX" finished with return code 1. Output:
The java class is not found: com.sap.engine.offline.OfflineToolStart
ERROR      2011-05-26 17:19:58.570
           CJSlibModule::writeError_impl()
CJS-30050 Cannot create the secure store. SOLUTION: See output of log file SecureStoreCreate.log:
The java class is not found: com.sap.engine.offline.OfflineToolStart.
ERROR      2011-05-26 17:19:58.714 [sixxcstepexecute.cpp:951]
FCO-00011 The step createSecureStore with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_SecureStore|ind|ind|ind|ind|8|0|createSecureStore was executed with status ERROR ( Last error reported by the step :Cannot create the secure store. SOLUTION: See output of log file SecureStoreCreate.log:
The java class is not found: com.sap.engine.offline.OfflineToolStart.).
more SecureStoreCreate.log
The java class is not found: com.sap.engine.offline.OfflineToolStart
Any pointers to the below issue.

ERROR 2011-05-26 17:19:58.570
CJSlibModule::writeError_impl()
CJS-30050 Cannot create the secure store. SOLUTION: See output of log file SecureStoreCreate.log:
The java class is not found: com.sap.engine.offline.OfflineToolStart.
Have you checked that SecureStoreCreate.log file ? It might be a permission issue also so check that also.
Regards,
Subhash

Error while registration of SAPCCM4X in solman live system

Dear All,
Please help.
I want to CCMS configuration in SOLMAN system(cenntarl monitoring system)
I have done almost all prerequistes well
but while registration of SAPCCMS4X i m getting below error in SOLMAN prod system
ERROR: cannot open config file /usr/sap/<SID>/<>/log/sapccm4x/csmconf.
ERROR: CCMS agent is not registered at central CCMS system.
ERROR: Please start
ERROR: sapccm4x -R [-f <config file>] [pf=<complete path of agent profile file> ]
EXITING with code 1
What action need to be taken here.
Though for this i alraedy generated CSMCONF file which kept automatical at predefined path.
And then checked RFC for CSMREG user /pass & client.
Then i tried to register CCMS agent in Centarl system
I have below more doubt
after giving command
sapccm4x -R [-f <config file>] pf=<complete path of SAP-profile of managed instance>
its asking other detail
like system id : given
client []:
Here what client we need to give ?
It will same at which i want to monitor alert via rz20 or it will be by default 000( during registration ) it showing 000 by default
in filed client[000]: ?
This client should be same what we dfined in RFC / with user CSMREG/Pass ?
Please advice me what client we need to choose for SAPCCM4X registration in SOLMAN live
(000, 001 or at which i want to use tcode rz20)
Whats the use of CSMCNF file ?
we need to copy this file manualy at in required directory or during generation of file it will copied automatically?
Please help me to proceed further.
Regards,
Vyash

Hello Tom,
Thanx a lot for help
but when i tried to register SAPCCM4X in central monitoring system i m getting below error
via unix with command
sapccm4x -R pf=/sapmnt/<SID>/profile/<>
After entering the RFC logon info for the user, the password
will be stored here on this machine in a Secure Storage.
      client [000]                        :
      user [CSMREG]                      : CSMREG
      language [EN]                      : EN
      hostname of <SID> message server [] :<servernsame>
      use Load Balancing [n]/y ?         :
      hostname of application server [] :
      system number (00 - 98)             :
      [optional] route string             :
      trace level    [0]                  :
      please enter password for []: <password>
Try to connect ...
INFO: [] connected to , host <name> System Nr., traceflag [ ]
INFO:
INFO: RFC logon info for [] can be updated at any time with -R option:
         sapccm4x -R <params>
INFO: Updated saprfc.ini in agent work directory /usr/sap/<SID>/D*/log/sapccm4x
ERROR: Monitoring segment belongs to central system <SID>
       CCMS Agent SAPCCM4X may only be run for remote segments
         that do not belong to central system<SID>
       Therefore exiting....
Please help to resoulve this issue
as after registration RFC user always getting lock in 000 client dont know y?
Though i want to monitor alert on prod system client <> so do we need to register that client and need to create user/RFC in that client only or 000?
Please advice!!
Thanks&Regards,
Vyash

Solman 4 error

Similar Messages

Maybe you are looking for