SQL delivered with 20.3.3hf3 july release generates a warning - Warning! The maximum key length is 900 bytes. The index 'UNQ_VIEW_ACCOUNT_IDX1' has maximum length of 922 bytes. For some combination of large values, the insert/update operation will fail.

book

Article ID: 220642

calendar_today

Updated On:

Products

DX Infrastructure Management

Issue/Introduction

On some SQL versions, the following warning is seen when running the SQL Script that is delivered with the UIM 20.3.3 July Patch:

 

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

Environment

Release : 20.3 JULY PATCH - SQL 2014 (and possibly prior versions)

Component : UIM - INSTALL

Resolution

This warning can be ignored.

What it means is that, if someone tries to create a new metric view, and the attempted insert (of the fields VIEW_NAME, ACCOUNT_ID, CREATEDBY, CS_ID, GROUP_ID, VIEW_TYPE) is over 900 bytes in length, the metric view will fail to insert properly.   This is relatively unlikely and would essentially require someone to attempt to create a metric view with a name that was around 800+ characters in length.

In the event that someone tries to do this, the operator console will generate a failure message and the user will have a chance to shorten the name prior to saving the view.