This appendix covers the following topics:
When using Advanced Provisioning to provision an environment, or when creating a standby environment, you are prompted for the operating system time zone you want to use for your environment. This appendix describes how default values for the operating system time zone are derived, as well as the implications of overriding the default values.
When taking a backup of an on-premises environment, you will be prompted for the operating system time zone that you wish to use when restoring the backup in Oracle Cloud Infrastructure. This value will be saved as backup metadata in a property called SRC_OS_TIMEZONE.
When provisioning a new environment from a backup, the default value for the operating system time zone is derived based on the following logic:
The value of the Oracle E-Business Suite profile option Server Timezone (code SERVER_TIMEZONE_ID) is used, if it exists.
Otherwise, if the Server Timezone profile option is not set, then the default value is derived from the value of the SRC_OS_TIMEZONE property in the backup's metadata, if it exists.
Otherwise, if both of the prior values are unavailable, then the default value becomes 'UTC'.
The following table illustrates some examples of scenarios with the default value for the field Operating system time zone as well as the time zone to be set in Oracle E-Business Suite Cloud Manager.
In these examples, the user has chosen not to bypass the Server Timezone profile validation.
In this table, the property SRC_OS_TIMEZONE is taken from the backup's metadata. The Oracle E-Business Suite profile option Server Timezone is referred to by its code, SERVER_TIMEZONE_ID.
| Backup Metadata | Default Value Shown in UI | User-Selected Value | Time Zone to be set on Compute | Time Zone to be set on Base Database Service DB Systems | Exadata Infrastructure Time Zone | Time Zone Variable (TZ) to be set on Exadata Database Service Dedicated |
|---|---|---|---|---|---|---|
SRC_OS_TIMEZONE = NOVALUEProfile option SERVER_TIMEZONE_ID = NOVALUE |
UTC | America/New_York | America/New_York | America/New_York | Europe/London | Time zone is America/New_York |
SRC_OS_TIMEZONE = Asia/KolkataProfile option SERVER_TIMEZONE_ID = NOVALUE |
Asia/Kolkata | Asia/Kolkata | Asia/Kolkata | Asia/Kolkata | Europe/London | Time zone is Asia/Kolkata |
SRC_OS_TIMEZONE = NOVALUEProfile option SERVER_TIMEZONE_ID = (GMT+05:30) India Time |
IST | IST | IST | IST | Europe/London | Time zone is IST |
SRC_OS_TIMEZONE = ISTProfile option SERVER_TIMEZONE_ID = (GMT - 5) Eastern Time |
America/New_York | America/New_York | America/New_York | America/New_York | Europe/London | Time zone is America/New_York |
Note the following:
In the first example, neither the backup's metadata nor the profile option has a time zone specified, so the default value is UTC.
In the second example, the backup's metadata includes a time zone but the profile option does not; therefore, the metadata's time zone becomes the default.
In the third example, the backup's metadata does not specify a time zone but the profile option does; therefore, the time zone specified by the profile option is used as the default.
In the fourth example, both the backup's metadata and the profile option specify a time zone, but different ones. In this case, the Server Timezone profile option takes precedence, and its value becomes the default value.
In the case of environments that use Exadata Database Service Dedicated, where there is one system with many databases on it, Oracle E-Business Suite Cloud Manager cannot use the operating system time zone for a given environment, but instead uses the time zone defined in the Exadata Database Service Dedicated infrastructure.
Alternatively, you might choose to bypass the Server Timezone profile validation.
In the examples in the following table, the user has chosen to override the default value for the time zone, and has chosen to bypass the validation.
| Backup Metadata | Default Value Shown in UI | User-Selected Value | Time Zone to be set on Compute | Time Zone to be set on Base Database Service DB Systems | Exadata Infrastructure Time Zone | Time Zone Variable (TZ) to be set on Exadata Database Service Dedicated |
|---|---|---|---|---|---|---|
SRC_OS_TIMEZONE = Asia/KolkataProfile option SERVER_TIMEZONE_ID = NOVALUE |
Asia/Kolkata | America/Los_Angeles (Override) | America/Los_Angeles | America/Los_Angeles | Europe/London | Not Set |
SRC_OS_TIMEZONE = NOVALUEProfile option SERVER_TIMEZONE_ID = (GMT+05:30) India Time |
Asia/Kolkata | America/Los_Angeles (Override) | America/Los_Angeles | America/Los_Angeles | Europe/London | Not Set |
SRC_OS_TIMEZONE = America/New_YorkProfile option SERVER_TIMEZONE_ID = (GMT+05:30) India Time |
Asia/Kolkata | America/Los_Angeles (Override) | America/Los_Angeles | America/Los_Angeles | Europe/London | Not Set |
In the case of environments that use Exadata Database Service Dedicated, where there is one system with many databases on it, Oracle E-Business Suite Cloud Manager cannot use the operating system time zone for a given environment, but instead uses the time zone defined in the Exadata Database Service Dedicated infrastructure. The time zone variable is not set.
In the case of creating a standby environment from an on-premises environment, the default value will be derived based on the Oracle E-Business Suite profile option Server Timezone (code SERVER_TIMEZONE_ID), if it exists. Otherwise, 'UTC' will be used.