Catalog Request creation is failing

Products

• CA Service Catalog

Issue/Introduction

after the creation of the case the following error message appears:

In the validations carried out in the test environment, this behavior is not evident.

Environment

Release : 17.3

Component : Catalog - MDB Issue

Cause

If the creation attempt can be reproduced, enable Catalog tracing during such a creation attempt to determine the cause of the error.  Please review KB Article 12894 to review how to engage the tracing 

Resolution

In the following example, the backend database needs to allow larger LOB content to be tolerated for storage

On review of the logging received, view.log, we note these entries of interest in the logging.  The specific SQL Server error is the entries highlighted in red.  One can find the associated Catalog request, 262144 in the above example referenced in the logging below.  Associated database fields and tables are in yellow.

 TRACE [ActiveMQ Session Task-184] [DBSource] Update [PreparedSql]: insert into usm_request_item_form (form_elem_name,form_elem_value,subscription_detail_id,is_visible) values (?,?,?,?)

 TRACE [ActiveMQ Session Task-184] [DBJDBC] SQL State=S0001, Error code=7139

 ERROR [ActiveMQ Session Task-184] [DBSource] Error while saving object:{form_elem_name=txtaError, form_elem_value=

 TRACE [ActiveMQ Session Task-184] [DBSource]   Params [PreparedSql]: [84507, Request Submission failed for 262144, REQSUBMIT_FAILED, RequestQueueListener, XXXX, CRITICAL, Length of LOB data (95102) to be replicated exceeds configured maximum 65536. Use the stored procedure sp_configure to increase the configured maximum value for max text repl size option, which defaults to 65536. A configured value of -1 indicates no limit, other that the limit imposed by the data type., , , 1, 05/16/2022 14:34:11]

Additional Information

In this example, the issue is unique to the particular database and how it is handling the LOB content.  The DBA should review their backend database configurations and potentially enlist the DB vendor if there is a difference in query behaviour.