- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Resize of oracle sys.AUD$ does not stay perman...
Operating System - HP-UX
1752801
Members
5702
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
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
тАО12-05-2005 08:30 AM
тАО12-05-2005 08:30 AM
Don't know if anybody else has encountered this but I resized the sys.AUD$ table last week on multiple servers only to check today and see that next extent settings to be different and no where close to what they were set to.
We run a nightly report from the table and then truncate the table. I suspect the change happens when the table is truncated.
If anybody has a handle on what resets the storage settings for next extent, let me know. Table filled up last week, thus the reason for increasing the next extent size.
Jack...
We run a nightly report from the table and then truncate the table. I suspect the change happens when the table is truncated.
If anybody has a handle on what resets the storage settings for next extent, let me know. Table filled up last week, thus the reason for increasing the next extent size.
Jack...
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-05-2005 08:39 AM
тАО12-05-2005 08:39 AM
Re: Resize of oracle sys.AUD$ does not stay permanent on 7.3.4
Jack,
Not sure if I'm reading your question correctly. Are you saying the the next_extent size that you defined for the table is changing? Or that the next extent that you allocated has gone away.
Truncate table without the REUSE STORAGE clause will release all but the initial extent.
If that's not the case is it possible that your script is dropping and recreating the table?
Patti
Not sure if I'm reading your question correctly. Are you saying the the next_extent size that you defined for the table is changing? Or that the next extent that you allocated has gone away.
Truncate table without the REUSE STORAGE clause will release all but the initial extent.
If that's not the case is it possible that your script is dropping and recreating the table?
Patti
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-05-2005 08:54 AM
тАО12-05-2005 08:54 AM
Re: Resize of oracle sys.AUD$ does not stay permanent on 7.3.4
I'm just using the truncate table table without any additional arguments. I'm setting the next extent size only. I'm not recreating the table. This is really weird.
I found a article on the truncate concern and it appears to be normal to resize the next extent.
"The table├в s storage parameter NEXT is changed to be the size of the last extent
deleted from the segment in the process of truncation."
http://asktom.oracle.com/pls/ask/f?p=4950:8:::::F4950_P8_DISPLAYID:1222036354881
Learn something every day.
jack
I found a article on the truncate concern and it appears to be normal to resize the next extent.
"The table├в s storage parameter NEXT is changed to be the size of the last extent
deleted from the segment in the process of truncation."
http://asktom.oracle.com/pls/ask/f?p=4950:8:::::F4950_P8_DISPLAYID:1222036354881
Learn something every day.
jack
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-05-2005 12:34 PM
тАО12-05-2005 12:34 PM
Solution
Hi Jack,
When you truncate a table the "Truncate" command uses the DROP STORAGE clause which keeps 'minextents' extents, thus only 1 extent.
So the storage parameter next extent of the table goes back to the default definition.
I had this issue too. So what you do is truncate the table then increate the next extent parameter using alter table storage (next 9999);. This will keep the next extents storage to what you set when you start population the table again.
Indira A
When you truncate a table the "Truncate" command uses the DROP STORAGE clause which keeps 'minextents' extents, thus only 1 extent.
So the storage parameter next extent of the table goes back to the default definition.
I had this issue too. So what you do is truncate the table then increate the next extent parameter using alter table
Indira A
Never give up, Keep Trying
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