We're getting the following SQL return code:

DB2CLI GetError
E: Database error (1): '57011' native code: -904 msg-len: 170
msg: '[IBM][CLI Driver][DB2] SQL0904N Unsuccessful execution caused by
an unavailable resource. Reason code: "",
type of resource: "", and resource name: "". SQLSTATE=57011

Environment: SuSE Linux SLES 8 for S/390
connected to z/OS 390 with DB2 7.2

As you see there's neither a reason code nor a resource name.

Any ideas why the error occured?
And why there's no reason code/resource name?

We have no clue where to poke around.

sqllib/db2dump/db2diag.log would be a good place to start...

mgrd wrote:
> We're getting the following SQL return code:
>
> DB2CLI GetError
> E: Database error (1): '57011' native code: -904 msg-len: 170
> msg: '[IBM][CLI Driver][DB2] SQL0904N Unsuccessful execution caused by
> an unavailable resource. Reason code: "",
> type of resource: "", and resource name: "". SQLSTATE=57011
>
> Environment: SuSE Linux SLES 8 for S/390
> connected to z/OS 390 with DB2 7.2
>
> As you see there's neither a reason code nor a resource name.
>
> Any ideas why the error occured?
> And why there's no reason code/resource name?
>
> We have no clue where to poke around.

Hello,

DB2 z/OS reason codes can be very particular to that platform and older DB2
Connect versions may not always handle them in a correct manner. The -904
SQLCODE can arise for various reasons, from a special type of lockout or an
utility in progress up to a missing database file. Usually, DB2 for z/OS
records more useful information regarding the error to it's console log
(aka "Joblog" or "JES-output" to your z/OS-guys), which can help to narrow
down the problem.

Cheers - Walter.


"mgrd" <mgrd@gmx.net> schrieb im Newsbeitrag
news:32b9b2F3j3oapU1@individual.net...
> We're getting the following SQL return code:
>
> DB2CLI GetError
> E: Database error (1): '57011' native code: -904 msg-len: 170
> msg: '[IBM][CLI Driver][DB2] SQL0904N Unsuccessful execution caused by
> an unavailable resource. Reason code: "",
> type of resource: "", and resource name: "". SQLSTATE=57011
>
> Environment: SuSE Linux SLES 8 for S/390
> connected to z/OS 390 with DB2 7.2
>
> As you see there's neither a reason code nor a resource name.
>
> Any ideas why the error occured?
> And why there's no reason code/resource name?
>
> We have no clue where to poke around.