Scheduler and timezones

Question

We have a number of different databases for different countries around the world, but they all run on Windows servers that are set to use unadjusted GMT (so no daylight savings time kicks in as far as the OS is concerned).
I want to schedule a job so that it runs at 3am local time, either on a Saturday or Sunday, once a week. So, for my UAE database, for example, I discover that UAE is 4 hours ahead of GMT, so when it's 3AM in UAE, it's 11PM the previous night in London, and on my servers!
I therefore do this:
begin
dbms_scheduler.create_job
(job_name=>'TABLE_POP',
job_type=>'STORED_PROCEDURE',
job_action=>'TABLELOAD.REPOPULATE',
start_date=>SYSTIMESTAMP,
repeat_interval=>'FREQ=WEEKLY; BYDAY=SAT; BYHOUR=23',
enabled=>TRUE);
end;
...and my hope (or assumption!) is that by specifying 23:00 on Saturday, the job will run at the moment it turns 3AM Sunday in UAE.
Am I correct in that assumption? Is it the case, in other words, that if you create a job in a database that's running on a server that itself uses GMT then the times you specify in the repeat_interval bit are automatically GMT? Is there a syntax that will make the time zone explicit?

Answer 1

So you're saying that "dbtimezone" is the same thing as the "systimestamp" referenced in the documentation you pointed me to?
As I mentioned, I already know the database timezone because of what is shown in the database_properties view.
I found out I can also do 'select systimestamp from dual', which is presumably an even better fit to what that documentation was saying, and in my case that also shows up +00:00, which is unadjusted GMT.
So, since all these sorts of queries tell me my database is using GMT, my original question can now be answered: yes.
That is, "if you create a job in a database that's running on a server that itself uses GMT then the times you specify in the repeat_interval bit *WILL* BE INTERPRETED, automatically, AS GMT".
With one slight proviso: just because the server's running GMT, it's not a guarantee that the database uses GMT. But if it does, then the above is indeed true.
Unless someone knows any different?!