By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
437,586 Members | 2,347 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 437,586 IT Pros & Developers. It's quick & easy.

problem exporting data from mainframe using db2 connect connectingfrom db2 on linux

P: n/a
Hi,

I am getting error when exporting data from mainframe using db2
connect while i am on db2 on linux.

Here is what error looks like
================================================== ============
$ db2 "export to abc.ixf of ixf lobs to /tmp modified by lobsinfile
select * from temp"
SQL3104N The Export utility is beginning to export data to file
"abc.ixf".

SQL3015N An SQL error "-904" occurred during processing.

SQL0904N Unsuccessful execution caused by an unavailable resource.
Reason
code: "00C90096", type of resource: "00000F01", and resource name:
"0173.0153.AFAAEF7D8CC3D82B26040154CB48.00001" . SQLSTATE=57011

SQL3105N The Export utility has finished exporting "10000" rows.
================================================== ============

I also tried running using UR with select and that does not work
either
Also, tablespace has been defined as locksize any in OS/390.
DB2 should be able to escalate it to tablespace locking.
Here is the explanation i found
================================================== ==============
00C90096
Explanation: The page, row or LOB lock on the page or subpage
identified
by NAME in message DSNT500I or DSNT501I caused the total number of
page,
row or LOB locks concurrently held to reach the installation
maximum
number of page, row or LOB locks (NUMLKUS) allowed for a single agent
in
the
system.

This reason code is issued by the following CSECT:
DSNILMCL

System Action: The operation that encountered this condition is
not
executed. If a utility job encountered this condition, the utility
is
stopped. Otherwise, any database updates for the statement that
was
executing are backed out. Any database reads for the statement that
was
executing are not executed. The position of the cursor is
unpredictable.

User Response: Rerun the application after correcting the cause of
this
resource unavailable
condition.
================================================== ===========
Any one had this problem , Please share your experience with me

regards,
db2admin
Dec 13 '07 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.