Return-Path: X-Original-To: oracle-l@orafaq.com Delivered-To: oracle-l@orafaq.com Received: from puck1183.startdedicated.com (localhost [127.0.0.1]) by puck1183.startdedicated.com (Postfix) with ESMTP id E52581960596 for ; Thu, 5 May 2016 16:50:43 +0200 (CEST) Received: from turing.freelists.org (freelists-180.iquest.net [206.53.239.180]) by puck1183.startdedicated.com (Postfix) with ESMTPS for ; Thu, 5 May 2016 16:50:43 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 9D513389C2; Thu, 5 May 2016 10:50:42 -0400 (EDT) X-Virus-Scanned: Debian amavisd-new at turing.freelists.org Received: from turing.freelists.org ([127.0.0.1]) by localhost (turing.freelists.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bi15bw31UDYe; Thu, 5 May 2016 10:50:42 -0400 (EDT) Received: from turing.freelists.org (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 6F6DE389BB; Thu, 5 May 2016 10:50:30 -0400 (EDT) Received: with ECARTIS (v1.0.0; list oracle-l); Thu, 05 May 2016 10:49:08 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 2F5133899C for ; Thu, 5 May 2016 10:49:08 -0400 (EDT) Received: from turing.freelists.org ([127.0.0.1]) by localhost (turing.freelists.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z-yQBe0sUrJe for ; Thu, 5 May 2016 10:49:08 -0400 (EDT) Received: from mail-io0-f179.google.com (mail-io0-f179.google.com [209.85.223.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTPS id D744738998 for ; Thu, 5 May 2016 10:49:07 -0400 (EDT) Received: by mail-io0-f179.google.com with SMTP id d62so86529507iof.2 for ; Thu, 05 May 2016 07:49:07 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=kXEx0PtJzc2SyMRHYy9YXrXPDdO3xHxCyGL8gdJNwFM=; b=S740SjOW8Xg+dSuAKTJWjjRENEd8+rBV5loqKR37WxrCW3uJr5Kyrt9uZbXFRZ/XB7 7SxiNN8dLKlLUsgTvUEnrXqI43p5IxVnl9lKCBID1cEwRGxRaRZyyXujZjAMyoIku2Q/ vABbU3OdNsFsuH6glyBZdQvrQMiYvM3jW6SR344uHMqYGjqu+rBVWuzmjU86mqbC9YZt kQA+QChmV7UWCukFtypGrRyF4dsXXsLmCfbxSDE+TJ7EtHaEYUV7t2/cVzPBVSj9SEEB Zq54BwoKv+c9b+uwttAvQl5r+BldbF+i6g3umNQrokiAxa57CJ227WDUOuvkIHsx67yu 3kKw== X-Gm-Message-State: AOPr4FXCZQwgOwd5WoQ2R0vbNemTSLrFCdRYL9EMTXjKkh3AzvJVpnW386ZcfypgW0HxLtftgYXNegtzsmphkQ== X-Received: by 10.107.191.7 with SMTP id p7mr20036986iof.115.1462459747492; Thu, 05 May 2016 07:49:07 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.9.17 with HTTP; Thu, 5 May 2016 07:48:47 -0700 (PDT) In-Reply-To: References: From: Don Seiler Date: Thu, 5 May 2016 09:48:47 -0500 Message-ID: Subject: Re: Looking for null byte (0x0) characters in triggers To: Luis Santos Cc: ORACLE-L Content-Type: multipart/alternative; boundary=001a114f3648bf7f9e0532197143 X-archive-position: 64825 X-ecartis-version: Ecartis v1.0.0 Sender: oracle-l-bounce@freelists.org Errors-to: oracle-l-bounce@freelists.org X-original-sender: don@seiler.us Precedence: normal Reply-To: don@seiler.us List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: oracle-l X-List-ID: oracle-l List-subscribe: List-owner: List-post: List-archive: X-list: oracle-l --001a114f3648bf7f9e0532197143 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable My teammate did a PL/SQL block for the implicit conversion as opposed to my explicit conversion. Got the same results anyway. On Thu, May 5, 2016 at 9:27 AM, Luis Santos wrote: > I really don=C2=B4t have advice to you. I=C2=B4m replying just to say tha= t 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 : > >> 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 i= s >> right and our other DP trigger import errors are due to some oother reas= on, >> but I want to confirm that I'm not missing anything or there isn't a bet= ter >> way to search. >> >> Don. >> >> -- >> Don Seiler >> http://www.seiler.us >> > > --=20 Don Seiler http://www.seiler.us --001a114f3648bf7f9e0532197143 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
My teammate did a PL/SQL block for the implicit conversion= as opposed to my explicit conversion. Got the same results anyway.

On Thu, May 5, 2016= at 9:27 AM, Luis Santos <lsantos@pobox.com> wrote:
I = really don=C2=B4t have advice to you. I=C2=B4m 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


<= /font>
<= /div>

2016-05-05 10:41 GMT-03:00 Don Seiler <don@seil= er.us>:
Oracle 12.1.0.2 w/ Jan 2016 PSU, x86-64.

We're u= sing 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 t= hese triggers have null bytes in them somehow. However, rather than just do= ing 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 t= hing I've done copy dba_triggers to a temp table, converting the trigge= r_body to a lob and then using dbms_lob.instr(trigger_body,chr(0)) to try t= o 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 bet= ter way to search.

D= on.

--




--
Don Seiler
http://www.seiler.us
--001a114f3648bf7f9e0532197143-- -- http://www.freelists.org/webpage/oracle-l