To change the system time zone used by your RDS Custom for Oracle DB instance, use the time zone option.
For example, you might change the time zone of a DB instance to be compatible with an
on-premises environment, or a legacy application. The time zone option changes the time
zone at the host level. Changing the time zone impacts all date columns and values,
including SYSDATE
and
SYSTIMESTAMP
.
Topics
Time zone option settings in
RDS Custom for Oracle
Amazon RDS supports the following settings for the time zone option.
Option setting | Valid values | Description |
---|---|---|
|
One of the available time zones. For the full list, see Available time zones in RDS Custom for Oracle. |
The new time zone for your DB instance. |
Available time zones in
RDS Custom for Oracle
You can use the following values for the time zone option.
Zone | Time zone |
---|---|
Africa |
Africa/Cairo, Africa/Casablanca, Africa/Harare, Africa/Lagos, Africa/Luanda, Africa/Monrovia, Africa/Nairobi, Africa/Tripoli, Africa/Windhoek |
America |
America/Araguaina, America/Argentina/Buenos_Aires, America/Asuncion, America/Bogota, America/Caracas, America/Chicago, America/Chihuahua, America/Cuiaba, America/Denver, America/Detroit, America/Fortaleza, America/Godthab, America/Guatemala, America/Halifax, America/Lima, America/Los_Angeles, America/Manaus, America/Matamoros, America/Mexico_City, America/Monterrey, America/Montevideo, America/New_York, America/Phoenix, America/Santiago, America/Sao_Paulo, America/Tijuana, America/Toronto |
Asia |
Asia/Amman, Asia/Ashgabat, Asia/Baghdad, Asia/Baku, Asia/Bangkok, Asia/Beirut, Asia/Calcutta, Asia/Damascus, Asia/Dhaka, Asia/Hong_Kong, Asia/Irkutsk, Asia/Jakarta, Asia/Jerusalem, Asia/Kabul, Asia/Karachi, Asia/Kathmandu, Asia/Kolkata, Asia/Krasnoyarsk, Asia/Magadan, Asia/Manila, Asia/Muscat, Asia/Novosibirsk, Asia/Rangoon, Asia/Riyadh, Asia/Seoul, Asia/Shanghai, Asia/Singapore, Asia/Taipei, Asia/Tehran, Asia/Tokyo, Asia/Ulaanbaatar, Asia/Vladivostok, Asia/Yakutsk, Asia/Yerevan |
Atlantic |
Atlantic/Azores, Atlantic/Cape_Verde |
Australia |
Australia/Adelaide, Australia/Brisbane, Australia/Darwin, Australia/Eucla, Australia/Hobart, Australia/Lord_Howe, Australia/Perth, Australia/Sydney |
Brazil |
Brazil/DeNoronha, Brazil/East |
Canada |
Canada/Newfoundland, Canada/Saskatchewan |
Etc |
Etc/GMT-3 |
Europe |
Europe/Amsterdam, Europe/Athens, Europe/Berlin, Europe/Dublin, Europe/Helsinki, Europe/Kaliningrad, Europe/London, Europe/Madrid, Europe/Moscow, Europe/Paris, Europe/Prague, Europe/Rome, Europe/Sarajevo |
Pacific |
Pacific/Apia, Pacific/Auckland, Pacific/Chatham, Pacific/Fiji, Pacific/Guam, Pacific/Honolulu, Pacific/Kiritimati, Pacific/Marquesas, Pacific/Samoa, Pacific/Tongatapu, Pacific/Wake |
US |
US/Alaska, US/Central, US/East-Indiana, US/Eastern, US/Pacific |
UTC |
UTC |
Considerations for setting the time
zone in RDS Custom for Oracle
If you choose to set the time zone for your DB instance, consider the following:
-
When you add the time zone option, a brief outage occurs while your DB instance is automatically restarted.
-
If you accidentally set the time zone incorrectly, you must recover your DB instance to its previous time zone setting. For this reason, we strongly suggest that you to use one of the following strategies before you add the time zone option to your instance:
-
If your RDS Custom for Oracle DB instance uses the default option group, take a snapshot of your DB instance. For more information, see Creating an RDS Custom for Oracle snapshot.
-
If your DB instance currently uses a nondefault option group, take a snapshot of your DB instance, and then create a new option group with the time zone option.
-
-
We strongly recommend that you back up your DB instance manually after applying the
Timezone
option. -
We strongly recommend that you to test the time zone option on a test DB instance before you add it to a production DB instance. Adding the time zone option can cause problems with tables that use system date to add dates or times. We recommend that you analyze your data and applications to assess the impact of changing the time zone.
Limitations for the
time zone setting in RDS Custom for Oracle
Note the following limitations:
-
You can't change your timezone directly on your host without moving it outside the support perimeter. To change your database timezone, you must create an option group.
-
Because the time zone option is a persistent option (but not a permanent option), you can't do the following:
-
Remove the option from an option group after you add the option.
-
Modify the time zone setting of the option to a different time zone.
-
-
You can't associate multiple option groups with your RDS Custom for Oracle DB instance.
-
You can't set the time zone for individual PDBs within a CDB.
Adding the time zone option to an
option group
The default option groups for RDS Custom for Oracle are the following:
-
default:custom-oracle-ee
-
default:custom-oracle-se2
-
default:custom-oracle-ee-cdb
-
default:custom-oracle-se2-cdb
When you create an option group, the settings are derived from the default option group. For general information about option groups in Amazon RDS, see Working with option groups.
Console
To add the time zone option to an option group
Sign in to the AWS Management Console and open the Amazon RDS console at https://console.aws.amazon.com/rds/
. -
In the navigation pane, choose Option groups.
-
Choose the option group that you want to modify, and then choose Add option.
-
In the Add option window, do the following:
-
Choose Timezone.
-
In Option settings, choose a time zone.
-
To enable the option on all associated RDS Custom for Oracle DB instances as soon as you add it, for Apply Immediately, choose Yes. If you choose No (the default), the option is enabled for each associated DB instances during its next maintenance window.
-
Important
If you add the time zone option to an existing option group that is already attached to one or more DB instances, a brief outage occurs while all the DB instances are automatically restarted.
-
-
When the settings are as you want them, choose Add option.
-
Back up the RDS Custom for Oracle DB instances whose time zones were updated. For more information, see Creating an RDS Custom for Oracle snapshot.
AWS CLI
The following example uses the AWS CLI add-option-to-option-group command to add the Timezone
option and the TIME_ZONE
option setting to an option group called
testoptiongroup
. The time zone is set to
America/Los_Angeles
.
For Linux, macOS, or Unix:
aws rds add-option-to-option-group \ --option-group-name "
testoptiongroup
" \ --options "OptionName=Timezone,OptionSettings=[{Name=TIME_ZONE,Value=America/Los_Angeles}]
" \ --apply-immediately
For Windows:
aws rds add-option-to-option-group ^ --option-group-name "
testoptiongroup
" ^ --options "OptionName=Timezone,OptionSettings=[{Name=TIME_ZONE,Value=America/Los_Angeles}]
" ^ --apply-immediately
Removing the time zone
option
The time zone option is a persistent option, but not a permanent option. You can't remove the option from an option group after you add it. To disassociate the old option group from your DB instance:
-
Create a new option group with an updated
Timezone
option. -
Associate the new option group with your DB instance when you modify the instance.