Skip to content

Commit 1097f54

Browse files
authored
Merge branch '968-database' into edit-968-database
2 parents 4469870 + b5e667b commit 1097f54

File tree

1 file changed

+6
-10
lines changed
  • docs/auto-discovery/database-discovery

1 file changed

+6
-10
lines changed

docs/auto-discovery/database-discovery/index.mdx

Lines changed: 6 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -266,11 +266,7 @@ Device42 supports autodiscovery on Windows and \*nix platforms for the following
266266

267267
Device42 database autodiscovery for Windows and \*nix targets supports discovery for Oracle RAC clustered database environments, which helps users better assess their cluster databases and understand all the IT assets tied to critical business applications. Discovery returns data about the RAC configuration, the RAC database, and the nodes (physical servers) running the RAC software. You can run the autodiscovery against one or more nodes in the Oracle RAC and return information about all connected nodes. Device42 requires the use of sudo for Oracle discoveries to mitigate the risk of lockout.
268268

269-
### Minimum Permissions Requirements for Oracle Discovery
270-
271-
Oracle database discovery requires two sets of permissions: database-level permissions for querying Oracle system views and system-level permissions for executing shell commands on the target servers.
272-
273-
#### Database-Level Permissions
269+
### Minimum Database-Level Permissions Requirements for Oracle Discovery
274270

275271
For discovery to return detailed info about your database instance, you will require read or view permissions for the following system views and tables:
276272

@@ -290,21 +286,21 @@ To get information about pluggable databases (PDBs) within an Oracle container d
290286

291287
#### System-Level Permissions
292288

293-
You need system-level access to execute shell commands on the target servers. Device42 requires `sudo` access to run various commands related to Oracle configuration and status information, for example:
289+
In addition to the minimum DB-level permissions above, discovery also needs shell access to the target system to run OS-level commands to get information about the Oracle environment.
290+
291+
For example, shell access is needed to read the `tnsames.ora` file, which contains network connection details:
294292

295293
```bash
296294
/usr/bin/cat: /dbprog/oracle/product/19.3.0.0.26/network/admin/tnsnames.ora
297295
```
298296

299-
or:
297+
Another example is the `lsnrctl status` command, which checks the status of the Oracle listener:
300298

301299
```bash
302300
oracle -c 'lsnrctl status'
303301
```
304302

305-
**Sample `sudoers` Configuration:**
306-
307-
Add the following entries to your `/etc/sudoers` file or create a separate `sudoers` file for Device42 Oracle discovery:
303+
To allow Device42 to run these commands securely, you can grant limited `sudo` access by adding the following to the `/etc/sudoers` file or by creating a separate `sudoers` file for Device42 Oracle discovery:
308304

309305
<details>
310306
<summary>Click to expand the code block</summary>

0 commit comments

Comments
 (0)