Re: Looking for null byte (0x0) characters in triggers

From: Tim Gorman <tim_at_evdbt.com>
Date: Fri, 6 May 2016 09:34:53 -0600
Message-ID: <e8eb5019-38e1-adc9-a3c0-8e4adefc142e_at_evdbt.com>



I don't believe DBA_SOURCE contains TRIGGER_BODY text.

DBMS_METADATA_UTIL looks interesting, thanks!

On 5/6/16 09:23, Yong Huang (Redacted sender yong321 for DMARC) wrote:
>> One thing I've done copy dba_triggers to a temp table, converting the
>> trigger_body to a lob and then using dbms_lob.instr(trigger_body,chr(0))
>> to try to find them.
> Hi Don,
>
> Why not get the code from dba_source, where the text column is varchar2 instead of long?
>
> In case you must use LONG (not in this case unless you can't use dba_source), you can also consider the undocumented dbms_metadata_util package, which has the long2clob function. It's convenient, but of course it's undocumented.
>
> Yong Huang
>
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>
>

--
http://www.freelists.org/webpage/oracle-l
Received on Fri May 06 2016 - 17:34:53 CEST

Original text of this message