Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1grpaV-0007eG-Eo for pgsql-admin@arkaria.postgresql.org; Thu, 07 Feb 2019 19:43:56 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1grpaS-00081l-Vc for pgsql-admin@arkaria.postgresql.org; Thu, 07 Feb 2019 19:43:52 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1grpaS-00081e-Dn for pgsql-admin@lists.postgresql.org; Thu, 07 Feb 2019 19:43:52 +0000 Received: from sonic309-14.consmr.mail.bf2.yahoo.com ([74.6.129.124]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1grpaO-0001rx-Nn for pgsql-admin@lists.postgresql.org; Thu, 07 Feb 2019 19:43:51 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1549568626; bh=23/GT1G7aOHP5X0UA3WvJzIuWPVg2b3k7fGH9ye+A1U=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=rgX/rKoGDGHy132SE4eGsJS5lgP5drBk8supgDnvQa4O0c8VB633bBz4QfJz+OEWPDBjS4ytaD4K3ogFYpjA0yku94EeOoxIU+HFYk08QM6FnpS5M9vXg+yOMaZvSZZvDOovrYHp9hmE98QWK3Fj1uOrNuUw5hUbGshdmVxgfutISGJr77duYQnP/y/uVJb2/LmmC74A+XAzA0ycxEkRLc32F0b92a/JY+kJpLoQFR8wPxE1WdbdphJIeNRuulTJrtHCGMY7uV97nlScyJnCtDVAmgMjYELn+KKP8UaxocbPlNkGq5KpMWaq+jBxW1BhhW99Tno29Wz2Vcu8vF3Egg== X-YMail-OSG: 2AkJ9ZkVM1mH0ZL2fXASctny5k8RJSfFwjx9CSFBaaGIdzOGv2dkLP2YiSSk0Cn N.alw5UEG2a48jqVz3_XoyIZVTh5RRpD4jkRZxqw2oh6G5La2UaB2XB8PWrJNBPZWadnXO6DmS5k pVdZXkDaGGI4XaBUR.WMgTQlO7AD24.I6_Iv0seAhxYFYAe1tawCe9UrwO.os2XcZpnrIt24UZ2E uUjck3AkDDHH4qkGl8TCbSH6fp6WIMjhwmlPMDZgyXjFCvYwrKTloU6vTr_2M1UQEtb6h6zScGGm BGTbpoaz6szKZtbLci9BByYZkRzQ9Oak35J372RJK32qJ5qlKNDOKKwb5GUksl2gnJyTLRzzMTjQ Qv0Hf7fiFjSM8zl7ffpkysNVEo2e2shroqWCrLAaOjAH1UNwqGXBD_u6r6E9V4fvKe3Yb1R7xqMt JoSC2WOMEaW.sePSdBoQmz6XHqklVO9kLtF.02ZohFBb__boAXSLm54VP0zhSntYtFg398oEIBiL MhIgX0UZmHHsuHLlxGvCmeJ3MaH_VHxz.cQwCL_H1i4ol3wsDk.Zrnk3p70Ur4OTLoz4r6v5ymlU BGzKO8C0zVOA1tjnacbPHQBR3J2.SfAOVZm.Y6sCzyld6IuD8h9TXWPNVe9GaP5I4C8rVDDBOfdG YQbWTT8RwHKbRMYGdBkADDPauhsVwk_Z58wviywfp2X2Fe4Yvi7oYuub6ry3JHnYogtxJktElTc7 nf3DI.as_pTakkOksmAWSTV2DDaqWQbAXpMrmZ2u1N7FBaFmzGBl58pFc2YCyf1O8_4GnntrlHuf GqJgQCVLBixMRFC3Xn0bntyWOSCrRdgBtYiJ3Eyhfb.1qvdTGjj1_96evzIqV5qQcSVCaSGlqn7. mGik3OgLOXzJrSlfA1vZ.bj3_RbX1auWO0H.4Ec1.ukD4CYOSAYIleo0JK1UyWJXNxmWl3jvV82q TBJuwkYwp8KEx0mm_.uEDJfAL7hkPmcQ6Dy6zJkk0dZKREjlzp1ySYCB9xm3AGvP82Gqh.XNcC_u J6soBS2xI6a1v9sUbLJEU3NQ1Br_TaKsYTi19wWZ8xsCl7Id1ttOHywcegtjl90BR1hExDYvYvKc - Received: from sonic.gate.mail.ne1.yahoo.com by sonic309.consmr.mail.bf2.yahoo.com with HTTP; Thu, 7 Feb 2019 19:43:46 +0000 Date: Thu, 7 Feb 2019 19:43:43 +0000 (UTC) From: Pepe TD Vo Reply-To: Pepe TD Vo To: Pepe TD Vo , "David G. Johnston" Cc: Pgsql-admin Message-ID: <979487675.4817021.1549568623947@mail.yahoo.com> In-Reply-To: <722258958.4166300.1549483147294@mail.yahoo.com> References: <722258958.4166300.1549483147294.ref@mail.yahoo.com> <722258958.4166300.1549483147294@mail.yahoo.com> Subject: Re: insert aborted commands ignored MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_4817020_14811183.1549568623944" X-Mailer: WebService/1.1.13027 YahooMailNeo Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 Content-Length: 15681 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk ------=_Part_4817020_14811183.1549568623944 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Mr. Johnston, for the error, "value too long for type character varying(34)thank you for = your information.=C2=A0 I resolved the problem.=C2=A0 v.r, Bach-Nga No one in this world is pure and perfect.=C2=A0 If you avoid people for the= ir mistakes you will be alone. So judge less, love and forgive more.To call= him a dog hardly seems to do him justice though in as much as he had four = legs, a tail, and barked, I admit he was, to all outward appearances. But t= o those who knew him well, he was a perfect gentleman (Hermione Gingold) **Live simply **Love generously **Care deeply **Speak kindly.*** Genuinely = rich *** Faithful talent *** Sharing success=20 On Wednesday, February 6, 2019 2:59 PM, Pepe TD Vo w= rote: =20 Thank you sir, I have tried one by one to show create table back and found a few fields wi= th=C2=A0character varying(34) and I don't know exactly which one failed.=C2= =A0 =C2=A0The data type was right from Oracle and count the characters on t= he insert script was fine.=C2=A0 The target column names listed in order bu= t the values supplied by the values are associated with the explicit or imp= licit column list left to right=C2=A0 and I need to check one by one column= and see what they are.=C2=A0 The problems are so many and the more I query= , psql hung and I needed to ctrl C to get out from psql and get back in. I am checking one by one table insert row now.=C2=A0 I need to pull all ins= ert of each table out first and see if insert ok and so far it's ok.=C2=A0 = With your information I will check back and increase the values (n) and see= the insert work or not, since the insert script was 20Gb and it will stop = running as soon as the error kick in.=C2=A0 Even without setting "-v ON_ERR= OR_STOP=3D1=C2=A0".=C2=A0 The 1st 200 insert lines are ok from the psql pro= mpt but stop insert if I running psql -U postgres -d CIDR < insert_cidrdba.= sql > insert_cidrdba.txt.=C2=A0 I am inserting one by one from psql now.=C2= =A0 Hope to find where the error occurs. thank you for your input again. v/r, Bach-Nga No one in this world is pure and perfect.=C2=A0 If you avoid people for the= ir mistakes you will be alone. So judge less, love and forgive more.To call= him a dog hardly seems to do him justice though in as much as he had four = legs, a tail, and barked, I admit he was, to all outward appearances. But t= o those who knew him well, he was a perfect gentleman (Hermione Gingold) **Live simply **Love generously **Care deeply **Speak kindly.*** Genuinely = rich *** Faithful talent *** Sharing success=20 On Wednesday, February 6, 2019 10:18 AM, David G. Johnston wrote: =20 On Wed, Feb 6, 2019 at 8:05 AM Pepe TD Vo wrote: >=C2=A0 get another error, "value too long for type character varying(34).= =C2=A0 How do I know which table How many tables in your schema are defined with a column having a type of "character varying(34)"? To narrow down if >1 you'd need to trace the load script and see at what point it is failing; or change half of them to "text", try again, change some back to varchar(34), try again repeat until only one of them is "text" and that is your culprit. Or just get rid of "varchar(n)" columns, make them all text and, for those were you really want to keep length limits, add explicit constraints. There have been discussions somewhat recently to make the error message itself more helpful but I don't believe anyone is actively working on it.=C2=A0 Its better, IMO, to avoid using "varchar(n)" in your schema anyway.=C2=A0 More precise check constraints are a better option not the least of which is because they can be named and self-identify with the table to which they are attached. David J. =20 =20 ------=_Part_4817020_14811183.1549568623944 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Mr. Johnston,

for the error, "value too long for type character varying(3= 4)thank you for your info= rmation.  I resolved the problem. 

v.r,

Bach-Nga

No one in this world = is pure and perfect.  If you avoid people for their mistakes you will = be alone. So judge less, love and forgive more.
<= div id=3D"yui_3_13_0_rc_1_1_1381789421038_7874" class=3D"yiv3811552299ms__i= d13893">To ca= ll him a dog hardly seems to do him justice though in as much as he had fou= r legs, a tail, and barked, I admit he was, to all outward appearances. But= to those who knew him well, he was a perfect gentleman (Hermione Gingold)<= /font>

**Live simply **Love = generously **Care deeply **Speak kindly.
*** Genuinely rich = *** Faithful talent *** Sharing success


On Wednesday, February 6, 2019 2:59 = PM, Pepe TD Vo <pepevo@yahoo.com> wrote:


<= div class=3D"y_msg_container">
Thank you sir,

I have tried one by one to show create table back and = found a few fields with character varying(34) and I don't know exactly which= one failed.   The data type was right from Oracle and count the = characters on the insert script was fine.  The target column names lis= ted in order but the values supplied by the values are associated with the = explicit or implicit column list left to right  and I need to check on= e by one column and see what they are.  The problems are so many and t= he more I query, psql hung and I needed to ctrl C to get out from psql and = get back in.

I am checking one = by one table insert row now.  I need to pull all insert of each table = out first and see if insert ok and so far it's ok.  With your informat= ion I will check back and increase the values (n) and see the insert work o= r not, since the insert script was 20Gb and it will stop running as soon as= the error kick in.  Even without setting "-v ON_ERROR_STOP=3D1 ".&nb= sp; The 1st 200 insert lines are ok from the psql prompt but stop insert if= I running psql -U postgres -d CIDR < insert_cidrdba.sql > insert_cid= rdba.txt.  I am inserting one by one from psql now.  Hope to find= where the error occurs.

thank you for your input again.

v/r,

<= /span>
Bach-Nga

No one in this world= is pure and perfect.  If you avoid people for their mistakes you will= be alone. So judge less, love and forgive more.
=
To call him a dog har= dly seems to do him justice though in as much as he had four legs, a tail, = and barked, I admit he was, to all outward appearances. But to those who kn= ew him well, he was a perfect gentleman (Hermione Gingold)

**Live simply **Love gen= erously **Care deeply **Speak kindly.
*** Genuinely rich *** Faithful talent *** Sharing success=


On Wednesday, = February 6, 2019 10:18 AM, David G. Johnston <david.g.johnston@gmail.com= > wrote:


On = Wed, Feb 6, 2019 at 8:05 AM Pepe TD Vo <pepevo@yahoo.com> wrote:

>  g= et another error, "value too long for type character varying(34).  How= do I know which table


How many = tables in your schema are defined with a column having a type
of "character varying(34)"?

To na= rrow down if >1 you'd need to trace the load script and see at
what point it is failing; or change half of them to "text", try a= gain,
change some back to varchar(34), try again repeat u= ntil only one of
them is "text" and that is your culprit.=

Or just get rid of "varchar(n)" colum= ns, make them all text and, for
those were you really wan= t to keep length limits, add explicit
constraints.

There have been discussions somewhat recentl= y to make the error
message itself more helpful but I don= 't believe anyone is actively
working on it.  Its be= tter, IMO, to avoid using "varchar(n)" in your
schema any= way.  More precise check constraints are a better option not
the least of which is because they can be named and self-identify= with
the table to which they are attached.

David J.




=
------=_Part_4817020_14811183.1549568623944--