|
|
|
Replication Manager API returned OK.
Cursor is at the end of the file (EOF).
Key value already exists.
Record not found.
Disconnected server.
Not able to connect to server.
Shutdown error.
Timeout error.
No more info; batch canceled.
Feature not yet supported.
RCES warning error code.
Couldn't initialize the configuration object.
Couldn't initialize the logger object.
Couldn't initialize the notification object.
Couldn't initialize the filesystem object.
Couldn't initialize the data provider object.
Invalid argument count.
Invalid argument value. This can occur if an element is missing from a connection string, such as a missing or invalid user name or password when connecting to the sever.
Missing required argument.
Hash table exceeded the maximum size.
Memory allocation error.
Queue exceeded the maximum size.
Invalid notification action.
Queue is not initialized.
Mutex is not initialized.
Mutex has not started the process thread.
Invalid action.
Mismatch provider DB type.
Couldn't load local c-tree library.
Couldn't allocate c-tree session.
Invalid field number.
Couldn't start schema update thread.
Internal error in <FC_PROD_RPL_MGR> API.
Couldn't initialize the replication object.
Invalid replication object.
Already started error.
Consumer not found.
Already exists error.
Invalid file type.
Invalid file volume.
Replication Plan is not deployed.
Missing authentication information.
File transfer not initialized.
Replication Plan is not stopped.
Replication Plan is not found.
Entity is in use.
Missing Replication Plan error.
Missing database in subscription.
Missing volume information.
File not found error.
Invalid subscription.
Invalid file path.
Invalid function.
Invalid operating system (opSystem).
Thread is not running.
Replication Plan is not started.
Replication Plan is missing log position.
Agent is not connected.
Invalid token. It could be the wrong token or an expired token.
DB Engine is in use.
Replication Agent error.
Master server is not ready yet.
Replication doesn't have any Subscription.
Target file already exists.
Replication Agent is disconnected.
Replication resync failed.
Replication is in a resync operation now.
Replication doesn't have any file.
Operation has been canceled.
File dump restore error.
SQL Port mismatch.
Replication Plan information already exists.
Replication Plan is not inactive.
Replication Plan is not archived.
Missing data provider.
Not possible to mark the main Replication Manager server as unmanaged.
FTI is not supported.
Not able to clean Replication Exceptions.
