Changelog
This page lists the changes of each release. Every entry links to its migration guide. The release notes on GitHub hold the pull requests and the contributors.
Versions
Section titled “Versions”- DB 23.26.2.0 → 23.26.3.0. The datafiles are compatible, so no dump and restore is necessary. The data dictionary needs one repair command.
- ORDS 26.1.2 → 26.2.2. ORDS upgrades its own schema on the first start.
Data dictionary repair
Section titled “Data dictionary repair”- New script
scripts/repair-ru-dictionary.sh(local-26ai.sh repair-ru-dictionary). A change of the database image does not upgrade the data dictionary. The database keeps the dictionary of the release update that created it, and the in-database JVM stops working without a message. The script finds the dictionary views that are missing, reloads the catalog scripts that create them, and reloads the JVM. --checkshows the gap.--repaircloses it.--summarygiveskey=valuelines for CI.- One run repairs every release update that your database missed, not only the newest one.
test-db-upgrade.ymlnow also proves the repair. The workflow changes the image on the same datafiles, runs the repair, and makes sure that the data, APEX and the dictionary are complete after it.
Space management
Section titled “Space management”- New script
scripts/cap-tablespaces.sh. Every datafile gets a size ceiling, so one datafile alone cannot fill the 12GB limit of the Free edition. A PDB that passes the limit does not open, and you cannot correct it from inside. create-user.shsetsMAXSIZEon the tablespace of a new schema.USER_TBS_MAXSIZEin.envchanges the default of2G.- New script
scripts/compress-space.sh. It applies Advanced Compression to the tables of one schema. create-user.shgains--compress, which creates the schema with compression.shrink-space.shreclaimsTBS_APEXand the audit tablespace. It drops the old APEX version, shrinks the LOB segments, and resizes the datafiles.after-first-db-start.shcaps the undo datafile at 2048MB andAUDIT_TRAILat 1GB. It also creates theUC_AUDIT_PURGEjob, which keeps 7 days of audit records.used-space.shgains--summaryand--quiet. It reports through the exit code, and the warning threshold moves from 10GB to 9.5GB.stop.shshows a warning if the database is close to the limit. This is the last moment at which you can act.drop-user.shreclaims the tablespace of the user and gains a-yflag.
Podman
Section titled “Podman”- The scripts detect the container engine now, so Podman works without changes.
Earlier releases documented Podman, but the scripts called
dockerdirectly. TheCONTAINER_CLIvariable overrides the detected engine. - CI installs the project with Docker and with Podman on every push.
- The project needs the Compose plugin. The old
docker-composeandpodman-composecommands are no longer supported. install.shstarts the database first and waits for it before it starts ORDS. Podman 5.5 and later do not report the container health status, so onecompose up -dfor the whole stack never continues.- The Podman guide names the API socket and the
enable-lingerrequirement.
Secure mode
Section titled “Secure mode”- New flag
install.sh --secure. It setsSECURE_MODE=truein.env. - Secure installs get bounded APEX session timeouts: 18 hours maximum length and 8 hours maximum idle. Local installs keep the 7-day developer default.
- New variable
DEBUG_TO_SCREENin.envcontrols the debug output of ORDS. Release 26.3 passedDEBUGto the container, and that name collides with a variable of the ORDS image and stops it.
APEX parameters
Section titled “APEX parameters”- The four parameters that APEX resolves at runtime are set once at the instance level. A workspace without its own override inherits the instance value.
upgrade-apex.shusesAPEX_INSTANCE_ADMIN.SET_PARAMETERfor the instance settings.
Backups
Section titled “Backups”backup-all.shresolves the workspace of a schema correctly. It deletes the Data Pump master tables that it creates, because they made every later dump larger. It reports a failure through the exit code.
Other scripts
Section titled “Other scripts”- A new user gets the
create assertionprivilege, so the assertions of 23.26.1 are usable. after-first-db-start.shstops the passwords of the database accounts from expiring.disable-password-expiration.shandunexpire-accounts.shcover more accounts.install-dbms-cloud.shcompletes the steps after the wallet.
Documentation
Section titled “Documentation”- The documentation follows ASD-STE100 Simplified Technical English.
- New guide: expose the environment with HTTPS through an nginx reverse proxy.
- New guide: retry an APEX upgrade that failed.
- The installation guide is split, so a new user can start faster.
Earlier releases
Section titled “Earlier releases”| Release | Headline | Migration guide |
|---|---|---|
| v26.3 | DB 23.26.2.0, ORDS 26.1.2, new install.sh and upgrade-apex.sh | Migrate to 26.3 |
| v26.2 | DB 26.1 and ORDS 26.1 | Migrate to 26.2 |
| v26.1 | Move to the 26ai database | Migrate to 26.1 |
| v25.3.1 | Hotfix for 25.3 | Migrate to 25.3 |
| v25.3 | DB 23.8 and ORDS 25.2 | Migrate to 25.3 |
| v25.1 | First public release | Migrate to 25.1 |