Normally you would store in BLOB, then you don’t have the 32K limit.
From: oracle-l-bounce@xxxxxxxxxxxxx <oracle-l-bounce@xxxxxxxxxxxxx> On Behalf
Of Andrew Kerber
Sent: Friday, March 26, 2021 6:33 AM
To: ORACLE-L <oracle-l@xxxxxxxxxxxxx>
Subject: Problem with JSON in Oracle
I really dont know much at all about JSON, though we have a group that is using
that format to store data in CLOBs in the database. They are running into a
problem that seems to be a hard oracle limit.
They have a bunch of JSON CLOBs larger than 32k. I havent asked them how they
created them, But anyway, they are using a stored procedure called
JSON_ELEMENT_T.PARSE. And they are getting a parse error whenever they try to
parse a json document larger than 32k. Looking at the documentation for JSON,
its pretty clear they are hitting a hard string length limit of 32k.
They tried to tell me its an Oracle bug, but reading through the documentation,
I can see that this 32k string size limit is pretty well documented. In any
case, does anyone know of a way around this? My suggestion was to pull out the
JSON in 32k chunks and assemble it in a language that can deal with JSON larger
than 32k.
--
Andrew W. Kerber
'If at first you dont succeed, dont take up skydiving.'
