Error: "maximum of 100 recorded errors reached" in the errlog.sql file.
This is an informational message only and is not an error.
"maximum of 100 recorded errors reached" indicates that a 100 errors in a session have been encountered in the errlog.sql file.
A session is defined as SQL statements between commits.
For example:
If you run an update for 500 records and then commit - that's 1 session.
If you run another update for 4000 records and then commit - that's another session.
If a 500 record update generates 500 OOS messages then only the first 100 messages will be written to the errlog.sql file. The remaining 400 records will be discarded to conserve resources.
The above example refers to the way messages are displayed in the errlog.sql file,
It does not impact the actual data replicated to the Target database.
You can control how many messages per session will be written to errlog.sql by using the SP_OPO_NERR_MAX parameter on Target.
You can use the parameter to increase or decrease the number of messages written to the errlog.sql file per session.
There is no way to set it to unlimited and you must set it to a specific value.
The default is 100 and it is a live parameter.
