You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/auto-discovery/database-discovery/index.mdx
+6-10Lines changed: 6 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -266,11 +266,7 @@ Device42 supports autodiscovery on Windows and \*nix platforms for the following
266
266
267
267
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.
268
268
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
274
270
275
271
For discovery to return detailed info about your database instance, you will require read or view permissions for the following system views and tables:
276
272
@@ -290,21 +286,21 @@ To get information about pluggable databases (PDBs) within an Oracle container d
290
286
291
287
#### System-Level Permissions
292
288
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:
Another example is the `lsnrctl status` command, which checks the status of the Oracle listener:
300
298
301
299
```bash
302
300
oracle -c 'lsnrctl status'
303
301
```
304
302
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:
0 commit comments