MESSAGE END

SQL Guide : solidDB® SQL statements : MESSAGE : MESSAGE END

MESSAGE END

MESSAGE unique_message_name END

Usage

The MESSAGE END statement closes a message in a replica database. Closing a message means that you can no longer append anything to it. A message must be “wrapped up” and made persistent before it can be sent to the master database. You must commit the transaction make the message persistent.

The MESSAGE END statement is applicable only in advanced replication configurations. It can be issued only on replica databases.

Note When working with messages, the autocommit mode must be switched off.

Return values from replica

Error code	Description
13133	Not a valid license for this product
25005	Message message_name is already active
25013	Message message_name not found
25018	Illegal message state. The MESSAGE BEGIN statement must exist to begin a transaction and the MESSAGE END statement can be executed only once per message.
25026	Not a valid master user
25035	Message message_name is in use A user is currently creating or forwarding this message.
25056	Autocommit not allowed

Return values from master

Error code	Description
25019	Database is not a replica database
25056	Autocommit not allowed

Examples

MESSAGE MyMsg001 END; COMMIT WORK;

The following example shows a complete message that propagates transactions and refreshes from publication PUB_CUSTOMERS_BY_AREA.

MESSAGE MyMsg001 BEGIN;
MESSAGE MyMsg001 APPEND PROPAGATE TRANSACTIONS;
MESSAGE MyMsg001 APPEND REFRESH PUB_CUSTOMERS_BY_AREA("OSOUTH');
MESSAGE MyMsg001 END;
COMMIT WORK;