It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,874
×6,033
×53
×37

question asked: Apr 28 '14, 9:21 a.m.
question was seen: 26,626 times
last updated: Apr 28 '14, 9:23 a.m.

Related questions

SQL Error: SQLCODE=-964, SQLSTATE=57011 and ETL job fails

2
1
Sumant Renukarya (1.1k●2●33●39) | asked Apr 28 '14, 9:21 a.m.
 Running workitem job fails with the following errors in the logs, after enabling debug logging for ETL: 

***

CRJAZ0265E The database resource or virtual storage is not available.
SQL: INSERT INTO "RICALM"."REQUEST_BASELINE" ("REQUEST_HISTORY_ID", "REC_DATETIME") VALUES (?, ?)
SQL Exception #1
SQL Message: DB2 SQL Error: SQLCODE=-964, SQLSTATE=57011, SQLERRMC=null, DRIVER=4.14.121
SQL State: 57011
Error Code: -964

***

How to resolve this? 

One answer

Most liked answers ↑|Newest answers|Oldest answers

2
permanent link
Sumant Renukarya (1.1k●2●33●39) | answered Apr 28 '14, 9:23 a.m.
--> Based on the DB2 error, it most likely was that the DB2 transaction log was filled up:

https://publib.boulder.ibm.com/infocenter/db2luw/v9r5/index.jsp?topic=%2Fcom.ibm.db2.luw.messages.sql.doc%2Fdoc%2Fmsql00964c.html&resultof%3D%2522%252d%2539%2536%2534%2522%2520%2522%2539%2536%2534%2522%2520

After increasing the log file size, the ETL jobs started running fine without errors.

http://publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp?topic=%2Fcom.ibm.db2.udb.spatial.doc%2Fcfgtranslog.html

In my case, increasing the logprimary and logsecond resolved the DB2 errors

One should check the LOGFILESIZ, LOGPRIMARY and LOGSECOND values, and increase them.
Then run the ETL. 

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.