|
Code
|
Class
|
Type
|
Description
|
|---|---|---|---|
|
25001
|
Synchronization
|
Error
|
Master cannot save propagated statements.
The master received propagated transaction statements from the replica, but is not able to save the statements. (Note that the master must save the statements before executing them). Possible causes of the error are:
▪Master database has exceeded the database size limit. You can increase the database size by changing the IndexFile.FileSpec parameter setting. For details on this parameter, read Managing parameters. You need to restart the server for the new setting to take effect.
▪An internal error exists in the database server. If error 25001 occurs even after you have increased the database size, contact solidDB® Support.
|
|
25002
|
Synchronization
|
Error
|
Cannot save data dictionary statements.
|
|
25003
|
Synchronization
|
Error
|
Cannot save SAVE statements.
It is not possible to save a “SAVE” statement for later propagation. For example, the following SQL statement returns an error:
SAVE CALL MYPROC(1, 'foo')
solidDB® statements that return this error:
SAVE sql_statement
|
|
25004
|
Synchronization
|
Error
|
Dynamic parameters are not supported.
Input parameters of a subscription must be given as literals. They cannot be dynamically bound to the statement.
solidDB® statements that return this error:
DROP SUBSCRIPTION
MESSAGE message_name APPEND REFRESH publication_name
|
|
25005
|
Synchronization
|
Error
|
Message message_name is already active.
A message of the specified name that was created appears to still be active. A message becomes active when the following MESSAGE command is executed:
MESSAGE message_name BEGIN
The message is automatically deleted when the reply of the message has been successfully executed in the replica database.
solidDB® statements that return this error:
MESSAGE message_name APPEND
MESSAGE message_name BEGIN
MESSAGE message_name DELETE
MESSAGE message_name EXECUTE
MESSAGE message_name FORWARD
MESSAGE GET REPLY
|
|
25006
|
Synchronization
|
Error
|
Message message_name not active
A message has already been committed or ended using the MESSAGE END statement. New tasks cannot be appended to the message using the MESSAGE APPEND command. Probable cause for this error is that the AUTOCOMMIT mode is used in the connection.
You must first remove the message with MESSAGE message_name DELETE command. Then switch autocommit off and run the script again.
solidDB® statements that return this error:
MESSAGE message_name APPEND synchronization_task
|
|
25007
|
Synchronization
|
Error
|
Master master_name not found
A replica attempts to perform an operation to a master database that cannot be found.
solidDB® statements that return this error:
SET SYNC CONNECT connect_string TO MASTER master_name DROP MASTER master_name IMPORT 'filename' SAVE sql_statement
|
|
25009
|
Synchronization
|
Error
|
Replica replica_name not found
The replica name specified in a command cannot be found.
solidDB® statements that return this error:
DROP REPLICA replica_name
DROP SUBSCRIPTION publication_name(parameter_list)
[FROM REPLICA replica_name] GRANT REFRESH ON publication_name
MESSAGE DELETE CURRENT TRANSACTION
MESSAGE message_name [FROM REPLICA replica_name] DELETE
|
|
25010
|
Synchronization
|
Error
|
Publication publication_name not found.
The publication name of a subscription is incorrect.
solidDB® statements that return this error:
MESSAGE APPEND REFRESH publication_name(parameter_list)
DROP PUBLICATION publication_name
EXPORT SUBSCRIPTION publication_name ...
REVOKE REFRESH ON publication_name...
|
|
25011
|
Synchronization
|
Error
|
Wrong number of parameters to publication publication_name.
A subscription to a publication contains incorrect number of parameters. The data types of the given subscription parameters must match the input parameter definition of the publication.
solidDB® statements that return this error:
DROP SUBSCRIPTION publication_name (parameter_list) [FROM REPLICA replica_name]
MESSAGE message_name APPEND REFRESH
publication_name (parameter_list)
|
|
25012
|
Synchronization
|
Error
|
Message reply timed out.
A reply message has not arrived to the replica database within the given timeout period. The reason is that the reply message is not yet ready in the master database. The message needs to be retrieved again using MESSAGE message_name GET REPLY command.
solidDB® statements that return this error:
MESSAGE message_name FORWARD TIMEOUT timeout_in_seconds MESSAGE message_name GET REPLY TIMEOUT timeout_in_seconds
For example, if the master database takes a long time to start due to, for example, a server restart, the message reply to replica can time out. To recover, reissue the MESSAGE GET REPLY command and set the timeout to a larger value or FOREVER.
|
|
25013
|
Synchronization
|
Error
|
Message name message_name not found.
The message with the given name does not exist. The message name is given when the message is created with command MESSAGE message_name BEGIN. The message name is released when the reply message has been successfully executed in the replica database.
Message names must be unique within the replica database.
A message can be deleted from the database with command: MESSAGE message_name [FROM REPLICA replica_name ] DELETE
Statements that return this error:
MESSAGE message_name APPEND
MESSAGE message_name DELETE
MESSAGE message_name END
MESSAGE message_name EXECUTE
MESSAGE message_name FORWARD
MESSAGE message_name FROM REPLICA EXECUTE
MESSAGE message_name FROM REPLICA
replica_name DELETE CURRENT TRANSACTION
MESSAGE message_name GET REPLY
|
|
25014
|
Synchronization
|
Error
|
More than one master name found.
|
|
25015
|
Synchronization
|
Error
|
Syntax error: error_message, line line_number Syntax is not correct.
Statements that return this error:
MESSAGE message_name APPEND
CREATE PUBLICATION publication_name
See the CREATE PUBLICATION syntax reference for correct syntax.
|
|
25016
|
Synchronization
|
Error
|
Message not found, replica id replica_id, message id message_id
Message not found in master during processing. This can happen if the message is explicitly deleted in master.
Statements that return this error:
MESSAGE message_name FORWARD MESSAGE message_name GET REPLY MESSAGE message_name RESTART
|
|
25017
|
Synchronization
|
Error
|
No unique key found for table table_name.
The primary key for the table has not been defined.
Each table that is part of an incremental publication must have a primary key defined. The synchronization history mechanism cannot function without explicitly defined primary keys.
Statements that return this error:
ALTER TABLE table_name SET SYNCHISTORY
|
|
25018
|
Synchronization
|
Error
|
Illegal message state.
An internal error has occurred in the message processing. It is not possible to continue executing the message after this error. Delete the message using the following command:
MESSAGE message_name [FROM REPLICA replica_name ] DELETE
Statements that return this error:
MESSAGE message_name ...
|
|
25019
|
Synchronization
|
Error
|
Database is not a replica.
A synchronization message can only be created in a database that has been registered to be a replica database. See the example code in solidDB® Advanced Replication User Guide, which provides information about registering a replica database.
Statements that return this error:
DROP MASTER master_name
DROP PUBLICATION publication_name REGISTRATION DROP SUBSCRIPTION publication_name ... IMPORT 'filename' MESSAGE message_name BEGIN MESSAGE message_name ENDSET SYNC CONNECT 'connect_string' TO MASTER master_name
|
|
25020
|
Synchronization
|
Error
|
Database is not a master.
A command that can be executed only in a master database has been attempted to execute in a non-master database.
A database can be set to be a master database of a system by entering the following command:
SET SYNC MASTER YES
Statements that return this error:
ALTER USER replica_user SET MASTER master_name USER MESSAGE message_name FROM REPLICA replica_name RESTART MESSAGE message_name FROM REPLICA replica_name DELETE DROP REPLICA replica_name DROP SUBSCRIPTION
subscription_name FROM REPLICA replica_name
|
|
25021
|
Synchronization
|
Error
|
Database is not master or replica database.
In order to create or drop publication definitions or set the SYNCHISTORY property of a table, the database must be defined to be either master or replica (or both).
Statements that return this error:
CREATE PUBLICATION publication_name ...
DROP PUBLICATION publication_name REGISTRATION
SET SYNC MAINTENANCE MODE ...;
ALTER TABLE table_name SET SYNCHISTORY
|
|
25022
|
Synchronization
|
Error
|
User generated error.
The execution of a transaction has been cancelled and rolled back in the master database. Because of the failed transaction, the execution of the message that contained the transaction has been stopped.
User can request the server to roll back a transaction by setting the following parameters to the bulletin board of the transaction:
PutParam('SYS_ROLLBACK', 'YES')
PutParam('SYS_ERROR_CODE', numeric_value_as_string) PutParam('SYS_ERROR_TEXT', error_text_as_string)
If the SYS_ERROR_CODE parameter is not specified or it contains an invalid value, the error number 25022 is returned.
Statements that return this error:
MESSAGE message_name FORWARD TIMEOUT timeout_in_seconds MESSAGE message_name GET REPLY TIMEOUT timeout_in_seconds
|
|
25023
|
Synchronization
|
Error
|
Replica registration failed.
An error has occurred during replica registration.
Statements that return this error:
MESSAGE message_name FORWARD TIMEOUT timeout_in_seconds MESSAGE message_name GET REPLY TIMEOUT timeout_in_seconds
|
|
25024
|
Synchronization
|
Error
|
Master not defined.
No definition for the master exists or the configuration changed during message processing. The server was unable to properly initialize the synchronization environment. You can check the master from the replica’s system table SYS_SYNC_MASTERS. All successfully registered replicas are found from the master database system table SYS_SYNC_REPLICAS.
Note This error can be returned if you use double quotation marks rather than single quotation marks around the master_connect_string in a MESSAGE FORWARD command.
Statements that return this error:
IMPORT 'filename'
MESSAGE message_name FORWARD TO 'master_connect_string'
TIMEOUT timeout_in_seconds
MESSAGE message_name GET REPLY ...
MESSAGE message_name APPEND REFRESH publication_name
MESSAGE message_name EXECUTE ....
|
|
25025
|
Synchronization
|
Error
|
Node name not defined.
Before setting up a master database or registering a replica database, the node name of the database must be set. This can be done with the following command:
SET SYNC NODE node_name
Statements that return this error:
DROP PUBLICATION publication_name REGISTRATION MESSAGE message_name APPEND REGISTER REPLICA MESSAGE message_name BEGIN ...
|
|
25026
|
Synchronization
|
Error
|
A user who has not been defined in the master database, attempts to perform a solidDB® SQL command.
Statements that return this error:
IMPORT 'filename' SAVE sql_statement MESSAGE message_name...
To resolve this problem, use the correct user ID if there is one. If there is not already a correct user ID, you have two options:
▪Map a master user to the replica userid you are using. (The master user must already have been downloaded from the master to the replica.) To map a master user to a replica user, execute the command:
ALTER USER replica_user SET MASTER master_name USER user_specification
▪Add an appropriate user to the master database, and download it by executing the following command:
MESSAGE message_name APPEND SYNC_CONFIG
|
|
25027
|
Synchronization
|
Error
|
Too long column or parameter value; configured maximum is <value>
|
|
25028
|
Synchronization
|
Error
|
Message message_name can include only one system subscription.
System subscriptions (REGISTER REPLICA and SYNC_CONFIG) must be kept in separate messages. These tasks must be the only ones of their messages.
Statements that return this error:
MESSAGE message_name APPEND
REFRESH publication_name
|
|
25030
|
Synchronization
|
Error
|
Replica replica_name is already registered.
A replica attempts to register itself using a name that is already in use. Replica names must be unique. If you know that the chosen replica name is no longer used by any other replicas, drop it from the master database with the command DROP REPLICA replica_name. Then register the replica again. Otherwise, change the newly created replica’s name and register it again. Note that replica registration occurs after the registration message is sent to the master.
Statements that return this error:
MESSAGE message_name FORWARD ...
MESSAGE message_name GET REPLY ...
|
|
25031
|
Synchronization
|
Error
|
Transaction is active, operation failed.
A replica attempts to process a message when having an active transaction.
Statements that return this error:
IMPORT 'filename'
MESSAGE message_name FORWARD ...
MESSAGE message_name GET REPLY TIMEOUT ...
MESSAGE message_name EXECUTE
|
|
25032
|
Synchronization
|
Error
|
All publication SQL statements must return rows.
The publication definition contains SQL operations that do not return rows. Only SELECT statements are allowed in the publication.
Statements that return this error:
CREATE PUBLICATION publication_name
|
|
25033
|
Synchronization
|
Error
|
Publication publication_name already exists.
A publication has been attempted to create with a name that is already in use.
Statements that return this error:
CREATE PUBLICATION publication_name
|
|
25034
|
Synchronization
|
Error
|
Message name message_name already exists.
Each message must have a name that is unique within the database.
Statements that return this error:
MESSAGE message_name BEGIN
|
|
25035
|
Synchronization
|
Error
|
Message message_name is in use.
A message is locked during an attempt to execute it or delete it. A locked message cannot be re-executed or deleted. If you get this error while attempting to create a new message, it is probably due to an existing message with the same name. You can check existing messages from the system table SYS_SYNC_REPLICA_MSGINFO in the replica or from the system table SYS_SYNC_MASTER_MSGINFO in the master database.
Statements that return this error:
MESSAGE message_name BEGIN
MESSAGE message_name END
MESSAGE message_name EXECUTE ...
MESSAGE message_name FROM REPLICA replica_name DELETE
MESSAGE message_name FORWARD TIMEOUT ...
MESSAGE message_name GET REPLY TIMEOUT ...
|
|
25036
|
Synchronization
|
Error
|
Publication publication_name not found or publication version mismatch.
A publication has been dropped or redefined at master during message processing. Recover by DROP SUBSCRIPTION at replica.
Statements that return this error:
IMPORT 'filename'
MESSAGE message_name FORWARD TIMEOUT ...
MESSAGE message_name GET REPLY TIMEOUT ...
MESSAGE message_name EXECUTE ...
|
|
25037
|
Synchronization
|
Error
|
Publication column count mismatch in table table_name. Database definitions at master and replica do not match.
Statements that return this error:
MESSAGE message_name FORWARD TIMEOUT timeout_in_seconds
MESSAGE message_name GET REPLY TIMEOUT timeout_in_seconds
MESSAGE message_name EXECUTE
|
|
25038
|
Synchronization
|
Error
|
Table is referenced in publication publication_name; drop or alter operations are not allowed.
A table which is referenced in a publication can not be dropped or altered.
Statements that return this error:
DROP TABLE table_name ALTER TABLE table_name
|
|
25039
|
Synchronization
|
Error
|
Table is referenced in subscription to publication publication_name; drop or alter operations are not allowed.
Statements that return this error: ALTER TABLE table_name
|
|
25040
|
Synchronization
|
Error
|
User id user_id is not found.
User information has been changed at the replica during message execution.
Statements that return this error:
IMPORT 'filename'
MESSAGE message_name GET REPLY TIMEOUT timeout_in_seconds
MESSAGE message_name EXECUTE ...
MESSAGE message_name FORWARD ...
|
|
25041
|
Synchronization
|
Error
|
Subscription to publication publication_name not found.
The subscription that is expected to be in the replica is not found. This error occurs if the subscription is explicitly dropped at the replica.
Statements that return this error:
IMPORT 'filename'
MESSAGE message_name EXECUTE ...
MESSAGE message_name FORWARD ...
MESSAGE message_name GET REPLY ...
DROP SUBSCRIPTION subscription_name
DROP SUBSCRIPTION subscription_name REPLICA replica_name
|
|
25042
|
Synchronization
|
Error
|
Message is too long (number bytes) to forward. Maximum is set to number bytes.
The length of a message to be forwarded exceeds the limit for message’s length. The limit can be set by variable SYS_R_MAXBYTES_OUT.
Statements that return this error:
MESSAGE message_name FORWARD
|
|
25043
|
Synchronization
|
Error
|
Reply message is too long (number bytes). Maximum is set to number bytes.
The length of a message to be received as a reply exceeds the limit for message’s length. The limit can be set by variable SYS_R_MAXBYTES_IN.
Statements that return this error:
MESSAGE message_name GET REPLY
|
|
25044
|
Synchronization
|
Error
|
SYNC_CONFIG system publication takes only character arguments.
In a subscription attempt, publication SYNC_CONFIG was found to have invalid data types for the arguments.
Statements that return this error:
MESSAGE message_name APPEND REFRESH SYNC_CONFIG
|
|
25045
|
Synchronization
|
Error
|
Master/replica node support disabled.
|
|
25046
|
Synchronization
|
Error
|
Commit and rollback are not supported in propagated transactions.
This error is caused when a transaction attempts to execute a COMMIT or ROLLBACK command in the master database. The error is returned to the server that is running the procedure. The message containing the procedure will fail.
|
|
25047
|
Synchronization
|
Error
|
Parameter info publication not found.
|
|
25048
|
Synchronization
|
Error
|
Publication publication_name request info not found.
A publication has been dropped while message is being executed.
Statements that return this error:
IMPORT 'filename'
MESSAGE message_name EXECUTE ...
MESSAGE message_name FORWARD ...
MESSAGE message_name GET REPLY ...
|
|
25049
|
Synchronization
|
Error
|
Referenced table table_name not found in subscription hierarchy.
A publication has referenced a table which does not exist.
Statements that return this error:
CREATE PUBLICATION publication_name ...
|
|
25050
|
Synchronization
|
Error
|
Table has no history.
|
|
25051
|
Synchronization
|
Error
|
Unfinished messages found.
Replica mode has been attempted to be switched off while there are messages either waiting to be forwarded or being executed at master.
Statements that return this error:
SET SYNC REPLICA NO
|
|
25052
|
Synchronization
|
Error
|
Failed to set node name to node_name. The node_name can be invalid.
|
|
25053
|
Synchronization
|
Error
|
Replica not registered in master.
|
|
25054
|
Synchronization
|
Error
|
Table table_name is not set for synchronization history.
A table in the master database has the SYNCHISTORY property set, but the corresponding table in the replica does not.
Statements that return this error:
IMPORT 'filename'
MESSAGE message_name GET REPLY ...
MESSAGE message_name FORWARD ...
|
|
25055
|
Synchronization
|
Error
|
Connect information is allowed only when not registered.
The connect info in MESSAGE message_name FORWARD TO connect_info options is allowed only if the replica has not yet been registered to the master database.
Statements that return this error:
MESSAGE message_name FORWARD TO connect_info options
|
|
25056
|
Synchronization
|
Error
|
Autocommit not allowed.
The statement must be executed with autocommit mode turned off.
Statements that return this error:
All MESSAGE message_name ... statements
DROP SUBSCRIPTION subscription_name
DROP SUBSCRIPTION subscription_name REPLICA replica_name
DROP REPLICA replica_name
DROP MASTER master_name
EXPORT SUBSCRIPTION
IMPORT 'filename'
|
|
25057
|
Synchronization
|
Error
|
Already registered to master master_name.
The replica database has already been registered to a master database.
Statements that return this error:
MESSAGE message_name GET REPLY ... (when registering a replica)
MESSAGE message_name FORWARD ... (when registering a replica)
|
|
25058
|
Synchronization
|
Error
|
Missing connect information.
|
|
25059
|
Synchronization
|
Error
|
After registration nodename cannot be changed.
The SYNC NODE NAME property of a database cannot be changed if the master has any registered replicas or replica has already been registered to a master database.
Statements that return this error:
SET SYNC NODE NAME unique_node_name
|
|
25060
|
Synchronization
|
Error
|
Column column_name does not exist on publication publication_name resultset in table table_name.
This error occurs when a replica finds out that the master is transferring data that does not include primary key values that the replica requires.
Statements that return this error:
IMPORT 'filename'
MESSAGE message_name GET REPLY ...
MESSAGE message_name FORWARD ...
|
|
25061
|
Synchronization
|
Error
|
Where condition for table table_name must refer to an outer table of the publication.
If a publication contains nested SELECTs, the WHERE clause of the inner SELECT must refer to the outer table of the outer SELECT.
Statements that return this error:
CREATE PUBLICATION publication_name
|
|
25062
|
Synchronization
|
Error
|
User user_id is not mapped to master user_id.
Dropping the user mapping failed because user is not mapped to a given master.
Statements that return this error:
ALTER USER replica_user SET MASTER master_name USER
|
|
25063
|
Synchronization
|
Error
|
User user_id is already mapped to master user_id.
User is already mapped to a given master.
Statements that return this error:
ALTER USER replica_user SET MASTER master_name USER
|
|
25064
|
Synchronization
|
Error
|
Unfinished message message_name found for replica replica_name.
Dropping the replica failed because there are unfinished messages.
Statements that return this error:
DROP REPLICA replica_name
|
|
25065
|
Synchronization
|
Error
|
Unfinished message message_name found for master master_name.
Dropping the master failed because there are unfinished messages.
Statements that return this error:
DROP MASTER master_name
|
|
25066
|
Synchronization
|
Error
|
Synchronization bookmark bookmark_name already exists.
Cannot create synchronization bookmark since the name already exists.
Statements that return this error:
CREATE SYNC BOOKMARK
|
|
25067
|
Synchronization
|
Error
|
Synchronization bookmark bookmark_name not found.
Bookmark name is not an existing bookmark.
Statements that return this error:
DROP SYNC BOOKMARK
|
|
25068
|
Synchronization
|
Error
|
Export file file_name open failure.
Failed to open export file for EXPORT SUBSCRIPTION.
Statements that return this error:
EXPORT SUBSCRIPTION
|
|
25069
|
Synchronization
|
Error
|
Import file file_name open failure.
Failed to open import file for IMPORT.
Statements that return this error:
IMPORT 'filename'
|
|
25070
|
Synchronization
|
Error
|
Statements can be saved only for one master in transaction.
Statements cannot be saved for multiple masters in one transaction.
Statements that return this error:
SAVE sql_statement
|
|
25071
|
Synchronization
|
Error
|
Not registered to publication publication_name.
Replica must be registered to a publication before the publication can be refreshed to the replica.
Statements that return this error:
DROP PUBLICATION publication_name REGISTRATION MESSAGE message_name APPEND REFRESH publication_name
|
|
25072
|
Synchronization
|
Error
|
Already registered to publication publication_name.
Replica is already registered to a publication.
Statements that return this error:
MESSAGE message_name APPEND REGISTER REPLICA
|
|
25073
|
Synchronization
|
Error
|
Export file can have data only from one master.
|
|
25074
|
Synchronization
|
Error
|
User definition not allowed for this operation.
Master user attempts to perform synchronization operation, but is denied access in the replica database because the registration user is still the active user. After the registration process, the command SET SYNC username must be set to NONE.
Statements that return this error:
SAVE sql_statement
DROP SUBSCRIPTION publication_name (in replica)
MESSAGE message_name APPEND REFRESH publication_name
MESSAGE message_name APPEND PROPAGATE TRANSACTIONS
MESSAGE message_name APPEND REGISTER PUBLICATION
MESSAGE message_name APPEND UNREGISTER PUBLICATION
MESSAGE message_name EXECUTE (in replica)
|
|
25075
|
Synchronization
|
Error
|
Transaction not found.
|
|
25076
|
Synchronization
|
Error
|
Only REGISTER REPLICA is allowed in message.
|
|
25077
|
Synchronization
|
Error
|
Node name is not valid.
|
|
25078
|
Synchronization
|
Error
|
Node name already exists.
|
|
25079
|
Synchronization
|
Error
|
Catalog is master and there are registered replicas. Catalog is not dropped.
|
|
25080
|
Synchronization
|
Error
|
Catalog is replica and it is registered to a master. Catalog is not dropped.
|
|
25081
|
Synchronization
|
Error
|
Subqueries are not allowed in publication definition.
|
|
25082
|
Synchronization
|
Error
|
Node name can not be removed if node is master or replica.
Node name cannot be set to NONE on a synchronized master and/or replica catalog.
Statements that return this error:
SET SYNC NODE NONE
|
|
25083
|
Synchronization
|
Error
|
Commit block cannot be used with HotStandby.
|
|
25084
|
Synchronization
|
Error
|
Cannot save ADMIN COMMAND.
|
|
25085
|
Synchronization
|
Error
|
Failed to store BLOB from message.
During synchronization, reading or storing a BLOB (LONG VARCHAR or LONG VARBINARY data) has failed because of an internal error.
|
|
25086
|
Synchronization
|
Error
|
Cannot save START statement.
|
|
25087
|
Synchronization
|
Error
|
Missing connect information for node node_name.
There is no connect string in the table SYS_SYNC_REPLICAS for the specified replica. If you have not defined the connect string in the replica solid.ini file, registering a replica does not automatically add the connect string into the SYS_SYNC_REPLICAS table. Define the connection information in the following way:
[Synchronizer] ConnectStrForMaster=<connect_string>
For example:
[Synchronizer]
ConnectStrForMaster=tcp replicahost 1316 |
|
25088
|
Synchronization
|
Error
|
Catalog already in maintenance mode. You have set the mode on already.
|
|
25089
|
Synchronization
|
Error
|
Not allowed to set maintenance mode off. Someone else has set the mode on, so you cannot set it off.
|
|
25090
|
Synchronization
|
Error
|
Catalog already in maintenance mode. Someone else has set the mode on, so you cannot set it off.
|
|
25091
|
Synchronization
|
Error
|
Catalog is not in maintenance mode. You tried to set the mode off when it was not on.
|
|
25092
|
Synchronization
|
Error
|
User version strings are not equal in master and replica, operation failed.
When the replica executes either of the following commands:
MESSAGE FORWARD
MESSAGE GET REPLY The server checks whether the master and replica sync schema version numbers are equal. If the version numbers are not equal, then the server gives this error.
Note If neither the master nor the replica has set the version number, you do not receive the error message.
|
|
25093
|
Synchronization
|
Error
|
A master database for this replica exists, operation failed. This message is returned when the user either tries to drop a replica catalog which is registered to a master, or tries to execute 'SET SYNC REPLICA NO' when the replica is registered to a master.
|
|
25094
|
Synchronization
|
Error
|
Received illegal message part type.
|
|
25095
|
Synchronization
|
Error
|
Message execution aborted.
|