cancel
Showing results for 
Search instead for 
Did you mean: 

Java ADD-IN installation problem

Former Member
0 Kudos

Hi All,

I have just upgraded BW 3.1c to NW04s SR1 release. I am now trying to install the Java component with usage type BI java, EP and AS java. The SCS and DB steps went in very smooth. When i got to CI install, i got a problem with deployment of SCA files. Basically, the install failed at the "install software units" step. The error I have in the sapinst_dev.log is -


Info: -


Deployment was successful -


Info: Summarizing the deployment results:

Error: Admitted: /software2/nw04supgSR1/java/J2EE_OSINDEP/UT/EPBC06_0.SCA

Processing error. Return code: 4

Error: Processing error. Return code: 4

WARNING 2006-09-29 14:02:44

CJSlibModule::writeWarning_impl()

SDM call of deploySdaList ends with returncode 4. See output of logfile /usr/sap/put/install/sapinst_instdir/NW04S/LM/AS-JAVA/ADDIN/ORA/CENTRAL/CI/callSdmViaSapinst.log.

ERROR 2006-09-29 14:02:44

CJSlibModule::writeError_impl()

CJS-30156 SDM deployment failed for at least one of the components to deploy.<br> SOLUTION: Check '/usr/sap/put/install/sapinst_instdir/NW04S/LM/AS-JAVA/ADDIN/ORA/CENTRAL/CI/callSdmViaSapinst.log' for more information.

ERROR 2006-09-29 14:02:44

FCO-00011 The step enableUsageTypes with step key |NW_Addin_CI|ind|ind|ind|ind|0|0|SAP_Software_Features_Enablement|ind|ind|ind|ind|11|0|enableUsageTypes was executed with status ERROR .

-


And, what i have in callSdmViaSapinst.log is -


Sep 29, 2006 2:02:43 PM Info: Initial deployment: Selected development componen

t 'com.sapportals.prt.portalruntime'/'sap.com'/'SAP AG'/'7.0006.20060301194711.0

000' will be deployed.

Sep 29, 2006 2:02:43 PM Info: Ending deployment prerequisites. All items are co

rrect.

Sep 29, 2006 2:02:43 PM Error: An error occured while storing the cluster insta

nces.

Sep 29, 2006 2:02:43 PM Error: There is no control instance running in the clus

ter:

Name:JM_T1159556563390_1_bowie

Host:bowie

State:5

HostAddress:138.126.81.41

Please check if there are running cluster instances.

Sep 29, 2006 2:02:43 PM Error: Received exception when saving current Engine st

ate: There is no control instance running in the cluster:

Name:JM_T1159556563390_1_bowie

Host:bowie

State:5

HostAddress:138.126.81.41

Sep 29, 2006 2:02:43 PM Error: Aborted: development component 'com.sap.pcd.dbsc

hema'/'sap.com'/'SAP AG'/'7.0006.20060301194711.0000':

Internal error in SDM: deployment was started although target system is not conf

igured properly. Db connect failed.

Sep 29, 2006 2:02:43 PM Error: An error occured while restoring the cluster ins

tances states

Sep 29, 2006 2:02:43 PM Error: There is no control instance running in the clus

ter:

Name:JM_T1159556563390_1_bowie

Host:bowie

State:5

HostAddress:138.126.81.41

Please check if there are running cluster instances.

Sep 29, 2006 2:02:43 PM Error: Received exception when restoring Engine state:

There is no control instance running in the cluster:

Name:JM_T1159556563390_1_bowie

Host:bowie

State:5

HostAddress:138.126.81.41

Please check if there are running cluster instances.

Sep 29, 2006 2:02:43 PM Info: -


Deployment was successful

-


Sep 29, 2006 2:02:43 PM Info: Summarizing the deployment results:

Sep 29, 2006 2:02:43 PM Error: Admitted: /software2/nw04supgSR1/java/J2EE_OSIND

EP/UT/EPBC06_0.SCA

Sep 29, 2006 2:02:43 PM Error: Processing error. Return code: 4

-


Please advise,

Mary Banh

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi, I have solved this problem by delete the JAVA stack completely per the installation manual instruction like delete the unix directories and files and also delete the oracle schema SAPSR3DB and the new tablespace PSAPSR3DB and its datafiles. One thing that the manual did not mention and i did have to delete otherwise i kept having problem is java related directories under /sapmnt/SID/global/*. Once everything deleted, i was able to perform the installation again and it completed with out any issue.

Former Member
0 Kudos

We got the Add-in to installed but once we did it killed our portal. We are still looking for solutions.