Release 3.0.74.2 is a corrective update. It is primarily intended for databases where the automatic update to 3.0.74.1 encountered an error when using row-level security (RLS).
If the transition from 3.0.73.1 to 3.0.74.1 was successful, the built-in change description clearly states that updating to 3.0.74.2 is not required.
What happened
The built-in change description for 3.0.74.2 states that the error occurring during the auto-update to version 3.0.74.1 in information databases using row-level security has been fixed.
The built-in description for 3.0.74.2 specifically mentions the correction of the auto-update error; no other user changes have been confirmed. New features of electronic document management (EDM), interface changes, legislation, or business documents have not been announced.
In 3.0.74.1 and in 3.0.74.2
| Situation | 3.0.74.1 | 3.0.74.2 |
|---|---|---|
| Auto-update of the database with RLS | An error could occur during the auto-update to 3.0.74.1 in certain databases with RLS | The section of the update process that could cause this error has been fixed |
| Successful transition from 3.0.73.1 | The database is already functioning normally on 3.0.74.1 | According to the built-in description, transitioning to 3.0.74.2 is not required |
| User changes | No other changes within this correction have been established | The correction of the auto-update error has been announced |
Who should update
3.0.74.2 is relevant if the auto-update to 3.0.74.1 did not complete successfully in a database with RLS. If the transition from 3.0.73.1 to 3.0.74.1 was successful, it is not necessary to install 3.0.74.2 solely for this correction.
The official wording indicates that the described error pertains to databases with row-level security. This specific situation is not stated for databases without RLS.
If the update failed
Do not continue working in a partially updated database. Stop users and follow the standard administrator procedure: determine the state of the database, restore a backup if necessary, then repeat the standard update to 3.0.74.2. After completion, check the database launch and user access.
Before updating, be sure to create a verified backup.
What is important to understand
There is no data on the complete disabling of RLS; the correction of the update process cannot be interpreted as the removal of access restrictions or a weakening of security.
Frequently asked questions
Does everyone need release 3.0.74.2?
No. It is not required after a successful transition from 3.0.73.1 to 3.0.74.1.
Who is affected by the correction?
Databases with RLS where an error occurred during the auto-update to 3.0.74.1.
Can I work after a failed update?
No. Work cannot continue in a partially updated database.
Does the release disable RLS?
There is no such data. The correction cannot be interpreted as disabling access restrictions.
How to repeat the update?
Follow the standard administrator procedure: restore a backup if necessary and update to 3.0.74.2.