My Oracle Support Banner

No Data Is Shown But No Data Is Loaded When Manually Running AWM Maintenance Scripts (Doc ID 462110.1)

Last updated on MARCH 10, 2020

Applies to:

Oracle OLAP - Version 10.1.0.2 and later
Information in this document applies to any platform.

Symptoms

It is possible to save the scripts used to maintain objects within an Analytical Workspace to a file. These files can later be executed as needed or integrated into batch processing systems.

Such a script could look as follows:

declare
xml_clob clob;
xml_str varchar2(4000);
isAW number;
begin
DBMS_LOB.CREATETEMPORARY(xml_clob,TRUE);
dbms_lob.open(xml_clob, DBMS_LOB.LOB_READWRITE);
dbms_lob.writeappend(xml_clob, 191, '  <BuildDatabase  Id="Action3" AWName="VRO_OWNER.VRO_OLAP" BuildType="BACKGROUND" RunSolve="true" CleanMeasures="false" CleanAttrs="true" CleanDim="true" TrackStatus="false" MaxJobQueues="1">');
dbms_lob.writeappend(xml_clob, 47, '    <BuildList XMLIDref="DIM_TIME.DIMENSION" />');
dbms_lob.writeappend(xml_clob, 18, '  </BuildDatabase>');
dbms_lob.close(xml_clob);
xml_str := sys.interactionExecute(xml_clob);
dbms_output.put_line(xml_str);
end;
/

When such a script is being executed via a third-party tool, it may not work as exepected.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution

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