cancel
Showing results for 
Search instead for 
Did you mean: 

J2EE Engine Does not starts

Former Member
0 Kudos

Hi,

I am using WebAS7.0, The SAP MMC does not start the Jcontrol instance remains yellow and does not change into green.

When i try to start Config tool to resolve the issue i get the error "<b>Error occurred while working with Configuration (Scanning). Msg Error while connecting to DB</b>.” So I could not connect to config tool.

when i see the developer trace for Jcontrol.exe then it shows that

" ERROR Invalid return code for process [bootstrap] [exitcode = 66] [jstartxx.c 1452]"

"JcontrolExecuteBootstrap:Error executing bootstrap node [rc 66]"

I have seen the jvm_bootstrap.out file then it shows that database initialization fail and so it raises the exeption

I beleive this is because of full DB log files can anyone give idea regarding how to delete or take backup of old db logfiles, so that my J2EE engine starts.

Here is what my bootstrap log says

-


Bootstrap MODE:

<INSTANCE GLOBALS>

determined by parameter [ID0087499].

-


Exception occured:

com.sap.engine.bootstrap.SynchronizationException: Database initialization failed! Check database properties!

at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:422)

at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:144)

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

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:324)

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

-


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


com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.

at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:360)

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

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

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

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

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

at com.sap.engine.bootstrap.Synchronizer.<init>(Synchronizer.java:66)

at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:419)

at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:144)

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

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:324)

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

Caused by: java.sql.SQLException: ORA-01033: ORACLE initialization or shutdown in progress

at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:111)

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:330)

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:282)

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:277)

at oracle.jdbc.driver.T4CTTIoauthenticate.receiveOsesskey(T4CTTIoauthenticate.java:292)

at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:356)

at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:419)

at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:164)

at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:34)

at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:752)

at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:215)

at com.sap.sql.connect.OpenSQLDataSourceImpl.createPooledConnection(OpenSQLDataSourceImpl.java:600)

at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:285)

at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:302)

... 14 more

[Bootstrap module]> Problem occured while performing synchronization.

Please help immediately....

Thanks

Saurabh.

Accepted Solutions (0)

Answers (6)

Answers (6)

Former Member
0 Kudos

Hi i have got the solution:

In case of Oracle database while it is up it keeps on creating a file CWPARCHARC00<xxx>_<xxxxxxxxxx>.001 for example CWPARCHARC00403_0569681871.001 at the location

<drive>:\oracle\<SID>\oraarch\. After seeing into various log files i came to know that this file is not being created any more, So i got my answer took backup of all the CWPARCHARC00403_0569681871.001 files at some other location and restarted webAS and the J2EE started with both the green instances.

Thanks

Saurabh.

Former Member
0 Kudos

Hi i have got the solution:

In case of Oracle database while it is up it keeps on creating a file CWPARCHARC00<xxx>_<xxxxxxxxxx>.001 for example CWPARCHARC00403_0569681871.001 at the location

<drive>:\oracle\<SID>\oraarch\. After seeing into various log files i came to know that this file is not being created any more, So i got my answer took backup of all the CWPARCHARC00403_0569681871.001 files at some other location and restarted webAS and the J2EE started with both the green instances.

Thanks

Saurabh.

Former Member
0 Kudos

Hi Saurabh,

May be the problem is that, database is full for sapmmc. Just check it through the sapmmc.

1 : logon to DBM-J2E instance.

2 : Check the used and free space for all data area(disk1, disk2....) in information block.

3 : if all the data area is fulled then go to configuration block and select Volumes. There you will get button for "add data volume".

4: just increase the data disk area for sapmmc through clicking the button.

5: now restart the server.

-


hope it will work for you----


thanks & regard,

Pankaj Shandilya

Former Member
0 Kudos

Hi,

Although my DB is running but i get see the error

<b>Archive process error: ORA-16038: log 3 sequence# 451 cannot be archived

ORA-19504: failed to create file ""

ORA-00312: online log 3 thread 1: 'D:\ORACLE\CWP\ORIGLOGA\LOG_G13M1.DBF'

ORA-00312: online log 3 thread 1: 'D:\ORACLE\CWP\MIRRLOGA\LOG_G13M2.DBF'

.</b>

in the eventvwr logs.

Can u help me on this, as to how i can get this Archive error resolved?

Former Member
0 Kudos

Hi,

Just check the space in your archive log destination.

Make sure that it is not full.

Srinivas

Former Member
0 Kudos

Hi Srinivas,

Can you plz tell me how to know whether the DB is online/up or not?

Also i am trying to delete all the *.ldf files and then try to restart the J2EE server, just a query are these *.ldf files specific to db log files?

i will let u know if your solution works.

Thanks

Saurabh.

Former Member
0 Kudos

Hi,

u chk this link to know whether ur db is up and running

http://help.sap.com/saphelp_nw04s/helpdata/en/44/4e43473045376ee10000000a114a6b/frameset.htm

and*.ldf files are the database log files .

Regards

srinivas

Former Member
0 Kudos

Hi ,

Since ur log file is full u need to clear the logs.Go to ur <SID>LOG folder where the log files (*.ldf) are present take a backup of them to different folder.

Reward Points

Thanks

srinivas