Oracle Instant Client configuration now refreshes correctly
Details
| Detail name | Value |
|---|---|
| Changelog Number | 26128 |
| Type | Bug |
| Status | Open |
| Affected Versions | Exasol 8.0.0 |
Description
After the Oracle Instant Client location was changed for a database, the related BucketFS configuration was not refreshed. As a result, an uploaded Oracle Instant Client could remain unavailable and Oracle imports could fail with an ETL-4: Oracle instant client not available error.
Workaround
Run exaconf commit after changing the Oracle configuration with db_configure.
Fix
Database Oracle configuration changes now refresh the related BucketFS configuration and restart the required BucketFS service instances. Uploaded Oracle Instant Client files are then available from the configured location.
Changed behavior
Previously, changing a database Oracle configuration with db_configure did not refresh the related BucketFS configuration. An uploaded Oracle Instant Client could remain unavailable until a full EXAConf commit was run.
Oracle configuration changes now automatically refresh the related BucketFS configuration and restart the required service instances.
