FlashCopy cloning function-clauses

Edit online

The following functions are supported by the fcmcli command option -f 'function' for FlashCopy® cloning operations: 


1 
2.1   -f create_clone?   -F
2.1   -f refresh_clone?   -F
2.1   -f preproc_clone
2.1   -f postproc_clone
2.1   -f inquire_clone
2.1   -f inquire_detail_clone
2.1   -f delete_clone?   -F
1   -C clone-database-name
1   -u clone-database-instance user name(1)
1   -d production-database-name
1   -X preprocessing-configuration-filename
1   -Y postprocessing-configuration-filename
Notes:
  • 1 This option is not required for -f inquire_clone or -f inquire_detail_clone commands.

1 
2.1   -f create_clone?   -F
2.1   -f refresh_clone?   -F
2.1   -f preproc_clone
2.1   -f postproc_clone
2.1   -f inquire_clone
2.1   -f inquire_detail_clone
2.1   -f delete_clone?   -F
1   -C clone-database-name
1   -u clone-database-instance user name(1)
1   -X preprocessing-configuration-filename
1   -Y postprocessing-configuration-filename
Notes:
  • 1 This option is not required for -f inquire_clone or -f inquire_detail_clone commands.

The return code of the fcmcli command is 0 if it finishes the request without an error or if there were no candidates for the request. The return code is 1 if one or more minor issues occur which are not critical but must be checked to prevent major issues later. Return code 2 indicates that an error occurred during the command execution.

Issue cloning-related commands on the production system as the production database instance owner. The cloning commands must be issued from the instance directory where the IBM® Storage Protect Snapshot product files are located. The fcmcli command identifies the name of the production database.

  • For DB2® databases, the DB2 database directory is used. If only one entry exists in the database directory, this entry is used to identify the production database name.
  • If the -d production database name option is specified, this value overwrites the value that is identified in the previous step. Also, this value is used to identify the production database name. Its use with DB2 depends on the number of database entries in the database directory. If more than one entry is in the DB2 database directory, the -d option is required.
For a DB2 database the cloned database is not moved to the clone target instance, when the target database name is identical to the production database name. If required to move the cloned database, rename the database by providing an alternative name. For example, two database instances are created on the clone server, the production instance that is named db2prodins and the clone instance named db2cloneins. To clone the production database PROD and move it to the clone target instance, issue the following command: 
fcmcli -f create_clone -C CLONE -u db2cloneins -d PROD