RDBPROD: RMU Load encountering deadlock but still storing the data
edited Jan 10, 2014 9:14AM in Rdb on OpenVMS, IBM zSeries and Oracle on OpenVMS (MOSC) 2 commentsAnswered ✓
Hi,
we are loading a table using RMU LOAD in protected mode and receive following error message:
$ rmu/load/transaction=protected sql$database T_SECU_MARKET_PRICE PND_INP:R2O_T_SECU_MARKET_PRICE.20110706_0025
%RDB-E-DEADLOCK, request failed due to resource deadlock
-RDMS-F-DEADLOCK, deadlock on logical area 612 "T_SECU_MARKET_PRICE"
%RMU-I-DATRECREAD, 315 data records read from input file.
%RMU-I-DATRECSTO, 315 data records stored 6-JUL-2011 11:30:37.78.
%RMU-F-FTL_LOAD, Fatal error for LOAD operation at 6-JUL-2011 11:30:37.94
Now what strikes me is the fact that although the load reports a deadlock, it still stores all 315 records successfully. The load also is running protected, so no other writer should be interfering. Can someone explain this behavior ? I would expect the transaction to be rolled back on a deadlock, but the records are stored, which seems a bit odd.
we are loading a table using RMU LOAD in protected mode and receive following error message:
$ rmu/load/transaction=protected sql$database T_SECU_MARKET_PRICE PND_INP:R2O_T_SECU_MARKET_PRICE.20110706_0025
%RDB-E-DEADLOCK, request failed due to resource deadlock
-RDMS-F-DEADLOCK, deadlock on logical area 612 "T_SECU_MARKET_PRICE"
%RMU-I-DATRECREAD, 315 data records read from input file.
%RMU-I-DATRECSTO, 315 data records stored 6-JUL-2011 11:30:37.78.
%RMU-F-FTL_LOAD, Fatal error for LOAD operation at 6-JUL-2011 11:30:37.94
Now what strikes me is the fact that although the load reports a deadlock, it still stores all 315 records successfully. The load also is running protected, so no other writer should be interfering. Can someone explain this behavior ? I would expect the transaction to be rolled back on a deadlock, but the records are stored, which seems a bit odd.
1