Oracle BI Hierarchy

Hi All,
i'm comming to Oracle BI from Microsoft Platform. I'm confused.
in microsoft platform to get a business intelligence solution
1- you creates the datawarehouse and make your integration for data by SQL Server Integration Services
2- you creates your OLAP Project by Analysis Services
3- you uses Performance point Application to make dashboards, reports or for planning .you can also use Reporting services to make Reports.
4- also you can build your own application with C# -for example- and coonect to the data warehouse or the olap and do wthat you want
when i came to Oracle BI i get more confusion
there is many many applications and i don't know which one to use. which are the same like microsoft ones.
i have some questions, please help me?
1- what's the job of the OBIEE . is it the same like MS PErformance Point ?? to create dashboards, reports and planning ??
2-is essbase is the same like MS Analysis Services (OLAP Server). ? is it contained IN the OBIEE
3- Oracle DAta Integrator is an independant Application from OBIEE??
if ODI to integrate the data and Essbase is to Analysis Data and OBIEE is to Make Dashboards and Reports
so what' the whole other applications for?
what's hyperion? what's Oracle Publisher???
please help me . i don't want what to download and what applications to use ??
what tutorials or books or documents to read?

Hi All,
Thanks David For Your help
please, when i go to the page to download OBIEE
[http://www.oracle.com/technology/software/products/ias/htdocs/101320bi.html]
i found more appications like
1- Oracle Business Intelligence Applications,
2- Informatica PowerCenter and PowerConnect Adapters
3-Oracle Real-Time Decisions,
4-Oracle Real-Time Decisions Applications,
5- Oracle Business Intelligence Data Warehouse Administration Console
mayyou please tell me what's the role of each one???
also is it essential to download them to start work ang get a complete BI Solution ???
Regards,
Ahmed Salah

Similar Messages

Oracle Tree Hierarchy Query

Hi,
Hoping someone can assist with this query:
I am currently using this query to construct a tree hierarchy, i.e.
SELECT "EMP"."MGR" as "MGR",
        "EMP"."EMPNO" as "EMPNO",
        "EMP"."ENAME" as "ENAME" ,
        (select count(*) from "EMP" "EMP2" where "EMP2"."MGR" = "EMP"."EMPNO") BranchCount
from
"EMP" "EMP"
where
"EMP"."MGR" = :BRANCH_IDUsing this query, I also need to retrieve the LEVEL pseudo-column as well for each record retrieved as I need the LEVEL info for trying to determine at what level of the tree I am at.
I would actually like to incorporate the LEVEL column into the above query - is this possible?
Thanks.
Tony.

SQL> desc test
Name Null? Type
COLUMN1 VARCHAR2(10)
COLUMN2 VARCHAR2(10)
MGR VARCHAR2(10)
SQL> select * from test
2 /
COLUMN1 COLUMN2 MGR
1 a 33
3 i 33
2 g 33
4 b 33
5 c 44
6 d 44
22 e
33 f 22
44 h 22
9 rows selected.
SQL> select column1, column2, mgr, level
2 from test
3 start with mgr = '22'
4 connect by prior column1 = mgr
5 order by level
6 /
COLUMN1 COLUMN2 MGR LEVEL
33 f 22 1
44 h 22 1
6 d 44 2
4 b 33 2
5 c 44 2
3 i 33 2
1 a 33 2
2 g 33 2
8 rows selected.

Security for value based hierarchy + OLAP

Hi,
I am using row-level security mechanism described here: http://www.rittmanmead.com/2012/03/obiee-11g-security-week-row-level-security/
It works well for level based hierarchies... but is there a way to apply it to value based OLAP hierarchy in OBIEE 11.1.1.6?
My case is:
- I have parent-child value based hierarchy representing management structure with various depth.
- of course facts are always linked to leaf members of hierarchy
- I need to apply security at different levels. E.g. Office manager should have access to one/multiple offices information (basically all employees he manage currently + his previous office before he was moved)
- In report I display presentation hierarchy that starts at country level and then manager drill to his offices
- At country level, manager should see a measure aggregate only for his offices (not whole country)
In relational database there is no problem:
- I follow rittman blog
- create session variable that store list of all leaf members of hierarchy (employees) managed by manager
- with OBIEE "Manage"->"Identity" I apply filter on fact table and get right measure aggregates at all levels of hierarchy
Issue for OLAP:
- with OBIEE "Manage"->"Identity" I apply filter on OLAP value based hierarchy
- in case of filter "MY_BMM"."Org Str"."Org Str Key" = VALUEOF(NQ_SESSION."LEAFS_LIST") -> when manager include hierarchy column to report there are no results because hierarchy starts at country level and he have no access to country data
- to workaround it I tried: "MY_BMM"."Org Str"."Org Str Key" = VALUEOF(NQ_SESSION."LEAFS_LIST_AND_ALL_ANCESTORS") -> manager can see all aggregates at country level because he have access to country, and OLAP just use country level aggregate
- IsDescendant("MY_BMM"."Org Str" , VALUEOF(NQ_SESSION."OFFICE_ID")) will work only for single office as we can not use row wise variables here
One solution I can imagine is to create additional level based dimension that have only 2 levels: "All"->"Org Str Leaf". Then apply filter on this "artifitial" dimension. It is not perfect solution to duplicate dimensions only for security purposes... that's why I ask you for advice if you know better way?
Regards,
mudi

Here is an example, how to set security in OBIEE 11.1.1.5 (or future versions) against Oracle OLAP dimensions.
*(1). Create the Oracle OLAP Hierarchy Descendant View against Value-based hierarchy*
These views return a row for each ancestor-descendent relationship in the hierarchy. As you can see how easy it is.
CREATE OR REPLACE VIEW DEPT_DESCENDANTS
AS
SELECT 'DEPT' "DIMENSION", 'DEPTHIER' "HIER", ancestor, descendant
FROM TABLE(OLAP_TABLE('BAWOLAP.BNSOLAP DURATION QUERY', null, 'LIMIT DEPT_HIERLIST TO 'DEPTHIER''',
'DMNS DESCENDANT AS VARCHAR2(60) FROM DEPT
DMNS GID_VAL AS NUMBER FROM ___AW_GID_DIMENSION
MSR ANCESTOR AS VARCHAR2(60) FROM DEPT_FAMILYRELVAL'
where ancestor is not null
*(2). Create the User ACL Tables and Populate with Data*
Create an Access Control list test table by user and Dept. Later this will be populated with production data.
create table user_dept_acls
username varchar2(30),
dept varchar2(60)
insert into user_dept_acls(username, dept) values ('user1', 'GWM');
insert into user_dept_acls(username, dept) values ('user1', 'GT');
insert into user_dept_acls(username, dept) values ('user1', 'SC');
insert into user_dept_acls(username, dept) values ('user2', 'GWM');
insert into user_dept_acls(username, dept) values ('user2', 'GT');
insert into user_dept_acls(username, dept) values ('user3', 'SC');
commit;
*(3). Create an Init Block Connection Pool*
Oracle BI EE requires a separate Connect Pool for Init blocks. It does not allow the default query connection pool to be reused for init blocks. So, we need to create a new init block.
*(4). Create the ACL Session Variables*
These session variables hold the list of all members that the user may access.
Example Session Variable: DEPT_ACL
Init Block: "Init DEPT_ACL"
SQL:
select 'DEPT_ACL', account from user_DEPT_acls where username = ':USER'
union all
select 'DEPT_ACL', descendant
from DEPT_descendants
where ancestor in (select account from user_DEPT_acls where username = ':USER')
union all
select 'DEPT_ACL', ancestor
from DEPT_descendants
where descendant in (select account from user_DEPT_acls where username = ':USER')
The first query block of the init block SQL just selects the members explicitly entered into the ACL table. The second block selects all the descendants of those members from the descendants view. The third block selects all the ancestors to ensure that the user has access to all the members in the drill path starting from the root member.
Make sure that row-wise initialization is checked in the Variable Target section of the init block.
*(5). Add the Data Filters*
In our test case we assigned the data filters to the BIAuthor role, but the filters should be added to whatever role makes the most sense.
Data filter on "BNSGL"."Department":
"BNSGL"."Department"."Dept" = VALUEOF(NQ_SESSION."DEPT_ACL")
*(6). Log in as a Normal User and Query the Hierarchy*
The user can only see to the members to which they are granted access in the ACL table plus all ancestors and descendants of those members.
Drill down to the bottom of the hierarchy.
*(7). Look at the Query Log*
In the nqquery.log we see that the session variable is expanded into an IN list in the physical SQL query. The BI Server breaks the IN list into two IN lists to avoid the Oracle SQL limit of 1,000 items per IN list.
Edited by: Nasar Ali-Khan on Jul 2, 2012 8:14 AM

Hierarchy authorization details show only last level

Hi,
I am facing on a hierarchy problem displayed on the Bex: The hierarchy has 9 levels, e.g. the organisation structure of the company from level 1 to level 9.
I made from the transaction RSSM :
Authorization from the hierarchy i entered for each level from 1 to 9 :
Type of authorisation : 1 (subtree below node)
Hierarchy level       : blank
Validity period       : blank
Node variable default value : blank
I made from the transaction PFCG :
Created a role for the user with the authorization :
Sap Business information warehouse - reporting (RSR)
value : 8055 (company code)
Unique ID for authorization : level_3
I need to authorize the user to execute a querry of his level (exemple level 3) and all the level below him (to the 9th level)
When the query is generated,(the query is using a variable hierarchy ) I get the lowest level displayed and shows only 2 key figures and values.
Any ideas ?
You assistance will be appreciated.
Thong VANNAXAY

Hi,
1007372 wrote:
Hi,
How to get only the last level in Oracle SQL Hierarchy Query?Depending on your requirements:
WHERE   CONNECT_BY_ISLEAF = 1
I hope this answers your question.
If not, post a little sample data (CREATE TABLE and INSERT statements, relevant columns only), and also post the results you want from that data.
Explain, using specific examples, how you get those results from that data.
If you can show what you want to do using commonly available tables (such as scott.emp, which contains a hierarchy), then you don't need to post any sample data; just the results and the explanation.
Always say which version of Oracle you're using (e.g., 11.2.0.2.0). This is always important, but especially so with CONNECT BY queries, because every version since Oracle 7 has had significant improvements in this area.
See the forum FAQ {message:id=9360002}

JDBC with Oracle

As i come from SQL server environment, I am new to Oracle environment. So my newbie question is how do you connect to particular sub-space (inner schema) of main service. For example, the database hierarchy looks like below.
(1) A (Database/Service Name)
----(1.1) X (database or inner schema)
----------(1.1.1) Number of tables belongs to x database
----(1.2) Y (database or inner schema)
---------(1.2.1) Number of tables belongs to y database
The TNS file (tnsname.ora) includes entry for "A" database/service. I use JDBC drive to connect to oracle database.
Connection conObj = DriverManager.getConnection(
"jdbc:oracle:thin:"+user+"/"+passwd+"@serverName:portnumber:A");
Above command let me connect to "A" database but when i replace "A" with "X" to connect to "X" database, it gives me following exception. I tried using setCatalog() function to connect to sub-space of the Connection database object's database, but it didn't work. Any idea what i am missing? Thanks
Exception Error: Io exception: Connection refused(DESCRIPTION=(TMP=)(VSNNUM=153093376)(ERR=12505)(ERROR_STACK=(ERROR=(CODE=12505)(EMFI=4))))
Best Regards,
Prashant Patel

The Oracle database hierarchy uses different terminology:
(1) A (Database)
----(1.1) X (schema)
----------(1.1.1) Number of tables belongs to x schema
----(1.2) Y (schema)
---------(1.2.1) Number of tables belongs to y schema
In Oracle world, a "database" properly speaking is the complete collection of files that store the data and the data state.
Also, service names are not the same as database names; service names can be thought of as "channels" in Oracle's networking layer, through which you connect to a database. 2 different service names may connect you to the same or different databases, either in different modes or with different resource restrictions (such as maximum CPU percentage).
Each Oracle user has their own schema and it is the default schema when they connect; if the user has privileges to access another schema, they may access the tables in the other schema directly, by fully qualifying table references with a schema name.
For example, users jdoe and sroe each have a table named my_table; jdoe has the "SELECT ANY TABLE" privilege and sroe doesn't. jdoe can get results from these SQL statements:
select count(*) from my_table;
select count(*) from jdoe.my_table;
select count(*) from sroe.my_table;user sroe can only do these:
select count(*) from my_table;
select count(*) from sroe.my_table;for sroe, "select count(*) from jdoe.my_table;" will return a privilege error.
Additionally a user session can change the "default schema", the schema that is used when a table refence is not fully qualified, by using the "ALTER SESSION" command. For example, jdoe could issue:
ALTER SESSION SET CURRENT_SCHEMA = SROE;
// get the count from sroe's table
select count(*) from my_table;Hope that helps.

Get only last level in SQL Hierarchy Query

Hi,
How to get only the last level in Oracle SQL Hierarchy Query?
Thanks

Hi,
1007372 wrote:
Hi,
How to get only the last level in Oracle SQL Hierarchy Query?Depending on your requirements:
WHERE CONNECT_BY_ISLEAF = 1
I hope this answers your question.
If not, post a little sample data (CREATE TABLE and INSERT statements, relevant columns only), and also post the results you want from that data.
Explain, using specific examples, how you get those results from that data.
If you can show what you want to do using commonly available tables (such as scott.emp, which contains a hierarchy), then you don't need to post any sample data; just the results and the explanation.
Always say which version of Oracle you're using (e.g., 11.2.0.2.0). This is always important, but especially so with CONNECT BY queries, because every version since Oracle 7 has had significant improvements in this area.
See the forum FAQ {message:id=9360002}

PO Hierarchy Setup

Hi,
We are Oracle 11.0.3. Would like to know if anyone has setup the hierarchy such that individual personal assistant can make the changes to hierarchy? As an example, Dept A has sub-depts A1, A2. Each dept and sub-depts has their own personal assistant(PA) say PA1 for dept A, PA2 for sub-dept A1 and PA3 for sub-dept A2.
1) Can we setup the hierarchy such that PA2 can only see the hierarchy for sub-dept A1 but cannot see the hierarchy for Sub-dept A2 and vice versa for PA3?
2) PA1 should be able to see the whole hierarchy.
If the above can't be setup, anyone has the experience to customize it?
Thanks for your reply.

Oracle Purchasing hierarchy will not look at the DFF. It will go only by your hierarchy setup (either position based or emp-supervisor based.)
Sandeep Gandhi

Data persistence using SQL/J

Hi !
I am trying to achieve data persistence using SQL/J.
The env / tools that I am using are WLS 4.5.1
Oracle 8i, SQL/J.
SQL/J works fine with the two - tier applications but with WLS the connectivity is not been arrived at.
Any help would be wewlcome.
Thanks,
Archana

Are you using an Oracle JDBC driver in WLS or not?
(1) If the answer is no, then you should replace:
oracle.sqlj.runtime.Oracle.connect(<url>,<user>,<pwd>);
(and similarly Oracle.getConnection())
with:
import sqlj.runtime.ref.DefaultContext;
<load JDBC driver, if necessary>
DefaultContext.setDefaultContext(new DefaultContext(<url>,<user>,<pwd>,false));
(2) Actually, forget (1): in the middle tier you should never use a default context at all (every thread must have its own connection context):
DefaultContext ctx = new DefaultContext(...);
#sql [ctx] { ..SQL statement.. };
(3) If you do not use an Oracle JDBC driver, then say in your sqlj command line:
-profile=false
(this omits Oracle customization and makes the .ser file smaller)
Also, you only need runtime.zip at runtime, anyway. And for non-Oracle JDBC drivers you can remove the whole oracle.* hierarchy from runtime.zip.
(4) You do need to deploy those .ser files with the bean. Or use -ser2class and deploy class files with the bean.
(5) Finally, it appears the WLS deployment tool has not heard about SQLJ - it may only understand .java files. In this case you have to translate all .sqlj files (and the .ser files) into .java files before putting these into WLS:
(a) run SQLJ over the .sqlj source with the -compile=false option. This produces .java files.
(b) you can also turn the .ser files into .java files by running:
java sqlj.runtime.profile.util.SerProfileToClass -nc *.ser
(issue the line without arguments to get an option synopsis)
You'd want to do (a) and (b) via a Makefile and not do it by hand more than once.
(c) During deployment time and runtime you must have runtime.zip (modulo comments in (3)) in the respective CLASSPATHS of the deployment tool and of the server.
Sorry these answers were rather generic - I still could not tell exactly how you are failing in WLS.

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);
}

Sql j

How can run oracle Copy Command wihtin sqlj code i need this very urgent

Are you using an Oracle JDBC driver in WLS or not?
(1) If the answer is no, then you should replace:
oracle.sqlj.runtime.Oracle.connect(<url>,<user>,<pwd>);
(and similarly Oracle.getConnection())
with:
import sqlj.runtime.ref.DefaultContext;
<load JDBC driver, if necessary>
DefaultContext.setDefaultContext(new DefaultContext(<url>,<user>,<pwd>,false));
(2) Actually, forget (1): in the middle tier you should never use a default context at all (every thread must have its own connection context):
DefaultContext ctx = new DefaultContext(...);
#sql [ctx] { ..SQL statement.. };
(3) If you do not use an Oracle JDBC driver, then say in your sqlj command line:
-profile=false
(this omits Oracle customization and makes the .ser file smaller)
Also, you only need runtime.zip at runtime, anyway. And for non-Oracle JDBC drivers you can remove the whole oracle.* hierarchy from runtime.zip.
(4) You do need to deploy those .ser files with the bean. Or use -ser2class and deploy class files with the bean.
(5) Finally, it appears the WLS deployment tool has not heard about SQLJ - it may only understand .java files. In this case you have to translate all .sqlj files (and the .ser files) into .java files before putting these into WLS:
(a) run SQLJ over the .sqlj source with the -compile=false option. This produces .java files.
(b) you can also turn the .ser files into .java files by running:
java sqlj.runtime.profile.util.SerProfileToClass -nc *.ser
(issue the line without arguments to get an option synopsis)
You'd want to do (a) and (b) via a Makefile and not do it by hand more than once.
(c) During deployment time and runtime you must have runtime.zip (modulo comments in (3)) in the respective CLASSPATHS of the deployment tool and of the server.
Sorry these answers were rather generic - I still could not tell exactly how you are failing in WLS.

/usr/bin/bash[34]: syntax error at line 40 : `set' unexpected

Hi All
I would like to install Oracle Database 11gR1 On Solaris 10
When I run root.sh command, I confused to input path
*# cd /home/oracle11/app/oracle11/product/11.1.0/db_1*
*# ./root.sh*
Running Oracle 11g root.sh script...
The following environment variables are set as:
ORACLE_OWNER= oracle11
ORACLE_HOME= /usr2/home/oracle11/app/oracle11/product/11.1.0/db_1
*Enter the full pathname of the local bin directory: [usr/local/bin]:/usr/bin/bash*
I have inputed "/usr/bin/bash"
Now I can not run bash on Solaris 10.
*# bash*
bash[34]: syntax error at line 40 : `set' unexpected
Please help me!
Thankyou and best regards,
thiensu2810

Hi
Output of "$ find /usr -name bash 2>/dev/null" is
*# find /usr -name bash 2>/dev/null*
*/usr/bin/bash*
*# less /usr/bin/bash*
+###################################+
+#+
+# $Header: coraenv.sh 17-may-2007.08:31:33 jboyce Exp $ coraenv+
+#+
+# Copyright (c) 1987, 2007, Oracle. All rights reserved.+
+#+
+# This routine is used to condition a C shell user's environment+
+# for access to an ORACLE database. It should be installed in+
+# the system local bin directory.+
+#+
+# The user will be prompted for the database SID, unless the variable+
+# ORAENV_ASK is set to NO, in which case the current value of ORACLE_SID+
+# is used.+
+# An asterisk '*' can be used to refer to the NULL SID.+
+#+
+# 'dbhome' is called to locate ORACLE_HOME for the SID. If+
+# ORACLE_HOME cannot be located, the user will be prompted for it also.+
+# The following environment variables are set:+
+#+
+# ORACLE_SID Oracle system identifier+
+# ORACLE_HOME Top level directory of the Oracle system hierarchy+
+# PATH Old ORACLE_HOME/bin removed, new one added+
+# ORACLE_BASE Top level directory for storing data files and+
+..................................+
+.................................+
else
if (-e $ORABASE_EXEC) then
if (-x $ORABASE_EXEC) then
set BASEVAL=`$ORABASE_EXEC`
setenv ORACLE_BASE $BASEVAL
echo "The Oracle base for ORACLE_HOME=$ORACLE_HOME is $ORACLE_BASE"
else
echo "The $ORACLE_HOME/bin/orabase binary does not have execute privile
ge"
echo "for the current user, $USER. Rerun the script after changing"
echo "the permission of the mentioned executable."
endif
else
setenv ORACLE_BASE $ORACLE_HOME
echo "The Oracle base for ORACLE_HOME=$ORACLE_HOME is $ORACLE_BASE"
endif
endif
+#+
+# Install local modifications here+
+#+
thank,
thiensu2810

Sending mails based on hierarchy by using Oracle Alerts

Hi All,
From past five days i am facing problem in Oarcle Alerts that my requirement is i need to send mails based on hierarchy people by uisng oracle alert.
In this need to send the mail only the different Hierarchy head person only and i need to do this by using alert only
Can any one please suggest me for this.
Any help is greatly appreciated.
Thanks
Anushka

Hi,
i have sql statement Now my problem is how to run 'Sql Statement Script' from Alerts, can you please suggest me on this .I believe this is explained in "Oracle Alert" manual.
Applications Releases 11i and 12
http://www.oracle.com/technology/documentation/applications.html
Thanks,
Hussein

Oracle ADF example of use of Single One Choice with Hierarchy Viewer

I am using JDeveloper Studio 11.1.2.3.0.
I am looking for a simple example where one can select a value from a Single One Choice component and have it drive a query
for populating the Hierarchy Viewer.

You can just use a VO with parameter as the base of your HV - then drag the executeWithParam operation to the page as a parameter form.
And possibly add a list or LOV to the parameter.
https://blogs.oracle.com/shay/entry/adding_an_lov_to_a_query_param
Instead of the table in the video use the HV.

Hierarchy in oracle

Dear expert
After so much digging around and studying I have been able to make some progress in understanding and utilizing hierarchy structures in oracle but I am not there unfortunately. I have the following sample data below
create table t1
parent_id varchar2(200),
child_id varchar2(200)
insert into t1
(parent_id, child_id)
values
('P1', 'C1');
insert into t1
(parent_id, child_id)
values
('P2', 'C2');
insert into t1
(parent_id, child_id)
values
('C1', 'D1');
insert into t1
(parent_id, child_id)
values
('D1', 'D2');
insert into t1
(parent_id, child_id)
values
('D1', 'D3');I can use this query below to get a parents child assuming it has only one child
select t.child_id
from t1 t
start with t.parent_id = 'D1'
connect by prior t.parent_id = t.child_id;but when if the parent has two children it crashes and returns so many unwanted info...Can any one help with that.
which is meant to get a child associated parents all the way to the last parent but it is not working.
Overall this is the output I want for D1
Child Path
D1 D1->C1->P1
also I should have an opportunity depending on the parameter to stop on one level if possible,
All help is appreciated. Thank you

Hi,
Thanks for posting the CREATE TABLE and INSERT statements; that really helps!
Don't forget to say which version of Oracle you're using. This is especially important with CONNECT BY queries, since every version since Oracle 7 has had significant improvements in this area. The queries below work in Oracle 10.1 (and up).
Here's one way:
SELECT     CONNECT_BY_ROOT     child_id          AS child
,     SYS_CONNECT_BY_PATH (parent_id, ' -> ')     AS path
FROM     t1
WHERE     CONNECT_BY_ISLEAF     = 1
START WITH     child_id     = 'D1'
CONNECT BY     child_id     = PRIOR parent_id
;or, if you really want 'D1' in the path:
WITH     got_root   AS
     SELECT     CONNECT_BY_ROOT     child_id          AS child
     ,     SYS_CONNECT_BY_PATH (parent_id, ' -> ')     AS path
     FROM     t1
     WHERE     CONNECT_BY_ISLEAF     = 1
     START WITH     child_id     = 'D1'
     CONNECT BY     child_id     = PRIOR parent_id
SELECT     child
,     child || path     AS path
FROM     got_root
;Output:
CHILD      PATH
D1         D1 -> C1 -> P1Unfortunately, you can't always use CONNECT_BY_ROOT in place of any other expression. In this case, an ORA-00932 error occurs if you try to do the || operation in the CONNECT BY query, but you can do it in a separate query.
user13328581 wrote:
... also I should have an opportunity depending on the parameter to stop on one level if possible,Sorry, I don't understand. Post the exact output you want, formatted, between \ tags.
You can include conditions like "AND LEVEL <= n" in the CONNECT BY clause. If n=1, it might be bettter just to do a self-join, rather than CONNECT BY.
Edited by: Frank Kulash on May 13, 2011 10:31 AM
Corrected spelling

Pass hierarchy dashboard prompt to analysis in Oracle BI

Hi All,
I am new to Oracle BI EE 11g. Right now i am learning this.
I have created time hierarchy dashboard prompt and saved it my shared folder.
I have created a analysis which shows Top 10 products Revenue and saved it my shared folder.
Now I am trying to connect the above two items in my dashboard. But I don't know how to pass hierarchy prompt values to my analysis. There is no option to drop hierarchy dimension in analysis filter and mark it as "is prompted".
Can anyone please help me?
Thanks
Maya

Well Haree, your idea don't activate filter
My BI version is Oracle Business Intelligence 11.1.1.6.0
I've checked that hierarchy column value from Time hierarchy selected via filter on dashboard A can be sent through Go URL
to new report B opened in new window, but BI don't suppport including hierarchy column in filter section of target report B.
So, other words, I've faced already 3 weeks against the same issue.
User select in Dashboard A subset of Time hierarchy along with common filters say Supplier, but it is not possible to drill through Supplier to its Customers with keeping
selected dimensions of Time hierarchy, say couple of selected weeks of September, in new target Report B.
And I wonder why BI allow pass hierarchy column value in Go URL but don't give to use its value in navigated report.
May be it's tiime to set Patch 11.1.1.6.2 BP1 ?
Any advices greately appreciated

Oracle BI Hierarchy

Similar Messages

Maybe you are looking for