Oracle

Can someone look at my attached screen shot and explain to me what -08:00 truly means in terms of a system timestamp on a Oracle 11g database?  Does this mean that we are 8 hours of GMT?
Timestamp.jpg
akdreamingAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
sdstuberConnect With a Mentor Commented:
your database server's operating system timezone is set with a -8 hour offset from UTC/GMT

The time zone offset reported by systimestamp has nothing to with the database time zone, which should always be +0:00.

I have no idea why Oracle allows you to set or query that value since there is no value in doing so, and they even note in their own documentation, as slightwv pointed out, that you should just leave it alone at +0:00
0
 
tailoreddigitalCommented:
Yes,  -08:00 represents the timezone in relation to GMT.   It's another way to say Pacific Time.  So the local time is based in,
timezone
0
 
akdreamingAuthor Commented:
Well, we are in Alaska.....on our own time zone.  We are one hour behind Pacific time.  Does it look right?
0
Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
tailoreddigitalCommented:
Is the database on a system in Alaska? Or could it be remote?

I just ran across this about Alaska's timezone,

"Effective 2007, the local time changes from AKST to AKDT at 02:00 LST to 03:00 LDT on the second Sunday in March and returns at 02:00 LDT to 01:00 LST on the first Sunday in November."

It sounds like it might use -08 between March and November.

FYI,
http://en.wikipedia.org/wiki/Alaska_Time_Zone
0
 
akdreamingAuthor Commented:
Yes, everything we have running is in the Alaska timezone.  Nothing hosted outside of Alaska.  The issue we are having is we use an application called Appworx, which runs off of a Oracle database.  The server the Oracle database is running on was upgraded to 11g from 10g.  Appworx seemed to run fine.  Appworx is basically a batch job scheduler.  Then we upgraded the server itself from Windows 2003 Server to Windows 2008R2.  Appworx is having issues.  Can login to application but some jobs are failing due to some sort of timing issue.  Date stamp on database is correct.  Time on server is correct.  Before any of these upgrades, there was no issue with Appworx or timing issues.  We've never had to do anything concerning the timezone subject concerning our database.
0
 
tailoreddigitalCommented:
I don't have any experience with Appworx.    I did a bit of researching on this issue but nothing comes up.    Hopefully another expert with the right experience can help.
0
 
PaulCommented:
>>Windows 2003 Server to Windows 2008R2
I'd be double-checking the time/locale settings on the servers - my memory on this is vague but there were some changes in Windows regarding handling daylight savings as well
0
 
slightwv (䄆 Netminder) Commented:
Also check out this:  Setting the Database Time Zone

http://docs.oracle.com/cd/E11882_01/server.112/e10729/ch4datetime.htm#NLSPG262
0
 
manny17Commented:
Yes, that's the timezone wrt to GMT
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.