DB 39.5.23

21 Feb 2025

Stable 1 for DB 39.5.23

To import stable 1 for DB 39.5.23, download the DB 39.5.23_Stable1 file from the transfer server, unzip it to the server directory and run the migration using the "DB23 Hotfix" component (linux ./planta_migration.sh -c config/migration/db23_hotfix.par under Linux and windows .\planta_migration.bat -c config\migration\db23_hotfix.par under Windows).

Before the update

Before an update to DB 39.5.23 under MSSQL, you have to activate the persistent_db_session parameter in the globals.conf. This is necessary so that the CalculateDepartmentAbsence migration package is executed correctly. The parameter should be deactivated again immediately after the update.
Before updating to DB 39.5.23 under Oracle you have to grant access to DBMS_CRYPTO: GRANT EXECUTE ON SYS.DBMS_CRYPTO TO <user>
When updating from DB 39.5.19 - DB 39.5.21 to DB 39.5.23 under Oracle, you have to verify that the ICOU has been executed correctly in earlier updates.

Further information

From S 39.5.36 Installer, Oracle systems are checked to see whether access to DBMS_CRYPTO is possible (see above). The update will not start if the rights are missing.
If the rights were already missing in the previous updates, the ICOU could not run correctly.
- This can be recognized by the fact that the migration package ApplyInCaseOfUpdate .
Before any update to DB 39.5.22 under Oracle you should therefore verify that ApplyInCaseOfUpdate has run correctly in the previous updates.
If it has failed, the reference tables in the system must be replaced prior to the update:
1) Download the reference status for the DB version from which you want to update from the transfer server under Current Releases > 39.5.x > Database > ICOU Reference Statuses and store it on the server.
2) Open module 009D18 Import Reference, store and import the path to the ZIP file.
3) After the import, close the system and run the update normally with the installer.
- DO NOT click on Find adjustments here! This step is carried out during the update.

After the update

After updating to version 39.5.23, a manual execution of the mandatory CalculateDepartmentAbsence migration packet is required. This ensures that the absence data recorded before the update is still displayed in the corresponding modules.
- Technical reason: To improve performance in the Absence (009AVH) module in the Employee Board and Absence of the Department (009ALC) module in the Department Board, the DIs DI066000 Vacation incl. sub-resources and DI066001 Absence incl. sub-resources have been converted from virtual to real, therefore the absence values must be summarized once for all periods via the resource structure.
  - Caution: The execution of the migration package may take some time.

Since release DB 39.5.17, PLANTA offers a new Online Help. If you update from a release < DB 39.5.17 and want to continue to use context sensitive help directly from within your system (F1/F2), or if your firewall only permits limited Internet access, you have to make sure that the PLANTA project application server has at least access to the IP address: 3.65.222.100.

Notes on update sources and component dependencies

A direct update to version DB 39.5.23 is possible from source versions DB 39.5.16 or higher. If you use an earlier version, you first have to update to version DB 39.5.16 and subsequently to version DB 39.5.23.
For an update to database DB 39.5.23, it is absolutely essential that you also update the server to version S 39.5.37 and the client to version C 39.5.34.
If you work with hybrid systems, please note that PLANTA project version 39.5.23 requires at least PLANTA pulse version 42.1.

If you have any questions, please contact your PLANTA consultant.

PLANTA project/portfolio and PLANTA Hybrid

PLANTA customizer

PLANTA link