Thread: Implicit commit+BLOB
07-18-11, 09:36 #1Registered User
- Join Date
- Jan 2002
Unanswered: Implicit commit+BLOB
In our transaction, there is 3 inserts in 3 tables and one select for update for update empty_blob in real value
insert into a values
insert into b values
insert into c values (...,empty_blob,..)
select for update...
Blobs are huge, and for time to time, there is ora-01691 (unable to extend LOB segment) (datafiles are autoextensible)
When there is ora-01691 error, we can see that is commited 3 inserts commands (select for update isn't because of ora-01691 error).
So, there must be implicit commit here. I thought this:
If there is no room for update blob, transaction implicitely call ALTER TABLESPACE command and try to extend tablespace. Although this command failed, it commit all except update (right with our observations)
But we try this with non-extensible datafiles, and we saw same error 01691. But, we also saw same thing:although in same transaction, first 3 commands are commited, and last one isn't.
So, is there any other ALTER TABLESPACE command which Oracle can try (so that it fire implicit commit, although datafiles are fixed size?)
Thanks for advice, Zvonimir
07-18-11, 10:29 #2Registered User
Provided Answers: 1
- Join Date
- Aug 2003
- Where the Surf Meets the Turf @Del Mar, CA
>When there is ora-01691 error, we can see that is commited 3 inserts commands (select for update isn't because of ora-01691 error).
EXACTLY how do you do as above.
please post COPY & PASTE so we can see what you do & how Oracle respondsYou can lead some folks to knowledge, but you can not make them think.
The average person thinks he's above average!
For most folks, they don't know, what they don't know.
Good judgement comes from experience. Experience comes from bad judgement.