MboCacheCopy

The MBOCacheCopy creates a timestamp for the moment after which all backend changes need to be captured and sent to the new package through Data Cache Notifications in order not to lose any changes.

Syntax

mbocachecopy.bat
[-u username] 
[-p password] 
[-S uaml database URL] 
-old <old package name and version>
-new <new package name and version>
[-out <output file> (mbocachecopy.sql)]
[-verbose true|false] (false)
[-test true|false] (false)

Parameters

• -u username – Required. The user name. The default is dba.
• -p password – Required. The password for the user. The default is SQL.
• -S uaml database URL – Required. The database URL. The default is jdbc:sybase:Tds:localhost:4747?servicename=uaml.
• -old – Required. The name of the old mobile deployment package.
• -new – The name of the new mobile deployment package.
• -out – Optional. Create an output file. The default file name is mbocachecopy.sql.
• -verbose – Optional.
  
  

  • true – logging is verbose.

  • false – logging is not verbose.

• -test – Optional.
  
  • true – allows you to get a preview of the generated SQL generated. The utility does not make any changes to the consolidated database (CDB) when –test is true.
  • false – the CDB is altered to reserve a range of SK values that will be generated during the copy operation.

Examples

• Example 1 –

  mbocachecopy -old mypackage_1.0.0 -new mypackage_2.0.0 -out migrate_mypackage.sql

• Example 2 –

  dbisql -datasource mycluster_uaml -f migrate_mypackage.sql

Permissions

You must be a Sybase Unwired Platform Administrator to use the MboCacheCopy utility.