Error Types within the ControlCenterEventLog Table - syncsort_capacity_management - Latest

Syncsort™ Capacity Management Guide
Product type
Software
Portfolio
Integrate
Product family
Syncsort™ Software
Product
Syncsort™ Capacity Management
Version
Latest
Language
English
Product name
Syncsort™ Capacity Management
Title
Syncsort™ Capacity Management Guide
Copyright
2024
First publish date
1985
Last edition
2024-08-06
Last publish date
2024-08-06T15:42:28.602035

Error Type

Description/Cause

Data needed by Support

FileReadError

Issues reading any captured files.

  1. Diagnostics extract

  2. A sequence of 20 – 30 ‘r’ files from the target (including first file or PerfText for Windows) covering at least one interval that raises the error.

  3. Confirm Virus scans, Indexing and Backups are turned off/excluded for the Syncsort™ Capacity Management …\work directory and subdirectories and the …\Logs directory

  4. For a UNIX box we would also need:

  • any mail messages for the ‘metron’ user on the Target

  • the most recent AMconfg

  • the AcqSetup.log

 

WindowsDataError

Issues processing Windows data files.

  1. Diagnostics extract

  2. A sequence of 20 – 30 ‘r’ files from the target (including first file or PerfText for Windows) covering at least one interval that raises the error.

 

AlreadyInserted

Issues inserting data for a particular time period that Control Center thinks has already been processed.

  1. Diagnostics extract

  2. A sequence of 20 – 30 ‘r’ files from the target (including first file or PerfText for Windows) covering at least one interval that raises the error.

 

NoMatchingTem­plate

Control Center is unable match the for­mat of data in a specific file to one of those defined in the templates.

  1. Diagnostics extract

  2. A sequence of 20 – 30 ‘r’ files from the target (including first file or PerfText for Windows) covering at least one interval that raises the error.

  3. The same files from the ..\Badfiles directory on the Control Centre server.

  4. For a UNIX Machine:

  • any mail messages for the ‘metron’ user on the Target

  • the most recent APMconfg file

  • the AcqSetup.log

 

ParseError

Issues reading the raw data files. Parsing errors generally mean that the data in the file is not of the format expected in the Control Center templates.

  1. Diagnostics extract

  2. A sequence of 20 – 30 ‘r’ files from the target (including first file or PerfText for Windows) covering at least one interval that raises the error.

  3. The same files from the ..\Badfiles directory on the Control Centre server.

  4. For a UNIX Machine:

  • any mail messages for the ‘metron’ user on the Target

  • the most recent APMconfg file

  • the AcqSetup.log from the $HOME directory

 

MissingFileOrSec­tion

Issues reading the raw data files. These errors occur if there are whole sections missing from a raw data file or whole files missing from a capture interval.

  1. Diagnostics extract

  2. A sequence of 20 – 30 ‘r’ files from the target (including first file or PerfText for Windows) covering at least one interval that raises the error.

 

TemplateError

Failure to load Control Center Templates usually due to incorrect matching of Control Center to template versions. This stops the Control Center service.

  1. Diagnostics extract

 

PDBUpdateError

Issues inserting data into the database. Errors can occur in the following areas:

  • Errors decompressing data files.

  • Errors parsing Windows and VMWare data files.

  • Deleting previous interval file once the update has completed.

  • Moving files to Bad files once the update has completed.

  • SQL Server connection issues.

  • Failure to insert data into the database due to invalid values.

  1. Diagnostics extract

  2. A sequence of 20 – 30 ‘r’ files from the target (including first file or PerfText for Windows) covering at least one interval that has failed

  3. One of the following depending on the type of error:

  • File moving and deleting errors: a ProcMon trace.

  • SQL Server errors: SQL Profiler Trace covering one or more times when the error is occurring and a sequence of data that was processed during the profile trace capture period.

 

RowInsertionError

Issues inserting specific data records into a database table.

  1. Diagnostics extract

  2. A sequence of 20 – 30 ‘r’ files from the target (including first file or PerfText for Windows) covering at least one interval that raises the error.

 

OverlappingPeriods

Measurement periods are overlapping unexpectedly.

  1. Diagnostics extract

  2. A sequence of 20 – 30 ‘r’ files from the target (including first file or PerfText for Windows) covering the current and previous measurement period.

  3. Ideally the diagnostics need to include the sample data for the target with a time range that includes the period that the data is overlapping with.

 

ValidationError

Intervals are being processed in the wrong order.

  1. Diagnostics extract

  2. A sequence of 20 – 30 ‘r’ files from the target (including first file or PerfText for Windows) covering the current and previous end date times specified in the error message.

  3. Also the diagnostics should include the sample data that the inserts are overlapping with.

 

StartNewPeriod

A new measurement period has been started. This is generally not an issue as it just shows there was an interruption in the data capture or a change in interval length.

  1. However, if this occurs without either of these conditions being seen then we would need:

  2. Diagnostics extract

  3. A sequence of 20 – 30 ‘r’ files from the target (including first file or PerfText for Windows) that includes intervals before and after the error occurred.

 

InvalidDecryption

This error occurs when Control Center has issues decrypting the passwords stored in the database. (This is very unlikely to occur unless s_Connec­tion.AuthValue has been tampered with outside of Syncsort™ Capacity Management.)

  1. Re-run Bulk Targets to repopulate the target tables.

 

FileCollection

These errors occur when Control Center is collecting files. Errors occur in the following areas:

  • Failure to collect files from the remote locations.

  • Failure to write collected files to the work area.

  • Failure to create a capture pro­file and write it to the ‘Out’ directory.

  1. Diagnostics extract.

  2. Results of testing the connection outside of Syncsort Capacity Management but using the same credentials (logged on user) as Syncsort™ Capacity Management

  3. Troubleshooting Control Center Capture and Collection provides flowcharts of the UNIX and Windows data processing that allows you to diagnose these issues.

Housekeeping

Control Center is unable to carry out its housekeeping jobs. Errors can occur in the following areas:

  • Failure to delete bad files.

  • Deleting old log files.

  • Errors reading configuration data.

  • Renaming directories in the Syncsort™ Capacity Management Work directory

  • Errors reading Auto Update Acquires from the database.

  1. Diagnostics extract.

  2. Confirm Virus scans, Indexing and Backups are turned off/excluded for the Syncsort™ Capacity Management …\work directory and subdirectories and the …\Logs directory

 

CaptureProfile

These errors occur when Control Center is sending out capture profiles. Errors occur for the following reasons:

  • Failure to send a capture profile

  • Error deleting the ‘Out’ directory after the capture profile has been sent

  • Often if there are issues no errors are raised it just doesn’t work, if it does they are mostly the same as collection.

  1. Diagnostics extract.

  2. Check the Syncsort™ Capacity Management User has Write as well as Read permissions on the remote target directory or share.

 

CaptureError

VMWare Only: Error messages found within the VMWare data capture file (data processing of this file stops and it is moved to Bad Files).

  1. Check ‘sdk’ in URL is lower case and account has VMware permissions.

  2. Switch VMware tracing on. (Note this will enable tracing for ALL VMWare targets sharing the same profile).

  3. Send us trace logs.

 

CaptureWarning

VMWare Only: Warning messages found within the VMWare data capture file (data processing of this file continues).

  1. Switch VMware tracing on and send us trace logs. (NOTE: this will enable tracing for ALL VMWare targets sharing the same profile).

  2. Send us trace logs.

 

CriticalMonitorError

Critical Service Monitor only: These errors occur when critical service monitor profiles are not defined correctly or not associated with the appropriate tar­get.

  1. Diagnostics extract.

 

ZerozOSCfgCP­Count

z/OS only: This error only occurs for z/OS data when there is a zero value for an essential metric.

  1. z/OS raw data files

 

NullVMwareCpu­Count

VMWare Only: This errors when there is no CPU Count available within the VMWare data files.

  1. VMWare data files

 

WebApiError

Concentrator and Control Center Web API Only: