Application behavior on the read-only node
An application needs to be aware of errors that it can encounter on the read-only node.
Application behavior when running on the read-only node is very similar to running on the secondary node when the replication state is BLOCKED. In general, applications and users are prevented from making changes to replication eligible objects from the read-only node.
The specific failures observed on the read-only node include the CPFC922 and CPF4ACF escape messages.
For SQL activity, the failure returned is SQLSTATE -7061, with SQLSTATE '55019' and reason code 80.
- 80 -- Replicated operation cannot be initiated on read-only node.