Online DBA

<<Back to Oracle Backup & Recovery Main Page RMAN-20005: target database name is ambiguous RMAN> RESTORE CONTROLFILE FROM TAG 'PR_WEEKLY_INCR0'; Starting restore at 26-OCT-20 RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of restore command at 10/26/2020 09:43:38 RMAN-12010: automatic channel allocation initialization failed RMAN-06004: ORACLE error from recovery catalog database: RMAN-20005: target database name is ambiguous Cause: Multiple registration of the database in catalog. Run the query below against catalog database to find out the duplicate entry  SQL>SELECT DB.DB_KEY,DB.DB_ID, DB.CURR_DBINC_KEY, DBINC.DB_NAME         FROM DB, DBINC        WHERE DB.CURR_DBINC_KEY = DBINC.DBINC_KEY          AND DBINC.DB_NAME   = 'UC43P' ; DB_KEY  DB_ID  CURR_DBINC_KEY  DB_NAM

<<Back to Oracle DATAPUMP Main Page DataPump Export (EXPDP) Error ORA-39095 Dump File Space Has Been Exhausted ORA - 39095 : " dump file space has been exhausted. Unable to allocate 8192 bytes" job system.sys_export_full_02 stops due to fatal error. cause: Not enough number of dump files defined expdp can create maximum 99 dumpfiles so if you are exporting very large database ensure to define filesize big enough so the total export can fit in <=99 dumpfiles The issue can also occur if you specify the dumpfiles manually for example if your parfile looks  like this full=Y directory=<DIRECTORY_NAME> dumpfile=full_1.dmp,full2_2.dmp,full_3.dmp filesize=10 if export did not finish in 3 dumpfiles and need to created 4th one you will receive the error ORA-39095: Dump file space has been exhausted: Unable to allocate 8192 bytes Job "SYSTEM"."sys_export_full_02" stopped due to fatal error at Wed Oct 7 21:13:55 2020 elapsed 0 10:09:02 Job sys_export_fu

<<Back to Oracle DATAPUMP Main Page How to find if the export job is running or Hanging  SET PAUSE ON SET PAUSE 'Press Return to Continue' SET PAGESIZE 60 SET LINESIZE 300 col MODULE for a30 col EVENT for a50 col SQL_ID for a15 col STATUS for a10 SELECT   v.status,   v.SID,   v.serial#,   io.block_changes,   event, module,   v.sql_id FROM   v$sess_io io,   v$session v WHERE   io.SID=v.SID AND   v.saddr IN (SELECT saddr FROM dba_datapump_sessions)  ORDER BY   io.BLOCK_CHANGES / Observe the BLOCK_CHANGES column if the value keeps increasing , your  job is running and not hanging

<<Back to Oracle DATAPUMP Main Page Is there any limit on number of files expdp can create Yes there is a limit.  The total number of dump files that can be created by expdp is  99. so if you specify dumpfile parameter like below and your export did not finish within 99 dumpfiles export will stop therefore if you are exporting big database specify bigger filesize  dumpfile=exp_full_%U.dmp 

<<Back to DB Administration Main Page How to Convert Classical Database in Multitenant Architecture Database Source DB (Classical Architecture) : ORCL1P Target DB (Multitenant Architecture) : CDB01DB ORCL1P to be plugged as PDB01P into  CDB01DB Container DB ( CDB01DB ) should already be installed and present NOTE: Demonstration in this post assumes the conversion on same host Execute on  ORCL1P Step1>Place the non-CDB in read-only mode SQL>select name from v$database; SQL>shutdown immediate; SQL>startup open read only; SQL> select name,open_mode from v$database; Step2> Prepare Conversion BEGIN  DBMS_PDB.DESCRIBE(  pdb_descr_file => '/ora_temp/rman/ORCL1P/PDB01P.xml'); END; / Step3> shutdown the NON-CDB database ( NONCDB) SQL>shutdown immediate; Execute on  CDB01DB Step4> Check the compatibility. Now connect to the container database, where it need to be plugged. SET SERVEROUTPUT ON DECLARE  compatible CONSTANT VARCHAR2(3) :=  CASE DBMS_PDB.CH