Error in accessing CLOB

Nelson Ng

Member²
Hi,

I've built a program open a table containing a CLOB field.

The program has a grid pointing to CLOB.
When the table is open, sometimes the following error appears

ORA-03130

Please help,
Nelson.
 
More information abuot the problem.

I found that if there is no record in the table, the table can be open and records can be inserted and edited without error.

However, if the tables has 1 or more records, when open the table, the mentioned error message will display.

Please help !!

Regards,
Nelson.
 
I haven't got a clue. Perhaps you can send me a small demo project to reproduce the problem?

------------------
Marco Kalter
Allround Automations
 
I've posted an CLOB field Oracle Error
ORA-03127 on this board which is very much like this one. I doubt that it may be owing to DOA's error.
Because 1.I can see the text field in SQL*Plus very correctly. I test this problem so many times with so many methods. Finally, I figure out it always happen to some fetching actions like calling a Dataset.Next etc..
2.The CLOB field may contain text in it. But
I test it with inputing some special character like #13,#10,#9 etc, or some 2-bytes character (ex. Traditional Chinese), after that , every time I call Next to fetch
it from the program,the error happened.
3.I try to fill the CLOB field with a very large string 'xxxxxx....',size is 8193, to test what it will happened,but it works fine.

Please anyone can help us,Thanks!

ORA-03130 the buffer for the next piece to be fetched is required
Cause: The application performed a piecewise define on the column.
Action: Provide the next buffer for the next piece to be retrieved.

Originally posted by Nelson Ng:
More information abuot the problem.

I found that if there is no record in the table, the table can be open and records can be inserted and edited without error.

However, if the tables has 1 or more records, when open the table, the mentioned error message will display.

Please help !!

Regards,
Nelson.
 
Hi,

My problem has now been fixed in the coming release. Support said it is due to insufficient buffer size allocated. You may ask for a prerelease version to test if it works for you.

Good luck,
Nelson.
 
Back
Top