Schema CTXSYS, MDSYS

HI,
I have a application which runs on mod_plsql procedural concept using WebDB as DAD.
I have some schema's like "CTXSYS" AND "MDSYS" as part of the database.
My Question, is it OK, if delete these schema's ?
Thanks in advance.

MDSYS provides the objects needed to run Oracle Spatial and Oracle Locator. CTXSYS provides the objects needed to run Oracle Text.
Oracle Text and Oracle Locator are free with the database.
Instead of deleting them, why not find out how you can cut the cost of your developer's code by using them effectively?
If you really want to delete them, use the installer to remove the capabilities. Do NOT drop the schemas manually.

Similar Messages

Oracle Text (schema CTXSYS): additional licence costs?

Hi,
it's my understanding that through installing and using Oracle-Text (schema CTXSYS) no additional licence costs arise (for Oracle Enterprise Edition).
I'm asking this question in this forum just to be sure that my understanding is not wrong...
Many thanks
JH

As far as I know this is correct.
Oracle Text is neither listed as an Entreprise Edition option in US price list:
http://www.oracle.com/us/corporate/pricing/technology-price-list-070617.pdf
nor in Licensing Information:
http://download.oracle.com/docs/cd/E11882_01/license.112/e10594/toc.htm .
Edited by: P. Forstmann on 9 août 2011 10:25

Find sys schema for imp database in 9i

Hi Experts,
Based on ORACLE rcommandation, I will take exp/imp to full database to other server ( it is only way based on source DB condition)
To avoid duplicated system objects, i run a sql to get a schema list
==============================
SQL> select owner from dba_objects group by owner order by
OWNER
CRYSTAL
CTXSYS
MDSYS
NWEKRANESES
ODM
ODM_MTR
OWNER
OE
OLAPSYS
ORDPLUGINS
ORDSYS
OUTLN
PIDLPASCUA
PM
PUBLIC
QS
QS_ADM
QS_CBADM
OWNER
QS_CS
QS_ES
QS_OS
QS_WS
SH
SYS
SYSTEM
WKSYS
WMSYS
XDB
32 rows selected.
SQL>
I am not sure which scheam is a system schema for oracle 9.0.06.0 in above SQL
So that I only need to emp/imo user data and programmeing codes.
by the way, Does sys schema stored user codes information or objects in there?
Thanks for your help!
JIM
Edited by: user589812 on Apr 22, 2009 12:28 PM

Thanks for your help.
I got lots of message as
Column : DESC[RIBE] {[schema.]object[@connect_identifier]}
IMP-00019: row rejected due to ORACLE error 1
IMP-00003: ORACLE error 1 encountered
ORA-00001: unique constraint (SYSTEM.HELP_TOPIC_SEQ) violated
Column : DESCRIBE
Column : 9
Column :
IMP-00019: row rejected due to ORACLE error 1
IMP-00003: ORACLE error 1 encountered
ORA-00001: unique constraint (SYSTEM.HELP_TOPIC_SEQ) violated
Column : DISCONNECT
Column : 1
Column :
IMP-00019: row rejected due to ORACLE error 1
IMP-00003: ORACLE error 1 encountered
ORA-00001: unique constraint (SYSTEM.HELP_TOPIC_SEQ) violated
Column : DISCONNECT
Column : 2
Column : DISCONNECT
IMP-00019: row rejected due to ORACLE error 1
IMP-00003: ORACLE error 1 encountered
ORA-00001: unique constraint (SYSTEM.HELP_TOPIC_SEQ) violated
Column : DISCONNECT
I am reviewing your paperlink that ia ver usefull.
As DBA_mike said, it seems there are a potential issue if user creates object by system account.
This is very old DB without archived and documents. we need to migreated to 10g/11i
Thanks
JIM

Export system or sys schema

If I am using imp/exp export schema system and sys, is it possible?

Girish Sharma wrote:
Sir,
As per your saying that SYS will not be included in export i tried following command and i got SYS schema exported:
In windows:
exp 'sys/pw@orcl as sysdba' owner=sys file=xx.dmp feedback=10 log=xx.dmp
In Linux:
expdp \'sys/pw@orcl as sysdba\' schemas=sys dumpfile=xx.dmp logfile=xx.logLike other has suggested, you can run exp/expdp doesn't mean you get it exported. See some example,
%exp sys owner=sys file=test.dmp
Username: sys as sysdba
Password:
Connected to: Oracle Database 10g Enterprise Edition
Release 10.2.0.3.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
Export done in US7ASCII character set and AL16UTF16 NCHAR character set
server uses AL32UTF8 character set (possible charset conversion)
About to export specified users ...
. exporting pre-schema procedural objects and actions
. exporting foreign function library names for user SYS
. exporting PUBLIC type synonyms
. exporting private type synonyms
. exporting object type definitions for user SYS
About to export SYS's objects ...
. exporting database links
. exporting sequence numbers
. exporting cluster definitions
. exporting synonyms
. exporting views
. exporting stored procedures
. exporting operators
. exporting referential integrity constraints
. exporting triggers
. exporting indextypes
. exporting bitmap, functional and extensible indexes
. exporting posttables actions
. exporting materialized views
. exporting snapshot logs
. exporting job queues
. exporting refresh groups and children
. exporting dimensions
. exporting post-schema procedural objects and actions
. exporting statistics
Export terminated successfully with warnings.As you can see no objects are listed as exported.
This Oracle metalink has this explained
Schema's CTXSYS, MDSYS and ORDSYS are Not Exported
Doc ID: Note:228482.1
Also if you check $ORACLE_HOME/rdbms/admin/catexp.sql
which is the script to Creates internal views for Export/Import utility
You will see
CREATE OR REPLACE VIEW exu81obj AS
        SELECT o$.*
        FROM    sys.obj$ o$, sys.user$ u$
        WHERE   BITAND(o$.flags, 16) != 16 AND
                /* Ignore recycle bin objects */
                BITAND(o$.flags, 128) != 128 AND
                o$.owner# = u$.user# AND
                u$.name NOT IN ('ORDSYS', 'MDSYS', 'CTXSYS', 'ORDPLUGINS',
                                'LBACSYS', 'XDB',   'SI_INFORMTN_SCHEMA',
                                'DIP',     'DMSYS', 'DBSNMP', 'EXFSYS',
                                'WMSYS')These database dictionary metadata schemas are deliberately excluded.
-hint- Maybe be by changing this script, you can get them included ;)
But don't take my word on that, changing DB dictionary is not supported in anyway.
>
Please quote your valuable suggestations because as per your saying i argued in a long debate with my friends that "we can not take export of sys's schema, because Ying sir is saying like that". I shall be highly informative on your feedback please.
I appreciate you take my word so seariously and I am glad I didn't let you down in this case.

Import from Database - how to restrict the list of schemas

This may be more of a general Oracle question, but the problem is showing up in OBIEE, so...
When running an Import from Database in the repository tool, I see a lot of schemas listed in the data source pane, like APEX_030200, CTXSYS, MDSYS, OLAPSYS, PUBLIC, SYS, and SYSTEM, in addition to the schema that I've used for the connection (TRAINING). There are a lot of other schemas in the database that are NOT shown in the import dialog.
Question 1: What's special about the schemas that I've mentioned above that causes them to always show up in the import dialog?
Question 2: How can I eliminate them from the import dialog, so that I see one and only one schema - TRAINING? What privileges or roles must I grant or revoke so that when my connecion pool uses the TRAINING schema, then TRAINING is the only schema listed on the import dialog?
Thanks!

to see the list of schemas
select username from dba_users
select distinct owner from dba_tables;{code}to know on which DB you are
{code:java}select instance_name from v$instance;{code}
Edited by: Leo Anderson on 7 sept. 2008 19:37

10g required schemas/owners for htmldb

Hi
I installed 10g recently and my question is:
In a new database, which schema owners are required to run htmldb. I imagine CTXSYS,MDSYS, WKSYS among others may be required. Can you confirm with me what owner accounts need to be present and unlocked for htmldb to operate?
Thanks as usual
Bill

Bill,
Non of the schemas you list are required nor do they need to be unlocked for HTML DB to install or operate successfully.
Sergio

EA1 error viewing XML schemas

When I want to view the XML schemas of MDSYS I get the error ORA-22835 . I am not connected as MDSYS.
This means that the buffer was to small for conversion from clob to char or blob to raw conversion.
After this error I see only 'No text available'.
I use Oracle version 11:
SQL> select * from v$version;
BANNER
Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
PL/SQL Release 11.1.0.6.0 - Production
CORE 11.1.0.6.0 Production
TNS for 32-bit Windows: Version 11.1.0.6.0 - Production
NLSRTL Version 11.1.0.6.0 - Production

Do you still have enough disk space available on your file system to store the different xml-facts the RuleAuthor will create for you?

Mdsys corruption

This happened after I tried to do a datapump export of mdsys. Something got corrupted and now I can't use the datapump or drop users:
SQL> drop user mark cascade;
drop user mark cascade
ERROR at line 1:
ORA-04098: trigger 'MDSYS.SDO_TOPO_DROP_FTBL' is invalid and failed
re-validation
I've tried to recompile ever function and package that belongs to mdsys, and I've tried re-running the catmd.sql script. No improvement. Help?

Weird. Especially given the sequence you describe.
(Although I'm not quite sure why anyone would want to export any Oracle-provided schemas - especially since export is not considered part of a backup strategy, and schemas like MDSYS should never be updated, except by patch. Oh well ... a separate discussion perhaps?)
Some questions about your situation...
1) 10.1, 10.2? ... patch level?
2) Operating system?
3) Is the user MDSYS locked or unlocked?
4) Are you using the Spatial Topology capability?
5) Is this a production or a test system?
6) Have you opened a Service Request or checked in the Spatial forum?

Questions for Export Full dump

According to Oracle 10.1 Utility Document, the Full Export Dump option has following restriction: "The following system schemas are not exported as part of a Full export because the metadata they contain is exported as part of other objects in the dump file set: SYS, ORDSYS, ORDPLUGINS, CTXSYS, MDSYS, LBACSYS, and XDB." So what this differentiates with using the export with schema option, if there is only one user defined schema (ex HR). In other words, if I use the schema=hr in export, does it also included the part of SYS, ORDSYS...all system objects. I am kind confused. I want to export dump the full database but not parts of my user schema.

Hi,
• Full – exports the contents of the entire database. This can be time consuming and requires substantial disk space, depending on the size of the database.
• User – exports all objects within a particular schema. If user SCOTT performs a user mode export, all of the objects belonging to SCOTT will be exported.
http://www.remote-dba.net/teas_rem_util7.htm
Cheers

Migration from 10g to 12c using data pump

hi there, while I've used data pump at the schema level before, I'm rather new at full database imports.
we are attempting a full database migration from 10.2.0.4 to 12c using the full database data pump method over db link.
the DBA has advised that we avoid moving SYSTEM and SYSAUX objects. but initially when reviewing the documentation it appeared that these objects would not be exported from the target system given TRANSPORTABLE=NEVER. can someone confirm this? the export/import log refers to objects that I believed would not be targeted:
23-FEB-15 19:41:11.684:
Estimated 3718 TABLE_DATA objects in 77 seconds
23-FEB-15 19:41:12.450: Total estimation using BLOCKS method: 52.93 GB
23-FEB-15 19:41:14.058: Processing object type DATABASE_EXPORT/TABLESPACE
23-FEB-15 20:10:33.185: ORA-31684: Object type TABLESPACE:"UNDOTBS1" already exists
23-FEB-15 20:10:33.185: ORA-31684: Object type TABLESPACE:"SYSAUX" already exists
23-FEB-15 20:10:33.185: ORA-31684: Object type TABLESPACE:"TEMP" already exists
23-FEB-15 20:10:33.185: ORA-31684: Object type TABLESPACE:"USERS" already exists
23-FEB-15 20:10:33.200:
Completed 96 TABLESPACE objects in 1759 seconds
23-FEB-15 20:10:33.208: Processing object type DATABASE_EXPORT/PROFILE
23-FEB-15 20:10:33.445:
Completed 7 PROFILE objects in 1 seconds
23-FEB-15 20:10:33.453: Processing object type DATABASE_EXPORT/SYS_USER/USER
23-FEB-15 20:10:33.842:
Completed 1 USER objects in 0 seconds
23-FEB-15 20:10:33.852: Processing object type DATABASE_EXPORT/SCHEMA/USER
23-FEB-15 20:10:52.368: ORA-31684: Object type USER:"OUTLN" already exists
23-FEB-15 20:10:52.368: ORA-31684: Object type USER:"ANONYMOUS" already exists
23-FEB-15 20:10:52.368: ORA-31684: Object type USER:"OLAPSYS" already exists
23-FEB-15 20:10:52.368: ORA-31684: Object type USER:"MDDATA" already exists
23-FEB-15 20:10:52.368: ORA-31684: Object type USER:"SCOTT" already exists
23-FEB-15 20:10:52.368: ORA-31684: Object type USER:"LLTEST" already exists
23-FEB-15 20:10:52.372:
Completed 1140 USER objects in 19 seconds
23-FEB-15 20:10:52.375: Processing object type DATABASE_EXPORT/ROLE
23-FEB-15 20:10:55.255: ORA-31684: Object type ROLE:"SELECT_CATALOG_ROLE" already exists
23-FEB-15 20:10:55.255: ORA-31684: Object type ROLE:"EXECUTE_CATALOG_ROLE" already exists
23-FEB-15 20:10:55.255: ORA-31684: Object type ROLE:"DELETE_CATALOG_ROLE" already exists
23-FEB-15 20:10:55.256: ORA-31684: Object type ROLE:"RECOVERY_CATALOG_OWNER" already exists
any insight most appreciated.

Schema's SYS,CTXSYS, MDSYS and ORDSYS are Not Exported using exp/expdp
Doc ID: Note:228482.1
I suppose he already installed a software 12c and created a database itseems - So when you imported you might have this "already exists"
Whenever the database is created and software installed by default system,sys,sysaux will be created.

10g to 11gR2 Upgrade using Data Pump Import

Hi,
I am intending to move a 10g database from one windows server to another. However there is also a requirement to upgrade this database to 11gR2. Therefore I was going to combine the 2 in one movement by -
1. take a full data pump export of the source 10g database
2. create a new empty 11g database on the target environment
3. import the dump file into the target database
However I have a couple of queries running over in my mind about this approach -
Q1. What happens with the SYSTEM and SYS objects from SYSTEM and SYSAUX during the import ? Given that I will have in effect already created a new dictionary on the empty target database - will any import of SYSTEM or SYS simply produce errror messages which should be ignored ?
Q2. should I use EXCLUDE on SYS and SYSTEM ( is this EXCLUDE better on the export or import side ) ?
Q3. what happens if there are things such as scheduled jobs etc on the source system - since these would be stored in SYSTEM owned tables, how would I bring these across to the new target 11g database ?
thanks,
Jim

Jim Thompson wrote:
Hi,
I am intending to move a 10g database from one windows server to another. However there is also a requirement to upgrade this database to 11gR2. Therefore I was going to combine the 2 in one movement by -
1. take a full data pump export of the source 10g database
2. create a new empty 11g database on the target environment
3. import the dump file into the target database
However I have a couple of queries running over in my mind about this approach -
Q1. What happens with the SYSTEM and SYS objects from SYSTEM and SYSAUX during the import ? Given that I will have in effect already created a new dictionary on the empty target database - will any import of SYSTEM or SYS simply produce errror messages which should be ignored ?
You wont get error related to system , sysaux tablespace bacsei these wont be exported at all. Schemas like "SYS, CTXSYS, MDSYS and ORDSYS" are never exported using datapump. Thats why oracle reommends not to create any objects under sys,system schema.
Q2. should I use EXCLUDE on SYS and SYSTEM ( is this EXCLUDE better on the export or import side ) ?
Not required, as datadictionary schemas wont be exported, so spcefying EXCLUDE wont do anything
Q3. what happens if there are things such as scheduled jobs etc on the source system - since these would be stored in SYSTEM owned tables, how would I bring these across to the new target 11g database ?
DDL will get export and imported into new database. For example if you have schema A and you had defined job whos owner is A, then while importing this information also gets imported. For user defined Jobs there are view like USER_SCHEDULER_JOBS etc, So dont worry about the user jobs, these will be created.
Also see
MOS note - Schema's CTXSYS, MDSYS and ORDSYS are Not Exported [ID 228482.1]
Export system or sys schema
I also run following test in my db which shows i cannt export the objects under sys schema;
SQL> show user
USER is "SYS"
SQL> create table pump (id number);
Table created.
SQL> insert into pump values (1);
1 row created.
SQL> insert into pump values (2);
1 row created.
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Pr
oduction
With the Partitioning, OLAP, Data Mining and Real Application Testing options
C:\Documents and Settings\rnagi\My Documents\Ranjit Doc\Performance\SQL>expdp tables=sys.pump logfile=test.log
Export: Release 11.2.0.1.0 - Production on Mon Feb 27 18:11:29 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
Username: / as sysdba
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Produc
tion
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Starting "SYS"."SYS_EXPORT_TABLE_01": /******** AS SYSDBA tables=sys.pump logfi
le=test.log
Estimate in progress using BLOCKS method...
Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
Total estimation using BLOCKS method: 0 KB
*ORA-39166: Object SYS.PUMP was not found.*
*ORA-31655: no data or metadata objects selected for job*
*Job "SYS"."SYS_EXPORT_TABLE_01" completed with 2 error(s) at 18:11:57*

Skip table during automatic standby database

We would like to skip a table from being replicated into a standby database.
We do the following on the standby database
startup nomount;
alter database mount standby database;
recover automatic standby database;
and cancel the process.
and then bring the standby database up to date at night for example.
And during the day we would like to use it as a report database, to see if that is possible.
To be able to do that, we do this:
alter database open read only;
But the problem is, there is one reporting table that we do not like to replicate.
We want to create a database link in the standby (report) database, that links to the table in the live database.
Because we need that data from the live database to be update to date in that table.
That table does not contain data that needs to be stored, so it is no problem if it does not end up in the standby report database.
Problem is that we cannot get Oracle to skip to replicate this REPORTPARAM table.
We tried this
execute dbms_logstdby.skip(stmt => 'SCHEMA_DDL',
schema_name => 'ABSSOLUTE',
object_name => 'REPORTPARAM',
use_like => FALSE);
exectue dbms_logstdby.skip(stmt => 'DML',
schema_name => 'ABSSOLUTE',
object_name => 'REPORTPARAM',
use_like => FALSE);
And when we check SELECT * FROM DBA_LOGSTDBY_SKIP
we see the values in there.
But still this table is being replicated.
How can we stop Oracle from doing that?
( And can when we stopped Oracle from doing that, create a database link with alias to the same table in the live database,
that will be the next step. )

This is the output from select * from dba_logstdby_skip
ERROR     STATEMENT_OPT     OWNER     NAME     USE_LIKE     ESC     PROC
N     SCHEMA_DDL     ABSSOLUTE     REPORTPARAM     N
N     DML          ABSSOLUTE     REPORTPARAM     N
N     INTERNAL      SCHEMA     SI_INFORMTN_SCHEMA     %     N
N     INTERNAL     SCHEMA     APEX_030200     %     N
N     INTERNAL     SCHEMA     XS$NULL     %     N
N     INTERNAL     SCHEMA     ORDPLUGINS     %     N
N     INTERNAL     SCHEMA     APPQOSSYS     %     N
N     INTERNAL     SCHEMA     ORACLE_OCM     %     N
N     INTERNAL     SCHEMA     XDB     %     N
N     INTERNAL     SCHEMA     WMSYS     %     N
N     INTERNAL     SCHEMA     DIP     %     N
N     INTERNAL     SCHEMA     OUTLN     %     N
N     INTERNAL     SCHEMA     EXFSYS     %     N
N     INTERNAL     SCHEMA     ANONYMOUS     %     N
N     INTERNAL     SCHEMA     CTXSYS     %     N
N     INTERNAL     SCHEMA     ORDSYS     %     N
N     INTERNAL     SCHEMA     ORDDATA     %     N
N     INTERNAL     SCHEMA     MDSYS     %     N
N     INTERNAL     SCHEMA     SYSTEM     %     N
N     INTERNAL     SCHEMA     SYS     %     N
N     INTERNAL     SCHEMA     MGMT_VIEW     %     N
N     INTERNAL     SCHEMA     SYSMAN     %     N
N     INTERNAL     SCHEMA     DBSNMP     %     N
The second select however
SELECT APPLIED_SCN, NEWEST_SCN FROM DBA_LOGSTDBY_PROGRESS;
returns no rows.

Script to create synonym and grants

How I can create DDL list of synonym & grants for particular schema.

Hi Anil
You can connect as SYS and run the following scripts:
PUBLIC SYNONYMS:
set feedback off
set trimspool on
set pagesize 1000
set linesize 1000
set heading   off
spool public_synonyms.txt
select      'create public synonym ' || table_name || ' for ' || table_owner || '.' || table_name || ';'
from        dba_synonyms
where
            owner='PUBLIC'
--and      table_owner not in ('SYS', 'SYSTEM')
order by
     table_owner;
spool off
exit
GRANTS:
set feedback off
set trimspool on
set pagesize 1000
set linesize 1000
set heading   off
spool grants.txt
select 'GRANT '||granted_role||' TO '||grantee||' ;' from dba_role_privs
--where grantee not in
--('AURORA$JIS$UTILITY$','DBA','DBSNMP','EXECUTE_CATALOG_ROLE','EXP_FULL_DATABASE',
--'IMP_FULL_DATABASE','OEM_MONITOR','ORDPLUGINS','OSE$HTTP$ADMIN',
--'SELECT_CATALOG_ROLE','SYS','SYSTEM','WMSYS','CTXSYS','MDSYS','ORDSYS','OUTLN')
spool off
exitHope it helps.
Regards
Zaffer Khan

How to deinstall interMedia?

I'm managing an Oracle8i Db where interMedia was installed for an error.
Now the Db instance have many schemas used by interMedia (CTXSYS, MDSYS, ORDPLUGINS and ORDSYS).
I'd like to disinstall/deactivate interMedia option in this instance?
- Do I have to manually drop interMedia schema?
- Do I have to disinstall interMedia Software form Universal Installer?
How should I do???
null

I think your only option is to use remove it with Universal Installer.

SYSAUX tablespace resize/shrink

Hi All,
I'm using 11g SE on Linux, and SYSAUX tablespace has grown too large (32Gb). I've reclaimed a space and the question is Is there any chance to resize this tablespace back to small size (let's say to 5Gb)?
I'll appreciate any help.
Thank you.

Hi,
Here it is an output. I've removed some stuff to fit the message limit.
~~~~~~~~~~~~~~~
AWR INFO Report
~~~~~~~~~~~~~~~
Report generated at 10:36:09 on May 29, 2013 ( Wednesday ) in Timezone +01:00
Warning: Non Default AWR Setting!
Snapshot interval is 60 minutes and Retention is 8 days
       DB_ID DB_NAME   HOST_PLATFORM                             INST STARTUP_TIME      LAST_ASH_SID PAR
* 182010396 PROD      db01p2.db.mydomain.com - Linux x86 6     2 14:54:16 (03/26)             0 YES
                       4-bit
(I) AWR Snapshots Information
(1a) SYSAUX usage - Schema breakdown (dba_segments)
|
| Total SYSAUX size                      1,790.6 MB ( 5% of 32,768.0 MB MAX with AUTOEXTEND ON )
|
| Schema SYS          occupies          1,245.0 MB ( 69.5% )
| Schema XDB          occupies            157.6 MB (   8.8% )
| Schema PERFSTAT     occupies            151.8 MB (   8.5% )
| Schema APEX_030200 occupies             77.4 MB (   4.3% )
| Schema MDSYS        occupies             65.8 MB (   3.7% )
| Schema SYSMAN       occupies             45.3 MB (   2.5% )
| Schema SYSTEM       occupies             13.7 MB (   0.8% )
| Schema ORDDATA      occupies             13.6 MB (   0.8% )
| Schema OLAPSYS      occupies              5.1 MB (   0.3% )
| Schema DBSNMP       occupies              4.1 MB (   0.2% )
| Schema EXFSYS       occupies              3.6 MB (   0.2% )
| Schema CTXSYS       occupies              3.6 MB (   0.2% )
| Schema WMSYS        occupies              3.5 MB (   0.2% )
| Schema ORDSYS       occupies              0.4 MB (   0.0% )
|
(1b) SYSAUX occupants space usage (v$sysaux_occupants)
|
| Occupant Name        Schema Name               Space Usage
| -------------------- -------------------- ----------------
| SM/AWR               SYS                          888.0 MB
| SM/OPTSTAT           SYS                          266.6 MB
| XDB                  XDB                          157.6 MB
| STATSPACK            PERFSTAT                     151.8 MB
| SDO                  MDSYS                         65.8 MB
| EM                   SYSMAN                        45.3 MB
| AO                   SYS                           36.3 MB
| XSOQHIST             SYS                           36.3 MB
| ORDIM/ORDDATA        ORDDATA                       13.6 MB
| LOGMNR               SYSTEM                        12.3 MB
| SM/ADVISOR           SYS                           11.3 MB
| JOB_SCHEDULER        SYS                            9.9 MB
| SM/OTHER             SYS                            7.1 MB
| XSAMD                OLAPSYS                        5.1 MB
| EM_MONITORING_USER   DBSNMP                         4.1 MB
| EXPRESSION_FILTER    EXFSYS                         3.6 MB
| TEXT                 CTXSYS                         3.6 MB
| WM                   WMSYS                          3.5 MB
| SMON_SCN_TIME        SYS                            3.3 MB
| SQL_MANAGEMENT_BASE SYS                            1.7 MB
| PL/SCOPE             SYS                            1.6 MB
| LOGSTDBY             SYSTEM                         1.4 MB
| STREAMS              SYS                            1.0 MB
| ORDIM                ORDSYS                         0.4 MB
| AUTO_TASK            SYS                            0.3 MB
| AUDIT_TABLES         SYS                            0.0 MB
| ORDIM/ORDPLUGINS     ORDPLUGINS                     0.0 MB
| ORDIM/SI_INFORMTN_SC SI_INFORMTN_SCHEMA             0.0 MB
| TSM                  TSMSYS                         0.0 MB
| ULTRASEARCH          WKSYS                          0.0 MB
| ULTRASEARCH_DEMO_USE WK_TEST                        0.0 MB
|
| Others (Unaccounted space)                         59.4 MB
|
(1c) SYSAUX usage - Unregistered Schemas
| This section displays schemas that are not registered
| in V$SYSAUX_OCCUPANTS
|
| Schema APEX_030200 occupies             77.4 MB
|
| Total space                               77.4 MB
|
(1d) SYSAUX usage - Unaccounted space in registered schemas
|
| This section displays unaccounted space in the registered
| schemas of V$SYSAUX_OCCUPANTS.
|
| Unaccounted space in SYS/SYSTEM          -18.1 MB
|
| Total space                              -18.1 MB
|
(2) Size estimates for AWR snapshots
|
| Estimates based on 60 mins snapshot INTERVAL:
|    AWR size/day                           53.0 MB (2,262 K/snap * 24 snaps/day)
|    AWR size/wk                           371.1 MB (size_per_day * 7) per instance
|    AWR size/wk                         1,484.4 MB (size_per_day * 7) per database
|
| Estimates based on 12 snaps in past 24 hours:
|    AWR size/day                           26.5 MB (2,262 K/snap and 12 snaps in past 24 hours)
|    AWR size/wk                           185.6 MB (size_per_day * 7) per instance
|    AWR size/wk                           742.2 MB (size_per_day * 7) per database
|
(3a) Space usage by AWR components (per database)
COMPONENT        MB % AWR KB_PER_SNAP MB_PER_DAY MB_PER_WEEK TABLE% : INDEX%
FIXED         860.8   96.9        2,193       25.7       179.9    55% : 45%
SPACE          18.1    2.0           46        0.5         3.8    59% : 41%
EVENTS          3.5    0.4            9        0.1         0.7    50% : 50%
SQL             2.9    0.3            7        0.1         0.6    37% : 63%
ASH             1.5    0.2            4        0.0         0.3    50% : 50%
RAC             0.6    0.1            2        0.0         0.1    50% : 50%
SQLTEXT         0.1    0.0            0        0.0         0.0    50% : 50%
SQLPLAN         0.1    0.0            0        0.0         0.0    50% : 50%
SQLBIND         0.1    0.0            0        0.0         0.0    50% : 50%
(3b) Space usage within AWR Components (> 500K)
COMPONENT        MB SEGMENT_NAME - % SPACE_USED                                           SEGMENT_TYPE
FIXED         336.0 WRH$_SYSMETRIC_HISTORY                                        - 12% TABLE
FIXED         296.0 WRH$_SYSMETRIC_HISTORY_INDEX                                  - 18% INDEX
FIXED          88.0 WRH$_SYSMETRIC_SUMMARY                                        - 10% TABLE
FIXED          42.0 WRH$_SYSMETRIC_SUMMARY_INDEX                                  - 18% INDEX
FIXED          24.0 WRH$_WAITCLASSMETRIC_HISTORY                                  - 21% TABLE
FIXED          21.0 WRH$_WAITCLASSMETRIC_HIST_IND                                 - 17% INDEX
FIXED          16.0 WRM$_SNAPSHOT_DETAILS_INDEX                                   - 80% INDEX
FIXED          10.0 WRM$_SNAPSHOT_DETAILS                                         - 92% TABLE
SPACE           0.9 WRH$_SEG_STAT.WRH$_SEG_ST_182010396_12506                     - 82% TABLE PARTITION
SPACE           0.9 WRH$_SEG_STAT.WRH$_SEG_ST_182010396_12530                     - 84% TABLE PARTITION
SPACE           0.8 WRH$_SEG_STAT.WRH$_SEG_ST_182010396_12458                     - 89% TABLE PARTITION
SPACE           0.8 WRH$_SEG_STAT.WRH$_SEG_ST_182010396_12650                     - 88% TABLE PARTITION
SPACE           0.8 WRH$_SEG_STAT.WRH$_SEG_ST_182010396_12626                     - 87% TABLE PARTITION
SPACE           0.8 WRH$_SEG_STAT.WRH$_SEG_ST_182010396_12602                     - 86% TABLE PARTITION
SPACE           0.8 WRH$_SEG_STAT.WRH$_SEG_ST_182010396_12578                     - 87% TABLE PARTITION
SPACE           0.8 WRH$_SEG_STAT.WRH$_SEG_ST_182010396_12482                     - 89% TABLE PARTITION
SPACE           0.8 WRH$_SEG_STAT.WRH$_SEG_ST_182010396_12554                     - 89% TABLE PARTITION
SPACE           0.7 WRH$_SEG_STAT_OBJ                                             - 46% TABLE
SPACE           0.6 WRH$_SEG_STAT_OBJ_INDEX                                       - 22% INDEX
SPACE           0.6 WRH$_SEG_STAT_OBJ_PK                                          - 26% INDEX
SPACE           0.5 WRH$_SEG_STAT_PK.WRH$_SEG_ST_182010396_12554                  - 63% INDEX PARTITION
SPACE           0.5 WRH$_SEG_STAT_PK.WRH$_SEG_ST_182010396_12626                  - 51% INDEX PARTITION
(4) Space usage by non-AWR components (> 500K)
COMPONENT        MB SEGMENT_NAME                                                          SEGMENT_TYPE
NON_AWR       104.0 SYS.I_WRI$_OPTSTAT_H_OBJ#_ICOL#_ST                                    INDEX
NON_AWR        80.0 SYS.WRI$_OPTSTAT_HISTGRM_HISTORY                                      TABLE
NON_AWR        53.2 XDB.SYS_LOB0000057465C00025$$                                         LOBSEGMENT
NON_AWR        50.0 SYS.I_WRI$_OPTSTAT_H_ST                                               INDEX
NON_AWR        18.0 MDSYS.SYS_LOB0000064008C00006$$                                       LOBSEGMENT
NON_AWR        16.1 SYS.SYS_LOB0000065858C00004$$                                         LOBSEGMENT
NON_AWR        13.0 SYS.WRI$_OPTSTAT_HISTHEAD_HISTORY                                     TABLE
NON_AWR         9.0 SYS.I_WRI$_OPTSTAT_HH_OBJ_ICOL_ST                                     INDEX
NON_AWR         8.0 XDB.XDB$RESOURCE                                                      TABLE
NON_AWR         7.2 SYS.SYS_LOB0000065843C00004$$                                         LOBSEGMENT
NON_AWR         7.0 MDSYS.SDO_CS_SRS                                                      TABLE
NON_AWR         5.0 SYS.SCHEDULER$_EVENT_LOG                                              TABLE
NON_AWR         5.0 APEX_030200.WWV_FLOW_DICTIONARY$CAPED                                 INDEX
NON_AWR         5.0 PERFSTAT.STATS$SQL_PLAN                                               TABLE
NON_AWR         5.0 PERFSTAT.STATS$SQL_PLAN_USAGE                                         TABLE
NON_AWR         5.0 PERFSTAT.STATS$SQLTEXT                                                TABLE
NON_AWR         5.0 APEX_030200.WWV_FLOW_PAGE_PLUGS                                       TABLE
NON_AWR         5.0 APEX_030200.WWV_FLOW_STEP_ITEMS                                       TABLE
NON_AWR         4.2 SYS.SYS_LOB0000065848C00004$$                                         LOBSEGMENT
NON_AWR         4.0 APEX_030200.WWV_FLOW_DICTIONARY$                                      TABLE
NON_AWR         4.0 SYSTEM.SYS_LOB0000001147C00009$$                                      LOBSEGMENT
NON_AWR         4.0 SYS.SCHEDULER$_INSTANCE_PK                                            INDEX
NON_AWR         4.0 SYS.I_WRI$_OPTSTAT_HH_ST                                              INDEX
NON_AWR         3.2 SYS.SYS_LOB0000065838C00004$$                                         LOBSEGMENT
NON_AWR         3.0 XDB.XDB$H_INDEX                                                       TABLE
(5a) AWR snapshots - last 50
Total snapshots in DB 182010396 Instance 3 = 201
Total snapshots in DB 182010396 Instance 2 = 201
      DBID    SNAP_ID INST FLUSH_ELAPSED        ENDTM             STARTUP_TIME      STATUS ERRCNT
182010396      12678     2 +00000 00:00:00.1    08:00:41 (05/29) 14:54:16 (03/26)       0      0
182010396      12678     3 +00000 00:00:00.5    08:00:41 (05/29) 14:56:33 (03/26)       0      0
182010396      12679     2 +00000 00:00:00.1    09:00:59 (05/29) 14:54:16 (03/26)       0      0
182010396      12679     3 +00000 00:00:00.1    09:00:59 (05/29) 14:56:33 (03/26)       0      0
182010396      12680     2 +00000 00:00:00.9    10:00:10 (05/29) 14:54:16 (03/26)       0      0
182010396      12680     3 +00000 00:00:00.1    10:00:10 (05/29) 14:56:33 (03/26)       0      0
(5b) AWR snapshots with errors or invalid
no rows selected
(5c) AWR snapshots -- OLDEST Non-Baselined snapshots
      DBID INST    SNAP_ID ENDTM             STATUS ERROR_COUNT
182010396     2      12480 02:00:25 (05/21)       0           0
(6) AWR Control Settings - interval, retention
       DBID LSNAPID LSPLITID LSNAPTIME      LPURGETIME      FLAG INTERVAL          RETENTION         VRSN
182010396    12680    12671 05/29 10:00:11 05/29 01:13:59     2 +00000 01:00:00.0 +00008 00:00:00.0    5
(7a) AWR Contents - row counts for each snapshots
   SNAP_ID INST        ASH        SQL      SQBND      FILES      SEGST     SYSEVT
     12656     2          0          0          0          0        104          0
     12679     2          0          0          0          0        107          0
   SNAP_ID INST        ASH        SQL      SQBND      FILES      SEGST     SYSEVT
     12679     3          0          0          0          0        113          0
     12680     2          0          0          0          0        110          0
     12680     3          0          0          0          0        109          0
(7b) AWR Contents - average row counts per snapshot
SNAP_COUNT INST        ASH    SQLSTAT    SQLBIND      FILES    SEGSTAT   SYSEVENT
       201     3          0          0          0          0     108.27          0
       201     2          0          0          0          0     109.23          0
(7c) AWR total item counts - names, text, plans
   SQLTEXT    SQLPLAN   SQLBMETA     SEGOBJ   DATAFILE   TEMPFILE
         0          0          0       2784          0          0
(II) Advisor Framework Info
(1) Advisor Tasks - Last 50
OWNER/ADVISOR TASK_ID/NAME                     CREATED          EXE_DURATN EXE_CREATN HOW_C STATUS
SYS/SQL Tuning 1/SYS_AUTO_SQL_TUNING_TASK       09:52:13 (09/17)                       AUTO INITIAL
SYS/Segment Ad 10161/SYS_AUTO_SPCADV_5215001005 00:15:52 (05/10)      2,925      2,925 CMD   COMPLETED
               2013
SYS/Segment Ad 10162/SYS_AUTO_SPCADV_3804011005 01:04:38 (05/10)         50         50 CMD   COMPLETED
(2) Advisor Task - Oldest 5
OWNER/ADVISOR TASK_ID/NAME                     CREATED          EXE_DURATN EXE_CREATN HOW_C STATUS
SYS/Segment Ad 9980/SYS_AUTO_SPCADV_04002329042 23:00:04 (04/29)        426        427 CMD   COMPLETED
               013
SYS/Segment Ad 9990/SYS_AUTO_SPCADV_16002330042 23:00:16 (04/30)      5,519      5,519 CMD   COMPLETED
               013
SYS/Segment Ad 9991/SYS_AUTO_SPCADV_16320001052 00:32:17 (05/01)      2,831      2,831 CMD   COMPLETED
               013
SYS/Segment Ad 9992/SYS_AUTO_SPCADV_29190101052 01:19:29 (05/01)         80         80 CMD   COMPLETED
               013
SYS/Segment Ad 10000/SYS_AUTO_SPCADV_1300230105 23:00:13 (05/01)        445        445 CMD   COMPLETED
               2013
(3) Advisor Tasks With Errors - Last 50
OWNER/ADVISOR TASK_ID/NAME                     CREATED          EXE_DURATN EXE_CREATN HOW_C STATUS
TASK_DESC
ERROR_MSG
SYS/SQL Tuning 1/SYS_AUTO_SQL_TUNING_TASK       09:52:13 (09/17)                       AUTO INITIAL
Description: Automatic SQL Tuning Task
Error Msg :
(III) ASH Usage Info
(1a) ASH histogram (past 3 days)
(1b) ASH histogram (past 1 day)
(2a) ASH details (past 3 days)
(2b) ASH details (past 1 day)
(2c) ASH sessions (Fg Vs Bg) (past 1 day across all instances in RAC)
Foreground %
Background %
MMNL %
End of Report

Schema CTXSYS, MDSYS

Similar Messages

Maybe you are looking for