Skip to Content
avatar image
Former Member

Instance J02 can not start (do not reach port 5<>04) when upgrading from 7.02 to 7.30

Dear Experts,

We are upgrading BW system from 7.02 to 7.3

ABAP and Java are separate but using common database

The ABAP stack upgrade is completed. We are having issues during JAVA stack upgrade with DEPLOY_DB_ONLINE phase.

and it throw error :

"Reason: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection to host: 172.X.X.X and port: 50204"

and i checked in SAP Management Console (DB and SCS01 is running, But J02 is stopped) with status:

"Problems : Jstart is stopped"

and

"javax.xml.rpc.soap.SOAPFaultException: JsfOpenShm failed: object not found

at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.buildFaultException(MimeHttpBinding.java:737)

at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.processDocumentFault(MimeHttpBinding.java:860)

at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1439)

at com.sap.managementconsole.soap.sap.sapcontrol.SAPControlStub.j2EEGetProcessList2(SAPControlStub.java:2660)

at com.sap.managementconsole.dataloader.soap.sap.SAPSOAPDataLoader.getJ2EEProcessList2(SAPSOAPDataLoader.java:569)

at com.sap.managementconsole.common.data.J2EEProcessList.loadChildren(J2EEProcessList.java:49)

at com.sap.managementconsole.operations.LoadOperation.execute(LoadOperation.java:32)

at com.sap.managementconsole.operations.LoadInstanceOverviewData.execute(LoadInstanceOverviewData.java:37)

at com.sap.managementconsole.common.DataLoader.executeAllQueuedOperations(DataLoader.java:670)

at com.sap.managementconsole.common.ThreadPoolDataLoader$DataLoaderTask.execute(ThreadPoolDataLoader.java:127)

at com.sap.managementconsole.common.ThreadPoolManager$ThreadPoolElement.run(ThreadPoolManager.java:276)

at java.lang.Thread.run(Unknown Source)"

log file of dev_bootstrap:

"

F ********************************************************************************

F *** ERROR => Java node 'Instance_bootstrap' terminated with exit code 558.

F ***

F *** Please see section 'Java program exit codes'

F *** in SAP Note 1316652 for additional information and trouble shooting advice.

F ********************************************************************************

"

and log file of dev_jstart :

"

F ********************************************************************************

F *** ERROR => Node 'bootstrap' failed with exit code 558.

F ***

F *** Please see section 'Failures in the 'synchronizing binaries' phase'

F *** in SAP Note 1316652 for additional information and trouble shooting advice.

F ********************************************************************************

"

Extra Information : J2EE Start process is normally via "sapstart r3" command:

"

Checking db Database

-------------------------------------------

J2EE Database is running

See logfile /home/jwdadm/JdbcCon.log

Starting Startup Agent sapstartsrv

OK

Instance Service on host bwdevapp01 started

-------------------------------------------

starting SAP Instance SCS01

Startup-Log is written to /home/jwdadm/startsap_SCS01.log

-------------------------------------------

/usr/sap/JWD/SCS01/exe/sapcontrol -prot NI_HTTP -nr 01 -function Start

Instance on host bwdevapp01 started

Starting Startup Agent sapstartsrv

OK

Instance Service on host bwdevapp01 started

-------------------------------------------

starting SAP Instance J02

Startup-Log is written to /home/jwdadm/startsap_J02.log

-------------------------------------------

/usr/sap/JWD/J02/exe/sapcontrol -prot NI_HTTP -nr 02 -function Start

Instance on host bwdevapp01 started

"

at the present, i can not connect to Visuall Admin and Configtool, and can not reach to port 50240 also

Please help me find out this problem

Thanks and best regards

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

4 Answers

  • avatar image
    Former Member
    Mar 17, 2012 at 05:28 PM

    Hi,

    You should start configtool.bat(.sh) located in /usr/sap/<SID>/<INSTANCE_NAME >/j2ee/configtool.

    You can check in the Secure Store whether the user name and password are correct. (The password cannot be seen but you can overwrite it with the correct one.)

    Another solution for this situation can be found in SAP Note 701654.

    If the administrator user is locked and therefore you cannot connect with SDM nor in any other way (Visual Admin, Telnet, Web application), one possible solution is to unlock the administrator user using SAP Note 669848.

    CHech this thread as well http://scn.sap.com/message/13116440#13116440

    Check below link for more details

    http://help.sap.com/saphelp_nw04/helpdata/en/76/fb72ec091f4bf8a2d8ba321bb7e8d9/content.htm

    Regards,

    Venkata S Pagolu

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Aug 07, 2012 at 02:04 PM

    Hi Tran,

    This is regarding the SAPSR3DB is locked and password exired for the mentioned user.

    Follow these steps to unlock and set the password for SAPSR3DB and aslo you need to change th e password in configtool secure area for oracle administartion password.

    NOTE:Change the password for oracle administrator in Configtool

    SQL> select USERNAME,ACCOUNT_STATUS from dba_users;

    USERNAME ACCOUNT_STATUS
    ------------------------------ --------------------------------

    SAPSR3DB EXPIRED & LOCKED(TIMED)

    SQL> alter user SAPSR3DB account unlock;

    User altered.

    SQL> select USERNAME,ACCOUNT_STATUS from dba_users;

    USERNAME ACCOUNT_STATUS
    ------------------------------ --------------------------------

    SAPSR3DB EXPIRED

    SQL> alter user SAPSR3DB identified by "password";

    User altered.

    SQL> select username,account_status from dba_users;

    USERNAME ACCOUNT_STATUS
    ------------------------------ --------------------------------

    SAPSR3DB OPEN
    Actual this is ssue is because of Profille life time set to 180 days in oracle.

    Please follow below procedure to change it unlimited.

    SQL> select * from dba_profiles;

    PROFILE RESOURCE_NAME RESOURCE LIMIT
    ----------------------------------------
    DEFAULT PASSWORD_LIFE_TIME PASSWORD 180

    SQL> alter profile default limit PASSWORD_LIFE_TIME unlimited;

    Profile altered.

    After setting this in your system please restart the system .Hope this will solve your problem.

    Thanks&Regards

    Janakiram Reddy

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Aug 07, 2012 at 02:08 PM

    For more information see the bootstrap logs in work directory.

    log_bootstrap --this will give more information

    Regards

    Janakiram Reddy

    Add comment
    10|10000 characters needed characters exceeded

  • Sep 06, 2012 at 03:50 PM

    Start the listener service on the system. Then try to connect to the database using configtool if that works, try to start the system.

    Add comment
    10|10000 characters needed characters exceeded