- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Max extents reached
Operating System - HP-UX
1753705
Members
5045
Online
108799
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
Go to solution
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
тАО08-17-2003 06:26 PM
тАО08-17-2003 06:26 PM
Re: Max extents reached
Kenny,
7.2 cannot increase the extend ???.In this case then just export the table and import back but make the extend size bigger...
Well this might be a good idea because the tables have a lot of insert and deletes....
insert/delete definately will make your table defrag and only export/import will help you.
is coalesce exist in 7.2 ???? Surely 8 you can do manual coelesce...
good luck.
regards
mB
7.2 cannot increase the extend ???.In this case then just export the table and import back but make the extend size bigger...
Well this might be a good idea because the tables have a lot of insert and deletes....
insert/delete definately will make your table defrag and only export/import will help you.
is coalesce exist in 7.2 ???? Surely 8 you can do manual coelesce...
good luck.
regards
mB
There are three person in my team-Me ,myself and I.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-17-2003 06:40 PM
тАО08-17-2003 06:40 PM
Re: Max extents reached
Hi mB
I get what you mean by coalesce. But Oracle 7.2 does not support Alter Tablespace coalesce
I get what you mean by coalesce. But Oracle 7.2 does not support Alter Tablespace
All Your Bases Are Belong To Us!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-17-2003 10:53 PM
тАО08-17-2003 10:53 PM
Re: Max extents reached
Hi,
For a table that has frequent deletes and inserts, it has tobe re-organised every now and then. For this you can cron job the task to export and then import the table data say once every week.
For the first time when you export the table data, drop the table and re-create the table with good size of initial and next extents. This will prevent you table from extending into too many extents.
There are other oprions as well. But as you are usng Oracle 7.2, the export and import of table data should fix the issue of extending to many extents. Choose and convenient time when the table is is not beeing used then schedule the cron job.
IA
For a table that has frequent deletes and inserts, it has tobe re-organised every now and then. For this you can cron job the task to export and then import the table data say once every week.
For the first time when you export the table data, drop the table and re-create the table with good size of initial and next extents. This will prevent you table from extending into too many extents.
There are other oprions as well. But as you are usng Oracle 7.2, the export and import of table data should fix the issue of extending to many extents. Choose and convenient time when the table is is not beeing used then schedule the cron job.
IA
Never give up, Keep Trying
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-18-2003 08:48 AM
тАО08-18-2003 08:48 AM
Re: Max extents reached
Hi Kenny,
this is bad news. So there is no way out than to reorganize. Indira listed the steps already. If you do not do this frequently, but only every now and then, be sure to assign only 100 for MAX-Extents in your reorg.
When you bounce this one, you can increase NEXT and set MAX to 110 and schedule your next reorg.
When you bounce 110 you can increase NEXT and set MAX to 115 and schedule an urgent reorg.
When you bounce 115 you can increase NEXT and set MAX to 119 and schedule a very very very urgent reorg and still have two spares left. :-)
Another thing you might consider is to use PCT_INCREASE, which will increase the NEXT size every time a new extent is allocated. But usually nobody likes this, because it requires a bit more of monitoring to avoid unexpected grow of segments.
Good luck
Volker
this is bad news. So there is no way out than to reorganize. Indira listed the steps already. If you do not do this frequently, but only every now and then, be sure to assign only 100 for MAX-Extents in your reorg.
When you bounce this one, you can increase NEXT and set MAX to 110 and schedule your next reorg.
When you bounce 110 you can increase NEXT and set MAX to 115 and schedule an urgent reorg.
When you bounce 115 you can increase NEXT and set MAX to 119 and schedule a very very very urgent reorg and still have two spares left. :-)
Another thing you might consider is to use PCT_INCREASE, which will increase the NEXT size every time a new extent is allocated. But usually nobody likes this, because it requires a bit more of monitoring to avoid unexpected grow of segments.
Good luck
Volker
- « Previous
-
- 1
- 2
- Next »
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