Topic
2 replies Latest Post - ‏2011-04-07T16:50:13Z by SystemAdmin
SystemAdmin
SystemAdmin
462 Posts
ACCEPTED ANSWER

Pinned topic Stale DB2 Connections

‏2011-04-06T20:46:46Z |
We have a DB2 datasource that succeeds in v6.1 but consistantly fails in v8.0. We know the database credentials are good. We've tested them with a little standalone java app. But from WAS it never seems to work. Why can't we get this working?
From the logs:

<=================================>Next Linked Exception: <=================================>Exception Message -> DB2 SQL error: SQLCODE: -204, SQLSTATE: 42704, SQLERRMC: WASCONN.TEST DSRA0010E: SQL State = 42704, Error Code = -204 SQLException  Error Code -> -204 SQLException  SQLState -> 42704 com.ibm.websphere.ce.cm.StaleConnectionException: DB2 SQL error: SQLCODE: -204, SQLSTATE: 42704, SQLERRMC: WASCONN.TEST DSRA0010E: SQL State = 42704, Error Code = -204
Updated on 2011-04-07T16:50:13Z at 2011-04-07T16:50:13Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    462 Posts
    ACCEPTED ANSWER

    Re: Stale DB2 Connections

    ‏2011-04-07T11:53:47Z  in response to SystemAdmin
    The -204 error is saying that the table WASCONN.TEST is not found in the database to which you are connecting.

    Is there a possibility that the new datasource is connecting to the wrong database? Or did you mean that TEST is in a different schema and you aren't sure why WASCONN is being referenced?

    Please share a little more detail and we can decide what else to look at.

    Paul Johnsen
    WebSphere Application Server RRA development
    • SystemAdmin
      SystemAdmin
      462 Posts
      ACCEPTED ANSWER

      Re: Stale DB2 Connections

      ‏2011-04-07T16:50:13Z  in response to SystemAdmin
      Ok, we figured it out and it was pretty dumb. The problem was the pretest string we had in there. The wsadmin process we built to create datasources had a poor choice of SQL as default. All is good now.

      Thanx!