[DB2 z/OS V10 CM] 00C900D1 while reading XML column

Rodney Krick

[DB2 z/OS V10 CM] 00C900D1 while reading XML column

Hi,

we have a table in our application with a XML Column where we "archive" a file we receive from one customer. Yesterday we've got a "large" file (ca. 2 MB) . We can save that data (INSERT) in the table, but we cannot read it (SELECT) back. When we try to read, we get the following error message:
UNSUCCESSFUL EXECUTION CAUSED BY AN UNAVAILABLE RESOURCE. REASON 00C900D1, TYPE OF RESOURCE 00000907, AND RESOURCE NAME. SQLCODE=-904, SQLSTATE=57011, DRIVER=3.64.106

Our DBA told us, we have the following settings defined in DB2:

LOBVALA 2048  (kb) and XMLVALA max values.

Resource 907 ist LOB Storage. We expected to see 90A (XML Storage), but maybe we are just expecting the wrong thing :-)

The table doesn't have any other "unstructured" column (only one XML).

Does anyone had some similar experiences with this and can give us a hint?

Thank you in advance!

Rodney Krick

Rodney Krick

[DB2 z/OS V10 CM] 00C900D1 while reading XML column
(in response to Lizette Koehler)
Lizette,

thank you very much. I've searched the DB2-L archives and also asked uncle
Google using "LOBVALA -904 00C900D1" and "XMLVALA -904 00C900D1". The
thread you posted wasn't in my matches! The explanation makes sense for
our situation: the value for XMLVALA doesn't restrict the amount of data,
but the value of LOBVALA does! And if the DB2 engine reuses it, it cannot
work. Thank you again!


Mit freundlichen Grüßen / Best regards,

Rodney Krick
Senior Consultant
Zertifizierter Projektmanagement-Fachmann (GPM)
____________________________
aformatik Training & Consulting GmbH & Co. KG
Tilsiter Str. 6, D-71065 Sindelfingen, Germany
Tel.: +49 (0)7031-23 807-0
Fax: +49 (0)7031-23 807-19

mailto:[login to unmask email]
___________________________________________
IBM Training Partner und autorisierter Reseller für IBM Schulungen
____________________________________________
Kommanditgesellschaft mit Sitz in Sindelfingen
Amtsgericht Stuttgart HRA 242677
USt-Id. Nr.: DE 814174749
pers. haftende Gesellschafterin: aformatik Verwaltungs-GmbH
Geschäftsführer: Dipl. Inform. Andreas Anglett
Sitz in Sindelfingen, Amtsgericht Stuttgart HRB 245894



Von:
Lizette Koehler <[login to unmask email]>
An:
[login to unmask email]
Datum:
03.02.2014 12:13
Betreff:
[DB2-L] - RE: [DB2 z/OS V10 CM] 00C900D1 while reading XML column



Also, a few searches on 00C900D1 indicate
From a thread http://tinyurl.com/llsnwey
Why? LOB manager is re-used in DB2 for bringing XML data
into DB2 from an application and vice versa. LOBVALA and LOBVALS put
limits on the XML string size. You need to set LOBVALA to at least the
maximum document length you will input and output.
If you consider this to be an DB2 issue, then you will probably need to
open an SR and collect the doc as indicated.
Otherwise your DB2 system admin that manages the resources needs to
increase the LOBVALA to more than 2MB if that is what you are hitting.
Lizette


From: Lizette Koehler [mailto:[login to unmask email]
Sent: Monday, February 03, 2014 4:45 AM
To: [login to unmask email]
Subject: [DB2-L] - RE: [DB2 z/OS V10 CM] 00C900D1 while reading XML column

Rodney,

The 00C900D1 Explanation
The amount of space allowed for processing LOB values by a user has been
exceeded. The amount of space allowed per user is indicated by panel
DSNTIPD.
System action
Collect the following diagnostic items:
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.
Listing of SYS1.LOGREC data set, obtained by executing IFCEREP1.

Have you verified the DSNTIPD panel? It may be a restriction at your
shop of 2MB.

Lizette



From: Rodney Krick [mailto:[login to unmask email]
Sent: Monday, February 03, 2014 3:57 AM
To: [login to unmask email]
Subject: [DB2-L] - [DB2 z/OS V10 CM] 00C900D1 while reading XML column

Hi,
we have a table in our application with a XML Column where we "archive" a
file we receive from one customer. Yesterday we've got a "large" file (ca.
2 MB) . We can save that data (INSERT) in the table, but we cannot read it
(SELECT) back. When we try to read, we get the following error message:
UNSUCCESSFUL EXECUTION CAUSED BY AN UNAVAILABLE RESOURCE. REASON 00C900D1,
TYPE OF RESOURCE 00000907, AND RESOURCE NAME. SQLCODE=-904,
SQLSTATE=57011, DRIVER=3.64.106
Our DBA told us, we have the following settings defined in DB2:
LOBVALA 2048 (kb) and XMLVALA max values.
Resource 907 ist LOB Storage. We expected to see 90A (XML Storage), but
maybe we are just expecting the wrong thing :-)
The table doesn't have any other "unstructured" column (only one XML).
Does anyone had some similar experiences with this and can give us a hint?
Thank you in advance!
Rodney Krick



Site Links: View post online View mailing list online Start new thread
via email Unsubscribe from this mailing list Manage your subscription
** ** ** Attend the 2014 North America IDUG DB2 Tech Conference ** ** **
--> --> Phoenix, Arizona 12 - 16 May 2014 <-- <--
http://www.idug.org/p/cm/ld/fid=314

Use of this email content is governed by the terms of service at:
http://www.idug.org/p/cm/ld/fid=2


Lizette Koehler

[DB2 z/OS V10 CM] 00C900D1 while reading XML column
(in response to Rodney Krick)
Rodney,




The 00C900D1 Explanation


The amount of space allowed for processing LOB values by a user has been
exceeded. The amount of space allowed per user is indicated by panel
DSNTIPD.


System action


Collect the following diagnostic items:


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.


Listing of SYS1.LOGREC data set, obtained by executing IFCEREP1.





Have you verified the DSNTIPD panel? It may be a restriction at your shop
of 2MB.





Lizette









From: Rodney Krick [mailto:[login to unmask email]
Sent: Monday, February 03, 2014 3:57 AM
To: [login to unmask email]
Subject: [DB2-L] - [DB2 z/OS V10 CM] 00C900D1 while reading XML column



Hi,

we have a table in our application with a XML Column where we "archive" a
file we receive from one customer. Yesterday we've got a "large" file (ca. 2
MB) . We can save that data (INSERT) in the table, but we cannot read it
(SELECT) back. When we try to read, we get the following error message:
UNSUCCESSFUL EXECUTION CAUSED BY AN UNAVAILABLE RESOURCE. REASON 00C900D1,
TYPE OF RESOURCE 00000907, AND RESOURCE NAME. SQLCODE=-904, SQLSTATE=57011,
DRIVER=3.64.106

Our DBA told us, we have the following settings defined in DB2:

LOBVALA 2048 (kb) and XMLVALA max values.

Resource 907 ist LOB Storage. We expected to see 90A (XML Storage), but
maybe we are just expecting the wrong thing :-)

The table doesn't have any other "unstructured" column (only one XML).

Does anyone had some similar experiences with this and can give us a hint?

Thank you in advance!

Rodney Krick



-----End Original Message-----

Lizette Koehler

[DB2 z/OS V10 CM] 00C900D1 while reading XML column
(in response to Lizette Koehler)

Also, a few searches on 00C900D1 indicate


From a thread <http://tinyurl.com/llsnwey>
http://tinyurl.com/llsnwey


Why? LOB manager is re-used in DB2 for bringing XML data
into DB2 from an application and vice versa. LOBVALA and LOBVALS put limits
on the XML string size. You need to set LOBVALA to at least the maximum
document length you will input and output.


If you consider this to be an DB2 issue, then you will probably need to open
an SR and collect the doc as indicated.


Otherwise your DB2 system admin that manages the resources needs to increase
the LOBVALA to more than 2MB if that is what you are hitting.


Lizette






From: Lizette Koehler [mailto:[login to unmask email]
Sent: Monday, February 03, 2014 4:45 AM
To: [login to unmask email]
Subject: [DB2-L] - RE: [DB2 z/OS V10 CM] 00C900D1 while reading XML column



Rodney,




The 00C900D1 Explanation


The amount of space allowed for processing LOB values by a user has been
exceeded. The amount of space allowed per user is indicated by panel
DSNTIPD.


System action


Collect the following diagnostic items:


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.


Listing of SYS1.LOGREC data set, obtained by executing IFCEREP1.





Have you verified the DSNTIPD panel? It may be a restriction at your shop
of 2MB.





Lizette









From: Rodney Krick [mailto:[login to unmask email]
Sent: Monday, February 03, 2014 3:57 AM
To: [login to unmask email]
Subject: [DB2-L] - [DB2 z/OS V10 CM] 00C900D1 while reading XML column



Hi,

we have a table in our application with a XML Column where we "archive" a
file we receive from one customer. Yesterday we've got a "large" file (ca. 2
MB) . We can save that data (INSERT) in the table, but we cannot read it
(SELECT) back. When we try to read, we get the following error message:
UNSUCCESSFUL EXECUTION CAUSED BY AN UNAVAILABLE RESOURCE. REASON 00C900D1,
TYPE OF RESOURCE 00000907, AND RESOURCE NAME. SQLCODE=-904, SQLSTATE=57011,
DRIVER=3.64.106

Our DBA told us, we have the following settings defined in DB2:

LOBVALA 2048 (kb) and XMLVALA max values.

Resource 907 ist LOB Storage. We expected to see 90A (XML Storage), but
maybe we are just expecting the wrong thing :-)

The table doesn't have any other "unstructured" column (only one XML).

Does anyone had some similar experiences with this and can give us a hint?

Thank you in advance!

Rodney Krick

_____

Lizette Koehler

[DB2 z/OS V10 CM] 00C900D1 while reading XML column
(in response to Rodney Krick)
I just used the following for the search

db2 10 00C900D1



I find a limited number of search strings to start is helpful. Then do more
to refine the search.



And sorry about the large font. I use ARIAL 10pt. But when I saw your
response it looked huge. So this is in Courier 10pt







Lizette





From: Rodney Krick [mailto:[login to unmask email]
Sent: Monday, February 03, 2014 4:35 AM
To: [login to unmask email]
Subject: [DB2-L] - [DB2 z/OS V10 CM] 00C900D1 while reading XML column



Lizette,

thank you very much. I've searched the DB2-L archives and also asked uncle
Google using "LOBVALA -904 00C900D1" and "XMLVALA -904 00C900D1". The thread
you posted wasn't in my matches! The explanation makes sense for our
situation: the value for XMLVALA doesn't restrict the amount of data, but
the value of LOBVALA does! And if the DB2 engine reuses it, it cannot work.
Thank you again!


Mit freundlichen Grüßen / Best regards,

Rodney Krick
Senior Consultant
Zertifizierter Projektmanagement-Fachmann (GPM)
____________________________
aformatik Training & Consulting GmbH & Co. KG
Tilsiter Str. 6, D-71065 Sindelfingen, Germany
Tel.: +49 (0)7031-23 807-0
Fax: +49 (0)7031-23 807-19

<mailto:[login to unmask email]> mailto:[login to unmask email]
___________________________________________
IBM Training Partner und autorisierter Reseller für IBM Schulungen
____________________________________________
Kommanditgesellschaft mit Sitz in Sindelfingen
Amtsgericht Stuttgart HRA 242677
USt-Id. Nr.: DE 814174749
pers. haftende Gesellschafterin: aformatik Verwaltungs-GmbH
Geschäftsführer: Dipl. Inform. Andreas Anglett
Sitz in Sindelfingen, Amtsgericht Stuttgart HRB 245894




Von:

Lizette Koehler <[login to unmask email]>


An:

[login to unmask email]


Datum:

03.02.2014 12:13


Betreff:

[DB2-L] - RE: [DB2 z/OS V10 CM] 00C900D1 while reading XML column



_____




Also, a few searches on 00C900D1 indicate
From a thread <http://tinyurl.com/llsnwey>
http://tinyurl.com/llsnwey
Why? LOB manager is re-used in DB2 for bringing XML data
into DB2 from an application and vice versa. LOBVALA and LOBVALS put limits
on the XML string size. You need to set LOBVALA to at least the maximum
document length you will input and output.
If you consider this to be an DB2 issue, then you will probably need to open
an SR and collect the doc as indicated.
Otherwise your DB2 system admin that manages the resources needs to increase
the LOBVALA to more than 2MB if that is what you are hitting.
Lizette


From: Lizette Koehler [ <mailto:[login to unmask email]>
mailto:[login to unmask email]
Sent: Monday, February 03, 2014 4:45 AM
To: [login to unmask email]
Subject: [DB2-L] - RE: [DB2 z/OS V10 CM] 00C900D1 while reading XML column

Rodney,


The 00C900D1 Explanation
The amount of space allowed for processing LOB values by a user has been
exceeded. The amount of space allowed per user is indicated by panel
DSNTIPD.
System action
Collect the following diagnostic items:
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.
Listing of SYS1.LOGREC data set, obtained by executing IFCEREP1.

Have you verified the DSNTIPD panel? It may be a restriction at your shop
of 2MB.

Lizette



From: Rodney Krick [ <mailto:[login to unmask email]> mailto:[login to unmask email]
Sent: Monday, February 03, 2014 3:57 AM
To: <mailto:[login to unmask email]> [login to unmask email]
Subject: [DB2-L] - [DB2 z/OS V10 CM] 00C900D1 while reading XML column


Hi,

we have a table in our application with a XML Column where we "archive" a
file we receive from one customer. Yesterday we've got a "large" file (ca. 2
MB) . We can save that data (INSERT) in the table, but we cannot read it
(SELECT) back. When we try to read, we get the following error message:
UNSUCCESSFUL EXECUTION CAUSED BY AN UNAVAILABLE RESOURCE. REASON 00C900D1,
TYPE OF RESOURCE 00000907, AND RESOURCE NAME. SQLCODE=-904, SQLSTATE=57011,
DRIVER=3.64.106

Our DBA told us, we have the following settings defined in DB2:

LOBVALA 2048 (kb) and XMLVALA max values.

Resource 907 ist LOB Storage. We expected to see 90A (XML Storage), but
maybe we are just expecting the wrong thing :-)

The table doesn't have any other "unstructured" column (only one XML).

Does anyone had some similar experiences with this and can give us a hint?

Thank you in advance!

Rodney Krick



_____



-----End Original Message-----





-----End Original Message-----