Support Home Sales Website Technology Contact Us
RDP Support  


RDPWin KB Booking Engine - IRM.Net RDPWin4 & PCI Compliance Search

Stat 2 or Stat 54 Error Messages May Indicate Data File Corruption

Updated: 5/3/12
Article ID#: K000097

Issue

Data corruption can be caused for a variety of reasons.  Most data corruption is caused by environmental factors like power outages or hardware failure.  For this reason, if the cause of the corruption is not immediately addressed, additional data corruption may occur.  For example, if  the network card on the data server fails and causes data corruption, until the network card is replaced with a working network card, the data may be corrupted again.

Pervasive Stat 2 and Stat 54 errors are generated by the Pervasive database indicating the file cannot be read from or written to due to file corruption.  These files cannot be read by Pervasive until either the RDP or Pervasive rebuild program is run.  In most cases, RDP support recommends running the RDP rebuild utility on all critical files.  The user may be encountering one error message, but in some cases additional data files may be corrupted.


If either Stat 2 or Stat 54 errors OCCUR, cALL RDP support prior to running any utilities.

Solution - RDPWin Steps

If RDPWin is installed, follow these steps below to resolve a Stat 2 or Stat 54.

  1. Exit all users from the RDP system. This includes all interface computers.
  2. Reboot the server on which the Pervasive Engine and the RDP Data resides.  In some cases a stat 2 or stat 54 are generated because the Pervasive cached in the memory on the server may be corrupted but the data is not corrupted.  A reboot of the server may clear the RAM on the server and resolve the issue.  A reboot may also flush out hardware failure on the server.
  3. Log one user into RDP and see if the problem still exists.  If the problem exists, proceed to step 4 to run the RDP rebuild utility.
  4. In RDPWin, go to the System menu --> File Utilities --> Rebuilt Files and Indexes.
  5. Select the radio button for Critical Files
  6. Under the Rebuild Options, select Rebuild Files and Indexes.
  7. Click the Process button.
  8. Rebuild Files

  9. At the prompt, click the Continue button.
  10. The Rebuild Files and Indexes program reads the total number of records in the file and the number of records copied.  The file will automatically be replaced.  If the number of Total Records is significantly more than the Records Copied, then complete a full restore from a backup and recreate all activity since restore.
  11. Rebuild Complete

  12. If the Records Copied is less than the Total Records for the HExpense file, run Reset Res from Folio from the Night Audit/Day End menu on future and in-house reservations.  Reset Res recalculates the balance due on reservations based on existing transactions.  And, if a payment was one of the transactions deleted in the steps above, the reservation's balance due has changed.  For example, a reservation that was checked out yesterday with a zero balance after the guest paid $100 by credit card may now have a $100 balance due.) 

Solution - RDP DOS Steps

  1. Exit all users from the RDP system. This includes all interface computers.
  2. Reboot the server on which the Pervasive Engine and the RDP Data resides.  In some cases a stat 2 or stat 54 are generated because the Pervasive cached in the memory on the server may be corrupted but the data is not corrupted.  A reboot of the server may clear the RAM on the server and resolve the issue.  A reboot may also flush out hardware failure on the server.
  3. Log one user into RDP and see if the problem still exists.  If the problem exists, proceed to step 4 to run the RDP rebuild utility.
  4. If the customer is on a version of RDP Dos prior to 12.02 build 454, update the customer.  Changes have recently been made to the 994 utility to include additional files when running the utility on all critical files.  See "RDPDOS Update Page"
  5. Login to RDP from one workstation using a login that has access to menu 99 - System Utilities.
  6. From the System Utilities menu, select option 994 - Rebuild an RDP Data File.
  7. Select option C - Rebuild all Critical Files.
  8. Option 994 reads the total number of records in the file and records the number of errors.  The file will automatically be replaced. 
    Look to see how many Btrieve Errors have been Encountered.  Look to see how many Btrieve Records Copied Successfully there were.  If the number of Btrieve Errors are a significant number in comparison to the number of Btrieve Records Copied Successfully, then complete a full restore from tape backup and recreate all activity since restore.
  9. If there are Btrieve Errors in file 85 (Hexpense.dat), run 996 on future and in-house reservations.  996 will produce a printout that records reservations whose totals changed. (i.e. - 996 recalculates the balance due on reservations based on existing transactions.  And, if a payment was one of the transactions deleted in the steps above, the reservation's balance due has changed.  For example, a reservation that was checked out yesterday with a zero balance after the guest paid $100 by credit card may now have a $100 balance due.)  If the property does a lot of group business or has owners, 996 should also be completed for these options.
Support Home  RDPWin4 & PCI Compliance Enhancement Requests Open A Web Support Ticket
Training New Sales Website Old Sales Website Contact Us

 Facebook     Twitter      LinkedIn   TODF