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

Similar Messages

  • 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

  • SYS, SYSTEM and SYSAUX when full database refresh.

    I took full export from database using below command
    expdp "'/ as sysdba'" full=Y directory=DPUMP_DIR dumpfile=expdp_11032011.dmp logfile=expdp_11032011.log Now, I need to import this file to an other database.
    When do schema refresh we usually drop all the object in that schema and start refresh, but when doing fullback up, do we need to drop all user?
    what about sys, system and sysaux user?

    user3636719 wrote:
    So, the tables in the SYS and SYSTEM will remain same when we refresh?
    Structure will not be modified but contents will be automatically modified when DLL is executed when importing.
    And do we have to drop other user before we import?Applications schemas that you have created should be dropped. In general don't modify any schema that is directly managed by Oracle such as SYS or SYSTEM or any schema used by some database option like Oracle Text, Oracle Spatial, etc.

  • 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 ... 

  • Tablespace management system and sysaux size.. a concern..

    Hi mates,
    I have the report of my tablespace as thus:
    FILE_NAME TABLESPACE_NAME STA Total MB % Free Aext
    /usr/lib/oracle/xe/oradata/XE/MD MDATE AVA 196.608 13.57 YES
    ATE.dbf
    /usr/lib/oracle/xe/oradata/XE/SL SLIPSTREAM AVA 327.680 17.54 YES
    IPSTREAM.dbf
    /usr/lib/oracle/xe/oradata/XE/sy SYSAUX AVA 542.720 1.77 YES
    saux.dbf
    /usr/lib/oracle/xe/oradata/XE/sy SYSTEM AVA 378.880 1.69 YES
    stem.dbf
    /usr/lib/oracle/xe/oradata/XE/TX TXCD AVA 131.072 99.46 YES
    CD.dbf
    /usr/lib/oracle/xe/oradata/XE/un UNDO AVA 1,048.576 90.92 NO
    do
    /usr/lib/oracle/xe/oradata/XE/us USERS AVA 102.400 98.38 YES
    ers.dbf
    Can you pls tell me if the size of the sysaux and system tablespace should be a concern as I have freespace of 1.69 and 1.77%.
    Thanxxxx.
    Kenny

    A datafile may not be able to resize (file system full). And resizing it may cause file fragmentation of that file (on that file system).
    I prefer to add a new file, e.g.
    ALTER TABLESPACE <tablespace> ADD DATAFILE [<filename>] SIZE <size>
    When using ASM, the filename is determined (per OFA standards) by ASM itself. No need for the DBA to concern him/herself with directory structures and filenames.
    By the way, the topic of this forum is SQL and PL/SQL - not database administration. I suggest that in future you post questions like this to the Database forum instead.

  • System and sysaux file block corruption

    Errors in file /u01/app/oracle/diag/rdbms/pdent/pdent/trace/pdent_smon_3135.trc:
    ORA-00604: error occurred at recursive SQL level 1
    ORA-01578: ORACLE data block corrupted (file # 1, block # 91607)
    ORA-01110: data file 1: '/u01/app/oracle/oradata/pdent/system01.dbf'
    I am unable to take r man backup, as well as export using datapump. i tried to recover it using rman blockrecover but still same. here is detail
    SQL> SELECT * FROM V$DATABASE_BLOCK_CORRUPTION;
    FILE# BLOCK# BLOCKS CORRUPTION_CHANGE# CORRUPTIO
    1 91607 1 0 CHECKSUM
    2 58710 1 0 CHECKSUM
    5 1202316 1 0 CHECKSUM
    SQL> SELECT
    tablespace_name,
    segment_type,
    owner,
    segment_name
    FROM dba_extents
    WHERE file_id = 1
    AND BETWEEN block_id AND block_id + blocks - 1; 2 3 4 5 6 7 8
    TABLESPACE_NAME SEGMENT_TYPE OWNER
    SEGMENT_NAME
    SYSTEM INDEX SYS
    I_OBJ2
    alter system dump datafile 1 block 344;
    SQL> SELECT
    tablespace_name,
    segment_type,
    owner,
    segment_name
    FROM dba_extents
    WHERE file_id = 2
    AND 58710 BETWEEN block_id AND block_id + blocks - 1; 2 3 4 5 6 7 8
    TABLESPACE_NAME SEGMENT_TYPE OWNER
    SEGMENT_NAME
    SYSAUX INDEX PARTITION SYS
    WRH$_OSSTAT_PK
    SQL> ALTER INDEX I_OBJ2 REBUILD ONLINE;
    ALTER INDEX I_OBJ2 REBUILD ONLINE
    ERROR at line 1:
    ORA-00701: object necessary for warmstarting database cannot be altered
    need immediate help.
    thanks in advance

    user11914238 wrote:
    Errors in file /u01/app/oracle/diag/rdbms/pdent/pdent/trace/pdent_smon_3135.trc:
    ORA-00604: error occurred at recursive SQL level 1
    ORA-01578: ORACLE data block corrupted (file # 1, block # 91607)
    ORA-01110: data file 1: '/u01/app/oracle/oradata/pdent/system01.dbf'
    I am unable to take r man backup, as well as export using datapump. i tried to recover it using rman blockrecover but still same. here is detail
    SQL> SELECT * FROM V$DATABASE_BLOCK_CORRUPTION;
    FILE# BLOCK# BLOCKS CORRUPTION_CHANGE# CORRUPTIO
    1 91607 1 0 CHECKSUM
    2 58710 1 0 CHECKSUM
    5 1202316 1 0 CHECKSUM
    SQL> SELECT
    tablespace_name,
    segment_type,
    owner,
    segment_name
    FROM dba_extents
    WHERE file_id = 1
    AND BETWEEN block_id AND block_id + blocks - 1; 2 3 4 5 6 7 8
    TABLESPACE_NAME SEGMENT_TYPE OWNER
    SEGMENT_NAME
    SYSTEM INDEX SYS
    I_OBJ2
    alter system dump datafile 1 block 344;
    SQL> SELECT
    tablespace_name,
    segment_type,
    owner,
    segment_name
    FROM dba_extents
    WHERE file_id = 2
    AND 58710 BETWEEN block_id AND block_id + blocks - 1; 2 3 4 5 6 7 8
    TABLESPACE_NAME SEGMENT_TYPE OWNER
    SEGMENT_NAME
    SYSAUX INDEX PARTITION SYS
    WRH$_OSSTAT_PK
    SQL> ALTER INDEX I_OBJ2 REBUILD ONLINE;
    ALTER INDEX I_OBJ2 REBUILD ONLINE
    ERROR at line 1:
    ORA-00701: object necessary for warmstarting database cannot be altered
    need immediate help.
    Immediate help can be only provided by Oracle Support Services. So if you need that, please raise a Sev1 SR . For your issue, as others have suggested already, if you have a valid backup and you are in the archive log mode, using RMAN's BMR(Block Media Recovery) , the issue can be resolved provided there is nothing wrong with the hardware of yours. If that's the case, recovery wouldn't yield any benefits.
    Aman....

  • CREATING SYSTEM AND SYSAUX FILES

    Hi,
    when creating DB by script, can we choose to have them in AUTOEXTEND OFF or ON like this :
    SYSAUX DATAFILE '/d12/ORA_DB/SYSAUX_001.dbf' SIZE 350M
    EXTENT MANAGEMENT LOCAL AUTOEXTEND OFF
    DATAFILE '/d12/ORA_DB/SYSTEM_001.dbf' SIZE 100M
    EXTENT MANAGEMENT LOCAL AUTOEXTEND OFF
    Many thanks

    The reason why this command fails from the beginning is because you are using 'EXTENT MANAGEMENT LOCAL' right after the datafile size, then you declare the autoextend on clause, this autoextend on is a datafile attribute, meanwhile the extent management local is a tablespace attribute which cannot be declared until you have completely specified the datafile:
    SYSAUX DATAFILE '/d12/ORA_DB/SYSAUX_001.dbf' SIZE
    350M
    EXTENT MANAGEMENT LOCAL AUTOEXTEND OFF
    DATAFILE '/d12/ORA_DB/SYSTEM_001.dbf' SIZE 100M
    EXTENT MANAGEMENT LOCAL AUTOEXTEND OFFSo, the command, properly rearranged, to create your tablespace is:
    SYSAUX DATAFILE '/d12/ORA_DB/SYSAUX_001.dbf' SIZE 350M AUTOEXTEND OFF
    EXTENT MANAGEMENT LOCAL
    DATAFILE '/d12/ORA_DB/SYSTEM_001.dbf' SIZE 100M AUTOEXTEND OFF
    EXTENT MANAGEMENT LOCAL ~ Madrid

  • Sysaux tablespace is getting full

    Hi,
    can anyone help me find out why my sysaux tablespace is getting full?
    Regards

    Hi,
    The datafiles of System ,and Sysaux tablespaces are in AUTIEXTEND ON mode by default.
    To findout what object is occupying the space
    SELECT OCCUPANT_NAME,OCCUPANT_DESC,SCHEMA_NAME,MOVE_PROCEDURE,SPACE_USAGE_KBYTES from V$SYSAUX_OCCUPANTS;

  • 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

  • ASSM and system, temp, undo tablespaces(10g)

    Hi, all.
    I created a database(10.2.0.2.0) by using DBCA.
    SYSAUX and USERS tablespaces are set to "auto" in
    SEGMENT_SPACE_MANAGEMENT column.
    However, system, temp and temp tablespaces have the value of "Manual" in
    SEGMENT_SPACE_MANAGEMENT column.
    Can I change this Value, "Manual" to "Auto" ??
    (system, temp, undo tablespace)
    Best Regards.

    Hi,
    The document states that there are certain restrictions on Automatic Segment-space Management.
    Firstly, you can specify this clause only for a permanent, locally managed tablespace.Secondly, you cannot specify this clause for the SYSTEM tablespace.
    http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_7003.htm
    Adith

  • SYSAUX tablespace full and snapshots not deleted

    hi all,
    I am on 10g linux.
    1) my sysaux tablespace is full and i realize there are many awr snapshots lying around.
    so i went to my OEM console -> Automatic Workload Repository and this are basically my settings
    Snapshot Retention (days) 7
    Snapshot Interval (minutes) 60
    Collection Level TYPICAL
    Next Snapshot Capture Time Sep 25, 2012 8:27:41 AM
    However, when i check the amount of snapshots
    ->
    Manage Snapshots and Preserved Snapshot Sets
    Snapshots 247
    Preserved Snapshot Sets 0
    Latest Snapshot Time Sep 25, 2012 7:27:41 AM
    Earliest Snapshot Time Jun 27, 2012 10:20:16 PM
    q1) i have got 247 snapshots dated as early as Jun 27 but i am only retaining 7 days of snapshots ?
    7 * 24 (1 hour snapshot frequency) != 247
    there is no snapshot baseline also.
    q2) why my latest snapshot time is dated way back to sept 25 ? is it because my sysaux is full for a longtime thus no more snapshot can be taken ? but i thought the retention of 7 days will remove obsolete snapshots ?
    Please advise.
    Regards,
    Noob

    Hi,
    there are some problem in delete AWR stats.
    For example, if the delete takes more 5 minute it's interrupted.
    Look which component grows using awrinfo.sql under $ORACLE_HOME/rdbms/admin
    You may execute the delete procedure manually than move and rebuild the tables.

  • 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...

  • ORA-01578: ORACLE data block corrupted on tables in sysaux tablespace

    Dear Experts,
    From the alert log file we noticed data block corruptions on one of our datafiles. After further investigation, we realized that the corruptions were on 3 of the AWR related tables in the SYSAUX tablespace:
    1. WRH$_LIBRARYCACHE
    2. WRH$_TEMPSTATXS
    3. WRI$_ALERT_OUTSTANDING
    The bad news is that we may not have a valid rman backup to do the recovery due to the retention policy - RECOVERY WINDOW OF 2 DAYS. Since this is a development database with limited monitoring, we did not discover the corruption until 6 days later. The issue happened about 6 days ago (about Christmas time).
    So, what are our recovery options? Can someone advice? We are thinking about drop and recreate the 3 affected v$WR* tables, but not quite sure about the impact to the system if we drop and recreate the 3 objects. Did someone experience this type of recovery. If you did, what are your approaches?
    We are running oracle 10.2.0.3 version.
    I greatly appreciate your input and suggestion. Thanks!!!

    as long as you have a backup of ur database before christmas, you can use the " MAXDAYS " cmd to get ur backup working so long as you have not used delete obsolote....had a same sistuation....where i had a backup and trying to restore it ...kept saying no valid backup...after going thru some stuff...found the MAXDAYS cmd to use my backup...here is an example ...
    $ rman target /
    Recovery Manager: Release 10.2.0.2.0 - Production on Sun Apr 6 09:05:44 2008
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    connected to target database (not started)
    RMAN> SET DBID=1528894801
    executing command: SET DBID
    RMAN> startup force nomount;
    startup failed: ORA-01078: failure in processing system parameters
    LRM-00109: could not open parameter file '/u01/app/oracle/product/10.2.0/db_1/dbs/initsameera.ora'
    starting Oracle instance without parameter file for retrival of spfile
    Oracle instance started
    Total System Global Area 159383552 bytes
    Fixed Size 1259672 bytes
    Variable Size 58722152 bytes
    Database Buffers 92274688 bytes
    Redo Buffers 7127040 bytes
    RMAN> set controlfile autobackup format for device type disk to '/u99/backup/sameera/control_spfile_%F';
    executing command: SET CONTROLFILE AUTOBACKUP FORMAT
    using target database control file instead of recovery catalog
    RMAN> run
    2> {
    3> allocate channel p1 type disk;
    4> restore spfile to pfile '/u01/app/oracle/product/10.2.0/db_1/dbs/initsameera.ora' from autobackup;
    5> shutdown abort;
    6> }
    allocated channel: p1
    channel p1: sid=36 devtype=DISK
    Starting restore at 06-APR-08
    channel p1: looking for autobackup on day: 20080406
    channel p1: looking for autobackup on day: 20080405
    channel p1: looking for autobackup on day: 20080404
    channel p1: looking for autobackup on day: 20080403
    channel p1: looking for autobackup on day: 20080402
    channel p1: looking for autobackup on day: 20080401
    channel p1: looking for autobackup on day: 20080331
    channel p1: no autobackup in 7 days found
    released channel: p1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 04/06/2008 09:09:09
    RMAN-06172: no autobackup found or specified handle is not a valid copy or piece
    Solution:
    RMAN> shutdown abort;
    RMAN> EXIT;
    $ ps -ef |grep pmon
    oracle 2891 2856 0 09:05 pts/1 00:00:00 grep pmon
    oracle 7448 1 0 Apr05 ? 00:00:00 ora_pmon_primary
    $export ORACLE_SID=sameera
    $ rman target /
    Recovery Manager: Release 10.2.0.2.0 - Production on Sun Apr 6 09:05:44 2008
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    connected to target database (not started)
    RMAN> SET DBID=1528894801
    executing command: SET DBID
    RMAN> startup force nomount;
    startup failed: ORA-01078: failure in processing system parameters
    LRM-00109: could not open parameter file '/u01/app/oracle/product/10.2.0/db_1/db s/initsameera.ora'
    starting Oracle instance without parameter file for retrival of spfile
    Oracle instance started
    Total System Global Area 159383552 bytes
    Fixed Size 1259672 bytes
    Variable Size 58722152 bytes
    Database Buffers 92274688 bytes
    Redo Buffers 7127040 bytes
    RMAN> set controlfile autobackup format for device type disk to '/u99/backup/sameera/control_spfile_%F';
    executing command: SET CONTROLFILE AUTOBACKUP FORMAT
    using target database control file instead of recovery catalog
    RMAN> run
    2> {
    3> allocate channel p1 type disk;
    4> restore spfile to pfile '/u01/app/oracle/product/10.2.0/db_1/dbs/initsameera.ora' from autobackup maxdays 15;
    5> shutdown abort;
    6> }
    released channel: ORA_DISK_1
    allocated channel: p1
    channel p1: sid=36 devtype=DISK
    Starting restore at 06-APR-08
    channel p1: looking for autobackup on day: 20080406
    channel p1: looking for autobackup on day: 20080405
    channel p1: looking for autobackup on day: 20080404
    channel p1: looking for autobackup on day: 20080403
    channel p1: looking for autobackup on day: 20080402
    channel p1: looking for autobackup on day: 20080401
    channel p1: looking for autobackup on day: 20080331
    channel p1: looking for autobackup on day: 20080330
    channel p1: looking for autobackup on day: 20080329
    channel p1: looking for autobackup on day: 20080328
    channel p1: looking for autobackup on day: 20080327
    channel p1: looking for autobackup on day: 20080326
    channel p1: looking for autobackup on day: 20080325
    channel p1: looking for autobackup on day: 20080324
    channel p1: looking for autobackup on day: 20080323
    channel p1: autobackup found: /u99/backup/sameera/control_spfile_c-1528894801-20080323-00
    channel p1: SPFILE restore from autobackup complete
    Finished restore at 06-APR-08
    Oracle instance shut down
    Check to make sure if initsameera.ora exists in $ORACLE_HOME/dbs location.
    $ cd $ORACLE_HOME/dbs
    $ ls -ltr
    total 7052
    -rw-r----- 1 oracle oinstall 2560 Apr 5 13:21 spfileprimary.ora
    -rw-r----- 1 oracle oinstall 7061504 Apr 5 13:23 snapcf_primary.f
    -rw-rw---- 1 oracle oinstall 1544 Apr 5 18:42 hc_sameera.dat
    -rw-r--r-- 1 oracle oinstall 1087 Apr 6 09:12 initsameera.ora
    $ pwd
    /u01/app/oracle/product/10.2.0/db_1/dbs
    $

  • SYSAUX tablespace grow too quick????

    We have EBS R12.1 on LINUX system. Recently I found our development EBS database SYSAUX tablespace grow very quick. The SYSAUX tablespace has two data files and each data files size is 6GB (total 12 GB). In one month all 12 GB space are gone.
    My questions are:
    1. what objects or reports or ??? take this much space?
    2. how to delete un-need space?
    3. what is reasonable SYSAUX size?
    Thanks.

    I double check SYSAUX space usage and found it only use less than 100MB. Why SYSAUX show all 12 Gb space are gone?
    SQL> l
    1 SELECT occupant_name, schema_name, move_procedure,
    2 space_usage_kbytes
    3 FROM v$sysaux_occupants
    4* ORDER BY 1
    SQL> /
    OCCUPANT_NAME SCHEMA_NAME MOVE_PROCEDURE SPACE_USAGE_KBYTES
    AO SYS DBMS_AW.MOVE_AWMETA 45888
    AUTO_TASK SYS 320
    EM SYSMAN emd_maintenance.move_em_tblspc 0
    EM_MONITORING_USER DBSNMP 0
    EXPRESSION_FILTER EXFSYS 0
    JOB_SCHEDULER SYS 1152
    LOGMNR SYSTEM SYS.DBMS_LOGMNR_D.SET_TABLESPACE 13376
    LOGSTDBY SYSTEM SYS.DBMS_LOGSTDBY.SET_TABLESPACE 1600
    ORDIM ORDSYS 0
    ORDIM/PLUGINS ORDPLUGINS 0
    ORDIM/SQLMM SI_INFORMTN_SCHEMA 0
    PL/SCOPE SYS 640
    SDO MDSYS MDSYS.MOVE_SDO 0
    SM/ADVISOR SYS 198528
    SM/AWR SYS 1006144
    SM/OPTSTAT SYS 10866560
    SM/OTHER SYS 8192
    SMON_SCN_TIME SYS 3328
    SQL_MANAGEMENT_BASE SYS 1728
    STATSPACK PERFSTAT 0
    STREAMS SYS 1216
    TEXT CTXSYS DRI_MOVE_CTXSYS 0
    TSM TSMSYS 256
    ULTRASEARCH WKSYS MOVE_WK 0
    ULTRASEARCH_DEMO_USE WK_TEST MOVE_WK 0
    R
    WM WMSYS DBMS_WM.move_proc 0
    XDB XDB XDB.DBMS_XDB.MOVEXDB_TABLESPACE 56192
    XSAMD OLAPSYS DBMS_AMD.Move_OLAP_Catalog 0
    XSOQHIST SYS DBMS_XSOQ.OlapiMoveProc 45888
    29 rows selected.

  • 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.

Maybe you are looking for

  • How to execute link without showing it on browser

    Hi, In my site iam implementing sms functionality through 3rd party tool. In that, they gave me an url which will send the sms through their website. For that, i have to execute the url. Is it possible to execute the url without showing on the browse

  • WL 7.x, JDK 1.4, SSL

    Hello, Given that: (1) WL will not be certified for use with JDK 1.4 until the Olympic release (otherwise known as version 8.1, hopefully available sometime early this summer if we're lucky?). (2) Our application requires JDK 1.4 functionality (prefe

  • Group Asse Posting

    I have created one group asset when i am trying to post one asset acquisition through F-90 getting an error showing that 'Asset is a group asset: posting with transaction type 100 is not allowed" Please help me to solve this issue

  • How to use Cinema4D lite with no opening After Effects CC ?

    How to use Cinema4D lite with no opening After Effects CC ? Is that possible ? Open a 3D object Photoshop-type in After Effects CC (without C4D) It is also possible? thanks xav

  • C++help

    hi guys, could you please help me with my C++ program I was trying to do it but i have no clue I have to write a function that finds out how many elements in an integer array are larger than the average of all the value is the array. The function sho