In replica: Valid master user, SYS_SYNC_ADMIN_ROLE, or SYS_SYNC_REGISTER_ROLE
Usage
Use the MESSAGE BEGIN statement to explicitly begin each message that is sent from a replica database to the master database.
The MESSAGE BEGIN statement can be executed only on the replica databases.
When working with messages, autocommit mode must be switched off.
Parameters, clauses, keywords, and variables
▪ unique‑message‑name: A message name that is unique within the replica database (although a different replica database of the same master database can have a message with the same name). To construct unique message names, you can use the GET_UNIQUE_STRING() function, see String functions.
Note After a message has been processed, that message name can be reused. However, if the message fails for any reason, the master database keeps a copy of the failed message and, if you try to reuse the message name before you delete the failed message, then the name is not unique. Therefore, you might want to use a new message name even in situations where you might be able to re-use an existing name.
▪ master-node-name: When using the REGISTER REPLICA statement to register a replica database with a master catalog, other than the master system catalog, you must provide the master node name in the MESSAGE BEGIN statement. The master node name is used to resolve the correct catalog at the master database. Later messages are automatically sent to the correct master node.
Note The master node name must be enclosed in double quotation marks.
Return values from replica database
Error code
Description
25005
Message message‑name is already active.
A message of the specified name was created and appears to still be active. The message is automatically deleted when the reply of the message has been successfully executed in the replica.
25035
Message message‑name is in use.
A user is currently creating or forwarding this message.