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 1hxu3C-0007in-8Q for pgsql-general@arkaria.postgresql.org; Wed, 14 Aug 2019 14:14:54 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hxu2C-0000kN-Et for pgsql-general@arkaria.postgresql.org; Wed, 14 Aug 2019 14:13: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 1hxu2A-0000be-Ej for pgsql-general@lists.postgresql.org; Wed, 14 Aug 2019 14:13:52 +0000 Received: from out4-smtp.messagingengine.com ([66.111.4.28]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from ) id 1hxu27-0000kJ-4E for pgsql-general@lists.postgresql.org; Wed, 14 Aug 2019 14:13:49 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id E830921E44; Wed, 14 Aug 2019 10:13:45 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Wed, 14 Aug 2019 10:13:45 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= subject:to:cc:references:from:message-id:date:mime-version :in-reply-to:content-type:content-transfer-encoding; s=fm3; bh=+ aNuqttDB7AoA0dEBic15RoUCrnCBJrLRDUAzZtN4LY=; b=uzV1YQ1PGAVAg76RJ 7FAUgZ7VTn4muBWcxRRkIrPFQknwu6HDzVcuT7lOCkyvvcQXfE9fvPM61izBKYzA h8IIZ7CeJmQamLl87rVIsE7VabaifYZmNnYTsM/kkjbhg0MEYI4RAZ3gGzDIzpOB fEEtADDloO95P55xL/Mq6xQMFAfsXWqTcZ2vZdfCEDpL7MqKChaBXUK+5FZ1Gdgk lmqt+NPdh0A4Iry7hM/wiRNmncl2njsof5GeR9R+46EmvRaNfDkgwqBYSooNKVR4 xOMPDx1eFZRY/uKK7bvRShXrbiiEBtY8ClDQzkshprH+ij81JBaqFKA4IUvVfyR6 NZU/A== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=+aNuqttDB7AoA0dEBic15RoUCrnCBJrLRDUAzZtN4 LY=; b=goYIIaiG7fBbh7Pv+vxN9bSQmotMf67yVQKen87qbAmupcmkzaByTeDhi q9EiGDmRMDr/jvaVk3EuJZxlNQ90zhNDPQ2KmHfuyqNJSTPFysK9otfEetd6A4Eq wv9Cdr9wiFPuR1/bLM9X7n/0s6M6vzs+uCElZT2WGAxDD6m3+3fUXZex23dx8VGC q6DLe7fvJ/+1nYqBFeyVo9opNtVcOHizbUxZ6X15X6aAIkL/aWn234pwgR43iBon G6ERy0y5q5uCLSHxaLlaCuf9LQ4fwpiICkev9s+Yoe6LQVWcofQcWCTr2UmJU8VJ tnw4s24Fi5JCUD/XiQP5DIho5wZ7A== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddruddvledguddvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepuffvfhfhkffffgggjggtgfesthejredttdefjeenucfhrhhomheptegurhhi rghnucfmlhgrvhgvrhcuoegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtoh hmqeenucffohhmrghinhepghhithhhuhgsrdgtohhmnecukfhppeejuddrvdduvddrudeh tddrvddtvdenucfrrghrrghmpehmrghilhhfrhhomheprggurhhirghnrdhklhgrvhgvrh esrghklhgrvhgvrhdrtghomhenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from [192.168.1.4] (unknown [71.212.150.202]) by mail.messagingengine.com (Postfix) with ESMTPA id C306A380084; Wed, 14 Aug 2019 10:13:44 -0400 (EDT) Subject: Re: ORA-24345: A Truncation or null fetch error occurred -ora2pg To: Daulat Ram , Luca Ferrari Cc: "pgsql-general@lists.postgresql.org" References: <17a34583-7035-056f-2cea-6d4d6e105593@aklaver.com> From: Adrian Klaver Message-ID: <8ab0597a-d464-ade7-857b-727135ee874a@aklaver.com> Date: Wed, 14 Aug 2019 07:13:43 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 8/14/19 2:39 AM, Daulat Ram wrote: > Hi Adrian , > > We have the below output. What we need to change. I am not an ora2pg user so I don't know what to suggest for below. I would say the best thing to do would be to file an issue here: https://github.com/darold/ora2pg/issues Along with the original error message include the below and the settings, if any, for NLS_*, CLIENT_ENCODING from your ora2pg.conf file. > > bash-4.2$ ora2pg -c ora2pg.bidder.conf -t SHOW_ENCODING > > Current encoding settings that will be used by Ora2Pg: > Oracle NLS_LANG AMERICAN_AMERICA.AL32UTF8 > Oracle NLS_NCHAR AL32UTF8 > Oracle NLS_TIMESTAMP_FORMAT YYYY-MM-DD HH24:MI:SS.FF6 > Oracle NLS_DATE_FORMAT YYYY-MM-DD HH24:MI:SS > PostgreSQL CLIENT_ENCODING UTF8 > Perl output encoding '' > Showing current Oracle encoding and possible PostgreSQL client encoding: > Oracle NLS_LANG AMERICAN_AMERICA.WE8MSWIN1252 > Oracle NLS_NCHAR WE8MSWIN1252 > Oracle NLS_TIMESTAMP_FORMAT YYYY-MM-DD HH24:MI:SS.FF6 > Oracle NLS_DATE_FORMAT YYYY-MM-DD HH24:MI:SS > PostgreSQL CLIENT_ENCODING WIN1252 > bash-4.2$ > > thanks -- Adrian Klaver adrian.klaver@aklaver.com