|
View previous topic :: View next topic
|
| Author |
Message |
rahuindo
New User
Joined: 09 Apr 2008
Posts: 83
Location: Chennai
|
|
|
|
Hi,
While exectuing a set of jobs, we encountered the following Error:
"DSNT408I SQLCODE = -904, ERROR: UNSUCCESSFUL EXECUTION CAUSED BY AN UNAVAILABLE RESOURCE. REASON 00E30305 RESOURCE 00000801
DSNT418I SQLSTATE = 57011 SQLSTATE RETURN CODE
DSNT415I SQLERRP = DSNXEAAL SQL PROCEDURE DETECTING ERROR
DSNT416I SQLERRD = -150 0 0 -1 0 0"
What can be the possible reason for this error code? Is it because of REBIND issues or lack of DB2 Virtual Storage space? |
|
| Back to top |
|
 |
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne
|
|
|
|
you can look the message up yourself at IBM's Message Help website:
www-03.ibm.com/servers/eserver/zseries/zos/bkserv/lookat/
by the way, professionals use dsntiar to display the complete message/description of negative sql codes.
had you done so, you would have seen the token for the resource.
as it is, you have to go thru the reason/resource codes contained in the documentation which the above link will present to you. |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
search the db2 manuals for the resource identified by 00000801
and act accordingly |
|
| Back to top |
|
|
Gnanas N
Active Member
Joined: 06 Sep 2007
Posts: 792
Location: Chennai, India
|
|
|
|
It seems automatic REBIND was issued for a non-operational package and it failed.
Reason code says package referred is not operational. And find out what made package non-operational and run REBIND for that package. |
|
| Back to top |
|
|
rahuindo
New User
Joined: 09 Apr 2008
Posts: 83
Location: Chennai
|
|
|
|
Thanks for all your responses.
Part of the problem occurred due to the introduction of a new table C. This table C had a foreign key association with a Table A. Hence all the programs which were having association with the Table A became invalid. Further all the packages which depended on objects having Referential Integrity with Table A also became invalid. It seems strange but during we observed it during the simulation of the problem.
As we have the AutoBind facility, most of the packages became Valid again. But the program which got abended somehow did not get ReBind and hence became inoperative.
Now we are trying to figure out that what would have caused the Rebind to fail for two programs but it passed for the other programs!!
Hope i am able to explain things to you all!!!
Please let me know if you have any updates.
If i find out something i will surely keep you posted with it. |
|
| Back to top |
|
|
|
|
