If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > Oracle > Very slow deletes

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #31 (permalink)  
Old 12-02-04, 12:16
RBARAER RBARAER is offline
Registered User
 
Join Date: Aug 2004
Location: France
Posts: 754
Ok, thanks Alan. I'll have to wait for patches, because we don't have an Oracle support account yet since we are still in development. No, it was not an IOT.

Regards,

RBARAER
Reply With Quote
  #32 (permalink)  
Old 12-02-04, 23:00
billm billm is offline
Drunkard
 
Join Date: Nov 2002
Location: Desk, slightly south of keyboard
Posts: 697
Hi RBARAER,

I don't want to sound like the "devil's advocate" but I would suggest that it is during development that you need the support account. Once in production, the support account is nice, but I would hope you've exhausted support/patches etc before going into production.

Hth
Bill
__________________
Please don't email me directly with questions. I've probably just got home from the pub and cannot guarantee the sanity of my answers. In fact, I can't believe I actually made it home.
Reply With Quote
  #33 (permalink)  
Old 12-03-04, 02:52
RBARAER RBARAER is offline
Registered User
 
Join Date: Aug 2004
Location: France
Posts: 754
Hello billm,

You're right, undoubtedly. However, I suppose we can only have a support account once we've bought an Oracle License. The point is we prefer not to pay for the license as long as we're in dev only. I think my boss plans to buy a license once we go in pre-prod. Do you think it will be too late ? Do you think we could negociate a support account with Oracle even though we still don't have bought any license (but of course we plan to) ?

Regards,

RBARAER
Reply With Quote
  #34 (permalink)  
Old 12-06-04, 11:12
The_Duck The_Duck is offline
Registered User
 
Join Date: Jul 2003
Posts: 2,292
Quote:
Originally Posted by RBARAER
Re-reading this thread,

1) The_Duck, I thought of using your idea, but the problem is that I may be inserting lots of data as well as querying it at the moment I would switch tables, so, even if I re-synch the new table after the synonym redefinition by inserting data from the old table that had not yet been inserted in the new, there will be a small period during which I could not query all available data. Or I could simply lock the tables (read & write) during the synonym redefinition, but IMO it's not a good solution. What do you think ?
I still think my option is fairly valid. Once you point the synonym to the different table then I would re-run the insert script for the time it took to create the new table to be sure you got every row (in case some got inserted as you moved data).

so maybe:
insert into table_B where table_A.data_date > (time I started the move);
__________________
- The_Duck
you can lead someone to something but they will never learn anything ...
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On