Portal 7.31: Config Tool: Load error

[former_member261631]

Hi ,

We are having SAP Portal 7.3 EhP1 system implemented running in virtual server landscape having server instance in one drive and Oracle 11 Db in other drive.

But now this system is not working, as the Oracle File structure has been placed on other drive. Due to this server instance is not working and the jstart.EXE is stopped. I have placed the Oracle file folder back to it’s old position again, but still jstart.EXE is not working.

Even I tried to access Config tool, but due to Database issue it is also not starting.So, require suggestion how to make start this system up again, by resolving system at Oracle database level.........

Config Tool Message when loading Config Tool.bat file:-

*************************************

Error occured while scanning DB

Msg: Error while connecting DB

****************************************

Regards,

Hanif

[former_member191911 · Accepted solution]

Are you able to start Oracle?

Did you created a correct controlfile after changing the Oracle file structure?

Can you execute: select open_mode from v$database

Kr. Mark

[former_member261631 · Accepted solution]

Hi Mark,

Thanks for the reply. Well I have installed Portal 7.3 EHP1 having downloaded oracle files from SAP service Mkt place i.e. 51042334_part1......part6.

Which is an Oracle Database 11g Release 2 Installer. After installing these file are saved in app folder in Fdrive. and also Oracle DB is not in active state in SAP MMC.

As you see from the SAP MMC viewer, the exact issue.

Regards,

hanif

[former_member191911 · Accepted solution]

Are you able to access Oracle via sqlplus? Can you check if you are able to start it?

Kr. Mark

[former_member189725 · Accepted solution]

Can you right click on the jstart.exe and check if you can see the developer trace . Paste the contents of the trace file.

Regards

Ratnajit

[former_member261631 · Accepted solution]

Hi Ranjit, jstart.EXE developer trace information.. --------------------------------------------------- trc file: "dev_jstart.2964", trc level: 1, release: "720" --------------------------------------------------- --------------------------------------------------- trc file: "dev_jstart.new", trc level: 1, release: "720" --------------------------------------------------- sysno      00 sid        DLS systemid  562 (PC with Windows NT) relno      7200 patchlevel 0 patchno    63 intno      20020600 make      multithreaded, Unicode, 64 bit, optimized profile    \\\sapmnt\DLS\SYS\profile\DLS_J00_pid        2964 * *  ACTIVE TRACE LEVEL          1 *  ACTIVE TRACE COMPONENTS      All, egi --------------------------------------------------- Regards, Hanif

[former_member189725 · Accepted solution]

Paste the complete trace file.

Regards

Ratnajit

[former_member261631 · Accepted solution]

---------------------------------------------------
trc file: "dev_jstart.2964", trc level: 1, release: "720"
---------------------------------------------------

---------------------------------------------------
trc file: "dev_jstart.new", trc level: 1, release: "720"
---------------------------------------------------
sysno      00
sid        DLS
systemid   562 (PC with Windows NT)
relno      7200
patchlevel 0
patchno    63
intno      20020600
make       multithreaded, Unicode, 64 bit, optimized
profile    \\DTDKCPHAS0614\sapmnt\DLS\SYS\profile\DLS_J00_DTDKCPHAS0614
pid        2964

*
*  ACTIVE TRACE LEVEL           1
*  ACTIVE TRACE COMPONENTS      All, egi
*

Tue Aug 28 09:18:44 2012
*
*  trace logging activated, max size = 52428800 bytes, 2 versions
*

arguments :
  arg[ 0] : E:\usr\sap\DLS\J00\exe\jstart.EXE
  arg[ 1] : pf=\\DTDKCPHAS0614\sapmnt\DLS\SYS\profile\DLS_J00_DTDKCPHAS0614

F 
F Tue Aug 28 09:18:44 2012
F  ********************************************************************************
F  Java environment properties (E:\usr\sap\DLS\J00\work\jstart.jvm)
F    root directory    : E:\usr\sap\DLS\J00\exe\sapjvm_6
F    vendor            : SAP AG
F    version           : 1.6.0_29
F    cpu               : amd64
F    java vm type      : server
F    java vm version   : 6.1.037 1.6-b11
F    jvm library name  : jvm.dll
F    library path      : E:\usr\sap\DLS\J00\exe\sapjvm_6\jre\bin\server;E:\usr\sap\DLS\J00\exe\sapjvm_6\jre\bin
F    executable path   : E:\usr\sap\DLS\J00\exe\sapjvm_6\bin
F  ********************************************************************************
F    SAP extensions    : available
F  ********************************************************************************
I  [Thr 1624] MtxInit: 30002 0 2

---------------------------------------------------
trc file: "dev_jstart", trc level: 1, release: "720"
---------------------------------------------------
*
*  ACTIVE TRACE LEVEL           1
*  ACTIVE TRACE COMPONENTS      All, egi
*
F  [Thr 1624] *** LOG => connected to Enqueue Server.
F  [Thr 1624] *** LOG => connected to Message Server.
F  [Thr 1624] *** LOG => Starting run level 1.
F  ********************************************************************************
F  Java process [deployment] properties:
F    section name     : deployment
F    config file      : E:\usr\sap\DLS\J00\exe\startup.properties
F    node name        : Deploy_offline
F    home directory   : E:\usr\sap\DLS\J00\j2ee\cluster
F    shutdown timeout : 136000 ms
F    exit timeout     : 7000 ms
F    debuggable       : false
F    debugger active  : false
F  ********************************************************************************
F  [Thr 1624] *** LOG => Instance state is "Deploying offline components" (STARTING @ 0, INACTIVE).
F  [Thr 1624] *** LOG => Starting nodes: runlevel 1.
F  ********************************************************************************
F  Starting process: E:\usr\sap\DLS\J00\exe\jstart.EXE
F    arg[ 1] = -nodeId=0
F    arg[ 2] = pf=\\DTDKCPHAS0614\sapmnt\DLS\SYS\profile\DLS_J00_DTDKCPHAS0614
F    arg[ 3] = -hostvm
F    arg[ 4] = -nodeName=deployment
F    arg[ 5] = -file=E:\usr\sap\DLS\J00\exe\startup.properties
F    arg[ 6] = -jvmFile=E:\usr\sap\DLS\J00\work\jstart.jvm
F    arg[ 7] = -traceFile=E:\usr\sap\DLS\J00\work\dev_deployment
F    arg[ 8] = -javaOutFile=E:\usr\sap\DLS\J00\work\jvm_deployment.out
F    env   : NODNSSAPTRANSHOST=1
F  exePath : PATH=E:\usr\sap\DLS\J00\exe\sapjvm_6\bin;E:\usr\sap\DLS\J00\exe;F:\app\Adminhsha\product\11.2.0\dbhome_1\bin;E:\app\Adminhsha\product\11.2.0\dbhome_1\bin;E:\app\Adminhsha\product\11.2.0\client_1;F:\app\Adminhsha\product\11.2.0\client_1;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;E:\usr\sap\DLS\SYS\exe\uc\NTAMD64
F  libPath : PATH=E:\usr\sap\DLS\J00\exe\sapjvm_6\jre\bin\server;E:\usr\sap\DLS\J00\exe\sapjvm_6\jre\bin;E:\usr\sap\DLS\J00\j2ee\os_libs;E:\usr\sap\DLS\J00\exe\sapjvm_6\bin;E:\usr\sap\DLS\J00\exe;F:\app\Adminhsha\product\11.2.0\dbhome_1\bin;E:\app\Adminhsha\product\11.2.0\dbhome_1\bin;E:\app\Adminhsha\product\11.2.0\client_1;F:\app\Adminhsha\product\11.2.0\client_1;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;E:\usr\sap\DLS\SYS\exe\uc\NTAMD64
F  stdout  : E:\usr\sap\DLS\J00\work\std_deployment.out
F  stderr  : E:\usr\sap\DLS\J00\work\std_deployment.out
F  console : no
F  debugger: no
F  nice    : no
F  ********************************************************************************
F  Process Deploy_offline started with pid 3820
F  ********************************************************************************
F  [Thr 1624] *** LOG => Process deployment started (pid 3820).
F 
F [Thr 1624] Tue Aug 28 09:18:47 2012
F  [Thr 1624] *** LOG => Process deployment stopping (pid 3820).
F 
F [Thr 2840] Tue Aug 28 09:18:47 2012
F  [Thr 2840] *** LOG => Signal 13 SIGCHLD.
F  [Thr 1624] *** LOG => Process deployment stopped (pid 3820).
F  [Thr 1624] *** LOG => Instance state is "Deploying offline components" (STOPPING @ 0, INACTIVE).
F  [Thr 1624] *** LOG => Run level 1 completed.
F  [Thr 1624] *** LOG => Starting run level 2.
F  ********************************************************************************
F  Java process [bootstrap] properties:
F    section name     : bootstrap
F    config file      : E:\usr\sap\DLS\J00\exe\startup.properties
F    node name        : Instance_bootstrap
F    home directory   : E:\usr\sap\DLS\J00\j2ee\cluster
F    shutdown timeout : 136000 ms
F    exit timeout     : 7000 ms
F    debuggable       : false
F    debugger active  : false
F  ********************************************************************************
F  [Thr 1624] *** LOG => Instance state is "Synchronizing binaries" (STARTING @ 0, INACTIVE).
F  [Thr 1624] *** LOG => Starting nodes: runlevel 2.
F  ********************************************************************************
F  Starting process: E:\usr\sap\DLS\J00\exe\jstart.EXE
F    arg[ 1] = -nodeId=0
F    arg[ 2] = pf=\\DTDKCPHAS0614\sapmnt\DLS\SYS\profile\DLS_J00_DTDKCPHAS0614
F    arg[ 3] = -hostvm
F    arg[ 4] = -nodeName=bootstrap
F    arg[ 5] = -file=E:\usr\sap\DLS\J00\exe\startup.properties
F    arg[ 6] = -jvmFile=E:\usr\sap\DLS\J00\work\jstart.jvm
F    arg[ 7] = -traceFile=E:\usr\sap\DLS\J00\work\dev_bootstrap
F    arg[ 8] = -javaOutFile=E:\usr\sap\DLS\J00\work\jvm_bootstrap.out
F    env   : NODNSSAPTRANSHOST=1
F  exePath : PATH=E:\usr\sap\DLS\J00\exe\sapjvm_6\bin;E:\usr\sap\DLS\J00\exe;F:\app\Adminhsha\product\11.2.0\dbhome_1\bin;E:\app\Adminhsha\product\11.2.0\dbhome_1\bin;E:\app\Adminhsha\product\11.2.0\client_1;F:\app\Adminhsha\product\11.2.0\client_1;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;E:\usr\sap\DLS\SYS\exe\uc\NTAMD64
F  libPath : PATH=E:\usr\sap\DLS\J00\exe\sapjvm_6\jre\bin\server;E:\usr\sap\DLS\J00\exe\sapjvm_6\jre\bin;E:\usr\sap\DLS\J00\j2ee\os_libs;E:\usr\sap\DLS\J00\exe\sapjvm_6\bin;E:\usr\sap\DLS\J00\exe;F:\app\Adminhsha\product\11.2.0\dbhome_1\bin;E:\app\Adminhsha\product\11.2.0\dbhome_1\bin;E:\app\Adminhsha\product\11.2.0\client_1;F:\app\Adminhsha\product\11.2.0\client_1;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;E:\usr\sap\DLS\SYS\exe\uc\NTAMD64
F  stdout  : E:\usr\sap\DLS\J00\work\std_bootstrap.out
F  stderr  : E:\usr\sap\DLS\J00\work\std_bootstrap.out
F  console : no
F  debugger: no
F  nice    : no
F  ********************************************************************************
F  Process Instance_bootstrap started with pid 2836
F  ********************************************************************************
F  [Thr 1624] *** LOG => Process bootstrap started (pid 2836).
F 
F [Thr 1624] Tue Aug 28 09:18:51 2012
F  [Thr 1624] *** LOG => Process bootstrap stopping (pid 2836).
F 
F [Thr 2532] Tue Aug 28 09:18:51 2012
F  [Thr 2532] *** LOG => Signal 13 SIGCHLD.
F  [Thr 1624] *** LOG => Process bootstrap stopped (pid 2836).
F  [Thr 1624] *** WARNING => Node bootstrap failed: result 1, exit code 558. [sfxxnode.hpp 1024]
F  ********************************************************************************
F  Native process [snapshot] properties:
F    section name     : snapshot
F    config file      : E:\usr\sap\DLS\J00\exe\startup.properties
F    node name        : snapshot
F    home directory   : E:\usr\sap\DLS\J00\work
F    shutdown timeout : 122000 ms
F    sf support       : false
F  ********************************************************************************
F  ********************************************************************************
F  Starting process: E:\usr\sap\DLS\J00\exe\sapcontrol.EXE
F    arg[ 1] = -prot
F    arg[ 2] = PIPE
F    arg[ 3] = -nr
F    arg[ 4] = 00
F    arg[ 5] = -function
F    arg[ 6] = CreateSnapshot
F    arg[ 7] = Servercrash
F    arg[ 8] = postmortem?node=bootstrap&exitcode=558
F    arg[ 9] = 1
F    arg[10] = 10000
F    arg[11] = ""
F    arg[12] = ""
F    arg[13] = DEFAULT
F    env   : NODNSSAPTRANSHOST=1
F  exePath : PATH=E:\usr\sap\DLS\J00\exe;F:\app\Adminhsha\product\11.2.0\dbhome_1\bin;E:\app\Adminhsha\product\11.2.0\dbhome_1\bin;E:\app\Adminhsha\product\11.2.0\client_1;F:\app\Adminhsha\product\11.2.0\client_1;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;E:\usr\sap\DLS\SYS\exe\uc\NTAMD64
F  libPath : PATH=E:\usr\sap\DLS\J00\exe;F:\app\Adminhsha\product\11.2.0\dbhome_1\bin;E:\app\Adminhsha\product\11.2.0\dbhome_1\bin;E:\app\Adminhsha\product\11.2.0\client_1;F:\app\Adminhsha\product\11.2.0\client_1;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;E:\usr\sap\DLS\SYS\exe\uc\NTAMD64
F  stdout  : E:\usr\sap\DLS\J00\work\std_snapshot.out
F  stderr  : E:\usr\sap\DLS\J00\work\std_snapshot.out
F  console : no
F  debugger: no
F  nice    : no
F  ********************************************************************************
F  Process snapshot started with pid 2860
F  ********************************************************************************
F  [Thr 1624] *** LOG => Process snapshot started (pid 2860).
F  [Thr 1624] *** LOG => Process snapshot running (pid 2860).
F  [Thr 1624] *** LOG => SAP Start Service (pid 1780) connected.
F  [Thr 1624] *** LOG => SAP Start Service (pid 1780) disconnected.
F 
F [Thr 3548] Tue Aug 28 09:18:58 2012
F  [Thr 3548] *** LOG => Signal 13 SIGCHLD.
F 
F [Thr 1624] Tue Aug 28 09:18:58 2012
F  [Thr 1624] *** LOG => Process snapshot stopped (pid 2860).
F  [Thr 1624] *** LOG => Instance state is "Synchronizing binaries" (STOPPING @ 0, INACTIVE).
F  [Thr 1624] *** LOG => Run level 2 completed.
F  [Thr 1624] *** LOG => Instance state is "Some processes failed" (STOPPED @ 0, INACTIVE).
I  [Thr 1624] MPI: dynamic quotas disabled.
I  [Thr 1624] MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%
F 
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  ********************************************************************************
F 
F  [Thr 1624] *** LOG => exiting (exitcode 22002, retcode 1).

[patelyogesh]

Can you post windows log please when you try to start your system.

[Former Member]

Hi, please check if listener is running! if not please start it and try again, also check the user the service has assigned... if this is a domain installation the user has to be domain\sidadm or domain\SAPserviceSID.

Best Regards!

[hemanth2]

Hi Hanif ,

Hope you are doing good.

Please execute a JdbcCheckup as per the below note to check if the

j2ee server is able to communicate fine with the DB:

SAP Note No. 867176: FAQ: Oracle JDBC

If this is successful, paste the relevant details  from configtool log folder and the default trace.

Thank you and have a nice day :).

_____________

Kind Regards,

Hemanth

[former_member261631]

Hi Hemant, Thanks for the reply.I am doing good but facing problems with Portal 7.3 EHP1 Oracle DB files. As you can see above my reply to Mark,I am not able to connect Oracle within or outside SAP MMC in the server OS. Regards, Hanif

[former_member191911]

Have you checked in the mean time if you're able to connect to Oracle via sqlplus and if it's possible to start the database manual?

Kr. Mark

[hemanth2]

Hi Hanif ,

As the server is not able to connect to the DB, please run the JbcCheckup tool as I mentioned earlier:

SAP Note No. 867176: FAQ: Oracle JDBC

Now, the j2ee connects to the DB when the bootstrapping process occurs, so you sgould be able to get the correct error in the below files:

/usr/sap/<SID>/work/ dev_bootstrap*, std_bootstrap* and jvm_bootstrap*

and

/usr/sap/<SID>/JC<nr>/j2ee/cluster/bootstrap/system.log

Please check this.

Thank you and have a nice day :).

_____________

Kind Regards,

Hemanth

[former_member261631]

Hi Hemant, From where I can get JdbcCheckup.sar tool to run JdbcCheckup for Oracle Database. Regards, Hanif

[former_member191911]

It's attached to the note that Hermanth mentioned. Just scroll to the bottom.

Kr. Mark

[hemanth2]

yup, thanks Mark.

@hanif: please see the note No. 867176.

As the error is:

"

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.

"

This means that either the DB connection is faulty or you need to check the bootstrap logs as I mentioned earlier.

Thank you and have a nice day :).

_____________

Kind Regards,

Hemanth

[Former Member]

Hi Hanif,

you seem not to be so experienced with the central Oracle administration tool sqlplus.

Kindly check this out, as it will help you solving this problem as well as maintaining database in the future.

Here would be a good start:

http://www.orafaq.com/wiki/SQL*Plus

As soon as you have an overview, try to start the database using sqlplus and look at the errors. Also check the Oracle tracefile, as I suppose there will be messages about "not readable datafiles". Maybe you forgot to adapt the authorizations appropriately after copying forth and back.

Additionally, check brtools (SAP based database tool using Oracle functions to perform typical tasks) if you try to move datafiles next time:

http://sapbasis.wordpress.com/2012/01/13/brtools-720-for-oracle-10g-and-11g/

As soon as Oracle is online, you may use this experience to solve the configtool problem. Synchronizing binaries phase failing may point to inappropriate authorizations (on source or target directory / files) too.

Good luck!

Peter

[anja_engelhardt2]

moved to SAP Netweaver Application Server Forum by moderator