He was probably inferring to that there were a lot of bugs that are 12.1 only
bugs relative to extended Datatypes.
From: Jeff Chirco <backseatdba@xxxxxxxxx>
Sent: Thursday, October 31, 2019 7:14 AM
To: Jared Still <jkstill@xxxxxxxxx>
Cc: Dimensional DBA <dimensional.dba@xxxxxxxxxxx>; oracle-l-freelist
<oracle-l@xxxxxxxxxxxxx>
Subject: Re: Extended Data types
Hey Jared I am not sure what that is in reference to?
On Wed, Oct 30, 2019 at 4:57 PM Jared Still <jkstill@xxxxxxxxx
<mailto:jkstill@xxxxxxxxx> > wrote:
ahem.. 12.1 ... nuf said
On Wed, Oct 30, 2019 at 08:16 <dimensional.dba@xxxxxxxxxxx
<mailto:dimensional.dba@xxxxxxxxxxx> > wrote:
I have changed many client databases on request to use extended datatypes and
experienced no problems at all.
However if you search in oracle support you will find lots of varying errors,
most related to 12.1 only but some more generic.
Here are few:
XDB Invalid after Utlrp during Activation of Extended Datatypes (Doc ID
1667689.1)
Database Won't Start After Varchar2(32k) Upgrade (Doc ID 1610329.1)
ORA-00600 [koklismem2: Insufficient Locator Len] on Update of Extended Data
types. (Doc ID 2474129.1)
ORA-01467 In Oracle 12c when max_string_size is Extended Data Types used (Doc
ID 2022269.1)
From: oracle-l-bounce@xxxxxxxxxxxxx <mailto:oracle-l-bounce@xxxxxxxxxxxxx>
<oracle-l-bounce@xxxxxxxxxxxxx <mailto:oracle-l-bounce@xxxxxxxxxxxxx> > On
Behalf Of Jeff Chirco
Sent: Tuesday, October 29, 2019 9:05 AM
To: oracle-l-freelist <oracle-l@xxxxxxxxxxxxx <mailto:oracle-l@xxxxxxxxxxxxx> >
Subject: Extended Data types
Hi all,
Has anyone enabled extended data types in 12c to get varchar2(32767) support
for the tables? We are looking to do this but wondering if anyone has
experienced any issues with it cause I know there is no going back once you do.
Thanks,
Jeff
--
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist
Principal Consultant at Pythian
Pythian Blog http://www.pythian.com/blog/author/still/
Github: https://github.com/jkstill
