- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- ORACLE 8.1.6 Drop table performace
Operating System - HP-UX
1752788
Members
5690
Online
108789
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-20-2001 06:37 AM
тАО02-20-2001 06:37 AM
ORACLE 8.1.6 Drop table performace
Hi,
Creating a one extent table tries < 1 sec
dropping the same table can try about 2 - 5 minutes some times
any idea?
thak you
Creating a one extent table tries < 1 sec
dropping the same table can try about 2 - 5 minutes some times
any idea?
thak you
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-20-2001 07:42 AM
тАО02-20-2001 07:42 AM
Re: ORACLE 8.1.6 Drop table performace
Try using the truncate command, which does not generate redo, and is faster than the drop command. It also resets the high water mark in the table
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-20-2001 08:17 AM
тАО02-20-2001 08:17 AM
Re: ORACLE 8.1.6 Drop table performace
Thank you fo your answer
but we did not have the possibility to change the application
but we did not have the possibility to change the application
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-01-2001 08:15 AM
тАО03-01-2001 08:15 AM
Re: ORACLE 8.1.6 Drop table performace
Guenter,
Is there anything else running at the same time, that could be causing contention?
When you drop a table, it is removed from the catalog, along with any associated constraints, indexes - also constraints are checked for Referential Integrity with other tables. That said, it should be pretty quick - at least as quick as a create, as the system does not perform a 'DELETE' in the SQL sense, and generates minimal Redo as a result.
I have read somewhere, that operations of this sort can have contention on the system tablespace, as that is where the catalog is stored, and the code for these operations can only run singularly. Therefore, if multiple create and drop table commands are running at the same time, they will run sequentially, regardless of how many processors your system has.
A way around this is to alter the tablespace you create your tables in, to locally managed - no code changes should be required. I cannot remember the exact command but I think you add the clause 'extent management local autoallocate ' or 'extent management local uniform size ___M' to your usual tablespace commands. The two options are used to contol fragmentation. For more details look at 8.1.X documentation. I canl try and fish out more if it helps.
Is there anything else running at the same time, that could be causing contention?
When you drop a table, it is removed from the catalog, along with any associated constraints, indexes - also constraints are checked for Referential Integrity with other tables. That said, it should be pretty quick - at least as quick as a create, as the system does not perform a 'DELETE' in the SQL sense, and generates minimal Redo as a result.
I have read somewhere, that operations of this sort can have contention on the system tablespace, as that is where the catalog is stored, and the code for these operations can only run singularly. Therefore, if multiple create and drop table commands are running at the same time, they will run sequentially, regardless of how many processors your system has.
A way around this is to alter the tablespace you create your tables in, to locally managed - no code changes should be required. I cannot remember the exact command but I think you add the clause 'extent management local autoallocate ' or 'extent management local uniform size ___M' to your usual tablespace commands. The two options are used to contol fragmentation. For more details look at 8.1.X documentation. I canl try and fish out more if it helps.
If at first you do not succeed. Destroy all evidence that you even attempted.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP