Changing a CLOB to a Varchar2

Hi Experts,

I have a situation where we have a CLOB when it should have been a varchar2(4000). We know that no data exceeds 4000 characters and want to convert the datatype.

I have created a new column of type Varchar2(4000 CHAR) successfully.
When I try and update the table to set the new column I get a constraint error and it is talking about deleting data

My code is

      ALTER TABLE XXX ADD TITLE_VAR VARCHAR2(4000 CHAR);
     
      UPDATEXXX SET TITLE_VAR = SUBSTR (TITLE, 1, 4000);
     
      ALTER TABLE XXX DROP COLUMN TITLE;
     
      ALTER TABLE XXX RENAME COLUMN TITLE_VAR TO TITLE;

The 1st line executes correctly, the second line however gives the following

SQL Error: ORA-02292: integrity constraint (AQD.FK_QACKLISTRES_QACKLISTITM) violated - child record found
02292. 00000 - "integrity constraint (%s.%s) violated - child record found"
*Cause:    attempted to delete a parent key value that had a foreign
           dependency.
*Action:   delete dependencies first then parent or disable constraint.

The foreign key being referred to is the primary key for this table being referenced by another table. The old and new columns being changed are not part of any relationship.

This error makes me think that Oracle is deleting the table and recreating - I can't think of any reason for this error.

It just doesn't make sense. The version of Oracle is 11.2.0.4 Enterprise with the code being run through SQL Developer.

I can't find any reference to this in any material anywhere. The solution I am using is widely quoted.

Does anyone have any ideas?

Kelvin
LVL 23
Kelvin SparksAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Wasim Akram ShaikCommented:
Cannot recreate your scenario, but have you given a try using dbms_redefinition package and sync the tables?, this should work without any errors, use primary key as it seems you already have one on your table..

For Sample illustrations of how to use dbms_redefinition, check burleson site..

http://www.dba-oracle.com/t_dbms_redefinition_example.htm
0
johnsoneSenior Oracle DBACommented:
My guess would be a trigger, or a constraint that was created with ENABLE NO VALIDATE.

I would check for triggers first.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Kelvin SparksAuthor Commented:
Thanks Johnsone

All it took was a fresh approach when the problem  caused me to become tunnel visioned. A trigger was the culprit - you just don't fire a trigger for a sequence on update! Not sure how this got in - and is a rarely updated table.

Thanks for the fresh view!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Oracle Database

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.