RE: SQL Auditing Help - Sol 10, 10.2.0.2

From: "Newman, Christopher" <cjnewman@xxxxxxxxxxxxx>
To: <rjoralist@xxxxxxxxxxxxxxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
Date: Wed, 27 Jan 2010 13:43:38 -0600

Good thought, but I've also tried with the ntimestamp# column from
sys.aud$, same result as below.  Any thoughts?

Thanks- Chris

-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Rich Jesse
Sent: Tuesday, January 26, 2010 4:21 PM
To: oracle-l@xxxxxxxxxxxxx
Subject: Re: SQL Auditing Help - Sol 10, 10.2.0.2

Might it be something silly like using a keyword ("TIMESTAMP") as a
column
name?

Just a knee jerk to what I see.  I know, I know, Oracle Corp does it.
For
this particular, I use "TIME_STAMP".  Not sure that helps, but it's a
shot...

Rich

> create table oracle.master_audit
> (DBNAME varchar2(10),
> OS_USERNAME varchar2(255),
> TIMESTAMP date,
> USERNAME VARCHAR2(30),
> USERHOST VARCHAR2(128),
> TERMINAL VARCHAR2(255))
> Partition by range (TIMESTAMP)
> (

--
http://www.freelists.org/webpage/oracle-l

--
http://www.freelists.org/webpage/oracle-l

Follow-Ups:

RE: SQL Auditing Help - Sol 10, 10.2.0.2
From: Newman, Christopher

References:
- SQL Auditing Help - Sol 10, 10.2.0.2
  - From: Newman, Christopher
- Re: SQL Auditing Help - Sol 10, 10.2.0.2
  - From: Rich Jesse

RE: SQL Auditing Help - Sol 10, 10.2.0.2

Other related posts: