If you encounter problems while installing the sensor, for example, if you have installed a sensor and No sensors detected is displayed when you log in to the web console, follow the steps outlined.
Check if the Database Security sensor process is up and running:
On Linux , run:
/etc/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 run it, check that the Database Security server has a valid license. If the sensor was connected to the server before applying the license, you need to manually restart the sensor.
If you are still unable to run the Database Security sensor, contact support after running the diagnostic tool.
If the Database Security sensor is not on the Database Security server sensors' list:
Verify that the server IP address and port are set correctly in the Database Security sensor's configuration file (located in Linux:
/etc/sysconfig/mfe-dbs-sensor; and on Windows, run TrellixDBSConfig.exe). If they are not set correctly, update the configuration file and restart the Database Security sensor service.Verify that the sensor can reach the server port, using ping <server ip> and telnet <server ip> <port number>.
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 it is blocked, enable 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, then contact support for assistance.
If you are still unable to reach the Database Security server from the Database Security sensor server, contact your system administrator for support.
If no DBMSs are displayed for your Database Security sensor:
On Windows platforms, run the diagnostic tool and then contact support for assistance.
On non-Windows platforms, 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 Trellix 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, fix them and restart the Database Security sensor service. Otherwise, contact Support after running the diagnostic tool.If your oratab file is in a different location, you can configure the sensor by editing the startup script accordingly (on Linux :
/etc/init.d/mfe-dbs-sensor; on by adding"-r <oratab full path>/oratab"to the start function.After editing the startup script, run the Database Security sensor.
If the DBMS appears on the Sensors list, but is listed as disconnected:
Verify that Oracle is version 8.1.7 or later, or MS SQL Server 2000 or later, or Sybase ASE 12.5. If you are trying to monitor another DBMS version, verify with support that the version is already supported.
If the Database Security sensor is still unable to monitor your DBMSs, run the diagnostic tool, then contact support.