pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-general@lists.postgresql.org
Subject: Re: org.postgresql.util.PSQLException: ERROR: invalid XML content. Huge Input lookup
Date: Thu, 3 Aug 2023 23:53:46 -0500
Message-ID: <ab77ff9a-f416-31d0-c300-b68a63bdfaea@gmail.com> (raw)
In-Reply-To: <CADBXDMVOYBTeHZ81B0d+M-TwCDn_ovoaYgk4_4XRn2UPqgkj4A@mail.gmail.com>
References: <CADBXDMV_D3pBaSA5ZfUWnQP42ZO1YsbP9GZv8t1FncdGTiLMug@mail.gmail.com>
	<30d2d7d1-47c2-386c-2ee3-06b338f1c7b3@gmail.com>
	<CADBXDMVOYBTeHZ81B0d+M-TwCDn_ovoaYgk4_4XRn2UPqgkj4A@mail.gmail.com>

I would install 14.7 on your Windows box (multiversioning /is/ supported, at 
least on Linux; probably Windows too), making sure that it uses the 
en_US.utf_8 locale (or the closest Windows analog). *Then* I'd try the same 
migration on the Windows box.

After all development boxes should run the same software version as 
production...

On 8/3/23 22:46, Sai Teja wrote:
> Thank you for the reply.
>
> The pg version is 14.7 (Azure DB)
> Locale :-
> LC_COLLATE & LC_CTYPE : en_US.utf_8
>
> Local postgreSQL:- Version:- (15.1-1-windows-x64-binaries)
>
> LC_COLLATE & LC_CTYPE:-
> English_United States.1252
>
> Please let me know if any other information is needed.
>
> Thanks & Best Regards,
> Sai Teja
>
>
>
>
>
>
> On Fri, 4 Aug, 2023, 8:03 am Ron, <ronljohnsonjr@gmail.com> wrote:
>
>     On 8/3/23 21:22, Sai Teja wrote:
>>     Hi team,
>>
>>     I am trying to migrate the data from db2 to postgreSQL in which one
>>     of the table is having XML data.
>>     For one of the file (13MB) I'm facing an error with
>>
>>     ERROR: invalid XML content
>>     Detail: line 418061: internal error: Huge input lookup
>>     nested exception is org.postgresql.util.PSQLException: ERROR: invalid
>>     XML content
>>
>>     I even tried with more size of XML data (30MB) but for this case I
>>     can able to migrate the date successfully.
>>
>>     But only for that file I'm facing the issue.
>>     Later, I got to know that there are some special characters in that
>>     file not sure whether this can be the issue or not.
>>
>>     I'm using java.sql.preparedstatement
>>     Preparedstatement.setSQLXML(iterator, xmlobject) to migrate the data
>>     from db2 to postgreSQL
>>     When I tried in my local postgreSQL (which is *windows* and located
>>     in *APAC* region. I can able to migrate successfully)
>>     But when I'm trying to migrate into *azure* postgreSQL (Linux OS,
>>     located in *Germany*) facing an issue.
>
>     That sounds like it has to do with locale differences between the two
>     systems.
>
>     *Exactly* what Pg version (including patch level) and locale are in
>     each of the two systems?
>
>     Even if it's not that, *something* is configured differently between
>     the two systems.
>
>     -- 
>     Born in Arizona, moved to Babylonia.
>

-- 
Born in Arizona, moved to Babylonia.

view thread (11+ messages)

Message-ID: <ab77ff9a-f416-31d0-c300-b68a63bdfaea@gmail.com>
Permalink:  ../ab77ff9a-f416-31d0-c300-b68a63bdfaea@gmail.com/
Also on:    postgresql.org/message-id/ab77ff9a-f416-31d0-c300-b68a63bdfaea@gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: ronljohnsonjr@gmail.com
  Subject: Re: org.postgresql.util.PSQLException: ERROR: invalid XML content. Huge Input lookup
  In-Reply-To: <ab77ff9a-f416-31d0-c300-b68a63bdfaea@gmail.com>
  References: <CADBXDMV_D3pBaSA5ZfUWnQP42ZO1YsbP9GZv8t1FncdGTiLMug@mail.gmail.com> <30d2d7d1-47c2-386c-2ee3-06b338f1c7b3@gmail.com> <CADBXDMVOYBTeHZ81B0d+M-TwCDn_ovoaYgk4_4XRn2UPqgkj4A@mail.gmail.com> <ab77ff9a-f416-31d0-c300-b68a63bdfaea@gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox