Lists the contents of a replica’s operation log
dumpoplog [ –cl·an clan-name ] [ –site site-name ] –fam·ily family-name
–u·ser username [ –p·assword ] password
[ –l·ong | –s·hort ] [ –at replica ]
[ oplog-ID... | [ –from oplog-ID ] [ –to oplog-ID ] ]
[ –since date-time ] [ –reverse ]
Use dumpoplog to list information in a replica’s operation log (oplog). The oplog tracks all database transactions, including record changes and schema modifications. Each oplog entry has an oplog ID.
You must have Super User privileges.
Default
Clan: First clan replicated at this site. If there is more than one clan at the site, –clan is required.
Site: Current site. If there is more than one site on this host, –site is required.
Family: No default; you must specify a family.
–cl·an clan-name
Name of the replica’s clan.
–site site-name
Name of the replica’s site.
–fam·ily family-name
User database family: Database name given to the user database when it was created.
Schema repository family: The family name is MASTR.
Default
You must specify a user name and password.
–u·ser user
Name of a user with Super User privileges.
–p·assword password
Password associated with the specified user.
Default
If no format is specified, the –short format is used. All oplog entries are listed.
–l·ong | –s·hort
With –long, displays all columns of the oplog, including information about the schema revision that applies to the packet data. With –short, displays each database operation that took place.
–at replica
Lists the oplog entries that originated from the sites you specify.
oplog-ID...
Lists the oplog entries you specify.
–from oplog-ID
Lists a range of oplog entries starting with oplog-ID and ending with the latest one or the one specified with –to. Specify oplog IDs as integers.
–to oplog-ID
Lists a range of oplog entries ending with oplog-ID and starting with 1 or the one specified with –from. Specify oplog IDs as integers.
–since date-time
Lists all oplog entries after date-time. The date-time argument can have any of the following formats:
date.time | date | time | now
where:
Specify the time in 24-hour format, relative to the local time zone. If you omit the time, the default value is 00:00:00. If you omit the date, the default value is today. If you omit the century, year, or a specific date, the most recent one is used. Specify UTC if you want the time to be resolved to the same moment in time regardless of time zone. Use the plus (+) or minus (-) operator to specify a positive or negative offset to the UTC time. If you specify UTC without hour or minute offsets, the default setting is Greenwich Mean Time (GMT). (Dates before January 1, 1970 Universal Coordinated Time (UTC) are invalid.)
Examples:
22-November-2002
sunday
yesterday.16:00
8-jun
13:00
today
9-Aug.10:00UTC
–reverse
Reverse the order of the list of oplog entries.
In these examples, the lines are broken for readability. You must enter each command on a single physical line.
multiutil dumpoplog -clan telecomm -site boston_hub -family DOC -user susan -p passwd Item 1, 22-Jan-2002.10:50:21 TABLE_PACKLET (epoch BOSTON_HUB.1 initiated 22-Jan-2002.10:50:21) Item 2, 22-Jan-2002.10:50:21 TABLE_PACKLET (epoch BOSTON_HUB.2 initiated 22-Jan-2002.10:50:21) Item 3, 22-Jan-2002.10:50:21 TABLE_PACKLET (epoch BOSTON_HUB.3 initiated 22-Jan-2002.10:50:21) Item 4, 22-Jan-2002.10:50:22 TABLE_PACKLET (epoch BOSTON_HUB.4 initiated 22-Jan-2002.10:50:22) Item 5, 22-Jan-2002.10:50:22 TABLE_PACKLET (epoch BOSTON_HUB.5 initiated 22-Jan-2002.10:50:22) Item 6, 22-Jan-2002.11:06:21 ACTION_PACKLET (epoch BOSTON_HUB.6 initiated 22-Jan-2002.11:06:21) Item 7, 22-Jan-2002.11:10:35 TABLE_PACKLET (epoch BOSTON_HUB.7 initiated 22-Jan-2002.11:10:35) Item 8, 22-Jan-2002.11:10:36 EXPORT_PACKLET to SANFRAN_HUB
multiutil dumpoplog -clan telecomm -site sanfran_hub -family DEV -user jcole -p passwd -short -at sanfran_hub Item 3, 07-Feb-2002.11:20:29 ACTION_PACKLET (epoch SANFRAN_HUB.1 initiated 07-Feb-2002.11:20:29) Item 4, 07-Feb-2002.11:23:24 TABLE_PACKLET (epoch SANFRAN_HUB.2 initiated 07-Feb-2002.11:23:24) Item 6, 07-Feb-2002.11:24:27 ACTION_PACKLET (epoch SANFRAN_HUB.3 initiated 07-Feb-2002.11:24:26) Item 7, 07-Feb-2002.11:24:49 TABLE_PACKLET (epoch SANFRAN_HUB.4 initiated 07-Feb-2002.11:24:49)
multiutil dumpoplog -clan telecomm -site bangalore -family DOC -user masako -p passwd -short -since 28-Jan-2002 Item 1, 28-Jan-2002.10:11:37 TABLE_PACKLET (epoch BOSTON_HUB.1 initiated 28-Jan-2002.10:11:37) Item 2, 28-Jan-2002.10:11:37 TABLE_PACKLET (epoch BOSTON_HUB.2 initiated 28-Jan-2002.10:11:37) Item 3, 28-Jan-2002.10:11:37 TABLE_PACKLET (epoch BOSTON_HUB.3 initiated 28-Jan-2002.10:11:37) Item 4, 28-Jan-2002.10:11:37 TABLE_PACKLET (epoch BOSTON_HUB.4 initiated 28-Jan-2002.10:11:37) Item 5, 28-Jan-2002.10:11:37 TABLE_PACKLET (epoch BOSTON_HUB.5 initiated 28-Jan-2002.10:11:37) Item 6, 28-Jan-2002.10:11:37 TABLE_PACKLET (epoch BOSTON_HUB.6 initiated 28-Jan-2002.10:11:37)
multiutil dumpoplog -clan telecomm -site boston_hub -family DEV -user susan passwd -long -from 3 -to 6 Item 3, 28-Jan-2002.10:11:37 TABLE_PACKLET 334 (epoch BOSTON_HUB.3 initiated 28-Jan-2002.10:11:37) Schema: 14, Schema Rev: 1, SchemaRev Ver:1 Item 4, 28-Jan-2002.10:11:37 TABLE_PACKLET 336 (epoch BOSTON_HUB.4 initiated 28-Jan-2002.10:11:37) Schema: 14, Schema Rev: 1, SchemaRev Ver:1 Item 5, 28-Jan-2002.10:11:37 TABLE_PACKLET 340 (epoch BOSTON_HUB.5 initiated 28-Jan-2002.10:11:37) Schema: 14, Schema Rev: 1, SchemaRev Ver:1 Item 6, 28-Jan-2002.10:11:37 TABLE_PACKLET 355 (epoch BOSTON_HUB.6 initiated 28-Jan-2002.10:11:37) Schema: 14, Schema Rev: 1, SchemaRev Ver:1
multiutil dumpoplog -clan testclan -site tokyo -family TEST -user masako -p passwd -long -from 1 Item 1, 29-Jan-2002.13:22:44 SPECIAL_PACKLET 88 (epoch TOKYO.1 initiated 29-Jan-2002.13:22:44) Schema: 10, Schema Rev: 1, SchemaRev Ver:0
lsepoch, scruboplog