Release notes - Guardium Insights Version 3.4.2

SQLCODE=-1803, SQLSTATE=57056, SQLERRMC=NULLID.SYSSN200 0X5359534C564C3031, DRIVER=4.26.14
SQLCODE=-901, SQLSTATE=58004, SQLERRMC=Plan/Environment mismatch!, DRIVER=4.26.14

Workaround: See Db2 errors for reports and risk services.

Workaround: To re-upload the files that have been preserved - and to resume ingestion - restart ssh-service.

• INS-37007
• INS-42808

Workaround: See Existing universal connector certificate does not work in a restored environment.

Data mart unavailable Cannot load data mart statistics. Refresh the page to try again

Workaround: If the Data mart ingestion page displays this error, you can access the data mart ingestion information by opening the Data mart ingestion status report. This report includes data marts collected from both collectors and aggregators. To open the reports page, select Reports in the main menu. Open this menu by clicking the main menu icon ()

Workaround: Go to the user management screen and add the user. Then return to the Refine alerts page to add the user to the list.

Workaround: Before upgrading, ensure that the length of the spec.guardiumInsightsGlobal.ingress.hostname value in your custom resource (CR) file is 58 characters or fewer.

Workaround: Restart the data retention pod after changing the settings.

Workaround: See Guardium Insights upgrade becomes stuck because CSV does not update.

Workaround: Before upgrading to Guardium Insights v3.4.0, you must stop streaming.

When you start data mart streaming after upgrade completion, enter a new date for v5 data marts. The initial start date can be set in the Schedule managed units export wizard in the page for the central manager. This date should be earlier than the date on which you stopped streaming data marts.

Workaround: Reset user configurations for the environment before opening compliance milestones.

Workaround: Restart the Service Pod before logging in to the application.

Workaround: Ensure that you have installed Tenant Minisnif and Tenant GUC Custom Resources Version 3.3.4 or later (see this step).

Workaround: Download the Dynamo Db plug-in and upload it to Guardium Insights (see Connecting to data sources by using the universal connector).

Workaround: Increase the storage volume count or contact IBM Cloud support.

Guardium Insights v3.4 changes the data model from v3.3 in order to improve report and ingestion performance. Shortly after upgrade, you may see scheduled reports running longer than usual or, in some circumstances, failing. The reason behind this may be that the data in the old data model and the new data model are being joined into a single result set in an attempt to minimize disruption. If you encounter longer than normal scheduled report execution times, this should be temporary and subsequent runs should be much faster.

Workaround: If scheduled reports are failing, inspect the reports-runner pod logs. If you encounter an SQLCODE=-4712, SQLSTATE=5U026 error, consider turning on the Table join optimization feature in the Tenant settings. If the problem persists or if you are encountering ERRORCODE=-1224, SQLSTATE=55032 instead, consider temporarily splitting the report into smaller time frames. These issues should only occur if the scheduled report includes a date range both prior to and after the v3.4 upgrade. Future reports should not encounter these issues.

These reports may contain duplicate data. The duplicates will not appear in the main reporting categories on the audit data (for example, DB Activity, Full SQL, and Policy Violation) as the processing of the active data to the permanent data consolidates and removes the duplication.

Workaround: None for the Active report categories. You can use the main report categories instead.

Workaround: See Existing data mart pull configuration does not work in a restored environment.

Workaround: Reconfigure the unhealthy universal connector connections..

Workaround: Re-register the Guardium Data Protection connections to update existing certificates.

Workaround: Manually delete the collections (assets_filter_template, assets_filter_template_mapping, asset_policy, asset_rule) from MongoDB and then launch the Asset inventory page again.

[WARNING] File MONGO_USER is not available.

Workaround: See MongoDB warning in pre-upgrade validation script.

Workaround: See Existing data mart pull configuration does not work in a restored environment.

Workaround: Reconfigure the Filebeat/syslog universal connector connections.