To prepare for application data copying

Verify the source and destination Infor Landmark Technology GEN databases.

At the command line of the source and destination environment, type

dbverify -q gen

Review the output. The end of the log file should resemble the example below. Although each product has a different number of tables, the number of SQL tables checked and number of SQL tables with no errors should match.

Number of SQL tables checked                     :    215
Number of SQL tables with no errors              :    215
Number of SQL tables in an empty dbspace         :    0
Number of missing SQL tables                     :    0
Number of SQL tables with incorrect definitions  :    0
Number of SQL tables with incorrect permissions  :    0

Number of SQL indexes with no errors             :    776
Number of extra SQL indexes                      :    0
Number of missing SQL indexes                    :    0
Number of SQL indexes with incorrect definitions :    0

Verify the source and destination application databases.
1. Run the following command to verify the dataarea.
  
  dbverify -q <dataarea>
2. Review the output. The end of the log file should resemble the example below.
  Note:
  Although each product has a different number of tables, the number of SQL tables checked and number of SQL tables with no errors should match.
```
Number of SQL tables checked                     :    215
Number of SQL tables with no errors              :    215
Number of SQL tables in an empty dbspace         :    0
Number of missing SQL tables                     :    0
Number of SQL tables with incorrect definitions  :    0
Number of SQL tables with incorrect permissions  :    0

Number of SQL indexes with no errors             :    776
Number of extra SQL indexes                      :    0
Number of missing SQL indexes                    :    0
Number of SQL indexes with incorrect definitions :    0
```
  Note:
  If the output contains inconsistencies, refer to Knowledge Base article 5409479 before proceeding.
3. Run datamaint in verify mode. At the command line, type:
  
  datamaint --auditsnapshot -Vc productLine
  
  Note:
  The datamaint verify procedure can be done at any time and can be run while users are on the system.
4. Review the log found in $LALOGDIR/datamaint to identify any business classes that have the following errors:
  - Business objects whose current data doesn't match Audited View
  - Business objects with inconsistent audit snapshot data
  Note:
  The log file will add the message "*** Errors Detected ***" for any file that contains errors.
  
  Run a keyword search on "*** Errors Detected ***" to locate the files that will need further processing.
5. If your data has errors, run the following command for only the business classes in error. (No other users should be on the system while this command is run.)
  
  datamaint --auditsnapshot -Uc productline businessClassList
  
  where businessClassList is a comma-separated list of the business classes in error (use no spaces in the list). For example:
  
  HRMActionReasonMapping,Candidate,S3InterfaceSetup
  
  Note:
  Use the -n option to specify the number of threads to use while running datamaint.
6. Review the log found in $LALOGDIR/datamaint to ensure that the errors no longer exist.
  
  Note:
  If the log still contains errors, contact Support.