Hello Jack,
We have a COTS application that generates DML but is violating various table
constraints. We can't nail down the SQL or the rows it's trying to affect. We
can't edit the DML to add the "Log Errors..." line, so I was trying to figure
out a way to do it dynamically.
Jack Applewhite <jack.applewhite@xxxxxxxxxxxxx> hat am 12. September 2017 um--
23:04 geschrieben:
I use DBMS_ErrLog to create logging tables a LOT and really like this feature
for troubleshooting SQL. It works only if you can add the "Log Errors ..."
line at the end of your DML statement. We have a COTS application that
generates DML but is violating various table constraints. We can't nail down
the SQL or the rows it's trying to affect. We can't edit the DML to add the
"Log Errors..." line, so I was trying to figure out a way to do it
dynamically.
Just now I tried using VPD to add a predicate to any DML on a table and
sneakily tack on the "Log Errors..." line. The policy function returns this
for the predicate.
' 1=1 Log Errors Into Reject Limit Unlimited '
I thought that, since the "Log Errors..." line is always tacked on the end of
the SQL, this might work. The function compiled and I created the policy,
both in Sys. When I ran an Insert that I knew would violate a table
constraint I got this error.
SQL Error: ORA-28113: policy predicate has error
28113. 00000 - "policy predicate has error"
*Cause: Policy function generates invalid predicate.
*Action: Review the trace file for detailed error information.
I found the trace file in bdump and saw that VPD adds the Where, then
encloses the predicate text in parentheses:
Insert .... WHERE (1 = 1 Log Errors Into Reject Limit Unlimited)
ORA-00907: missing right parenthesis
Anyone know of a trick to get around this or other method to dynamically add
the "Log Errors..." line?
Thanks.
