Solution Manager 4.0 Installation error on vmware

Hi guys,
I try to install the solution Manager 4.0 SR4 in a vmware server Win2003 64bit
and get the following error message in phase 17 (import ABAP)
Execution of the command "C:\j2sdk1.4.2_17-x64\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 2. Output:
java version "1.4.2_17"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_17-b06)
Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_17-b06, mixed mode)
Required system resources are missing or not available:
Import directory '
hyperv01\c$\SAPINSTALL\SAP SOLUTION MANAGER 7.0 Installation Export 1\EXP1' does not exist;
Import directory '
hyperv01\c$\SAPINSTALL\SAP SOLUTION MANAGER 7.0 Installation Export 1\EXP2' does not exist;
Import directory '
hyperv01\c$\SAPINSTALL\SAP SOLUTION MANAGER 7.0 Installation Export 2\EXP3' does not exist;
Import directory '
hyperv01\c$\SAPINSTALL\SAP SOLUTION MANAGER 7.0 Installation Export 2\EXP4' does not exist.
of course the path exists and the further dvd locations where also found?
is ther something wrong with the naming of the install dir?
must I have a character for the "harddrive"
Plse help
thank you and br
Wolfgang

Hello shareef,
there is no extra recommendation from SAP regarding SolMan on vmware.
SAP supports installations on vmware wheanwhile also for productive systems (plse check PAM).
The experience I have for my installation:
I works fine til now, no probs.
cu Wolfgang

Similar Messages

Solution manager 4.0 installation error in vmware

Hi,
I am facing following error during the Sol manager 4.0 installation.
INFO 2006-10-02 11:30:43
Disconnect from message server (sapsmdev/3951) succeeded.
ERROR 2006-10-02 11:30:47
CJS-30149 ABAP processes of instance GSM/DVEBMGS01 [ABAP: UNKNOWN] did not start after 10:00 minutes. Giving up.
ERROR 2006-10-02 11:30:47
FCO-00011 The step start with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_Start|ind|ind|ind|ind|0|0|start was executed with status ERROR .
RAM 3GB SWAP 6GB.

Pls find our default profile pasted below and let me know if anything mission or we need to change something:
SAPDBHOST = <server Name>
j2ee/dbtype = sap
j2ee/dbname = SM1
j2ee/dbhost = <server Name>
j2ee/dbadminurl = http://<server Name>:9999/webdbm?Server=<server Name>&Database=SM1&User=control
SAPSYSTEMNAME = SM1
SAPGLOBALHOST = <server Name>
SAP Central Service Instance for J2EE
j2ee/scs/host = <server Name>
j2ee/scs/system = 00
j2ee/ms/port = 3900
rdisp/bufrefmode = sendoff,exeauto
SAP Messaging Service for ABAP
rdisp/mshost = <server Name>
rdisp/msserv = sapmsSM1
rdisp/msserv_internal = 3901
SAP Central Service Instance for J2EE
SAP Messaging Service for ABAP
login/system_client = 001

Solution Manager 4.0 Installation Error

am doing the Solution Manager 40 installation on AIX as root.
FYI: We are using central SLD.
During the installation in phase 30 "check DDIC password"
Sapinst stops with the following error.
In sapinst.log the error is:
In the installation log it says ERROR 2006-09-01 16:53:47
FRF-00025 Unable to call function. Error message: Large time
difference between application server a .
INFO 2006-09-01 16:53:47
RFC connection closed.
In sapinst_dev.log the error is:
FCO-00011 The step runRUTTTYPSET with step key
|NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_I
nstance|ind|ind|ind|ind|11|0|NW_CI_Instance_ABAP_Reports|ind|ind|ind|ind|1|0|runRUTTTYPSET
was executed with status ERROR .
I did tried retry,stopped exit out and stopsap and stared again.
Even I upgraded it to the latest kernel(75) and tried again but no luck.
I see the follwoing error in dev_w0:
A Large time difference between application server and database..
A
M ***LOG R68=> ThIRollBack, roll back () [thxxhead.c 13155]
A *** ERROR => zdate_gettime: Service for ABAP time in EMERGENCY
MODE. [zdate.c 1390].
Should I rollback to the old kernel which was 52, which came with
installation DVD's ?
The permissions of /usr/sap/trans and files and dir below is ok and owned by sidadm.
Does anyone has any idea ?
Thanks & Regards
Haq

Hi,
Could you please tell me what was the solution to this error. I am facing the similar issue.
Please help, thanks
Regards,
Nitin Nayyar

Solution Manager 4.0 Installation Error AIX 5.3 / Oracle 10.2.0.1

Hi All,
I am facing an error in the installation step of Solution Manager 4.0 on AIX 5.3 / Oracle 10.2.0.1
Hostname : INXXXXSAPIDES
The ABAP instance is not coming up and the Installation failed.I tried to bring up the instance manually.But was not successful.
Workprocess traces :
S queue size (profile) = 300
S hostspool list size = 3000
S option list size is 30
S found processing queue enabled
S found spool memory service RSPO-RCLOCKS at 0x7000001732fa070
S doing lock recovery
S setting server cache root
S found spool memory service RSPO-SERVERCACHE at 0x7000001732fa470
S using messages for server info
S size of spec char cache entry: 297032 bytes (timeout 100 sec)
S size of open spool request entry: 2176 bytes
S immediate print option for implicitely closed spool requests is disabled
A
A -PXA--
A PXA INITIALIZATION
A System page size: 4kb, total admin_size: 5720kb, dir_size: 5664kb.
A Attached to PXA (address 0x7000001e0000000, size 150000K)
A abap/pxa = shared unprotect gen_local
A PXA INITIALIZATION FINISHED
A -PXA--
A
Signal 6 encountered.
=> 64 bit R/3 Kernel
=> 64 bit AIX Kernel
=> Heap limit = unlimited
=> Stack limit = unlimited
=> Core limit = unlimited
=> File size limit = unlimited
=> Heap address = 0x0x113a1f5c0
=> Stack address = 0xfffffffffffded0
=> Stack low = 0xfffffffffffb5e0
=> Stack high = 0xffffffffffff810
=> Stack Trace:
 pthread_kill() at 0x900000000490650
 praise() at 0x900000000490070
 raise() at 0x900000000059624
 abort() at 0x900000000084a90
TrThHookFunc: called for WP dump
M ThCallHooks: call hook >ThrSaveSPAFields< for event BEFORE_DUMP
M *** ERROR => ThrSaveSPAFields: no valid thr_wpadm [thxxrun1.c 720]
M *** ERROR => ThCallHooks: event handler ThrSaveSPAFields for event BEFORE_DUMP failed [thxxtool3.c 260]
M Entering ThSetStatError
M ThIErrHandle: do not call ThrCoreInfo (no_core_info=0, in_dynp_env=0)
M ThErrPrivHandle: set th_errno (11)
M Entering ThReadDetachMode
M *** ERROR => ThIErrHandle: bad value for th_act_em_hdl (8), detach T0/M0 [thxxhead.c 10721]

DEV_DISP 
CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
CCMS: start to initalize 3.X shared alert area (first segment).
DpMsgAdmin: Set release to 7000, patchlevel 0
MBUF state PREPARED
MBUF component UP
DpMBufHwIdSet: set Hardware-ID
***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c 1050]
DpMsgAdmin: Set patchno for this platform to 102
Release check o.K.
Sat Jul 28 22:41:18 2007
ERROR => W0 (pid 442462) died [dpxxdisp.c 14319]
ERROR => W2 (pid 635048) died [dpxxdisp.c 14319]
ERROR => W3 (pid 598164) died [dpxxdisp.c 14319]
ERROR => W4 (pid 770084) died [dpxxdisp.c 14319]
ERROR => W5 (pid 815142) died [dpxxdisp.c 14319]
ERROR => W6 (pid 761862) died [dpxxdisp.c 14319]
my types changed after wp death/restart 0xbf --> 0xbd
ERROR => W7 (pid 671804) died [dpxxdisp.c 14319]
my types changed after wp death/restart 0xbd --> 0xb9
ERROR => W8 (pid 630958) died [dpxxdisp.c 14319]
ERROR => W9 (pid 622786) died [dpxxdisp.c 14319]
ERROR => W10 (pid 549070) died [dpxxdisp.c 14319]
my types changed after wp death/restart 0xb9 --> 0xb1
ERROR => W11 (pid 544802) died [dpxxdisp.c 14319]
my types changed after wp death/restart 0xb1 --> 0xa1
ERROR => W12 (pid 508062) died [dpxxdisp.c 14319]
my types changed after wp death/restart 0xa1 --> 0x81
Sat Jul 28 22:41:55 2007
ERROR => W1 (pid 802934) died [dpxxdisp.c 14319]
my types changed after wp death/restart 0x81 --> 0x80
DP_FATAL_ERROR => DpWPCheck: no more work processes
DISPATCHER EMERGENCY SHUTDOWN ***
increase tracelevel of WPs
stderr1
Command: dw.sapSM4_DVEBMGS10
 pf=/usr/sap/SM4/SYS/profile/SM4_DVEBMGS10_INSISCSAPIDES
ICM up and operational (pid: 675892) ***
timezone value meaningless. BSD libraries linked?
work process W1 died => ThSigHandler: signal
timezone value meaningless. BSD libraries linked?
work process W2 died => ThSigHandler: signal
timezone value meaningless. BSD libraries linked?
work process W12 died => ThSigHandler: signal
timezone value meaningless. BSD libraries linked?
.timezone value meaningless. BSD libraries linked?
work process W4 died => ThSigHandler: signal
work process W8 died => ThSigHandler: signal
timezone value meaningless. BSD libraries linked?
Can someone please help me in this.
Thanks
Siva
Message was edited by:
 siva sakthi

I found the solution..
There was a a problem in the timezone setting for the server.After changing it and rebooting it worked perfectely.

Solution Manager 7.0 Installation Error on Import ABAP -Test DB connection

Hi, SDN fellows.
I am installing Solution Manager 7.0. In Step 16 of 44 - Import ABAP, I encountered an error when the installer was testing the database connection. It failed at this command:
R3load.exe -testconnect
Below is the error I copied from the log viewer. Thanks for all possible advices/suggestions to fix this issue.
=================
WARNING 2011-07-12 03:51:49.188
Execution of the command "C:\usr\sap\SM1\SYS\exe\uc\NTAMD64\R3load.exe -testconnect" finished with return code 2. Output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
C:\usr\sap\SM1\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20110712035148
(DB) ERROR: db_connect rc = 256
(DB) ERROR: DbSlErrorMsg rc = 99
WARNING[E] 2011-07-12 03:51:49.188
CJS-30023 Process call 'C:\usr\sap\SM1\SYS\exe\uc\NTAMD64\R3load.exe -testconnect' exits with error code 2. For details see log file(s) R3load.exe.log.
ERROR 2011-07-12 03:51:49.204
FCO-00011 The step testDatabaseConnection 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_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|testDatabaseConnection was executed with status ERROR .
=============
KC

cont....
4 ETW000 33 1.576524
4 ETW000 [dev trc ,00000] Conn_i:1 selection:1 singleton:1 flag_fupd:0 use_cursor:0 chksum: 1112312
4 ETW000 24 1.576548
4 ETW000 [dev trc ,00000] DbSlRead - Error 103 (dbcode 208) on open 19 1.576567
4 ETW000 [dev trc ,00000] DbSlRead - <##Y4ISBDCAPPsm100000045960000000001234118>
4 ETW000 19 1.576586
4 ETW000 [dev trc ,00000] DbSlRead - Error 103 (dbcode 208) on fetch 13 1.576599
4 ETW000 [dev trc ,00000] DbSlRead - <##Y4ISBDCAPPsm100000045960000000001234118>
4 ETW000 18 1.576617
4 ETW000 [dblink ,01299] ***LOG BZA=>table SVERS does not exist on database [dblink#5 @ 1299]
4 ETW000 8060 1.584677
4 ETW000 [dev trc ,00000] Wed Jul 13 23:41:19 2011 41342 1.626019
4 ETW000 [dev trc ,00000] DbSlBegRead[1]: ##Y4ISBDCAPPsm100000045960000000002234118
4 ETW000 25 1.626044
4 ETW000 [dev trc ,00000] ParamStmtExec: line 13165. hr: 0x80040e14 Statement(s) could not be prepared.
4 ETW000 3649 1.629693
4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 8180, sev 0), Statement(s) could not be prepared.
4 ETW000 33 1.629726
4 ETW000 [dev trc ,00000] Procname: [##Y4ISBDCAPPsm100000045960000000002234118]
4 ETW000 19 1.629745
4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 208, sev 16), Invalid object name 'DDNTT'.
4 ETW000 27 1.629772
4 ETW000 [dev trc ,00000] Procname: [##Y4ISBDCAPPsm100000045960000000002234118]
4 ETW000 19 1.629791
4 ETW000 [dev trc ,00000] ParamStmtExec failed. HR 80040e14 DBSL retcode 103. stmt: [SELECT TOP 1 COMPCNT FROM "DDNTT" ]
4 ETW000 28 1.629819
4 ETW000 [dev trc ,00000] Conn_i:1 selection:1 singleton:0 flag_fupd:0 use_cursor:0 chksum: 1122000
4 ETW000 20 1.629839
4 ETW000 [dev trc ,00000] NTAB: SELECT COMPCNT FROM DDNTT FAILED 277 1.630116
4 ETW000 [dev trc ,00000] DbSlBegRead[1]: ##Y4ISBDCAPPsm100000045960000000003234118
4 ETW000 44 1.630160
4 ETW000 [dev trc ,00000] ParamStmtExec: line 13165. hr: 0x80040e14 Statement(s) could not be prepared.
4 ETW000 459 1.630619
4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 8180, sev 0), Statement(s) could not be prepared.
4 ETW000 33 1.630652
4 ETW000 [dev trc ,00000] Procname: [##Y4ISBDCAPPsm100000045960000000003234118]
4 ETW000 18 1.630670
4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 208, sev 16), Invalid object name 'DDNTT'.
4 ETW000 29 1.630699
4 ETW000 [dev trc ,00000] Procname: [##Y4ISBDCAPPsm100000045960000000003234118]
4 ETW000 23 1.630722
4 ETW000 [dev trc ,00000] ParamStmtExec failed. HR 80040e14 DBSL retcode 103. stmt: [SELECT TOP 1 VERSION FROM "DDNTT" ]
4 ETW000 29 1.630751
4 ETW000 [dev trc ,00000] Conn_i:1 selection:1 singleton:0 flag_fupd:0 use_cursor:0 chksum: 1122000
4 ETW000 20 1.630771
4 ETW000 [dev trc ,00000] NTAB: SELECT VERSION FROM DDNTT FAILED 267 1.631038
4 ETW000 [dev trc ,00000] DbSlBegRead[1]: ##Y4ISBDCAPPsm100000045960000000004234118
4 ETW000 43 1.631081
4 ETW000 [dev trc ,00000] ParamStmtExec: line 13165. hr: 0x80040e14 Statement(s) could not be prepared.
4 ETW000 436 1.631517
4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 8180, sev 0), Statement(s) could not be prepared.
4 ETW000 32 1.631549
4 ETW000 [dev trc ,00000] Procname: [##Y4ISBDCAPPsm100000045960000000004234118]
4 ETW000 18 1.631567
4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 208, sev 16), Invalid object name 'DDNTT'.
4 ETW000 58 1.631625
4 ETW000 [dev trc ,00000] Procname: [##Y4ISBDCAPPsm100000045960000000004234118]
4 ETW000 19 1.631644
4 ETW000 [dev trc ,00000] ParamStmtExec failed. HR 80040e14 DBSL retcode 103. stmt: [SELECT TOP 1 DBASE FROM "DDNTT" ]
4 ETW000 28 1.631672
4 ETW000 [dev trc ,00000] Conn_i:1 selection:1 singleton:0 flag_fupd:0 use_cursor:0 chksum: 1122000
4 ETW000 21 1.631693
4 ETW000 [dbntab.c ,00000] *** ERROR => NTAB: SELECT VERSION/DBASE FROM DDNTT FAILED
4 ETW000 284 1.631977
4 ETW000 [dbntab ,01276] ***LOG BZY=>unexpected return code 103 calling NTAB [dbntab#4 @ 12761]
4 ETW000 31 1.632008
4 ETW000 [twdydbacc.c ,00568] i:0 8690 1.640698
4 ETW000 [twdydbacc.c ,00569] db_fd_p.fname: PGMID 20 1.640718
4 ETW000 [twdydbacc.c ,00570] db_fd_p.is_key: 0 11 1.640729
4 ETW000 [twdydbacc.c ,00571] db_fd_p.offset: 0 10 1.640739
4 ETW000 [twdydbacc.c ,00572] db_fd_p.db_length: 0 10 1.640749
4 ETW000 [twdydbacc.c ,00573] db_fd_p.fixed_length:4 10 1.640759
4 ETW000 [dev trc ,00000] DbSlBegRead[1]: ##Y4ISBDCAPPsm100000045960000000005234118
4 ETW000 40 1.640799
4 ETW000 [dev trc ,00000] ParamStmtExec: line 13165. hr: 0x80040e14 Statement(s) could not be prepared.
4 ETW000 434 1.641233
4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 8180, sev 0), Statement(s) could not be prepared.
4 ETW000 32 1.641265
4 ETW000 [dev trc ,00000] Procname: [##Y4ISBDCAPPsm100000045960000000005234118]
4 ETW000 75 1.641340
4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 208, sev 16), Invalid object name 'XXXXT'.
4 ETW000 31 1.641371
4 ETW000 [dev trc ,00000] Procname: [##Y4ISBDCAPPsm100000045960000000005234118]
4 ETW000 18 1.641389
4 ETW000 [dev trc ,00000] ParamStmtExec failed. HR 80040e14 DBSL retcode 103. stmt: [SELECT TOP 1 COMPCNT FROM "XXXXT" ]
4 ETW000 28 1.641417
4 ETW000 [dev trc ,00000] Conn_i:1 selection:1 singleton:0 flag_fupd:0 use_cursor:0 chksum: 1122000
4 ETW000 21 1.641438
4 ETW000 [dev trc ,00000] NTAB: SELECT COMPCNT FROM XXXXT FAILED 269 1.641707
4 ETW000 [dev trc ,00000] DbSlBegRead[1]: ##Y4ISBDCAPPsm100000045960000000006234118
4 ETW000 44 1.641751
4 ETW000 [dev trc ,00000] ParamStmtExec: line 13165. hr: 0x80040e14 Statement(s) could not be prepared.
4 ETW000 437 1.642188
4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 8180, sev 0), Statement(s) could not be prepared.
4 ETW000 32 1.642220
4 ETW000 [dev trc ,00000] Procname: [##Y4ISBDCAPPsm100000045960000000006234118]
4 ETW000 18 1.642238
4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 208, sev 16), Invalid object name 'XXXXT'.
4 ETW000 28 1.642266
4 ETW000 [dev trc ,00000] Procname: [##Y4ISBDCAPPsm100000045960000000006234118]
4 ETW000 19 1.642285
4 ETW000 [dev trc ,00000] ParamStmtExec failed. HR 80040e14 DBSL retcode 103. stmt: [SELECT TOP 1 VERSION FROM "XXXXT" ]
4 ETW000 27 1.642312
4 ETW000 [dev trc ,00000] Conn_i:1 selection:1 singleton:0 flag_fupd:0 use_cursor:0 chksum: 1122000
4 ETW000 70 1.642382
4 ETW000 [dev trc ,00000] NTAB: SELECT VERSION FROM XXXXT FAILED 273 1.642655
4 ETW000 [dev trc ,00000] DbSlBegRead[1]: ##Y4ISBDCAPPsm100000045960000000007234118
4 ETW000 44 1.642699
4 ETW000 [dev trc ,00000] ParamStmtExec: line 13165. hr: 0x80040e14 Statement(s) could not be prepared.
4 ETW000 435 1.643134
4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 8180, sev 0), Statement(s) could not be prepared.
4 ETW000 32 1.643166
4 ETW000 [dev trc ,00000] Procname: [##Y4ISBDCAPPsm100000045960000000007234118]
4 ETW000 19 1.643185
4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 208, sev 16), Invalid object name 'XXXXT'.
4 ETW000 28 1.643213
4 ETW000 [dev trc ,00000] Procname: [##Y4ISBDCAPPsm100000045960000000007234118]
4 ETW000 20 1.643233
4 ETW000 [dev trc ,00000] ParamStmtExec failed. HR 80040e14 DBSL retcode 103. stmt: [SELECT TOP 1 DBASE FROM "XXXXT" ]
4 ETW000 30 1.643263
4 ETW000 [dev trc ,00000] Conn_i:1 selection:1 singleton:0 flag_fupd:0 use_cursor:0 chksum: 1122000
4 ETW000 21 1.643284
4 ETW000 [dbntab.c ,00000] *** ERROR => NTAB: SELECT VERSION/DBASE FROM XXXXT FAILED
4 ETW000 324 1.643608
4 ETW000 [dbntab ,01276] ***LOG BZY=>unexpected return code 103 calling NTAB [dbntab#4 @ 12761]
4 ETW000 27 1.643635
2EETW000 sap_dext called with msgnr "2":
2EETW000 -
db call info -
2EETW000 function: db_ntab
2EETW000 fcode: NT_RDTDESCR
2EETW000 tabname: TADIR
2EETW000 len (char): 5
2EETW000 key: TADIR
2EETW000 retcode: 2
4 ETW000 [dev trc ,00000] db_con_rollback (con_da={R/3,0,0},th_rollback=1,tx=0)
4 ETW000 9946 1.653581
4 ETW000 [dev trc ,00000] Rollback: TestConnection(1) successful 36526 1.690107

Error during solution manager 3.2 installation.

Hi !
I am getting the error in solution manager 3.2 installation . I am doing installation using system copy / backup restore method .
Getting ther following error -
"CJS-00084 SQL statement or script failed. DIAGNOSIS: Error message: SP2-0310: unable to open file
"CONTROL.SQL"ORA-01012: not logged onORACLE instance started."
Kindly suggest the solution.
Regards-
sanjay

hi Markus!
The ora_sql_results.log file shows the following-
"2007-06-07, 18:32:21 SAPINST ORACLE start logging for
connect / as sysdba ;
CONNECT / AS SYSDBA
SHUTDOWN ABORT
@CONTROL.SQL
SHUTDOWN IMMEDIATE
STARTUP MOUNT
ALTER DATABASE ARCHIVELOG;
ALTER DATABASE OPEN;
EXIT
exit;
Output of SQL executing program:
SQL*Plus: Release 9.2.0.6.0 - Production on Thu Jun 7 18:32:21 2007
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected.
Connected.
ORACLE instance shut down.
SP2-0310: unable to open file "CONTROL.SQL"
ORA-01012: not logged on
ORACLE instance started.
Total System Global Area 546906764 bytes
Fixed Size               455308 bytes
Variable Size            293601280 bytes
Database Buffers       251658240 bytes
Redo Buffers              1191936 bytes
ORA-00205: error in identifying controlfile, check alert log for more info
ALTER DATABASE ARCHIVELOG
ERROR at line 1:
ORA-01507: database not mounted
ALTER DATABASE OPEN
ERROR at line 1:
ORA-01507: database not mounted
Disconnected from Oracle9i Enterprise Edition Release 9.2.0.6.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.6.0 - Production
SAPINST: End of output of SQL executing program E:\oracle\SMP\920/bin/sqlplus.
SAPINST found errors.
SAPINST The current process environment may be found in sapinst_ora_environment.log.
2007-06-07, 18:32:28 SAPINST ORACLE stop logging"
What to follow... pls guide
Regards-
sanjay

Solution manager 7.1 installation in ECC 6.0 landscape

Dear All,
I am planning to install solman 7.1 SP04 in my landscape where the managed systems are running on ECC 6.0. SP 07(PRD, DEV,...).
Is it fine to start installation with current landscape or i need to upgrade the ECC version.
Any documents available regarding the technical system patch level requirements for Solution manager 7.1 installation.
Please suggest.

Hi Jithu,
Pls refer below links,
Solution Manager installation 7.1
SAP Solution Manager 7.1 – SAP Help Portal Page
Dia Agent Connect To system in solman 7.1 sp10
Regards
K.N

Error in Solution Manager 4.0 Installation

When installing Solution Manager 4.0 on Windows server 2003 with Oracle 10g, Installation
failed at Import ABAP.
The Error message is :-
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log
file(s) import_monitor.java.log, import_monitor.log.
import_monitor.java.log
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 5, completed 12, failed 0, total 18.
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 0, waiting 5, completed 12, failed 1, total 18.
Import Monitor jobs: running 1, waiting 4, completed 12, failed 1, total 18.
Loading of 'SAPSSRC' import package: ERROR
Import Monitor jobs: running 0, waiting 4, completed 12, failed 2, total 18.
Import Monitor jobs: running 1, waiting 3, completed 12, failed 2, total 18.
Loading of 'SAPSPROT' import package: ERROR
Import Monitor jobs: running 0, waiting 3, completed 12, failed 3, total 18.
Import Monitor jobs: running 1, waiting 2, completed 12, failed 3, total 18.
Loading of 'SAPSDOCU' import package: ERROR
import_monitor.log
WARNING: 2006-07-27 09:47:26
Cannot start import of packages with views because not all import packages with tables are
loaded successfully.
WARNING: 2006-07-27 09:47:26
4 error(s) during processing of packages.
INFO: 2006-07-27 09:47:26
Import Monitor is stopped.
The Java version we are using is - j2sdk-1_4_2_12-windows-i586-p
Any guidance will be appreciated
Thanks
Gireesh

ganesh if solved ur problem plz help me
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()

Error in Solution Manager 4.0 Installation u0096 Step 32 Create JAVE users

Hi All,
I am installing Solution Manager 4.0 on WIN server 2003 & Oracle10g. The installation has been successful so far but at Step 32 (Create JAVA users) the installation errors and the error log is as follows:
ERROR 2016-09-10 06:39:28
CJS-30197 . For more details see output of logfile:
ERROR 2016-09-10 06:39:28
FCO-00011 The step createJSF with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_Doublestack|ind|ind|ind|ind|2|0|createJSF was executed with status ERROR .
Critical Error
Launching program failed
-> Invalid JDK (rc = -17)
Entries in the log file (UserCheck.log)
Critical Error
Launching program failed
-> Invalid JDK (rc = -17)
The Java version Im using is - j2re1.4.2_12 windows.
Any guidance will be appreciated
Thanks
Frank

Dear all
use j2re1.4.2_16 windows.
case1-if sapjsf user not craeted login to 001 clint with sap* delete
case2- if sapjsf user not craete a sapjsf user createand then delete
agin proceed
i am trouble this problem within week
but at last complte of the installation
thanks
regards
venkat

Oracle Errors while Solution Manager 4.0 installation on linux

While installing Oracle 10g instance for Solution Manager 4.0, The following popup message displayed. I checked the log file and not much information. Please tell me what shall I need to do.
Error message:
Error in invoking target 'ntcontab.o' of make file '/oracle/<sid>/102_32/network/lib/ins_net_client.mk'
see '/oracle/orainventory/logs/installActions2006-10-08_06-39-02PM.log' for details
Thanks in advance
Regards
Srinivas

Hello, have some one solved the problem ? I have the same problem on SLES9. I have fond note #499055. There are something about relinking files during Oracle installation on Linux. Please give an information did You soled a problem.
Best Regards
Marcin Sobolewski

Solution manager 7.1 sp4 , error @Bytecode adpater installation

HI All,
 I am facing the below issue while executing the managed system wizard @ Bytecode adapter installation.
Error @ Managed system
Failed to create Introscope Agent Connector at: /usr/sap/SMD/SMDA98/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.3.5-2011-09-13/wily/connectors: - java.io.IOException: Cannot run program "null/bin/java" (in directory "/usr/sap/SMD/SMDA98/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.3.5-2011-09-13/wily/connectors"): java.io.IOException: error=2, No such file or directory.
Error @ Diagnostic agent level
Jun 6, 2014 10:52:31 AM [Thread[Thread-19,5,main]
] Error
Operation Failed :
[EXCEPTION]
com.sap.smdagent.vmmanager.VMManagerException: Failed to get Instance properties - 48161
at com.sap.smdagent.vmmanager.impl700.VMManager._getSettings(VMManager.java:170)
at com.sap.smdagent.vmmanager.impl700.VMManager.getSettings(VMManager.java:156)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sap.smd.server.exec.asio.AsioInvocationHandler$1.call(AsioInvocationHandler.java:94)
at com.sap.smd.server.util.concurrent.FutureResult$1.run(FutureResult.java:90)
at com.sap.smd.server.exec.asio.AsioInvocationHandler$AsioRunner.run(AsioInvocationHandler.java:285)
at com.sap.smd.server.exec.TaskRunner.run(TaskRunner.java:46)
at com.sap.smd.server.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:785)
at java.lang.Thread.run(Thread.java:679)
Caused by: java.lang.SecurityException: User is not authorized to access Configuration Manager.
at com.sap.engine.services.configuration.ConfigurationRuntimeInterfaceImpl.checkAuthorization(ConfigurationRuntimeInterfaceImpl.java:62)
at com.sap.engine.services.configuration.ConfigurationRuntimeInterfaceImpl.getConfigurationContext(ConfigurationRuntimeInterfaceImpl.java:48)
at sun.reflect.GeneratedMethodAccessor392.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:331)
at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:159)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
1. As per standard note , patch levels are on sap recommended level only.
2. Created connector manually as per wily documentation , but still no use.
3. Given the permissions for temp,<SID>cluster etc.. as per sap notes and restarted all the services including sapstartsrv
4. Assigend SPML roles as suggested by note.
5. checked java environment and umask for diagnostic users , everything looks ok.
 Checked couple of notes related to the above issue ,
 1616058 - XSRF possible in SPML Services in AS Java
 1820230 - Byte Code Adapter Installation error in Solution Manager 7.1 Managed System Configuration step Configure Automatically
 1752441 - Introscope Agent Connector generation is done using JDK at: null

I would like paste few more error lines,
Jun 9, 2014 6:43:33 AM [Thread[FileSystemService_4cdecd7c,5,main]
] Error
[WHS] Failed to find javaPath for node 5818350
[EXCEPTION]
com.sap.smdagent.vmmanager.VMManagerException: Failed to get Instance properties - 58183
at com.sap.smdagent.vmmanager.impl700.VMManager._getSettings(VMManager.java:170)
at com.sap.smdagent.vmmanager.impl700.VMManager.getSettings(VMManager.java:156)
at sun.reflect.GeneratedMethodAccessor298.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sap.smd.server.exec.asio.AsioInvocationHandler$1.call(AsioInvocationHandler.java:94)
at com.sap.smd.server.util.concurrent.FutureResult$1.run(FutureResult.java:90)
at com.sap.smd.server.exec.asio.AsioInvocationHandler$AsioRunner.run(AsioInvocationHandler.java:285)
at com.sap.smd.server.exec.TaskRunner.run(TaskRunner.java:46)
at com.sap.smd.server.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:785)
at java.lang.Thread.run(Thread.java:679)
Caused by: java.lang.SecurityException: User is not authorized to access Configuration Manager.

Solution Manager 4.0(Installation)

Hallo Everyone,
I'am trying for about four hours to install Solution Manager 4.0.
Without any progess.
I only reach Step 2 "Define Parameters, Media Browser > Software package"
At the End, I got this error and the Installation was aborded.
ERROR      2007-04-16 17:57:48 [iaxxinscbk.cpp:271]
           abortInstallation
CJS-00030 Assertion failed: in NW_ABAP_Import_Dialog.dialogPreconditions: Import directory 'D:\EXP1' must exist
ERROR      2007-04-16 17:57:48
           CJSlibModule::writeError_impl()
MUT-03025 Caught ESAPinstException in Modulecall: ESAPinstException: error text undefined.
ERROR      2007-04-16 17:57:48
FCO-00011 The step dialogPreconditions 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|9|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|dialogPreconditions was executed with status ERROR .
INFO       2007-04-16 17:58:08 [iaxxgenimp.cpp:779]
           showDialog()
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|9|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|dialogPreconditions".
Exit status of child: 1
P.s. The installation is on a Virtual Machine(VMware) and the JDK is "j2sdk1.4.2_14"
Thanks for everyone's help,
Kais

Hi Kais,
Installation on VMWare instance is a little unstable as I too faced a lot of issues similar to that. To solve your issue, please do copy all the installation media to the local VMWare instance itself and then start the installation, it will go through. Moreoever, to be on the safer side, do install JDK 1.4.2_09 or 10. Coz I faced issues when I tried with 1.4.2_12 and 13.
Hope this would help. Please do revert if you would require further help.
Regards,
P. Kumaravel.
Ps: Award points for helpful answers.

Install ECC 6.0 and Solution Manager on same server Error (MaxDB/Linux)

I have installed Solution manager on one server and then ECC 6 also in the same server with another SID. during the installation it errored out at phase "SLD configuration" with UME error , J2EE_ADMIN locked etc..we checked the user id and noticed it got locked in ECC 6 system and we unlocked it.
But after the ECC installation the solution manager java engine is not coming up error with "com.sap.security.core.ume.service failed" error. Prior to the ECC installation the Solution Manager J2EE was working.
thanks in advance
Mathew

error in the /j2ee/cluster/server0/log/defaultTrace.1.trc
is as follows
#1.5#00137256A483001E0000001700006F190004163784D40864#1150327614343#com.sap.engine.core.Framework##com.sap.engine.core.Framework#######SAPEngine_System_Thread[impl:5]_61##0#0#Fatal#1#/System/Server#Plain###Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.#
When I looked at using jcmon the dispacher is up and the server0 and SDM is down

Solution Manager 4.0 SR2: Error during step 1 installPolicyArchive

Hi,
I faced a really annoying problem in first step of Installation of a SAP Solution Manager 4.0 SR2 on Suse Linux Enterprise Server 10.
The Installation hangs in Phase 1 installPolicyArchive.
I think i have passed all prerequisites before starting the Installation.
Perhaps for help:
i set the Environment Variables as follows:
JDK_HOME=/usr/lib/jvm/java-1_4_2-sun-1.4.2.11/
JRE_HOME=/usr/lib/jvm/java-1_4_2-sun-1.4.2.11/jre
JAVA_BINDIR=/usr/lib/jvm/java-1_4_2-sun-1.4.2.11/bin
JAVA_HOME=/usr/lib/jvm/java-1_4_2-sun-1.4.2.11/
SAPINST_JAVA_HOME=/usr/lib/jvm/java-1_4_2-sun-1.4.2.11/
JAVA_ROOT=/usr/lib/jvm/java-1_4_2-sun-1.4.2.11/
As you see Java Version is java-1_4_2-sun-1.4.2.11.
The Error in sapinst.log is as follows:
ERROR 2009-03-03 15:58:44
FSL-00001 System call failed. Error 2 (No such file or directory) in execution of system call 'realpath' with parameter (/usr/lib/jvm/java-1_4_2-sun-1.4.2.11/jre/lib/security/local_policy.jar), line (346) in file (syuxclink.cpp).
ERROR 2009-03-03 15:58:44
MUT-03025 Caught ESyException in Modulecall: ESAPinstException: error text undefined.
ERROR 2009-03-03 15:58:44
FCO-00011 The step installPolicyArchive with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_getJavaHome|ind|ind|ind|ind|1|0|NW_getJavaHome_jcePolicy|ind|ind|ind|ind|0|0|installPolicyArchive was executed with status ERROR .
Can anyone help me solve the problem?
Thanks beforehand and Best Regards,
C. Peifer

> I'm on 32 bit
Ok - then the JDK correct.
sapinst searches for a policy file, is the given filename there?
/usr/lib/jvm/java-1_4_2-sun-1.4.2.11/jre/lib/security/local_policy.jar

Issue on Solution Manager 4.0 installation SR3

Dear all,
During the Oracle Client installation phase of a SAP Solution Manager 4.0
system installation with sapinst, I get the following error
ERROR 2008-01-21 16:04:06.776 [iaxxejsbas.cpp:178]
EJS_ErrorReporter
FJS-00003 TypeError: linkTarget has no properties (in script
NW_Onehost|ind|ind|ind|ind, line 3431: ???)
ERROR 2008-01-21 16:04:07.399 [iaxxgenimp.cpp:731]
showDialog()
FCO-00011 The step createOcl10Links with step key
|NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_C
reateDBandLoad|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|in
d|ind|0|0|NW_OraDBStd|ind|ind|ind|ind|3|0|NW_OraClient|ind|ind|ind|ind|3|0|createOcl10Links was executed with status ERROR .
TRACE 2008-01-21 16:04:07.443 [iaxxgenimp.cpp:719]
showDialog()
Any ideas?
Many thanks
Andreas

On Solaris 10 platform...
We found that we could correct the problem by extracting the SAR file OCL10264.SAR from the client DVD into the client directory /oracle/client/10x_64 (which we had to create) and execute "ln -s instantclient_10202 instantclient" to create the symbolic link for the instantclient directory. Then the installation continued successfully.
Credit to Rama Ekambaram for figuring this out...
Tim Pittman

Solution Manager 4.0 Installation error on vmware

Similar Messages

Maybe you are looking for