Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Database Performance Analyzer (DPA) > DPA - Knowledgebase Articles > Register an Oracle standby database for monitoring

Register an Oracle standby database for monitoring

Table of contents
No headers
Created by Interspire Import, last modified by Mandeville on Dec 02, 2016

Views: 1,392 Votes: 0 Revisions: 12

You can start an Oracle standby database in read-only mode to run reports and perform other activities against it. You can monitor the read-only database with DPA, however there is a special registration process. Standard registration fails when the database is read-only.


You must register another Oracle database that is not read-only, and then repoint DPA to the read-only database.


  1. Click Options > Register for Monitoring. Register a separate Oracle database in the Register Instance Wizard.
  2. On the home screen, click Action > Stop Monitor next to the new database.
  3. Click Options > Update Connection Info
  4. Select the newly registered database, and click Next.
  5. Enter the connection and user information of the read-only Oracle database, and complete the wizard.
    • If you registered the production database tied to this standby, the DPA monitoring user should exist.
  6. Log in to the DPA repository database with a SQL statement execution tool.
  7. Find the ID for the newly registered database by running this SQL statement:
    select id, name from cond order by name;  -- remember the ID value for the new database
  8. Modify the name by running a SQL statement like this:
    update cond set name = '&NewName' where id = &IDFromPreviousQuery;
  9. On the home screen, click Action > Start Monitor next to the standby database.


NOTE: This will work as long as the objects currently exist for the monitoring user (likely because the primary was registered and objects replicated). Check out the objects and permissions here.

Last modified