ORA-1688: unable to extend table in SYSAUX tablespace [message #166969] |
Mon, 10 April 2006 10:44 |
pzlj6x
Messages: 107 Registered: May 2005 Location: Louisville
|
Senior Member |
|
|
I get this errorin my alert log file.
ORA-1688: unable to extend table SYS.WRH$_ACTIVE_SESSION_HISTORY partition WRH$_ACTIVE_216122103_4291 by 64 in tablespace SYSAUX
SYSAUX is new to Oracle10g. Don't have much knowledge on this tablespace.
Any idea why this error comes and what should be looking into.
Thanks in advance
|
|
|
Re: ORA-1688: unable to extend table in SYSAUX tablespace [message #167037 is a reply to message #166969] |
Mon, 10 April 2006 23:46 |
alexzeng
Messages: 133 Registered: August 2005 Location: alexzeng.wordpress.com
|
Senior Member |
|
|
Connect to your database by sysdba and then run the follow sql:
select a.TABLESPACE_NAME, round(total,1) Total_M, round(free) Free_M, round(100*(1-free/total),1) Usage
from (select TABLESPACE_NAME,sum(BYTES)/(1024*1024) total from dba_data_files group by TABLESPACE_NAME) a
,(select TABLESPACE_NAME,sum(BYTES)/(1024*1024) free from dba_free_space group by TABLESPACE_NAME) b
where a.TABLESPACE_NAME=b.TABLESPACE_NAME(+) order by 4 DESC;
You will get the USAGE information about SYSAUX. If it is full, you can add more data files or enlarge the exist datafiles.
Alex zeng |Skpye me: hans9zeng
|
|
|
|
Re: ORA-1688: unable to extend table in SYSAUX tablespace [message #167141 is a reply to message #166969] |
Tue, 11 April 2006 09:11 |
pzlj6x
Messages: 107 Registered: May 2005 Location: Louisville
|
Senior Member |
|
|
Thanks for the suggestions.
I did take an immediate action to add datafile when I got this error in order to resolve the problem. At least we had enough storage disk available to add data files.
Madhu, You are correct. We are taking the snapshot. The default period is to retain for 7 days. However this process is in production for more than 6 months. And I had never faced problem.
But came accross this problem just recently. Since the problem is now resolved, I am now investing to find out what could be the possible cause.
I checked the wrh$active_session_history table. Count is 850,000 records which I think is possibly high.
The question is that Can I delete records from this table. Will there be any problem if I do that?
Or is there a better solution to prevent this happening again.
Thanks
|
|
|
|
|
|
|