Changes Made in APEX Theme Roller Against a Second Database Instance Are Not Permanently Saved When Configured Against ORDS 3.0
(Doc ID 2036779.1)
Last updated on MARCH 12, 2021
Applies to:Oracle Application Express (APEX) - Version 5.0.0.00.31 and later
Oracle REST Data Services - Version 3.0 to 3.0.1 [Release 3 to APEX 3.0]
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Two database instances are configured against Ords version 3 or Ords version 3.0.1. For the second database instance the changes made by Theme Roller in APEX 5.0 are not saved permanently, instead the changes made by the Theme Roller in APEX 5.0 are lost.
- For the original database instance, when changes are made with the Theme Roller, changes are saved.
- When having multiple database instances configured against Ords version 2.x, the Theme Roller changes are saved correctly both the first and second database instances.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document