My Oracle Support Banner

CDB_PDBS View Is Not Updated After Enabling Force Nologging or Force Logging for a PDB from the CDB$ROOT. (Doc ID 2921221.1)

Last updated on JULY 20, 2024

Applies to:

Oracle Database - Enterprise Edition - Version 19.16.0.0.0 and later
Information in this document applies to any platform.

Symptoms

While enabling force logging or force no-logging for a particular PDB from the CDB$ROOT the command finishes successfully, however when querying the CDB_PDBS view the columns force logging and force_nologging are not getting updated and do not reflect that the setting was changed.
The PDB was open in restricted mode previously to change the force logging or force no-logging setting as per the below testcase, same behavior is seen with both force logging and force no-logging parameters.

Changes

 No changes.

Cause

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
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.