Re: Looking for null byte (0x0) characters in triggers
Date: Thu, 5 May 2016 11:27:02 -0300
Message-ID: <CAPWdmV8ahC=AoZQBBD_2Z7i7MJxVxWx9xgL7pAtG=t9Gk6N1kw_at_mail.gmail.com>
I really don´t have advice to you. I´m replying just to say that I loved your technique! Copying dba_triggers to a temp table and convert the trigger_body to a LOB to make it searchable was a great idea!
*--*
*Att*
*Luis Santos*
2016-05-05 10:41 GMT-03:00 Don Seiler <don_at_seiler.us>:
> Oracle 12.1.0.2 w/ Jan 2016 PSU, x86-64.
>
> We're using the datapump API to import objects from one DB to another.
> However we occasionally hit the error described in DocID 1628926.1. It
> seems some of these triggers have null bytes in them somehow. However,
> rather than just doing trial and error to find them one-at-a-time as we hit
> them, I'd like just search for the ones that have the null byte.
>
> 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. However that only returned one trigger. Perhaps that is
> right and our other DP trigger import errors are due to some oother reason,
> but I want to confirm that I'm not missing anything or there isn't a better
> way to search.
>
> Don.
>
> --
> Don Seiler
> http://www.seiler.us
>
-- http://www.freelists.org/webpage/oracle-lReceived on Thu May 05 2016 - 16:27:02 CEST