All keywords are case-insensitive.
...
- Keywords are shown in UPPERCASE.
- Placeholders for which you must substitute an actual value are shown in lowercase. These can include clauses and other expressions.xxxdatafile249
- Vertical (|) bars separate multiple choices. They indicate "or".
- Square brackets ( [] ) are not typed. They indicate that the enclosed syntax is optional.
- Curly braces ( {} ) usually are not typed. They indicate that you must specify one of the enclosed choices. (The choices are separated by vertical bars.)
- Loops or repetitions are indicated by a second, bracketed appearance of the term, set of terms, or expression, followed by ellipsis points. The brackets indicate that the repetition is optional (all repetitions are optional). The ellipsis points indicate that multiple repetitions are allowed. The bracketed appearance of the term begins with a comma if the repetitions are comma delimited.
- All other punctuation (quotation marks, commas, semicolons, and so on) must be typed as shown.
- Some commands require a restart of the MINE or APPLY processes.
| Anchor |
|---|
...
|
...
|
...
APPLY
Shows general help, help for specific command or help for a variable.
...
Reads the designated file like it 
APPLY COMMIT TRANSACTION. Force commit of the specified transaction on APPLY. Use List transactions first to see what transactions are currently pending on APPLY.
Ensure you fully understand the implication before running this command.
APPLY ROLLBACK TRANSACTION. Force rollback of the specified transaction on APPLY. Use List transactions first to see what transactions are currently pending on APPLY.
Ensure you fully understand the implication before running this command.
| Anchor | ||||
|---|---|---|---|---|
|
Shows general help, help for specific command or help for a variable.
| Anchor | ||||
|---|---|---|---|---|
|
Reads the designated file like it would be entered at command prompt. As with SQL*Plus, both "@file" and "@ file" work.
...
The transaction list may also include internal non committed transaction not related to the replication. Please see List transactions for more information.
Use APPLY COMMIT TRANSACTION to force commit of the specified transactions on APPLY, or APPLY ROLLBACK TRANSACTION to force rollback of the transaction on APPLY. Ensure you fully understand the implication before running the COMMIT or ROLLBACK commands.
...
APPLY COMMIT TRANSACTION. Force commit of the specified transaction on APPLY. Use List transactions first to see what transactions are currently pending on APPLY.
Ensure you fully understand the implication before running this command.
APPLY ROLLBACK TRANSACTION. Force rollback of the specified transaction on APPLY. Use List transactions first to see what transactions are currently pending on APPLY.
Ensure COMMIT TRANSACTION to force commit of the specified transactions on APPLY, or APPLY ROLLBACK TRANSACTION to force rollback of the transaction on APPLY. Ensure you fully understand the implication before running this command.the COMMIT or ROLLBACK commands.
| Anchor | ||||
|---|---|---|---|---|
|
...
The DEFAULT conflict handler will not be applied to existing prepared (replicated) tables. The DEFAULT conflict handler will only be applied to tables that are prepared after the DEFAULT conflict handler is set. To change the conflict handler for existing prepared tables, each table has to be individually set using FOR TABLE conflict handler.
| Anchor | ||||
|---|---|---|---|---|
|
...