Issue:
Unable to create a new field or import a .def file on the
AST:Attribute form on Remedy 9.1.03.
Error message:
The SQL database operation failed:
org.springframework.orm.jpa.JpaSystemException: Exception
[EclipseLink-4002]
(Eclipse Persistence Services - 2.4.2v20130514-5956486):
org.eclipse.persistence.exceptions.DatabaseException
Internal Exception:
java.sql.SQLIntegrityConstraintViolationExcep.
History:
The AST:Attributes has been overlayed. Per the FIELD table count
there are 62 custom/overlayed fields on the form.
The system has been upgrade from 8.1 to 9.1.03. In 8.1, there were no
issues in manually creating fields or importing .def file on
AST:Attributes. Issue started to occur after the 9.1.03 upgrade.
Symptoms:
* Unable to import .def file or create a custom field
* Getting the above “SQL constraint violation” error
* Despite the error, the “Alter Table Add Column” is running. On
the corresponding T table a new column. C[database id of new field],
has been added.
* The metadata tables (e.g. FIELD, arschema, field_char, etc…) are
not being updated.
Weird Occurrence:
While running API logs, we can see the exact table (FIELD) and values
that are causing the unique constraint violation. Weird – when we
run the test again (add a new field to the form), the same unique
constraint on the FIELD table is violated, BUT the field name has
changed. If you run the test 5 different times then you will get 5
different existing fields trying to reinsert back into the FIELD
table. Note: the unique constraint on the FIELD table is on schemaid,
fieldid, and overlaygroup. Every field that it’s trying to reinsert
is a custom field on the overlay. It just seems that Remedy is
ignoring existing custom fields. On save, it is treating these custom
fields as new and trying to reinsert the custom field’s data back
into the metadata tables; causing the unique key violation.
Additionally, were are not seeing any “Alter Table Add Column”
errors in the SQL log. If Dev Studio/Remedy were actually treating
these exiting fields as “new” then we would be getting “alter
table” errors as it tries to add the same column to a table that
already has the column. It seems the issue is isolated to workflow
that is updating the metadata tables.
--
ARSList mailing list
ARSList@arslist.org
https://mailman.rrr.se/cgi/listinfo/arslist
