Home » RDBMS Server » Performance Tuning » problems with updating big table by commit at end
problems with updating big table by commit at end [message #192991] Thu, 14 September 2006 09:05 Go to next message
coral_3
Messages: 2
Registered: September 2006
Junior Member
I need to update a huge table once a week, but data consistency is required(So I have to commit once).
I delete all records and insert all new data again to keep fresh data, and do commit at the end.
The code is running slowly gradually. Five times slower than using auto commit on.

Any better idea I can solve this problem? Or except commit , is there a better way to update huge table?

Thanks
Re: problems with updating big table by commit at end [message #192993 is a reply to message #192991] Thu, 14 September 2006 09:10 Go to previous messageGo to next message
Mahesh Rajendran
Messages: 10672
Registered: March 2002
Location: oracleDocoVille
Senior Member
Account Moderator
Please search the board.
There are too many related discussions on BIG commit.
After every major change (insert/delete/update), you are supposed to collect statistics on those tables/indexes.
Are you doing that?
Re: problems with updating big table by commit at end [message #193133 is a reply to message #192993] Fri, 15 September 2006 00:26 Go to previous messageGo to next message
rleishman
Messages: 3724
Registered: October 2005
Location: Melbourne, Australia
Senior Member
Take a look at DBMS_REDEFINITION.

Ross Leishman
Re: problems with updating big table by commit at end [message #193291 is a reply to message #192993] Fri, 15 September 2006 10:11 Go to previous message
coral_3
Messages: 2
Registered: September 2006
Junior Member

I am not dba. how to collect the statistics? Is the statistics helpful for increasing the speed?
Previous Topic: Number of Datafiles in a Tablespace
Next Topic: Join Query problem. One using index while another full table scan
Goto Forum:
  


Current Time: Sun Dec 04 00:42:01 CST 2016

Total time taken to generate the page: 0.22163 seconds