Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

No start instance Java (problem connection database DB2)

Hi, I have problem with start instance Java, problem connectio database.

S.O: Solaris

Database: DB2

show log db2:

ADM7519W DB2 could not allocate an agent. The SQLCODE is "-1225".

show log directory work:

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

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

at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.<init>(Persistence

Handler.java:38)

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

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

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

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

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

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

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

Caused by: com.ibm.db2.jcc.am.SqlException: DB2 SQL Error: SQLCODE=-10003, SQLSTATE=57011, SQLERRMC=null, DRIVER=3.59.81

[Bootstrap module]> Problem occurred while performing synchronization.

Help please.

Former Member
Former Member replied

Hey Eli,

It looks like a memory issue. It would be good if you could provide more lines from db2diag.log file.

Please make sure that DB2 configuration complies with the default suggested. Below link would help you understand better.

http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/index.jsp?topic=/com.ibm.db2.luw.qb.server.doc/doc/t0008238.html

More over set the ulimit for virtual memory and maximum memory size to unlimited in order to maximize the use of your current physical memory, after that restart DB2.

Please let us know if issue gets resolved.

Cheers!!!

Vishi Rajvanshi

0 View this answer in context
Not what you were looking for? View more on this topic or Ask a question