mount an external NFS (Network File System) to Oracle Database as a Service (DBaaS)

 it is possible to mount an external NFS (Network File System) mount point to Oracle Database as a Service (DBaaS) to write data into it. However, there are specific steps and considerations to ensure that the NFS mount is correctly configured and integrated with DBaaS, including security, network configuration, and appropriate user permissions.

Here’s an outline of the steps required to achieve this:

1. Prepare the NFS Server

  • Ensure the NFS server is configured and accessible from the DBaaS instance.
  • The NFS server should export the directory with appropriate permissions.
  • Example NFS export configuration on the server (/etc/exports file):

/nfs_shared_dir 192.168.x.x(rw,sync,no_root_squash)
Restart the NFS Services.

sudo exportfs -ra
2. Ensure Network Connectivity

  • Ensure that the DBaaS instance can reach the NFS server. You may need to set up appropriate network security rules (e.g., in Oracle Cloud Infrastructure's (OCI) Virtual Cloud Network (VCN) security lists or network security groups (NSG)).

    ping \<NFS\_server\_IP>

Test network connectivity to the NFS server from the DBaaS instance:

ping <NFS_server_IP>
3. Install NFS Client on DBaaS

  • If not already installed, install the NFS client on the DBaaS instance. This can be done with the following commands:

sudo yum install -y nfs-utils # For Oracle Linux
sudo apt-get install -y nfs-common # For Ubuntu-based systems

4. Create a Mount Point on DBaaS

  • Create a directory on the DBaaS instance where you want to mount the NFS export:

sudo mkdir /mnt/nfs_shared_dir
5. Mount the NFS Directory

  • Use the mount command to mount the NFS directory:

sudo mount -t nfs <NFS_server_IP>:/nfs_shared_dir /mnt/nfs_shared_dir
Ensure that the NFS mount is persistent across reboots by adding it to /etc/fstab:

<NFS_server_IP>:/nfs_shared_dir /mnt/nfs_shared_dir nfs defaults 0 0
6. Set Correct Permissions

  • Make sure that the Oracle database user (typically oracle) has the correct permissions to read from and write to the NFS-mounted directory.
  • Adjust ownership and permissions as needed:

sudo chown oracle:oinstall /mnt/nfs_shared_dir
sudo chmod 775 /mnt/nfs_shared_dir

7. Verify the Mount

  • Check if the NFS mount is active and accessible

df -h
ls /mnt/nfs_shared_dir

Comments

Post a Comment

Popular posts from this blog

Creating Physical Standby using RMAN Duplicate Without Shutting down The Primary

Oracle Server - Enterprise Edition - Version: 10.1.0.2 to 10.2.0.4 - Release: 10.1 to 10.2 Information in this document applies to any platform. Oracle Server Enterprise Edition - Version: 10.2.0.1 to 10.2.0.4 Goal  - Ref Metalink ID - 789370.1 The following note describes step-by-step procedure to create physical standby by using RMAN duplicate without shutting down the primary (Production) database. Database Name :- prim Primary db_unique_name :- prim standby db_unique_name :- stdby Primary Hostname :- raca.idc.oracle.com standby Hostname :- core1.idc.oracle.com Solution 1.Enable force logging. 2.Create SRL(standby redo logs). 3.Make proper changes in the parameter file of primary. 4.Backup the database that includes backup of datafiles, archivelogs and controlfile for standby and copy the backups to standby server. 5.Create the parameter file for standby, 6.Establish the connectivity from primary to standby. 7. Move backup to standby. 8 and 9. Start the standby instance. 10.U
Read more

How to Configure Logging for EM 12c Management Agent

The goal of this article is to provide instruction on how to enable logging for the Enterprise Manager 12c Management Agent.. ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- The logging properties for the agent are stored in $EMSTATE/sysman/config/emd.properties file, same as in 11.1. But the properties that control logging follow the log4j configuration syntax instead of the syntax supported by the 11.1 agent. To active changes to the logging parameters, you can use either of the emctl commands: emctl reload agent emctl setproperty agent Overview Agent logging entries look similar to the standard log4j logging, with the only significant difference being the prefix 'Logger.' that you will see on each line. For example: # logging properties Logger.log4j.appender.Rolling=org.apache.log4j.RollingFileAppender Logger.lo
Read more

index rebuild candidates oracle

Steps... CREATE TABLE index_log (  owner          VARCHAR2(30),  index_name     VARCHAR2(30),  last_inspected DATE,  leaf_blocks    NUMBER,     target_size    NUMBER,  idx_layout     CLOB); ALTER TABLE index_log ADD CONSTRAINT pk_index_log PRIMARY KEY (owner,index_name); CREATE TABLE index_hist (  owner          VARCHAR2(30),  index_name     VARCHAR2(30),  inspected_date DATE,  leaf_blocks    NUMBER,     target_size    NUMBER,  idx_layout     VARCHAR2(4000)); ALTER TABLE index_hist ADD CONSTRAINT pk_index_hist PRIMARY KEY  (owner,index_name,inspected_date); CREATE OR REPLACE PACKAGE index_util AUTHID CURRENT_USER IS vMinBlks     CONSTANT POSITIVE := 1000; vScaleFactor CONSTANT NUMBER := 0.6; vTargetUse   CONSTANT POSITIVE := 90;  -- equates to pctfree 10  vHistRet     CONSTANT POSITIVE := 10;  -- (#) records to keep in index_hist  procedure inspect_schema (aSchemaName IN VARCHAR2);  procedure inspect_index (aIndexOwner IN VARCHAR2, aIndexName IN VARCHAR2, a
Read more