Question & Answer
Question
Is there a workaround for serialization errors?
Answer
In NPS versions prior to 3.1, if two transactions attempt to modify the same data, the second transaction is rolled back, and an error similar to the following appears:
- ERROR: Could not serialize - transaction aborted
In NPS 3.1, Delete and Update transactions on the same table are queued.
In NPS 4.0, this error can occur if you wrap a BEGIN WORK command around the DELETE or UPDATE statements.
The recommended workaround is to enable a setting in the /nz/data/postgresql.conf file.
1. In a text editor, open the /nz/data/postgresql.conf file for editing.
2. Confirm that it contains the following line:
- serialization_queue_timeout = 30
3. Add the following line:
- begin_queue_if_full = true
[{"Product":{"code":"SSULQD","label":"IBM PureData System"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":null,"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"1.0.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Historical Number
NZ518656
Was this topic helpful?
Document Information
Modified date:
17 October 2019
UID
swg21575966