NLS_LENGTH_SEMANTICS reverts to BYTE after a database Interruption in Automation Engine.
search cancel

NLS_LENGTH_SEMANTICS reverts to BYTE after a database Interruption in Automation Engine.

book

Article ID: 442364

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

After a temporary database connection loss (e.g., deadlock, network interruption, or DB reboot), the Automation Engine session parameters are not fully restored upon reconnection. Specifically, the NLS_LENGTH_SEMANTICS parameter reverts to the Oracle default of BYTE, even if the connection string explicitly defines it as CHAR.

In the Automation Engine logs, the following sequence can be observed:

  1. Initial successful connection shows correct parameters: U00003535 DB INFO: 'NLS_LENGTH_SEMANTICS = CHAR'
  2. Connection is lost and re-established: U00003538 UCUDB: Re-connection to database successful.
  3. Only a partial ALTER SESSION is performed: U00029114 UCUDB - ALTER SESSION: NLS_LANGUAGE=AMERICAN
  4. Subsequent DB info shows the incorrect semantics: U00003535 DB INFO: 'NLS_LENGTH_SEMANTICS = BYTE'

Cause

This issue is caused by a defect in the Automation Engine's reconnection logic for C-based processes (CP/WP). When a connection is re-established, the system fails to re-apply all session parameters specified in the ODBC connection string, specifically NLS_LENGTH_SEMANTICS.

This issue is currently being addressed by Engineering under defect DE202233.

Resolution

Update to a fixed version listed below or a newer version if available.

Automic Automation Engine TBA - TBA

Additional Information

Article title: How to register to Broadcom Software Product updates and Critical Alerts

https://knowledge.broadcom.com/external/article?articleId=133819