Skip to main content
insightsoftware Documentation insightsoftware Documentation
{%article.title%}
Published:
Was this article helpful?
0 out of 0 found this helpful

Fixed Issues

The fixed issues in Angles for Oracle Generator 24.1 for Oracle Analytics. are as follows:

Angles for Oracle Generator supports TIMESTAMP data types.

The Angles for Oracle Generator for Oracle Business Intelligence (Angles for Oracle Generator) did not support the TIMESTAMP data types of the Oracle Database. Consequently, values of these data types were not converted to values of a data type that is recognized by Oracle Business Intelligence, Noetix views containing such columns could not be used in the business intelligence (BI) tool, and error messages pertaining to the columns were logged during the global consistency check.

[GEN-492]

Repository generation successful for views with single key flexfield segment.

The generation of Noetix Views (NoetixViews) metadata failed if a list of values (LoV) view was associated with the single key flexfield segment column of a view, and an error message similar to the following was displayed:

“2015-12-02 12:00:26,735 ERROR (5832) [Noetix.OBIEEGenerator.GeneratorTask] Generation failed

System.ArgumentException: Level not created yet: "[Noetix-Noetix] NoetixViews for Oracle Supply Chain"."INVG0_Stock_Locators$DETAIL".INVG0_LOV_LOCATION_FLEXFIELDS

at Noetix.UDMLGen.Dimension.GetLevel(String name)

at Noetix.OBIEEGenerator.GeneratorTask.PopulateLogicalLayer(UDMLDoc doc, Database database, IRepository`1 tabRepo, IRepository`1 joinRepo, IRepository`1 dimRepo)

at Noetix.OBIEEGenerator.GeneratorTask.GenerateSchema(List`1& udmlFileNames, List`1& changedUdmlFileNames)

at Noetix.OBIEEGenerator.GeneratorTask.GenerateUdml(List`1& udmlFileNames, List`1& changedUdmlFileNames)

at Noetix.OBIEEGenerator.GeneratorTask.MainGeneration()”

[GEN-1018]

Custom columns in joins generated successfully.

In Angles for Oracle Generator 4.2, if views from different roles were joined with the use of custom columns in the NoetixViews metadata, some of the join columns were excluded from the presentation layer during generation, warning messages similar to the following were logged, and existing reports that used the columns failed to run:

“Column with join_to_flag='Y' was not used in a join.”

[GEN-1524]

Performance, reliability of incremental regeneration improved.

The incremental regeneration process has been refactored for reliability and improvement of performance. The process now parses related object properties directly from the repository Universal Database Markup Language (UDML) file instead of attempting to read them from the NoetixViews metadata.

[GEN-1697]

Generation successful for Noetix Analytics metadata with calculated fields.

If calculated fields based on multiple columns with different data types were present in the metadata, the generation failed, and an error message similar to the following was displayed:

“ORA-00001: unique constraint (NOETIXIDS.N_GEN_VIEW_COLUMNS_PK) violated”.

[GEN-1759]

Sort order of calculated fields retained after generation.

Previously, after the Noetix Analytics for Oracle E-Business Suite (Noetix Analytics) metadata was generated into the Oracle BI repository, the sort order of the calculated fields was not retained in the presentation layer as seen in the Business Manager window of the Noetix Metadata Manager.

[GEN-1761]

Incremental regeneration detects join changes in NoetixViews metadata.

Incremental regeneration failed to detect join changes in NoetixViews metadata when the modified joins included changes to view modifier or join type. Consequently, these changes were missing in the NoetixViews metadata that was incrementally regenerated into the repository.

[GEN-1807, GEN-1897, GEN-1914]

Performance of metadata generation process improved.

Previously, the generation of the Noetix Analytics or NoetixViews metadata took longer than expected to complete.

[GEN-1847]

Metadata generation for different generators successful.

The metadata generation initiated by the Angles for Oracle Generator for Oracle Business Intelligence failed if you had previously run a generation on the metadata with the use of the Angles for Oracle Generator.

[GEN-2298]

Caching of physical tables disabled by default.

In a repository generated for the Noetix Analytics metadata, data caching was not configured consistently for the physical tables. Caching was also enabled by default for the NoetixViews metadata. Now, data caching is disabled for all the physical tables pertaining to the Noetix Analytics and NoetixViews metadata. To modify the default data caching behavior, use the instructions provided in the Map.xml file that is available with the Angles for Oracle Generator. To modify the data cache setting defined for each table, you can also use the hk_popgvw.sql script to update the value of the CACHE_MODE column in the N_GEN_ALL_TABLES_V view on the basis of the cache modes listed in the Map.xml or MapOverride.xml file. For assistance, contact insightsoftwareSupport.

[GEN-2350]

Logical table names no longer fail incremental regeneration.

Previously, if your metadata contained certain logical tables names, the incremental regeneration process failed with the following error message:

“System.ArgumentOutOfRangeException: Index and length must refer to a location within the string.”

[GEN-2412]

 

Published:

Fixed Issues

The fixed issues in Angles for Oracle Generator 24.1 for Oracle Analytics. are as follows:

Angles for Oracle Generator supports TIMESTAMP data types.

The Angles for Oracle Generator for Oracle Business Intelligence (Angles for Oracle Generator) did not support the TIMESTAMP data types of the Oracle Database. Consequently, values of these data types were not converted to values of a data type that is recognized by Oracle Business Intelligence, Noetix views containing such columns could not be used in the business intelligence (BI) tool, and error messages pertaining to the columns were logged during the global consistency check.

[GEN-492]

Repository generation successful for views with single key flexfield segment.

The generation of Noetix Views (NoetixViews) metadata failed if a list of values (LoV) view was associated with the single key flexfield segment column of a view, and an error message similar to the following was displayed:

“2015-12-02 12:00:26,735 ERROR (5832) [Noetix.OBIEEGenerator.GeneratorTask] Generation failed

System.ArgumentException: Level not created yet: "[Noetix-Noetix] NoetixViews for Oracle Supply Chain"."INVG0_Stock_Locators$DETAIL".INVG0_LOV_LOCATION_FLEXFIELDS

at Noetix.UDMLGen.Dimension.GetLevel(String name)

at Noetix.OBIEEGenerator.GeneratorTask.PopulateLogicalLayer(UDMLDoc doc, Database database, IRepository`1 tabRepo, IRepository`1 joinRepo, IRepository`1 dimRepo)

at Noetix.OBIEEGenerator.GeneratorTask.GenerateSchema(List`1& udmlFileNames, List`1& changedUdmlFileNames)

at Noetix.OBIEEGenerator.GeneratorTask.GenerateUdml(List`1& udmlFileNames, List`1& changedUdmlFileNames)

at Noetix.OBIEEGenerator.GeneratorTask.MainGeneration()”

[GEN-1018]

Custom columns in joins generated successfully.

In Angles for Oracle Generator 4.2, if views from different roles were joined with the use of custom columns in the NoetixViews metadata, some of the join columns were excluded from the presentation layer during generation, warning messages similar to the following were logged, and existing reports that used the columns failed to run:

“Column with join_to_flag='Y' was not used in a join.”

[GEN-1524]

Performance, reliability of incremental regeneration improved.

The incremental regeneration process has been refactored for reliability and improvement of performance. The process now parses related object properties directly from the repository Universal Database Markup Language (UDML) file instead of attempting to read them from the NoetixViews metadata.

[GEN-1697]

Generation successful for Noetix Analytics metadata with calculated fields.

If calculated fields based on multiple columns with different data types were present in the metadata, the generation failed, and an error message similar to the following was displayed:

“ORA-00001: unique constraint (NOETIXIDS.N_GEN_VIEW_COLUMNS_PK) violated”.

[GEN-1759]

Sort order of calculated fields retained after generation.

Previously, after the Noetix Analytics for Oracle E-Business Suite (Noetix Analytics) metadata was generated into the Oracle BI repository, the sort order of the calculated fields was not retained in the presentation layer as seen in the Business Manager window of the Noetix Metadata Manager.

[GEN-1761]

Incremental regeneration detects join changes in NoetixViews metadata.

Incremental regeneration failed to detect join changes in NoetixViews metadata when the modified joins included changes to view modifier or join type. Consequently, these changes were missing in the NoetixViews metadata that was incrementally regenerated into the repository.

[GEN-1807, GEN-1897, GEN-1914]

Performance of metadata generation process improved.

Previously, the generation of the Noetix Analytics or NoetixViews metadata took longer than expected to complete.

[GEN-1847]

Metadata generation for different generators successful.

The metadata generation initiated by the Angles for Oracle Generator for Oracle Business Intelligence failed if you had previously run a generation on the metadata with the use of the Angles for Oracle Generator.

[GEN-2298]

Caching of physical tables disabled by default.

In a repository generated for the Noetix Analytics metadata, data caching was not configured consistently for the physical tables. Caching was also enabled by default for the NoetixViews metadata. Now, data caching is disabled for all the physical tables pertaining to the Noetix Analytics and NoetixViews metadata. To modify the default data caching behavior, use the instructions provided in the Map.xml file that is available with the Angles for Oracle Generator. To modify the data cache setting defined for each table, you can also use the hk_popgvw.sql script to update the value of the CACHE_MODE column in the N_GEN_ALL_TABLES_V view on the basis of the cache modes listed in the Map.xml or MapOverride.xml file. For assistance, contact insightsoftwareSupport.

[GEN-2350]

Logical table names no longer fail incremental regeneration.

Previously, if your metadata contained certain logical tables names, the incremental regeneration process failed with the following error message:

“System.ArgumentOutOfRangeException: Index and length must refer to a location within the string.”

[GEN-2412]

 

For an optimal Community experience, Please view on Desktop
Powered by Zendesk