cancel
Showing results for 
Search instead for 
Did you mean: 

SolMan installation START INSTANCE throws error

Former Member
0 Kudos

Hi All,

I am stuck up with the error I am getting in the phase of Start Instance. The sapdev_inst.log gives no exact message of the error. Is there anything I can look into???

Thanks

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Dear Prashant,

Please use the below note, it will resolve your issue ORA-0060.

Note-84348 Oracle deadlocks, ORA-00060.

Please follow all steps mentioned in the note.

Let me know if still issue persists.

Thanks

Kishore

Answers (6)

Answers (6)

APAG
Explorer
0 Kudos

Hello Everybody

follow these steps

1. Stop the SAP installation

2. Restart your Data Base

3. Open SAPMMC (SAP Console) and run it.

4. Start your sap installation with the continue option

Hope it works

PAVAN

0 Kudos

Hi,

I faced same problem while Installing Solman on Solaris

Installation got struck in START INSTANCE Phase 26 of 46

ABAP processes of instance SOL/DVEBMGS00 [ABAP: UNKNOWN] did not start after 10:30 minutes. Giving up

I checked R3trans -d with <SID>ADM user it gives rc 12

later i found /oracle/client was not extracted with trans.log. i did it manually and checked R3trans -d it executed with rc 0

start SAP manually

stop installation and start installation with continue old option

Installation will pass that Phase 26

Regards,

Navin

Former Member
0 Kudos

The /tmp/SAPINST_.../AS/ check for the latest file updated, which will show you what is going on.

ls -ltra

From the sapinst_dev.log you get the problem area from where you have to navigate for the error.

Also then stucked at Import SLD phase 40

In java.log it was getting update like

Import .. Loading xxx of xxxxx

Basically the import phase consumes loads of memory. Since we had 4 GB RAM, I think it was not sufficient for it to go.

So added 4GB more and it went through.

please check the vmstat 3 555 and check the swaps. You will come to know how much memory the process takes.

Former Member
0 Kudos

The installation do not move ahead. No activity in the /tmp../../AS folder for the logs.....

I do not know what SAP is doing???

Former Member
0 Kudos

Installation halt at Install Software unit

java.log

(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDepl

oyerImpl.checkLoginCredentials.DMEXC)

Info: Starting to save the repository

Info: Finished saving the repository

Info: Starting: Initial deployment: Selected software component 'LM-SERVICE'/'sa

p.com'/'SAP AG'/'1000.7.00.12.0.20070524105900''/'0' will be deployed.

Error: Aborted: software component 'LM-SERVICE'/'sap.com'/'SAP AG'/'1000.7.00.12

.0.20070524105900''/'0':

Failed deployment of SDAs:

development component 'tc/smd/agent/application/global/conf'/'sap.com'/'SAP AG'/

'7.0012.20070328124852.0000'/'0' : aborted

Please, look at error logs above for more information!

Info: Starting to save the repository

Info: Finished saving the repository

Info: J2EE Engine is in same state (online/offline) as it has been before this d

eployment process.

Error: -


At least one of the Deployments failed -


Info: Summarizing the deployment results:

Error: Aborted: /sapcd/51032958/J2EE_OSINDEP/UT_SOLMAN/LMSERVICE12_0.SCA

Processing error. Return code: 4

Error: Processing error. Return code: 4

sapinst_dev.log

(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDep

oyerImpl.checkLoginCredentials.DMEXC)

Info: Starting to save the repository

Info: Finished saving the repository

Info: Starting: Initial deployment: Selected software component 'LM-SERVICE'/'s

p.com'/'SAP AG'/'1000.7.00.12.0.20070524105900''/'0' will be deployed.

Error: Aborted: software component 'LM-SERVICE'/'sap.com'/'SAP AG'/'1000.7.00.1

.0.20070524105900''/'0':

Failed deployment of SDAs:

development component 'tc/smd/agent/application/global/conf'/'sap.com'/'SAP AG'

'7.0012.20070328124852.0000'/'0' : aborted

Please, look at error logs above for more information!

Info: Starting to save the repository

Info: Finished saving the repository

Info: J2EE Engine is in same state (online/offline) as it has been before this

eployment process.

Error: -


At least one of the Deployments failed -


Info: Summarizing the deployment results:

Error: Aborted: /sapcd/51032958/J2EE_OSINDEP/UT_SOLMAN/LMSERVICE12_0.SCA

Processing error. Return code: 4

Error: Processing error. Return code: 4

WARNING 2008-07-30 00:02:25.522

CJSlibModule::writeWarning_impl()

EJS_Installer::writeTraceToLogBook()

2008-07-31 00:02:25.523 NWSDM.getLogfile()

TRACE 2008-07-30 00:02:25.525 [iaxxejsexp.cpp:199]

EJS_Installer::writeTraceToLogBook()

SdmCommandlineApi_630_getLogfile() returning /tmp/sapinst_instdir/SOLMAN/SYSTEM/

ORA/CENTRAL/AS/callSdmViaSapinst.log

TRACE 2008-07-30 00:02:25.585 [iaxxejsexp.cpp:199]

EJS_Installer::writeTraceToLogBook()

NWException thrown: nw.sdm.deploymentErrorWithLog:

SDM deployment failed for at least one of the components to be deployed. SOLUTIO

N: Check /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/callSdmViaSapinst.log

for more information.

TRACE 2008-07-30 00:02:25.589 [iaxxejsexp.cpp:199]

EJS_Installer::writeTraceToLogBook()

2008-07-31 00:02:25.586 ERROR : Caught NWSDMDeployException. nw.sdm.deploymentEr

rorWithLog:

SDM deployment failed for at least one of the components to be deployed. SOLUTIO

N: Check /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/callSdmViaSapinst.log

for more information.Rethrowing ...

TRACE 2008-07-30 00:02:25.707 [iaxxejsexp.cpp:199]

EJS_Installer::writeTraceToLogBook()

2008-07-31 00:02:25.706 NWSDM.getLogfile()

TRACE 2008-07-30 00:02:25.708 [iaxxejsexp.cpp:199]

EJS_Installer::writeTraceToLogBook()

SdmCommandlineApi_630_getLogfile() returning /tmp/sapinst_instdir/SOLMAN/SYSTEM/

ORA/CENTRAL/AS/callSdmViaSapinst.log

TRACE 2008-07-30 00:02:26.650 [syuxcfile.cpp:344]

CSyFileImpl::copy(const CSyPath & /tmp/sapinst_instdir/SOLMAN/SYSTEM/

ORA/CENTRAL/AS/UsageTypesDeployment.log, ISyNode::CopyMoveMode_t 0x3, ISyProgres

sObserver*) const

Copying file /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/callSdmViaSapinst

.log to /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/UsageTypesDeployment.l

og

INFO 2008-07-30 00:02:26.715 [syuxcfile.cpp:574]

CSyFileImpl::copy(const CSyPath & /tmp/sapinst_instdir/SOLMAN/SYSTEM/

ORA/CENTRAL/AS/UsageTypesDeployment.log, ISyNode::CopyMoveMode_t 0x3, ISyProgres

sObserver*) const

Copied file '/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/callSdmViaSapinst

.log' to '/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/UsageTypesDeployment

.log'.

-


callSdmViaSapinst.log

TRACE 2008-07-30 00:02:25.589 [iaxxejsexp.cpp:199]

EJS_Installer::writeTraceToLogBook()

2008-07-31 00:02:25.586 ERROR : Caught NWSDMDeployException. nw.sdm.deploymentEr

rorWithLog:

SDM deployment failed for at least one of the components to be deployed. SOLUTIO

N: Check /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/callSdmViaSapinst.log

for more information.Rethrowing ...

TRACE 2008-07-30 00:02:25.707 [iaxxejsexp.cpp:199]

EJS_Installer::writeTraceToLogBook()

2008-07-31 00:02:25.706 NWSDM.getLogfile()

Please, look at error logs above for more information!

Jul 30, 2008 12:01:15... Info: Starting to save the repository

Jul 30, 2008 12:01:23... Info: Finished saving the repository

Jul 30, 2008 12:01:23... Info: J2EE Engine is in same state (online/offline) as

it has been before this deployment process.

Jul 30, 2008 12:01:23... Error: -


At least one of the Deployments

failed -


Jul 30, 2008 12:01:27... Info: Summarizing the deployment results:

Jul 30, 2008 12:01:27... Error: Aborted: /sapcd/51032958/J2EE_OSINDEP/UT_SOLMAN/

LMSERVICE12_0.SCA

Jul 30, 2008 12:01:31... Error: Processing error. Return code: 4

~

-


UsageTypesDeployment.log

(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDepl

oyerImpl.checkLoginCredentials.DMEXC)

Jul 30, 2008 12:01:07... Info: Starting to save the repository

Jul 30, 2008 12:01:15... Info: Finished saving the repository

Jul 30, 2008 12:01:15... Info: Starting: Initial deployment: Selected software c

omponent 'LM-SERVICE'/'sap.com'/'SAP AG'/'1000.7.00.12.0.20070524105900''/'0' wi

ll be deployed.

Jul 30, 2008 12:01:15... Error: Aborted: software component 'LM-SERVICE'/'sap.co

m'/'SAP AG'/'1000.7.00.12.0.20070524105900''/'0':

Failed deployment of SDAs:

development component 'tc/smd/agent/application/global/conf'/'sap.com'/'SAP AG'/

'7.0012.20070328124852.0000'/'0' : aborted

Please, look at error logs above for more information!

Jul 30, 2008 12:01:15... Info: Starting to save the repository

Jul 30, 2008 12:01:23... Info: Finished saving the repository

Jul 30, 2008 12:01:23... Info: J2EE Engine is in same state (online/offline) as

it has been before this deployment process.

Jul 30, 2008 12:01:23... Error: -


At least one of the Deployments

failed -


Jul 30, 2008 12:01:27... Info: Summarizing the deployment results:

Jul 30, 2008 12:01:27... Error: Aborted: /sapcd/51032958/J2EE_OSINDEP/UT_SOLMAN/

LMSERVICE12_0.SCA

Jul 30, 2008 12:01:31... Error: Processing error. Return code: 4

Please suggest

Edited by: Prashant Dhas on Jul 30, 2008 8:03 AM

markus_doehr2
Active Contributor
0 Kudos

you can check

dev_disp

dev_w0

in the work directory of the instance (/usr/sap/<SID>/DVEBMGS00/work)

Markus

Former Member
0 Kudos

I have the output of the dev_w0 and other files. is there anything with the access problem. I am blank now....

disp_dev

Tue Jul 29 11:30:30 2008

MBUF state ACTIVE

      • WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

      • WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

Tue Jul 29 11:30:31 2008

      • WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

      • WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

Tue Jul 29 11:32:35 2008

SoftCancel request for T19 U20 M0 received from IC_MAN

Tue Jul 29 11:34:41 2008

SoftCancel request for T19 U21 M0 received from IC_MAN

Tue Jul 29 11:27:22 2008

***LOG Q0K=> DpMsAttach, mscon ( sapdev) [dpxxdisp.c 11753]

DpStartStopMsg: send start message (myname is >sapdev_SMD_00 <)

DpStartStopMsg: start msg sent

CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.

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 111

Release check o.K.

Tue Jul 29 11:30:30 2008

MBUF state ACTIVE

      • WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

      • WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

Tue Jul 29 11:41:15 2008

      • WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

Tue Jul 29 11:41:16 2008

      • WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

EX-T19, U26, , 10.150.203.95, 11:40:58, M0, W-1, , 1/0

      • ERROR => DpRqCheck: T19 U26 <> req.uid 20 [dpxxdisp.c 6872]

***LOG Q0G=> DpRqBadHandle, bad_req ( DIA) [dpxxdisp.c 5207]

      • ERROR => BAD REQUEST - Reason: DpRqCheck failed (line 5999): [dpxxdisp.c 5209]

-IN-- sender_id DISPATCHER tid 19 wp_ca_blk 75 wp_id 4

-IN-- action SEND_TO_WP uid 20 appc_ca_blk -1 type DIA

-IN-- new_stat WP_WAIT mode 0 len 704 rq_id 435

-IN-- req_info MSG_WITH_REQ_BUF MSG_WITH_OH

Tue Jul 29 11:41:23 2008

      • WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

EX-T19, U26, 000 SAPSYS, 10.150.203.95, 11:41:18, M0, W3, , 1/0

      • ERROR => DpRqCheck: T19 U26 <> req.uid 24 [dpxxdisp.c 6872]

***LOG Q0G=> DpRqBadHandle, bad_req (NOWP) [dpxxdisp.c 5207]

      • ERROR => BAD REQUEST - Reason: DpRqCheck failed (line 3732): [dpxxdisp.c 5209]

-IN-- sender_id DISPATCHER tid 19 wp_ca_blk 76 wp_id 5

-IN-- action SEND_TO_WP uid 24 appc_ca_blk -1 type NOWP

-IN-- new_stat WP_WAIT mode 0 len 672 rq_id 483

-IN-- req_info MSG_WITH_REQ_BUF MSG_WITH_OH

Tue Jul 29 11:41:24 2008

      • WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

Tue Jul 29 11:41:25 2008

      • WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

Tue Jul 29 11:41:26 2008

      • WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

Tue Jul 29 11:42:03 2008

SoftCancel request for T19 U26 M0 received from IC_MAN

SoftCancel request for T20 U25 M0 received from IC_MAN

EX-T19, U28, 000 SAPSYS, 10.150.203.95, 11:42:03, M0, W3, , 1/0

      • ERROR => DpRqCheck: T19 U28 <> req.uid 26 [dpxxdisp.c 6872]

***LOG Q0G=> DpRqBadHandle, bad_req (NOWP) [dpxxdisp.c 5207]

      • ERROR => BAD REQUEST - Reason: DpRqCheck failed (line 3732): [dpxxdisp.c 5209]

-IN-- sender_id DISPATCHER tid 19 wp_ca_blk 75 wp_id 5

-IN-- action SEND_TO_WP uid 26 appc_ca_blk -1 type NOWP

-IN-- new_stat WP_WAIT mode 0 len 672 rq_id 589

-IN-- req_info MSG_WITH_REQ_BUF MSG_WITH_OH

      • WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

Tue Jul 29 11:42:04 2008

      • WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

Tue Jul 29 11:42:05 2008

      • WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

Tue Jul 29 11:42:06 2008

      • WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

dev_w1

C Tue Jul 29 11:41:32 2008

C OCI-call failed with -1=OCI_ERROR

C SQL error 60: 'ORA-00060: deadlock detected while waiting for resource'

C *** ERROR => Error 60 in stmt_fetch() from oci_execute_stmt(), orpc=0

[dbsloci.c 12714]

C *** ERROR => ORA-60 occurred when executing SQL stmt (parse error offset=0)

M SecAudit(RsauShmInit): addr of RSAUSLOTS...... = 0xffffffff7b3007ac

C

C Tue Jul 29 11:41:32 2008

C OCI-call failed with -1=OCI_ERROR

C SQL error 60: 'ORA-00060: deadlock detected while waiting for resource'

C *** ERROR => Error 60 in stmt_fetch() from oci_execute_stmt(), orpc=0

[dbsloci.c 12714]

C *** ERROR => ORA-60 occurred when executing SQL stmt (parse error offset=0)

[dbsloci.c 12733]

C C sc_p=0x1069ef080,no=6,idc_p=0x106a07db0,con=0,act=1,slen=378,smax=512,#vars=2,stmt=0x106e84b50,ta

ble=REPOSRC

C SELECT "SQLX" , "EDTX" , "DBNA" , "CLAS" , "TYPE" , "OCCURS" , "SUBC" , "APPL" , "SECU" , "CNAM"

, "\

C CDAT" , "VERN" , "LEVL" , "RSTAT" , "RMAND" , "RLOAD" , "UNAM" , "UDAT" , "UTIME" , "DATALG" , "V

ARC\

C L" , "DBAPL" , "FIXPT" , "SSET" , "SDATE" , "STIME" , "IDATE" , "ITIME" , "LDBNAME" , "UCCHECK" ,

"M\

C AXLINELN" FROM "REPOSRC" WHERE "PROGNAME" = :A0 AND "R3STATE" = :A1 FOR UPDATE;

C sc_p=0x1069ef080,no=6,idc_p=0x106a07db0,con=0,act=1,slen=378,smax=512,#vars=2,stmt=0x106e84b50,ta

ble=REPOSRC

C prep=0,lit=0,nsql=0,lobret=0,#exec=12,dbcnt=0,upsh_p=(nil),ocistmth_p=0x106e85a80

C IN : cols=2,rmax=1,xcnt=0,rpc=0,rowi=0,rtot=0,upto=4294967295,rsize=82,vmax=32,bound=1,iobuf_p=0x

106b238d0,vda_p=0x106e871c0

C OUT: cols=31,rmax=1,xcnt=1,rpc=0,rowi=0,rtot=0,upto=4294967295,rsize=280,vmax=32,bound=1,iobuf_p=

0x106d7bd10,vda_p=0x106e87950

C lobs=0,lmax=0,lpcnt=0,larr=(nil),lcurr_p=(nil),rret=0

C SELECT "SQLX" , "EDTX" , "DBNA" , "CLAS" , "TYPE" , "OCCURS" , "SUBC" , "APPL" , "SECU" , "CNAM"

, "\

C CDAT" , "VERN" , "LEVL" , "RSTAT" , "RMAND" , "RLOAD" , "UNAM" , "UDAT" , "UTIME" , "DATALG" , "V

ARC\

C L" , "DBAPL" , "FIXPT" , "SSET" , "SDATE" , "STIME" , "IDATE" , "ITIME" , "LDBNAME" , "UCCHECK" ,

"M\

C AXLINELN" FROM "REPOSRC" WHERE "PROGNAME" = :A0 AND "R3STATE" = :A1 FOR UPDATE;

B ***LOG BYO=> deadlock aborts transaction [dbsh#2 @ 1139] [dbsh 1139 ]

B SQL code: 60, SQL text: ORA-00060: deadlock detected while waiting for resource

B

B Tue Jul 29 11:41:34 2008

B ***LOG BY4=> sql error 60 performing SEL on table REPOSRC [dbrepo#4 @ 2550] [dbrepo 2550

]

B ***LOG BY0=> ORA-00060: deadlock detected while waiting for resource [dbrepo#4 @ 2550] [dbrepo 2

550 ]

A TH VERBOSE LEVEL FULL

A ** RABAX: level LEV_RX_PXA_RELEASE_MTX entered.

A ** RABAX: level LEV_RX_PXA_RELEASE_MTX completed.

sapinst.log

INFO 2008-07-29 11:37:00.890

Connect to message server (sapdev/3900) succeeded.

INFO 2008-07-29 11:37:00.891

Disconnect from message server (sapdev/3900) succeeded.

ERROR 2008-07-29 11:37:05.627

CJS-30149 ABAP processes of instance SMD/DVEBMGS00 [ABAP: STARTING] did not start after 10:00 minu

es. Giving up.

ERROR 2008-07-29 11:37:05.872

FCO-00011 The step start with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|i

d|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_Start|ind|ind|ind|ind|1|0|start was ex

cuted with status ERROR .

sapinst_dev.log

TRACE 2008-07-29 11:37:05.625 [iaxxejsexp.cpp:199]

EJS_Installer::writeTraceToLogBook()

NWException thrown: nw.progress.waitingForStartABAPFailed:

ABAP processes of instance SMD/DVEBMGS00 [ABAP: STARTING] did not start after 10:00 minutes. Giving

up.

ERROR 2008-07-29 11:37:05.627

CJSlibModule::writeError_impl()

CJS-30149 ABAP processes of instance SMD/DVEBMGS00 [ABAP: STARTING] did not start after 10:00 minut

es. Giving up.

TRACE 2008-07-29 11:37:05.790 [iaxxejsbas.hpp:460]

EJS_Base::dispatchFunctionCall()

JS Callback has thrown unknown exception. Rethrowing.

ERROR 2008-07-29 11:37:05.872 [iaxxgenimp.cpp:731]

showDialog()

<html><head></head><body><p>An error occurred while processing service <b>SAP Solution Manager 4.0 S

upport Release 3 > SAP Systems > Oracle > Central System > Central System Installation</b>. You may

now</p><ul> <li>press <I>Retry</I> to repeat the current step.</li> <li>press the <I>View Log</I> bu

tton to get more information about the error.</li> <li>stop the task and continue with it later.</li

></ul><p>Log files are written to <b>/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS</b>.</p></bod

y>

TRACE 2008-07-29 11:37:06.485 [iaxxgenimp.cpp:1155]

showDialog()

waiting for an answer from gui

Please suggest

Edited by: Eric Brunelle on Feb 19, 2010 10:00 AM

fixed html tags

markus_doehr2
Active Contributor
0 Kudos

You have deadlocks on your database.

What version and patchlevel of the database do you run?

Markus

Former Member
0 Kudos

The oracle version is 10.2.0.1.0.

Kumar: I will check the notes and try it.

Regards

markus_doehr2
Active Contributor
0 Kudos

10.2.0.1 is NOT supported.

Please read the installation guide attentively. It tells you to

- install 10.2.0.1

- install the latest patchset (which is 10.2.0.2 or 10.2.0.4)

- install the latest interim patch for the respective version

and THEN continue with the installation.

See also note 871096 - Oracle Database 10g: Patch sets/patches for 10.2.0

It's possible that your database is hosed and that you need to start over.

Regards,

Markus

Former Member
0 Kudos

Thanks Markus and Kumar, the installation went through.

Just restarted the DB and retry the installation...

Before that I have checked the locks and db_waiters everythings. The error message tells that there is no locks from Oracle but from the application.

Now the only problem is that the Oracle version is 10.2.0.1.0 and I needed to apply the patch for 2.0, but that option never came in Solman. Now reading the note 871096. Is it necessary now to update the patch??

If yes then how after the complete installation ?

Thanks

markus_doehr2
Active Contributor
0 Kudos

Your database version is not supported - check the note I posted. It's clear from the installation guide and the corresponding installation notes. It's good possible that further installation don't go through too.

You must install that patch - at least 10.2.0.2 + all the 40+ interim patches - or install 10.2.0.4 and the 28 patches. All kinds of further problems will arise if you don't do that.

And yes, it's a big note and it's quite a big amount of work to do, but that's Oracle...

Markus

Former Member
0 Kudos

Previously I got the error message and check the dev_jcontrol. It pointed that .jvmx.jar file not present. I have just added the parameter in Default profile and retry it. I gone through

Now

I am stuck at the step no 34 with the message at the bottom

RFC_ABAP_INSTALL_AND_RUN . I am reading the note 514998 but does not tell what to do ?

It tells

Solution

1. Modification to the function module RFC_ABAP_INSTALL_AND_RUN on the actual system requirements. Or:

2. Implement a customer-specific function module and adapt the programs used to this function module.

But where do I do that??

How to start/stop java engine. Where are the docs for the java/SDM ??

Edited by: Prashant Dhas on Jul 30, 2008 8:12 AM

Former Member
0 Kudos

Markus,

please suggest the way out to complete the installation of SOLMAN??

callSdmViaSapinst.log

(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDepl

oyerImpl.checkLoginCredentials.DMEXC)

Jul 30, 2008 10:14:01... Info: Starting to save the repository

Jul 30, 2008 10:14:03... Info: Finished saving the repository

Jul 30, 2008 10:14:03... Info: Starting: Initial deployment: Selected software c

omponent 'LM-SERVICE'/'sap.com'/'SAP AG'/'1000.7.00.12.0.20070524105900''/'2' wi

ll be deployed.

Jul 30, 2008 10:14:03... Error: Aborted: software component 'LM-SERVICE'/'sap.co

m'/'SAP AG'/'1000.7.00.12.0.20070524105900''/'2':

Failed deployment of SDAs:

development component 'tc/smd/agent/application/runtime'/'sap.com'/'SAP AG'/'7.0

012.20070328124852.0000'/'2' : aborted

Please, look at error logs above for more information!

Jul 30, 2008 10:14:03... Info: Starting to save the repository

Jul 30, 2008 10:14:05... Info: Finished saving the repository

Jul 30, 2008 10:14:05... Error: Could not create JStartupClusterController conne

cted to MessageServer[Host:sapdev, Port:3901] : Connection refused Throwable: j

ava.net.ConnectException Throwable message: Connection refused

Jul 30, 2008 10:14:05... Error: Received exception when restoring Engine state:

Could not create JStartupClusterController connected to MessageServer[Host:sapde

v, Port:3901] : Connection refused

Jul 30, 2008 10:14:05... Error: -


At least one of the Deployments

failed -


Jul 30, 2008 10:14:08... Info: Summarizing the deployment results:

Jul 30, 2008 10:14:08... Error: Aborted: /sapcd/51032958/J2EE_OSINDEP/UT_SOLMAN/

LMSERVICE12_0.SCA

Jul 30, 2008 10:14:08... Error: Processing error. Return code: 4

Edited by: Prashant Dhas on Jul 30, 2008 9:16 AM