ORA-44787: Service cannot be switched into on Oracle 12c PDB

-
If you encounter ORA-44787 when switching to PDB using alter session set container, main reason for same can be the unavailability of default PDB service. When a PDB is enabled it does starts its own default PDB service with service name set to the PDB name. Although it is possible to create new service for PDB using DBMS_SERVICE.create_service, it is required to keep the default service up and running as it is used by internal operations. If you have stopped the default service it is the main reason for this particular error.

Below is a simple example where stopping of default PDB service leads to ORA-44787

Creating the new service

 SQL> alter session set container=ORCLPDB;  
 Session altered.  
 SQL> BEGIN  
  DBMS_SERVICE.create_service(  
   service_name => 'new_service',  
   network_name => 'NEW_SERVICE'  
  );  
  END;  2  3  4  5  6  
  7 /  
 PL/SQL procedure successfully completed.  
 SQL> exec dbms_service.start_service('new_service');  
 PL/SQL procedure successfully completed.  
 SQL>

Now this new service can be used to connect to the database. Also untile you have the default services running alter session set container should work without any issue.

Stopping the default service

 SQL> alter session set container=ORCLPDB;  
 Session altered.  
 SQL> SELECT NAME FROM V$ACTIVE_SERVICES;  
 NAME  
 ----------------------------------------------------------------  
 new_service  
 orclpdb  
 SQL> exec DBMS_SERVICE.STOP_SERVICE('orclpdb');  
 PL/SQL procedure successfully completed.  
 SQL>   
 </code>  
 Now if you try to switch to the PDB it will faile with ORA-44787.  
 SQL> show pdbs;  
   CON_ID CON_NAME            OPEN MODE RESTRICTED  
 ---------- ------------------------------ ---------- ----------  
      2 PDB$SEED            MOUNTED  
      3 ORCLPDB            READ WRITE NO  
 SQL> alter session set container=ORCLPDB;  
 ERROR:  
 ORA-44787: Service cannot be switched into.  
 SQL> exit
Although the switch to PDB fails external connections using the new service name will working. But this can cause manageability issues.
A quick fix would be to restart the PDB using below steps. 
 SQL> show pdbs;  
   CON_ID CON_NAME            OPEN MODE RESTRICTED  
 ---------- ------------------------------ ---------- ----------  
      2 PDB$SEED            MOUNTED  
      3 ORCLPDB            READ WRITE NO  
 SQL> alter pluggable database "ORCLPDB" close;  
 Pluggable database altered.  
 SQL> show pdbs;  
   CON_ID CON_NAME            OPEN MODE RESTRICTED  
 ---------- ------------------------------ ---------- ----------  
      2 PDB$SEED            MOUNTED  
      3 ORCLPDB            MOUNTED  
 SQL> alter session set container=ORCLPDB;  
 Session altered.  
 SQL> startup;  
 Pluggable Database opened.  
 SQL> exit  
 Disconnected from Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production  
 ora12c@racbprdb1:~$ sqlplus sys as sysdba  
 SQL*Plus: Release 12.2.0.1.0 Production on Mon Aug 10 13:51:37 2020  
 Copyright (c) 1982, 2016, Oracle. All rights reserved.  
 Enter password:  
 Connected to:  
 Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production  
 SQL> show pdbs;  
   CON_ID CON_NAME            OPEN MODE RESTRICTED  
 ---------- ------------------------------ ---------- ----------  
      2 PDB$SEED            MOUNTED  
      3 ORCLPDB            READ WRITE NO  
 SQL> alter session set container=ORCLPDB;  
 Session altered.  
 SQL> show pdbs;  
   CON_ID CON_NAME            OPEN MODE RESTRICTED  
 ---------- ------------------------------ ---------- ----------  
      3 ORCLPDB            READ WRITE NO  
 SQL>


Comments

Post a Comment

Popular posts from this blog

ORA-16433: The database or pluggable database must be opened in read/write

-
Image
ORA-16433 is an error returned when a database cannot be opened. This can be a result of multiple conditions including, The inconsistency of the database Physical corruption Loss of dependent files or access issues etc.. More often than not the solution is to recover from available backups, but there can be situations where backups are not available, specially on UAT or Test setups. Although not the ideal scenario, in this type of situation you might want to open the databases even with inconsistency.  In Comes --> _ALLOW_RESETLOGS_CORRUPTION First, if you are in a position to use _ALLOW_RESETLOGS_CORRUPTION=TRUE, that means it has to be a critical moment, and when you come across more ora- errors while you are trying to reopen the databsae, that can be annoying. Note - _ALLOW_RESETLOGS_CORRUPTION=TRUE must only be used after Oracle support confirmation as a last resort. Also make sure to take cold backup before proceeding. Basic steps to be followed to resolve ORA 16433 af...
Read more

Oracle Multitenant - Create new service for PDB using DBMS_SERVICE

-
Image
When an Oracle PDB is created it starts up a default service with the PDB name. For direct connections to    PDB this service can be used. But there are situations where new service name is required in PDB level, common example is after a PDB restoration/clone, in order to enable application connections without changes in connection string. Setting service_names parameter in PDB level is not possible hence it is not an option in multitenant setup. How to create a new PDB service on Oracle 12C Check the current services, here only the default service is running, SQL> show pdbs; CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 3 NFACTORPDB READ WRITE NO SQL> select service_id, name, pdb from dba_Services; SERVICE_ID NAME PDB ---------- ---------------------------------------- ---------- 7 nfactorpdb NFACTORPDB SQL> ...
Read more

Wait for unread message on broadcast channel - Blocking Sessions

-
Image
What is Wait for unread message on broadcast channel wait event? Wait for unread message on broadcast channel is a wait event where source destination communication is involved and the database is waiting for a reply from remote party. Mostly this wait is seen related to data pump export (expdp) or import (impdp) operations. Although categorized in idle wait class "Wait for unread message on broadcast channel" can become the blocking session for some other sessions. Common causes for stuck sessions waiting on this wait event includes, Broken databases links, where remote database is not responding. Abnormally killed remote processes causing the sessions to wait. When a session is waiting on "Wait for unread message on broadcast channel" it can become a blocking session for dependent sessions. Most probably these sessions will be waiting on "library cache pin" or related concurrency wait events. The blocking_session column of (g)v$session view...
Read more