Symptom
- ABAP short dump occurs every time the Central Calendar Log Collector runs - Job DBA:DB13CMIRROR
Category ABAP Programming Error
Runtime Errors UNCAUGHT_EXCEPTION
Except. CX_PARAMETER_INVALID_RANGE
ABAP Program CL_SYB_DBMS_UTILS=============CP
Application Component BC-DB-SYB
----------------------------------------------------------------------------------------------------
Short Text
An exception has occurred that was not caught.
----------------------------------------------------------------------------------------------------
What happened?
Exception 'CX_PARAMETER_INVALID_RANGE' was raised, but it was not caught
anywhere along the call hierarchy.
Since exceptions represent error situations, and this error was not
adequately responded to, ABAP program 'CL_ABAP_TSTMP=================CP' had
to be terminated.
----------------------------------------------------------------------------------------------------
Error analysis
An exception has occurred which is explained in more detail below. The
exception is assigned to class 'CX_PARAMETER_INVALID_RANGE' and was not caught
in procedure
"LOCAL_DATETIME_TO_DB" "(METHOD)", nor was it propagated by a RAISING clause.
Since the caller of the procedure could not have anticipated this
exception, the current program was terminated.
The reason for the exception is:
A parameter has an invalid value: Parameter TSTMP-SECS has the invalid value 0.
Read more...
Environment
- SAP Adaptive Server Enterprise for Business Suite 16.0.x
- SAP Adaptive Server Enterprise for Business Suite 15.7.x
- SAP NetWeaver (NW) - All versions
- DBA Cockpit
Product
Keywords
KBA , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview