Sysaux Tablespace keep on increasing

Sysaux tablespace keeps on increasing not able to control it, am keep on adding datafiles to control it but its keep on growing. Please tell me some suggestion.
Edited by: 992890 on Mar 10, 2013 5:07 AM

Hi
I have executed the following query and attached the output
select * from DBA_HIST_WR_CONTROL;
DBID     SNAP_INTERVAL     RETENTION     TOPNSQL
3471086047     +00 01:00:00.000000     +07 00:00:00.000000     DEFAULT
3,944,815,540     +00 01:00:00.000000     +07 00:00:00.000000     DEFAULT
2,882,923,506     +00 01:00:00.000000     +07 00:00:00.000000     DEFAULT
1,387,452,485     +00 01:00:00.000000     +07 00:00:00.000000     DEFAULT
2,061,558,320     +00 01:00:00.000000     +07 00:00:00.000000     DEFAULT
4,288,048,108     +00 01:00:00.000000     +07 00:00:00.000000     DEFAULT
3,558,022,128     +00 01:00:00.000000     +07 00:00:00.000000     DEFAULT
412,070,703     +00 01:00:00.000000     +08 00:00:00.000000     DEFAULT
3,516,040,524     +00 01:00:00.000000     +08 00:00:00.000000     DEFAULT
3,580,520,771     +00 01:00:00.000000     +08 00:00:00.000000     DEFAULT
2,350,953,892     +00 01:00:00.000000     +08 00:00:00.000000     DEFAULT
3,922,397,616     +00 01:00:00.000000     +08 00:00:00.000000     DEFAULT
3,923,062,658     +00 01:00:00.000000     +08 00:00:00.000000     DEFAULT
217,995,194     +00 01:00:00.000000     +08 00:00:00.000000     DEFAULT
218,007,544     +00 01:00:00.000000     +08 00:00:00.000000     DEFAULT
2,106,485,754     +00 01:00:00.000000     +08 00:00:00.000000     DEFAULT
Regards
Sham

Similar Messages

SYSAUX tablespace increasing in size

Hi,
I have noticed that SYSAUX tablespace increasing in size. This tablespace is being used by the below components. However, none of those components are used by my applications. They are installed by default with Oracle 10g Realese1. what makes this tablespace increase?? and what should be done to stop increasing in this tablespace?
Oracle Ultra Search 10.1.0.3.0 VALID WKSYS
Oracle Enterprise Manager 10.1.0.3.0 VALID SYSMAN
Oracle XML Database 10.1.0.3.0 VALID XDB
OLAP Catalog 10.1.0.3.0 VALID OLAPSYS
Oracle Text 10.1.0.3.0 VALID CTXSYS
Spatial 10.1.0.3.0 VALID MDSYS
Oracle interMedia 10.1.0.3.0 VALID ORDSYS
Oracle Expression Filter 10.1.0.3.0 VALID EXFSYS
Oracle Workspace Manager 10.1.0.2.0 VALID WMSYS
Oracle Data Mining 10.1.0.3.0 VALID DMSYS

The following is from a metalink post of mine on the same subject>>
The sysaux tablespace is used to hold AWR data among other uses. Reduce the retention and interval setting for the AWR snapshots to reduce the space necessary to hold the data. See dbms_workload_repository package procedure modify_snapshot_settings.
Your statistics collection level will also feed into the above.
Take a look at other features/products you have assigned to sysaux if any and examine the data collection and retention rules you have specified for them.
<<
HTH -- Mark D Powell --

What is the use of SYSAUX Tablespace in Oracle 10G

Dear Experts,
Please Tell me What is the use of SYSAUX Tablespace in Oracle 10G Because
during Web Load Testing It is going to increase countinuosly.Although i am not using this with any tables.
How Can I find out the what is gong on in this.
Can I Remove this tablesspace and other non using Schemas like FLOWS_020100,MDSYS,OUTLN,DIP and TSMSYS etc.

What is SYSAUX?
The SYSAUX tablespace provides storage of non-sys-related tables and indexes that traditionally were placed in the SYSTEM tablespace. For example, the tables and indexes that were previously owned by the system user can now be specified for a SYSAUX tablespace. Unfortunately, Oracle still places the SCOTT schema and the other demonstration schemas in the SYSTEM tablespace. Go figure.
The SYSAUX tablespace is specified with the CREATE DATABASE command. This is demonstrated in the example database creation script in Figure 1.1.
CREATE DATABASE test
MAXINSTANCES 1
MAXLOGHISTORY 1
MAXLOGFILES 5
MAXLOGMEMBERS 3
MAXDATAFILES 100
DATAFILE '/usr/oracle/OraHome1/oradata/aultdb1/test/system01.dbf' SIZE 300M REUSE AUTOEXTEND ON NEXT 10240K MAXSIZE UNLIMITED
EXTENT MANAGEMENT LOCAL
SYSAUX DATAFILE '/usr/oracle/OraHome1/oradata/aultdb1/test/sysaux01.dbf' SIZE 120M REUSE AUTOEXTEND ON NEXT 10240K MAXSIZE UNLIMITED
DEFAULT TEMPORARY TABLESPACE TEMP TEMPFILE '/usr/oracle/OraHome1/oradata/aultdb1/test/temp01.dbf' SIZE 20M REUSE AUTOEXTEND ON NEXT 640K MAXSIZE UNLIMITED EXTENT MANAGEMENT LOCAL
UNDO TABLESPACE "UNDOTBS1" DATAFILE '/usr/oracle/OraHome1/oradata/aultdb1/test/undotbs01.dbf' SIZE 200M REUSE AUTOEXTEND ON NEXT 5120K MAXSIZE UNLIMITED
CHARACTER SET WE8ISO8859P1
NATIONAL CHARACTER SET AL16UTF16
LOGFILE GROUP 1 ('/usr/oracle/OraHome1/oradata/aultdb1/test/redo01.log') SIZE 10240K,
GROUP 2 ('/usr/oracle/OraHome1/oradata/aultdb1/test/redo02.log') SIZE 10240K,
GROUP 3 ('/usr/oracle/OraHome1/oradata/aultdb1/test/redo03.log') SIZE 10240K
USER SYS IDENTIFIED BY "password" USER SYSTEM IDENTIFIED BY "password";
Oracle10g sysaux
With the new SYSAUX tablespace, Oracle comes closer to providing all the needed tablespaces for a truly OFA-compliant database right out of the box. With just one CREATE DATABASE command we can specify the SYSTEM tablespace, the TEMPORARY tablespace, the AUXSYS tablespace, the default UNDO tablespace, and the redo logs.
Of course, with the Oracle Managed Files option you can create an entire database with a single command, but the database created is not suitable for production use and is not OFA-compliant.
The SYSAUX tablespace is required in all new 10g databases. Only the SYSAUX tablespace datafile location is specified. Oracle specifies the remainder of the tablespace properties including:
online
permanent
read write
extent managment local
segment space management auto
If a datafile is specified for the SYSTEM tablespace, then one must be specified for the SYSAUX tablespace as well. If one is not specified, then the CREATE DATABASE command will fail. The only exception is for an Oracle Managed File system.
During any update of a database to Oracle Database 10g, a SYSAUX tablespace must be created or the upgrade will fail. The SYSAUX tablespace has the same security profile as the SYSTEM tablespace. However, loss of the SYSAUX tablespace will not result in a database crash, only the functional loss of the schemas it contains.
Can I drop SysAux?
DROP DATAFILE
Read this...

Sysaux tablespace reached to 90%

Hi
I am getting alert message that sysaux tablespace reached to 90% I checked and found that total allocated space to sysaux is 500M.
1. Can I add datafile to increase size for sysaux tablespace?
2. What could be the reason for growth? Is there any way to free the space from sysaux table space?
Platform Solaris Database 10.2.0.4
Thank you in advance

SDD wrote:
Hi
I am getting alert message that sysaux tablespace reached to 90% I checked and found that total allocated space to sysaux is 500M.
1. Can I add datafile to increase size for sysaux tablespace?
2. What could be the reason for growth? Is there any way to free the space from sysaux table space?
Platform Solaris Database 10.2.0.4
Thank you in advanceselect occupant_name, space_usage_kbytes from v$sysaux_occupants;
use segment advisor to analyze the space occupied in sysaux tablesapace.
One thing you could do is to set AUTOEXTEND OFF in datafile(s) of SYSAUX tablespace, so you'll get an error, but you can understand where is the problem. Identify datafile(s) :
SQL> select file_name from dba_data_files
2 where tablespace_name = 'SYSAUX';
then for each file_name
SQL> alter database datafile
2 '<file_name>' autoextend off;
The sysaux tablespace is used to hold AWR data among other uses. Reduce the retention and interval setting for the AWR snapshots to reduce the space necessary to hold the data. See dbms_workload_repository package procedure modify_snapshot_settings.
Your statistics collection level will also feed into the above.
Take a look at other features/products you have assigned to sysaux if any and examine the data collection and retention rules you have specified for them.
Another major occupant of the SYSAUX tablespace is the embedded Enterprise Manager (EM) repository. This repository is used by Oracle Enterprise Manager Database Control to store its metadata. The size of this repository depends on database activity and on configuration-related information stored in the repository.
Other database components in the SYSAUX tablespace will grow in size only if their associated features (for example, Oracle UltraSearch, Oracle Text, Oracle Streams) are in use. If the features are not used, then these components do not have any significant effect on the size of the SYSAUX tablespace.
hope, this will helps you.
Edited by: rajeysh on Jun 17, 2010 4:20 PM

SYSAUX tablespace full

Hi,
What will happen if SYSAUX tablespace size is full and we do not increase the size?
Will the database hang or continue to run?
AFAIK if SYSTEM tablespace is full then database gets hanged.
Edited by: oratest on Feb 13, 2010 11:00 PM

If sysaux tblsp is full, the database would still remain operational except the functionality associated with AWR will not work. I would expect that the snapshots that by default gets gathered every hour cannot be stored anymore unless you increase the sysaux tablespace size.
Your database users would still be able to work normally though.

Sysaux tablespace running low !!

Hi
My sysaux tablespace is running low. It was created with autoextend and the max size it can autoextend on is 3 GB. Please check the following
SQL> select TABLESPACE_NAME, FILE_NAME, BYTES/(1024*1024), AUTOEXTENSIBLE, MAXBYTES/(1024*1024)
2 from dba_data_files
3 where tablespace_name = 'SYSAUX';
TABLESPACE FILE_NAME BYTES/(1024*1024) AUT MAXBYTES/(1024*1024)
SYSAUX H:\ORACLE\ORADATA\STUTEST\SYSAUX01.DBF 3175.28125 YES 32767
What is the best practise? Do i have to add another datafile in sysaux tablespace with same size and auto extensible max size to 3 gb?
Thanks for your help!!!

It depends on your requirement. If you have any job running which will trigger an alert about space utilization or you are using OEM to see the space utilization then probably you can keep the autoextend off and resize the datafile when require else you can keep it on.
Regards

Oracle Tablespace (USERS) is increasing drastically

Hi,
I am using Oracle 8.1.7 Enterprise Edition. Recently, I moved my oracle database from one server another server. Database is working fine on new servers. After 1 month I found one of the Tablespace USERS is keep on increasing drastically and it full the tablespace in 2 days. I increase more data files to support and keep database running. I already added 12 database files and tablespace already at 93% full and size of the tablespace is 43GB. Previously it is only 4 GB and only used 2 data files.
Even I done the reindex and stop the archive log and redo log.
Please help to find out what causing this problem and how to fix it.

Hi,
plz first find out to see that no general users are granted powerful roles such as DBA. the follows the query
select grantee from dba_role_privs
where granted_role='dba'
and grantee not in ('SYS','SYSTEM');
and also check to see if any user accounts have been granted sensitive privileges or roles that provide them with the potential to cause serious damage to the database.
select grantee, privilege, admin_option
from dba_sys_privs
where (privilege like '%ANY%' or privilege like '%DROP%' or privilege in ('ALTER SYSTEM', ALTER TABLESPACE','BECOME USER','UNLIMITED TABLESPACE'))
and grantee not in ('SYS','SYSTEM')
and grantee not in (select role from dba_roles
union all
select grantee, privilege admin_option
from dba_sys_privs
where (privilege like '%ANY%' or privilege like '%DROP%' or privilege in ('ALTER SYSTEM', ALTER TABLESPACE','BECOME USER','UNLIMITED TABLESPACE'))
and grantee not in ('SYS','SYSTEM')
and grantee in (select role from dba_roles where role not in ('DBA','AQ_ADMINISTRATOR_ROLE',''IMP_FULL_DATABASE','SNMPAGENT','OEM_MONITOR','EXP_FULL_DATABASE'));
REGRADS...........................

Oracle XE system and sysaux tablespaces

I've got a question regarding system and sysaux tablespaces. Below are numbers from my Oracle XE database. Are these tablespaces constant or are they growing over time? I do not have any custom objects in either system or sysaux schema. If they extend is there a way to clean them up in order to reduce used space? Also, what is the impact of their size on the 4 GB XE limit?
# TABLESPACE NAME ALLOCATED (MB) USED (MB) FREE (MB) USED (%) FREE (%)
=====================================================================
1.SYSAUX....................710...............696.44........13.56..........98.09..........1.91
2.SYSTEM...................440...............429.75........10.25...........97.67......... 2.33
Thanks,
Art

Both should remain relatively constant.
The size of the SYSTEM tablespace will increase if you have many PL/SQL objects.
Whether they can be cleaned up can't be answered in a generic way, it depends.
They likely count to the 4 Gb limit.
Sybrand Bakker
Senior Oracle DBA

How to release space of SYSAUX tablespace

Hi,
I am now using htmldb 2.0 and created tens of tables in one schema. Several tables are stored in tablespace SYSAUX. Since now I am trying to store a big file to the table(1GB), I found the tablespace grows pretty fast and I have to extend the size. The odd thing is when I delete that file from my table, SYSAUX tablespace seems not release any room and when I insert the big file again into the table, SYSAUX grows again. How can I release the space then? I can't image that why it can't release any room. I also check the occupants of SYSAUX and found one occupant called "other" takes over 90% of space. I tried to move it out of SYSAUX, it doesn't work. What do "other" do actually? I got completely lost. Any help will be greatly appreciated.
Linke

Hi,
if you drop a table in Oracle 10g,
you will find teh extents of this table in
DBA_FREE_SPACE.
in DBA_FREE_SPACE???
I don't think so.
SQL >select ddf.tablespace_name,round(total/1024/1024,3) ttlSize,round((total-nvl(freespace,0))/1024/1024,3) used, round((total-nvl(freespace,0))/total*100,2) usedpct
from
(select tablespace_name,sum(bytes) total from dba_data_files group by tablespace_name) ddf,
(select tablespace_name,sum(bytes) freespace from dba_free_space group by tablespace_name) dfs
where ddf.tablespace_name=dfs.tablespace_name(+) and ddf.tablespace_name='USERS';
TABLESPACE_NAME                   TTLSIZE       USED    USEDPCT
USERS                                  16      2.813 17.58
SQL >create table test (col1 number) storage(initial 2m)
2 /
Table created.
SQL >select ddf.tablespace_name,round(total/1024/1024,3) ttlSize,round((total-nvl(freespace,0))/1024/1024,3) used, round((total-nvl(freespace,0))/total*100,2) usedpct
from
(select tablespace_name,sum(bytes) total from dba_data_files group by tablespace_name) ddf,
(select tablespace_name,sum(bytes) freespace from dba_free_space group by tablespace_name) dfs
where ddf.tablespace_name=dfs.tablespace_name(+) and ddf.tablespace_name='USERS';
TABLESPACE_NAME                   TTLSIZE       USED    USEDPCT
USERS                                  16      4.813 30.08<--used 2mb
SQL >select sum(bytes)/1024/1024 from dba_segments where tablespace_name='USERS'
2 /
SUM(BYTES)/1024/1024
                6.75
SQL >drop table test
2 /
Table dropped.
SQL >select sum(bytes)/1024/1024 from dba_segments where tablespace_name='USERS'
2 /
SUM(BYTES)/1024/1024
                6.75 <-- kept in the same tablespace

Logical corruption found in the sysaux tablespace

Dear All:
We lately see the logical corruption error when running dbverify command which shows the block corruption. It is always on the the sysaux tablespace. The database is 11g and platform is Linux.
we get the error like:error backing up file 2 block xxxx: logical corruption and this comes to alert.log out of the automated maintenance job like sqltunning advisor running during maintenance window.
Now As far as I know,we can't drop or rename the sysaux tablespace. there is a startup migrate option to drop the SYSAUX but it does not work due to the presence of domain indexes. you may run the rman block media recovery but it ends with not fixing since rman backups are more of physical than maintain the logical integrity.
Any help, advise, suggestion will be highly appreciated.

If you let this corruption there then you are likely to face a big issue that will compromise database availability sooner or later. The sysaux is a critical tablespace, so you must proceed with caution.
Make sure you have a valid backup and don't do any thing unless you are sure about what you are doing and you have a fall back procedure.
if you still have a valid backup then you can use rman to perform a db block level recovery, this will help you in fixing the block. Otherwise try to restore and recover the sysaux. In case you cannot fix the block by refreshing the sysaux tablespace then I suggest you to create a new database and use aTransportable Tablespace technique to migrate all tablespaces from your current database to the new one and get rid of this database.
~ Madrid
http://hrivera99.blogspot.com

System and sysaux tablespace

hi,
can anyone tell me whata system and sysaux tablespace contains, and how to manage them.

The system tablespace
The system tablespace is always available when a database is open (it cannot be taken offline).
The system tablespace stores the data dictionary (or their base tables, respectively).
The sysaux tablespace
The sysaux tablespace is new with Oracle 10g. It is used to store database components that were stored in the system tablespace in prior releases of the database.
Also, the tablespaces that were needed for RMAN's recovery catalog, for Ultra Search, for Data Mining, for XDP and for OLAP are going to sysaux with 10g.
Additionally, it is the place where automatic workload repository stores its information.
The SYSAUX tablespace was installed as an auxiliary tablespace to the SYSTEM tablespace when you created your database. Some database components that formerly created and used separate tablespaces now occupy the SYSAUX tablespace.
If the SYSAUX tablespace becomes unavailable, core database functionality will remain operational. The database features that use the SYSAUX tablespace could fail, or function with limited capability.
refer the links:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/tspaces.htm#i1011659

Sysaux tablespace issue

hi,
I ve upgraded an database for 9i to 10g. The upgrade was sucessfull and the Db was in normal usage. Due to some functionality testing the database was restored to a state from the backup taken after upgrade. But while restoring the database i forgot to include the path of the datafile of sysaux tablespace in the control file re-creation script.
I didnt notice this issue for long time until i realised the mistake made by me.
I found in the alert logs which showed errors such as
ORA-01157: cannot identify/lock data file 124 - see DBWR trace file
ORA-01110: data file 124: '/oracle/ora/dbs/MISSING00141'
ORA-27037: unable to obtain file status
since the path of the sysaux tablespace was not referred in the script i thought of referring it now and i issued the following command
alter tablespace sysaux add datafile '<path>/sysaux01.dbf' reuse;
i issed this as the datafile was already present and i thought of jus reuing it again.
But what had happened is this datafile had been added as an additional datafile for the sysaux tablespace,which means the sysaux is still referring '/oracle/ora/dbs/MISSING00141' as one of the datafile.
but one important thing is that there isnt any such datafile ie '/oracle/ora/dbs/MISSING00141' when i checked inside the dbs folder.
The path is getting referred as part of the sysaux tablespace but its physical location is not found.
So i did took this datafile offlinedrop issuing
alter database datafile '/oracle/ora/dbs/MISSING00141' ofline drop
but the problem i m facing now is the AWR is not opening up and it throw error stating first datafile of sysaux tablespace '/oracle/ora/dbs/MISSING00141' not found.
ORA-00376: file 124 cannot be read at this time
ORA-01110: data file 141: '/oracle/ora/dbs/MISSING00141'
ORA-06512: at line 21.
any solution for solving the problem would be appreciated
thanks,
ahmed

i m able to start up the database normally....there isnt any errors while starting the DB.These errors are encountered in alert log file and user trace files.As as result AWR is not opening.

Sysaux tablespace issue-missing sysux datafile

hi,
I ve upgraded an database for 9i to 10g. The upgrade was sucessfull and the Db was in normal usage. Due to some functionality testing the database was restored to a state from the backup taken after upgrade. But while restoring the database i forgot to include the path of the datafile of sysaux tablespace in the control file re-creation script.
I didnt notice this issue for long time until i realised the mistake made by me.
I found in the alert logs which showed errors such as
ORA-01157: cannot identify/lock data file 124 - see DBWR trace file
ORA-01110: data file 124: '/oracle/ora/dbs/MISSING00141'
ORA-27037: unable to obtain file status
since the path of the sysaux tablespace was not referred in the script i thought of referring it now and i issued the following command
alter tablespace sysaux add datafile '<path>/sysaux01.dbf' reuse;
i issued this as the datafile was already present and i thought of jus reusing it again.
But what had happened is this datafile had been added as an additional datafile for the sysaux tablespace,which means the sysaux is still referring '/oracle/ora/dbs/MISSING00141' as one of the datafile.
but one important thing is that there isnt any such datafile ie '/oracle/ora/dbs/MISSING00141' when i checked inside the dbs folder.
The path is getting referred as part of the sysaux tablespace but its physical location is not found.
So i did took this datafile offlinedrop issuing
alter database datafile '/oracle/ora/dbs/MISSING00141' ofline drop
but the problem i m facing now is the AWR is not opening up and it throw error stating first datafile of sysaux tablespace '/oracle/ora/dbs/MISSING00141' not found.
ORA-00376: file 124 cannot be read at this time
ORA-01110: data file 141: '/oracle/ora/dbs/MISSING00141'
ORA-06512: at line 21.
any solution for solving the problem would be appreciated
thanks,
ahmed

Hi, I've got exactly the same problem up to the point where I try to offline drop the MISSING0009 datafile.
The command says it completed OK but the phantom datafile does not go and still reports that it's there in dba_data_files, althoguh the online_status is RECOVER, the status is ONLINE.
I'm not sure how to get rid of the entry if the offline drop command doesnt work. I've tried recreating the control file and deleting the entry for this datafile too but somehow it returned after that too!
I''m also not sure what to do when I do get rid of it - since I cant recover the old sysaux01.dbf datafile since it's not consistent with the database since there has been a week inbetween and we're not running archivelogging.
I would assume that all the stuff usually put in the SYSAUX tablespace is therefore lost, but I dont think we use anything that normally puts stuff in there, I've only noticed this since I was trying to install em.
Do I have to rebuild the database from scratch? Or any ideas on how I can recover the situation? Can I do something like startup upgrade and re-run the upgrade scripts which will put their stuff back into sysaux....?
Many thanks for ideas
Rob

Time Machine - data to back up keeps on increasing as it's backing up!

Apologies if this has been asked and answered before, but I couldn't find anything on it when I searched.
I want to install Mavericks on my iMac, currently running 10.8.5, but before I do so, I want to do an up-to-date Time Machine backup.
I already had Time Machine set to back up to an external 1TB drive, but after several versions of backups over the past few months, and also me adding and creating several GBs of new data on my iMac, Time Machine ran out of space to do any more backups to the external HD.
So to be safe, before the Mavericks install, I wanted a fresh new up-to-date backup of all my data. I did a quick erase of the external HD to clear the space on it, and also deleted quite a few GBs of unnecessary data on the iMac. After that, I had 999GB of free space on the external HD and just 850-ish GB of data on the iMac to backup. So I set my Time Machine to run, and watched it start backing up... 1GB of 850GB... 2GB of 850GB... 3GB of 850GB... And so on. All going as expected. No problems there.
So then I leave my Mac to get on with it, as it estimates it's going to take several hours.
After the estimated time has passed, I come back to see if it's done, but to my surprise, the progress bar is now reading something along the lines of 850GB of 900GB. Where did the extra 50GB come from to take it up to 900GB?
Worse still, as I sit and watch it continue, it progresses along the lines of 860GB of 920G (60GB remaining), then 870GB of 940GB (now 70GB remaining), then 880GB of 960GB (now 80GB remaining) and so on.
So not only is the total amount increasing for some bizarre reason, but it's also increasing faster than it's backing up!
What on earth is going on here?!
It may be worth mentioning that I originally tried doing this with approx 900GB of data to back up to the external 1TB disk, and a similar thing happened, but when I came back to check on that a couple of hours after it was due to complete, I came back to see an error message stating that Time Machine could not do the backup because it needed an additional 100mb of space. Just 100mb, that's all.
After that error, I removed approx 50GB, way more than 100mb, and got my data down to 850GB before starting this again. But the same thing is happening. The total amount just keeps on increasing and increasing and increasing as it progresses!
It's worth noting that I am not doing ANYTHING else on my Mac whilst this is running that would take up data / disk space. No apps are running at all.
Can anyone please tell me what's going on here, and more importantly, how can I fix it?
Thanks!

Thanks for the suggestions.
I am aware that you can turn Time Machine on and off completely via the preferences, but that basically defeats the purpose of having a "set and forget" backup. Especially since Time Machine specifically includes an option to not backup when on battery power.
I'll try the "full reset" option described in the link to see if that helps.

UNDOTBS1 and SYSAUX Tablespace Filename Mismatch in Oracle 11g XE

Hi,
We have installed Oracle 11g XE 32 bit on Windows and found that Tablespace name and filenames are mismatched for UNDOTBS1, SYSAUX.
If you run following query:
SELECT TABLESPACE_NAME, FILE_NAME FROM DBA_DATA_FILES; You will get below output:
TABLESPACE_NAME                    FILE_NAME
============================================================================
USERS                C:\ORACLE\ORACLE11GXE\APP\ORACLE\ORADATA\XE\USERS.DBF
UNDOTBS1           C:\ORACLE\ORACLE11GXE\APP\ORACLE\ORADATA\XE\SYSAUX.DBF
SYSAUX                C:\ORACLE\ORACLE11GXE\APP\ORACLE\ORADATA\XE\UNDOTBS1.DBF
SYSTEM                C:\ORACLE\ORACLE11GXE\APP\ORACLE\ORADATA\XE\SYSTEM.DBFNotice the difference between UNDOTBS1 and SYSAUX.
UNDOTBS1 tablespace has filename SYSAUX.DBF while
SYSAUX tablespace has filename UNDOTBS1.DBF
Is this a bug or just a wrong name mapping?
Will this affects the internal behavior of tablespace as well for undo tablespace and APEX Installation?
Regards,
Sohil Bhavsar.

Error: ORA-03297 ... related to this mismatch of UNDOTBS1 with SYSAUXActually its related to trying to resize a file smaller than the existing extents in use, so yes, restores aren't the only place that could cause confusion from the "incorrect" datafile names.
Fixing it could be done in one pass if you don't mind adjusting filenames so they don't clash, i.e. shut down your database instance and move the files at the OS, startup mount and rename the files in the database.
Don't use the services applet, the instance has to be shutdown with sqlplus, leave the database service running. If you try to open the database with OS files renamed but not corrected in the instance, the database won't open if there are troubles with the undo datafile.
sqlplus /nolog
conn /as sysdba;
... connected ...
col name format a60
col tsname format a10
set lines 120
select t.name tsname, d.name, d.BYTES / 1024 / 1024 mb from v$tablespace t, v$datafile d where t.ts# = d.ts#;
system .../system.dbf <n>
shutdown immediate;
... database closed ...
exit
cd <datafile directory>
move sysaux.dbf undotbs01.dbf
move UNDOTBS1.DBF sysaux.dbf
# or use file explore GUI after shutdown
sqlplus /nolog
conn /as sysdba;
... connected to idle instance ...
startup mount;
... SGA, instance size info ...
alter database rename file 'C:\...<full path>\SYSAUX.DBF' to 'C:\...<full path>\UNDOTBS01.DBF';
alter database rename file 'C:\...<full path>\UNDOTBS1.DBF' to 'C:\...<full path>\SYSAUX.DBF';
select t.name tsname, d.name, d.BYTES / 1024 / 1024 mb from v$tablespace t, v$datafile d where t.ts# = d.ts#;
... make sure you get what was asked for ...
TSNAME     NAME                                                       MB
SYSTEM     C:\ORACLEXE\APP\ORACLE\ORADATA\XE\SYSTEM.DBF              360
SYSAUX     C:\ORACLEXE\APP\ORACLE\ORADATA\XE\SYSAUX.DBF              660
UNDOTBS1   C:\ORACLEXE\APP\ORACLE\ORADATA\XE\UNDOTBS01.DBF            25
USERS      C:\ORACLEXE\APP\ORACLE\ORADATA\XE\USERS.DBF               100
alter database open;
... database altered ...

Sysaux Tablespace keep on increasing

Similar Messages

Maybe you are looking for