SQLCODE -904

gylbharat · Posted: Wed Dec 14, 2011 11:27 am

Hi,

Yesterday, while going testing for programmatic load,my job failed with sqlcode -904. Resource unavailable.

senthilnathanj · New User Joined: 31 Jul 2007 Posts: 47 Location: chennai

Check all the Database/Tablespace Status is START or STOP.

gylbharat · Posted: Wed Dec 14, 2011 12:42 pm

I checked the Database and Tablespaces. All were in RW mode.

senthilnathanj · New User Joined: 31 Jul 2007 Posts: 47 Location: chennai

May be the Problem will occur the following reasons:
•Console output from the system on which the job was run, and a listing of the SYSLOG data set for the period of time spanning the failure.
•SVC dump (or system dump), taken to SYS1.DUMPxx data set, as result of an operator-initiated dump command or SLIP trap exit.
•SYSABEND, SYSUDUMP, or SYSMDUMP output.
•Listing of SYS1.LOGREC data set, obtained by executing IFCEREP1.
•IDCAMS LISTCAT output for the ICF (VSAM) catalog that contains the DB2 subsystem catalog that defined the failing index or table.
•VTOC listing of the disk volume on which the failing operation occurred.
•Listing of the results produced by the SQL statements.
•SYSPRINT output, including JCL, for the application program or batch job, and system messages that were issued. Make sure that MSGLEVEL=(1,1) on the JOB statement so that all diagnostic information is sent to SYSPRINT.
•Definitions of views and tables involved in the error.

gylbharat · Posted: Wed Dec 14, 2011 1:25 pm

rakesha.hg · Posted: Wed Dec 14, 2011 2:01 pm

GuyC · Posted: Wed Dec 14, 2011 2:16 pm

Maybe there is just not enough space available. Check with your SMS guy.

gylbharat · Posted: Wed Dec 14, 2011 2:41 pm

GuyC · Posted: Wed Dec 14, 2011 2:52 pm

I'm no space person.
I do know that depending on SMS definitions certain VSAMs can only use certain volumes (=SMS storage group) and sometimes they have to add volumes or tell us to clean up.

gylbharat · Posted: Wed Dec 14, 2011 2:59 pm

ok... Thanks GuyC...

db2sysdba.zos · New User Joined: 04 Oct 2011 Posts: 25 Location: INDIA

Tell me whether your database is SMS managed or not?

gylbharat · Posted: Wed Dec 14, 2011 5:17 pm

Yes... The database is SMS managed.

db2sysdba.zos · New User Joined: 04 Oct 2011 Posts: 25 Location: INDIA

Fire this command in the console

DD CLEAR,DSN=ALL

Then check the target tablespace status,which you are going to load. ensure that RW mode.

then execute the LOAD.

gylbharat · Posted: Wed Dec 14, 2011 5:43 pm

db2sysdba.zos · New User Joined: 04 Oct 2011 Posts: 25 Location: INDIA

DD CLEAR,DSN=ALL

It's a MVS Command. Get your zO/S system administrator help, before firing this command in zO/S console.

gylbharat · Posted: Wed Dec 14, 2011 5:50 pm

Hi,

I will not be able to get the system admin help on this... As he would be asking too many questions... And also he if from client side.

db2sysdba.zos · New User Joined: 04 Oct 2011 Posts: 25 Location: INDIA

I will clear you why I asked you to fire that command.

you are getting this error code. 00D70014

Since your database is SMS managed and its extends is below 251 there is nothing wrong with your extends or space( assumed that your storage group is SMS managed and there eonugh volumes for spanning).

So, conclusion is since you had the error code 00D70014 ,

Problem is with SYS1.DUMPxx.

If it's a testing region and if you have the authority to fire the MVS command, you can fire the above mentioned command there by you cal clear the DUMP DSN.

Then make sure your TS & Indexspace are in RW mode, before go ahead with LOAD Utility.

gylbharat · Posted: Wed Dec 14, 2011 6:47 pm

Thanks... I will check if i am able to run that command.

Before firing the command, how can we check if actual issue is with the SYS1.DUMPxx?