Opaque Exceptions Table
An opaque exceptions table records a whole message into a column along with the error message.
Subscription Service uses two logical layers when processing a message. The first layer decodes data from the message and the second layer provides the database transaction. If an exception occurs in the first layer, the adapter logs the message to the opaque exceptions table.
In the second layer, if any DML command fails at any level, the adapter rolls back this transaction and starts another transaction, inserting into exceptions tables. If the insert into exceptions table transaction fails, the adapter then logs the message to the opaque exceptions table.
An opaque exceptions table has the following columns:
You can configure several Subscription Service services in the ADB_SUBTAB column by using only one opaque exceptions table in the same database schema.