cancel
Showing results for 
Search instead for 
Did you mean: 

Problem connection j2ee with database DB2

Former Member
0 Kudos

Hi, i have problem connection j2ee with database db2. the instance java not start. attached the log error.

Exception occurred:

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

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

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)

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

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.

any idea?? help please.

Accepted Solutions (1)

Accepted Solutions (1)

sunny_pahuja2
Active Contributor
0 Kudos

Hi,

It looks like DB2 license issue. Please check whether you have applied DB2 license or not.

Thanks

Sunny

Former Member
0 Kudos

Hi, Sunny, how check license??

sunny_pahuja2
Active Contributor
0 Kudos

Hi,

login with db2<sid> user and run command db2licm -l. If it is showing you expired then it means u have not applied db2 license.

Thanks

Sunny

Former Member
0 Kudos

Hi Sunny, show commands:

mxmlnbw02:db2epd 10% db2licm -l

Product name: "DB2 Enterprise Server Edition"

License type: "Trial"

Expiry date: "09/04/2011"

Product identifier: "db2ese"

Version information: "9.7"

Product name: "DB2 Connect Server"

License type: "Trial"

Expiry date: "09/04/2011"

Product identifier: "db2consv"

Version information: "9.7"

mxmlnbw02:db2epd 11% db2start

06/10/2011 08:38:46 0 0 SQL1063N DB2START processing was successful.

SQL1063N DB2START processing was successful.

mxmlnbw02:db2epd 12% ps -ef | grep db

root 21016 2807 0 08:38:43 pts/6 0:01 db2syscr

db2epd 21029 20666 0 08:38:50 pts/6 0:00 grep db

db2epd 21021 21016 0 08:38:46 pts/6 0:01 db2fmpr 0,0,0,0,1,0,0,0,1,0,8a6678,14,20014,2,0,1,1ffc0,210000000,210000000,160

root 21019 21017 0 08:38:44 ? 0:00 db2syscr

root 21020 21017 0 08:38:44 ? 0:00 db2syscr

root 21018 21017 0 08:38:44 ? 0:00 db2syscr

db2epd 21028 20666 0 08:38:50 pts/6 0:00 ps -ef

db2epd 20666 19414 0 08:36:26 pts/6 0:00 -csh

db2epd 21017 21016 0 08:38:44 ? 0:01 db2sysc

mxmlnbw02:db2epd 14% db2stop

06/10/2011 08:39:20 0 0 SQL1064N DB2STOP processing was successful.

SQL1064N DB2STOP processing was successful.

mxmlnbw02:db2epd 15% ps -ef | grep db

db2epd 21053 20666 0 08:39:24 pts/6 0:00 ps -ef

db2epd 21054 20666 0 08:39:24 pts/6 0:00 grep db

db2epd 20666 19414 0 08:36:26 pts/6 0:00 -csh

Answers (2)

Answers (2)

sivakumar_kilari3
Active Contributor
0 Kudos

Hi,

[http://publib.boulder.ibm.com/infocenter/db2luw/v8/index.jsp?topic=/com.ibm.db2.udb.doc/core/rql10000.htm]

SQL10003C

There are not enough system resources to process the request. The request cannot be processed.

Explanation:

The database manager could not process the request due to insufficient system resources. The resources that can cause this error include:

The amount of memory in the system

The number of message queue identifiers available in the system.

User Response:

Stop the application. Possible solutions include:

Remove background processes.

Terminate other applications using the above resources.

If you are using Remote Data Services, increase the Remote Data Services heap size (rsheapsz) in the server and client configuration because at least one block is used per application.

NOTE: This is applicable only for releases of DB2 prior to Version 2.

Decrease the values of the configuration parameters that define allocation of memory, including ASLHEAPSZ if UDFs are involved in the failing statement.

Avoid accessing large files or use non-buffered I/O. To use non-buffered I/O, set the DB2 registry variable DB2_DIRECT_IO to YES.

sqlcode : -10003 sqlstate : 57011

Thanks

Siva

Former Member
0 Kudos

Hi, Siva, I think problem is connect J2ee with DB2

See run command

mxmlnbw02:db2epd 11% db2start

06/10/2011 08:38:46 0 0 SQL1063N DB2START processing was successful.

SQL1063N DB2START processing was successful.

mxmlnbw02:db2epd 12% ps -ef | grep db

root 21016 2807 0 08:38:43 pts/6 0:01 db2syscr

db2epd 21029 20666 0 08:38:50 pts/6 0:00 grep db

db2epd 21021 21016 0 08:38:46 pts/6 0:01 db2fmpr 0,0,0,0,1,0,0,0,1,0,8a6678,14,20014,2,0,1,1ffc0,210000000,210000000,160

root 21019 21017 0 08:38:44 ? 0:00 db2syscr

root 21020 21017 0 08:38:44 ? 0:00 db2syscr

root 21018 21017 0 08:38:44 ? 0:00 db2syscr

db2epd 21028 20666 0 08:38:50 pts/6 0:00 ps -ef

db2epd 20666 19414 0 08:36:26 pts/6 0:00 -csh

db2epd 21017 21016 0 08:38:44 ? 0:01 db2sysc

The database start and stop successful

How test connection j2ee to DB??

Former Member
0 Kudos

Hi, this new error

mxmlnbw02>epdadm: more /home/epdadm/JdbcCon.log

Start: Mon Jun 13 09:08:56 CDT 2011

Error: Couldn't connect to DB

com.ibm.db2.jcc.am.DisconnectNonTransientConnectionException: [jcc][t4][2043][11550][3.59.81] Exception java.net.ConnectException: Error opening socket to server mxmlnbw02/10.20.0.61 on port 5,913 with message: Connection refused. ERRORCODE=-4499, SQLSTATE=08001

Edited by: Eli Daniel Ramones on Jun 13, 2011 11:17 AM

Former Member
0 Kudos

I solved problem, apply notes modify parameters Kernel operation system.

Thanks

Former Member
0 Kudos

Hi Eli,

First Check DB2 database is up and running!!!

Then Check Profiles