If you encounter issues while installing the sensor, follow the steps outlined in the following sections. For example, if you have installed a sensor and No sensors detected is displayed when you log on to the Database Security console, follow the steps outlined in these sections.
Verify that the Database Security sensor process is up and running
Check if the Database Security sensor process is up and running:
On Linux or Solaris, run:
/etc/init.d/mfe-dbs-sensor statusOn AIX, run:
/etc/rc.d/init.d/mfe-dbs-sensor statusOn HP-UX, run:
/sbin/init.d/mfe-dbs-sensor statusOn Windows, run:
services.mscand look for the service Trellix-DBS-Sensor
If the sensor service is down and does not come up after you start it, check the validity of Database Security server license. If the sensor was connected to the server before applying the license, you need to manually restart the sensor.
If you still can't run the Database Security sensor, Run the diagnostic tool and also contact Customer Success.
If the sensor does not appear on the Sensor list:
Verify that the server IP address and port are set correctly in the Database Security sensor's configuration file.
Platform
File path
Linux
/etc/sysconfig/mfe-dbs-sensorSolaris
/etc/default/mfe-dbs-sensorAIX
/etc/mfe-dbs-sensorHP-UX
/etc/rc.config.d/mfe-dbs-sensorWindows
C:\Program Files\McAfee\Trellix-DBS-SensorVerify that the sensor can reach the server port, using ping <server ip> and telnet <server ip> <port number> services.
If it is not reachable, verify that there is no firewall blocking the communication (check that Database Security sensor communication port is open for TCP). If the port is blocked, reconfigure the port to allow TCP communications on that port and restart the Database Security sensor service.
If the Database Security server IP address and port are reachable from the Database Security sensor computer and you still do not see the sensor on the sensors list on the Database Security server, Run the diagnostic tool, and also contact Customer Success for assistance.
If the DBMS appears on the Sensors list, but is listed as disconnected:
Verify database versions, for more information see Database Security sensor requirements.
If the Database Security sensor still can't monitor your DBMS, Run the diagnostic tool, and also contact Customer Success.
If no Oracle DBMS is displayed for your Database Security sensor:
For Windows platform, Run the diagnostic tool and also contact Customer Success for assistance.
For non-Windows platform, verify that:
You have group read and execute permissions on
$ORACLE_HOMEand$ORACLE_HOME/dbs, and group read permissions on$ORACLE_HOME/dbs/sp*.oraand$ORACLE_HOME/dbs/init*.ora.Your ORACLE_HOME group is either dba or oinstall. If not, add the relevant Oracle group to the OS user.
Your oratab file (under
/etc/oratabor/var/opt/oracle/oratab) points to the correct ORACLE SID and ORACLE_HOME (entries in the file are in this format:$ORACLE_SID:$ORACLE_HOME:<N|Y>:). If the entries are incorrect, update the values as required and restart the Database Security sensor service. Otherwise, contact Customer Success after you Run the diagnostic tool.If your oratab file is located at a different path to the default, you can configure Database Security sensor by editing the startup script to add
-r <oratab full path>/oratabto the start functionPlatform
Startup script
AIX
/etc/rc.d/init.d/mfe-dbs-sensorHP-UX
/sbin/init.d/mfe-dbs-sensorLinux
/etc/init.d/mfe-dbs-sensorSolaris
/etc/init.d/mfe-dbs-sensorAfter editing the startup script, run the Database Security sensor.
If the DBMS on the sensor appears as disconnected:
To verify the supported database versions, see Database Security sensor requirements.
If you are running an Oracle database on a non-Windows Platform, verify that:
You have group read and execute permissions on $ORACLE_HOME, $ORACLE_HOME/dbs and group read permissions on $ORACLE_HOME/dbs/sp*.ora and $ORACLE_HOME/dbs/init*.ora.
Your ORACLE_HOME group is either dba or oinstall. If not, add the relevant Oracle group to the mfedbs OS user.
If the Database Security sensor still can’t monitor your DBMSs, Run the diagnostic tool, and also contact Customer Success for assistance.