ORA-1688: unable to extend table
SYS.WRH$_ACTIVE_SESSION_HISTORY partition
WRH$_ACTIVE_3970712838_6793 by 128 in tablespace SYSAUX?
What is the solution for this issue?
Answers were Sorted based on User's Feedback
1) Export the snapshots and then do a manual purge
2) Ignore this error Else let oracle do the job. Did you
know the MMON does auto maintenance of sysaux storage
management. Look below as taken from alert log.
ORA-1688: unable to extend table SYS.WRH$_LATCH_CHILDREN
partition WRH$_LATCH__2530202403_28403 by 128 in tablespace
SYSAUX
ORA-1688: unable to extend table SYS.WRH$_LATCH_CHILDREN
partition WRH$_LATCH__2530202403_28403 by 128 in tablespace
SYSAUX
MMON Flush encountered SYSAUX out of space error(1688).
MMON (emergency) purge of WR snapshots (28078) and older
Mon Feb 15 06:02:42 2010
3) Increase space of sysaux data file or add another file.
4) Oracle provides utlsyxsz.sql file to help calculate
approx the size required by sysaux. Find out the space and
add another 25% extra on top of it to be sure for a good
measure.
5) It might be possible Disable alerts due to sysaux space
warnings .
Is This Answer Correct ? | 2 Yes | 0 No |
Answer / jed
This will solve the symptom, but you might be facing a bug. Here is a write up I just did on this.
http://tinky2jed.wordpress.com/2013/12/05/ora-1688-unable-to-extend-table-sys-wrh_active_session_history/
Is This Answer Correct ? | 0 Yes | 0 No |
ORA-09700: sclin: maximum number of latches exceeded
ORA-27003: cannot open file on device allocated with NOIO option
ORA-02404: specified plan table not found
SQL*Loader-00470: table string does not have system generated OID
NNL-00411: Minimum response time: string
ORA-30200: Wrong NLS item was passed into OCINlsGetInfo()
NNL-00353: Not allowed
LPX-00013: wrong node type
ORA-00335: online log string: No log with this number, log does not exist
SQL*Loader-00902: Error opening cursor: [number]
PLS-00368: in RAISE statement, 'string' must be an exception name
ORA-28043: invalid bind credentials for DB-OID connection