Database Job sysdate defaults to midnight

Question

Oracle 11g on AIX.
I have a database job that inserts data into a table and one of the date columns I am inserting into is populated by using sysdate. No matter what time I run the job, the time always defaults to midnight. Anyone know why?
Owner of the procedure, owner of the table, and owner of the job are all the same. This same owner has the NLS date set to include the hour minutes and seconds. I have the exact same job setup for different databases, and it inserts the correct time. All DDL is the exact same for these databases.

Answer 1

AIX 5.3.0.0 on 11g 11.1.0.7.0. Code is posted below. The job runs every 4 hours so when I am trying to insert at 2am, it inserts the current date with 12:00:00AM added on instead of 2:00:00AM. Then the next time the job runs at 6am, the job fails because of a primary key constraint since it tries to insert 12:00:00AM again. All NLS parameters are set to default (null) on both databases. Fixed_date is not set. This problem occurs every time the job runs. The sysdate returns the correct date/time when running ordinary queries.
CREATE TABLE "TEST"."METRIC_HISTORY"
"INSTANCE_NAME" VARCHAR2(16 BYTE),
"METRIC_DATE" DATE,
"METRIC_ID" NUMBER,
"METRIC_NAME" VARCHAR2(64 BYTE),
"METRIC_UNIT" VARCHAR2(64 BYTE),
"METRIC_MINIMUM" NUMBER,
"METRIC_MAXIMUM" NUMBER,
"METRIC_AVERAGE" NUMBER,
CONSTRAINT "METRIC_HISTORY_PK" PRIMARY KEY ("INSTANCE_NAME", "METRIC_DATE", "METRIC_ID"))
TABLESPACE "USERS" ;
create or replace
PROCEDURE TEST."METRIC_GATHER"
is
begin
insert into TEST.METRIC_HISTORY (instance_name, metric_date, metric_id, metric_name, metric_unit, metric_minimum, metric_maximum, metric_average)
select INSTANCE_NAME,
TO_DATE(SYSDATE, 'DD-MON-YY HH:MI:SS AM') METRIC_DATE,
METRIC_ID,
CASE METRIC_NAME
WHEN 'SQL Service Response Time' then 'SQL Service Response Time (secs)'
WHEN 'Response Time Per Txn' then 'Response Time Per Txn (secs)'
ELSE METRIC_NAME
END METRIC_NAME,
METRIC_UNIT,
CASE METRIC_NAME
WHEN 'SQL Service Response Time' then ROUND((MINVAL / 100),2)
WHEN 'Response Time Per Txn' then ROUND((MINVAL / 100),2)
ELSE MINVAL
END METRIC_MINIMUM,
CASE METRIC_NAME
WHEN 'SQL Service Response Time' then ROUND((MAXVAL / 100),2)
WHEN 'Response Time Per Txn' then ROUND((MAXVAL / 100),2)
ELSE MAXVAL
END METRIC_MAXIMUM,
CASE METRIC_NAME
WHEN 'SQL Service Response Time' then ROUND((AVERAGE / 100),2)
WHEN 'Response Time Per Txn' then ROUND((AVERAGE / 100),2)
ELSE AVERAGE
END METRIC_AVERAGE
from SYS.GV_$SYSMETRIC_SUMMARY S JOIN SYS.GV_$INSTANCE I on S.INST_ID = I.INST_ID
where METRIC_ID in (2004,2107,2075,2106,2109,2003,2000,2103,2006,2058,2071,2061,2069,2108);
end;
BEGIN
sys.dbms_scheduler.create_job(
job_name => '"TEST"."TESTJOB"',
job_type => 'STORED_PROCEDURE',
job_action => '"TEST"."METRIC_GATHER"',
repeat_interval => 'FREQ=HOURLY;INTERVAL=4',
start_date => to_timestamp_tz('2010-05-24 14:00:00 CST6CDT', 'YYYY-MM-DD HH24:MI:SS TZR'),
job_class => '"DEFAULT_JOB_CLASS"',
auto_drop => FALSE,
enabled => FALSE);
sys.dbms_scheduler.set_attribute( name => '"TEST"."TESTJOB"', attribute => 'raise_events', value => dbms_scheduler.job_failed);
sys.dbms_scheduler.set_attribute( name => '"TEST"."TESTJOB"', attribute => 'logging_level', value => DBMS_SCHEDULER.LOGGING_OFF);
sys.dbms_scheduler.set_attribute( name => '"TEST"."TESTJOB"', attribute => 'job_weight', value => 1);
sys.dbms_scheduler.enable( '"TEST"."TESTJOB"' );
END;