Oracle Database uses timezone definitions to handle time calculations and daylight-saving time transitions. Timezone changes potentially alter data stored in columns using the TIMESTAMP WITH TIMEZONE data type. Previously, Exadata Smart Scan was disabled for the entire database during an upgrade of the timezone definitions.

In conjunction with Oracle Database 23ai, Oracle Exadata System Software release 24.1.0 reduces the impact of timezone upgrades. Under the new arrangement, Exadata Smart Scan remains enabled for queries on all tables without TIMESTAMP WITH TIMEZONE columns. Furthermore, the impact of timezone changes is now contained within a pluggable database (PDB). So, if a timezone change impacts one PDB, Exadata Smart Scan remains enabled for all the other PDBs.