<afreema@cio.sc.gov> wrote in message
news:f181c5b4.0408201210.692ee34@posting.google.co m...[color=blue]
> We have a WebSphere application that quit working this week. It was
> trying to hit DB2 UDB Version 8 on Linux. The Driver is DB2 V7. This
> is the message in the WebSphere logs. Does anyone know what may have
> happened?
>
> [8/18/04 11:17:35:631 EDT] 3e68b4c8 SystemErr R
>[/color]
us.sc.scstoweb.unclaimedproperty.business.Property Search.getLastUpdateDateFr
omDB()...Exception[color=blue]
> selecting from UNCLAIMED_PROP Tables (SQL): SELECT
> TREASURE.UNCLAIMED_PROP.LAST_UPDATE_DATETIME AS
> MinOfLAST_UPDATE_DATETIME FROM TREASURE.UNCLAIMED_PROP WHERE
> TREASURE.UNCLAIMED_PROP.LAST_UPDATE_DATETIME IS NOT NULL fetch first 1
> rows only
> [8/18/04 11:17:35:688 EDT] 3e68b4c8 SystemErr R
> us.sc.scstoweb.business.ReportSet.loadData()...Exc eption opening
> connection to Database...Error: COM.ibm.db2.jdbc.DB2Exception:
> [IBM][CLI Driver][DB2/LINUX] SQL0969N There is no message text
> corresponding to SQL error "-29020" in the message file on this
> workstation. The error was returned from module "SQLRQPIN" with
> original tokens "SQL-289".[/color]
You may have to call IBM Support about this problem.
Your error message basically says that the real problem was SQL29020 but DB2
wasn't able to find the message text for that error so it gave you SQL0969N
instead. (I think SQL0969N usually occurs because you haven't installed the
message files for DB2 correctly but I might be wrong about that.) This is
the writeup for SQL29020:
--------------
SQL29020N An internal error has occurred. Error = error.
Explanation: An error has occurred during internal processing.
User Response: Contact IBM Support and provide the db2diag.log and
qpdiag.log files.
--------------
There's not much of a clue about what the underlying problem may be. You
might find something useful in db2diag.log and/or qpdiag.log; otherwise, you
should probably contact IBM support.
Before calling IBM, you could post the relevant parts of db2diag.log or
qpdiag.log and maybe someone here will have some idea what is going wrong
for you.
One other thing: SQL29020N appears to be a message that is new to DB2 V8; my
V7 manuals don't have it. Perhaps that is why you aren't getting the message
properly; DB2 may be trying to look it up in the V7 message file, not the V8
message file.
Rhino
