DB2 SQL error: SQLCODE: -930, SQLSTATE: 57011, SQLERRMC: null

Paul Chang

DB2 SQL error: SQLCODE: -930, SQLSTATE: 57011, SQLERRMC: null
 
Hi,
I am new to the db2 v9.(it is not z/OS)
When I connect db2 v9, I got
Cause: DB2 SQL error: SQLCODE: -930, SQLSTATE: 57011, SQLERRMC: null
error.  I cannot find error code with -930 in the db2 doc.
If anybody knows, please explain the error messages.
thanks in advance.
Paul.




_____________________________________________________________________

* IDUG North America * Tampa, Florida, * May 10-14 2010 * http://IDUG.ORG/NA *
_____________________________________________________________________

http://www.idug.org/db2-videos.html has hundreds of video presentations!
Did you miss out on attending an IDUG conference?
Many of the presentations were recorded and are available on our website!
_____________________________________________________________________

If you need to change settings, http://www.idug.org/cgi-bin/wa?A0=DB2-L is the home of IDUG's DB2-L

Philip Gunning

Re: DB2 SQL error: SQLCODE: -930, SQLSTATE: 57011, SQLERRMC: null
(in response to Paul Chang)
See below, it is in the doc. Below from DB2 command line:



è/gts1/ db2 ? sql0930n





SQL0930N There is not enough storage available to process the

statement.



Explanation:



A request was made to the database that required another memory page but

no more pages are available to the database manager.



The statement cannot be processed.



User response:



Possible solutions include:



* Verify that your system has sufficient real and virtual memory.

* Remove background processes.

* If the error occurs during DUOW resynchronization, reduce the

RESYNC_INTERVAL database manager configuration parameter value.

* If the error occurs on a statement which referenced a routine (UDF,

stored procedure or method), it may be that the storage required to

contain the arguments and return values was more than the memory

available in the system. This might occur if the routine is defined

with BLOB, CLOB, DBCLOB parameters or return values, having a large

size (2GB for example).



If the possible solutions listed above do not solve the problem, it may

be necessary to consider changing the definition of the routine.



sqlcode: -930



sqlstate: 57011, 5UA0L





From: IDUG DB2-L [mailto:[login to unmask email] On Behalf Of Paul Chang
Sent: Tuesday, January 05, 2010 9:43 PM
To: [login to unmask email]
Subject: [DB2-L] DB2 SQL error: SQLCODE: -930, SQLSTATE: 57011, SQLERRMC:
null






Hi,

I am new to the db2 v9.(it is not z/OS)

When I connect db2 v9, I got

Cause: DB2 SQL error: SQLCODE: -930, SQLSTATE: 57011, SQLERRMC: null

error. I cannot find error code with -930 in the db2 doc.

If anybody knows, please explain the error messages.

thanks in advance.

Paul.



_____

< http://www.idug.org > IDUG - The Worldwide DB2 User Community!

The IDUG DB2-L Listserv is only part of your membership in IDUG. If you are
not already an IDUG member, please < http://www.idug.org/register > register
here.


_____________________________________________________________________

* IDUG North America * Tampa, Florida, * May 10-14 2010 * http://IDUG.ORG/NA *
_____________________________________________________________________

http://www.idug.org/db2-videos.html has hundreds of video presentations!
Did you miss out on attending an IDUG conference?
Many of the presentations were recorded and are available on our website!
_____________________________________________________________________

If you need to change settings, http://www.idug.org/cgi-bin/wa?A0=DB2-L is the home of IDUG's DB2-L

Robert Catterall

Re: DB2 SQL error: SQLCODE: -930, SQLSTATE: 57011, SQLERRMC: null
(in response to Philip Gunning)
As Phil pointed out, in a DB2 command line processor session you can get
information about an error message by entering a question mark followed by
the error message of interest (and the same can be done with a SQLSTATE
value). You can also find this information via the DB2 for LUW Information
Center on IBM's Web site. Here's the link for the DB2 9.7 Information
Center:

http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp

On that page, you can either enter the message in the search box and click
on GO to get the related information, or you can, under "Contents" on the
left side of the page, expand "Database fundamentals" and then expand
"Messages" and then expand "SQL Messages."

You can also download the Information Center at this page:

http://www-01.ibm.com/support/docview.wss?rs=71&uid=swg27009474&S_TACT=imdb2luw&S_CMP=ibm_im

Robert


On Tue, Jan 5, 2010 at 10:32 PM, Phil Gunning <[login to unmask email]> wrote:

> See below, it is in the doc. Below from DB2 command line:
>
>
>
> è/gts1/ db2 ? sql0930n
>
>
>
>
>
> SQL0930N There is not enough storage available to process the
>
> statement.
>
>
>
> Explanation:
>
>
>
> A request was made to the database that required another memory page but
>
> no more pages are available to the database manager.
>
>
>
> The statement cannot be processed.
>
>
>
> User response:
>
>
>
> Possible solutions include:
>
>
>
> * Verify that your system has sufficient real and virtual memory.
>
> * Remove background processes.
>
> * If the error occurs during DUOW resynchronization, reduce the
>
> RESYNC_INTERVAL database manager configuration parameter value.
>
> * If the error occurs on a statement which referenced a routine (UDF,
>
> stored procedure or method), it may be that the storage required to
>
> contain the arguments and return values was more than the memory
>
> available in the system. This might occur if the routine is defined
>
> with BLOB, CLOB, DBCLOB parameters or return values, having a large
>
> size (2GB for example).
>
>
>
> If the possible solutions listed above do not solve the problem, it may
>
> be necessary to consider changing the definition of the routine.
>
>
>
> sqlcode: -930
>
>
>
> sqlstate: 57011, 5UA0L
>
>
>
>
>
> *From:* IDUG DB2-L [mailto:[login to unmask email] *On Behalf Of *Paul Chang
> *Sent:* Tuesday, January 05, 2010 9:43 PM
> *To:* [login to unmask email]
> *Subject:* [DB2-L] DB2 SQL error: SQLCODE: -930, SQLSTATE: 57011,
> SQLERRMC: null
>
>
>
>
>
> Hi,
>
> I am new to the db2 v9.(it is not z/OS)
>
> When I connect db2 v9, I got
>
> Cause: DB2 SQL error: SQLCODE: -930, SQLSTATE: 57011, SQLERRMC: null
>
> error. I cannot find error code with -930 in the db2 doc.
>
> If anybody knows, please explain the error messages.
>
> thanks in advance.
>
> Paul.
>
>
> ------------------------------
>
> [image: IDUG - The Worldwide DB2 User Community!] < http://www.idug.org >
>
> The IDUG DB2-L Listserv is only part of your membership in IDUG. If you are
> not already an IDUG member, please register here. < http://www.idug.org/register >
>
> ------------------------------
>
> [image: IDUG - The Worldwide DB2 User Community!] < http://www.idug.org >
>
> The IDUG DB2-L Listserv is only part of your membership in IDUG. If you are
> not already an IDUG member, please register here. < http://www.idug.org/register >
>



--
Robert Catterall
Catterall Consulting
www.catterallconsulting.com

_____________________________________________________________________

* IDUG North America * Tampa, Florida, * May 10-14 2010 * http://IDUG.ORG/NA *
_____________________________________________________________________

http://www.IDUG.org membership is now free.
Do you have people in your office who are not an IDUG member?
Show them how to access the information and help train the next generation of DB2 Users!
_____________________________________________________________________

If you need to change settings, http://www.idug.org/cgi-bin/wa?A0=DB2-L is the home of IDUG's DB2-L