1. Installation and Administration Guide
  2. Troubleshoot the Plug-In
  3. Metric Collection Errors

Metric Collection Errors

Some common configuration problems manifest as Metric Collection Errors. In some cases, these error messages contain an "Internal Error" followed by a longer Java Exception.

The Support Center uses the Java Exception (if the problem is complex). The following table lists Common Metric Collection problems.

Table 3-2 Common Metric Collection Errors

Metric Collection Error Problem/Solution

No java security providers configured on Management Agent: TLS_RSA_WITH_AES_256_CBC_SHA

Problem: The plugin cannot use AES256, which is required to communicate with OKM.

Possible causes: The java used by the Enterprise Manager Management Agent has not been configured to use AES256.

Solution: Follow the instructions in "Enable Java Unlimited Cryptographic Strengths".

1000 Access denied

Problem: The credentials being used to monitor the system are being rejected by the KMA.

Possible causes:

  • The OKM User may not have an Operator role associated with it, or maybe be Disabled.

  • The certificate files associated with the Monitoring Credentials may be missing or inaccessible to the Management Agent system, or maybe be incorrect or corrupt.

Solution:

  1. Verify the User is configured correctly on the KMA.

  2. Follow the instructions in "Configure the OKM Appliance".