cancel
Showing results for 
Search instead for 
Did you mean: 

Rename SAP Netweaver CE 7.2

Former Member
0 Kudos

Hi

I tried to rename a SAP Netweaver CE 7.2 System with swpm. On the last step (Import temporary license) i got en error:

Last error reported by the step: Error starting instance 'SCS01': 11.09.2014 12:24:27 Start OK 11.09.2014 12:24:49 StartWait FAIL: process gwrd.EXE Gateway not running .

Any Idea why the gateway does not start?

Kind regards

Peter

Accepted Solutions (0)

Answers (3)

Answers (3)

Sriram2009
Active Contributor
0 Kudos

Hi Peter

1. Could you do the full restart and than start the instance

2. Still are you facing the same issue could you update the full log

BR

SS

divyanshu_srivastava3
Active Contributor
0 Kudos

Hi Peter,

What is your OS ?

Can you share dev_rd log file ?

Regards,

Divyanshu

Former Member
0 Kudos

the os is windows server 2008 R2

Log:

P Thu Sep 11 2014 13:48:54:056 trace file reopened

S Thu Sep 11 2014 13:48:54:056 set gw/reg_no_conn_info to Level : 1

S Thu Sep 11 2014 13:48:54:056 set gw/reg_no_conn_info to Level : 1

divyanshu_srivastava3
Active Contributor
0 Kudos

I am not sure that is an error anyway.

May be you should stop system completely and try again

OR

set gw/acl = 0 in your profiles.

stop sap and restart.

Former Member
0 Kudos

I tried the parameter gw/acl_mode = 0 restartet the sap system - but the same issue:

P Thu Sep 11 2014 14:03:18:804 trace file reopened

S Thu Sep 11 2014 14:03:18:804 set gw/reg_no_conn_info to Level : 1

S Thu Sep 11 2014 14:03:18:804 set gw/reg_no_conn_info to Level : 1

Former Member
0 Kudos

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

trc file: "dev_rd", trc level: 1, release: "720"

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

Thu Sep 11 14:11:13 2014

***LOG S00=> GwInitReader, gateway started ( 1680) [gwxxrd.c     1758]

systemid   562 (PC with Windows NT)

relno      7200

patchlevel 0

patchno    327

intno      20020600

make       multithreaded, Unicode, 64 bit, optimized

pid        1680

gateway runs with dp version 138000(ext=119000) (@(#) DPLIB-INT-VERSION-138000-UC)

gateway (version=720.2012.10.10)

gw/reg_no_conn_info = 1

gw/local_addr : 0.0.0.0

gw/reg_no_conn_info = 1

* SWITCH TRC-RESOLUTION from 1 TO 1

switch off alert monitoring

Bind service 3301 (socket) to port 3301

GwIRegInitRegInfo: reginfo version = 1

*** ERROR => GwInitHostAdrs: GwHostToAddr failed [gwxxaddr.c   227]

***LOG S10=> GwInitReader, GwInitHostAdrs () [gwxxrd.c     2041]

divyanshu_srivastava3
Active Contributor
0 Kudos

Check your host file and update with IP FQDN HOSTNAME

Former Member
0 Kudos

thank you - now it start

Sriram2009
Active Contributor
0 Kudos

You can check the DNS resolution by using the command NSLOOKUP

Former Member
0 Kudos

i was to fast with my last post

now I got this error:

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

trc file: "dev_jstart.3676", trc level: 1, release: "720"

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

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

trc file: "dev_jstart.new", trc level: 1, release: "720"

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

sysno      00

sid        SP6

systemid   562 (PC with Windows NT)

relno      7200

patchlevel 0

patchno    63

intno      20020600

make       multithreaded, Unicode, 64 bit, optimized

profile    \\SPDEV06\sapmnt\SP6\SYS\profile\SP6_J00_SPDEV06

pid        3676

*

*  ACTIVE TRACE LEVEL           1

*  ACTIVE TRACE COMPONENTS      All, egi

*

Thu Sep 11 14:37:31 2014

*

*  trace logging activated, max size = 52428800 bytes, 2 versions

*

arguments :

  arg[ 0] : D:\usr\sap\SP6\J00\exe\jstart.EXE

  arg[ 1] : pf=\\SPDEV06\sapmnt\SP6\SYS\profile/SP6_J00_SPDEV06

F Thu Sep 11 14:37:31 2014

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

F  Java environment properties (D:\usr\sap\SP6\J00\work\jstart.jvm)

F    root directory    : D:\usr\sap\SP6\J00\exe\sapjvm_6

F    vendor            : SAP AG

F    version           : 1.6.0_37

F    cpu               : amd64

F    java vm type      : server

F    java vm version   : 6.1.045 21.1-b06

F    jvm library name  : jvm.dll

F    library path      : D:\usr\sap\SP6\J00\exe\sapjvm_6\jre\bin\server;D:\usr\sap\SP6\J00\exe\sapjvm_6\jre\bin

F    executable path   : D:\usr\sap\SP6\J00\exe\sapjvm_6\bin

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

F    SAP extensions    : available

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

I  [Thr 2288] MtxInit: 30002 0 2

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

trc file: "dev_jstart", trc level: 1, release: "720"

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

*

*  ACTIVE TRACE LEVEL           1

*  ACTIVE TRACE COMPONENTS      All, egi

*

F  [Thr 2288] *** LOG => connected to Enqueue Server.

F  [Thr 2288] *** LOG => connected to Message Server.

F  [Thr 2288] *** LOG => Starting run level 1.

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

F  Java process [deployment] properties:

F    section name     : deployment

F    config file      : D:\usr\sap\SP6\J00\exe\startup.properties

F    node name        : Deploy_offline

F    home directory   : D:\usr\sap\SP6\J00\j2ee\cluster

F    shutdown timeout : 136000 ms

F    exit timeout     : 7000 ms

F    debuggable       : false

F    debugger active  : false

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

F  [Thr 2288] *** LOG => Instance state is "Deploying offline components" (STARTING @ 0, INACTIVE).

F  [Thr 2288] *** LOG => Starting nodes: runlevel 1.

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

F  Starting process: D:\usr\sap\SP6\J00\exe\jstart.EXE

F    arg[ 1] = -nodeId=0

F    arg[ 2] = pf=\\SPDEV06\sapmnt\SP6\SYS\profile\SP6_J00_SPDEV06

F    arg[ 3] = -hostvm

F    arg[ 4] = -nodeName=deployment

F    arg[ 5] = -file=D:\usr\sap\SP6\J00\exe\startup.properties

F    arg[ 6] = -jvmFile=D:\usr\sap\SP6\J00\work\jstart.jvm

F    arg[ 7] = -traceFile=D:\usr\sap\SP6\J00\work\dev_deployment

F    arg[ 8] = -javaOutFile=D:\usr\sap\SP6\J00\work\jvm_deployment.out

F    env   : NODNSSAPTRANSHOST=1

F  exePath : PATH=D:\usr\sap\SP6\J00\exe\sapjvm_6\bin;D:\usr\sap\SP6\J00\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;D:\usr\sap\SP6\SYS\exe\uc\NTAMD64;d:\sapdb\clients\SP6\bin;d:\sapdb\clients\SP6\pgm;D:\sapdb\programs\bin;D:\sapdb\programs\pgm

F  libPath : PATH=D:\usr\sap\SP6\J00\exe\sapjvm_6\jre\bin\server;D:\usr\sap\SP6\J00\exe\sapjvm_6\jre\bin;D:\usr\sap\SP6\J00\j2ee\os_libs;D:\usr\sap\SP6\J00\exe\sapjvm_6\bin;D:\usr\sap\SP6\J00\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;D:\usr\sap\SP6\SYS\exe\uc\NTAMD64;d:\sapdb\clients\SP6\bin;d:\sapdb\clients\SP6\pgm;D:\sapdb\programs\bin;D:\sapdb\programs\pgm

F  stdout  : D:\usr\sap\SP6\J00\work\std_deployment.out

F  stderr  : D:\usr\sap\SP6\J00\work\std_deployment.out

F  console : no

F  debugger: no

F  nice    : no

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

F  Process Deploy_offline started with pid 1640

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

F  [Thr 2288] *** LOG => Process deployment started (pid 1640).

F [Thr 2288] Thu Sep 11 14:37:33 2014

F  [Thr 2288] *** LOG => Process deployment stopping (pid 1640).

F [Thr 4112] Thu Sep 11 14:37:33 2014

F  [Thr 4112] *** LOG => Signal 13 SIGCHLD.

F  [Thr 2288] *** LOG => Process deployment stopped (pid 1640).

F  [Thr 2288] *** LOG => Instance state is "Deploying offline components" (STOPPING @ 0, INACTIVE).

F  [Thr 2288] *** LOG => Run level 1 completed.

F  [Thr 2288] *** LOG => Starting run level 2.

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

F  Java process [bootstrap] properties:

F    section name     : bootstrap

F    config file      : D:\usr\sap\SP6\J00\exe\startup.properties

F    node name        : Instance_bootstrap

F    home directory   : D:\usr\sap\SP6\J00\j2ee\cluster

F    shutdown timeout : 136000 ms

F    exit timeout     : 7000 ms

F    debuggable       : false

F    debugger active  : false

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

F  [Thr 2288] *** LOG => Instance state is "Synchronizing binaries" (STARTING @ 0, INACTIVE).

F  [Thr 2288] *** LOG => Starting nodes: runlevel 2.

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

F  Starting process: D:\usr\sap\SP6\J00\exe\jstart.EXE

F    arg[ 1] = -nodeId=0

F    arg[ 2] = pf=\\SPDEV06\sapmnt\SP6\SYS\profile\SP6_J00_SPDEV06

F    arg[ 3] = -hostvm

F    arg[ 4] = -nodeName=bootstrap

F    arg[ 5] = -file=D:\usr\sap\SP6\J00\exe\startup.properties

F    arg[ 6] = -jvmFile=D:\usr\sap\SP6\J00\work\jstart.jvm

F    arg[ 7] = -traceFile=D:\usr\sap\SP6\J00\work\dev_bootstrap

F    arg[ 8] = -javaOutFile=D:\usr\sap\SP6\J00\work\jvm_bootstrap.out

F    env   : NODNSSAPTRANSHOST=1

F  exePath : PATH=D:\usr\sap\SP6\J00\exe\sapjvm_6\bin;D:\usr\sap\SP6\J00\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;D:\usr\sap\SP6\SYS\exe\uc\NTAMD64;d:\sapdb\clients\SP6\bin;d:\sapdb\clients\SP6\pgm;D:\sapdb\programs\bin;D:\sapdb\programs\pgm

F  libPath : PATH=D:\usr\sap\SP6\J00\exe\sapjvm_6\jre\bin\server;D:\usr\sap\SP6\J00\exe\sapjvm_6\jre\bin;D:\usr\sap\SP6\J00\j2ee\os_libs;D:\usr\sap\SP6\J00\exe\sapjvm_6\bin;D:\usr\sap\SP6\J00\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;D:\usr\sap\SP6\SYS\exe\uc\NTAMD64;d:\sapdb\clients\SP6\bin;d:\sapdb\clients\SP6\pgm;D:\sapdb\programs\bin;D:\sapdb\programs\pgm

F  stdout  : D:\usr\sap\SP6\J00\work\std_bootstrap.out

F  stderr  : D:\usr\sap\SP6\J00\work\std_bootstrap.out

F  console : no

F  debugger: no

F  nice    : no

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

F  Process Instance_bootstrap started with pid 4228

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

F  [Thr 2288] *** LOG => Process bootstrap started (pid 4228).

F [Thr 2288] Thu Sep 11 14:37:36 2014

F  [Thr 2288] *** LOG => Process bootstrap stopping (pid 4228).

F [Thr 4360] Thu Sep 11 14:37:36 2014

F  [Thr 4360] *** LOG => Signal 13 SIGCHLD.

F  [Thr 2288] *** LOG => Process bootstrap stopped (pid 4228).

F  [Thr 2288] *** WARNING => Node bootstrap failed: result 1, exit code 503. [sfxxnode.hpp 1024]

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

F  Native process [snapshot] properties:

F    section name     : snapshot

F    config file      : D:\usr\sap\SP6\J00\exe\startup.properties

F    node name        : snapshot

F    home directory   : D:\usr\sap\SP6\J00\work

F    shutdown timeout : 122000 ms

F    sf support       : false

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

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

F  Starting process: D:\usr\sap\SP6\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=503

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=D:\usr\sap\SP6\J00\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;D:\usr\sap\SP6\SYS\exe\uc\NTAMD64;d:\sapdb\clients\SP6\bin;d:\sapdb\clients\SP6\pgm;D:\sapdb\programs\bin;D:\sapdb\programs\pgm

F  libPath : PATH=D:\usr\sap\SP6\J00\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;D:\usr\sap\SP6\SYS\exe\uc\NTAMD64;d:\sapdb\clients\SP6\bin;d:\sapdb\clients\SP6\pgm;D:\sapdb\programs\bin;D:\sapdb\programs\pgm

F  stdout  : D:\usr\sap\SP6\J00\work\std_snapshot.out

F  stderr  : D:\usr\sap\SP6\J00\work\std_snapshot.out

F  console : no

F  debugger: no

F  nice    : no

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

F  Process snapshot started with pid 2564

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

F  [Thr 2288] *** LOG => Process snapshot started (pid 2564).

F  [Thr 2288] *** LOG => Process snapshot running (pid 2564).

F  [Thr 2288] *** LOG => SAP Start Service (pid 864) connected.

F  [Thr 2288] *** LOG => SAP Start Service (pid 864) disconnected.

F [Thr 3748] Thu Sep 11 14:37:43 2014

F  [Thr 3748] *** LOG => Signal 13 SIGCHLD.

F [Thr 2288] Thu Sep 11 14:37:43 2014

F  [Thr 2288] *** LOG => Process snapshot stopped (pid 2564).

F  [Thr 2288] *** LOG => Instance state is "Synchronizing binaries" (STOPPING @ 0, INACTIVE).

F  [Thr 2288] *** LOG => Run level 2 completed.

F  [Thr 2288] *** LOG => Instance state is "Some processes failed" (STOPPED @ 0, INACTIVE).

I  [Thr 2288] MPI: dynamic quotas disabled.

I  [Thr 2288] MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%

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

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

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  [Thr 2288] *** LOG => exiting (exitcode 22002, retcode 1).

any idea?

thanks for your help

divyanshu_srivastava3
Active Contributor
0 Kudos

can you share set_server0 and std_bootstrap if they are generated.

Refer - 1902005 - J2EE System fails with "exitcode 503"


Also, check you database service is up and running.

Reagan
Product and Topic Expert
Product and Topic Expert
0 Kudos

Go to the work directory D:\usr\sap\SP6\J00\work and check the bootstrap logs

Regards

RB

Former Member
0 Kudos

hmm...this is the log:

[Sep 11, 2014 3:02:42 PM ] Starting to configure the bootstrap

[Sep 11, 2014 3:02:42 PM ]       Bootstrap properties file [D:\usr\sap\SP6\J00\j2ee\cluster\bootstrap\bootstrap.properties] found

[Sep 11, 2014 3:02:42 PM ] Bootstrap configured for [62] ms

[Sep 11, 2014 3:02:42 PM ]

[Sep 11, 2014 3:02:42 PM ] Memory available to the bootstrap JVM: [2 GiB / 2863333376 bytes]

[Sep 11, 2014 3:02:42 PM ]

-----[Bootstrap Module started]--------[Thu Sep 11 15:02:42 CEST 2014]-------

[Sep 11, 2014 3:02:42 PM ]

+------------[Bootstrap synchronization activities information]-----------+

| Runtime Binaries: [X]        Native files: [X] Instance Properties: [X] |

|  Nodes Structure: [X] Cluster File System: [X]    Online bootstrap: [ ] |

+-------------------------------------------------------------------------+

[Sep 11, 2014 3:02:42 PM ] Properties used for initialization: [element.resynch=detect, Logging properties = {log[defaultTrace]=FileLog, .logs=log[defaultTrace],log[consoleLog], log[defaultTrace].pattern=..\..\work\log_bootstrap.log, /.severity=Info, log[consoleLog].formatter=formatter[ConsoleFormatter], formatter[ConsoleFormatter]=TraceFormatter, log[consoleLog]=com.sap.engine.bootstrap.logging.BootstrapConsoleLog, log[defaultTrace].cnt=3, formatter[BootstrapFormatter]=TraceFormatter, log[defaultTrace].formatter=formatter[BootstrapFormatter], formatter[ConsoleFormatter].pattern=%m, log[defaultTrace].limit=5242880, .severity=Info, formatter[BootstrapFormatter].pattern=[%24d] %m}, debug=no, Watchdog properties = {watchdog.timeout=90000, watchdog.check_interval=2000}]

[Sep 11, 2014 3:02:42 PM ] Bootstrap initialized for [109] ms

[Sep 11, 2014 3:02:42 PM ] Watchdog [90000] ms checking every [2000] ms started

[Sep 11, 2014 3:02:42 PM ] Starting to initialize database connection

[Sep 11, 2014 3:02:43 PM ] SecStoreFS object initialized.

[Sep 11, 2014 3:02:43 PM ] setDefaultFilenames () called, filename = "D:\usr\sap\SP6\SYS\global/security/data/SecStore.properties".

[Sep 11, 2014 3:02:43 PM ] File version = "7.00.000.001", software version = "7.00.000.001".

[Sep 11, 2014 3:02:43 PM ] File version = "7.00.000.001", software version = "7.00.000.001".

[Sep 11, 2014 3:02:43 PM ] setDefaultKeyFilename () called, filename = "D:\usr\sap\SP6\SYS\global/security/data/SecStore.key".

[Sep 11, 2014 3:02:43 PM ] Check record okay.

[Sep 11, 2014 3:02:43 PM ] Existing store opened.

[Sep 11, 2014 3:02:43 PM ] File version = "7.00.000.001", software version = "7.00.000.001".

[Sep 11, 2014 3:02:43 PM ] count is 10

[Sep 11, 2014 3:02:43 PM ] size is 10000000

[Sep 11, 2014 3:02:43 PM ] SQL error occurred on connection SPDEV06:SP6:SAPSP6DB: code=-4,004, state="42000", message="[-4004] (at 14): Unknown table name or unknown schema:J2EE_CONFIG";

SQL statement is "INSERT INTO "J2EE_CONFIG"("CID","PARENTCID","CPATH","LINKEDCPATH","PATHHASH","CACHEMODE","PATHPREFIX","CTYPE") VALUES (?, ?, ?, ?, ?, ?, ?, ?)".

[Sep 11, 2014 3:02:43 PM ] SQL error occurred on connection SPDEV06:SP6:SAPSP6DB: code=-4,004, state="42000", message="[-4004] (at 14): Unknown table name or unknown schema:J2EE_CONFIG";

SQL statement is "INSERT INTO "J2EE_CONFIG"("CID","PARENTCID","CPATH","LINKEDCPATH","PATHHASH","CACHEMODE","PATHPREFIX","CTYPE") VALUES (?, ?, ?, ?, ?, ?, ?, ?)".

[EXCEPTION]

com.sap.dbtech.jdbc.exceptions.jdbc40.SQLSyntaxErrorException: [-4004] (at 14): Unknown table name or unknown schema:J2EE_CONFIG

    at com.sap.dbtech.jdbc.exceptions.jdbc40.SQLSyntaxErrorException.createException(SQLSyntaxErrorException.java:53)

    at com.sap.dbtech.jdbc.exceptions.SQLExceptionSapDB.createException(SQLExceptionSapDB.java:251)

    at com.sap.dbtech.jdbc.exceptions.SQLExceptionSapDB.generateDatabaseException(SQLExceptionSapDB.java:138)

    at com.sap.dbtech.jdbc.packet.ReplyPacket.createException(ReplyPacket.java:69)

    at com.sap.dbtech.jdbc.ConnectionSapDB.throwSQLError(ConnectionSapDB.java:1096)

    at com.sap.dbtech.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:720)

    at com.sap.dbtech.jdbc.CallableStatementSapDB.sendCommand(CallableStatementSapDB.java:1840)

    at com.sap.dbtech.jdbc.StatementSapDB.sendSQL(StatementSapDB.java:932)

    at com.sap.dbtech.jdbc.CallableStatementSapDB.doParse(CallableStatementSapDB.java:234)

    at com.sap.dbtech.jdbc.CallableStatementSapDB.constructor(CallableStatementSapDB.java:187)

    at com.sap.dbtech.jdbc.CallableStatementSapDB.<init>(CallableStatementSapDB.java:99)

    at com.sap.dbtech.jdbc.CallableStatementSapDBFinalize.<init>(CallableStatementSapDBFinalize.java:11)

    at com.sap.dbtech.jdbc.ConnectionSapDB.prepareStatement(ConnectionSapDB.java:997)

    at com.sap.dbtech.jdbc.trace.Connection.prepareStatement(Connection.java:347)

    at com.sap.sql.jdbc.direct.DirectConnection.prepareStatement(DirectConnection.java:1430)

    at com.sap.sql.jdbc.direct.DirectConnection.prepareStatement(DirectConnection.java:218)

    at com.sap.engine.core.configuration.impl.persistence.rdbms.DBAccessDefault.init(DBAccessDefault.java:555)

    at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionImpl.<init>(DBConnectionImpl.java:53)

    at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPoolImpl.createConnection(DBConnectionPoolImpl.java:412)

    at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPoolImpl.<init>(DBConnectionPoolImpl.java:179)

    at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandlerImpl.<init>(PersistenceHandlerImpl.java:50)

    at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init>(ConfigurationCache.java:132)

    at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:259)

    at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationManagerBootstrapImpl.java:38)

    at com.sap.engine.bootstrap.StorageAccess.<init>(StorageAccess.java:124)

    at com.sap.engine.bootstrap.Bootstrap.initializeSynchronizer(Bootstrap.java:76)

    at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:243)

    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

    at java.lang.reflect.Method.invoke(Method.java:597)

    at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:162)

[Sep 11, 2014 3:02:43 PM ] Exception occurred for component [internal/unkown] of type [unkown]

com.sap.engine.bootstrap.SynchronizationException: Storage access initialization failed.Check if the database is running and the database connection properties

    at com.sap.engine.bootstrap.StorageAccess.<init>(StorageAccess.java:131)

    at com.sap.engine.bootstrap.Bootstrap.initializeSynchronizer(Bootstrap.java:76)

    at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:243)

    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

    at java.lang.reflect.Method.invoke(Method.java:597)

    at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:162)

----------==[ Caused by: ]==----------

com.sap.engine.frame.core.configuration.ConfigurationException: Error during initialization of DBConnection.

    at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionImpl.<init>(DBConnectionImpl.java:57)

    at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPoolImpl.createConnection(DBConnectionPoolImpl.java:412)

    at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPoolImpl.<init>(DBConnectionPoolImpl.java:179)

    at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandlerImpl.<init>(PersistenceHandlerImpl.java:50)

    at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init>(ConfigurationCache.java:132)

    at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:259)

    at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationManagerBootstrapImpl.java:38)

    at com.sap.engine.bootstrap.StorageAccess.<init>(StorageAccess.java:124)

    at com.sap.engine.bootstrap.Bootstrap.initializeSynchronizer(Bootstrap.java:76)

    at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:243)

    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

    at java.lang.reflect.Method.invoke(Method.java:597)

    at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:162)

Caused by: com.sap.sql.exception.OpenSQLSyntaxErrorException: [-4004] (at 14): Unknown table name or unknown schema:J2EE_CONFIG

    OpenSQLExceptionCategories: [NON_TRANSIENT, DB_OBJECT_UNKNOWN]

    at com.sap.sql.exception.SQLExceptionFactory.createOpenSQLException(SQLExceptionFactory.java:129)

    at com.sap.sql.exception.SQLExceptionFactory.wrapChainedSQLException(SQLExceptionFactory.java:72)

    at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLExceptionJava6(DirectPooledConnection.java:938)

    at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLException(DirectPooledConnection.java:864)

    at com.sap.sql.jdbc.direct.DirectConnection.processSQLException(DirectConnection.java:1524)

    at com.sap.sql.jdbc.direct.DirectConnection.prepareStatement(DirectConnection.java:1434)

    at com.sap.sql.jdbc.direct.DirectConnection.prepareStatement(DirectConnection.java:218)

    at com.sap.engine.core.configuration.impl.persistence.rdbms.DBAccessDefault.init(DBAccessDefault.java:555)

    at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionImpl.<init>(DBConnectionImpl.java:53)

    ... 14 more

Caused by: com.sap.dbtech.jdbc.exceptions.jdbc40.SQLSyntaxErrorException: [-4004] (at 14): Unknown table name or unknown schema:J2EE_CONFIG

    at com.sap.dbtech.jdbc.exceptions.jdbc40.SQLSyntaxErrorException.createException(SQLSyntaxErrorException.java:53)

    at com.sap.dbtech.jdbc.exceptions.SQLExceptionSapDB.createException(SQLExceptionSapDB.java:251)

    at com.sap.dbtech.jdbc.exceptions.SQLExceptionSapDB.generateDatabaseException(SQLExceptionSapDB.java:138)

    at com.sap.dbtech.jdbc.packet.ReplyPacket.createException(ReplyPacket.java:69)

    at com.sap.dbtech.jdbc.ConnectionSapDB.throwSQLError(ConnectionSapDB.java:1096)

    at com.sap.dbtech.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:720)

    at com.sap.dbtech.jdbc.CallableStatementSapDB.sendCommand(CallableStatementSapDB.java:1840)

    at com.sap.dbtech.jdbc.StatementSapDB.sendSQL(StatementSapDB.java:932)

    at com.sap.dbtech.jdbc.CallableStatementSapDB.doParse(CallableStatementSapDB.java:234)

    at com.sap.dbtech.jdbc.CallableStatementSapDB.constructor(CallableStatementSapDB.java:187)

    at com.sap.dbtech.jdbc.CallableStatementSapDB.<init>(CallableStatementSapDB.java:99)

    at com.sap.dbtech.jdbc.CallableStatementSapDBFinalize.<init>(CallableStatementSapDBFinalize.java:11)

    at com.sap.dbtech.jdbc.ConnectionSapDB.prepareStatement(ConnectionSapDB.java:997)

    at com.sap.dbtech.jdbc.trace.Connection.prepareStatement(Connection.java:347)

    at com.sap.sql.jdbc.direct.DirectConnection.prepareStatement(DirectConnection.java:1430)

    ... 17 more

[Sep 11, 2014 3:02:43 PM ] [Bootstrap]> Error during synchronization. More details: the previous log entries

Reagan
Product and Topic Expert
Product and Topic Expert
0 Kudos

Open Configtool.bat from D:\usr\sap\SP6\J00\j2ee\configtool and provide the securestore information.

Regards

RB

divyanshu_srivastava3
Active Contributor
0 Kudos

Hi Peter,


Check if the database is running and the database connection properties

1st check is your database running and your DB services are UP.

Also, are you able to login to configtool ?

divyanshu_srivastava3
Active Contributor
0 Kudos

As 503 error is related to database connection.

Check if DB is up.

Also, share config.properties.

Former Member
0 Kudos

it was a wrong user - i changed the user with the configtool and it looks now it startup

thanks for your help

Reagan
Product and Topic Expert
Product and Topic Expert
0 Kudos

Check the gateway log dev_rd present at /usr/sap/SID/SCS01/work directory

Former Member
0 Kudos

it shows:  set gw/reg_no_conn_info to Level : 1

where can I set dis parameter? in the <sid>scs01_<hostname>?

Kind regards

Reagan
Product and Topic Expert
Product and Topic Expert
0 Kudos

If the gateway is not starting due to that parameter then yes set it in the profile of SCS and restart SAP.

Former Member
0 Kudos

I added the parameter to the config file <SID>\SYS\profile\<SID>_SCS01_<Hostname>

Parameter: gw/reg_no_conn_info=1

The error in the log file is after a reboot of the server still the same