Skip to main content

Unable to connect to PDB in Oracle 12.2

Unable to connect to PDB  as a system in Oracle 12.2


Issue:  When we are trying to connect as system user it is hanging forever and not allowing new connections. (No issues observed with existing application connections)


Error: Errors in alert log file

Errors in file /u01/app/oracle/diag/rdbms/XXXXX/XXXXX/trace/xxxxx_ora_127384.trc:
ORA-04088: error during execution of trigger 'SYS.BLOCK_TOOLS_FROM_PROD'
ORA-00604: error occurred at recursive SQL level 1
ORA-20000: Development tools are not allowed here.
ORA-06512: at line 13
2020-06-10 12:31:44.388000 +00:00
WARNING: CLMN has failed to cleanup a dead process for 2400 attempts

2020-06-10 08:38:11.555000 +00:00
WARNING: CLMN has failed to cleanup a dead process for 1000 attempts
Errors in file /u01/app/oracle/diag/rdbms/xxxxx/xxxxx/trace/xxxxx_clmn_114254.trc  (incident=8918402) (PDBNAME=CDB$ROOT):
ORA-00700: soft internal error, arguments: [ksuxdl: cleanup failures], [0x351C23FC0], [process], [1000], [0x34BDE7CC8], [session], [601], [], [], [], [], []
Incident details in: /u01/app/oracle/diag/rdbms/xxxxx/xxxxxx/incident/incdir_8918402/xxxxx_clmn_114254_i8918402.trc
Dumping diagnostic data in directory=[cdmp_20200610083812], requested by (instance=1, osid=114254 (CLMN)), summary=[incident=8918402].



Workaround:  After restarting container database we were able to connect without any issues but issue recurring again after 3 days

Solution: We have raised Service request with oracle support and Support team confirmed that this is a bug 29794462.

 Latest update from Oracle:



Labels:

Comments

Post a Comment

Popular posts from this blog

ORA-65139: Mismatch between XML metadata file and data file

Error: CDB$ROOT@EBTUPRDC> CREATE PLUGGABLE DATABASE EBTUSPRDPDB1 using '/home/oracle/EBTUSPRDC.xml' nocopy tempfile reuse; CREATE PLUGGABLE DATABASE EBTUSPRDPDB1 using '/home/oracle/EBTUSPRDC.xml' nocopy tempfile reuse * ERROR at line 1: ORA-65139: Mismatch between XML metadata file and data file /u05/odb/ORADATA_1/EBTUSPRDC/datafile/system.1531.807800993 for value of fcpsb (2230502002 in the plug XML file, 2230505492 in the data file) Fix: Don't open Non-CDB database until we complete pdb creation other wise we will get above error. Shutdown immediate; startup mount; alter database open read only; create xml file. shutdown immediate; Connect to CDB and Create Pluggable database .
2 comments
Read more

Useful OEM Queries to get Target details from OEM Repository

List Targets with TNS Listener ports configured : SELECT mgmt$target.host_name , mgmt$target.target_name , mgmt$target.target_type , mgmt$target_properties.property_name , mgmt$target_properties.property_value FROM mgmt$target , mgmt$target_properties WHERE ( mgmt$target.target_name = mgmt$target_properties.target_name ) AND ( mgmt$target.target_type = mgmt$target_properties.target_type ) and ( mgmt$target.target_type = 'oracle_listener' ) and ( mgmt$target_properties.property_name = 'Port' ); Devora02       LISTENER_ora02                       oracle_listener Port 1529 Devora01       LISTENER_ora01                       oracle_listener Port 1529 Devora04       LISTENE...
1 comment
Read more

TFA-00002 : Oracle Trace File Analyzer (TFA) is not running

TFA Failed to start listening for commands on one of the Rac Node : As a root user /etc/init.d/init.tfa  start Starting TFA.. start: Job is already running: oracle-tfa Waiting up to 100 seconds for TFA to be started.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Successfully started TFA Process.. . . . . . TFA-00002 : Oracle Trace File Analyzer (TFA) is not running TFA Failed to start listening for commands Solution : run synctfanodes.sh  if you have root password . if no root password copy below files to TFA Failed node and try to restart TFA .. Please check whether these 4 files exist on all nodes are similar. TFA_HOME/server.jks TFA_HOME/client.jks TFA_HOME/internal/ssl.properties   TFA_HOME/internal/ portmapping.txt If not similar just copy these files to TFA Failing node and try TFA Restart ..It Worked for me .   [root@host01]# ./tfactl  -v "debug" start Starting TFA...
Post a Comment
Read more