Page History

...

In order to monitor Oracle, Precise needs to install an agent on the monitored instance. The Precise for Oracle agent reads the Oracle SGA directly. To do so, the Precise user must be in the same group as the Oracle user to have access to the Oracle shared memory. 

When installing a new Oracle agent on Windows with Oracle 12c and later, where:

• the listener is already installed, and
• the Oracle server is running using Oracle home user who is a standard Windows user and not part of the Admin group:

1. Allow full access to the Oracle home user on the Precise root directory on the monitored machine (the machine where you are attempting to install the Oracle agent or where the Oracle instance is running)
2. Add the Oracle home user to the performance monitoring group 

UNIX

For UNIX servers:

1. Create a Precise user on every monitored server.
2. Add the Precise user to the same group as the Oracle software owner (e.g. dba or oinstall). Your DBA group should be the primary group of the Precise user.

...

• The user on the server from where you are running the Sybase collector must have admin rights on both the local host and to the server where the Sybase instance is running. The password is also required for the installation.
• Make sure you have access to an existing Sybase user name with the system administrator privileges.

• Check that the Open Client and related ODBC version is one of the following:

  Open Client	ODBC Version
  12.5.1 ESD #2	Sybase Adaptive Server Enterprise ODBC driver 4.20.00.67
  12.5.1 ESD #15	Adaptive Server Enterprise 12.05.01.529
  15.x	Adaptive Server Enterprise 15.00.00.152

• Make sure that the user used to monitor the Sybase instance is a member of the mon_role and sa_role server roles.
• Check that the mon and master tables are activated.
• Run the sp_sysmon system stored procedure with the noclear option. For example, sp_sysmon 00:01:00, noclear

• To enable monitoring of the Sybase app tier, adjust the Adaptive Server Enterprise (ASE) configuration parameters as specified in the following table:

  Parameter	Value
  max SQL text monitored	16384
  enable monitoring	1
  SQL batch capture	1
  wait event timing	1
  SQL text pipe active	0
  plain text pipe active	0
  statement pipe active	0
  errorlog pipe active	0
  deadlock pipe active	0
  process wait events	0
  object lockwait timing	0
  statement statistics active	0
  per object statistics active	0

  Info
  The value given for the event buffer per engine parameter in the table is a minimum value. You may also use a higher value, if required.

...