Add a database

Connect an Oracle database to Scops with one read-only account. Scops tests the connection before it adds the database.

The Add Database dialog on its Connection tab, after a connection test that passed

Before you begin

  • An Oracle 12.2 or later account with CREATE SESSION and SELECT_CATALOG_ROLE, or with a grant on each view. See Database user privileges.
  • A network path from the Scops server to the listener, usually port 1521.
  • The Manage databases permission, and a free place in your edition.

Connect a database

  1. Open Databases in the top bar and click Add Database.

  2. On Connection, enter the Host, Port and Service name. Select the DB credential, or click Add to save a new one.

    The Add Credential dialog with a credential name, a DB user and a password field
  3. Click Test Connection. The other tabs open only after the test passes. If it fails, see If the test fails.

  4. Click Next. On Details, select the Environment and the Group.

  5. Click Next. On Policies, check the policies and the switches.

  6. Click Add Database.

Collection starts within a minute. A window shows what is ready and what comes next: Radar Engine and Scops AI get more accurate as the history grows. Later, Learning on the database bar shows the same.

Connection

FieldWhat to enter
HostThe host name, an IP address, or the SCAN name of a RAC cluster.
PortThe listener port, 1521 by default.
Service nameFor a pluggable database, its own service. For a container database, the service of its root.
DB credentialThe saved user name and password. To add one, you need Manage credentials.

If the test fails

The cause shows under the fields. Correct it and test again.

A failed connection test with 7 required grants missing and the Show Script button
The test saysWhat to do
An Oracle error, such as ORA-12514See A database cannot connect.
"Oracle 12.1 Enterprise is not supported."Scops cannot monitor this release.
"The Oracle version could not be read"The account cannot read V$INSTANCE or PRODUCT_COMPONENT_VERSION. Grant the required views.
"7 required grants missing."Click Show Script. Ask a DBA to run the Monitoring script as SYS, in the pluggable database for a PDB.
"2 Diagnostics and Tuning Pack grants missing."Do the same, or set Diagnostics and Tuning Pack to off.

The Grant Script dialog

Show Script shows the GRANT scripts for the missing grants in three tabs: Monitoring, Automation and Add-ons. Without the Monitoring grants, you cannot add the database. Grant the other two for the features that you use. See The GRANT script.

Catalog Role asks for the views with one role. If your site does not permit the role, click Individual Grants: the scripts then have one GRANT for each view. See Grant the views one by one.

The Grant Script dialog with the Monitoring, Automation and Add-ons tabs and the Monitoring script

Turn on Diagnostics and Tuning Pack

Do this only for a database with a license for both Oracle packs. Monitoring does not need them.

  1. On Connection, set Diagnostics and Tuning Pack to on.

  2. Tick the license confirmation. Scops records your user name and the time.

  3. Click Test Connection. The test also checks the pack grants.

The Diagnostics and Tuning Pack switch on, with its license confirmation ticked

The switch turns on SQL plan baselines, SQL profiles, the automatic plan fix, the SQL Tuning Advisor, SQL Monitor and AWR plans. If you set it to off, Scops removes the confirmation.

Add an OS credential

This is optional. Scops then reads the alert, ASM, CRS and listener logs over SSH, usually port 22.

  1. On Connection, select an OS credential, or click Add next to it.

  2. Use an OS user that can read the Oracle logs, usually oracle or grid, not root.

Then select Show OS Logs in the row menu of the database, open Settings, click Find Log Files, turn on Collect OS logs and click Save.

Details

The Details tab with an environment, a group, an owner and a note
FieldWhat it is
EnvironmentRequired. Where the database runs, for example Production. To add one, you need Manage environments.
GroupRequired. The team or application. To add one, you need Manage groups.
Display nameA second name for alerts, reports and the database pickers.
OwnerThe person who owns the database.
NotesUp to 4,000 characters.

Policies and monitoring

The Policies tab with the default policies and the Cache, Radar and Ask Scops switches on
FieldWhat it doesDefault
AlertsThe alert policy.Default Alerts
ReportsThe report policy.Default Reports
RetentionThe retention policy. Required.Default Retentions
CacheThe pages of the database open without a query on the database.On
RadarRadar Engine looks for risks on the database.On
Ask ScopsScops AI answers questions about the database.On, if AI is on

To change the switches for many databases, use Policies › Monitoring.

After you add the database

WhatFirst data
Status on the Databases pageAt once
Live Activity and the activity on the DashboardWithin a minute
Alerts, size, last backup and the Objects catalogWithin about 5 minutes
Radar Engine and Health CheckWithin about 10 minutes
Insights and SQL statisticsWithin 10 to 20 minutes
Growth and trend chartsAs history grows

If Scops refuses the database

The Details tab with Environment and Group marked Required and a red 2 on the tab

Scops saves nothing and opens the first tab with a problem:

  • A required field is empty: it shows Required, and its tab shows a red number.
  • The connection test fails. Scops tests again before it saves.
  • The edition is full: see When you reach a limit.
  • The database is already registered. A standby is a different database.

Edit a database later

  1. On the Databases page, right-click the row and select Edit Database.

  2. Change the fields on any tab and click Save.

You do not have to test again. If you turn on the pack switch, Scops checks the pack grants.

Updated November 10, 2026