Unspecified error=0D=0A when running Oracle Data Collection in CCS

Products

• Control Compliance Suite Standards Server
• Control Compliance Suite
• Control Compliance Suite Databases Oracle
• Control Compliance Suite Standards Module

Issue/Introduction

Control Compliance Suite (CCS)

When running a data collection or CER job for Oracle on an Agent-based asset results in the following error:

Unspecified error=0D=0A error message.

Environment

CCS 12.6.1 - 12.8

Cause

This is a general error and can by caused by a number of things. 

In this case, the reason for the Unspecified error is that the local database credential does not exist.

Can also be caused by the agent being offline/unavailable. The oracle listener is not running.

Or other unknown reasons.

Resolution

Agent-based data collection:

On the CCS Agent run the 'ccsorasetup' tool to configure local credentials using either '-a' option to configure using SID, or the '-s' option to configure Service Name.

• This will create a file either "ccsora_sid_<ORACLESID>.dat" or "ccsora_service_<ORACLESERVICENAME>.dat" file in the /esm/bin/dcmodules/Linux/ORCL/ConfigFiles/ directory.
• When the Oracle asset is imported into CCS the default "Database Name Type" is "SID". If you configure using the "Service Name" then make sure you update the Oracle asset in CCS.

Depending on how the CCS Asset is configured.

As per the documentation, the Service Name should be used.

"If the Oracle Service name and the Oracle SID name are same, you can scan the agent-based asset with database name type as Service Name only.
Also, you must manually change the database name type from SID to Service Name after the agent-based asset is imported to Control Compliance Suite."

Data collection support for agent-based Oracle assets

Agent-less data collection:

Make sure that the Oracle asset has all the attributes filled out, especially the Operating System field. This will cause this error, as CCS is not able to identify the OS.
Once that is set the issue will no longer occur. 

Additional Information

Verify the following:

1. That there is only 1 agent registered, and the oracle database assets are associated with the correct agent.
2. The agent us running and the only agent registered to CCS, e.g not registered with short name and fqdn.
3. Oracle is properly running and accessible and the listener is running and knows about the db in question.
4. Make sure the "ccsora_sid_<OracleDB>.dat" file(s) OR "ccsora_service_<OracleDB>.dat" but NOT both, exist in /esm/bin/dcmodules/Linux/ORCL/ConfigFiles.
   If you are not sure which one was the last to be configured, remove them both and reconfigure via the ccsorasetup utility.
5. Verify that the "Configure Platform Settings" in Deployment View in the Oracle page under "Credential Management Settings" are enabled.