Error log does not show actual DB error message
Posted: Mon Feb 25, 2019 3:55 am
The server job fails due to column length issue (target.table.column has length less than source.table.column) but log doesn't show the actual error message, only shows few column values of the row that failed. It happens also with unique constraint error.
Below is the error message while updating the target table:
J_PERSON_TEST..SRC_PS_PERSON_UPD.IDENT4: The value of the row is: PERSON_NBR = 1224 ETHNIC_ID = 0 PER_ID = 6286 PF_ID = 0 PLN_IND = - P_NM = abc FULL_IND = N
The execution order of the job looks something like this: MSEQ1>MSEQ2>SEQ>Server Job
All options under Severity Level in Administrator > Log Views have been checked but still have the same issue, not showing the actual DB error.
Is something needs to be done in the server job/administrator so that the log shows the complete/actual error message?
Below is the error message while updating the target table:
J_PERSON_TEST..SRC_PS_PERSON_UPD.IDENT4: The value of the row is: PERSON_NBR = 1224 ETHNIC_ID = 0 PER_ID = 6286 PF_ID = 0 PLN_IND = - P_NM = abc FULL_IND = N
The execution order of the job looks something like this: MSEQ1>MSEQ2>SEQ>Server Job
All options under Severity Level in Administrator > Log Views have been checked but still have the same issue, not showing the actual DB error.
Is something needs to be done in the server job/administrator so that the log shows the complete/actual error message?