Install & configure NRDOT for Oracle monitoring with CLI

This recipe monitors one or more Oracle Database instances (each reachable via SSH) from a single collector. Instead of prompting for a single host/container/credential set, it reads an instances file (YAML) listing every instance to monitor, and optionally a secrets file to pin specific monitoring-user passwords instead of auto-generating them.

Before you run this command, have ready:

• SSH access (with agent forwarding) to every Oracle Database host listed, where each ssh_user can run sudo su - oracle without a password prompt
• Container type per instance (CDB for all PDBs, or a single PDB name)
• CDB or PDB service name per instance
• Whether you want Basic or Advanced metrics

1. Create the instances file. Add one entry per Oracle Database instance you want this collector to monitor; just one entry if you're only monitoring a single instance:

   bash

   Copia

   $
   cat > ~/oracle-instances.yml << 'EOF'
   $
   instances:
   $
     - host: dbhost1.example.com
   $
       port: 1521
   $
       ssh_user: opc
   $
       container_type: 1
   $
       pdb_name:
   $
       service: ORCLCDB
   $
       login_name: newrelic
   $
   EOF

   container_type is 1 for CDB (monitors all PDBs, creates a common c##<login_name> user) or 2 for a single PDB (pdb_name required only then). Enter login_name without the c## prefix: the recipe adds it for you in CDB mode.

2. (Optional) Create a secrets file to pin a fixed monitoring-user password per instance instead of letting the recipe auto-generate one. Self-hosted Oracle needs no admin credentials here. The monitoring user is created via SSH and OS-authenticated SYSDBA access:

   bash

   Copia

   $
   umask 077
   $
   cat > ~/oracle-secrets.env << 'EOF'
   $
   NR_CLI_ORACLE_LOGIN_PASSWORD_1=SomeFixedPassword1
   $
   EOF
   $
   chmod 600 ~/oracle-secrets.env

   Leave the secrets file path blank (or point it at a file that doesn't exist) to auto-generate a random password for every instance instead.

Run this from a host with SSH access (with agent forwarding) to every Oracle Database host listed in your instances file:

$
curl -Ls https://download.newrelic.com/install/newrelic-cli/scripts/install.sh | bash && sudo NEW_RELIC_API_KEY=INSERT_YOUR_API_KEY NEW_RELIC_ACCOUNT_ID=INSERT_YOUR_ACCOUNT_ID NEW_RELIC_REGION=INSERT_YOUR_REGION /usr/local/bin/newrelic install -n nrdot-collector-oracle

The CLI prompts interactively for the following variables. You can also set them ahead of time as environment variables to run non-interactively.

This recipe monitors one or more RDS Oracle endpoints from a single collector, using an instances file plus a secrets file.

Before you run this command, have ready:

• RDS Oracle endpoint, listener port, and DB service name for every instance
• RDS master username and password for every instance
• Whether you want Basic or Advanced metrics

1. Create the instances file (one entry per RDS Oracle endpoint you want this collector to monitor, still just one entry if you're only monitoring a single instance):

   bash

   Copia

   $
   cat > ~/oracle-instances.yml << 'EOF'
   $
   instances:
   $
     - host: rds-orders.abcdef123.us-east-1.rds.amazonaws.com
   $
       port: 1521
   $
       service: ORDERSDB
   $
       login_name: newrelic
   $
   EOF

2. Create the secrets file with the RDS master username and password for each instance, indexed to match the instances file's order. You can optionally pin a fixed monitoring-user password per instance too. Leave it out to auto-generate one:

   bash

   Copia

   $
   umask 077
   $
   cat > ~/oracle-secrets.env << 'EOF'
   $
   NR_CLI_ORACLE_ADMIN_USER_1=admin
   $
   NR_CLI_ORACLE_ADMIN_PASSWORD_1=YourMasterPassword1
   $
   EOF
   $
   chmod 600 ~/oracle-secrets.env

$
curl -Ls https://download.newrelic.com/install/newrelic-cli/scripts/install.sh | bash && sudo NEW_RELIC_API_KEY=INSERT_YOUR_API_KEY NEW_RELIC_ACCOUNT_ID=INSERT_YOUR_ACCOUNT_ID NEW_RELIC_REGION=INSERT_YOUR_REGION /usr/local/bin/newrelic install -n nrdot-collector-oracle-rds

The CLI prompts interactively for the following variables. You can also set them ahead of time as environment variables to run non-interactively.

This recipe monitors one or more Oracle Autonomous Database (ADB) instances from a single collector, using an instances file plus a secrets file. Each instance connects over mutual TLS (ADB's default) using its own downloaded wallet. Don't share one wallet directory between instances.

Before you run this command, have ready:

• For each instance: its connection string (host, port, service, from the ADB console's Database connection > Connection strings)
• For each instance: its downloaded Oracle Wallet (ADB console's Database connection > Download wallet), unzipped to its own directory on the collector host
• ADB admin (ADMIN) username and password for every instance

1. Create the instances file. Add one entry per ADB instance you want this collector to monitor; just one entry if you're only monitoring a single instance:

   bash

   Copia

   $
   cat > ~/adb-instances.yml << 'EOF'
   $
   instances:
   $
     - host: adb1.adb.us-ashburn-1.oraclecloud.com
   $
       port: 1522
   $
       service: myadb1_high
   $
       login_name: newrelic
   $
       wallet_dir: /home/opc/wallet1
   $
   EOF

   wallet_dir is the directory where that instance's wallet was unzipped (must contain cwallet.sso and sqlnet.ora); an instance with a missing or invalid wallet directory is skipped rather than failing the whole install.

2. Create the secrets file with the ADB admin username and password for each instance, indexed to match the instances file's order. You can optionally pin a fixed monitoring-user password per instance too. Leave it out to auto-generate one:

   bash

   Copia

   $
   umask 077
   $
   cat > ~/adb-secrets.env << 'EOF'
   $
   NR_CLI_ORACLE_ADMIN_USER_1=ADMIN
   $
   NR_CLI_ORACLE_ADMIN_PASSWORD_1=YourAdminPassword1
   $
   EOF
   $
   chmod 600 ~/adb-secrets.env

Run this from a host that has sqlplus (Oracle Instant Client) on PATH and network connectivity (mTLS) to every ADB instance listed:

$
curl -Ls https://download.newrelic.com/install/newrelic-cli/scripts/install.sh | bash && sudo NEW_RELIC_API_KEY=INSERT_YOUR_API_KEY NEW_RELIC_ACCOUNT_ID=INSERT_YOUR_ACCOUNT_ID NEW_RELIC_REGION=INSERT_YOUR_REGION /usr/local/bin/newrelic install -n nrdot-collector-oracle-adb

The CLI prompts interactively for the following variables. You can also set them ahead of time as environment variables to run non-interactively.