Understanding DBA Directory

 To create a directory:

CREATE OR REPLACE DIRECTORY alias AS 'pathname';
To Grant:
GRANT permission ON DIRECTORY alias TO {user | role | PUBLIC};

SQL> SELECT DIRECTORY_NAME , DIRECTORY_PATH FROM DBA_DIRECTORIES WHERE DIRECTORY_NAME = 'DUMP';

DIRECTORY_NAME                 DIRECTORY_PATH
------------------------------ ---------------
DUMP                          /home/appsolworld
$ chmod 777 /home/appsolworld
Just test run:

DECLARE
   Handle   UTL_FILE.FILE_TYPE;
BEGIN
   Handle := UTL_FILE.FOPEN ('DUMP', 'abc.txt', 'w');

   UTL_FILE.PUT ('This is the first line');
   UTL_FILE.FCLOSE (Handle);
EXCEPTION
   WHEN OTHERS
   THEN
      DBMS_OUTPUT.PUT_LINE (
         'Exception: SQLCODE=' || SQLCODE || '  SQLERRM=' || SQLERRM);
      RAISE;
END;
/

DBA_DIRECTORIES view which we use to check directory information. Let us describe that.

SQL> desc DBA_DIRECTORIES;
 Name					   Null?    Type
 ----------------------------------------- -------- ----------------------------
 OWNER					   NOT NULL VARCHAR2(128)
 DIRECTORY_NAME 			   NOT NULL VARCHAR2(128)
 DIRECTORY_PATH 				    VARCHAR2(4000)
 ORIGIN_CON_ID					    NUMBER

Now I am describing CDB_DIRECTORIES.

SQL> desc CDB_DIRECTORIES;
 Name					   Null?    Type
 ----------------------------------------- -------- ----------------------------
 OWNER					   NOT NULL VARCHAR2(128)
 DIRECTORY_NAME 			   NOT NULL VARCHAR2(128)
 DIRECTORY_PATH 				    VARCHAR2(4000)
 ORIGIN_CON_ID					    NUMBER
 CON_ID 					    NUMBER

We can see CDB_DIRECTORIES have the same structure as DBA_DIRECTORIES just one column is added CON_ID.

Let us explore more

Step 1: Query DBA_DIRECTORIES view from CDB$ROOT container

SQL> select * from dba_directories;

OWNER  DIRECTORY_ DIRECTORY_PATH      ORIGIN_CON_ID
----- ---------- -------------------- -------------
SYS	 ORACLE_HOME /				          1
	 E

SYS	 ORACLE_BAS /				          1
	 E

SYS	 OPATCH_LOG /u01/oracle/product/	   1
	 _DIR	    12.1.0/db_1/QOpatch

SYS	 OPATCH_SCR /u01/oracle/product/	  1
	 IPT_DIR    12.1.0/db_1/QOpatch

OWNER DIRECTORY_ DIRECTORY_PATH	      ORIGIN_CON_ID
----- ---------- -------------------- -------------

SYS	 OPATCH_INS /u01/oracle/product/	  1
	 T_DIR	     12.1.0/db_1/OPatch

SYS	 DATA_PUMP_ /u01/oracle/admin/my	  1
	 DIR	    cdb/dpdump/

SYS	 XSDDIR     /u01/oracle/product/	  1
		       12.1.0/db_1/rdbms/xm
		       l/schema

Step 2 : Query DBA_DIRECTORIES from pluggable database .

SQL> select * from dba_directories;

OWNER	 DIRECTORY_ DIRECTORY_PATH	 ORIGIN_CON_ID
-------- ---------- -------------------- -------------
SYS	 DATA_PUMP_ /appsolworld/admin/my	     1
	 DIR	    cdb/dpdump/

SYS	 OPATCH_INS /appsolworld/product/	     1
	 T_DIR	    12.1.0/db_1/OPatch

SYS	 OPATCH_SCR /appsolworld/product/	     1
	 IPT_DIR    12.1.0/db_1/QOpatch

SYS	 OPATCH_LOG /appsolworld/product/	     1
	 _DIR	    12.1.0/db_1/QOpatch

OWNER	 DIRECTORY_ DIRECTORY_PATH	 ORIGIN_CON_ID
-------- ---------- -------------------- -------------

SYS	 ORACLE_BAS /				     1
	 E

SYS	 ORACLE_HOM /				     1
	 E

SYS	 DEM	    /appsolworld/			     3
SYS	 XSDDIR     /appsolworld/product/	     3
		    12.1.0/db_1/rdbms/xm
		    l/schema

OWNER	 DIRECTORY_ DIRECTORY_PATH	 ORIGIN_CON_ID
-------- ---------- -------------------- -------------

Step 3 : Query CDB_DIRECTORIES from CDB$ROOT container :

SQL> select * from CDB_DIRECTORIES;

OWNER	 DIRECTORY_ DIRECTORY_PATH	 ORIGIN_CON_ID	   CON_ID
-------- ---------- -------------------- ------------- ----------
SYS	 DATA_PUMP_ /appsolworld/admin/my	     1		3
	 DIR	    cdb/dpdump/

SYS	 OPATCH_INS /appsolworld/product/	     1		3
	 T_DIR	    12.1.0/db_1/OPatch

SYS	 OPATCH_SCR /appsolworld/product/	     1		3
	 IPT_DIR    12.1.0/db_1/QOpatch

SYS	 OPATCH_LOG /appsolworld/product/	     1		3
	 _DIR	    12.1.0/db_1/QOpatch

OWNER	 DIRECTORY_ DIRECTORY_PATH	 ORIGIN_CON_ID	   CON_ID
-------- ---------- -------------------- ------------- ----------

SYS	 ORACLE_BAS /				     1		3
	 E

SYS	 ORACLE_HOM /				     1		3
	 E

SYS	 DEM	    /appsolworld			     3		3
SYS	 XSDDIR     /appsolworld/product/	     3		3
		    12.1.0/db_1/rdbms/xm
		    l/schema

OWNER	 DIRECTORY_ DIRECTORY_PATH	 ORIGIN_CON_ID	   CON_ID
-------- ---------- -------------------- ------------- ----------

SYS	 XSDDIR     /appsolworld/product/	     1		1
		    12.1.0/db_1/rdbms/xm
		    l/schema

SYS	 DATA_PUMP_ /appsolworld/admin/my	     1		1
	 DIR	    cdb/dpdump/

SYS	 OPATCH_INS /appsolworld/product/	     1		1
	 T_DIR	    12.1.0/db_1/OPatch


OWNER	 DIRECTORY_ DIRECTORY_PATH	 ORIGIN_CON_ID	   CON_ID
-------- ---------- -------------------- ------------- ----------
SYS	 OPATCH_SCR /appsolworld/product/	     1		1
	 IPT_DIR    12.1.0/db_1/QOpatch

SYS	 OPATCH_LOG /appsolworld/product/	     1		1
	 _DIR	    12.1.0/db_1/QOpatch

SYS	 ORACLE_BAS /				     1		1
	 E

SYS	 ORACLE_HOM /				     1		1
	 E

OWNER	 DIRECTORY_ DIRECTORY_PATH	 ORIGIN_CON_ID	   CON_ID
-------- ---------- -------------------- ------------- ----------

Step 4 : Query CDB_DIRECTORIES from pluggable database PDB1:

SQL> select * from CDB_DIRECTORIES;

OWNER	 DIRECTORY_ DIRECTORY_PATH	 ORIGIN_CON_ID	   CON_ID
-------- ---------- -------------------- ------------- ----------
SYS	 DEM	    /appsolworld			     3		3
SYS	 XSDDIR    /appsolworld/product/	     3		3
		    12.1.0/db_1/rdbms/xm
		    l/schema

SYS	 DATA_PUMP_ /appsolworld/admin/my	     1		3
	 DIR	    cdb/dpdump/

SYS	 OPATCH_INS /appsolworld/product/	     1		3
	 T_DIR	    12.1.0/db_1/OPatch


OWNER	 DIRECTORY_ DIRECTORY_PATH	 ORIGIN_CON_ID	   CON_ID
-------- ---------- -------------------- ------------- ----------
SYS	 OPATCH_SCR /appsolworld/product/	     1		3
	 IPT_DIR    12.1.0/db_1/QOpatch

SYS	 OPATCH_LOG /appsolworld/product/	     1		3
	 _DIR	    12.1.0/db_1/QOpatch

SYS	 ORACLE_BAS /				     1		3
	 E

SYS	 ORACLE_HOM /				     1		3
	 E

OWNER	 DIRECTORY_ DIRECTORY_PATH	 ORIGIN_CON_ID	   CON_ID
-------- ---------- -------------------- ------------- ----------


8 rows selected.

SQL>

We have queries DBA_DIRECTORIES and CDB_DIRECTORIES from root container and pluggable database container.

In step 1 we have queried DBA_DIRECTORIES from root container which shows directories associated with Root container.

In step 2 we have queries DBA_DIRECTORIES from mypdb1 which shows all directories associated with Pluggable container mypdb1.

In step 3 we have queries CDB_DIRECTORIES from root container which shows directories of root container as well as all directories of all pluggable database we can see associated CON_ID in CDB_DIRECTORIES.

In step 4 we have queried CDB_DIRECTORIES from mypdb1 which shows same output as DBA_DIRECTORIES just one column more which shows CON_ID of PDB1 that is 3.

Comments

Post a Comment

Popular posts from this blog

How to drop index and before dropping it how to get the DDL.

  Oracle DROP INDEX statement DROP INDEX [schema_name.]index_name; DECLARE index_count INTEGER; BEGIN SELECT COUNT(*) INTO index_count FROM USER_INDEXES WHERE INDEX_NAME = 'index_name' ; IF index_count > 0 THEN EXECUTE IMMEDIATE 'DROP INDEX index_name' ; END IF; END; / In case want to check whether index exists and then delete it. If try to drop a non-existing, you will get the following error: SQL Error : ORA -01418 : specified index does not exist In SQLplus, set these before running the commands set long 100000 set longchunksize 100000 select DBMS_METADATA.GET_DDL( 'INDEX' , 'index_name') from all_indexes where owner in ( USER , 'USER_OTHER_THAN_LOGGED_IN_USER' ); Use below script to fetch metadata other information. SELECT DBMS_METADATA,GET_GRANTED_DDL('SYSTEM_GRANT','SSO******') from dual;
Read more

PRVG-11250 : The check "RPM Package Manager database" was not performed because

Following message reported from cluvfy while performing pre-requisite for Clusterware Installation:  Verifying RPM Package Manager database ...INFORMATION PRVG-11250 : The check "RPM Package Manager database" was not performed because it needs 'root' user privileges. SOLUTION Execute runcluvfy manually with "-method root" option and enter root password when prompted : Example: $/runcluvfy.sh stage -pre crsinst -n <HOSTNAME1>,<HOSTNAME2> -method root Enter "ROOT" password: For reference metalink doc id :  2548970.1
Read more

ORA-00257:archiver error, connect internal only until freed

  Issue: Application log shows below error and users are unable to connect to the database. 0RA-00257:archiver error, connect internal only until freed (OR) 0RA-00257:archiver error, connect internal only until freed ORA-16020: less destinations available than specified by LOG_ARCHIVE_MIN_SUCCEED_DEST Fix: 1) Check if there are any errors for the archive destination(s). Make sure that the number of VALID archive destinations is greater than or equal to the value specified by LOG_ARCHIVE_MIN_SUCCEED_DEST initialization parameter. set pages 1000 col dest_name for a30 col destination for a60 SELECT dest_id, dest_name, binding, status, destination, error FROM v$archive_dest; SHOW PARAMETER log_archive_min_succeed_dest 2) If space is full in one or more of the archive destinations (or if destination is not available), take any of the following steps: 2.a) Manually move the archives to another location and delete them from archive destination.   (OR) 2.b) Change the archive des...
Read more

Verifying Daemon “Avahi-Daemon” Not Configured And Running …FAILED (PRVG-1360)

  Execute "/tmp/CVU_19.0.0.0.0_grid/runfixup.sh" as root user on nodes "shsebs7idb1" to perform the fix up operations manually Press ENTER key to continue after execution of "/tmp/CVU_19.0.0.0.0_grid/runfixup.sh" has completed on nodes "shsebs7idb1" Fix: Daemon "avahi-daemon" not configured and running   Node Name                             Status   ------------------------------------  ------------------------   shsebs7idb1                           failed ERROR: shsebs7idb1: PRVG-9023 : Manual fix up command "/tmp/CVU_19.0.0.0.0_grid/runfixup.sh" was not issued by root user on node "shsebs7idb1" Result: "Daemon "avahi-daemon" not configured and running" could not be fixed on nodes "shsebs7idb1" SOLUTION: To fix this error, stop and disable avahi-daemon service. 1. Check avahi-daemon status: [root@shsebs7idb1 ~]# ls -...
Read more

Linux OL7/RHEL7: PRVE-0421 : No entry exists in /etc/fstab for mounting /dev/shm

  This is due to below bugs: OL7 -  Unpublished Bug 21441387- 12.2/MAIN/OL7.1: CVU REPORTS /DEV/SHM NOT MOUNTED WHEN IT IS MOUNTED  21441387.8 RHEL 7 - Unpublished Bug 25907259 : RHEL7.2: CVU REPORTS /DEV/SHM NOT MOUNTED WHEN IT IS MOUNTED  25907259.8 As a work-around in OL7: In OL7, the /dev/shm is not mounted in /etc/fstab on a fresh system, it is done in: [root@testc140 u02]# ll /usr/lib/dracut/modules.d/99base/init.sh -rwxr-xr-x. 1 root root 11379 Mar 26 10:14 vi /usr/lib/dracut/modules.d/99base/init.sh and comment the below lines 62 if ! ismounted /dev/shm; then 63 mkdir -m 0755 /dev/shm 64 mount -t tmpfs -o mode=1777,nosuid,nodev,strictatime tmpfs /dev/shm >/dev/null 65 fi so, this validation is not really valid for OL7.    We can also safely ignore this message. For reference metalink id: -  Doc ID 2065603.1
Read more

SKIP DNS RESLOV.CONF CHECK DURING RAC CONFIGURATION

 shsebs7idb1: PRVG-2064 : There are no configured name servers in the file              '/etc/resolv.conf' on the nodes "shsebs7idb1" Solution: [root@shsebs7idb2 ~]# ls -ltr /etc/resolv.conf -rw-r--r--. 1 root root 78 Jul  3 11:02 /etc/resolv.conf [root@shsebs7idb2 ~]# mv /etc/resolv.conf /etc/resolv.conf.sid Rename resolv.conf to resolv.conf.sid for example and re run the installation again . It  worked for me
Read more

CPU Patch Analysis

 Oracle CPU patch analysis Identifying the Latest Critical Patch Update for Oracle E-Business Suite Release 12.2 (Doc ID 2484000.1) Database Quick-Link If you only care about the database patches, this MOS note steps you through really easily. Assistant: Download Reference for Oracle Database/GI Update, Revision, PSU, SPU(CPU), Bundle Patches, Patch sets and Base Releases (Doc ID 2118136.2) https://www.oracle.com/security-alerts/ Critical Patch Updates Critical Patch Updates provide security patches for supported Oracle on-premises products. They are available to customers with valid support contracts. Starting in April 2022, Critical Patch Updates are released on the third Tuesday of January, April, July, and October (They were previously published on the Tuesday closest to the 17th day of January, April, July, and October). The next four dates are: 16 April 2024 16 July 2024 15 October 2024 21 January 2025 A pre-release announcement will be published on the Thursday preceding eac...
Read more

How to write to a CSV file using Oracle SQL*Plus

  SPOOL command  The  SPOOL  command is  unavailable  in the browser-based SQL*Plus version,  iSQL*Plus . To generate files while using iSQL*Plus, change the necessary preference settings to directly output to a file. This is accomplished using the  SPOOL  statement. While  SPOOL  is  active , SQL*PLus will store the output of any query to the specified file. Therefore, the next command to enter is  spool : spool filepath Skipping ahead slightly,  after  your query is inserted, you also need to halt  spool  so the file output is closed by using the  spool off  command: spool off Insert the query  The last step after the settings are modified and  spool  is running is to insert your query. For our simple example, we’re outputting all books from our  books  table. SELECT   title,   author FROM   authors; Don’t forget the semi...
Read more

How to troubleshoot Long Running Concurrent Request in EBS 12.2

 The following points need to answer before jumping into troubleshooting: Are there any recent code changes done in the concurrent program?           Check long_running_sid and verify the recent code change of last_ddl_timestamp after a             discussion with the developer. Was this running long in the last few run as well, or was this time only?            ==> Check the program history. How much time does it take to complete?           Once again program history can give us some idea. Are these jobs fetching higher data compared to the last run           ===> Confirm on data change . Query Plan change will indicate this issue. Does this job runs at any specific time or it can be run anytime           ===> The nature of the job can help to understand the job's nature. Does this job fetch data using DB Link...
Read more

How To Manage Space of The FRA in the Oracle DB

  Delete Old files connect with the target database using RMAN RMAN target / Delete the old files RMAN> delete obsolete; Remove Restore Points SQL> SELECT name, storage_size FROM gv$restore_point; Drop the restore point SQL> DROP restore point RP; Delete the archive logs RMAN> DELETE archivelog ALL Increase the Space SQL> ALTER SYSTEM SET db_recovery_file_dest_size = 20G scope=both; Disable the Flashback ALTER DATABASE flashback off;
Read more