We are having problems connecting to DB2 and it gives an error stating,
com.wm.pkg.art.error.DetailedServiceException: [ART.118.5053] Adapter Runtime (Connection): Unable to get a connection to resource CASS_Env:db2.
[ADA.1.204] Cannot connect to the database with DataSource class “COM.ibm.db2.jdbc.DB2DataSource”.
[IBM][CLI Driver] SQL1032N No start database manager command was issued. SQLSTATE=57019
We are using DB2JD to connect tothe Database adn it is started properly.
Our Env is
IS 601 SP2 (With Fixes)
JDBC Adapter 602
Any ideas would be appreciated.
Let me know if any further information is required.
This is from a DB2 pdf i got which explains about your error. I would recommend you contact your DB2 Administrator regarding this issue.
SQL1032N No start database manager
command was issued.
Explanation:
The start database manager
command has not been processed. It must be
processed before a stop database manager, any
SQL statement, or utility can be issued.
The command cannot be processed.
User Response:
Issue a start database manager
command and resubmit the current command.
If using multiple logical nodes, ensure the
DB2NODE environment variable is set correctly.
The DB2NODE environment variable indicates
the node the application will attempt to connect
to. DB2NODE must be set to the node number of
one of the nodes defined on the same host as the
application.
Note that in a partitioned database environment,
the RESTART database command is run on a
per-node basis. To ensure that the database is
restarted on all nodes, use the command:
db2_all db2 restart database
<database_name>
This command may have to be run several times
to ensure that all in-doubt transactions have been
resolved.
If you are installing the sample database, drop it
and install the sample database again.
Yes you are correct. I forgot to update here. I also found that for some weird reason the normal startup script for DB2 (db2start) didnt run when the Unix machine was rebooted and we from Integration perspective got the DB2Connect up and were trying to connect to the Database.
We resolved the issue by issuing the db2Start command and re-starting the DB2Connect and the IS. I re-started the IS just to make sure that the connections are refreshed.