grid control

Errors in alert log [NI cryptographic checksum mismatch] TNS-12599

Using rdbms 11.2 as the repository for our Grid Control environmont, noticed a lot of the same errors in the alert file of the repository or/and the target database:

NI cryptographic checksum mismatch error: 12599.
VERSION INFORMATION:
TNS for Linux: Version 11.2.0.2.0 – Production
Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.2.0 – Production
TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.2.0 – Production
Time: 24-MAR-2011 11:58:31
Tracing not turned on.
Tns error struct:
ns main err code: 12599

TNS-12599: TNS:cryptographic checksum mismatch
ns secondary err code: 2526
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0

Note: 1150874.1 gives the cause, workaround and solution:

By |May 25th, 2011|Categories: Database, grid control||0 Comments

Grid Control: number of active connections is….

Just for my collection of Grid Control messages, bugs and what so ever – for my effort (between my normal business) to get the ‘pie’ completely green and as few ‘critical’ errors as possible, which is sometimes a very depressive task:

After installing and configuring application server, the agent on that server started to sent messages like ‘The number of active connections is ..’  and a high number, too high for the metric.  But.. there are no connections yet on the system (as far as I know)!  Grid Control (OMS + agent) = 10.2.05, application server 10.1.2.0.2

Bug: 5717633 / 4458130. Note: 330819.1 —> EM/GRID CONTROL FALSELY REPORT ACTIVE HTTP CONNECTIONS WHEN KEEPALIVE=ON.

Solution:

1. “Change the value of the parameter KeepAlive to ‘Off’ in httpd.conf” —>  (nice! and what if this is not to be recommended for the application..).
2. “Restart all components using opmnctl stopall and then opmnctl startall” —> I tried to just stop and start the http-server and the agent, but that didn’t work.
3. “Check the current value of the active connections metric using the metric browser.” —>

What the heck is a metric browser, and how to use this…

Just try it out:

a. vi <AGENT_HOME>/sysman/config/emd.properties  (make a backup in advance..)

b. uncomment the following line:

#enableMetricBrowser=true

c. reload the agent through:

<AGENT_HOME>/bin/emctl reload agent

d. check the metric browser:

http|https://<agent_hostname>:<agent_port>/emd/browser/main

Example:

http://myServer.myDomain:3872/emd/browser/main

By |September 23rd, 2009|Categories: grid control|Tags: |2 Comments

VM-time out of sync, runs too fast with guest-O.S. Suse Linux 9 / 10

Grid Control is calling  >> “Difference between OMS system time and Agent system time is 121 mins and has exceeded the critical threshold 120 mins”

The system time runs too fast on a (Suse) Linux-based (kernel 2.6) virtual machine, while the ntp has been configured. There are a lot of documents regarding this kind of issues. For explanation and understanding a few documents we used:
http://www.vmware.com/pdf/vmware_timekeeping.pdf
http://support.microsoft.com/kb/918461 (Microsoft? seems to work for VM-ware too…)
http://www.novell.com/coolsolutions/feature/15345.html (time not syncing with ntp-server)

Next option for me when all above should not be working, but didn’t have to use it:
http://ict-freak.nl/2007/01/10/how-to-setup-ntp-on-vmware-esx-server/

Solution we implemented, seemed to work:
– add the clock=pit parameter to the kernel entry (for explanation, see below)
– in addition add the option ‘burst iburst‘ to the ntp-configuration.

To see by the way how the ntp is working:
# watch ntpq -p

Clock=pit for the GRUB bootloader
In the guest operating system, open the /boot/grub/menu.lst file by using a text editor such as Vi. For example, type the following command from a console, and then press ENTER:
vi /boot/grub/menu.lst
This file contains the Linux boot options and resembles the following:
title Linux
kernel (hd0,4)/vmlinuz root=/dev/hda7 vga=791
initrd (hd0,4)/initrd
title windows
etc.
In the title Linux area of this file, add the clock=pit parameter to the kernel entry. This area should resemble the following:
title Linux
kernel (hd0,4)/vmlinuz root=/dev/hda7 vga=791 clock=pit
initrd (hd0,4)/initrd
Save the changes to the file, exit Vi, and then restart the Linux-based virtual machine.

By |September 9th, 2009|Categories: grid control|Tags: , |0 Comments

Discoverer shows down in Grid Control while up.

Short one this time, all in favour of getting my green ‘pie’ in Grid Control management server.

Grid Control: 10.2.0.5. Discoverer: 10.1.2.x
In Grid Control, after upgrade to 10.2.0.5, a Discoverer target shows down in the list, while it’s functioning quite well.

It seemed an old bug (Grid Ctrl 10.1.04) is still not fixed:
– Bug 4474849 / 3897834 ‘DISCOVERER INSTANCES ALWAYS SHOW DOWN’
– Note: 332363.1

Solution:

1- Remove the Application Server target which owns the Discoverer component (10.1.2) in the Grid Control

2- Stop the agent

3- Backup the file %CENTRAL_AGENT_ORACLE_HOME%/sysman/admin/metadata/oracle_discoverer.xml file.

Replace this file by:

%BI_ORACLE_HOME%/sysman/admin/metadata/oracle_discoverer.xml file

BI_ORACLE_HOME corresponds to the Oracle_Home where Discoverer 10.1.2 is installed.

4- Restart the agent

5- Rediscover the Application Server target on the host, by typing (Agent-environment)  ‘agentca -d’.

By |September 9th, 2009|Categories: grid control|Tags: , |2 Comments

Object ODS.OID_RESPONSE_ARRAY_TYPE does not exist, Grid Control 10.2.0.5

After installing Oracle Application Server 10.2.0.2, with corresponding OID,  Grid Control 10.2.0.5 gave me the obove mentioned error, and the the item OID a ‘metric collection error’.

To fix the metric collection error downloaded and applied Patch 5686191 on top of OID product.This is a sql-script to run against the OID-repository. Unpublished bug according to note 764088.1

Shutdown the DAS:

~/media/5686191> opmnctl stopproc process-type=OC4J_SECURITY

~/media/5686191> /software/oracle/product/10.2/infra/OPatch/opatch apply

Oracle Interim Patch Installer version 1.0.0.0.52
Copyright (c) 2005 Oracle Corporation. All Rights Reserved..

We recommend you refer to the OPatch documentation under
OPatch/docs for usage reference. We also recommend using
the latest OPatch version. For the latest OPatch version
and other support related issues, please refer to document
293369.1 which is viewable from metalink.oracle.com

Oracle Home = /software/oracle/product/10.2/infra
Location of Oracle Universal Installer components = /software/oracle/product/10.2/infra/oui
Location of OraInstaller.jar  = “/software/oracle/product/10.2/infra/oui/jlib”
Oracle Universal Installer shared library = /software/oracle/product/10.2/infra/oui/lib/linux/liboraInstaller.so
Location of Oracle Inventory Pointer = /etc/oraInst.loc
Location of Oracle Inventory = /software/oracle/product/10.2/infra/inventory
Path to Java = /software/oracle/product/10.2/infra/jre/1.4.2/bin/java
Log file = /software/oracle/product/10.2/infra/.patch_storage/<patch ID>/*.log

Backing up comps.xml …

OPatch detected non-cluster Oracle Home from the inventory and will patch the local system only.

By |August 31st, 2009|Categories: grid control|Tags: , |1 Comment