A collection of 5 posts
ORA-65149: PDB name conflicts with existing service name in the CDB or the PDB
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=DBONEPDB; Session altered.
After restart, following tracing is seen: "psdgbt: bind csid (1) does not match session csid (XX) psdgbt: session charset is WE8ISO8859P15"
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:
Select on read-only standby database returns ORA-04045 and ORA-16000
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 access
ORA-39511: Correcting the ORACLE HOME
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 'datahost' CRS-0223: Resource 'ora.dbone.db' has