When doing a expdp of a PDB, you may see the next error message: ORA-20000: Resource Manager Plan Is Not Active or is not managing CPU usage This are the steps to avoid the error message and be able to do the export:

After refreshing a database with a container database, you need to restore the refreshed name of the pluggable database to the expected in the non-prod environment. For this, you would first connect to the PDB and restart it on "open restrict" mode: SQL> alter session set container=

In a situation like a server being rebooted due activities that need to be carried by system administrators and then you get the go to start the databases, you may see the alertlog showing the same trace file appearing repetitively at the alertlog. The trace file shows the following text:

A customer reports that while doing a select through a DB Link or directly to a standby database that is opened in read-only, the following error is shown: SQL> select * from DATAHUB1; * ERROR at line 1: ORA-04045: errors during recompilation/revalidation of PUBLIC.DATAHUB1 ORA-16000: database open for read-only

When you're trying to start the database, you could find this error: SQL> startup restrict; ORA-39511: Start of CRS resource for instance '223' failed with error: [CRS-2800: Cannot start resource 'ora.DATA.dg' as it is already in the INTERMEDIATE state on server