TREX 7.0 System AIX 5.3 DB2 Error FCO-00011 The step extractTrexBinaries
Hi Colleagues,
In the process 6 of 12 the installation the trex stopped with this error,
FCO-00011 The step extractTrexBinaries with step key |TREX_NW_CI_MAIN|ind|ind|TREX|ind|0|0|TREX_MAIN|ind|ind|TREX|ind|0|0|TREX_BINARY_INST|ind|ind|TREX|ind|4|0 |extractTrexBinaries was executed with status ERROR .
The version the sapinst is last in the sapnet.
Please Helpppppp Meeeee
Hi Colleagues,
I installed the sapinst TREX70_37-20000466.SAR but the error continue.
Regards Victor.
Similar Messages
-
Error FCO-00011 while performing System Import for PI 7.0
Hi All,
Error occured while performing system import for PI 7.0.
Error occured at phase 11 of 34 (Create database instance)
As per the log sapinst.log
FCO-00011 The step sdb_init_instance_type with step key |NW_Doublestack_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_CreateDB|ind|ind|ind|ind|0|0|NW_ADA_DB|ind|ind|ind|ind|6|0|SdbPreInstanceDialogs|ind|ind|ind|ind|3|0|SdbInstanceDialogs|ind|ind|ind|ind|1|0|SDB_INSTANCE_CREATE|ind|ind|ind|ind|0|0|sdb_init_instance_type was executed with status ERROR .
As per the log XCMDOUT.log
> Subprocess starts at 20090420093658
Execute Command : /sapdb/programs/bin/dbmcli -n lgsbie -d EXI -u CONTROL,********
Start subprocess as user with uid: root
Execute Session Command : param_startsession
> Subprocess stops at 20090420093658
Error! Connection failed to node (hostname) for database (SID):
database not found
Please let me know your valuable inputs.
Regards
Shiva.Details of Error :
This is the Test System.
When trying to do system copy by extracting the export from production, selected the option for ABAP+JAVA and moving further selected Homogenous System copy (backup n recovery), at phase 10 - 34 it has removed database instance n in the next phase while creating the database it got struck.
Error displayed even go ahead selecting New installation :
Subprocess starts at 20090422134100
Execute Command : /sapdb/programs/bin/dbmcli -n hostname -d SID -u CONTROL,******** db_online
Start subprocess as user with uid: root
> Subprocess stops at 20090422134133
ERR
-24988,ERR_SQL: SQL error
-902,I/O error
3,Database state: OFFLINE
6,Internal errorcode, Errorcode 9050 "disk_not_accessible"
20017,RestartFilesystem failed with 'I/O error'
Please provide me the best solution at the earliest which will be really aprreciated
Regards
Shiva -
Error in import abap step while importing system copy.
Hi All,
My colleague had taken System copy of development server, few days back. it was completed successfully,
now we want to restore that system copy, as hardware failed. But when we start the import of system copy,
all ABAP jobs are failing in import abap step, Some DDL statement problem. can u pls help wht to do.
I found in some forums, SMIGR_create_DDL report need to be generated prior to taking system copy, but he
didnt taken tht.
OS: Windows 2003
DB: DB2
Pls find sapinst.log
INFO 2009-10-27 10:43:06.890
Output of C:\j2sdk1.4.2_13-x64\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst is written to the logfile import_monitor.java.log.
WARNING 2009-10-27 10:53:37.125
Execution of the command "C:\j2sdk1.4.2_13-x64\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2_13"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_13-b06)
Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_13-b06, mixed mode)
Import Monitor jobs: running 1, waiting 63, completed 0, failed 0, total 64.
Import Monitor jobs: running 2, waiting 62, completed 0, failed 0, total 64.
Import Monitor jobs: running 3, waiting 61, completed 0, failed 0, total 64.
Loading of 'DOKCLU' import package: ERROR
Import Monitor jobs: running 2, waiting 61, completed 0, failed 1, total 64.
Loading of 'D010TAB' import package: ERROR
Import Monitor jobs: running 1, waiting 61, completed 0, failed 2, total 64.
Loading of 'REPOSRC' import package: ERROR
Import Monitor jobs: running 0, waiting 61, completed 0, failed 3, total 64.
Import Monitor jobs: running 1, waiting 60, completed 0, failed 3, total 64.
Import Monitor jobs: running 2, waiting 59, completed 0, failed 3, total 64.
Import Monitor jobs: running 3, waiting 58, completed 0, failed 3, total 64.
Loading of 'DYNPSOURCE' import package: ERROR
Import Monitor jobs: running 2, waiting 58, completed 0, failed 4, total 64.
Loading of 'SAPAPPL1_4' import package: ERROR
Import Monitor jobs: running 1, waiting 58, completed 0, failed 5, total 64.
Loading of 'SAPAPPL2_2' import package: ERROR
Import Monitor jobs: running 0, waiting 58, completed 0, failed 6, total 64.
Import Monitor jobs: running 1, waiting 57, completed 0, failed 6, total 64.
Import Monitor jobs: running 2, waiting 56, completed 0, failed 6, total 64.
Import Monitor jobs: running 3, waiting 55, completed 0, failed 6, total 64.
Loading of 'SAPNTAB' import package: ERROR
Import Monitor jobs: running 2, waiting 55, completed 0, failed 7, total 64.
Loading of 'SAPSSEXC_9' import package: ERROR
Import Monitor jobs: running 1, waiting 55, completed 0, failed 8, total 64.
Loading of 'SAPSSEXC_8' import package: ERROR
Import Monitor jobs: running 0, waiting 55, completed 0, failed 9, total 64.
Import Monitor jobs: running 1, waiting 54, completed 0, failed 9, total 64.
Import Monitor jobs: running 2, waiting 53, completed 0, failed 9, total 64.
Import Monitor jobs: running 3, waiting 52, completed 0, failed 9, total 64.
Loading of 'SAPAPPL2_6' import package: ERROR
Import Monitor jobs: running 2, waiting 52, completed 0, failed 10, total 64.
Loading of 'SAPAPPL1_3' import package: ERROR
Import Monitor jobs: running 1, waiting 52, completed 0, failed 11, total 64.
Loading of 'SAPAPPL2_5' import package: ERROR
Import Monitor jobs: running 0, waiting 52, completed 0, failed 12, total 64.
Import Monitor jobs: running 1, waiting 51, completed 0, failed 12, total 64.
Import Monitor jobs: running 2, waiting 50, completed 0, failed 12, total 64.
Import Monitor jobs: running 3, waiting 49, completed 0, failed 12, total 64.
Loading of 'D010INC' import package: ERROR
Import Monitor jobs: running 2, waiting 49, completed 0, failed 13, total 64.
Loading of 'SAPAPPL1_2' import package: ERROR
Import Monitor jobs: running 1, waiting 49, completed 0, failed 14, total 64.
Loading of 'SAPAPPL1_7' import package: ERROR
Import Monitor jobs: running 0, waiting 49, completed 0, failed 15, total 64.
Import Monitor jobs: running 1, waiting 48, completed 0, failed 15, total 64.
Import Monitor jobs: running 2, waiting 47, completed 0, failed 15, total 64.
Import Monitor jobs: running 3, waiting 46, completed 0, failed 15, total 64.
Loading of 'SAPSSEXC_2' import package: ERROR
Import Monitor jobs: running 2, waiting 46, completed 0, failed 16, total 64.
Loading of 'DYNPLOAD' import package: ERROR
Import Monitor jobs: running 1, waiting 46, completed 0, failed 17, total 64.
Loading of 'SAPSSEXC_5' import package: ERROR
Import Monitor jobs: running 0, waiting 46, completed 0, failed 18, total 64.
Import Monitor jobs: running 1, waiting 45, completed 0, failed 18, total 64.
Import Monitor jobs: running 2, waiting 44, completed 0, failed 18, total 64.
Import Monitor jobs: running 3, waiting 43, completed 0, failed 18, total 64.
Loading of 'SAPSDIC' import package: ERROR
Import Monitor jobs: running 2, waiting 43, completed 0, failed 19, total 64.
Loading of 'SAPAPPL2_14' import package: ERROR
Import Monitor jobs: running 1, waiting 43, completed 0, failed 20, total 64.
Loading of 'SAPAPPL0_2' import package: ERROR
Import Monitor jobs: running 0, waiting 43, completed 0, failed 21, total 64.
Import Monitor jobs: running 1, waiting 42, completed 0, failed 21, total 64.
Import Monitor jobs: running 2, waiting 41, completed 0, failed 21, total 64.
Import Monitor jobs: running 3, waiting 40, completed 0, failed 21, total 64.
Loading of 'SAPSSEXC_3' import package: ERROR
Import Monitor jobs: running 2, waiting 40, completed 0, failed 22, total 64.
Loading of 'SAPSSEXC_4' import package: ERROR
Import Monitor jobs: running 1, waiting 40, completed 0, failed 23, total 64.
Loading of 'SAPAPPL2_10' import package: ERROR
Import Monitor jobs: running 0, waiting 40, completed 0, failed 24, total 64.
Import Monitor jobs: running 1, waiting 39, completed 0, failed 24, total 64.
Import Monitor jobs: running 2, waiting 38, completed 0, failed 24, total 64.
Import Monitor jobs: running 3, waiting 37, completed 0, failed 24, total 64.
Loading of 'SAPSSEXC_7' import package: ERROR
Import Monitor jobs: running 2, waiting 37, completed 0, failed 25, total 64.
Loading of 'SAPAPPL0_7' import package: ERROR
Import Monitor jobs: running 1, waiting 37, completed 0, failed 26, total 64.
Loading of 'SAPAPPL0_1' import package: ERROR
Import Monitor jobs: running 0, waiting 37, completed 0, failed 27, total 64.
Import Monitor jobs: running 1, waiting 36, completed 0, failed 27, total 64.
Import Monitor jobs: running 2, waiting 35, completed 0, failed 27, total 64.
Import Monitor jobs: running 3, waiting 34, completed 0, failed 27, total 64.
Loading of 'SAPAPPL2_7' import package: ERROR
Import Monitor jobs: running 2, waiting 34, completed 0, failed 28, total 64.
Loading of 'SAPAPPL2_4' import package: ERROR
Import Monitor jobs: running 1, waiting 34, completed 0, failed 29, total 64.
Loading of 'SAPAPPL1_6' import package: ERROR
Import Monitor jobs: running 0, waiting 34, completed 0, failed 30, total 64.
Import Monitor jobs: running 1, waiting 33, completed 0, failed 30, total 64.
Import Monitor jobs: running 2, waiting 32, completed 0, failed 30, total 64.
Import Monitor jobs: running 3, waiting 31, completed 0, failed 30, total 64.
Loading of 'SAPAPPL0_3' import package: ERROR
Import Monitor jobs: running 2, waiting 31, completed 0, failed 31, total 64.
Loading of 'SAPCLUST' import package: ERROR
Import Monitor jobs: running 1, waiting 31, completed 0, failed 32, total 64.
Loading of 'SAPAPPL0_8' import package: ERROR
Import Monitor jobs: running 0, waiting 31, completed 0, failed 33, total 64.
Import Monitor jobs: running 1, waiting 30, completed 0, failed 33, total 64.
Import Monitor jobs: running 2, waiting 29, completed 0, failed 33, total 64.
Import Monitor jobs: running 3, waiting 28, completed 0, failed 33, total 64.
Loading of 'SAPSSRC' import package: ERROR
Import Monitor jobs: running 2, waiting 28, completed 0, failed 34, total 64.
Loading of 'ENHOBJCONTRACT' import package: ERROR
Import Monitor jobs: running 1, waiting 28, completed 0, failed 35, total 64.
Loading of 'SAPAPPL0_4' import package: ERROR
Import Monitor jobs: running 0, waiting 28, completed 0, failed 36, total 64.
Import Monitor jobs: running 1, waiting 27, completed 0, failed 36, total 64.
Import Monitor jobs: running 2, waiting 26, completed 0, failed 36, total 64.
Import Monitor jobs: running 3, waiting 25, completed 0, failed 36, total 64.
Loading of 'SAPSSEXC_1' import package: ERROR
Import Monitor jobs: running 2, waiting 25, completed 0, failed 37, total 64.
Loading of 'SAPSSEXC_6' import package: ERROR
Import Monitor jobs: running 1, waiting 25, completed 0, failed 38, total 64.
Loading of 'SAPAPPL2_8' import package: ERROR
Import Monitor jobs: running 0, waiting 25, completed 0, failed 39, total 64.
Import Monitor jobs: running 1, waiting 24, completed 0, failed 39, total 64.
Import Monitor jobs: running 2, waiting 23, completed 0, failed 39, total 64.
Import Monitor jobs: running 3, waiting 22, completed 0, failed 39, total 64.
Loading of 'SAPPOOL' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 0, failed 40, total 64.
Loading of 'SAPAPPL2_1' import package: ERROR
Import Monitor jobs: running 1, waiting 22, completed 0, failed 41, total 64.
Loading of 'SAPAPPL1_5' import package: ERROR
Import Monitor jobs: running 0, waiting 22, completed 0, failed 42, total 64.
Import Monitor jobs: running 1, waiting 21, completed 0, failed 42, total 64.
Import Monitor jobs: running 2, waiting 20, completed 0, failed 42, total 64.
Import Monitor jobs: running 3, waiting 19, completed 0, failed 42, total 64.
Loading of 'REPOTEXT' import package: ERROR
Import Monitor jobs: running 2, waiting 19, completed 0, failed 43, total 64.
Loading of 'SAPAPPL0_5' import package: ERROR
Import Monitor jobs: running 1, waiting 19, completed 0, failed 44, total 64.
Loading of 'SAPAPPL2_9' import package: ERROR
Import Monitor jobs: running 0, waiting 19, completed 0, failed 45, total 64.
Import Monitor jobs: running 1, waiting 18, completed 0, failed 45, total 64.
Import Monitor jobs: running 2, waiting 17, completed 0, failed 45, total 64.
Import Monitor jobs: running 3, waiting 16, completed 0, failed 45, total 64.
Loading of 'SAPSSEXC_10' import package: ERROR
Import Monitor jobs: running 2, waiting 16, completed 0, failed 46, total 64.
Loading of 'SAPAPPL2_3' import package: ERROR
Import Monitor jobs: running 1, waiting 16, completed 0, failed 47, total 64.
Loading of 'SAPAPPL0_6' import package: ERROR
Import Monitor jobs: running 0, waiting 16, completed 0, failed 48, total 64.
Import Monitor jobs: running 1, waiting 15, completed 0, failed 48, total 64.
Import Monitor jobs: running 2, waiting 14, completed 0, failed 48, total 64.
Import Monitor jobs: running 3, waiting 13, completed 0, failed 48, total 64.
Loading of 'SAPSLEXC' import package: ERROR
Import Monitor jobs: running 2, waiting 13, completed 0, failed 49, total 64.
Loading of 'SAPAPPL0_9' import package: ERROR
Import Monitor jobs: running 1, waiting 13, completed 0, failed 50, total 64.
Loading of 'SAPAPPL2_11' import package: ERROR
Import Monitor jobs: running 0, waiting 13, completed 0, failed 51, total 64.
Import Monitor jobs: running 1, waiting 12, completed 0, failed 51, total 64.
Import Monitor jobs: running 2, waiting 11, completed 0, failed 51, total 64.
Import Monitor jobs: running 3, waiting 10, completed 0, failed 51, total 64.
Loading of 'SAPSPROT' import package: ERROR
Import Monitor jobs: running 2, waiting 10, completed 0, failed 52, total 64.
Loading of 'SAPAPPL2_13' import package: ERROR
Import Monitor jobs: running 1, waiting 10, completed 0, failed 53, total 64.
Loading of 'SAPAPPL2_12' import package: ERROR
Import Monitor jobs: running 0, waiting 10, completed 0, failed 54, total 64.
Import Monitor jobs: running 1, waiting 9, completed 0, failed 54, total 64.
Import Monitor jobs: running 2, waiting 8, completed 0, failed 54, total 64.
Import Monitor jobs: running 3, waiting 7, completed 0, failed 54, total 64.
Loading of 'SAPSLOAD' import package: ERROR
Import Monitor jobs: running 2, waiting 7, completed 0, failed 55, total 64.
Loading of 'SAPSDOCU' import package: ERROR
Import Monitor jobs: running 1, waiting 7, completed 0, failed 56, total 64.
Loading of 'SAPAPPL1_1' import package: ERROR
Import Monitor jobs: running 0, waiting 7, completed 0, failed 57, total 64.
Import Monitor jobs: running 1, waiting 6, completed 0, failed 57, total 64.
Import Monitor jobs: running 2, waiting 5, completed 0, failed 57, total 64.
Import Monitor jobs: running 3, waiting 4, completed 0, failed 57, total 64.
Loading of 'SAPDDIM' import package: ERROR
Import Monitor jobs: running 2, waiting 4, completed 0, failed 58, total 64.
Loading of 'SAPUSER' import package: ERROR
Import Monitor jobs: running 1, waiting 4, completed 0, failed 59, total 64.
Loading of 'SAPDFACT' import package: ERROR
Import Monitor jobs: running 0, waiting 4, completed 0, failed 60, total 64.
Import Monitor jobs: running 1, waiting 3, completed 0, failed 60, total 64.
Import Monitor jobs: running 2, waiting 2, completed 0, failed 60, total 64.
Import Monitor jobs: running 3, waiting 1, completed 0, failed 60, total 64.
Loading of 'SAPDODS' import package: ERROR
Import Monitor jobs: running 2, waiting 1, completed 0, failed 61, total 64.
Loading of 'SAPUSER1' import package: ERROR
Import Monitor jobs: running 1, waiting 1, completed 0, failed 62, total 64.
Loading of 'SAP0000' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 0, failed 63, total 64.
ERROR 2009-10-27 10:53:37.125
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR 2009-10-27 10:53:37.140
FCO-00011 The step runMigrationMonitor with step key |NW_Doublestack_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|runMigrationMonitor was executed with status ERROR ( Last error reported by the step :Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.).
Thanks.i checked the DOKCLU log, pls find the log below:
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20091027104307
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#20 $ SAP
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Aug 23 2009 23:42:38
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe -i DOKCLU.cmd -dbcodepage 4103 -k 1gage5M50Dp01eqte1]x3Qa5 -l DOKCLU.log -stop_on_error -loadprocedure fast LOAD
(DB) INFO: connected to DB
(GSI) INFO: dbname = "ATD "
(GSI) INFO: vname = "DB6 "
(GSI) INFO: hostname = "UNKNOWN "
(GSI) INFO: sysname = "Windows NT"
(GSI) INFO: nodename = "SERVER"
(GSI) INFO: release = "5.2"
(GSI) INFO: version = "3790 Service Pack 1"
(GSI) INFO: machine = "4x AMD64 Level 6 (Mod 23 Step 7)"
(DB) ERROR: DDL statement failed
( DROP TABLE "DOKCLU" )
dsql_exec_immediate returned DS_DBOBJECTUNKNOWN
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
( CREATE TABLE "DOKCLU" ( "ID" SAPDB6CHAR(2) DEFAULT ' ' NOT NULL , "OBJECT" SAPDB6CHAR(60) DEFAULT ' ' NOT NULL , "LANGU" SAPDB6FIXCHAR(1) DEFAULT ' ' NOT NULL , "TYP" SAPDB6FIXCHAR(1) DEFAULT ' ' NOT NULL , "DOKVERSION" SAPDB6FIXCHAR(4) DEFAULT '0000' NOT NULL , "PAGENO" SMALLINT DEFAULT 0 NOT NULL , "TIMESTMP" SAPDB6CHAR(46) DEFAULT ' ' NOT NULL , "PAGELG" SMALLINT DEFAULT 0 NOT NULL , "VARDATA" VARCHAR(3800) FOR BIT DATA ) IN ATD#ES700D INDEX IN ATD#ES700I LONG IN ATD#ES700D )
dsql_exec_immediate returned DS_DBOBJECTUNKNOWN
(DB) INFO: disconnected from DB
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20091027104307
Thanks -
Error while installing the java add-on on abap system
Dear All,
We are trying to install java add-on with EP on present ABAP system, but getting struck up with error as below at creating java users (sapjsf) in central instance installation phase.
ENVIRONMENT:
ECC6.0
WIN 2003
KERNEL 136
SUPPORT PACK LEVEL AT 13
NETWEAVER 2004S SR1.
DB- ORACLE
error: ( usercheck.log)
java.lang.NoClassDefFoundError: com/sun/tools/javac/Main
Exception in thread "main" Reserved 1610612736 (0x60000000) bytes before loading DLLs.
Critical Error
Launching program failed
-> Internal program error (rc = -1)
error: (sapinst.log)
WARNING 2008-08-11 15:00:00
Execution of the command "C:\usr\sap\B60\DVEBMGS00\exe\jlaunch.exe UserCheck.jlaunch com.sap.security.tools.UserCheck "C:\Program Files\sapinst_instdir\ERP\LM\AS-JAVA\ADDIN\ORA\CENTRAL\CI\install\lib;C:\Program Files\sapinst_instdir\ERP\LM\AS-JAVA\ADDIN\ORA\CENTRAL\CI\install\sharedlib;C:\Program Files\sapinst_instdir\ERP\LM\AS-JAVA\ADDIN\ORA\CENTRAL\CI\install" -c sysnr=00 -c ashost=sapserver -c client=001 -c user=DDIC -c XXXXXX -a checkCreate -u SAPJSF -p XXXXXX -r SAP_BC_JSF_COMMUNICATION_RO -message_file UserCheck.message" finished with return code -1. Output:
java.lang.NoClassDefFoundError: com/sun/tools/javac/Main
Exception in thread "main" Reserved 1610612736 (0x60000000) bytes before loading DLLs.
Critical Error
Launching program failed
-> Internal program error (rc = -1)
INFO 2008-08-11 15:00:00
Removing file C:\Program Files\sapinst_instdir\ERP\LM\AS-JAVA\ADDIN\ORA\CENTRAL\CI\dev_UserCheck.
ERROR 2008-08-11 15:00:00
CJS-30197 . For more details see output of logfile:
ERROR 2008-08-11 15:00:00
FCO-00011 The step createJSF with step key |NW_Addin_CI|ind|ind|ind|ind|0|0|NW_CI_Instance|ind|ind|ind|ind|8|0|NW_CI_Instance_Doublestack|ind|ind|ind|ind|2|0|createJSF was executed with status ERROR .
Please help us out at your earliest convenience.
Thanks and warm regards,Dear Samrat Dangeti ,
Thanks.
Inst version: 701.
JDK version: 1.4.2_13
Regards, -
Error while Installing the Java Add-In for an Existing ABAP System
Hi all,
I need help, i am Installing the Java Add-In for an Existing ABAP System
SAPInst stops on the first installation step: "Central Services Instance (SCS) Java Add-In", the step is "Install common system files" on the following sub-steps:
These are the last few lines on the sapinst.log.
INFO 2009-05-21 12:35:12
Execute step createAccounts of component |NW_Addin_SCS|ind|ind|ind|ind|0|0|NW_Users_Create_Do|ind|ind|ind|ind|3|0.
INFO 2009-05-21 12:35:18
Execute step setUserEnvironment of component |NW_Addin_SCS|ind|ind|ind|ind|0|0|NW_Users_Create_Do|ind|ind|ind|ind|3|0.
INFO 2009-05-21 12:35:19
Execute step InstallJDBCDriver of component |NW_Addin_SCS|ind|ind|ind|ind|0|0|NW_JDBCDriver_DB4|ind|ind|ind|ind|4|0.
INFO 2009-05-21 12:35:19
Creating directory V:\sapmnt\BIQ\jdbc.
INFO 2009-05-21 12:35:19
Creating directory V:\sapmnt\BIQ\jdbc\tbx.
INFO 2009-05-21 12:35:21
Copied file 'V:/QIBM/ProdData/HTTP/Public/jt400/lib/jt400.jar' to 'V:/sapmnt/BIQ/jdbc/tbx/jt400.jar'.
INFO 2009-05-21 12:35:22
Execute step updateNtPatchDlls of component |NW_Addin_SCS|ind|ind|ind|ind|0|0|NW_System|ind|ind|ind|ind|5|0.
INFO 2009-05-21 12:35:23
Execute step sCreateSystemOS4 of component |NW_Addin_SCS|ind|ind|ind|ind|0|0|NW_System|ind|ind|ind|ind|5|0.
ERROR 2009-05-21 12:35:42
MOS-02001 Call of command "CRTR3SYS SID(BIQ) GLOBALHOST(*LOCAL)" failed. Exception is "CPF0006".
ERROR 2009-05-21 12:35:42
MOS-02001 Call of command "CRTR3SYS SID(BIQ) GLOBALHOST(*LOCAL)" failed. Exception is "CPF0006".
ERROR 2009-05-21 12:35:42
FCO-00011 The step sCreateSystemOS4 with step key |NW_Addin_SCS|ind|ind|ind|ind|0|0|NW_System|ind|ind|ind|ind|5|0|sCreateSystemOS4 was executed with status ERROR .
Thanks in advance for any help.
Kiran ChebroluHi,
Hope this note would solve your issue, please read carefully and validate with your issue
Note 1032019 - Java Add-In: Error when you create the SCS instance
below notes give your suffice information.
Note 883948 - NW 7.00(2004s): Inst.Add.Java Usage Types/Software Units
Note 1268493 - NW 7.01/BS 7: Inst.Add.Java Usage Types/Software Units
Note 1025789 - RUNR3CMD generates CPF0006
regards
nag -
I am trying to update my Itunes software on a Windows XP system and keep getting an error message saying the update can't locate "itunes.msi" where is that file located?
thanks, JudyThe servers are getting slammed by millions of people wanting to upgrade.. just give it some time, and soon enough you'll have your upgrade.
-
Oracle BI 11g: Error at the step - "Creating BI Server System Components"
I am attempting to install Oracle BI 11g on a Windows VM. The installation process completes successfully. However, the configuration process errors out at the step - Creating BI Server System Components. The last entry in the install log is as below:
[2010-09-24T18:26:12.107+05:30] [as] [NOTIFICATION] [] [oracle.as.install.bi] [tid: 26] [ecid: 0000Ih3l5E00vlx6wBedMG1Cb79200000H,0] Install handler params :-componentName coreapplication_obis1 -componentType OracleBIServerComponent -biApplicationName coreapplication -fmwConfigPath C:\Middleware\user_projects\domains\bifoundation_domain\config\fmwconfig -appServerUsername <Secure value. Cannot be logged> -appServerPassword <Secure value. Cannot be logged> -appServerAdminPort 7001 -appServerManagedPort 9704 -systemAdministratorUsername <Secure value. Cannot be logged> -systemAdministratorPassword <Secure value. Cannot be logged> -repositoryPassword <Secure value. Cannot be logged> -biServerRepositoryFile SampleAppLite.rpd -biPresentationServicesCatalogName SampleAppLite -biPresentationServicesCatalogZipFileName SampleAppLiteCatalog.zip -biSchedulerSchemaUser <Secure value. Cannot be logged> -biSchedulerSchemaPassword <Secure value. Cannot be logged> -actionFrameworkWorkflowServer http://host-name:7001 -actionFrameworkWorkflowService ANALYTICS -actionFrameworkWorkflowSystem obiaftests -databaseType Microsoft SQL Server -connectString sqlservername:port:db -autoCreatePorts -biServerPort 9703 -biServerMonitorPort 9701 -biPresentationServerPort 9710 -biClusterControllerPort 9706 -biClusterControllerMonitorPort 9700 -biJavaHostPort 9810 -biSchedulerPort 9705 -biSchedulerMonitorPort 9708 -biSchedulerScriptRPCPort 9707 -portRangeStart 9700 -portRangeEnd 10000 -skipDomainProvisioning true
The resource utilization seems to be normal. Netstat confirms that all of the above ports are free. Since there is no explicit error message in the log, we are unable to decipher the exact source for this error.
Virtual Machine details: Intel Xeon @ 2.67 GHz, Windows Server 2003 SP2, 4GB RAM, 50GB HDD, Static IP
Oracle BI Schema DB: MS SQL Server
Any inputs on this error will be greatly appreciated.
Edited by: OBIGuy on Sep 27, 2010 2:37 PMHi,
I recenty started instaling OBIEE 11g and got the same error : "Creating BI server system components". I read your solution and would like to know that if this patch is okay to install on a Windows VM (win server 2003 EE, SP2). If yes, after rebooting, do we reinstall ?
I am also getting the following errors:
-Executing: opmnctl start coreapplication_obiccs1
-Executing: opmnctl start coreapplication_obis1
-Executing: opmnctl start coreapplication_obips1
-Executing: opmnctl start coreapplication_obisch1
Thanks in advance.
HG -
Using SQL Server 2008 R2. Tempdb resides on disks W and X
both of those are 250 GB each. Nothing else resides on these disks. The recovery mode for tempdb is set to Simple and is split in 8 files and one log file. Each of the tempdb file is set for auto growth by 128 MB and max size is unlimited. The log file is
set for auto growth by 10% and max size unlimited.
I get the following error at least once a week while running an ETL:
[SQLSTATE 01003] (Message 8153) Could not allocate space for object '<temporary system object: 335532118192937>' in database 'tempdb' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup,
adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup. [SQLSTATE 42000] (Error 50000). The step failed.
I have to then shrink the tempdb log and files to create space on the disks.
What is a permanent solution to this problem, I don't want my ETL to break due to TempDB diskspace full.
Thanks in advance.Hi,
Permanent solution would be finding out query which is causing tempdb log file to grow out of proportion and fill it and I would like you to take help of below article
Troubleshooting out of space issue in Tempdb
Please change Autogrowth value for Log file from 10 % to may be 100 M. This is just a tentative value you need to study
growth of tempdb to reach to correct value. You kept 128 MB autogrowth for tempdb data file is this value tentative or you just put it.
Below article can be referred for tempdb details
Working with tempdb
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles -
Create a Connection on TREX for 2 systems with same SID
Hello world,
Here is my case,
We have a PRO systems With SID=PRO On Host= production , and a Sandbox system with also SID=PRO On Host=SANDBOX
now i need to create a connection in TREX in parallel so when i add the 2nd one it just edits the 1st one that i have already made
So is it possible to create 2 connection of same SID but diffrent Hosts In parallel?
If Yes how ?
Thanks In Advance...
Ahmed SalamHi Ahmed,
it could be possible from the TREX perspective , however such configuration isn't supported . The reason for this is that the SAP applications create indexes using the ABAP system ID and client as a part of the index names (f.e. esh:e10002~e10002~acc_sid~sid). As it's not possible to create an index with the same name 2nd time, you will not be able to use the TREX instance with two systems with same SID.
Best regards,
Mikhail -
Where are TREX index stored? TREX server File system? or KM repository?
hi, friends:
can someone tell me where are TREX index stored ?
in TREX server file system?
or in portal KM repository? file system or DB?
thank you
CarolCarol,
TREX is a separate product. During installation and configuration of TREX you connect it to the portal. The search iViews of the portal will use the configured TREX server to do the actual search:
SAP Help: http://help.sap.com/saphelp_nw70/helpdata/EN/a4/929d4206b70931e10000000a1550b0/content.htm
The index is stored on the TREX server: TREX/IndexServer/basepath/index=%(SAP_RETRIEVAL_PATH)/index
SAP Help: http://help.sap.com/saphelp_nw70/helpdata/EN/4c/d91e40777cdd5fe10000000a155106/content.htm
br,
Tobias -
Some errors after doing the system copy for DB2 database instance
HI,
Recently we have transferred the DB2 database instance from old host( db 9.1.7 under windows 2003 R2) to new host( DB2 9.7.9 under windows 2008 R2) using the system copy database depending methods.
Currently system is:
* ECC 6.0 under NW 7.0 SR3
* Kernel : 7.20
* Basis: 7.0 with support package level 17
*application instance connecting db instance via DB2 CLI
1) a) After log in system using the T-code: SM21 to read the system log, it will record the bellow error:
b) From the log taken from log fie: dev_w*, i also found the below error:
A ABAP Program SAPMSSY2 .
A Source RSBTCTRC Line 60.
A Error Code DBIF_RSQL_SQL_ERROR.
A Module $Id: //bas/720_REL/src/krn/runt/absapsql.c#28 $ SAP.
A Function ab_HandleRsqlErrors Line 716.
A ** RABAX: level LEV_RX_STDERR completed.
A ** RABAX: level LEV_RX_RFC_ERROR entered.
A ** RABAX: level LEV_RX_RFC_ERROR completed.
A ** RABAX: level LEV_RX_RFC_CLOSE entered.
A ** RABAX: level LEV_RX_RFC_CLOSE completed.
A ** RABAX: level LEV_RX_IMC_ERROR entered.
A ** RABAX: level LEV_RX_IMC_ERROR completed.
A ** RABAX: level LEV_RX_DATASET_CLOSE entered.
A ** RABAX: level LEV_RX_DATASET_CLOSE completed.
A ** RABAX: level LEV_RX_ERROR_SAVE entered.
A ** RABAX: level LEV_RX_ERROR_SAVE completed.
A ** RABAX: level LEV_RX_ERROR_TPDA entered.
A ** RABAX: level LEV_RX_ERROR_TPDA completed.
A ** RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.
A ** RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.
A ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.
A ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.
A ** RABAX: level LEV_RX_END entered.
A ** RABAX: level LEV_RX_END completed.
A ** RABAX: end no http/smtp
A ** RABAX: end RX_BTCHLOG|RX_VBLOG
A SQL error in the database when accessing a table..
c) any background job will be cancelled when it is running. I think the error is related to above mentioned issue.
2) If i go to T-code: DB13---Diagnostics----db2 logs, it will come out the below error:
Thanks.HI Manas,
Yes, this problem is with particular this table.
Refer to below error coming from db2diag.log when i access the table:BTCCTL:
2014-08-12-17.52.08.866000+480 I35784932F1196 LEVEL: Severe
PID : 3380 TID : 2676 PROC : db2syscs.exe
INSTANCE: DB2DV1 NODE : 000 DB : DV1
APPHDL : 0-127 APPID: *LOCAL.DB2DV1.140812095207
AUTHID : DB2DV1
EDUID : 2676 EDUNAME: db2agent (DV1) 0
FUNCTION: DB2 UDB, data management, sqldSetupIndexScan, probe:1873
MESSAGE : ZRC=0x82040001=-2113667071=SQLD_NONSEVERE_PRGERR
"non-severe dms programming error"
DIA8532C An internal processing error has occurred.
DATA #1 : String, 39 bytes
Specified index not found for scan open
DATA #2 : String, 12 bytes
sqldScanOpen
CALLSTCK:
[0] 0x000000018010E989 pdLog + 0x353
[1] 0x0000000003ABE3C2 sqlzSetAndLog901 + 0x192
[2] 0x0000000001E61F01 sqldSetupIndexScan + 0xF37
[3] 0x0000000001E5F5CC sqldScanOpen + 0xBEE
[4] 0x000000000334F460 sqlriopn + 0x316
[5] 0x00000000034AE788 sqlritaSimplePerm + 0x252
[6] 0x000000000336AC8B sqlriSectInvoke + 0x139
[7] 0x00000000030A6F0C sqlrr_process_fetch_request + 0x1A8
[8] 0x00000000030A2902 sqlrr_open + 0x534
[9] 0x000000000223FCCB sqljs_ddm_opnqry + 0x447
2014-08-12-17.52.08.866000+480 I35786130F533 LEVEL: Error
PID : 3380 TID : 2676 PROC : db2syscs.exe
INSTANCE: DB2DV1 NODE : 000 DB : DV1
APPHDL : 0-127 APPID: *LOCAL.DB2DV1.140812095207
AUTHID : DB2DV1
EDUID : 2676 EDUNAME: db2agent (DV1) 0
FUNCTION: DB2 UDB, data management, sqldSetupIndexScan, probe:1873
DATA #1 : unsigned integer, 4 bytes
10
DATA #2 : unsigned integer, 4 bytes
1704
DATA #3 : unsigned integer, 2 bytes -
New ECC 6.0 system on z/OS - DB2 - good choice?
Hi
We are considering a new ECC 6.0 system on z/OS - DB2. Any experiences with the advantages/disadvantages of this platform would be most helpful.
Thanks in advance.
MikeOmer certainly has more experience with DB2 for z/OS and running SAP on it. He has written lots of great articles on ittoolbox that have been really helpful. In response to his post:
1. rdisp/wp_auto_restart is defaulted to zero, meaning that SAP will never automatically restart a work process. SAP note 101717 (which details how/why to change the default) says "The solution described here should only be used if all other options are exhausted since this is not an elimination of the actual cause of the problem but only a workaround.". I have not personally experienced needing to change this parameter from the default outside of DB2 for z/OS. It is recommended in the SAP for DB2 z/OS Admin Guide to set this parameter to the equivalent of 1 day in seconds. This would seem to acknowledge either a known and unfixed memory leak in DB2 for z/OS (up to and including v9), or is perhaps a precaution because of the 2 gig thread storage limit. As I stated before, it adds no value and causes useless reconnect information to be put into the SM21 system logs.
2. I think perhaps our issue with extents is because our storage system was not setup from the beginning to enable extent constraint relief. Setting the secondary extent quantity to a sufficient size for each tablespace is certainly one way to ensure that extents don't become a problem. With over 70,000 tables in ECC 6.0, even trying to manage 1% of the tables this way could be quite time consuming. Setting ZPARM MGEXTSZ to the SAP recommended value of yes allows DB2 to use the sliding algorithm and make each additional secondary extent bigger and bigger. Even so, we've had surprises (and thanks to Murphy usually off-hours) where there was still plenty of space left on our DB2 volumes but the total number of extents for a particular dataset or the total extents on a non-full volume exceeded the maximum. All that really says is that SAP on DB2 for z/OS appears to require more careful storage monitoring than on other platforms. It does allow for more flexibility, however.
3. Being able to manage individual tables and/or tablespaces is an advantage, though it does not come without the cost of additional overhead for the DBA. As for restoring and individual table, this is certainly possible but it would be best practice to work with SAP support to make sure all table dependencies are resolved and that data integrity is maintained when restoring an individual table. The DBA should not be expected to know about all of the table relationships with the 70,000 tables in ECC 6.0. That would seem to limit the advantages of an individual table restore.
4 & 5. I don't have a lot of experience with virtual memory monitoring on z/OS, but I can understand why it would have vastly superior capabilities compared to other platforms. When memory is expensive (as in thousands of dollars per gigabyte) and when DB2 still has some components which are restricted to 2 gig, it absolutely makes sense to have very detailed tools to manage memory usage.
Regarding sizing... I'm sure that mistakes are made quite often regardless of platform. It was exactly my point that it does not usually add significant cost to increase the resources on commodity hardware. My experience has been that commodity hardware vendors usually size the hardware too big anyway. Whether that is to allow some flexibility or simply to increase their sales, I am not sure. Contrast that to this recent success story for SAP on zSeries:
http://www-01.ibm.com/software/success/cssdb.nsf/cs/STRD-7NGMA9?OpenDocument&Site=gicss67sap&cty=en_us
"Colacem had to come up with more money for the upgrade - but IBM offered it to us at a price that we regard as very fair"
This customer had to upgrade to a Z10 after their Z9 ran out of gas, right in the middle of their first SAP implementation. I can only guess that the additional cost was not insignificant.
6. Thus far we have not experienced any strange problems with other databases and SAP, but we are using database versions that have been certified by SAP for 4+ years. In fairness though, we're not a huge implementation with individual tables in the terabytes.
Being on a platform with a small percentage customers has its disadvantages in trying to get product changes made as well. As an example, where is the Adobe Document Services support for Linux on zSeries? I know of at least one other customer that wanted this. Although adobe is now available for other 64bit platforms that run SAP, it is still not available for Linux on zSeries.
There is also the issue of third party SAP partners (Vertex, BSI, SAP's own WWI product) and the platforms they support. Very few support Linux for zSeries, so there will be additional commodity hardware servers in the datacenter. That results in the added complexity of supporting more platforms.
The one area of concern I do have about running SAP on a non-zSeries platform is the quality of SAP support for other platforms. The zSeries SAP support team is phenomenal and I can't say we've gotten even close to the response times or the quality of answers for non-zSeries related OSS messages.
All that said, I am just offering one person's experiences and opinions. Obviously I am not overly impressed with the value delivered vs the cost of zSeries.
Brian -
Can we install TREX on our system
Hi, we have installed TREX on a system with release number 700, can we install it on a system with release number 620 ?
Hi,
In the documentation it says;
Configuration of the RFC connection with the TREX admin tool (stand-alone) is only available as of
SAP Basis Component SAP_BASIS 6.20 SP58, 6.40 SP16, and 7.0 SP6.
Don't worry if you patch level is lower.
It means that you can not generate RFC-connection to you 6.20 system automatically.
The same documentation says:
If you are using TREX with an SAP system based on an earlier support package,
you have to configure the RFC connection manually as described in the SAP NetWeaver 04 Installation Guide
for Search and Classification (TREX) 6.1.
You can find this guide on the SAP Service Marketplace at service.sap.com/instguides
- SAP NetWeaver Release 04
- Installation
- Cross-NW
- Installation Guide Search and Classification TREX 6.1.
You can find this information
[at this link|http://help.sap.com/saphelp_nw04s/helpdata/en/40/83505303bd5616e10000000a114cbd/frameset.htm]
Then the following path:
- Search and Classification.
- TREX 7.0 for SAP Netweaver 7.0.
- TREX Configuration.
- Post-installation Configuration.
- Server side.
- Configuration of the RFC connection.
- Configuring the RFC connection in the TREX admin tool. -
Can use STSongStd-Light-Acro.otf font in unix system(aix)
In unix system (aix 5.3)
as 10.1.2
NLS_LANG=AMERICAN_AMERICA.ZHS16GBK (chinese charater)
Now run report, output charaters is not right，why?
In windows system,I modify uifont.ali file,as the follow
[ PDF ]
.....ZHS16GBK = "STSongStd-Light-Acro"
and the report run well,but the same config in unix system (aix 5.3),output charaters is error.
why?
Can anyone tell me step by step?
Thanks in advance!Welcome to OTN
Check the two link..
1. Re: Oracle Reports 10g Fonts issue
2. Re: Adding new font to my Reports Setup
Hope this will help you
Hamid
If someone's response is helpful or correct, please mark it accordingly. -
OUI-18001:operating system AIX is not supported.
Hi All,
I am installing my NW 7.0 SR2 system on AIX and oracle 10.2.0.2.
During database installation, when RUNINSTALLER is doing the prerequisite check it is showing me error:
OUI-18001: operating system AIX is not supported.
My AIX system is of version 5300-10-01.
Its very strange that it is giving error for AIX 5.3 ML 10. And in log it is showing that tool is expecting result 5200.004 or 5300.002.
Is it true that for AIX 5.3 ML 10 is not supported for oracle ?
Thanks
SunnyDear Sunny,
As an alternative, you can adjust oraparam.ini file with your operating system version detail.
Please refer the following SAP Notes carefully :
[SAP Note 980426 - Oracle 10.2 Software installation on new operating systems|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=980426]
[SAP Note 833766 - Oracle Database 10g: Software installation problems 10.1.0|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=833766]
I hope this info. will be helpful.
Regards,
Bhavik G. Shroff
Maybe you are looking for
-
ISU-Installment Plan item in Invoice
Hi, We are rolling out installment plan and were able to create the standard installment plan. The present Invoice has 3 heads i.e. 1)Current month amount, 2) Outstanding and Net Amount Due (Total of 1& 2) The business requirement is to add the insta
-
I have to guess where the comma is the @ sign is and various signals now tell what am i doing wrong on the apple usb keyboard
-
Hi all, I am using SRM 3.5(EBP 3.0)with ITS and R/3 4.7. While executing the service "Create shopping cart",after ordering the item i.e. saving the shopping cart,the approval workflow is executed but when i login as the approver and go to the wor
-
Troubles with Outlook calendar and icloud
I just uninstalled icloud from my pc after it messed up Outlook. Now all my existing calendar dates have migrated to the "icloud calendar" and have left the original calendar that I created. How do I get the dates back to the original calendar?
-
Installing optional content on a different hard drive
Hey, I'm about to install Final Cut Studio 5.1 on my computer and i have a quick question. Will installing the optional content (Apple loops, fonts, tutorials...) on a different drive than the boot drive that i am installing Final Cut Pro on, negativ