SergioMorales

CA Tuesday Tip: Working with the APM database - reminders

Discussion created by SergioMorales Employee on Jun 21, 2011
Latest reply on Feb 8, 2013 by JavierPM
CA Wily Tuesday Tip by Sergio Morales for 06/21/2011

Hi All,

Here is a list of some recommendations and common issues reported to support, some of these issues are not documented in any userguide

1. About running Introscope v9.x without APM db.

If you decide to run the EM without an APM database temporarily, note that when the EM starts, it will write connection failure messages in EM log every 5 seconds as shown below, filling the EM log quickly.

[WARN] [pool-3-thread-1] [Manager.com.timestock.tess.framework.util.DbExecutorService] Db is not reachable, will continue checking Connections could not be acquired from the underlying database

To disable the above message, add the following entry in IntroscopeEnterpriseManager.properties file under log4j configuration section:

log4j.logger.Manager.com.timestock.tess.framework.util.DbExecutorService=ERROR, console, logfile

Please remember that running the EM without an APM db is not supported.


2. Recommendations about having a single apm db instance to host multiple APM db/schemas.

This is technically possible and a customer can attempt this, but again this has not been certified or load tested.
There could be significant performance impact. If you try this, you should provision the DB box with the sum of the DB machine resources needed for each APM instance, as described in the sizing guide. We do recommend against this if you are using full APM with TIM monitoring, because each DB instance should be configured to use separate disks for transaction logs versus data, etc.

3. About APM database supportability:

Version 8.3.7 & 8.4


Operating System
Platform 32-bit / 64-bit

RedHat 4.8

32-bit / 64-bit

RedHat 5.4

32-bit / 64-bit

Solaris 10

32-bit / 64-bit




Version 8.3.10 & 8.4


Operating System
Platform 32-bit / 64-bit

Win2003

32-bit / 64-bit

Win2008

32-bit / 64-bit




Oracle Enterprise Edition (with partitioning option)


Version
Platform 32-bit / 64-bit

10gR1

32-bit / 64-bit

10gR2

32-bit / 64-bit

11gR1

32-bit / 64-bit

11gR2

32-bit / 64-bit


4. APM database in Postgres

When installing the APM Database on PostgreSQL, specify the installation path and directory using ASCII characters only.

Windows:
Users must have admin privileges on the machine to complete the DB installation.

Linux
- In the past, if you were installing the APM database on Linux, you needed to run the installer as the root user. This restriction has disappeared since v9.0.6.0, you can now install the APM db with a root or non-root user account
- maximum shared memory configuration is needed, configure in /etc/sysctl.conf file similar as kernel.shmmax = 6693928832

Solaris:
- Support for PosgreSQL on Solaris is available since 9.0.5. You need to run the installer as the root user
- Starting from v9.0.6, you can now install with a root or non-root user account
- If the APM database schema is not created correctly, you should check the memory and disk available on the server where you are running the installer. If you have sufficient memory and disk, check that the PostgreSQL database instance is installed and running by looking at the "postgres" process running in the background and reviewing the logs available under /tmp/install-postgresql.log and the POSTGRES_HOME/data/pg_log/ directory. If the postgres instance is running successfully, re-run the installer and select the option to connect to the existing database instance, then choose the option to install a new database schema.
- maximum shared memory configuration is needed:
when installing as root, configure in /etc/system set shmsys:shminfo_shmmax=6693928832
when installing as non-root, you have to run this command
projadd -U postgres -K "project.max-shm-memory=(priv,7000MB,deny)" user.postgres
- If you are using Solaris 10 in zone, you might need to update the /etc/project file as below:
Set max-shm-memory for root user, example showing below:
user.root:1::::project.max-shm-memory=(privileged,6693928832,deny)
Add postgres user, example showing below:
projadd -U postgres -K "project.max-shm-memory=(priv,7000MB,deny)" user.postgres
Rerun install.
If you still have the problem, try create the '/etc/system' file by adding the following:
set shmsys:shminfo_shmmax=6693928832
Rerun the install

5. APM database in Oracle

- Support for 10g (r1,r2) and 11g (r1,r2) Enterprise Editions on all platforms is available since 9.0.5

-APM only creates schema for Oracle.
Prerequisites: Oracle installation and database creation.
You are given the option to install an APM database schema onto an existing Oracle database instance via a set of command-line scripts or using the Enterprise Manager installer - see attached "How to create a new user using Oracle EM UI and create the APM db.doc" that explains step by step how to do that.

- APM DB user needs to be set with the following:
Roles : Connect, Resource
System privileges : Analyze , Unlimited Tablespace, Create view
Quota : Unlimited on users

NOTE: "Create Any View" and "Analyze Any" roles are not mandatory as mentioned in the installation guide.
"Create View" and "Analyze" (basically privilege to call dbms_stats.gather_table_stats procedure) are sufficient as we only operate these within our schema.

- You can use your own Oracle "custom roles" but you should make sure to include the below privileges required for the APM user.
CREATE SEQUENCE
CREATE TYPE
CREATE PROCEDURE
CREATE TABLE
CREATE SESSION

-Tools for manual schema creation and deletion are under <em_home>\install\database-scripts\windows (or Unix). For example:
CreateSchema -databaseName <database_name> -databaseType <database_type> -host <host_name> -port <port_number> -releaseVersion <version> -scriptsDir <directory> -user <user_name> -password <password>
dbDrop -databaseName <database_name> -databaseType <database_type> -host <hostname> -port <port_number> -releaseVersion <version> -scriptsDir <dir> -user <user_name> -password <password>

- Logging is controlled by <em_home>\install\common\config\log4j-dbtools.properties

- Performance considerations:
a.Separate data, index and temp onto separate drives. Redo logs can be with temp and should be set ~1GB. ASM (Oracle’s Automatic storage management) can also be considered.
b.Enable Automatic memory management.
For more details, please refer to sizing guide for APM performance recommendations

If you have still have issues installting/configuring the APM database, you should contact support and provide the following information:

-EM_HOME/install/*.log
-POSTGRES_HOME/data/pg_log/.*
-/tmp/install-postgresql.log
-Exact Introscope, Oracle if applicable and OS versions.

Regards,

Sergio

Outcomes