Configuring the collation.properties file entries

This topic lists the collation.properties file entries that the sensor uses.

com.collation.discovery.oracle.extended
This property specifies whether additional configuration values about Oracle database links are stored.

The default value is N (No).

If you set the property to Y (Yes), the sensor stores additional configuration values about Oracle database links.

com.collation.platform.os.ignoreLoopbackProcesses=true
The default value is true, which means that the processes that are listening on loopback interfaces are ignored. Therefore, if a server is listening only on the loopback IP address (127.0.0.1), and not on any other externally available IP address, that server will not be discovered.

This property controls the discovery of external IP addresses.

If the value of this property is set to false, all processes with listening ports are considered for discovery.

You must set this property to true if you want to discover an Oracle Application Server or the WebLogic sensors. For example, if the WeblogicServerVersionSensor sensor tries to start using a local host address, this property must be set to true.

com.collation.discovery.oracle.tablelimit
This property controls the quantity of tables that are discovered by Oracle sensor.

The default value is 1000. The property supports only positive values.

com.collation.oracle.sensor.ignoreNonRegisteredSidOfListener=true
The default value of this property is false.
If this property is set to true, the Oracle Sensor will ignore those SIDs which are found to be not registered on Oracle listener.

Oracle Sensor first tries to establish a jdbc connection with the listener for a SID. If it gets an error "ORA-12505, TNS: listener does not currently know of SID given in connect descriptor", the SID is ignored. If the connection is unsuccessful with any other error, a shallow Oracle Instance Model Object is created with this listener's IP and Port details.

Another impact to this property is that, it will not create those Oracle instances which have not registered with any listener.

Note: In Fix Pack 6, this property is replaced by com.collation.oracle.sensor.CreateOnlyConfirmedRegisteredSid=true
com.collation.oracle.sensor.CreateOnlyConfirmedRegisteredSid=true
The default value of this property is true. For true value:
  • Oracle Sensor will only create Oracle Instances for SIDs for which Jdbc connection is success on the listener. Success of jdbc connection act as a confirmation that the SID is registered on the current listener for which the sensor is invoked. The model object will be created with this listener’s IP or Port details
  • It will also create shallow Oracle Instance for SIDs where we get this error "ORA-01017: invalid username/password; logon denied". This is because jdbc driver throws this error after it had checked that SID is registered with listener
If the value set to false:
  • Sensor will create shallow Oracle Instance for SID even if sensor is not able to establish Jdbc connection to the SID on this listener for which sensor has invoked. This means that if the target system has only single listener and all SID are registered on it, but jdbc connection is failed because of any reason, then shallow Oracle Instances will get created with the listener’s IP or Port details. But if the target has multiple Listeners and each listener is listening on different virtual IP or Port, then Oracle Instances may get created with any random Port even if its listener is not listening on that port or Virtual IP
Note: This property setting will be ignored in case “Light level Oracle discovery” is enabled. This property can be scoped to level of a particular IP address eg, com.collation.oracle.sensor.CreateOnlyConfirmedRegisteredSid.1.2.3.4=false.

The above configuration will be applicable to only selective IP ,e.g. 1.2.3.4

com.collation.oracle.sensor.cmd.prefix
This is an optional property and is used to specify a text that will be prefixed with the Oracle commands executed by this sensor.
Some of the Oracle commands executed by this sensor are: srvctl config scan, crs_stat -v etc
This property can also be specified as per OS and targets.
In the following example, before actual execution of the command, specified Oracle user profile will be sourced to set up the requisite environment variables.
com.collation.oracle.sensor.cmd.prefix.linux.<context_ip> =. /app/grid/home/.profile
com.collation.oracle.sensor.cmd.prefix.linux=. /app/grid/home/.profile
com.collation.oracle.sensor.cmd.prefix=. /app/grid/home/.profile
com.collation.discover.agent.OracleAgent.pdb.seed=true
The default value of this property is true. If this property is set to true, the Oracle Sensor will discover details of the PDB seeds. If the value is set to false, then for performance optimization, Oracle Sensor will discover seed PDBs but will skip its details like DBVersion, TableSpaces, Schemas, PDBHistory and DBLinks.
com.collation.discover.agent.OracleAgent.pdb.maxPoolSize=10
The default value of this property is 10. This is an optional property and set the maximum size of thread pool for parallel processing of PDB's in multiple threads.