Column Override Save As System Wide Default Not Working For Columns When Archiving and Unarchiving Between Environments (Doc ID 2992177.1)

Last updated on DECEMBER 21, 2023

Applies to:

Symptoms

When Archiving and Unarchiving the reports between the two OBIEE environments, Column format> Override data format > Save as "System Wide Default "  for the columns done in the Source report is not working for columns in the reports in Target environment.

In OBIEE 12c, the web catalog is located at:

<DOMAIN_HOME>\bidata\service_instances\ssi\metadata\content\catalog

Whenever an analysis is created with a column from a Subject Area, for example Subject Area name is "A - Sample Sales" , then in Column Properties > Data Format > [x] Override Default Data Format > Save As Default > Save as the system-wide default for {column}, the custom format is "saved" in the <DOMAIN_HOME>\bidata\service_instances\ssi\metadata\content\catalog\root\system\metadata folder.

Due to the above steps, the following files will appear in the directory <DOMAIN_HOME>\bidata\service_instances\ssi\metadata\content\catalog\root\system\metadata :-
a+-+sample+sales >> This will be an XML file
a+-+sample+sales.atr >> This will be an associated permissions file

The file created is always Subject Area specific, for example if there are 2 columns from the same Subject Area with "save as system-wide defaults", then there would be just the 1 XML file with the Subject Area name and it would contain 2 settings, that will be 1 per column.

These files won't get moved when Archiving and Unarchiving the analysis between two environment and we have to manually move these files from the Source to the Target.

Changes

 Archiving and Unarchiving between the two OBIEE environments.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.