ACSLS - "Could not find matching request" When ACS or LSM is Varied Online (Doc ID 1308614.1)

Last updated on JULY 11, 2022

Applies to:

Symptoms

1.  Cannot vary the ACS after the library was brought down.   The library is an SL8500 with dual-TCP feature enabled.

2.  The acsss_event.log is showing these messages:

     2011-03-01 14:35:28 ACSLH[0]:
     2034 N EventLog.C 1 123
     ACSLH: Request Recoverer: RequestRecoverer: Vprocess():
     Error in processTmMessages(): IntermediateResponse: execute(): Could not find matching request.

     2011-03-01 14:35:28 ACSLH[0]:
     1133 N Lh_main.C 1 260
     Lh error: main:FlushCircuits: Serious internal error, please check event log.

     2011-03-01 14:35:38 ACSLH[0]:
     2034 N EventLog.C 1 123
     ACSLH: Request Recoverer: RequestRecoverer: Vprocess():
     Error in processTmMessages(): FinalResponse: execute(): Could not find matching request.

3.  The vary command fails with these error messages:

     2011-03-01 14:45:49 VARY[48272]:
     126 N va_lsm_stat.c 1 2656
     va_lsm_state:st_req_error: Timed out waiting for message

     2011-03-01 14:45:49 VARY[48272]:
     1 E va_lsm_stat.c 1 2727
     va_lsm_state:st_req_error: cl_lsm_update() unexpected status = STATUS_VALUE_UNCHANGED

     2011-03-01 14:45:49 ACSSA[0]:
     1435 W sa_demux.c 1 296
     Unable to handle unusual status or event. See related messages.

Changes

1.  The library was brought down to perform hardware maintenance. The LSM in ACSLS was not varied offline prior to the library going down.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.