Running the MboCacheCopy Utility

Run the MboCacheCopy utility, edit the generated SQL to customize,

There is no access control on this utility. You must know the consolidated database username and password (dba/SQL by default) to run the utility.

  1. Deploy the new package version.
  2. At the command line, run the data cache copy utility in –test true mode: java –classpath <onepage.jar;jconn3.jar> com.sybase.sup.admin.MboCacheCopy -u <username> -p <password> -S <jdbc:sybase:Tds:localhost:4747?servicename=uaml> -old <old package name and version> -new <new package name and version> -test true. Running the utility with -test set to true allows you to look at the generated SQL that will be run to transfer the data. MBOs that are not automatically copied also have the SQL generated, but that SQL is commented out, with additional notes in the comments about why the MBO was not copied.
  3. Analyze the SQL output and make any applicable customizations to the SQL. For example, include setting default values for MBOs that have added attributes, or add CONVERT functions for attributes that have changed type or length.
  4. Prepare to send data change notification (DCN) streams that will keep both versions of the package in sync with the backend database. This means you must send DCNs to both packages. They can be parallel by sending two DCN requests concurrently. For example, if you have two versions of a package, V1 and V2, then DCNs only apply changes in the packages to which they were sent.
  5. Run the migrate utility with –test false mode to generate the final SQL to be used. This reserves SKs in the CDB.
  6. Data change notifications (DCNs) to the old package can be resumed at this time. If DCNs to the new package are also started, queue them up until the copy process has completed.
  7. Edit the generated SQL to make any customizations that were identified in Step 3.
  8. At the command line, run dbisql.exe to execute the SQL script that was customized in Step 7. This copies all identified MBO data from the old to new package versions that was present in the old package as of the cutoverTime. The cutoverTime is established automatically at the instant the MBOCacheCopy utility is run with -test=false.
  9. When the execution of the SQL script completes, the DCN bulk-load begins for those MBOs that were not covered by migration
  10. Once the DCN bulk-load is complete, process the queued DCN requests for the new version of the package.
    The new package version is ready for use.
Parent topic: MBO data cache copy utility