Author Topic: ARS2089E error while extracting with arsdoc get  (Read 1456 times)

rmazurki

  • Jr. Member
  • **
  • Posts: 20
    • View Profile
ARS2089E error while extracting with arsdoc get
« on: July 14, 2021, 05:26:31 AM »
hi,

Currently I am doing some 2010 year extractions from our CMOD on z/OS - version 9.0.0.6 (DB2 + data in OAM files).
Document type - AFP.
I have issue while arsdoc get - error is "ARS2089E Information has been modified on the server.  Please logoff, logon, and retry the operation."

Some log details:
2021-07-14 13:57:10.868179: ARS6063I Searching for documents in 'NLPDK-PENSOVER' ...
2021-07-14 13:57:10.868200: ARS6117I Querying database with SQL string '5;DATO,DATO,DOC_NAME,DOC_NAME,DOC_NAME;'2010-08-09','2010-08-09','','','';WHERE (DATO BETWEEN ? AND ?) AND DOC_NAME NOT IN (?,?,?) '
2021-07-14 13:57:17.757775: ARS6084I Search successful
2021-07-14 13:57:17.757879: ARS6107I 331 document(s) have been queried. Retrieving 331 document(s).
2021-07-14 13:57:17.950935: ARS2089E Information has been modified on the server.  Please logoff, logon, and retry the operation.
2021-07-14 13:57:17.954641: ARS6026I arsdoc completed.

I was able to find problematic objects by reducing search period and then adding more conditions to SQL query to have less hit ratio.
But it is time consuming way to find problematic objects.

Q: Is there a faster way to find documents which has this issue?

While trying to open this document in CMOD Client we also have message: "Information has been modified on the server.  Please logoff, logon, and retry the operation."
Offcourse logoff and logon does not help :).

I checked logs while loading these documents and this issue is connected with following db2 error:
03-06-2010 17:28:52   US00600        661504   Error   No       13   DB Error: äDB2 FOR OS/390åäODBC DRIVERåäDSN08015å   DSNT408I SQLCODE = -911, ERROR:  THE CURRENT UNIT OF WORK HAS BEEN ROLLED BACK            DUE TO DEADLOCK OR TIMEOUT.  REASON 00C9008E, TYPE OF RESOURCE                   00000302, AND RESOURCE NAME ARS   
This error is occuring at the same moment while loading problematic documents.

Q: Can we somehow "rescue" this documents?

Regards
Rafal

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1199
    • View Profile
Re: ARS2089E error while extracting with arsdoc get
« Reply #1 on: July 14, 2021, 03:45:26 PM »
When I google on TYPE OF RESOURCE 00000302 it says table space page is the problem.

Looked at a few old records that had the same error code (-911) and the answer has always been that the DBAs need to drill down to figure out what the problem is, that the application coder usually doesn't have the visibility within the system to determine what the problem could be.

Ed
#zOS #ODF

rmazurki

  • Jr. Member
  • **
  • Posts: 20
    • View Profile
Re: ARS2089E error while extracting with arsdoc get
« Reply #2 on: July 15, 2021, 12:48:24 AM »
this was in 2010 - so, I am not interested in understanding nature of this problem.
I just need rescue this documents if it is possible :).

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1199
    • View Profile
Re: ARS2089E error while extracting with arsdoc get
« Reply #3 on: July 15, 2021, 06:10:37 AM »
Does it help if fewer documents are retrieved per query?

Ed
#zOS #ODF

rmazurki

  • Jr. Member
  • **
  • Posts: 20
    • View Profile
Re: ARS2089E error while extracting with arsdoc get
« Reply #4 on: July 15, 2021, 06:23:21 AM »
When i discover which objects (DOC_NAME in segment tables) has this issue then I can ommit them and extraction will work fine.

I have two problems
1. I would like to find a new easier way to find documents/objects which are not available without running arsdoc get plenty times.
2. I would like to know if problematic documents can be rescued or not.

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1199
    • View Profile
Re: ARS2089E error while extracting with arsdoc get
« Reply #5 on: July 19, 2021, 01:34:23 PM »
>  I would like to find a new easier way to find documents/objects which are not available without running arsdoc get plenty times.

I'm guessing - and this is just a guess - that some storage set has been inadvertently deleted.

If you can figure out the node id and do a mapping to the arsnode table then that may signal to you in advance what to avoid retrieving.


> I would like to know if problematic documents can be rescued or not.

Can't help on that one, and am not hopeful. 

Maybe if you come up to a supported release and open a PMR somebody may have a trick up their sleeve, but my confidence level is low.

Ed

#zOS #ODF

rmazurki

  • Jr. Member
  • **
  • Posts: 20
    • View Profile
Re: ARS2089E error while extracting with arsdoc get
« Reply #6 on: July 20, 2021, 01:24:41 AM »
I'm guessing - and this is just a guess - that some storage set has been inadvertently deleted.

If you can figure out the node id and do a mapping to the arsnode table then that may signal to you in advance what to avoid retrieving.

I checked that it is not a problem with whole storage node - 99,9% objects in this storage node are fine - only few objects has this problem.