In order to bring you the best possible user experience, this site uses Javascript. If you are seeing this message, it is likely that the Javascript option in your browser is disabled. For optimal viewing of this site, please ensure that Javascript is enabled for your browser.
Login  |   Cloud ERP  |   Home  |   qad.com



  •     QAD Glossary

  • Mass Rowid Synchronization Tool
    From time to time you may need to perform Progress database dump and load procedures for various maintenance-related reasons. Performing dump and load procedures changes the assigned rowids in the QAD Enterprise Applications database; this means that they will no longer be synchronized with the original rowids stored in the QXO database. This reassignment of rowids will result in erroneous messages being generated by QXO.
    Note: You only need to use this tool if you use rowids—synchronizing rowids is obviously not an issue with OIDs.
    To correct the rowid mismatch and resolve this issue, after performing a Progress database dump and load you must run the QXO mass rowid synchronization utility, which is located in the <qxo>src/tools directory.
    This utility iterates through the records in the Event Message section table of qxodb and queries the QAD Enterprise Applications database to determine if the rowids match. If there is a mismatch, the utility synchronizes the Event Message section record rowid to that of the QAD Enterprise Applications rowid.
    The utility comprises the following files:
    Startup script (start.msync)
    Database parameter (dbparm.pf)
    Mass rowid sync program (rowid-msync.p)
    Generated log file (rowidUpdate-msync.txt)
    You run the synchronization utility from the command line. Before running the utility you must:
    1
    Edit start.msync to set the correct values for DLC, PROPATH, and MFGDB.
    2
    Edit dbparm.pf to set the correct values for the databases being used.
    The utility creates an entry in the log file in the <qxo>/src/tools directory for the first record and for multiples of 100,000 records. You can check this log file periodically to see the progress of the utility.