Wish they all could be California....

I'm an applications programmer, so please bear with me.

We have an odd problem with system date/time. We are running Oracle 7.1.3 on a UNIX system V host, and the tools are running on a Novell network using SQLNET 2.1.4.1.4. We have users in several locations using different networked servers to execute their Forms.

The problem: On some of the machines, when Oracle is asked for the system date/time, it will sometimes respond with a time that is 7 hours ahead of Pacific Standard Time. The hosts have the correct time. I have no idea where to start looking to resolve this problem, but since we date/timestamp the users' data entry, they are understandably annoyed. I can see no obvious pattern in when the time will be correct and when it will be incorrect.

The only thing I can think of is that there must be some sort of timezone parameter someplace that needs to be set and isn't. (7 hours ahead is GMT.)

Our DBA and Oracle could shed no light, except to tell me that they think it's a SQLNET problem.

I tried putting in a database trigger to change the timezone on the tables I timestamp, but not all of the users get the wrong time.

Any guesses?

Louise Miller Received on Thu Nov 16 1995 - 00:00:00 CET