This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
We have an Oracle database that throws the "Bigger type length than maximum" SQLException when processing huge records. Sometimes it is able to process large number of records without errors, but other times this error is thrown, and we have to restart the transaction to get rid of this error. Of late we are unable to get rid of this error for a particular huge transaction. When the load is split into smaller records the transaction goes through, but it fails when the record count is huge.
I want to know if there is any other solution to go by, other than upgrading the database. Our current oracle build is 126.96.36.199. Which build should I upgrade to to fix this ? I am also not convinced that upgrading the DB will fix the error. Patch sets seem to fix the "Bigger type length than maximum" errors that occur on CLOBs, which we dont use. I was told that the Oranxo driver fixes this error but introduces some errors of its own. Any one solved this ? [ March 17, 2007: Message edited by: John Meyers ]
You can try using batch inserts,updates etc. If that doesn't seem to be solution you are looking then run batch programs through CRON jobs schedulers so that you can periodcally keep on pinging databse and doing your stuff
SCJP,SCWCD,SCBCD<br />If Opportunity doesn't knock then build the door