on 06-14-2004 4:39 AM
Hello,
I am having trouble in installing WebAS 6.3(ABAP+J2EE) , getting these error messages in Deploy via SDM/J2EE step.
MUT-02041 SDM call of deploySdaList ends with returncode 4. See output of logfile /sapinstdir/dev/WAS/callSdmViaSapinst
.log
the content of callSdmViaSapinst.log is
-
Jun 14, 2004 12:00:10... Info:
Jun 14, 2004 12:00:10... Info: ============================================
Jun 14, 2004 12:00:10... Info: = Starting to execute command 'deploy' =
Jun 14, 2004 12:00:10... Info: ============================================
Jun 14, 2004 12:00:10... Info: Starting SDM - Software Deployment Manager...
Jun 14, 2004 12:00:11... Info: tc/SL/SDM/SDM/sap.com/SAP AG/6.30.20030716102041.0000
Jun 14, 2004 12:00:12... Info: SDM operation mode successfully set to: Standalone
Jun 14, 2004 12:00:13... Info: Connecting to database "KED".
Jun 14, 2004 12:00:13... Info: Connected to database "KED".
Jun 14, 2004 12:00:14... Info: Initializing Network Manager (50017)
Jun 14, 2004 12:00:14... Info: Checking if another SDM is running on port 50018
Jun 14, 2004 12:00:14... Info: -
Starting deployment -
Jun 14, 2004 12:00:14... Info: Loading selected archives...
Jun 14, 2004 12:00:14... Info: Loading archive '/instcd/j2eecd/J2EE-ENG/JDD/J2EE_JDDSCHEMA.SDA'
Jun 14, 2004 12:00:15... Info: Loading archive '/instcd/j2eecd/J2EE-ENG/JDD/SYNCLOG.SDA'
Jun 14, 2004 12:00:15... Info: Loading archive '/instcd/j2eecd/J2EE-ENG/JDD/COM.SAP.SECURITY.DBSCHEMA.SDA'
Jun 14, 2004 12:00:15... Info: Loading archive '/instcd/j2eecd/J2EE-ENG/JDD/XML_DAS_SCHEMA.SDA'
Jun 14, 2004 12:00:15... Info: Loading archive '/instcd/j2eecd/J2EE-ENG/JDD/JMS_JDDSCHEMA.SDA'
Jun 14, 2004 12:00:15... Info: Selected archives successfully loaded.
Jun 14, 2004 12:00:15... Info: OnErrorStop
Jun 14, 2004 12:00:15... Info: Starting to execute deployment action com.sap.security.dbschema
Jun 14, 2004 12:00:18... Info: 12:00:15 2004-06-14 dbs-Info: <<<<<<<<<<<<<< Table Deployment >>>>>>>>>>>>>
Jun 14, 2004 12:00:18... Info: 12:00:16 2004-06-14 dbs-Info: >>> Create required runtime tables <<<
Jun 14, 2004 12:00:18... Info: 12:00:16 2004-06-14 dbs-Info: <<< Analyze table BC_DDDBRTH >>>
Jun 14, 2004 12:00:18... Info: 12:00:16 2004-06-14 dbs-Info: No action required for table
Jun 14, 2004 12:00:18... Info: 12:00:16 2004-06-14 dbs-Info: <<< Analyze table BC_DDDBTABLERT >>>
Jun 14, 2004 12:00:18... Info: 12:00:16 2004-06-14 dbs-Info: No action required for table
Jun 14, 2004 12:00:18... Info: 12:00:16 2004-06-14 dbs-Info: <<< Analyze table BC_DDDBRTH >>>
Jun 14, 2004 12:00:18... Info: 12:00:16 2004-06-14 dbs-Info: No action required for table
Jun 14, 2004 12:00:18... Info: 12:00:16 2004-06-14 dbs-Info: <<< Analyze table BC_DDDBRTX >>>
Jun 14, 2004 12:00:18... Info: 12:00:16 2004-06-14 dbs-Info: No action required for table
Jun 14, 2004 12:00:18... Info: 12:00:16 2004-06-14 dbs-Info: >>> Analyze tables from archive in database ORACLE
Jun 14, 2004 12:00:18... Info: 12:00:16 2004-06-14 dbs-Info: Next archive object : UME_ACL_ACL.gdbtable
Jun 14, 2004 12:00:18... Info: 12:00:16 2004-06-14 dbs-Info: <<< Analyze table UME_ACL_ACL >>>
Jun 14, 2004 12:00:18... Info: 12:00:16 2004-06-14 dbs-Info: No action required for table
Jun 14, 2004 12:00:18... Info: 12:00:17 2004-06-14 dbs-Info: Runtime XML of UME_ACL_ACL successfully written
Jun 14, 2004 12:00:18... Info: 12:00:17 2004-06-14 dbs-Info: Runtime XML of UME_ACL_ACL successfully written
Jun 14, 2004 12:00:18... Info: 12:00:17 2004-06-14 dbs-Info: Next archive object : UME_ACL_ACLENTRY.gdbtable
Jun 14, 2004 12:00:18... Info: 12:00:17 2004-06-14 dbs-Info: <<< Analyze table UME_ACL_ACLENTRY >>>
Jun 14, 2004 12:00:18... Info: 12:00:17 2004-06-14 dbs-Info: No action required for table
Jun 14, 2004 12:00:18... Info: 12:00:17 2004-06-14 dbs-Info: Runtime XML of UME_ACL_ACLENTRY successfully written
Jun 14, 2004 12:00:18... Info: 12:00:17 2004-06-14 dbs-Info: Runtime XML of UME_ACL_ACLENTRY successfully written
Jun 14, 2004 12:00:18... Info: 12:00:17 2004-06-14 dbs-Info: Next archive object : UME_ACL_MANAGER.gdbtable
Jun 14, 2004 12:00:18... Info: 12:00:17 2004-06-14 dbs-Info: <<< Analyze table UME_ACL_MANAGER >>>
Jun 14, 2004 12:00:18... Info: 12:00:17 2004-06-14 dbs-Info: No action required for table
Jun 14, 2004 12:00:18... Info: 12:00:17 2004-06-14 dbs-Info: Runtime XML of UME_ACL_MANAGER successfully written
Jun 14, 2004 12:00:18... Info: 12:00:17 2004-06-14 dbs-Info: Runtime XML of UME_ACL_MANAGER successfully written
Jun 14, 2004 12:00:18... Info: 12:00:17 2004-06-14 dbs-Info: Next archive object : UME_ACL_OWNER.gdbtable
Jun 14, 2004 12:00:18... Info: 12:00:17 2004-06-14 dbs-Info: <<< Analyze table UME_ACL_OWNER >>>
Jun 14, 2004 12:00:18... Info: 12:00:17 2004-06-14 dbs-Info: No action required for table
Jun 14, 2004 12:00:18... Info: 12:00:17 2004-06-14 dbs-Info: Runtime XML of UME_ACL_OWNER successfully written
Jun 14, 2004 12:00:18... Info: 12:00:17 2004-06-14 dbs-Info: Runtime XML of UME_ACL_OWNER successfully written
Jun 14, 2004 12:00:18... Info: 12:00:17 2004-06-14 dbs-Info: Next archive object : UME_ACL_PERM.gdbtable
Jun 14, 2004 12:00:18... Info: 12:00:17 2004-06-14 dbs-Info: <<< Analyze table UME_ACL_PERM >>>
Jun 14, 2004 12:00:18... Info: 12:00:17 2004-06-14 dbs-Info: No action required for table
Jun 14, 2004 12:00:18... Info: 12:00:17 2004-06-14 dbs-Info: Runtime XML of UME_ACL_PERM successfully written
Jun 14, 2004 12:00:18... Info: 12:00:17 2004-06-14 dbs-Info: Runtime XML of UME_ACL_PERM successfully written
Jun 14, 2004 12:00:18... Info: 12:00:17 2004-06-14 dbs-Info: Next archive object : UME_ACL_PERM_MEM.gdbtable
Jun 14, 2004 12:00:18... Info: 12:00:17 2004-06-14 dbs-Info: <<< Analyze table UME_ACL_PERM_MEM >>>
Jun 14, 2004 12:00:18... Info: 12:00:18 2004-06-14 dbs-Info: No action required for table
Jun 14, 2004 12:00:18... Info: 12:00:18 2004-06-14 dbs-Info: Runtime XML of UME_ACL_PERM_MEM successfully written
Jun 14, 2004 12:00:18... Info: 12:00:18 2004-06-14 dbs-Info: Runtime XML of UME_ACL_PERM_MEM successfully written
Jun 14, 2004 12:00:18... Info: 12:00:18 2004-06-14 dbs-Info: Next archive object : UME_ACL_SUP_PERM.gdbtable
Jun 14, 2004 12:00:18... Info: 12:00:18 2004-06-14 dbs-Info: <<< Analyze table UME_ACL_SUP_PERM >>>
Jun 14, 2004 12:00:18... Info: 12:00:18 2004-06-14 dbs-Info: No action required for table
Jun 14, 2004 12:00:18... Info: 12:00:18 2004-06-14 dbs-Info: Runtime XML of UME_ACL_SUP_PERM successfully written
Jun 14, 2004 12:00:18... Info: 12:00:18 2004-06-14 dbs-Info: Runtime XML of UME_ACL_SUP_PERM successfully written
Jun 14, 2004 12:00:18... Info: 12:00:18 2004-06-14 dbs-Info: Next archive object : UME_BLOBS.gdbtable
Jun 14, 2004 12:00:18... Info: 12:00:18 2004-06-14 dbs-Info: <<< Analyze table UME_BLOBS >>>
Jun 14, 2004 12:00:18... Info: 12:00:18 2004-06-14 dbs-Info: No action required for table
Jun 14, 2004 12:00:18... Info: 12:00:18 2004-06-14 dbs-Info: Runtime XML of UME_BLOBS successfully written
Jun 14, 2004 12:00:18... Info: 12:00:18 2004-06-14 dbs-Info: Runtime XML of UME_BLOBS successfully written
Jun 14, 2004 12:00:18... Info: 12:00:18 2004-06-14 dbs-Info: Next archive object : UME_STRINGS.gdbtable
Jun 14, 2004 12:00:18... Info: 12:00:18 2004-06-14 dbs-Info: <<< Analyze table UME_STRINGS >>>
Jun 14, 2004 12:00:18... Info: 12:00:18 2004-06-14 dbs-Info: No action required for table
Jun 14, 2004 12:00:18... Info: 12:00:18 2004-06-14 dbs-Info: Runtime XML of UME_STRINGS successfully written
Jun 14, 2004 12:00:18... Info: 12:00:18 2004-06-14 dbs-Info: Runtime XML of UME_STRINGS successfully written
Jun 14, 2004 12:00:18... Info: 12:00:18 2004-06-14 dbs-Info: Next archive object : UME_USERNUMBER.gdbtable
Jun 14, 2004 12:00:18... Info: 12:00:18 2004-06-14 dbs-Info: <<< Analyze table UME_USERNUMBER >>>
Jun 14, 2004 12:00:18... Info: 12:00:18 2004-06-14 dbs-Info: No action required for table
Jun 14, 2004 12:00:18... Info: 12:00:18 2004-06-14 dbs-Info: Runtime XML of UME_USERNUMBER successfully written
Jun 14, 2004 12:00:18... Info: 12:00:18 2004-06-14 dbs-Info: Runtime XML of UME_USERNUMBER successfully written
Jun 14, 2004 12:00:18... Info: 12:00:18 2004-06-14 dbs-Info: Next archive object : UME_USERSYNC.gdbtable
Jun 14, 2004 12:00:18... Info: 12:00:18 2004-06-14 dbs-Info: <<< Analyze table UME_USERSYNC >>>
Jun 14, 2004 12:00:18... Info: 12:00:18 2004-06-14 dbs-Info: Action: CONVERT
Jun 14, 2004 12:00:18... Info: 12:00:18 2004-06-14 dbs-Info: Table has to be converted
Jun 14, 2004 12:00:18... Info:
Jun 14, 2004 12:00:18... Info: E R R O R ******* (DbModificationManager)
Jun 14, 2004 12:00:18... Info: 12:00:18 2004-06-14 dbs-Error: Table conversion currently not possible
Jun 14, 2004 12:00:18... Info: 12:00:18 2004-06-14 dbs-Info: Next archive object : UME_USERSYNCLOCK.gdbtable
Jun 14, 2004 12:00:18... Info: 12:00:18 2004-06-14 dbs-Info: <<< Analyze table UME_USERSYNCLOCK >>>
Jun 14, 2004 12:00:18... Info: 12:00:18 2004-06-14 dbs-Info: Action: CONVERT
Jun 14, 2004 12:00:18... Info: 12:00:18 2004-06-14 dbs-Info: Table has to be converted
Jun 14, 2004 12:00:18... Info:
Jun 14, 2004 12:00:18... Info: E R R O R ******* (DbModificationManager)
Jun 14, 2004 12:00:18... Info: 12:00:18 2004-06-14 dbs-Error: Table conversion currently not possible
Jun 14, 2004 12:00:18... Info: 12:00:18 2004-06-14 dbs-Info: Next archive object : UME_USERSYNCTEMP.gdbtable
Jun 14, 2004 12:00:18... Info: 12:00:18 2004-06-14 dbs-Info: <<< Analyze table UME_USERSYNCTEMP >>>
Jun 14, 2004 12:00:18... Info: 12:00:18 2004-06-14 dbs-Info: No action required for table
Jun 14, 2004 12:00:18... Info: 12:00:18 2004-06-14 dbs-Info: Runtime XML of UME_USERSYNCTEMP successfully written
Jun 14, 2004 12:00:18... Info: 12:00:18 2004-06-14 dbs-Info: Runtime XML of UME_USERSYNCTEMP successfully written
Jun 14, 2004 12:00:18... Info: 12:00:18 2004-06-14 dbs-Info: Analysis and adjustment of tables finished with errors
Jun 14, 2004 12:00:18... Info: Deployment action com.sap.security.dbschema executed.
Jun 14, 2004 12:00:18... Error: Execution of deployment com.sap.security.dbschema aborted.
No further description found.
Jun 14, 2004 12:00:19... Error: Deployment NOT successful for com.sap.security.dbschema
Jun 14, 2004 12:00:19... Error: -
At least one of the Deployments failed -
Jun 14, 2004 12:00:19... Info: Summarizing the deployment results:
Jun 14, 2004 12:00:19... Info: Already Deployed: /instcd/j2eecd/J2EE-ENG/JDD/J2EE_JDDSCHEMA.SDA
Jun 14, 2004 12:00:19... Info: Already Deployed: /instcd/j2eecd/J2EE-ENG/JDD/SYNCLOG.SDA
Jun 14, 2004 12:00:19... Error: Aborted: /instcd/j2eecd/J2EE-ENG/JDD/COM.SAP.SECURITY.DBSCHEMA.SDA
Jun 14, 2004 12:00:19... Error: Admitted: /instcd/j2eecd/J2EE-ENG/JDD/XML_DAS_SCHEMA.SDA
Jun 14, 2004 12:00:19... Info: Already Deployed: /instcd/j2eecd/J2EE-ENG/JDD/JMS_JDDSCHEMA.SDA
Jun 14, 2004 12:00:19... Error: Processing error. Return code: 4
-
Our System informations are
- HP-UX 11.11
- Oracle 9.2.0.4
- JDK 1.3.1.13
I already checked Issue 1003 in FAQ documens, but i can not resolved the problem.
please your support.
Thanks,
bk
Message was edited by: bk lim
Hello,
the last entries in your posted error log seem to indicate that there was an older installation on your system. If yes, you should check if everything has been uninstalled completely/correctly before proceeding to an upgrade/new installation. If no: Please be more specific about the error occured.
Regards
Klaus
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, I am getting the below error when trying to deploy Content Management Support Package 11. It occurs only with JDDSCHEMA SDA files. all other SDA got deployed fine.
22:04:08 2005-04-14 dbs-Info: $Id: //tc/DictionaryDatabase/630_VAL_REL/src/_dictionary_database_dbs/java/com/sap/dictionary/database/dbs/DbModificationManager.java#1 $
22:04:08 2005-04-14 dbs-Info: <<<<<<<<<<<<<< Table Deployment >>>>>>>>>>>>>
22:04:08 2005-04-14 dbs-Info:
22:04:08 2005-04-14 dbs-Info: <<< Analyze table BC_DDDBRTH >>>
E R R O R ******* (DbMssTable)
22:04:08 2005-04-14 mss-Error: setColumnsViaDb failed: <null>
E R R O R ******* (DbModificationManager)
22:04:08 2005-04-14 dbs-Error:
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.