Error Installing the SALESTRACK analytic workspace in the OLAPTRAIN schema

Hello all,
I am working on Oracle 11g v.11.1.0.
When I am trying to install the SALESTRACK aw, it gives me an error saying,'OLAP error,Unable to parse the XML string returned from client to server'. What actually does the error denote? And how shall I get it fixed? Please help me out to get it fixed. Any help would be appreciated..
thanks and regards,
Susane

First thing to check is that you're running 11.1.0.7 with the required OLAP patch on the server. See here for list of OLAP patches - http://www.oracle.com/technology/products/bi/olap/collateral/olap_certification.html
Then doublecheck you're following the correct instuctions as per the installation (like the user your running script has appropriate privileges)
Laura

Similar Messages

How to read the java analytical workspace object, when it is being rebuild?

Hi is there any way to save the OLAP into java object, so that it can be read even though it is being rebuild?
so when I rebuild the AW(analytical workspace), the other user still can read the old AW object while waiting the new AW object is build
I even try to create 2 AW, while I create 1 AW I try to read another AW in the same database schema
but then the reading process for the second AW is hang until the creation of the first AW is finish
is there any way so that the process can happen simultaneously without waiting the building process is finished?

A second user should be able to access an AW even while it is being built as long as the two users have different sessions - instances of OracleConnection in jdbc terms. It is not enough to use two Java Threads sharing the same connection.

Could not apply the Blur Gallery workspace because the file is locked...

I fixed the permissions 10x times (from Safe Mode as well). I reassigned and reassigned the Permissions. I reset the PS Preferences. I "Uninstall LT5, Uninstall PSCC2014, Unistall Creative Cloud. Reinstall Creative Cloud, Install PSCC 2014 from the Cloud, (and HAVE NOT reinstall) LT5.5 from the Adobe site."; I reinstalled OX 10.10.3. Nothing fixes the problems I am having: CC updater always stopped at 50% and the failed. I will get "Could not apply the Blur Gallery workspace because the file is locked..." any blur from Blur Gallery. I did noticed one thing, I can use any blur from this menu once and then I will get the error message. I will get to use one tool once from the Blur Gallery. Also I couldn't save my keyboard "Short Cut". Anyone
I tried everything I can find online and nothing helps. Any suggestions welcome. Thanks!!

We would need to know the amount of Video ram you have. If it is above 512 MB, then check for driver updates.
Windows OS
Click Start.
On the Start menu, click Run.
In the Open box, type "dxdiag" (without the quotation marks), and then click OK.
The DirectX Diagnostic Tool opens. Click the Display tab.
On the Display tab, information about your graphics card is shown in the Device section. You can see the name of your card, as well as how much video memory it has.
Once you know the kind of graphics card you have, visit the manufacturer's website to download the latest driver. Here are links for downloading drivers from the most common graphics card manufacturers:
NVIDIA: http://www.nvidia.com/content/drivers/drivers.asp
AMD: http://support.amd.com/en-us/download
Intel: http://support.intel.com/support/graphics/

I tried to install latest OS update. Recd error installing. IT tried to load the upgrade in Safe Mode. Now system will not boot up. IT says I have to do a clean install which loses all data.

After receiving an error when I try to install the latest update of OS-X, I took my laptop to oour schools IT dept. They tried to run the update in safe mode and then they got an error saying the system could not find the hard drive. Now they want to run a clean install which loses 1000's of docs and pictures. I have Block I exams in med school next Monday and all of my notes and slides are on that hard drive.
The IT dept took the hard drive out and tried to back it up and they said they other computer could not connect or find my hard drive.
Major panic....
I have Norton antivirus and have never found any viruses on the system. I also have a program called ExamSoft which some other students here have noted they had similar crashes. Not sure if that is the issue...

Several take home messages here:
always back up before you update.
always back up anything you don't want to lose. Kind of like flossing. Only floss the teeth you don't want to lose.
Norton is very, very bad software, and you should get rid of it.
You don't need antivirus software on your mac. Antivirus software on macs causes more trouble than it is worth.
Your hard drive may be failing and thus may not be salvageable.
You could try booting into the recovery partition and seeing if you can repair your hard drive.
If that doesn't work, then there is a small chance that a third party utility (like Disk Warrior or TechTool) might be able to fix your drive (if it is not failing).
If that doesn't work, you may be able to send your drive and a lot of cash to a drive recovery service and see if they can get your files off it.
In the mean time, get notes and slides from a (smart) friend.

Fatal Error installing a Laserjet Pro400 m401dne using the full installion driver

When we go to install this printer on our computer using a USB port and select windows 7 64 bit and do the full installation everything goes smooth till it gets to 99% then it just takes forever and comes up with a "Fatal Error" we tried the lastest driver on the HP driver support site and also tried the CD that came with the machine. We then just used the driver with no installer which allowed up to print and then did the firmware update so we have the lastest firmware then again tired doing the full installation but still get the "Fatal Error" any ideas how to fix this?
Paul

I would also like to update this request by adding I am having same issue trying to reinstall my officejet 6500n.
Sounds like same problem. No 4 digit error code. Windows 7. Used event viewer to find the code 1359. This one is not on your list. Followed another error code instructions. Like Oriignal poster, I diabled services and start up, re-registered 'Atl.dll' and unregistered and re-registered 'msiexec'. I have used the original disk as well as the newest downloadable drivers.
I have also attepmted the workaround offered by dowloading and installing basic print and scan drivers. I get the same error message as I did in the full installation attmept.

Error installing KB3025390. Now cannot decline the patch.

I am running SBS 2011 Windows 2008R2.
Patch KB3025390 was pushed through by WSUS. When I tried to install the patch it failed. I then downloaded the patch from the Microsoft Download site and tried to install it. It failed again. Now I cannot decline the patch in SBS Console > Updates. It
just shows up under errors.
Does anyone know how I can either get this patch installed or declined?
Thanks
Howard

Hi Howard,
Based on your description, I understand that you failed to install the KB3025390 when it pushed via WSUS. Then
directly download the update from Microsoft site and install again. However, still fail to install the update.
Did you install any third-party application on the server? Please perform a
clean boot and check if this issue still exist. Please also run
SBS BPA tool and check if find relevant issues.
Meanwhile, did you get any error message when failed to install this update? Please also check
CBS and WindowsUpdate log files if find more clues.
For WSUS, please refer to following article and repair WSUS, then check if can help you.
Repair Windows Server Update Services
If anything I misunderstand or any update, please don’t hesitate to let me know.
Hope this helps.
Best regards,
Justin Gu
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Problem with Oracle Analytic Workspace Manager ver 10.1.0.4

Hi,
I am running Oracle Analytic Workspace Manager ver 10.1.0.4. When I tried getting connected to Analytical workspace I get the following error. Any help could be appreciated.
java.sql.SQLException: ORA-00904: "O"."SF_VERSION": invalid identifier
at oracle.olap.awm.businessobject.aw.WorkspaceBO.getWorkspacesOwnedBySchemaInStandardForm(WorkspaceBO.java:191)
at oracle.olap.awm.navigator.node.WorkspaceFolderNode.getChildren(WorkspaceFolderNode.java:101)
at oracle.olap.awm.navigator.node.BaseNodeModel.refreshData(BaseNodeModel.java:74)
at oracle.olap.awm.navigator.node.BaseNodeModel.dTreeItemExpanding(BaseNodeModel.java:221)
at oracle.bali.ewt.dTree.DTreeDeferredParent.__fireExpansionChanging(Unknown Source)
at oracle.bali.ewt.dTree.DTreeDeferredParent.setExpanded(Unknown Source)
at oracle.olap.awm.navigator.node.BaseNode.expandHelper(BaseNode.java:1813)
at oracle.olap.awm.navigator.node.BaseNode.access$000(BaseNode.java:93)
at oracle.olap.awm.navigator.node.BaseNode$ExpansionThread.run(BaseNode.java:1763)
Thanking u,
Amudha

There are posts on the OLAP forum covering this problem. Anthony Waite from the OLAP Product Management team has provided the following information:
e new, default Model View in AWM 10.1.0.4.0 is based upon the OLAP Analytic Workspace API (a.k.a. AW/XML). Just to recap and further clarify my earlier post, you must pass the following requirements in order to use it:
1) Be sure to be using the Enterprise Edition of the Oracle Database 10g.
SQL> select banner from v$version where banner like 'Oracle%';
You should see Oracle Database 10g Enterprise Edition.
2) Be sure to have the Data Warehouse database configuration or the OLAP Option enabled.
SQL> select parameter, value from v$option where parameter='OLAP';
You should see OLAP TRUE.
3) Be sure that the RDBMS 10.1.0.4 patch set has been completely installed. Users often miss the required Post-Installation Steps such as running catpatch.sql.
SQL> select comp_name, version, status from dba_registry;
You should see VALID and 10.1.0.4.0 for the OLAP components.
4) The Oracle Database must have the compatibility mode of 10.1 to use the Model View as it relies on the unique features found in Oracle Database 10g.
SQL> select name, value, description from v$parameter where name ='compatible';
You should see 10.1, not 9.2 or earlier.
5) Please refer to the patchnote.htm that is bundled with 10.1.0.4.0 patch set. Only you are aware of what type of database configuration you have. You will want to pay close attention to "7.2.1.3 Set the SHARED_POOL_SIZE and JAVA_POOL_SIZE Initialization Parameters" and "7.2.2 Upgrade the Release 10.1 Database".
Basically, I believe you have missed these required steps after installing the 10.1.0.4.0 patch set from the OUI: (pasted from the patchnote.htm)
For the full discussion please refer to this link:
Re: Error trying to Analytic Workspace using latest version AWM 10.1.0.4
Hope this helps
Keith
Oracle Business Intelligence Product Management
BI on Oracle: http://www.oracle.com/bi/
BI on OTN: http://www.oracle.com/technology/products/bi/
BI Beans http://www.oracle.com/technology/products/bib/index.html
Discoverer: http://www.oracle.com/technology/products/discoverer/
BI Software: http://www.oracle.com/technology/software/products/ias/devuse.html
Documentation: http://www.oracle.com/technology/documentation/appserver1012.html
BI Samples: http://www.oracle.com/technology/products/bi/samples/
Blog: http://oraclebi.blogspot.com/

Creating an Analytic Workspace

Hi,
i want to create an analytic Workspace without the AWM, but I want to see the Dimensions Cubes, etc what I create in the AWM. I Work with the AWM 10.2.0.3.0. What packages must I use for it? Someone say I must use the cwm2 and the dbms package an otherone say that I must use the AW/XML package.
Give it a Example for Creating an AWM??
Thanks

If you want to create the AW without manually sitting in front of the AWM, Oracle prefers you to use the AWXML and AWAction packages in Java. If you have the AWM installed on your machine, you have the jar files you need in the AWM install directory. Download JDEV and try to load and compile this example program as a way to start learning the library.
package oracle.olapi.examples;
import oracle.AWAction.BuildDatabase;
import oracle.AWAction.Interaction;
import oracle.AWXML.AggregationDefinition;
import oracle.AWXML.AggregationHierarchySpecification;
import oracle.AWXML.Attribute;
import oracle.AWXML.AttributeProjection;
import oracle.AWXML.AttributeSourceExpression;
import oracle.AWXML.AW;
import oracle.AWXML.AWConnection;
import oracle.AWXML.Cube;
import oracle.AWXML.CubeDimensionSourceExpression;
import oracle.AWXML.CubeDimRef;
import oracle.AWXML.CubeMapGroup;
import oracle.AWXML.Dimension;
import oracle.AWXML.DimensionKeySourceExpression;
import oracle.AWXML.DimensionMapGroup;
import oracle.AWXML.DimensionMemberExpression;
import oracle.AWXML.HierarchicalParentSourceExpression;
import oracle.AWXML.Hierarchy;
import oracle.AWXML.HierarchyLevelAssociation;
import oracle.AWXML.Level;
import oracle.AWXML.Measure;
import oracle.AWXML.MeasureFolder;
import oracle.AWXML.MeasureSourceExpression;
import oracle.AWXML.PreComputeClause;
import oracle.AWXML.SourceColumn;
import oracle.express.spl.SPLExecutor;
import oracle.jdbc.OracleConnection;
import java.io.File;
import java.io.FileWriter;
import java.sql.DriverManager;
import java.sql.ResultSet;
import java.sql.SQLException;
import java.sql.Statement;
import java.util.Iterator;
import java.util.Properties;
import java.util.StringTokenizer;
import java.util.Vector;
* Creates an analytic workspace based on the Global schema and populates
* the analytic workspace with data from the tables of that relational schema.
* Before creating the analytic workspace, the program deletes an analytic
* workspace of the same name if it already exists.
* The program generates a log file and it creates a file that records the
* creation of the Oracle OLAP Analytic Workspace Java API objects as an XML string.
* This program requires the Global schema, which is available on the Oracle
* Technology Network at
* http://www.oracle.com/technology/products/bi/olap/olap.html
* To download the sample schema, in the Documentation section see Sample
* Schemas for Documentation.
* To run this program, use the following command-line arguments, where
* server_name is the server on which the Oracle Database is running,
* port is the number of the port on which Oracle OLAP is listening,
* and sid is the system identifier (SID) of the database instance:
* -conn server_name:port:sid -user global_aw -password global_aw
* Instead of the -conn argument, you could substitute a -url argument
* of the following form:
* -url jdbc:oracle:thin:@server_name:port:sid
* An example of the command-line arguments is the following:
* -conn myOracleServer:1521:orcl -user global_aw -password global_aw
public class BuildAWExample extends BaseExample
public static AWConnection awConnection;
private Interaction curInteraction;
// The elements in the _keys Vector are the relational key columns to which
// a Level is mapped.
Vector _keys = new Vector(0);
// The elements in the _cols Vector are the relational columns to which
// the attributes for a Level are mapped.
Vector _cols = new Vector(0);
// The elements in the _levels Vector are the Level objects for specifying
// the levels of a hierarchy.
Vector _levels = new Vector(0);
// The elements in the _levColumns Vector are the relation columns to which
// the levels of the hierarchy are mapped.
Vector _levColumns = new Vector(0);
Vector _dimList = new Vector(0);
Vector _measures = new Vector(0);
Vector _measCols = new Vector(0);
// File name for writing the XML string.
String xmlStr = "buildAWEx.xml";
// File for AW build log.
String xmlBldStr = "buildAWEx.log";
* Constructor.
public void BuildAWExample()
* Creates the top-level objects for the analytic workspace and calls methods
* that create the lower-level objects.
* Writes the analytic workspace objects to an XML string.
* Builds the analytic workspace framework and populates the analytic
* workspace with data.
* Connects to the Oracle Database instance, retrieves information
* about the construction of the analytic workspace, and writes the
* information to a log file.
* Finally, closes the connection to the database.
public void run() throws Exception
// Get the command line arguments that are stored in the Properties object.
String connection = getConnectionProperty(props);
String user = props.getProperty("user");
String password = props.getProperty("password");
// Create the AWConnection.
try
System.out.println("Connecting to " + connection + ".");
awConnection = new AWConnection(user, password, connection);
catch(Exception e)
System.out.println("Error connecting to " + connection + ".\n" + e);
// Specify a name for the analytic workspace.
String awName = "GLOBALAW";
// Delete the analytic workspace if it already exists.
deleteExistingAW(awConnection, user, awName);
// Create an AW object and give it a name.
AW globalAW = new AW();
globalAW.setName(awName);
// Create Dimension objects, and pass each Dimension to a method that
// creates Attribute, Hierarchy, and Level objects for it.
// Create the TIME_AW Dimension and set names for the object.
Dimension timeDim = globalAW.createDimension();
timeDim.setName("TIME_AW");
timeDim.setShortName("TIME_AW");
timeDim.setLongName("TIME_AW dimension");
timeDim.setIsTime(true);
// Create the Attribute, Level, and Hierarchy objects for the Dimension.
this.createTimeDim(timeDim);
// Get the detail level to use when creating a Cube.
Vector timelevels = timeDim.getLevels();
Level monthLevel = (Level)_time_levels.elementAt(0);
// Create the CUSTOMER_AW Dimension and set names for the object.
Dimension customerDim = globalAW.createDimension();
customerDim.setName("CUSTOMER_AW");
customerDim.setShortName("CUSTOMER_AW");
customerDim.setLongName("CUSTOMER_AW dimension");
// Create the Attribute, Level, and Hierarchy objects for the Dimension.
this.createCustomerDim(customerDim);
// Get the detail level to use when creating a Cube.
Vector customerDim_levels = customerDim.getLevels();
Level shipToLevel = (Level)customerDim_levels.elementAt(0);
// Create the PRODUCT_AW Dimension and set names for the object.
Dimension productDim = globalAW.createDimension();
productDim.setName("PRODUCT_AW");
productDim.setShortName("PRODUCT_AW");
productDim.setLongName("PRODUCT_AW Dimension");
// Create the Attribute, Level, and Hierarchy objects for the Dimension.
this.createProductDim(productDim);
// Get the detail level to use when creating a Cube.
Vector productDim_levels = productDim.getLevels();
Level itemLevel = (Level)productDim_levels.elementAt(0);
// Create the CHANNEL_AW Dimension and set names for the object.
Dimension channelDim = globalAW.createDimension();
channelDim.setName("CHANNEL_AW");
channelDim.setShortName("CHANNEL_AW");
channelDim.setLongName("CHANNEL_AW dimension");
// Create the Attribute, Level, and Hierarchy objects for the Dimension.
this.createChannelDimension(channelDim);
// Get the detail level, which is shared by all dimension hierarchies,
// to use when creating a Cube.
Vector channellevels = channelDim.getLevels();
Level channelLevel = (Level)_channel_levels.elementAt(0);
// Create the UNITS_CUBE_AW Cube and the measures to associate with it.
this.clearCubeMapVectors();
Cube unitsCube = globalAW.createCube();
unitsCube.setName("UNITS_CUBE_AW");
// Add the dimensions to the _dimList Vector.
_dimList.add(timeDim);
_dimList.add(customerDim);
_dimList.add(productDim);
_dimList.add(channelDim);
// Specify the dimensions for the Cube.
this.associateCubeDimensions(unitsCube, _dimList);
// Create an aggregation map for the Cube.
this.precomputeNA(unitsCube, "AGGMAP_UC");
// Create a Measure for the quantities of units sold.
Measure units = unitsCube.createMeasure();
units.setName("UNITS_AW");
units.setShortName("UNITS_AW");
units.setLongName("UNITS_AW measure");
units.setDataType("NUMBER");
// Add the Measure to the _measures Vector.
_measures.add(units);
// Add the column of the Global schema relational table to the
// _measCols Vector.
measCols.add("GLOBAL.UNITSHISTORY_FACT.UNITS");
// Create a Measure for the monetary amount of units sold.
Measure sales = unitsCube.createMeasure();
sales.setName("SALES_AW");
sales.setShortName("SALES_AW");
sales.setLongName("SALES_AW measure");
sales.setDataType("NUMBER");
_measures.add(sales);
_measCols.add("GLOBAL.UNITS_HISTORY_FACT.SALES");
// Add the detail levels for the dimensions to the _levels Vector and
// the relational columns for the levels to the _cols Vector.
_levels.add(monthLevel);
_cols.add("GLOBAL.UNITS_HISTORY_FACT.MONTH_ID");
_levels.add(shipToLevel);
_cols.add("GLOBAL.UNITS_HISTORY_FACT.SHIP_TO_ID");
_levels.add(itemLevel);
_cols.add("GLOBAL.UNITS_HISTORY_FACT.ITEM_ID");
_levels.add(channelLevel);
_cols.add("GLOBAL.UNITS_HISTORY_FACT.CHANNEL_ID");
// Map the columns of the relational tables to the dimensions and measures
// of the analytic workspace Cube.
this.createCubeMap(unitsCube, _levels, _cols, _measures, _measCols);
// Create the PRICE_COST_CUBE_AW Cube and the measures to associate with it.
this.clearCubeMapVectors();
Cube priceCostCube = globalAW.createCube();
priceCostCube.setName("PRICE_COST_CUBE_AW");
_dimList.add(productDim);
_dimList.add(timeDim);
this.associateCubeDimensions(priceCostCube, _dimList);
this.precomputeNA(priceCostCube, "AGGMAP_PCC");
// Create a Measure for unit prices.
Measure price = priceCostCube.createMeasure();
price.setName("UNIT_PRICE_AW");
price.setShortName("UNIT_PRICE_AW");
price.setLongName("UNIT_PRICE_AW measure");
price.setDataType("NUMBER");
_measures.add(price);
_measCols.add("GLOBAL.PRICE_AND_COST_HIST_FACT.UNIT_PRICE");
// Create a Measure for unit costs.
Measure cost = priceCostCube.createMeasure();
cost.setName("UNIT_COST_AW");
price.setShortName("UNIT_COST_AW");
cost.setLongName("UNIT_COST_AW measure");
cost.setDataType("NUMBER");
_measures.add(cost);
_measCols.add("GLOBAL.PRICE_AND_COST_HIST_FACT.UNIT_COST");
_levels.add(itemLevel);
_cols.add("GLOBAL.PRICE_AND_COST_HIST_FACT.ITEM_ID");
_levels.add(monthLevel);
_cols.add("GLOBAL.PRICE_AND_COST_HIST_FACT.MONTH_ID");
this.createCubeMap(priceCostCube, _levels, _cols, _measures, _measCols);
// Create a MeasureFolder and add the measures to it.
// A MeasureFolder appears as an MdmSchema object to an
// Oracle OLAP Java API application.
MeasureFolder measureFolder = globalAW.createMeasureFolder();
measureFolder.setName("GLOBALAW_SCHEMA");
measureFolder.setShortName("GLOBALAW_SCHEMA");
measureFolder.setLongName("GLOBALAW_SCHEMA schema");
measureFolder.addMeasure(units);
measureFolder.addMeasure(sales);
measureFolder.addMeasure(cost);
measureFolder.addMeasure(price);
// Write the XML string for the analytic workspace.
String XML = globalAW.WriteToXML();
try
File xmlFile = new File(xmlStr);
FileWriter xmlout = new FileWriter(xmlFile);
xmlout.write(XML);
xmlout.write("\n");
xmlout.close();
catch (Exception e)
System.out.println("Failure to write XML string to file: " +
e.toString());
// Build the analytic workspace framework.
System.out.println("Building the " + awName + " framework.");
globalAW.Create(awConnection);
globalAW.Commit(awConnection);
System.out.println(awName + " framework built!");
// Populate the analytic workspace with the metadata objects and
// the data from the relational schema.
System.out.println("Populating " + awName + "." );
try
xml_build_global_aw(awName);
catch(Exception e)
System.out.println("The following error occurred while building "
+ awName + ":\n\t" + e.toString());
// Connect to the Oracle Database instance and retrieve information
// about building the analytic workspace.
try
// Create a DriverManager.
DriverManager.registerDriver (new oracle.jdbc.OracleDriver());
// Create a connection to the Oracle Database instance.
OracleConnection o_connection =
(OracleConnection)DriverManager.getConnection("jdbc:oracle:thin:@" +
connection, user, password);
// Get information from the olapsys.xml_load_log table.
String result = null;
String sqlText = "select distinct xml_loadid " +
"from olapsys.xml_load_log " +
"order by xml_loadid desc";
Statement sqlStmt = o_connection.createStatement();
ResultSet rs = sqlStmt.executeQuery(sqlText);
if(rs.next())
// Get the first value.
int loadid = rs.getInt(1);
rs.close();
// Now get the rest of the log without the timestamp for easy diffing.
sqlText = "select SUBSTR(xml_message, 9) xml_message " +
"from olapsys.xml_load_log " +
"where xml_loadid = " + loadid + " " +
"order by xml_loadid, xml_recordid";
rs = sqlStmt.executeQuery(sqlText);
String tempResult;
while(rs.next())
tempResult = rs.getString(1);
if(result == null)
result = tempResult.trim();
else
result = result + "\n" + tempResult.trim();
// Write the information to a file.
try
File xmlBuildLog = new File(xmlBldStr);
FileWriter xmlBldout = new FileWriter(xmlBuildLog);
xmlBldout.write(result);
xmlBldout.write("\n");
xmlBldout.close();
catch (Exception e)
System.out.println("Failure to write XML build log: " + e.toString());
catch(Exception e)
System.out.println("Verifier failure with " + e.toString());
// Close the connection to the database.
awConnection.close();
* Builds the analytic workspace.
public void xml_build_global_aw(String awName)
// Create an Interaction object for building the analytic workspace.
curInteraction = new Interaction();
// Set the AWConnection to use when building the analytic workspace.
curInteraction.setConnection(awConnection);
// Create an BuildDatabase object.
BuildDatabase myBuild =
(BuildDatabase)curInteraction.createAction("BUILDDATABASE");
// Set the name of the analytic workspace.
myBuild.setAWName(awName);
// Specify not running solves when building the database.
myBuild.setRunSolve(false);
// Build the analytic workspace.
myBuild.Execute();
* Creates Attribute, Level, and Hierarchy objects for the Time Dimension.
public void createTimeDim(Dimension timeDim)
// Indicate that the primary key of the dimension table contains the
// lowest-level dimension members.
timeDim.setUseNativeKey(true);
// Create the Long and Short Description Attribute objects for the Dimension.
Attribute timeLDAttr = createLongDescAttr(timeDim);
Attribute timeSDAttr = createShortDescAttr(timeDim);
// Create the End_Date and Time_Span Attribute objects.
Attribute timeEndDateAttr = timeDim.createAttribute();
timeEndDateAttr.setName("End_Date");
timeEndDateAttr.setClassification("END_DATE");
Attribute timeTimeSpanAttr = timeDim.createAttribute();
timeTimeSpanAttr.setName("Time_Span");
timeTimeSpanAttr.setClassification("TIME_SPAN");
// Create the Level objects for the Dimension.
// Create the detail level, MONTH_AW.
Level monthLevel = timeDim.createLevel();
monthLevel.setName("MONTH_AW");
monthLevel.setShortName("MONTH_AW");
monthLevel.setLongName("MONTH_AW level");
// Create AttributeProjection objects for the attributes for the
// MONTH_AW Level.
this.setupAttributeProjection(monthLevel, "Long Description", timeLDAttr);
this.setupAttributeProjection(monthLevel, "Short Description", timeSDAttr);
this.setupAttributeProjection(monthLevel, "End Date", timeEndDateAttr);
this.setupAttributeProjection(monthLevel, "Time Span", timeTimeSpanAttr);
this.clearLevelMapVectors();
_keys.add("GLOBAL.TIME_DIM.MONTH_ID");
_cols.add("GLOBAL.TIME_DIM.MONTH_DSC"); // Long description
_cols.add("GLOBAL.TIME_DIM.MONTH_DSC"); // Short description
_cols.add("GLOBAL.TIME_DIM.MONTH_END_DATE");
_cols.add("GLOBAL.TIME_DIM.MONTH_TIMESPAN");
this.createLevelMap(monthLevel, _keys,_cols);
// Create the QUARTER_AW Level.
Level quarterLevel = timeDim.createLevel();
quarterLevel.setName("QUARTER_AW");
quarterLevel.setShortName("QUARTER_AW");
quarterLevel.setLongName("QUARTER_AW level");
// Create AttributeProjection objects for the attributes for the
// QUARTER_AW Level.
this.setupAttributeProjection(quarterLevel, "Long Description",
timeLDAttr);
this.setupAttributeProjection(quarterLevel, "Short Description",
timeSDAttr);
this.setupAttributeProjection(quarterLevel, "End Date", timeEndDateAttr);
this.setupAttributeProjection(quarterLevel, "Time Span", timeTimeSpanAttr);
this.clearLevelMapVectors();
_keys.add("GLOBAL.TIME_DIM.QUARTER_ID");
_cols.add("GLOBAL.TIME_DIM.QUARTER_DSC"); // Long description
_cols.add("GLOBAL.TIME_DIM.QUARTER_DSC"); // Short description
_cols.add("GLOBAL.TIME_DIM.QUARTER_END_DATE");
_cols.add("GLOBAL.TIME_DIM.QUARTER_TIMESPAN");
this.createLevelMap(quarterLevel, _keys, _cols);
// Create the top level, YEAR_AW.
Level yearLevel = timeDim.createLevel();
yearLevel.setName("YEAR_AW");
yearLevel.setShortName("YEAR_AW");
yearLevel.setLongName("YEAR_AW level");
// Create AttributeProjection objects for the attributes for the
// YEAR_AW Level.
this.setupAttributeProjection(yearLevel, "Long Description", timeLDAttr);
this.setupAttributeProjection(yearLevel, "Short Description", timeSDAttr);
this.setupAttributeProjection(yearLevel, "End Date", timeEndDateAttr);
this.setupAttributeProjection(yearLevel, "Time Span", timeTimeSpanAttr);
this.clearLevelMapVectors();
_keys.add("GLOBAL.TIME_DIM.YEAR_ID");
_cols.add("GLOBAL.TIME_DIM.YEAR_DSC"); // Long description
_cols.add("GLOBAL.TIME_DIM.YEAR_DSC"); // Short description
_cols.add("GLOBAL.TIME_DIM.YEAR_END_DATE");
_cols.add("GLOBAL.TIME_DIM.YEAR_TIMESPAN");
this.createLevelMap(yearLevel, _keys, _cols);
// Create the CALENDAR_YEAR_AW Hierarchy.
Hierarchy calendarYearHier = timeDim.createHierarchy();
calendarYearHier.setName("CALENDAR_YEAR_AW");
calendarYearHier.setShortName("CALENDAR_YEAR_AW");
calendarYearHier.setLongName("CALENDAR_YEAR_AW hierarchy");
// Add the Level objects for the Hierarchy, and the columns for them,
// to Vector objects in the hierarcharchical order of the levels,
// with the top level first.
this.clearHierarchyMapVectors();
_levels.add(yearLevel);
_levColumns.add("GLOBAL.TIME_DIM.YEAR_ID");
_levels.add(quarterLevel);
_levColumns.add("GLOBAL.TIME_DIM.QUARTER_ID");
_levels.add(monthLevel);
_levColumns.add("GLOBAL.TIME_DIM.MONTH_ID");
// Specify the levels for the hierarchy and map them to relational columns.
this.createHierarchyMap(calendarYearHier, _levels, _levColumns);
* Create the Long_Description Attribute for a Dimension.
public Attribute createLongDescAttr(Dimension dim)
Attribute ldAttr = dim.createAttribute();
ldAttr.setName("Long_Description");
ldAttr.setClassification("MEMBER_LONG_DESCRIPTION");
return ldAttr;
* Creates Attribute, Hierarchy, and Level objects for the Customer Dimension.
public void createCustomerDim(Dimension customerDim)
// Indicate that the primary key of the dimension table contains the
// lowest-level dimension members.
customerDim.setUseNativeKey(true);
// Create the Long and Short Description Attribute objects for the Dimension.
Attribute customerLDAttr = createLongDescAttr(customerDim);
Attribute customerSDAttr = createShortDescAttr(customerDim);
// Create Level objects for the SHIPMENTS_AW Hierarchy.
// Create the detail level, SHIP_TO_AW.
// This level is in both of the hierarchies of the Customer Dimension.
Level customerShip_ToLevel = customerDim.createLevel();
customerShip_ToLevel.setName("SHIP_TO_AW");
customerShip_ToLevel.setShortName("SHIP_TO_AW");
customerShip_ToLevel.setLongName("SHIP_TO_AW level");
// Create the Long and Short Description AttributeProjection objects for
// SHIP_TO_AW Level.
this.setupAttributeProjection(customerShip_ToLevel, "Long Description",
customerLDAttr);
this.setupAttributeProjection(customerShip_ToLevel, "Short Description",
customerSDAttr);
this.clearLevelMapVectors();
_keys.add("GLOBAL.CUSTOMER_DIM.SHIP_TO_ID");
_cols.add("GLOBAL.CUSTOMER_DIM.SHIP_TO_DSC"); // Long description
_cols.add("GLOBAL.CUSTOMER_DIM.SHIP_TO_DSC"); // Short description
this.createLevelMap(customerShip_ToLevel, _keys, _cols);
// Create the WAREHOUSE_AW level.
Level customerWarehouseLevel = customerDim.createLevel();
customerWarehouseLevel.setName("WAREHOUSE_AW");
customerWarehouseLevel.setShortName("WAREHOUSE_AW");
customerWarehouseLevel.setLongName("WAREHOUSE_AW level");
// Create the Long and Short Description AttributeProjection objects for
// WAREHOUSE_AW Level.
this.setupAttributeProjection(customerWarehouseLevel, "Long Description",
customerLDAttr);
this.setupAttributeProjection(customerWarehouseLevel, "Short Description",
customerSDAttr);
this.clearLevelMapVectors();
_keys.add("GLOBAL.CUSTOMER_DIM.WAREHOUSE_ID");
_cols.add("GLOBAL.CUSTOMER_DIM.WAREHOUSE_DSC"); // Long description
_cols.add("GLOBAL.CUSTOMER_DIM.WAREHOUSE_DSC"); // Short description
this.createLevelMap(customerWarehouseLevel, _keys, _cols);
// Create the REGION_AW Level.
Level custRegionLevel = customerDim.createLevel();
custRegionLevel.setName("REGION_AW");
custRegionLevel.setShortName("REGION_AW");
custRegionLevel.setLongName("REGION_AW level");
// Create the Long and Short Description AttributeProjection objects for
// the REGION_AW Level.
this.setupAttributeProjection(custRegionLevel, "Long Description",
customerLDAttr);
this.setupAttributeProjection(custRegionLevel, "Short Description",
customerSDAttr);
this.clearLevelMapVectors();
_keys.add("GLOBAL.CUSTOMER_DIM.REGION_ID");
_cols.add("GLOBAL.CUSTOMER_DIM.REGION_DSC"); // Long description
_cols.add("GLOBAL.CUSTOMER_DIM.REGION_DSC"); // Short description
this.createLevelMap(custRegionLevel, _keys, _cols);
// Create the top level, TOTAL_CUSTOMER_AW.
Level allCustomersLevel = customerDim.createLevel();
allCustomersLevel.setName("TOTAL_CUSTOMER_AW");
allCustomersLevel.setShortName("TOTAL_CUSTOMER_AW");
allCustomersLevel.setLongName("TOTAL_CUSTOMER_AW level");
// Create the Long and Short Description AttributeProjection objects for
// the ALL_CUSTOMERS_AW Level.
this.setupAttributeProjection(allCustomersLevel, "Long Description",
customerLDAttr);
this.setupAttributeProjection(allCustomersLevel, "Short Description",
customerSDAttr);
this.clearLevelMapVectors();
_keys.add("GLOBAL.CUSTOMER_DIM.TOTAL_CUSTOMER_ID");
_cols.add("GLOBAL.CUSTOMER_DIM.TOTAL_CUSTOMER_DSC"); // Long description
_cols.add("GLOBAL.CUSTOMER_DIM.TOTAL_CUSTOMER_DSC"); // Short description
this.createLevelMap(allCustomersLevel, _keys, _cols);
// Create the SHIPMENTS_AW Hierarchy.
Hierarchy shipmentsHier = customerDim.createHierarchy();
shipmentsHier.setName("SHIPMENTS_AW");
shipmentsHier.setShortName("SHIPMENTS_AW");
shipmentsHier.setLongName("SHIPMENTS_AW hierarchy");
// Add the Level objects for the Hierarchy, and the columns for them,
// to Vector objects in the hierarcharchical order of the levels,
// with the top level first.
this.clearHierarchyMapVectors();
_levels.add(allCustomersLevel);
_levColumns.add("GLOBAL.CUSTOMER_DIM.TOTAL_CUSTOMER_ID");
_levels.add(custRegionLevel);
_levColumns.add("GLOBAL.CUSTOMER_DIM.REGION_ID");
_levels.add(customerWarehouseLevel);
_levColumns.add("GLOBAL.CUSTOMER_DIM.WAREHOUSE_ID");
_levels.add(customerShip_ToLevel);
_levColumns.add("GLOBAL.CUSTOMER_DIM.SHIP_TO_ID");
// Specify the levels for the hierarchy and map them to relational columns.
this.createHierarchyMap(shipmentsHier, _levels, _levColumns);
// Create Level objects for the MARKET_SEGMENT_AW Hierarchy.
// Create the ACCOUNT_AW Level.
Level customerAccountLevel = customerDim.createLevel();
customerAccountLevel.setName("ACCOUNT_AW");
customerAccountLevel.setShortName("ACCOUNT_AW");
customerAccountLevel.setLongName("ACCOUNT_AW level");
// Create the Long and Short Description AttributeProjection objects for
// the ACCOUNT_AW Level.
this.setupAttributeProjection(customerAccountLevel, "Long Description",
customerLDAttr);
this.setupAttributeProjection(customerAccountLevel, "Short Description",
customerSDAttr);
this.clearLevelMapVectors();
_keys.add("GLOBAL.CUSTOMER_DIM.ACCOUNT_ID");
_cols.add("GLOBAL.CUSTOMER_DIM.ACCOUNT_DSC"); // Long description
_cols.add("GLOBAL.CUSTOMER_DIM.ACCOUNT_DSC"); // Short description
this.createLevelMap(customerAccountLevel, _keys, _cols);
// Create the MARKET_SEGMENT_AW Level.
Level customerMktSegmentLevel = customerDim.createLevel();
customerMktSegmentLevel.setName("MARKET_SEGMENT_AW");
customerMktSegmentLevel.setShortName("MARKET_SEGMENT_AW");
customerMktSegmentLevel.setLongName("MARKET_SEGMENT_AW level");
// Create the Long and Short Description AttributeProjection objects for
// the MARKET_SEGMENT_AW Level.
this.setupAttributeProjection(customerMktSegmentLevel, "Long Description",
customerLDAttr);
this.setupAttributeProjection(customerMktSegmentLevel, "Short Description",
customerSDAttr);
this.clearLevelMapVectors();
_keys.add("GLOBAL.CUSTOMER_DIM.MARKET_SEGMENT_ID");
_cols.add("GLOBAL.CUSTOMER_DIM.MARKET_SEGMENT_DSC"); // Long description
_cols.add("GLOBAL.CUSTOMER_DIM.MARKET_SEGMENT_DSC"); // Short description
this.createLevelMap(customerMktSegmentLevel, _keys, _cols);
// Create the top level, TOTAL_MARKET_AW.
Level customerTotalMktLevel = customerDim.createLevel();
customerTotalMktLevel.setName("TOTAL_MARKET_AW");
customerTotalMktLevel.setShortName("TOTAL_MARKET_AW");
customerTotalMktLevel.setLongName("TOTAL_MARKET_AW level");
// Create AttributeProjection objects for the long and short description
// attributes for the TOTAL_MARKET_AW Level.
this.setupAttributeProjection(customerTotalMktLevel, "Long Description",
customerLDAttr);
this.setupAttributeProjection(customerTotalMktLevel, "Short Description",
customerSDAttr);
this.clearLevelMapVectors();
_keys.add("GLOBAL.CUSTOMER_DIM.TOTAL_MARKET_ID");
_cols.add("GLOBAL.CUSTOMER_DIM.TOTAL_MARKET_DSC"); // Long description
_cols.add("GLOBAL.CUSTOMER_DIM.TOTAL_MARKET_DSC"); // Short description
this.createLevelMap(customerTotalMktLevel, _keys, _cols);
// Create the MARKET_SEGMENT_AW Hierarchy.
Hierarchy marketSegmentHier = customerDim.createHierarchy();
marketSegmentHier.setName("MARKET_SEGMENT_AW");
marketSegmentHier.setShortName("MARKET_SEGMENT_AW");
marketSegmentHier.setLongName("MARKET_SEGMENT_AW hierarchy");
// Add the Level objects for the Hierarchy, and the columns for them,
// to Vector objects in the hierarcharchical order of the levels,
// with the top level first.
this.clearHierarchyMapVectors();
_levels.add(customerTotalMktLevel);
_levColumns.add("GLOBAL.CUSTOMER_DIM.TOTAL_MARKET_ID");
_levels.add(customerMktSegmentLevel);
_levColumns.add("GLOBAL.CUSTOMER_DIM.MARKET_SEGMENT_ID");
_levels.add(customerAccountLevel);
_levColumns.add("GLOBAL.CUSTOMER_DIM.ACCOUNT_ID");
_levels.add(customerShip_ToLevel);
_levColumns.add("GLOBAL.CUSTOMER_DIM.SHIP_TO_ID");
// Specify the levels for the hierarchy and map them to relational columns.
this.createHierarchyMap(marketSegmentHier, _levels, _levColumns);
* Creates Attribute, Level, and Hierarchy objects for the Product Dimension.
public void createProductDim(Dimension productDim)
// Indicate that the primary key of the dimension table contains the
// lowest-level dimension members.
productDim.setUseNativeKey(true);
// Create the Attribute objects for the Dimension.
Attribute packageAttr = productDim.createAttribute();
packageAttr.setName("PACKAGE_AW");
packageAttr.setClassification("USER");
Attribute buyerAttr = productDim.createAttribute();
buyerAttr.setName("BUYER_AW");
buyerAttr.setClassification("USER");
Attribute mktMngrAttr = productDim.createAttribute();
mktMngrAttr.setName("MARKETING_MANAGER_AW");
mktMngrAttr.setClassification("USER");
Attribute productLDAttr = createLongDescAttr(productDim);
Attribute productSDAttr = createShortDescAttr(productDim);
// Create the detail level, ITEM_AW.
Level itemLevel = productDim.createLevel();
itemLevel.setName("ITEM_AW");
itemLevel.setShortName("ITEM_AW");
itemLevel.setLongName("ITEM_AW level");
// Create AttributeProjection objects for the attributes for the
// ITEM_AW Level.
this.setupAttributeProjection(itemLevel, "PACKAGE_AW", packageAttr);
this.setupAttributeProjection(itemLevel, "BUYER_AW", buyerAttr);
this.setupAttributeProjection(itemLevel, "MARKETING_MANAGER_AW", mktMngrAttr);
this.setupAttributeProjection(itemLevel, "Long Description", productLDAttr);
this.setupAttributeProjection(itemLevel, "Short Description", productSDAttr);
this.clearLevelMapVectors();
_keys.add("GLOBAL.PRODUCT_DIM.ITEM_ID");
_cols.add("GLOBAL.PRODUCT_DIM.ITEM_PACKAGE_ID");
_cols.add("GLOBAL.PRODUCT_DIM.ITEM_BUYER");
_cols.add("GLOBAL.PRODUCT_DIM.ITEM_MARKETING_MANAGER");
_cols.add("GLOBAL.PRODUCT_DIM.ITEM_DSC"); // Long description
_cols.add("GLOBAL.PRODUCT_DIM.ITEM_DSC"); // Short description
this.createLevelMap(itemLevel, _keys,_cols);
// Create the FAMILY_AW level.
Level familyLevel = productDim.createLevel();
familyLevel.setName("FAMILY_AW");
familyLevel.setShortName("FAMILY_AW");
familyLevel.setLongName("FAMILY_AW level");
// Create AttributeProjection objects for the attributes for the
// FAMILY_AW Level.
this.setupAttributeProjection(familyLevel, "Long Description",
productLDAttr);
this.setupAttributeProjection(familyLevel, "Short Description",
productSDAttr);
this.clearLevelMapVectors();
_keys.add("GLOBAL.PRODUCT_DIM.FAMILY_ID");
_cols.add("GLOBAL.PRODUCT_DIM.FAMILY_DSC"); // Long description
_cols.add("GLOBAL.PRODUCT_DIM.FAMILY_DSC"); // Short description
this.createLevelMap(familyLevel, _keys,_cols);
// Create the CLASS_AW level.
Level classLevel = productDim.createLevel();
classLevel.setName("CLASS_AW");
classLevel.setShortName("CLASS_AW");
classLevel.setLongName("CLASS_AW level");
// Create AttributeProjection objects for the attributes for the
// CLASS_AW Level.
this.setupAttributeProjection(classLevel, "Long Description",
productLDAttr);
this.setupAttributeProjection(classLevel, "Short Description",
productSDAttr);
this.clearLevelMapVectors();
_keys.add("GLOBAL.PRODUCT_DIM.CLASS_ID");
_cols.add("GLOBAL.PRODUCT_DIM.CLASS_DSC"); // Long description
_cols.add("GLOBAL.PRODUCT_DIM.CLASS_DSC"); // Short description
this.createLevelMap(classLevel, _keys,_cols);
// Create the top level, TOTAL_PRODUCT_AW.
Level totalProductLevel = productDim.createLevel();
totalProductLevel.setName("TOTAL_PRODUCT_AW");
totalProductLevel.setShortName("TOTAL_PRODUCT_AW");
totalProductLevel.setLongName("TOTAL_PRODUCT_AW level");
// Create AttributeProjection objects for the attributes for the
// TOTAL_PRODUCT_AW Level.
this.setupAttributeProjection(totalProductLevel, "Long Description",
productLDAttr);
this.setupAttributeProjection(totalProductLevel, "Short Description",
productSDAttr);
this.clearLevelMapVectors();
_keys.add("GLOBAL.PRODUCT_DIM.TOTAL_PRODUCT_ID");
_cols.add("GLOBAL.PRODUCT_DIM.TOTAL_PRODUCT_DSC"); // Long description
_cols.add("GLOBAL.PRODUCT_DIM.TOTAL_PRODUCT_DSC"); // Short description
this.createLevelMap(totalProductLevel, _keys,_cols);
// Create the PRODUCT_PRIMARY_AW Hierarchy.
Hierarchy prodPrimaryHier = productDim.createHierarchy();
prodPrimaryHier.setName("PRODUCT_PRIMARY_AW");
prodPrimaryHier.setShortName("PRODUCT_PRIMARY_AW");
prodPrimaryHier.setLongName("PRODUCT_PRIMARY_AW level");
// Add the Level objects for the Hierarchy, and the columns for them,
// to Vector objects in the hierarcharchical order of the levels,
// with the top level first.
this.clearHierarchyMapVectors();
_levels.add(totalProductLevel);
_levColumns.add("GLOBAL.PRODUCT_DIM.TOTAL_PRODUCT_ID");
_levels.add(classLevel);
_levColumns.add("GLOBAL.PRODUCT_DIM.CLASS_ID");
_levels.add(familyLevel);
_levColumns.add("GLOBAL.PRODUCT_DIM.FAMILY_ID");
_levels.add(itemLevel);
_levColumns.add("GLOBAL.PRODUCT_DIM.ITEM_ID");
// Specify the levels for the hierarchy and map them to relational columns.
this.createHierarchyMap(prodPrimaryHier, _levels, _levColumns);
* Creates Attribute, Level, and Hierarchy objects for the Channel Dimension.
public void createChannelDimension(Dimension channelDim)
// Indicate that the primary key of the dimension table contains the
// lowest-level dimension members.
channelDim.setUseNativeKey(true);
// Create the Long and Short Description Attribute objects for the Dimension.
Attribute channelLDAttr = createLongDescAttr(channelDim);
Attribute channelSDAttr = createShortDescAttr(channelDim);
// Create the Level objects for the Dimension.
// Create the detail level, CHANNEL_AW.
Level channelLevel = channelDim.createLevel();
channelLevel.setName("CHANNEL_AW");
channelLevel.setShortName("CHANNEL_AW");
channelLevel.setLongName("CHANNEL_AW level");
// Create AttributeProjection objects for the long and short description
// attributes for the CHANNEL_AW Level.
this.setupAttributeProjection(channelLevel, "Long Description",
channelLDAttr);
this.setupAttributeProjection(channelLevel, "Short Description",
channelSDAttr);
this.clearLevelMapVectors();
_keys.add("GLOBAL.CHANNEL_DIM.CHANNEL_ID");
_cols.add("GLOBAL.CHANNEL_DIM.CHANNEL_DSC"); // Long description
_cols.add("GLOBAL.CHANNEL_DIM.CHANNEL_DSC"); // Short description
this.createLevelMap(channelLevel, _keys, _cols);
// Create the top level, ALL_CHANNELS_AW.
Level allChannelsLevel = channelDim.createLevel();
allChannelsLevel.setName("TOTAL_CHANNEL_AW");
allChannelsLevel.setShortName("TOTAL_CHANNEL_AW");
allChannelsLevel.setLongName("TOTAL_CHANNEL_AW level");
// Create the Long and Short Description AttributeProjection objects for
// the TOTAL_CHANNEL_AW Level.
this.setupAttributeProjection(allChannelsLevel, "Long Description",
channelLDAttr);
this.setupAttributeProjection(allChannelsLevel, "Short Description",
channelSDAttr);
this.clearLevelMapVectors();
// The order of the elements in the _cols Vector depends on the order
// in which the attributes are created.
// Columns in the relational tables are specified in the form
// user.tablename.column
_keys.add("GLOBAL.CHANNEL_DIM.TOTAL_CHANNEL_ID");
_cols.add("GLOBAL.CHANNEL_DIM.TOTAL_CHANNEL_DSC"); // Long description
_cols.add("GLOBAL.CHANNEL_DIM.TOTAL_CHANNEL_DSC"); // Short description.
this.createLevelMap(allChannelsLevel, _keys, _cols);
// Create the CHANNEL_PRIMARY_AW Hierarchy.
Hierarchy chanRollupHier = channelDim.createHierarchy();
chanRollupHier.setName("CHANNEL_PRIMARY_AW");
chanRollupHier.setShortName("CHANNEL_PRIMARY_AW");
chanRollupHier.setLongName("CHANNEL_PRIMARY_AW hierarchy");
// Add the Level objects for the Hierarchy, and the columns for them,
// to Vector objects in the hierarcharchical order of the levels,
// with the top level first.
this.clearHierarchyMapVectors();
_levels.add(allChannelsLevel);
_levColumns.add("GLOBAL.CHANNEL_DIM.TOTAL_CHANNEL_ID");
_levels.add(channelLevel);
_levColumns.add("GLOBAL.CHANNEL_DIM.CHANNEL_ID");
// Specify the levels for the hierarchy and map them to relational columns.
this.createHierarchyMap(chanRollupHier, _levels, _levColumns);
* Create the Short_Description Attribute for a Dimension.
public Attribute createShortDescAttr(Dimension dim)
Attribute sdAttr = dim.createAttribute();
sdAttr.setName("Short_Description");
sdAttr.setClassification("MEMBER_SHORT_DESCRIPTION");
return sdAttr;
* Creates an AttributeProjection for a Level and sets the name and the
* Attribute to project onto the Level.
public void setupAttributeProjection(Level _lev, String _name, Attribute _attr)
AttributeProjection _ap = _lev.createAttributeProjection();
_ap.setName(_name);
_ap.setAttribute(_attr);
* Creates the associations between Level objects and a Hierarchy.
public void createHierarchyMap(Hierarchy _hier, Vector _levels, Vector columns)
int i = 0;
for(Iterator _lev = _levels.iterator(); _lev.hasNext();)
Level _curLev = (Level)_lev.next();
HierarchyLevelAssociation _hla = _hier.createHierarchyLevelAssociation();
_hla.setLevel(_curLev);
DimensionMapGroup _dmg = _hla.createSourceDimensionMapGroup();
DimensionKeySourceExpression _dkse = _dmg.CreateKeyMap();
SourceColumn _levColumn = _dkse.CreateSourceColumn();
_levColumn.setColumn((String)columns.elementAt(i));
// The first level has no parent.
// Each subsequent level does have a parent.
// The first element in the Vector must be the top-most level.
if (i > 0)
HierarchicalParentSourceExpression _hpse = _dmg.CreateParentMap();
SourceColumn _hpsesc = _hpse.CreateSourceColumn();
_hpsesc.setColumn((String)columns.elementAt(i-1));
i++;
* Clears the Vector objects that are used for specifying the Level objects
* in a Hierarchy and for mapping the levels to the columns of a relational
* table.
public void clearHierarchyMapVectors()
_levels.removeAllElements();
_levColumns.removeAllElements();
* Clears the Vector objects that are used for mapping a Level object to the
* columns of a relational table.
public void clearLevelMapVectors()
_keys.removeAllElements();
_cols.removeAllElements();
* Creates a DimensionMapGroup that maps a Level to the columns of
* a relational table.
public void createLevelMap(Level _lev, Vector _keys, Vector _columns)
// Map the keys of the relational table to the level.
DimensionMapGroup _dmg = _lev.createSourceDimensionMapGroup();
DimensionKeySourceExpression _key = _dmg.CreateKeyMap();
for (int y=0; y < _keys.size(); y++)
SourceColumn _keycol = _key.CreateSourceColumn();
_keycol.setColumn((String)_keys.elementAt(y));
// Map the columns of the relational tables or views to the
// AttributeProjection objects.
int i = 0;
for(Iterator attrs = _lev.getAttributes().iterator(); attrs.hasNext();)
AttributeProjection _curAttr = (AttributeProjection)attrs.next();
AttributeSourceExpression _attrMap = _dmg.CreateAttributeMap();
_attrMap.setTargetObject(_curAttr);
SourceColumn _attrCol = _attrMap.CreateSourceColumn();
_attrCol.setColumn((String)_columns.elementAt(i));
i++;
* Clears the Vector objects that are used for specifying the Level objects
* in a Hierarchy and for mapping the levels to the columns of a relational
* table.
public void clearCubeMapVectors()
_measures.removeAllElements();
_measCols.removeAllElements();
_levels.removeAllElements();
_cols.removeAllElements();
_dimList.removeAllElements();
* Specifies the dimensions for a Cube.
public void associateCubeDimensions(Cube _cube, Vector _dimList)
for (int i=0; i < _dimList.size(); i++)
CubeDimRef _cdr = _cube.createCubeDimRef();
Dimension _dim = (Dimension)_dimList.elementAt(i);
_cdr.setDimension(_dim);
* Maps the columns of the relational tables to the dimensions and measures
* of the analytic workspace Cube.
public void createCubeMap(Cube _cube, Vector _levels, Vector _columns,
Vector _measures, Vector _measCols)
CubeMapGroup _cmg = _cube.createSourceCubeMapGroup();
// Create the primary key in the fact table.
for (int y=0; y < _levels.size(); y++)
CubeDimensionSourceExpression _cdse = _cmg.CreateKeyMap();
_cdse.addLevel((Level)_levels.elementAt(y));
// Loop through the associated comma delimited
// FKey columns in the fact table.
StringTokenizer _st =
new StringTokenizer((String)_columns.elementAt(y), "," );
while (_st.hasMoreTokens())
SourceColumn _keycol = _cdse.CreateSourceColumn();
_keycol.setColumn(_st.nextToken());
for(int x=0; x < _measures.size(); x++)
Measure curMeasure = (Measure)_measures.elementAt(x);
curMeasure.setAutoSolve("NO_AUTO_SOLVE");
String curMeascol = (String)_measCols.elementAt(x);
MeasureSourceExpression _measMap = _cmg.CreateAttributeMap();
_measMap.setTargetObject(curMeasure);
SourceColumn _meascol = _measMap.CreateSourceColumn();
_meascol.setColumn(curMeascol);
* Specifies excluding NA values when computing values while building the
* analytic workspace.
public void precomputeNA(Cube _cube, String _aggdef_name)
// Rename the default aggregation definition that was implicitly created.
AggregationDefinition _aggdef =_cube.getDefaultAggregationDefinition();
_aggdef.setName(_aggdef_name);
// Remove the default calculation specification.
_aggdef.getCalculationSpecification().clear();
Vector _dimrefs = _cube.getCubeDimRefs();
for (Iterator _d = _dimrefs.iterator(); _d.hasNext();)
AggregationHierarchySpecification _aggHierSpec =
_aggdef.createAggregationHierarchySpecification();
CubeDimRef _dimref = (CubeDimRef)_d.next();
Dimension _dim = _dimref.getDimension();
_aggHierSpec.setDimension(_dim);
PreComputeClause _precompute_clause =
_aggHierSpec.createPreComputeClause();
DimensionMemberExpression _dimMemExp =
_precompute_clause.createDimensionMemberExpression();
_dimMemExp.setExpression("ALL");
_dimMemExp.setExpressionType("EXCLUDE");
* Deletes the analytic workspace if it already exists.
private void deleteExistingAW(AWConnection awConnection, String user,
String awName)
try
OracleConnection conn = (OracleConnection)
awConnection.getSQLConnection();
SPLExecutor splExec = new SPLExecutor(conn);
splExec.initialize();
try
System.out.println("Deleting " + user + "." + awName + " if it exists.");
splExec.executeCommand("aw delete " + user + "." + awName);
// System.out.println("Deleted " + user + "." + awName + ".");
catch(Exception e)
// System.out.println("The " + user + "." + awName + " analytic workspace "
// + "either did not exist or it could not be deleted.");
catch(SQLException e)
System.out.println("Could not initialize the SPL executor. " + e);
private String getConnectionProperty(Properties props)
String conn = props.getProperty("conn");
if (conn == null)
String url = props.getProperty("url");
if (url.indexOf("@") > 0)
conn = url.substring((url.lastIndexOf("@") + 1), url.length());
props.put("conn", conn);
return conn;
public static void main(String[] args)
new BuildAWExample().execute(args);
}

AWM-Importing Analytical workspace thru XML

Need help in Oracle:AWM
I have been trying to load XML file to import the Analytical work space with DML statements.
I am not able to import AWS on server.It gives following error
Success <Line 1, Column 1>: XML-20108: (Fatal Error) Start of root element expected.
ORA-34684: All of your attached analytic workspaces are read-only.
Following is the code got from oracle site:
CREATE OR REPLACE PROCEDURE LOAD_AWM (DIR_NAME VARCHAR, XML_NAME VARCHAR) AS
clb CLOB;
infile BFILE;
dname varchar2(500);
sql_text varchar2(200);
BEGIN
DBMS_OUTPUT.PUT_LINE('started');
-- Create a temporary clob
DBMS_LOB.CREATETEMPORARY(clb, TRUE,10);
-- Create a BFILE use BFILENAME function
infile := BFILENAME(DIR_NAME,XML_NAME);
-- Open the BFILE
DBMS_LOB.fileopen(infile, dbms_lob.file_readonly);
DBMS_OUTPUT.PUT_LINE('File open...');
-- Load temporary clob from the BFILE
DBMS_LOB.LOADFROMFILE(clb,infile,DBMS_LOB.LOBMAXSIZE, 1, 1);
DBMS_OUTPUT.PUT_LINE('File load');
-- Close the BFILE
DBMS_LOB.fileclose(infile);
DBMS_OUTPUT.PUT_LINE('File close');
-- Create the GLOBAL analytic workspace
DBMS_OUTPUT.PUT_LINE(DBMS_AW_XML.execute(clb));
DBMS_AW.AW_UPDATE;
DBMS_OUTPUT.PUT_LINE('Awm Update.');
COMMIT;
-- Free the Temporary Clob
DBMS_LOB.FREETEMPORARY(clb);
EXCEPTION
WHEN OTHERS
THEN
DBMS_OUTPUT.PUT_LINE(SQLERRM);
END;
There is no other instance open for which it can throw read-only error.
The XML file is kept in folder on UNIX server which has permissions as drwxrwxr-x
Please help in this issue.

Hi,
iam trying to install oracle 8i in fedora 4 with kernel version 2.6.11 and glibc-2.3.6-3
when iam trying to run ./runinstaller it is giving the following error.
And i want to know whether oracle 8i is supported on fedora 4. Plse tell me what all the linux flavours are supported for oracle 8i and also it is compatable for php4 or php5.
as we are trying to use php with oracle 8i database...!
######## error:
[oracle@localhost linux]$ ./runInstaller
Initializing Java Virtual Machine from ../stage/Components/oracle.swd.jre/1.1.8/1/DataFiles/Expanded/linux/bin/jre. Please wait...
Exception java.lang.NullPointerException occurred..
java.lang.NullPointerException
at sun.awt.motif.MComponentPeer.setFont(MComponentPeer.java:192)
at sun.awt.motif.MFramePeer.<init>(MFramePeer.java:68)
at sun.awt.motif.MToolkit.createFrame(MToolkit.java:137)
at java.awt.Frame.addNotify(Frame.java:196)
at java.awt.Window.show(Window.java:138)
at java.awt.Component.show(Component.java:528)
at java.awt.Component.setVisible(Component.java:490)
at oracle.sysman.oii.oiic.OiicInstaller.main(OiicInstaller.java:419)
Plse help me...!
Thanks in advance..

ORA-34492: Analytic workspace object cubename _STORED does not exist.

I am having issues accessing cube data from a user other than where the AW was built.
Following is what I have done in User-1:
1. Create two AW's in User-1 : AW-1 and AW-2.
2. Create all objects in these two AW's
3. AW-2 is dynamically attached on attaching AW-1 by using PERMIT startup programs. Please refer Attaching multiple AW's
4. Refreshed both AW's to load data
5. ALLCOMPILE - no errors.
6. Created some SQL views on User-1 which basically query the underlying cube views. I also have some queries using the olap_table option.
7. All my querries work fine in User-1. I can access data from AW-1 and AW-2.
However, we give access to the above SQL views through an abstract user: User-abs. In 10g, all we did was grant select privs to all the User-1.AW$ tables and also on all the sql views. This would let User-abs get data from the cubes in User-1.
I am not able to get User-abs to do the same in 11g. We encounter an error mentioning that the workspace object <cubename>_STORED does not exist. The cubename it is referring to exists in AW-2.
I granted select privs on all AW$ tables, dimension views, cube views and the abstracted sql views but the error persists.
I tried searching this forum but could not find any helpful leads. Any help will be greatly appreciated.
Thanks!
Database - 11.2.0.1
AWM - 11.2.0.2.0A

I can think of two possible problems. First, you may not be properly qualifying the owner name when you refer to the object. This can be important when refering to objects owned by other schemas. For example instead of 'my_cube_stored' you would say 'user-1.aw-2!my_cube_stored'. You should also be careful about the order in which you attach the AWs. Do you want AW-2 attached first or last? Use the LAST keyword on AW ATTACH to control this.
Another possibility is that you have added additional logic to PERMIT_READ over and above the 'aw attach' comand. I was able to recreate the error with the following code in a new AW called TEST_AW in the GLOBAL schema.
DEFINE PERMIT_READ PROGRAM BOOLEAN
PROGRAM
aw attach global.global
show global.global!units_cube_stored
return true
ENDAttaching TEST_AW in RO mode as any user gives me the following error.
ORA-34492: Analytic workspace object GLOBAL.GLOBAL!UNITS_CUBE_STORED does not
exist.
ORA-06512: at "SYS.DBMS_AW", line 93
ORA-06512: at "SYS.DBMS_AW", line 122
ORA-06512: at line 1Here is the documentation for PERMIT_READ
>
PERMIT_READ
A PERMIT_READ program is a program that you can create and that Oracle OLAP checks for by name when an AW ATTACH read-only command executes. Depending on the value returned by the program, Oracle OLAP executes the code within the program after attaching the analytic workspace. Depending on the statements in the permit_read program the user is granted or denied access to specific objects or sets of object values. Within permit_read program, you can specify PERMIT commands that grant or restrict access to individual workspace objects. All of the objects referred to in a given permit_read must exist in the same analytic workspace.
>
Note, especially, the restriction in the last sentence. This means that a PERMIT_READ program in AW1, for example, cannot refer to objects in AW2. So this is why my PERMIT_READ doesn't work. The AUTOGO does not have these restrictions, but as we know from the forum post you cited, AUTOGO is broken in 11.2.0.1. You can move forward to 11.2.0.2 where AUTOGO is fixed, but there is workaround, which is to add a PERMIT_READ program to the second AW to do the work. For example, if I add this PERMIT_READ to GLOBAL and remove the 'show' command from the PERMIT_READ in TEST_AW, then everything works as expected.
DEFINE PERMIT_READ PROGRAM BOOLEAN
PROGRAM
if aw(attached 'test_aw')
then do
show global.global!units_cube_stored
doend
return true
END

Oracle 10g Analytic Workspace Manager 10.1.0.4( where to download?)

Guys,
I'm looking for a link to install Oracle 10g Analytic Workspace Manager 10.1.0.4.
Can someone help me with the link?.
Thanks,
Bhagat

Thank you, we have this :
SELECT COMP_NAME, VERSION, STATUS FROM DBA_REGISTRY WHERE COMP_NAME LIKE '%OLAP%';
COMP_NAME VERSION STATUS
OLAP Analytic Workspace 10.2.0.1.0 VALID
Oracle OLAP API 10.2.0.1.0 VALID
OLAP Catalog 10.2.0.1.0 VALID
Is Analytic Workspace Manager installed ? How to know its version ?
Thank you.

Does Analytic Workspace Manager 11.2.0.3.0A work with oracle database 12c?

hello,
i would like to know if AWM 11.2.0.3.0A works against with oracle database 12c in pdb mode or not .
regards
jm

I have attempted to connect 11g versions of AWM to 12c and get this error:
'This version of Analytic Workspace Manager is incompatible with the database instance. The Analytic Workspace Manager version is 11.2.0.3.0 and the database compatible version is 12.1.0.0.0'
So unfortunately it is not compatible, and there is currently no AWM for 12c
I also contacted Oracle support and they wont give me any information about a release date or any information on the xml template specification for 12c.
I guess we will just have to wait till they release a version of AWM that supports 12c...
Laszlo

Is it possible to create relational view on Analytic Workspace in Oracle 9i Release1

Hi All,
We are in the initial stages of Oracle 9i OLAP prototype. Since the current version of BIBeans 2.5 does not work with Release 2 of Oracle 9i OLAP, we are planning to use Oracle 9i OLAP Release 1. So can you please answer the following questions.
1. Is it possible to create relational view on Analytic Workspace(like in Release 2) and populate the OLAP catalog, if so can you give me guidance to get the appropriate user guide. The OLAP DML guide in Release 1 talks about creating OLAP catalog metadata for Analytic Workspace using a metadata locator object.
2, Is it advisable to use Oralce 9i OLAP Release 1? Does the Analytic Workspace and the corresponding BIBeans work in Release 1?
Thank you,
Senthil

Analytic Workspaces (Express/multidimensional data objects and procedures written in
the OLAP DML) are new to Oracle9i OLAP Release 2, you cannot find them in Release 1.
BI Beans will soon (within a week) introduce a version on OTN that will work with Oracle9i OLAP Release 2.

Error installing iTunes 10 on Windows 7 64 Bit

I upgraded to Windows 7 from XP since I changed laptop. I did tried to install iTunes on this new machine (win 7 64 bit Corei7 processor and 4G RAM) but during the installation when the status screen states "Publising Product Information", I'm getting the following error message:
"An error occurred during the installation of assembly 'Microsoft.VC80.CRT,version="8.0.50727.4053",type="win32",publicKeyToken='1fc8b 3b9a1e18e3b",processorarchitecture="x86". Please refer to Help and Support for more information. HRESULT:0x800736FD."
Following this message, the installer reverses the installation process and after a 10-15 minute wait, a screen comes up that says the Itunes installation was complete. Obviously it wasn't but that is what the message says. When you close out of that message, Itunes tries to start and this message pops up:
"Apple Application Support was not found.
Apple Application Support is required to run iTunes. Please uninstall itunes, then install iTunes again.
Error 2"
Any help will be very much appreciated

HRESULT:0x800736FD
It's rarer to see these on Windows 7 than it is on Vista. Somtimes they're a bit easier to deal with on 7, too.
First, head to Windows Update and see if you can update the PC. If you can, and you collect updates without any errors, try another iTunes install.
If you get errors installing Windows Updates, double click on the failed updates in your Update history to bring up a small window containing alphanumeric codes for the erros. Are they also 800736FDs, or are you getting other error codes?

Creating Database Standard Form Analytic Workspaces

Just been looking through the new 9.2.0.4.1 documentation and came across the following. Thought it might be useful.
The 9.2.0.4.1 release of Oracle OLAP introduces a new concept known as �Database Standard Form� Analytic Workspaces. This is a way of constructing analytic workspaces in a standard way such that they can be used by tools such as the Analytic Workspace Manager, the Java OLAP API, and BI Beans.
When analytic workspaces are created from a relational star-schema using the Analytic Workspace Manager, it automatically creates the analytic workspace in standard form as part of the migration process. However, if you�re migrating an Express database to Oracle OLAP, the migrated database has to be processed to be in standard form before it is usable by any of the new Oracle OLAP GUI tools.
If you create an analytic workspace using PL/SQL or the OLAP Worksheet, of course you can create dimensions, variables, relations and so on in any form, just as you can create table structures, joins, views and columns in any form in a relational database. However, the database standard form requirement stipulates that;
Certain objects and properties need to be found in the analytic workspace, that are used by tools such as the Analytic Workspace Manager to perform tasks such as aggregation, data loads, and OLAP API enablement. OLAP DML views (beginning with AW$) need to created in the analytic workspace, to provide metadata and to identify relationships between objects in the analytic workspace. Objects need to be registered in the OLAP Catalog, and these registrations have to be kept in sync so that the OLAP tools are aware of changes to the base objects. Data that is migrated in to an analytic workspace, from a relational star-schema using the Analytic Workspace Manager, is already in database standard form and no further work is needed. However, some work is needed to get migrated Express databases into standard form, and Oracle have provided a utility with the 9.2.0.4.1 release of Oracle OLAP to help accomplish this.
This utility, known as CREATE_DB_STDFORM, is an OLAP DML program that takes existing Oracle Express Objects metadata in a migrated Express database, and uses this to create the additional metadata required to make the analytic workspace �database standard form�.
Once CREATE_DB_STDFORM has been used to create this additional metadata, it can also be used to import data into the workspace either from flat files, or from Oracle tables and views. If you don�t have Express Objects metadata in the Express database, CREATE_DB_STDFORM doesn�t work, and you�ll have to use Oracle Warehouse Builder 9.2 to initially create a relational star-schema that equates to the Express database, then use the OLAP Bridge within OWB to export the data into a database standard form analytic workspace.
CREATE_DB_STDFORM, once run, allows the migrated Express database to be accessed via BI Beans straight afterwards, as it creates all the OLAP Catalog entries required for the OLAP API. If the Express database only contains data at the lowest level (i.e. it hasn�t been rolled up), aggregation wizards in the Analytic Workspace Manager can be used to summarise the data as required.
CREATE_DB_STDFORM doesn�t do everything, however. First of all, you need to have created Oracle Express Objects metadata within the Express database, which is an additional step and not always appropriate for all systems. In addition, you need to create time dimensions in a particular way, which may require the data model to be adjusted to meet this requirement. Lastly, any Express language programs within the Express database may need to be adjusted to remove or change commands that have changed or become obsolete.
The new document, �Oracle OLAP Application Developers Guide Release 9.2.0.4.1�, available on metalink under note 251352.1, details how database standard form works, has code examples, and walks through the migration of the XADEMO Express database to an analytic workspace using database standard form.

In your message, you wrote "Certain objects and properties need to be found ... aware of changes to base objects". A large bit is represented by "...". Question is whether I have any commands or package functions that I can use to set up all the proper objects and relationships to make it have database standard form, short of regressing to a ROLAP star schema and usnig the AWM wizard. I have what appears to be working MOLAP activity, all created at the OLAP worksheet prompt, and loaded with DML program. Do I really have to put that all aside and start with a star schema? No way to put my AW in standard form for OLAP API without this?

Error Installing the SALESTRACK analytic workspace in the OLAPTRAIN schema

Similar Messages

Maybe you are looking for