The MESSAGE FROM REPLICA EXECUTE statement executes a failed message on the master database.
The MESSAGE FROM REPLICA EXECUTE statement is applicable only in advanced replication configurations. It can only be issued on the master database. On replica databases, use the MESSAGE EXECUTE statement.
The execution of a message stops, for example, if a DBMS level error such as a duplicate insert occurs during the execution. Also the execution of a message can stop if an error is raised from a procedure by putting the SYS_ROLLBACK parameter to the transactions bulletin board. This kind of error is recoverable by fixing the reason for the error, for example, by removing the duplicate row from the database, and then executing the message.
When the transaction in error is deleted with MESSAGE DELETE CURRENT TRANSACTION, the deletion is completed before the MESSAGE FROM REPLICA EXECUTE command is executed; that is, the statement starts the message from replica, but waits until the active statement is completed before actually executing the message. Thus the command performs asynchronous message execution.
Note When working with the messages, the autocommit mode must always be switched off.
Return values
Error code
Description
13047
No privilege for operation
25009
Replica replica_name not found
25013
Message name message_name not found
25018
Illegal message state.
An attempt was made to delete a transaction from a message that is not in error.
25056
Autocommit not allowed
Example
MESSAGE MyMsg0002 FROM REPLICA bills_laptop EXECUTE;