Notification of actions needed by users when upgrading to 21.02

BMC is alerting users of TrueSight Server Automation that they must perform certain actions before and after they upgrade to version 21.02.

Problem 1: The Application Server reaches its maximum connection limit

After you upgrade to version 21.02, the Application Server reaches its maximum connection limit randomly. The Application Server log displays the following warning:

[Appserver] Cannot accept new connections. The appserver has reached its maximum connection limit.

Solution 1

Before you upgrade to version 21.02, update the load balancer and health monitor to use the JmxManagement port (9838), instead of the AuthSvc port (9840), AppSvc port (9841), and ProxySvc port (9842). 

If you have not changed this port before upgrade, change the port after upgrade and restart the Application Server.

For more information about the problem and workaround, see the KB Article.

Problem 2: A user exceeds the maximum number of webservices sessions permitted

After you upgrade to version 21.02, the maximum allowed webservices (SOAP, REST) connections exceed under the same load prior to the upgrade. The Application Server log displays the following error:

The user 'USER' has exceeded the maximum number of sessions permitted for a user.

Solution 2

After the upgrade to version 21.02.00 is complete, contact BMC Support for the hotfix. For more information about the problem and workaround, see the KB Article. 

This issue has been fixed in version 21.02.01. See DRBLG-126253 on Known-and-corrected-issues.

Problem 3: The Agent Installer job and Update Server Properties job fail with the java.lang.Stringjava.lang.ClassCastException

The Agent Installer job and Update Server Properties job might fail with the following exception:

[WorkItem-Thread-0] [ERROR] [prod.UserA.1005497015:BLAdmins:] [ServerProperty] [] com.bladelogic.om.infra.model.typesystem.value.ComplexPropertyReferenceBlValueImpl cannot be cast to java.lang.String[02 Apr 2020 1x:1y:102,657] [WorkItem-Thread-0] [ERROR] [prod.userA.46x49701h:BLAdmins:] [ServerProperty] [] com.bladelogic.om.infra.model.typesystem.value.ComplexPropertyReferenceBlValueImpl cannot be cast to java.lang.Stringjava.lang.ClassCastException: com.bladelogic.om.infra.model.typesystem.value.ComplexPropertyReferenceBlValueImpl cannot be cast to java.lang.String at com.bladelogic.om.infra.model.server.ServerImpl.comparePropertyValue(ServerImpl.java:7296) ~[bladelogic_infra.jar:?]

Solution 3

After the upgrade to version 21.02.00 is complete, contact BMC Support for the hotfix. For more information about the problem and fix, see the KB Article. 

This issue has been fixed in version 21.02.01. See DRBLG-126421 on Known-and-corrected-issues.

Problem 4: Database migration fails with the FKX1_BL_AUTH constraint violation

During upgrade from version 20.02.01 to 21.02, the database migration fails with the following error if ACL uses the AgentConfig.* authorization:

[1] ERROR: TSK NM=Insert Core Data ; TSK SCR NM= ; TO=21.02.00.000 ; TSK MSG=The DELETE statement conflicted with the REFERENCE constraint "FKX1_BL_AUTH". The conflict occurred in database "BLADELOGIC", table "dbo.bl_acl_agg_auth", column 'bl_auth_id'.
[2] ERROR: TSK NM=Insert Core Data ; TSK SCR NM= ; TO=21.02.00.000 ; TSK MSG=Upgrade halted. Insert Core Data did not complete step Start of core data insert. Contact BladeLogic Support before resuming.
.[1] ERROR: TSK NM=Insert Core Data ; TSK SCR NM= ; TO=21.02.00.000 ; TSK MSG=Upgrade halted. Insert Core Data did not complete step Start of core data insert. Contact BladeLogic Support before resuming.

[2] ERROR: TSK NM=Insert Core Data ; TSK SCR NM= ; TO=21.02.00.000 ; TSK MSG=The DELETE statement conflicted with the REFERENCE constraint "FKX1_BL_AUTH". The conflict occurred in database "BLADELOGIC", table "dbo.bl_acl_agg_auth", column 'bl_auth_id'.
Do not hit any FK Constraint issues

Solution 4

Scenario 1: You have not started the upgrade process.

  1. Execute the following SELECT statements:

    SELECT * FROM BL_ACL_AGG_AUTH WHERE BL_AUTH_ID IN (10700, 10701, 10702, 10703,10704,10705,10706,10707);
    SELECT * FROM bl_acl_policy_agg_auth WHERE BL_AUTH_ID IN (10700, 10701, 10702, 10703,10704,10705,10706,10707);
    SELECT * FROM BL_AUTH_NOTIFICATION WHERE BL_AUTH_ID IN (10700, 10701, 10702, 10703,10704,10705,10706,10707);
    SELECT * FROM AUDIT_TRAIL WHERE BL_AUTH_ID IN (10700, 10701, 10702, 10703,10704,10705,10706,10707);
  2. If the above SELECT statements return more than one row, contact BMC Support to avoid the upgrade failure.

Scenario 2: You have started the upgrade process, and the error occurs.

  1. Cancel the upgrade process, and execute the following SELECT statements:

    SELECT * FROM BL_ACL_AGG_AUTH WHERE BL_AUTH_ID IN (10700, 10701, 10702, 10703,10704,10705,10706,10707);
    SELECT * FROM bl_acl_policy_agg_auth WHERE BL_AUTH_ID IN (10700, 10701, 10702, 10703,10704,10705,10706,10707);
    SELECT * FROM BL_AUTH_NOTIFICATION WHERE BL_AUTH_ID IN (10700, 10701, 10702, 10703,10704,10705,10706,10707);
    SELECT * FROM AUDIT_TRAIL WHERE BL_AUTH_ID IN (10700, 10701, 10702, 10703,10704,10705,10706,10707);

  2. See the KB Article for more information about the problem. Contact BMC Support with the output of the above statements and the NSH/br/blmigration.log file.

This issue has been fixed in version 21.02.01. See DRBLG-126505 on Known-and-corrected-issues.

Problem 5: The SQL Server database migration fails with the "Table 'bl_patch_language' does not have the identity property. Cannot perform SET operation" error

During upgrade to 21.02.00, the SQL Server database migration fails with the following error:

2021-05-04T03:57:17,915 [Thread-659 -- Task: com.bmc.install.product.bladelogic.task.upgrade.BlUpgPersistConfigurationIntoDatabaseTask] INFO com.bladelogic.mig.framework.common.MigLogger [] - EXCEPTION WHILE RUNNING SINGLE STEP MIGRATION FROM 20.02.01.000 TO 21.02.00.000

============================================================================================
[1] ERROR: TSK NM=Insert Core Data ; TSK SCR NM= ; TO=21.02.00.000 ; TSK MSG=Upgrade halted. Insert Core Data did not complete step Start of core data insert. Contact BladeLogic Support before resuming.
[2] ERROR: TSK NM=Insert Core Data ; TSK SCR NM= ; TO=21.02.00.000 ; TSK MSG=Table ' bl_patch_language' does not have the identity property. Cannot perform SET operation.

Solution 5

This issue only affects SQL Server environments which, at some point in the past, were running a TrueSight Server Automation version earlier than 8.9. The issue does not affect the SQL Server environments which started with TrueSight Server Automation 8.9 or later.

Scenario 1: You have not started the upgrade process.

  1. Execute the following SELECT statement:

    IF
    OBJECTPROPERTY(OBJECT_ID('bl_patch_language'), 'TableHasIdentity') = 1
    PRINT N'bl_patch_language has identity.';
    ELSE
    PRINT N'bl_patch_language identity not found.';
  2. If the above SELECT statement returns "bl_patch_language identity not found.", contact BMC Support to avoid the upgrade failure. 
  3. If the above SELECT statement returns "bl_patch_language has identity", proceed with the 21.02 upgrade as planned.

Scenario 2: You have started the upgrade process, and the error occurs.

  1. Cancel the upgrade process, and execute the following SELECT statements:

    Query:1

    IF OBJECTPROPERTY(OBJECT_ID('bl_patch_language'), 'TableHasIdentity') = 1
    PRINT N'bl_patch_language has identity.';
    ELSE
    PRINT N'bl_patch_language identity not found.';

    Query:2
    select t.name as TableName,c.name as ColumnName
    from sys.identity_columns c
    inner join sys.tables t on c.object_id = t.object_id
    where t.name = 'bl_patch_language';

    Query:3
    select * from mig_run ;

  2. See the KB Article for more information about the problem. Contact BMC Support with the output of the above statements and the NSH/br/blmigration.log file.

This issue has been fixed in version 21.02.01. See DRBLG-126447 on Known-and-corrected-issues.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*