469,360 Members | 1,807 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,360 developers. It's quick & easy.

DB2 problem when accessing via a web page

I have a system that has been working fine for months, until this week.
This is the error message that I am now getting :

A DB2 problem occurred.
Sqlcode: -712 Sqlstate: 57011 , Sqlerrd.1: -140
Sqlerrd.2: -136
Sqlerrp: ARIXRST

I suspect it is something to do with space. If my selection criteria results
on a lot of data (40,000+) being returned, the problem occurs. If I only
select a small amount of data (<40,000), it works perfectly.
The system runs on a VM server

I have been trying to resolve this for a week now so any help would be most
appreciated.

TIA
Steve
Nov 19 '05 #1
4 2556
Steve B wrote:
I have a system that has been working fine for months, until this week.
This is the error message that I am now getting :

A DB2 problem occurred.
Sqlcode: -712 Sqlstate: 57011 , Sqlerrd.1: -140
Sqlerrd.2: -136
Sqlerrp: ARIXRST

I suspect it is something to do with space. If my selection criteria results
on a lot of data (40,000+) being returned, the problem occurs. If I only
select a small amount of data (<40,000), it works perfectly.
The system runs on a VM server

I have been trying to resolve this for a week now so any help would be most
appreciated.

TIA
Steve

Can't find explanations for any of these error msgs or codes in the DB2
doc. What's in the db2diag.log at the exact time when this occurs?

Larry Edelstein
Nov 19 '05 #2
"Larry" <la***@nospam.net> wrote in message
news:H8******************@fe12.lga...
Can't find explanations for any of these error msgs or codes in the DB2
doc. What's in the db2diag.log at the exact time when this occurs?

Larry Edelstein


DB2 is running on VM OS according to OP.
Nov 19 '05 #3
In article <dl**********@news6.svr.pol.co.uk>, Steve B
(st***@beard.worldonline.co.uk) says...
I have a system that has been working fine for months, until this week.
This is the error message that I am now getting :

A DB2 problem occurred.
Sqlcode: -712 Sqlstate: 57011 , Sqlerrd.1: -140
Sqlerrd.2: -136
Sqlerrp: ARIXRST

I suspect it is something to do with space. If my selection criteria results
on a lot of data (40,000+) being returned, the problem occurs. If I only
select a small amount of data (<40,000), it works perfectly.
The system runs on a VM server

I have been trying to resolve this for a week now so any help would be most
appreciated.

TIA
Steve


I copied the message text from the DB2 Server for VM V7 bookshelf at
the IBM website, you can find it at the (wrapped) link:
http://publibfp.boulder.ibm.com/cgi-...lves/arivbs20?
FS=TRUE

--------------------------------------------------

-712 The SQL statement failed because internal dbspaces were not
available or were too small.

Explanation: The system may require internal dbspaces to process SQL
statements involving ORDER BY, GROUP BY, or joins. Either it was
unable to acquire enough internal dbspaces, or the internal dbspaces
were not large enough to process the command.
SQLSTATE 57011.
System Action: Processing of the SQL statement has ended.
User Response: If SQLERRD2 = -74, internal dbspaces are returned to
the system by a COMMIT or ROLLBACK statement. If you have issued
previous SELECT statements without doing a COMMIT statement, you
could alleviate the problem by issuing COMMIT statements interspersed
with your other SQL statements. Also, notify your system programmer
to increase the number of internal dbspaces in the system.
If SQLERRD2 = -77, -78 or -136 notify your system programmer to
increase the size of the internal dbspaces.
System Programmer Response: If SQLERRD2 = -74, allocate additional
internal dbspaces using the ADD DBSPACE operation (SQLADBSP EXEC) and
resubmit the original command.
If SQLERRD2 = -77, -78 and -136, perform an ADD DBSPACE operation
(SQLADBSP EXEC) for internal dbspaces with a larger size parameter
than previously specified and resubmit the original command.
Nov 19 '05 #4
Thanks for all that, it looks like it will be very helpful. I will let you
know how it goes.

"Gert van der Kooij" <ge**@invalid.nl> wrote in message
news:MP************************@news.xs4all.nl...
In article <dl**********@news6.svr.pol.co.uk>, Steve B
(st***@beard.worldonline.co.uk) says...
I have a system that has been working fine for months, until this week.
This is the error message that I am now getting :

A DB2 problem occurred.
Sqlcode: -712 Sqlstate: 57011 , Sqlerrd.1: -140
Sqlerrd.2: -136
Sqlerrp: ARIXRST

I suspect it is something to do with space. If my selection criteria
results
on a lot of data (40,000+) being returned, the problem occurs. If I only
select a small amount of data (<40,000), it works perfectly.
The system runs on a VM server

I have been trying to resolve this for a week now so any help would be
most
appreciated.

TIA
Steve


I copied the message text from the DB2 Server for VM V7 bookshelf at
the IBM website, you can find it at the (wrapped) link:
http://publibfp.boulder.ibm.com/cgi-...lves/arivbs20?
FS=TRUE

--------------------------------------------------

-712 The SQL statement failed because internal dbspaces were not
available or were too small.

Explanation: The system may require internal dbspaces to process SQL
statements involving ORDER BY, GROUP BY, or joins. Either it was
unable to acquire enough internal dbspaces, or the internal dbspaces
were not large enough to process the command.
SQLSTATE 57011.
System Action: Processing of the SQL statement has ended.
User Response: If SQLERRD2 = -74, internal dbspaces are returned to
the system by a COMMIT or ROLLBACK statement. If you have issued
previous SELECT statements without doing a COMMIT statement, you
could alleviate the problem by issuing COMMIT statements interspersed
with your other SQL statements. Also, notify your system programmer
to increase the number of internal dbspaces in the system.
If SQLERRD2 = -77, -78 or -136 notify your system programmer to
increase the size of the internal dbspaces.
System Programmer Response: If SQLERRD2 = -74, allocate additional
internal dbspaces using the ADD DBSPACE operation (SQLADBSP EXEC) and
resubmit the original command.
If SQLERRD2 = -77, -78 and -136, perform an ADD DBSPACE operation
(SQLADBSP EXEC) for internal dbspaces with a larger size parameter
than previously specified and resubmit the original command.

Nov 19 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

reply views Thread by RichardF | last post: by
3 posts views Thread by niju | last post: by
1 post views Thread by Jeff Lynch | last post: by
9 posts views Thread by J055 | last post: by
1 post views Thread by Marylou17 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.