Make sure you don't have the environment variable : TZ set to GMT.
If at the time of database startup, if this variable is set, then all
subsequent dates would return as per this.
-Madhu S
tvf1413_at_yahoo.com (tvf) wrote in message news:<e86dbafc.0211040750.3b9755c3_at_posting.google.com>...
> We are running an old CRM app (Scopus) and are in the process of
> evaluating a replacement. I recently copied the backend Oracle 7.3.4
> database from Solaris 2.6 to new hardware running Solaris 8. I've
> since noticed that the Oracle sysdate command now returns GMT and this
> is screwing up the timestamps that the app is using. I cannot change
> the code in the app to stop it from using sysdate. Is there a way I
> can update the Oracle sysdate so that it reflects the OS date/time? Is
> setting the init.ora parameter fixed_date the only way to do this?
>
> # uname -a
> SunOS xxx.xxx.com 5.8 Generic_108528-07 sun4u sparc
> SUNW,Ultra-Enterprise
> # date
> Mon Nov 4 09:45:10 CST 2002
>
> --
> Oracle7 Server Release 7.3.4.0.1 - Production
> PL/SQL Release 2.3.4.0.0 - Production
>
> SQL> select to_char(sysdate, 'mm/dd/yyyy hh:miAM') from dual;
> TO_CHAR(SYSDATE,'MM/DD/YYYYHH:MIAM')
> ---------------------------------------------------------------------------
> 11/04/2002 03:45PM
>
> Thank you for your time.
Received on Mon Nov 04 2002 - 14:57:49 CST
