Release Notes › Known Issues › General › Warning Message When Running an OOTB Snapshot DDL Script

Warning Message When Running an OOTB Snapshot DDL Script

Symptom:

The following sql script produces an invalid index when run on a Microsoft SQL database:

IdentityManager/IAM_Suite/IdentityManager/tools/imrexport/db/SqlServer/ims_mssql_report.sql

The script returns with the following warning message:

Warning! The maximum key length is 900 bytes. The index 'imruser6_index_3' has maximum length of 1260 bytes. For some combination of large values, the insert/update operation will fail.

Solution:

Follow these steps:

1. Use the following code to create a stored procedure:

   CREATE PROCEDURE sp_imruser6_index_3_exists
   AS
   BEGIN
   DECLARE @MAX_LEN integer
   DECLARE @sql_cmd nvarchar(255)
   DECLARE @stmt nvarchar(255)
       SET @MAX_LEN = (SELECT SUM(max_length)AS TotalIndexKeySize FROM sys.columns WHERE name IN (N'imr_userdn', N'imr_reportid') AND object_id = OBJECT_ID(N'imruser6'))
            IF EXISTS (SELECT name FROM sysindexes WHERE name = 'imruser6_index_3') DROP INDEX imruser6_index_3 on imruser6
       IF (@MAX_LEN > 900)
           CREATE INDEX imruser6_index_3 ON imruser6 (imr_reportid) INCLUDE(imr_userdn)
       ELSE
           CREATE INDEX imruser6_index_3 ON imruser6 (imr_reportid, imr_userdn)
   END
   GO
   

   Stored procedure is now created.

2. Use the following command to run the stored procedure:

   EXEC sp_imruser6_index_3_exists 
   

After successfully executing the stored procedure, the column imr_userdn under imruser6_index_3 becomes as included column.

Non-Context Sensitive Help for Mobile App

Symptom:

When a user clicks the help icon while performing mobile app tasks, unrelated help displays.

Solution:

Browse for mobile app help in the table of contents or by searching the help.