When corruption is present, PROUTIL DUMP and PROUTIL DUMPSPECIFIED return errors with corruption details, the table number, partition identifier and record identifier. Use the stopaftererror num parameter to limit the number of errors processed by either utility.

Use the following PROUTIL DUMP syntax to limit the number of errors processed.

Syntax

proutil db-name -C dump [owner-name.]table-name directory  [ stopaftererror num ] [-index num]

In the syntax, db-name specifies the database from which you want to dump, owner-name specifies the owner of the table containing the data you want to dump, table-name specifies the name of the table containing the data you want to dump, directory specifies the name of the target directory where the data is to be dumped, num specifies the number of errors to process, and -index num specifies an index that is used to dump the table contents.

To expand the PROUTIL DUMP syntax for a threaded online dump, use the syntax shown in Dump table contents with PROUTIL.

Examples

The following output shows a missing LOB field:

 proutil sports2000 -C dump Item -index ItemNum stopaftererror 55
Using index ItemNum (33) for dump of table Item. (17813)
SYSTEM ERROR: Binary Dump failed in dsmLobGet, lobType = 1, dsmRet = -1. (9200)
Skipped LOB dump for record: 1736, LOB object: 7, LOB Id: 19522, partition: 0. (20531)
Record 1736 was dumped with error because 1 LOB filed(s) couldn't be retrieved successfully. (20532)
Dumped 55 records. (13932)
Binary Dump complete. (6254)

The following output shows a broken record continuation:

 proutil sports2000 -C dump Customer -index CustNum stopaftererror 100
Using index CustNum (13) for dump of table Customer. (17813)
Missing Record Continuation - Area: 8, Table: 3, Partition: 0, Recid: 488 (20533)
………..
Missing Record Continuation - Area: 8, Table: 3, Partition: 0, Recid: 385 (20533)
Dumped 1107 records. (13932)
Binary Dump complete. (6254)

The following output shows a record upgrade error:

 proutil sports2000 -C dump Customer -index CustNum stopaftererror 50
Using index CustNum (13) for dump of table Customer. (17813)
 Hit end of record indicator before finding last field
Record Upgrade Error - Area: 10, Table: 4, Partition: 0, Recid: 9227 (20533)
Dumped 1107 records. (13932)
Binary Dump complete. (6254)

Use the following PROUTIL DUMPSPECIFIED syntax to limit the number of errors processed: 

proutil db-name -C dumpspecified [owner-name.]table-name.field-name
          operator1 low-value [ AND operator2 high-value] 
             directory 
         [ tenant tenant-name| group group-name| 
                     partition partition-name | composite initial]
         [stopaftererror value] 
         [-preferidx index-name]

Example

The following output shows errors returned from corrupted records when dumping selective contents with DUMPSPECIFIED:

 proutil sports2000 -C dumpspecified Customer.Recid GE 50000 and LE 60000 -index Name stopaftererror 4
Using index 16  which is Name  for the dump of table Customer . (10035)
Record Not Found - Area: 10, Table: 4, Partition: 0, Recid: 54577 (20533)
Record Not Found - Area: 10, Table: 4, Partition: 0, Recid: 54788 (20533)
Record Not Found - Area: 10, Table: 4, Partition: 0, Recid: 53286 (20533)
Record Not Found - Area: 10, Table: 4, Partition: 0, Recid: 54546 (20533)
Binary Dump stopped because it reached its stopaftererror limit 4. (20534)
Binary Dump failed. (6253)