Updating clob column

Posted by / 18-Jul-2017 10:14

If I do convert the varchar2 into a lob though, I would have to make some changes to the dependent stored procedures wouldn't I?

I'm trying to create a tiny test here to see what that would entail. Thank you so much, Chandini June 10, 2009 - pm UTC the stored procedures will work with up to 32k of data - beyond that, and they will need to change since the longest string in plsql is 32k.

The significance of the “fixed size” payload is that the payload can be modified in place if the pointer to a LOB chunk has to be changed – and this minimises disruption of the index (at a cost of some wasted space).

Asked: June 09, 2009 - am UTC Answered by: Tom Kyte - Last updated: September 23, 2013 - pm UTC Category: Database - Version: 10g Viewed 50K times!

The size of the single CLOB is roughly 365KB (or about 45 blocks of 8KB).' Extra line Commit; update t set y = null; commit; alter table t modify y long; alter table t modify y clob; update t set y = y_copy; ' Definitely need a commit Commit; alter table t drop column y_copy; alter table t drop column y; Table altered.is "safe", the alter table does a COMMIT, then it drops the column, then it either commits (if successful on the drop) or rolls back (just the drop). Definitely do not need a commit there, it was there all along.*** Footnote: My description of the LOBINDEX was an approximation.Each index entry carries a fixed size “payload” listing up to eight lob chunks; so the (LOB_ID, chunk_number) index entries in a LOBINDEX may point to every 8th chunk in the LOB.

updating clob column-74updating clob column-80updating clob column-17

I have a table that has been defined with a column of type VARCHAR2(4000).

One thought on “updating clob column”

  1. It seems like this would be an easy enough task to complete, but you might be surprised at how quickly everything can go wrong based on misuse and misunderstanding of these two little features.