Randy,

Just for grins:

Server has "correct" time - currently 2:20 (EST) The proc is run on the target db instance. Tried this via SLQ+ ssh to the (LINUX) box directly too - same result.

The difference seems to be the environment that the proc runs in when I execute via SQL+ and the DBMS_JOB environment.

Did you ever work in tech support?

TIA,
Tim




> -----Original Message-----
> From: Randy Patterson [mailto:[Email Address Removed] Sent: Wednesday, April 30, 2003 2:08 PM
> To: Tim Cornwell
> Subject: RE: Odd date / timestamp behavior
>
>
> Just for grins, look at the server now and see what time it thinks it
> is.
>
> Or, if one record was written from a client application, see what time
> THAT server thinks it is.
>
> Randy Patterson
> > [Email Address Removed] Anadarko Petroleum Corp.
> P.O. Box 1330
> Houston, TX 77251-1330
> (832)636-1655
>
>
>
>
Oracle LazyDBA home page