Search this site


    Oracle Technology‎ > ‎Database‎ > ‎

    database notes

    Subscribe to posts

    Oracle PSU's for 11.2.0.1 on Unix

    posted 22 Dec 2011 02:02 by Alan Nolan-Davies   [ updated 29 Dec 2011 03:16 ]

    Patch PSU Includes CPU
    9352237 11.2.0.1.1 Apr-10
    9654983 11.2.0.1.2 Jul-10
    9952216 11.2.0.1.3 Oct-10
    10248516 11.2.0.1.4 Jan-11
    11724930 11.2.0.1.5 Apr-11
    12419378 11.2.0.1.6 Jul-11

    11.2.0.1.6 was the final release for 11.2.0.1

    Oracle Database Desupport Dates

    posted 15 Sep 2010 01:54 by Alan Nolan-Davies   [ updated 22 Jul 2011 07:33 ]

    Details of the Oracle Database Releases can be found on Oracle Support Note: 161818.1 - summarised here     
    Database Version

    Oracle11gR2    11.2.0.x 

    Oracle11gR1    11.1.0.x

    Oracle10gR2    10.2.0.x 

    Oracle10gR1    10.1.0.x

    Oracle9iR2       9.2.0.x

    Oracle9iR1    9.0.1.x

    Oracle8i    8.1.7.x

    Oracle 8    8.0.6.x

    Oracle 7    7.3.4.x
    Support Ends

    January 2015   

     August 2012

    July 2010

    January 2009

    July 2007

    December 2003

    December 2004

    October 2001

    December 2000
    Extended Support Ends

    January 2018

    August 2015

    July 2013

    January 2012

    July 2010

    none

    December 2006

    September 2003

    December 2002
    This is a general guide and it should be noted that Oracle do extend some platforms and so Oracle Support should be consulted for confirmation.

    Query Audited Logons

    posted 18 Mar 2009 05:16 by Alan Nolan-Davies   [ updated 22 Jul 2011 07:56 ]

    SELECT USERNAME, OS_USERNAME, USERHOST, action_name,
           decode(RETURNCODE,0,'Logon Accepted',1017,'Failed - Invalid username/password',28000,'Failed - the account is locked',28001,'Failed - the password has expired',RETURNCODE) RETURNCODE,
           to_char(TIMESTAMP,'DD-MON-YYYY HH24:MI:SS') TIMESTAMP
    FROM SYS.DBA_AUDIT_SESSION
    order by timestamp desc


    Move Sys.AUD$ in Oracle11g

    posted 13 Jan 2009 02:42 by Alan Nolan-Davies   [ updated 22 Jul 2011 07:36 ]

    It’s recommended to create a new Tablespace for holding the Audit generated logs in the table SYS.AUD$  rather than leave it in the SYSTEM tablespace

     

    However when Oracle can no longer write to the SYS.AUD$ it will refuse any further logins to the database, so space checking is important (as usual)

     

    I created the tablespace AUDIT_DATA in the new Oracle11g Database PHKE

     

    Then I used DBMS_AUDIT_MGMT to move the SYS.AUD$ table

     

    SQL> begin
      2  DBMS_AUDIT_MGMT.SET_AUDIT_TRAIL_LOCATION(
      3  audit_trail_type => DBMS_AUDIT_MGMT.AUDIT_TRAIL_DB_STD,
      4  audit_trail_location_value => 'AUDIT_DATA');
      5  end;
      6  /


    DBMS_AUDIT_MGMT

    posted 31 Dec 2008 01:01 by Alan Nolan-Davies   [ updated 22 Jul 2011 07:32 ]

    Oracle recommend using the DBMS_AUDIT_MGMT package to move the sys.aud$ table from the System Tablespace to another.

    I created a new Tablespace called AUDIT_DATA and then ran this procedure.

    SQL> begin
      2  DBMS_AUDIT_MGMT.SET_AUDIT_TRAIL_LOCATION(
      3  audit_trail_type => DBMS_AUDIT_MGMT.AUDIT_TRAIL_DB_STD,
      4  audit_trail_location_value => 'AUDIT_DATA');
      5  end;
      6  /

    PL/SQL procedure successfully completed.

    it's simple and it works... nice

    1-5 of 5

    Sign in|Report Abuse|Print Page|Remove Access|Powered By Google Sites