This page is my own personal work. Anyone can use it for their own edification, but must realize that this material is not supported by me and the site is not affiliated with IBM Rational Software or Atlassian.
Transfer mastership.
# mu chmaster -clan clanname -site sitename -family familyname -user admin-logon -password admin-password entity-selectorThe entity-selector is something like user:login or record-type:record-id. The only objects that can have their mastership transferred are records, users, groups, and Workspace items (such as a query). Each of the selectors can optionally be specified using a sitename, as in user:login.site-name.
-cl.an clan-name | All replicas that use the same schema repository belong to the same clan. Default: first clan replicated at this site. |
-site site-name | Default: current site. |
-fam.ily family-name | All replicas of the same database belong to the same family. No default. |
-u.ser admin-logon | The name of a user with appropriate database privileges for the object whose mastership is changing. |
-p.assword admin-password | CQ password for -user. |
-all [ -l.ong ] | Transfer (give up) mastership of all objects locally mastered. For verbose output, use -long. |
-working.master | Transfer the working schema repository to another site. Must use MASTR with -family. |
-force old-master-replica | Transfer mastership of an object to the specified replica. |
-forceall | New in CQ 2003.06.00. Forcefully take mastership of everything mastered by obsolete-replica. |
Transfer record mastership.
# mu chmaster -clan clan -site site-name -family family-name -user admin-login -password admin-password -force old-replica-name record-type:record-id
Transfer user/group mastership.
# mu chmaster -clan clanname -site sitename -family familyname -user admin-logon -password admin-password new-master-replica user:username
Mastership of users records.
Transfer all masterships (retire a replica).
Licenses.
Resolve naming conflicts.
Configure a client machine to use multiutil.
# path\installutil adddbset dbset db-vendor server-hostname \\unc-path\database admin-login admin-password connect-optionsThe connect-options are only necessary for ORACLE, otherwise use "".
List the contents of replica's oplog.
# mu dumpoplog -family family -user admin -password password -at replicaSome useful options:
-l.ong | View all columns of the oplog. |
-s.hort | Limit the output to just the database operation. |
-from oplog-entry-number | Use with "-to" to specify a range of oplog entries. |
-to oplog-entry-number | Use with "-from" to specify a range of oplog entries. |
-since date-time | Limit the listing to those entries new since date-time. |
-reverse | Reverse the order of the output. |
Remove old oplog entries.
# mu scruboplog -family family -user admin -password password -before { number | date-time }The dumpoplog command can be used to determine the "-before" number or date-time.
Set up an alternate storage class.
Avoid ticket number collisions.
Determine a site's clan name.
Determine the site name.
List epoch numbers.
# mu lsepoch -family family-name -user admin -password admin Oplog IDs for row "siteC" (@ siteC-server) siteB=221 siteA=709 siteC=653 Oplog IDs for row "siteA" (@ siteA-server) siteB=504 siteA=950 siteC=653 Oplog IDs for row "siteB" (@ siteB-server) siteB=504 siteA=709 siteC=653The output of lsepoch is lines of ascii text. The rows can be mentally arranged in a visual format that better illustrates the information.
updates originating at siteA | updates originating at siteB | updates originating at siteC | |
siteA's own status | 950 | 504 | 653 |
siteA's estimate of siteB | 709 | 504 | 653 |
siteA's estimate of siteC | 950 | 221 | 653 |
List any packets that might be in a shipping bay.
# mu lspacketOptions:
-s.hort | List only the pathname of the packet. |
-l.ong | Also list the oplog IDs (epoch #s) and creating replica's OID. |
packet-name | Limit the listing to the named packet. Must appear after any options. |
Retransmit a missing packet.
At the exporting end: # mu recoverpacket -c "Retransmitting data." -family family-name -user admin -password admin -since date-time replica-name
At the import end: # mu lsepoch -family family-name -user admin -password password At the export end: # mu chepoch -family family-name -user admin -password password import-replica export-replica=epoch-given-by-import-admin
Create a database replica.
# mu activate -dbset schema-repo-name -user admin-logon -password admin-password -clan clan-name -site site-name -host hostnameThe user must have Super User privileges. The hostname is the machine on which the local Rational Shipping Server resides.
# mu mkreplica -export -user admin-logon -password admin-password -family family-name -workdir path -fship remote-hostname:remote-sitenameThe user database's schema repository database is automatically replicated as well. The user must have Super User privileges. The family name is the name of the local user database (5 characters). A working directory (workdir) must be specified, such as C:\temp\cq_workdir. It will create and then remove cq_workdir when its done. It cannot already exist. The -fship option tells to export immediately. Specify the remote shipping server's name (hostname). The remote site's name is designated at this time.
-sh.ip | Create the outgoing packet, but don't send it just yet. See shipping_server. |
-scl.ass storage-class | Use an alternate storage class. |
-pex.pire date-time | Specify a time at which the store-and-forward facility stops trying to send the packet. Default is 14 days. Never expire is 0. See the syncreplica man page for date-time syntax. |
-not.ify email-address | The delivery-failure message is sent to this address. |
-out packet-name | Use packet-name and place it in a directory of your choosing. Used for shipping by tape or email. |
-max.size size(k, m, or g) | An upper limit to the packet size in kilo, mega or giga bytes. Subsequent packets are appended with sequential integers. |
Import a database replica.
# mu lspacket -s # mu mkreplica -import -site site-name -repository physical-schemadb -vendor vendor-db schemadb-params -database physical-userdb -vendor vendor-db userdb-params packet-nameThe site-name must be the same as the remote-sitename given during export. It is listed as "Recipients" in the lspacket output. The db-info is for the schema repository and user databases being imported:
DB2 | Database Alias |
Oracle | SQL*Net Alias |
SQL Server | Physical Database Name |
# installutil dropdbset CQMS.clan-name.site-nameBack to the INDEX.
Change the properties of a replica.
# mu chreplica -clan clan -site site -family family -user admin -password password -host new-hostname replica-nameBack to the INDEX.
Remove a replica.
At SiteA: # mu chmaster -family family -user admin -password password SiteB-replica -all Or, at SiteB: # mu chmaster -family family -user admin -password password SiteB-replica -all -force SiteA-replica
# mu syncreplica -export -family family -user admin -password password -fship SiteB-replica
# mu syncreplica -import -family family -user admin -password password -receive Test the new masterhsip.
# mu rmreplica -family family -user admin -password password SiteA-replica
# mu syncreplica -export -family family -user admin -password password -fship other-replicas
Synchronize replicas.
At the exporting site: # mu syncreplica -export -family family -user admin -password password -fship remote-replica At the importing site: # mu lspacket -short # mu syncreplica -import -family family -user admin -password password packet-pathnameOther options:
-max.size max-packet-size | On export, limit packet sizes to max-packet-size(k, m, or g) |
-max.size max-packet-size -limit num-packets | Same as above, except limit the total number of packets to num-packets. |
-scl.ass storage-class | Export or import, specify the storage class. Available only for -ship and -fship. |
-pex.pire date-time | On Export, designate how long store-and-forward should retry sending. Default is 14 days. Never expire is 0. See the syncreplica man page for date-time syntax. |
-not.ify email-address | The deliver-failure message is sent to email-address. |
-sh.ip | On export, let store-and-forward create the packet in the outgoing bay but not deliver it. |
-fsh.ip | On export, let store-and-forward create the packet and send it immediately. |
-tape raw-tape-device | On export, create the packet on the raw-tape-device. |
-out packet-file | Designate your own packet-file for ftp or other transmission later. |
Describe a replica.
# mu describe -family family -user admin -password password { -all | -local | replica-name }Back to the INDEX.
Restore a replica from backup.
# mu restorereplica -family family -user admin -password passwordThe restorereplica command will look for update packets from all members of the family. If you only want to use a subset of the family members (perhaps the last update was only sent to one site), use the -replace option. Unlike other mu operations, that option requires the remote site names as it arguments, not the remote replica names.
# mu restorereplica -family family -user admin -password password -completedBack to the INDEX.
List replicas.
# mu lsreplica -family family -user admin -password password replicaIf -clan nor -site are specified, the current clan and site are assumed. The schema repository's family name is MASTR.
-cl.an clan-name | Name of the replica's clan. |
-site site-name | Name of the replica's site. |
-l.ong | List creation information and synchronization server. |
-s.hort | List the replica names only. |
-fmt format-string | See the lsrpelica man page for formatting options. |
-working.master | Lists the working schema repository for the clan you specified. |
-sib.lings | For a user database, lists the family members of the current replica, but does not list the current replica itself. Same for schema repository. |
-infa.mily family | Lists replicas of the specified replica when -family is MASTR. |
Determine ID block size and threshold.
multiutil lsreplica -clan TRAINING -site s1 -u admin -p "Back to the INDEX." -fam SAMPL –long - or - multiutil idblockinfo -clan XYZ_CLAN -site XYZ_HQ -fam XYZ_DB -u admin " " -ser req
Programmatically determine the local replica's name.
$replica_name = $session->GetLocalReplica->GetDisplayName;Back to the INDEX.