One Error Was Found. Fix This Error and Save Again. An Unknown Error Has Occurred.
Troubleshooting
Problem
A user may meet an unknown error message when attempting to relieve a record in one or many applications after a Database Configuration (configdb) has been completed.
Symptom
The following message will exist displayed to the users.
The below (shortened) error will be logged to the System Log file at the time the user clicks Salve.
[Fault] java.lang.NullPointerException
java.lang.NullPointerException
at psdi.mbo.MboSet.eAuditMbo(MboSet.java:10101)
at psdi.mbo.MboSet.saveTransaction(MboSet.java:6524)
at psdi.txn.MXTransactionImpl.saveTransaction(MXTransactionImpl.coffee:227)
at psdi.txn.MXTransactionImpl.salve(MXTransactionImpl.java:162)
at psdi.mbo.MboSet.relieve(MboSet.java:6329)
at psdi.mbo.MboSet.save(MboSet.java:6286)
at psdi.webclient.system.beans.AppBean.salvage(AppBean.java:506)
at psdi.webclient.system.beans.AppBean.SAVE(AppBean.java:815)
at psdi.webclient.beans.workorder.WOAppBean.SAVE(WOAppBean.java:575)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Cause
This trouble occurs when Electronic Audit (eAudit) is enabled on a database object, all the same the Application uses a database View to read and write records to the database. When a tape is saved, Maximo attempts to write an Audit record to the eAudit objects associated with the Awarding. Since at that place are multiple objects in the View just only ane object is eAudit enabled the Naught mistake is thrown as no Audit tables be for the other objects in the View.
Diagnosing The Trouble
To properly diagnose this consequence, verify that the in a higher place fault is written to the System Log when a transaction is saved. Audit tables are created when eAudit is enabled on a Maximo database Object via the Database Configuration awarding and a ConfigDB is executed.
Resolving The Trouble
In that location are a number of ways to resolve this issue:
1. Turn off eAudit via the Database Configuration application on the offending Object. Run ConfigDB to apply the change.
ii. Turn on eAudit for all other Maximo objects included in the database View.
3. Manually remove the Audit tables and re-add using Client-created SQL Scripts. (Non Recommended or Supported past IBM Support)
IBM has recorded this issue as APAR IZ53085 and has been fixed in Maximo Base Services Fix Pack 7.i.i.five. This APAR does not resolve the problem every bit it only clarifies the mistake bulletin that is logged to the log file and is displayed to users saving records.
[{"Product":{"code":"SSLKT6","label":"IBM Maximo Nugget Direction"},"Business Unit":{"code":"BU055","characterization":"Cognitive Applications"},"Component":"east-Audit","Platform":[{"code":"PF002","characterization":"AIX"},{"code":"PF010","characterization":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"7.1;7.1.1;seven.2","Edition":"All Editions","Line of Business":{"code":"LOB02","characterization":"AI Applications"}},{"Production":{"code":"SSWK4A","label":"Maximo Asset Management Essentials"},"Business organization Unit of measurement":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":" ","Platform":[{"lawmaking":"","label":""}],"Version":"","Edition":"","Line of Business":{"lawmaking":"LOB02","characterization":"AI Applications"}},{"Product":{"code":"SSLKTY","characterization":"Maximo Asset Management for It"},"Business Unit":{"code":"BU053","characterization":"Cloud & Data Platform"},"Component":" ","Platform":[{"lawmaking":"","label":""}],"Version":"","Edition":"","Line of Business":{"code":"LOB02","characterization":"AI Applications"}},{"Product":{"lawmaking":"SSKTXT","label":"Tivoli Change and Configuration Management Database"},"Concern Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":" ","Platform":[{"code":"","label":""}],"Version":"","Edition":"","Line of Business":{"code":"LOB45","characterization":"Automation"}},{"Product":{"lawmaking":"SS6HJK","characterization":"Tivoli Service Request Manager"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":" ","Platform":[{"lawmaking":"","label":""}],"Version":"","Edition":"","Line of Business":{"lawmaking":"LOB45","label":"Automation"}}]
Source: https://www.ibm.com/support/pages/bmxaa4214e-unknown-error-has-occurred-null-after-save
Postar um comentário for "One Error Was Found. Fix This Error and Save Again. An Unknown Error Has Occurred."