Skip to content

Oracle Database

Integrate Oracle Database with vScope to gain insights into database structures, users, and privileges. Ensure the database user has the required privileges, and configure the correct Connect Descriptor for seamless integration.


Required Privileges for Oracle Database Integration

To allow vScope to scan your Oracle Database, assign the following roles and privileges:

  • Role: SELECT_CATALOG_ROLE

    • Purpose: Allows read access to database structures, users, and privileges.
    • Command:
      ALTER USER "USERNAME" DEFAULT ROLE "SELECT_CATALOG_ROLE";
  • System Privilege: CREATE SESSION

    • Purpose: Enables session creation to access the database.
    • Command:
      GRANT CREATE SESSION TO "USERNAME";

Replace "USERNAME" with the actual username.


Configuring the Connect Descriptor

To connect vScope to Oracle DB, specify the correct Instance Name or Service Name in the Connect Descriptor. If unsure of the instance name, follow the methods below.

Finding the Oracle DB Connect Descriptor

Solution 1 – Try Common Instance Names

Start by trying these standard instance names:

  • XE (Oracle Express Edition)
  • ORCL (Oracle default SID)
  • IASDB (Oracle Application Server 9i Rel. 2 – 10g)
  • SA (SAP)

Solution 2 – Use lsnrctl to Check Instance Names on Your Oracle DB Server

Run the command lsnrctl status in your terminal (works on Unix, Linux, and Windows) to list listeners and associated SIDs.

Example Output:

C:>lsnrctl status Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC_FOR_XE))) STATUS of the LISTENER
Alias LISTENER Version TNSLSNR for 32-bit Windows: Version 10.2.0.1.0 - Production Start Date 13-JUN-2009 12:04:14 ... Services Summary... Service "CLRExtProc" has 1 instance(s). Instance "CLRExtProc", status UNKNOWN, has 1 handler(s) for this service... Service "XE_XPT" has 1 instance(s). Instance "xe", status READY, has 1 handler(s) for this service... Service "xe" has 1 instance(s). Instance "xe", status READY, has 1 handler(s) for this service...

In this example, available instance names include XE_XPT and XE.

Solution 3 – Query the Database for the Instance Name

If you have database access, use the following query to retrieve instance names:

SELECT SYS_CONTEXT('USERENV', 'SID') FROM DUAL;

Following these steps will help you configure the correct Connect Descriptor and enable full Oracle DB discovery with vScope.