Topic
IC4NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
2 replies Latest Post - ‏2015-05-19T23:40:35Z by DeepakPydimarry
amccarl
amccarl
73 Posts
ACCEPTED ANSWER

Pinned topic ERRORCODE=-4499 rejected establishment of the connection

‏2013-06-12T21:38:33Z |
 
Attempt to connect to a database using Type 4 JCC driver fails with the following exception:
 
java.sql.SQLException: 
[jcc][t4][2057][11264][3.53.95] The application server rejected establishment of the connection. An attempt was made to access a database, <database name>, which was either not found or does 
not support transactions. ERRORCODE=-4499, 
SQLSTATE=08004 DSRA0010E: SQL State = 08004, Error Code = -4,499 
 
Using DCS DB alias or local alias name of the database in the connection string will cause this error. The URL format for IBM Data Server Driver for JDBC and SQLJ type 4 connectivity is:
 
"jdbc:db2://<server name>: <portnumber>/<database name>";
 
In the Type 4 JDBC JCC driver connection string used, 
If the connection is to a DB2 for Linux,Unix,Windows server, the database name should be the Target database name in the database server, it should not be the local alias name cataloged in the client.
If the connection is to a DB2 for z/OS server, database name is the DB2 location name that is defined during installation. All characters in the DB2 location name must be upper-case characters. The IBM Data Server Driver for JDBC and SQLJ does not convert lower-case characters in the database value to upper-case for IBM Data Server Driver for JDBC and SQLJ type 4 connectivity.
The location name can be found by executing the following SQL statement on the server:
SELECT CURRENT SERVER FROM SYSIBM.SYSDUMMY1;
 
The target database name can also be found from the DCS directory on the client using the command:
db2 list dcs directory.

This is also covered by the technical article 1443723,  http://www.ibm.com/support/docview.wss?uid=swg21443723

 

Updated on 2013-06-14T14:34:48Z at 2013-06-14T14:34:48Z by amccarl
  • amccarl
    amccarl
    73 Posts
    ACCEPTED ANSWER

    Re: ERRORCODE=-4499 rejected establishment of the connection

    ‏2013-06-14T14:22:42Z  in response to amccarl
    Hello!  We've had a number of clients respond through feedback to our technical documents indicating that they have further questions or comments that require additional dialogue.  Unfortunately, our feedback is anonymous, so unless an email address or other contact information is included, we have no way to get back in touch with you.
     
    Within DB2 support, the management team asked if we could somehow link our documents to the forums so that we could invite more discussion - like this!   As a start, we chose about 30 technical articles and "seeded" the forum with initial entries so that we could have a starting place for conversation.  The documents have now been updated with links to the forums as well.  
     
    Hopefully, we will make DB2 support better by providing more interaction around our technical information!
     
    • DeepakPydimarry
      DeepakPydimarry
      1 Post
      ACCEPTED ANSWER

      Re: ERRORCODE=-4499 rejected establishment of the connection

      ‏2015-05-19T23:40:35Z  in response to amccarl

      Hello,

       

      We ran into this error and interestingly it occurs only intermittently. Reading at the article I could not decipher if using the local alias would result in getting this exception consistently or it is going to be intermittent. I suspect there might be some other problem that is contributing. Any help would be appreciated.

       

      Thanks