SQL Guide : System stored procedures : System stored procedures for advanced replication : SYNC_UNREGISTER_REPLICA
  
SYNC_UNREGISTER_REPLICA
The SYNC_UNREGISTER_REPLICA system stored procedure unregisters the specified replica catalog from the master and optionally drops the replica catalog.
CALL SYNC_UNREGISTER_REPLICA (
  replica_catalog_name,  -- WVARCHAR
  drop_catalog,          -- INTEGER
  force                  -- INTEGER
)
EXECUTES ON: replica.
You must have administrator or synchronization administrator access rights to execute this stored procedure.
If the drop_catalog parameter has a non-zero value, the replica catalog is dropped. Any possibly hanging messages for the replica are deleted in both ends of the system.
If the replica_catalog_name is NULL, the current catalog is used.
If force is non-zero, the master accepts unregistration even if messages for this replica exist in the master. In that case, those messages are deleted.
If the user has any uncommitted changes (that is, open transactions), the call will fail with an error.
This system procedure does not return a resultset.
RC
Text
Description
13047
No privilege for operation
 
13110
NULL not allowed
Catalog name cannot be NULL if drop_catalog is non-zero.
13133
Not a valid license for this product.
 
21xxx
Communication error
Was not able to connect to master. For more details about 21xxx errors, see “solidDB® communication errorsin the solidDB® Administrator Guide.
25005
Message is already active.
 
25019
Database is not a replica database.
 
25020
Database is not a master database.
 
25023
Replica not registered.
 
25031
Transaction is active, operation failed.
The user has made some changes that have not yet been committed.
25035
Message is in use.
 
25051
Unfinished messages found.
 
25056
Autocommit not allowed.
You must run this stored procedure with autocommit off.
25079
Catalog is master and there are registered replicas. Catalog is not dropped.
 
25093
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.
See also
System stored procedures for advanced replication