Release 10.1B: Progress Fathom Replication
User Guide
Preface
This Preface contains the following sections:
Purpose
This book describes the how to configure and use Progress® Fathom™ Replication. In addition, it describes the underlying architecture of Fathom Replication.
Audience
This book is intended for anyone familiar with OpenEdge™ database administration who plans to set up and use Fathom Replication.
Organization
Chapter 1 "Overview of Fathom Replication"
Provides an overview of the functionality and architecture of Fathom Replication.
Chapter 2 "Planning for Fathom Replication"
Provides a description of database considerations for Fathom Replication.
Chapter 3 "Implementing Fathom Replication"
Provides instructions on how to use Fathom Replication and describes the procedures Fathom Replication automatically performs.
Chapter 4 "Replication Database Recovery"
Provides details about how to handle failure conditions and database failure on source or target machines, including information about transition and the failback process.
Provides reference information for Fathom Replication, including descriptions of properties, utilities, and virtual system tables.
Chapter 6 "Fathom Replication Quick Command Summary"
Provides a quick command summary for setting up and using Fathom Replication.
Using this manual
Use this manual to get an overview of Fathom Replication and its architecture; to plan for and implement Fathom Replication; to handle replication database recovery; and to review replication reference and command summary information.
Typographical conventions
This manual uses the following typographical conventions:
Examples of syntax descriptions
In this example,
ACCUM
is a keyword, andaggregate
andexpression
are variables:
FOR
is one of the statements that can end with either a period or a colon, as in this example:
In this example,
STREAM
stream
,UNLESS-HIDDEN
, andNO-ERROR
are optional:
In this example, the outer (small) brackets are part of the language, and the inner (large) brackets denote an optional item:
A called external procedure must use braces when referencing compile-time arguments passed by a calling procedure, as shown in this example:
In this example,
EACH
,FIRST
, andLAST
are optional, but you can choose only one of them:
In this example, you must include two expressions, and optionally you can include more. Multiple expressions are separated by commas:
In this example, you must specify
MESSAGE
and at least oneexpression
orSKIP
[ (n
) ], and any number of additionalexpression
orSKIP
[ (n
) ] is allowed:
In this example, you must specify {
include-file
, then optionally any number ofargument
or&argument-name = "argument-value"
, and then terminate with }:
Long syntax descriptions split across lines
Some syntax descriptions are too long to fit on one line. When syntax descriptions are split across multiple lines, groups of optional and groups of required items are kept together in the required order.
In this example,
WITH
is followed by six optional items:
Complex syntax descriptions with both required and optional elements
Some syntax descriptions are too complex to distinguish required and optional elements by bracketing only the optional elements. For such syntax, the descriptions include both braces (for required elements) and brackets (for optional elements).
In this example,
ASSIGN
requires either one or morefield
entries or onerecord
. Options available withfield
orrecord
are grouped with braces and brackets:
OpenEdge messages
OpenEdge displays several types of messages to inform you of routine and unusual occurrences:
- Execution messages inform you of errors encountered while OpenEdge is running a procedure; for example, if OpenEdge cannot find a record with a specified index field value.
- Compile messages inform you of errors found while OpenEdge is reading and analyzing a procedure before running it; for example, if a procedure references a table name that is not defined in the database.
- Startup messages inform you of unusual conditions detected while OpenEdge is getting ready to execute; for example, if you entered an invalid startup parameter.
After displaying a message, OpenEdge proceeds in one of several ways:
- Continues execution, subject to the error-processing actions that you specify or that are assumed as part of the procedure. This is the most common action taken after execution messages.
- Returns to the Progress Procedure Editor, so you can correct an error in a procedure. This is the usual action taken after compiler messages.
- Halts processing of a procedure and returns immediately to the Progress Procedure Editor. This does not happen often.
- Terminates the current session.
OpenEdge messages end with a message number in parentheses. In this example, the message number is
200
:
If you encounter an error that terminates OpenEdge, note the message number before restarting.
Obtaining more information about OpenEdge messages
In Windows platforms, use OpenEdge online help to obtain more information about OpenEdge messages. Many OpenEdge tools include the following Help menu options to provide information about messages:
- Choose Help
Recent Messages to display detailed descriptions of the most recent OpenEdge message and all other messages returned in the current session.
- Choose Help
Messages and then type the message number to display a description of a specific OpenEdge message.
- In the Progress Procedure Editor, press the HELP key or F1.
On UNIX platforms, use the Progress
pro
command to start a single-user mode character OpenEdge client session and view a brief description of a message by providing its number.
![]()
To use the pro command to obtain a message description by message number:
Copyright © 2006 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |