Cannot login: Error U00003703 due to Invalid Variable GBNAME

Products

• CA Automic Workload Automation - Automation Engine
• CA Automic One Automation

Issue/Introduction

Users are unable to log in to an Automic instance (e.g., v21). Attempting to log in with correct credentials results in a timeout or hang. The Work Processor (WP) logs and forced memory trace dumps reveal the following error:

• U00003703 Ungültige Variable bei READ gefunden: Feld='GBNAME'
• U00011801 Fehler in Serverroutine 'UCUSER_R'
• U00015006 System hat einen Memory-Trace-Dump erzwungen.

Environment

Version: 21.0

Cause

he issue is caused by database corruption in the OVW or OVD tables related to the system variable objects UC_USER_HOST and/or UC_USER_LANGUAGE. Specifically, the field OVW_VRNAME or OVD_VRNAME may contain an invalid character, such as a pipe symbol (|) (e.g., USS| instead of the expected USS). This invalid value causes a failure during the UCUSER_R server routine when the system attempts to read user/host information during the login process.

Resolution

To resolve this issue, the corrupted system variable objects must be replaced with clean versions from a working system.

1. Identify Corrupted Records: Run the following SQL queries in the database to confirm the presence of invalid characters (like |) in the OVW or OVD tables:

   sql

    

   -- Check OVW table for UC_USER_HOSTSELECT OVW.* FROM OVW JOIN OH ON OH_idnr = ovw_oh_idnr WHERE OH_name = 'UC_USER_HOST';
   -- Check OVD table for UC_USER_HOST and UC_USER_LANGUAGESELECT * FROM OVD WHERE OVD_VRNAME LIKE '%|%';

2. Recover Objects via Transport Case: Obtain a transport case (uc_data.txt) containing the UC_USER_HOST and UC_USER_LANGUAGE objects from a healthy Automic system of the same version.

3.  Load Clean Objects: Use the ucybdbld utility to load the clean objects into Client 0 of the affected system:

   bash

    

   # Navigate to the utilities binary directorycd {path_to_utilities}/bin
   # Run the load command./ucybdbld -B -X{path_to_uc_data.txt} -EREPLACE

4. Verification: Restart the Automic system components if necessary and attempt to log in. The error U00003703 should no longer occur, and the login should proceed successfully.