Error received in the errlog.sql file:
"maximum of 100 recorded errors reached"
This is an informational message only, not an error.
--maximum of 100 recorded errors reached, means that a maximum of 100 errors in a session will be shown in the errlog.sql log 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 one session. You run another update for 4000 records and then commit, that's another session. If a 500 record update generates 500 out of sync messages then only the 1st 100 error messages out of 500 will be written in the log file. The other 400 records will not be written in the file. This is done in order to conserve resources.
The above message only refers to the way errlog.sql will be populated, it does not impact the actual data written to the database. So there is nothing to "fix" because nothing is broken. You can change how many messages per session will be written to errlog.sql by using param SP_OPO_NERR_MAX, which is supported in 5.3. You can use this parameter to increase/decrease the number of error messages written to the errlog per session. There is no way to set it to unlimited, you must set it to some specific value.