ODS / Release Guide / 3.1

Section 4 Problem Resolutions
Administrative User Interface
correctly. Hence, the resulting usage of the WHERE clause could wind up with
incorrect or invalid SQL.
Note: This only impacted users of the Freeze Single table function. The Freeze
Multiple tables function uses different logic entirely and was NOT
impacted by this particular defect.
Resolution
The method of delimiting data in parameter lists for JOB streams was changed to
account for commas being used inside parameter values.
1-191CCV
Impact
When the Health Check job is run, row count warnings are reported for meta data,
as well as warnings that indexes are missing.
Resolution
Corrected the reported meta data numbers in MGKODSU. Obsolete system
generated indexes were removed from MGBINDX.
1-1ABGHL
Impact
The Javascript code behind the Delete button had a bug in it, limiting the number
of control reports that could be selected.
Resolution
The technique used to identify records to be deleted was changed.
1-1EJL1X
Impact
The ability to only assign the WebTailor role of 'Information Access Meta Data'
would not work. Users get an error when logging in.
Resolution
Missing rows were added for the bmenu.P_MainMenu to the TWGRMENU table.
1-10XGUN
Impact
If using combinatorial "OR" logic in a WHERE clause with a Freeze Table definition,
not wrapping the condition(s) with parenthesis can cause unexpected results.
Resolution
Supplied WHERE clause conditions in Freeze Table definitions are now wrapped
automatically with parentheses when the WHERE clause combined with the
automatic EVENT conditions when processing a Freeze.
1-N7FXD
Impact
If more than one DB link exists in the ODS instance with a naming like
'%SOURCE_DB%', this error would occur, causing the Health Check job to abort.
Operational Data Store Release 3.1 April 2007
28 Release Guide Confidential