OWB 11.2.0.1 dimension and cube operators + ODBC target database

Hi,
We are considering using OWB to populate a netezza data mart making use of the dimension and cube operators.
Could we use OWB for this/is it supported in this manner or do we need to use another ETL tool/workaround.
Understand OWB supports ODBC as target.
Any advice much appreciated.
Thanks

Hi
You can have ODBC targets but the cube/dim operators use MERGE loading type so its not a tested/supported case using the operators with Netezza. It has been optimized for Oracle.
Cheers
David

Similar Messages

How to import SH Sample Dimensions and Cubes with OWB Client

Hi, is there a functionality to import the Dimensions and Cubes from the sample to reuse and manipulate them within the OWB Client?
I can add Dimensions in the Enterprise Manager but mapping should be difficult- right?
Specs: DB 10g rel2, OWB 10.1.0.4

dimension - either define a table on your own, or use the data modeler and physically define a new dimension.
Cube - same as above.
as for levels and hierarchies, this can also be done in the data modeler. You can specify keys, levels, attributes, measures...all that stuff for dims and facts. There many tabs on the lower half of the dimension modeler screen that control this.
Check out the oracle by examples for easy tutorials.

Using dimension and cube operator

hi
I am facing problem in using this dimension and cube operator..
Actually I want to create a sales data with dimensions as time,customer and product
After creating a dimension in owb I get a table created attached with it same is the case with cube operator
so where should I store my measures in the cube or the table created and where to store the data about dimensions in the table created.
and finally how to use them in mapping to retrieve the data stored
Thanks

It sounds like you are not getting any matching keys for loading into the cube.
Do you have a time dimension created by OWB in the cube? The key used by the cube operator for an OWB time dimension is a formatted number. The time dimension keys are stored as follows;
Day Level - YYYYMMDD
Month Level - YYYYMM
Week Level - YYYYWW
Quarter - YYYYQ
Year - YYYY
If you have a source that has a SQL date datatype for example and want to construct the key for a cube's time dimension at the day level something like the following expression can be used to construct the time reference from a SQL date...
to_number(to_char( time_key, 'YYYYMMDD'))
It may not be this but just a thought.
Cheers
David

Building Dimensions and Cubes in 11.1

Hi Experts,
Can anyone provide me a weblink or atleast steps as to how to create a Dimensions and Cubes in OWB 11.1.
For practice purpose i am accessing HR User. In there i have selected Locations and Countries table and is using it to create the Place_Dim (Place Dimension)
Issues:
1. What are Levels and Heirarchiies
(In ROLAP its asking me to use the surrogate Key i both the levels)
2. It is asking me to bound it to table or view. I have never seen any help regarding in bounding and out bounding in the tool.
Please help.
Regards,
Ravi Remje

Many Thanks Dave for your help. The links are very helpfull.
I have a silly doubt in my mind. Kindly apologize for my dumbness.
Concerns:
I went through the OWB tool and came to the conclusion that the DIMENSIONS and CUBES are logical object. However, if i want to use it as a Physical table, is it any way as in how we can use the simple tables as different types of dimensions and facts by changing their loading type. Is it any possible way to implement the same feature for DIMENSION and CUBE objects. I dont want them to be used as views but as a table.
Please help.
Regards,
Ravi Remje

Cannot find object after creating dimension and cube.

I need to develop a project using olap api to get olap data.
My db release is 10.1.0.2, owb is 10.1.0.4.
After i create dimension and cube in owb, I cannot find any object i have created in owb. Except that in OEM, after i click the button dimension, there comes an message as that the dimension does not have complete metadata or was created by old release and OEM will create a metadata for it. After that, I can find the dimension in AWM and get the imformation using olap api.
However, there is no measure button in OEM, I cannot find the measures in measure folder. So that i cannot get the information of the MdmMeasureDimension using olap api.
Can somebody help me with this issue? Thanks!

With OWB 10.1 and prior releases to get OLAP metadata for a dimension or cube you must have used the OWB transfer wizard to deploy the OLAP metadata. This bridge basically creates and executes a script with all of the CWM calls to create the OLAP dimension and cube metadata.
When you deployed the dimension from OWB in 10.1 it only created the 'create dimension DDL' for the object.
Cheers
David

Can CWM2 API creating dimensions and cube reference a view

Can CWM2 API creating dimensions and cube reference a view instead of a table.
Can the following API reference a view instead of table
For creating dimensions
CWM2_OLAP_TABLE_MAP.MAP_DIMTBL_HIERLEVEL
CWM2_OLAP_TABLE_MAP.MAP_DIMTBL_HIERLEVELATTR
For creating cubes
CWM2_OLAP_TABLE_MAP.MAP_FACTTBL_LEVELKEY
CWM2_OLAP_TABLE_MAP.MAP_FACTTBL_MEASURE

Hi!
Yes!
And I am using views sometimes.
I am reading at this moment also the following...
maybe someone can explain me this sentence...
MULTIPLE FACT TABLES:
"The CWM2 APIs also support multiple fact tables per cube. In this case, the data
associated with a given combinations of hierarchies can be stored in a separate fact
table. All the fact tables associated with a cube must have the same column
structure."
I get a fetch error message..'cause of this.
What does it mean by "the same column
structure" ???
ODDS

ROLLUP AND CUBE OPERATORS IN ORACLE 8I

제품 : PL/SQL
작성날짜 : 2000-06-29
========================================
ROLLUP AND CUBE OPERATORS IN ORACLE 8I
========================================
PURPOSE
ROLLUP 과 CUBE Operator에 대해 설명하고자 한다.
Explanation
ROLLUP operator는 SELECT문의 GROUP BY절에 사용된다.
SELECT절에 ROLLUP 을 사용함으로써 'regular rows'(보통의 select된 data)와
'super-aggregate rows'(총계)을 구할 수 있다. 기존에는 select ... union select
를 이용해 구사해야 했었던 것이다. 'super-aggregate rows'는 'sub-total'
(중간 Total, 즉 소계)을 포함한다.
CUBE operator는 Cross-tab에 대한 Summary를 추출하는데 사용된다. 모든 가능한
dimension에 대한 total을 나타낸다. 즉 ROLLUP에 의해 나타내어지는 item total값과
column total값을 나타낸다.
NULL값은 모든 값에 대한 super-aggregate 을 나타낸다. GROUPING() function은
모든 값에 대한 set을 나타내는 null값과 column의 null값과 구별하는데 쓰여진다.
GROUPING() function은 GROUP BY절에서 반드시 표현되어야 한다. GROUPING()은 모든
값의 set을 표현합에 있어서 null이면 1을 아니면 0을 return한다.
ROLLUP과 CUBE는 CREATE MATERIALIZED VIEW에서 사용되어 질수 있다.
Example
아래와 같이 테스트에 쓰여질 table과 data을 만든다.
create table test_roll
(YEAR NUMBER(4),
REGION CHAR(7),
DEPT CHAR(2),
PROFIT NUMBER );
insert into test_roll values (1995 ,'West' , 'A1' , 100);
insert into test_roll values (1995 ,'West' , 'A2' , 100);
insert into test_roll values (1996 ,'West' , 'A1' , 100);
insert into test_roll values (1996 ,'West' , 'A2' , 100);
insert into test_roll values (1995 ,'Central' ,'A1' , 100);
insert into test_roll values (1995 ,'East' , 'A1' , 100);
insert into test_roll values (1995 ,'East' , 'A2' , 100);
SQL> select * from test_roll;
YEAR REGION DE PROFIT
1995 West A1 100
1995 West A2 100
1996 West A1 100
1996 West A2 100
1995 Central A1 100
1995 East A1 100
1995 East A2 100
7 rows selected.
예제 1: ROLLUP
SQL> select year, region, sum(profit), count(*)
from test_roll
group by rollup(year, region);
YEAR REGION SUM(PROFIT) COUNT(*)
1995 Central 100 1
1995 East 200 2
1995 West 200 2
1995 500 5
1996 West 200 2
1996 200 2
700 7
7 rows selected.
위의 내용을 tabular로 나타내어 보면 쉽게 알 수 있다.
Year Central(A1+A2) East(A1+A2) West(A1+A2)
1995 (100+NULL) (100+100) (100+100) 500
1996 (NULL+NULL) (NULL+NULL) (100+100) 200
700
예제 2: ROLLUP and GROUPING()
SQL> select year, region, sum(profit),
grouping(year) "Y", grouping(region) "R"
from test_roll
group by rollup (year, region);
YEAR REGION SUM(PROFIT) Y R
1995 Central 100 0 0
1995 East 200 0 0
1995 West 200 0 0
1995 500 0 1
1996 West 200 0 0
1996 200 0 1
700 1 1
7 rows selected.
참고) null값이 모든 값의 set에 대한 표현으로 나타내어지면 GROUPING function은
super-aggregate row에 대해 1을 return한다.
예제 3: CUBE
SQL> select year, region, sum(profit), count(*)
from test_roll
group by cube(year, region);
YEAR REGION SUM(PROFIT) COUNT(*)
1995 Central 100 1
1995 East 200 2
1995 West 200 2
1995 500 5
1996 West 200 2
1996 200 2
Central 100 1
East 200 2
West 400 4
700 7
위의 내용을 tabular로 나타내어 보면 쉽게 알 수 있다.
Year Central(A1+A2) East(A1+A2) West(A1+A2)
1995 (100+NULL) (100+100) (100+100) 500
1996 (NULL+NULL) (NULL+NULL) (100+100) 200
100 200 400 700
예제 4: CUBE and GROUPING()
SQL> select year, region, sum(profit),
grouping(year) "Y", grouping(region) "R"
from test_roll
group by cube (year, region);
YEAR REGION SUM(PROFIT) Y R
1995 Central 100 0 0
1995 East 200 0 0
1995 West 200 0 0
1995 500 0 1
1996 West 200 0 0
1996 200 0 1
Central 100 1 0
East 200 1 0
West 400 1 0
700 1 1
10 rows selected.
===============================================
HOW TO USE ROLLUP AND CUBE OPERATORS IN PL/SQL
===============================================
Release 8.1.5 PL/SQL에서는 CUBE, ROLLUP 이 지원되지 않는다. 8i에서는 DBMS_SQL
package을 이용하여 dynamic SQL로 구현하는 방법이 workaround로 제시된다.
Ordacle8i에서는 PL/SQL block에 SQL절을 직접적으로 위치시키는 Native Dynamic SQL
(참고 bul#11721)을 지원한다.
Native Dynamic SQL을 사용하기 위해서는 COMPATIBLE 이 8.1.0 또는 그 보다 높아야
한다.
SVRMGR> show parameter compatible
NAME TYPE VALUE
compatible string 8.1.0
예제 1-1: ROLLUP -> 위의 예제 1과 비교한다.
SQL> create or replace procedure test_rollup as
my_year test_roll.year%type;
my_region test_roll.region%type;
my_sum int;
my_count int;
begin
select year, region, sum(profit), count(*)
into my_year, my_region, my_sum, my_count
from test_roll
group by rollup(year, region);
end;
Warning: Procedure created with compilation errors.
SQL> show errors
Errors for PROCEDURE TEST_ROLLUP:
LINE/COL ERROR
10/8 PL/SQL: SQL Statement ignored
13/18 PLS-00201: identifier 'ROLLUP' must be declared
SQL> create or replace procedure test_rollup as
type curTyp is ref cursor;
sql_stmt varchar2(200);
tab_cv curTyp;
my_year test_roll.year%type;
my_region test_roll.region%type;
my_sum int;
my_count int;
begin
sql_stmt := 'select year, region, sum(profit), count(*) ' ||
'from test_roll ' ||
'group by rollup(year, region)';
open tab_cv for sql_stmt;
loop
fetch tab_cv into my_year, my_region, my_sum, my_count;
exit when tab_cv%NOTFOUND;
dbms_output.put_line (my_year || ' '||
nvl(my_region,' ') ||
' ' || my_sum || ' ' || my_count);
end loop;
close tab_cv;
end;
SQL> set serveroutput on
SQL> exec test_rollup
1995 Central 100 1
1995 East 200 2
1995 West 200 2
1995 500 5
1996 West 200 2
1996 200 2
700 7
PL/SQL procedure successfully completed.
예제 2-1: ROLLUP and GROUPING() -> 위의 예제 2와 비교한다.
SQL> create or replace procedure test_rollupg as
my_year test_roll.year%type;
my_region test_roll.region%type;
my_sum int;
my_count int;
my_g_region int;
my_g_year int;
begin
select year, region, sum(profit),
grouping(year), grouping(region)
into my_year, my_region, my_sum, my_count,
my_g_year, my_g_region
from test_roll
group by rollup(year, region);
end;
Warning: Procedure created with compilation errors.
SQL> show error
Errors for PROCEDURE TEST_ROLLUPG:
LINE/COL ERROR
12/4 PL/SQL: SQL Statement ignored
17/13 PLS-00201: identifier 'ROLLUP' must be declared
SQL> create or replace procedure test_rollupg as
type curTyp is ref cursor;
sql_stmt varchar2(200);
tab_cv curTyp;
my_year test_roll.year%type;
my_region test_roll.region%type;
my_sum int;
my_count int;
my_g_region int;
my_g_year int;
begin
sql_stmt := 'select year, region, sum(profit), count(*), ' ||
'grouping(year), grouping(region) ' ||
'from test_roll ' ||
'group by rollup(year, region)';
open tab_cv for sql_stmt;
loop
fetch tab_cv into my_year, my_region, my_sum, my_count,
my_g_year, my_g_region;
exit when tab_cv%NOTFOUND;
dbms_output.put_line (my_year || ' '||my_region ||
' ' || my_sum || ' ' || my_count ||
' ' || my_g_year || ' ' || my_g_region);
end loop;
close tab_cv;
end;
Procedure created.
SQL> set serveroutput on
SQL> exec test_rollupg
1995 Central 100 1 0 0
1995 East 200 2 0 0
1995 West 200 2 0 0
1995 500 5 0 1
1996 West 200 2 0 0
1996 200 2 0 1
700 7 1 1
PL/SQL procedure successfully completed.
예제 3-1: CUBE -> 위의 예제 3과 비교한다.
SQL> create or replace procedure test_cube as
my_year test_roll.year%type;
my_region test_roll.region%type;
my_sum int;
my_count int;
begin
select year, region, sum(profit), count(*)
into my_year, my_region, my_sum, my_count
from test_roll
group by cube(year, region);
end;
Warning: Procedure created with compilation errors.
SQL> show error
Errors for PROCEDURE TEST_CUBE:
LINE/COL ERROR
10/4 PL/SQL: SQL Statement ignored
13/13 PLS-00201: identifier 'CUBE' must be declared
SQL> create or replace procedure test_cube as
type curTyp is ref cursor;
sql_stmt varchar2(200);
tab_cv curTyp;
my_year test_roll.year%type;
my_region test_roll.region%type;
my_sum int;
my_count int;
begin
sql_stmt := 'select year, region, sum(profit), count(*) ' ||
'from test_roll ' ||
'group by cube(year, region)';
open tab_cv for sql_stmt;
loop
fetch tab_cv into my_year, my_region, my_sum, my_count;
exit when tab_cv%NOTFOUND;
dbms_output.put_line (my_year || ' '||
nvl(my_region,' ') ||
' ' || my_sum || ' ' || my_count);
end loop;
close tab_cv;
end;
Procedure created.
SQL> set serveroutput on
SQL> exec test_cube
1995 Central 100 1
1995 East 200 2
1995 West 200 2
1995 500 5
1996 West 200 2
1996 200 2
Central 100 1
East 200 2
West 400 4
700 7
PL/SQL procedure successfully completed.
예제 4-1: CUBE and GROUPING() -> 위의 예제 4와 비교한다.
SQL> create or replace procedure test_cubeg as
my_year test_roll.year%type;
my_region test_roll.region%type;
my_sum int;
my_count int;
my_g_region int;
my_g_year int;
begin
select year, region, sum(profit),
grouping(year), grouping(region)
into my_year, my_region, my_sum, my_count,
my_g_year, my_g_region
from test_roll
group by cube(year, region);
end;
Warning: Procedure created with compilation errors.
SQL> show error
Errors for PROCEDURE TEST_CUBEG:
LINE/COL ERROR
12/4 PL/SQL: SQL Statement ignored
17/13 PLS-00201: identifier 'CUBE' must be declared
SQL> create or replace procedure test_cubeg as
type curTyp is ref cursor;
sql_stmt varchar2(200);
tab_cv curTyp;
my_year test_roll.year%type;
my_region test_roll.region%type;
my_sum int;
my_count int;
my_g_region int;
my_g_year int;
begin
sql_stmt := 'select year, region, sum(profit), count(*), ' ||
'grouping(year), grouping(region) ' ||
'from test_roll ' ||
'group by cube(year, region)';
open tab_cv for sql_stmt;
loop
fetch tab_cv into my_year, my_region, my_sum, my_count,
my_g_year, my_g_region;
exit when tab_cv%NOTFOUND;
dbms_output.put_line (my_year || ' '||my_region ||
' ' || my_sum || ' ' || my_count ||
' ' || my_g_year || ' ' || my_g_region);
end loop;
close tab_cv;
end;
Procedure created.
SQL> set serveroutput on
SQL> exec test_cubeg
1995 Central 100 1 0 0
1995 East 200 2 0 0
1995 West 200 2 0 0
1995 500 5 0 1
1996 West 200 2 0 0
1996 200 2 0 1
Central 100 1 1 0
East 200 2 1 0
West 400 4 1 0
700 7 1 1
PL/SQL procedure successfully completed.
Reference Ducumment
Note:67988.1

Hello,
As previously posted you should use export and import utilities.
To execute exp or imp statements you have just to open a command line interface, for instance,
a DOS box on Windows.
So you don't have to use SQL*Plus or TOAD.
About export/import you may care on the mode, to export a single or a list of Tables the Table mode
is enough.
Please, find here an example to begin:
http://wiki.oracle.com/page/Oracle+export+and+import+
Hope this help.
Best regards,
Jean-Valentin

How to change column names in dimension and cube views?

whenever AWM creates a view on a dimension or cube, it creates columns for long and short description with full name
forexanmpel, it creates like
CREATE OR REPLACE VIEW OLAPTRAIN.CHANNEL_VIEW
AS
SELECT
"DIM_KEY",
"LEVEL_NAME",
"MEMBER_TYPE",
"DIM_ORDER",
"LONG_DESCRIPTION",
"SHORT_DESCRIPTION",
"ALL_CHANNELS_LONG_DESCRI",
"ALL_CHANNELS_SHORT_DESCR",
"CLASS_LONG_DESCRIPTION",
"CLASS_SHORT_DESCRIPTION",
"CHANNEL_LONG_DESCRIPTION",
"CHANNEL_SHORT_DESCRIPTIO",
"CHANNEL_TYPE",
"CHANNEL_CHANNEL_TYPE",
"CHANNEL_ALL_CHANNELS_ID",
"CHANNEL_CLASS_ID",
"CHANNEL_CHANNEL_ID"
FROM TABLE(CUBE_TABLE('"OLAPTRAIN"."CHANNEL"') );
what is the way to customize the column name? for example for class level, how can we say insterad of long_description and short_description, use LONG and SHORT simply?
i also see the size of long and short descriptions are set to varchar2(60) and varchar2(20), is there a way to change that for each level in AWM?
Thanks

Hi there,
I don't think there is a way to control the column names within the OLAP product itself, but if this is something you really want to do, have you tried creating your own views?
As you can see, the syntax is pretty simple
Thanks,
Stuart Bunby
OLAP Blog: http://oracleOLAP.blogspot.com
OLAP Wiki: http://wiki.oracle.com/page/Oracle+OLAP+Option
OLAP on OTN: http://www.oracle.com/technology/products/bi/olap/index.html
DW on OTN : http://www.oracle.com/technology/products/bi/db/11g/index.html

Dimensions and Cubes Process OK / database 'Process Full' fails

Hello,
I am having trouble processing SSAS database (SQL 2008R2).
Within BIDS environment I can process all dimensions and two cubes - no problem. But when I try to process the database (Process Full – Sequential/ All in one transaction), I keep getting errors about one specific dimension (however the very same dimension
is processed separately just fine).
Any ideas why this would happen?
Thanks,
Lana

Thanks so much for all your replies! Your help is greatly appreciated
J
Here is the error message I am getting (it is the same for bunch of other attributes of the same dimension called
Item):
Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Item', Name of 'Item' was being processed.
Errors in the OLAP storage engine: An error occurred while the 'Product Group' attribute of the 'Item' dimension from the 'InvCube' database was being processed.
OLE DB error: OLE DB or ODBC error: Operation canceled; HY008.
Errors in the OLAP storage engine: A duplicate attribute key has been found when processing: Table: 'dbo_Item', Column: 'Colour', Value: ''. The attribute is 'Colour'.
Keep in mind that the Key for this dimension is called ItemID and there are no duplicates (I checked). Before processing the cube, I have dozens of procedures (within SSIS package that brings the data into DW) that are checking if all the
keys (FK columns on Fact table) exist within dim tables (PK columns). I also do not allow NULLs or blanks for the dim keys within Fact tables, I replace them with
special “DimName-000” Keys that, again, exist within dim tables.
What I am trying to figure out… why I can process Item dimension just fine on its own (I also process all the other dimensions OK), after that I can process both cubes that are using this (and other) dimension(s) … and I can browse the cubes, getting breakdown
by Item / Colour / Product Group, etc... So, everything seems to work perfectly. However, when I try to process the whole database (with all previously processed dimensions and both cubes - there are only two cubes for now, to make is simple), the process
fails, giving me an error about duplicate attribute key for this specific Item dimension.
Any thoughts?
Thanks again!

How to get DIMENSION and CUBE data into JDeveloper???

i have build cube and dimension using oracle analytical workspace manager (AWM),
how i can get the cube and dimension data using jdeveloper 11gR2??
does anybody know?
any extension? or what??

The simplest thing is to use JDBC (java.sql package) to access the cube and dimension views through SQL. Something like this (with appropriate error handling).
String sql = "SELECT dim_key FROM product_view";
Statement statement = connection.createStatement();
ResultSet rs = statement.executeQuery(sql);
while (rs.next())
// Process row here
rs.close();
statement.close(); If your requirements are more complicated or you feel adventurous, then you can use the Java OLAP API. This is the code used by the data viewer in AWM. (Look for olap_api.jar in your database installation -- olap\api\lib\olap_api.jar my windows instance.)

Are fact tables and cubes same in OWB?

Dear all
A simple question. How can I create a star schema (that is, with a fact table and dimensions) using OWB?
OWB has options to create cubes, but as per my understanding a cube is not a fact table.
Cube contains pre-computed data where as fact table contains normal data with references to dimensions.
Please correct me if I am wrong.
thanks in advance

These are just different levels of abstraction.
"Cube" is the highest level of abstraction referring to the overall package of data.
"Star schema" is how cubes are modelled showing the relationships from a fact entity to the dimension entities.
Relational and OLAP are different methods of physical implementation.
In OWB, to promote sharing of dimensions across cubes to avoid inconsistency the idea is you define and build the dimensions independently. Then you define the "cubes" as measures and references to the dimensions. When you build the "cube" you pass in business identifiers from the source data which OWB will use to link the measures to the applicable dimension data. Due to the wonders of inner joins anyone reading the "cube" will only see dimension data related to the data in that cube!
Using OWB you do not need to be concerned with the physical implementation when you use the dimension and cube operators as those operators know what to do.

Conformed Dimensions and OWB

Hi, I am trying to use some of my dimensions from one WH Target module in another WH target module.
The simple idea as follows, I am deploying a few new conformed dimensions into my conformed dim WH target. And im puting down a cube into a datamart WH target. This is all in one project. BUT it appears I cannot share, or reference the dims and cubes from other targets :( Even though they will be resolved via thier locations into the same instance.
I would like a statement as this appears to be major missing functionality? (given you can reference tables etc between WH target modules in the same project)
Thanks,
Richard.

Richard,
The current release is indeed restricted to use the dimensions in one module only. This restriction will be removed in the next major release (US summer 2004).
Mark.

How to create ssas cube by using MySQL Database

please tell me step by step process to create ssas cube by using MySQL database in my system, i have Sqlserver 2008 enterprise edition and MySql5.0

There is an OLEDB provider for MySQL which you can get from here
https://cherrycitysoftware.com/ccs/Providers/ProvMySQL.aspx otherwise you can also use SSIS to push the data straight into the Analysis Services database without needing to stage it in SQL Server. Also, as you can load data into AS using XMLA you could
also write your own loader to extract data using ODBC and push it into AS using XMLA, essentially what I suspect SSIS does. However those latter solutions don't allow you to create a database on top of MySQL because you need an OLEDB (or .net) provider for
that.
In the simplest case, install the OLEDB provider and then in AS create a Data Source connection using that provider. Once you have done that you should be able to create a Data Source View using that connection enabling you to import the schema definitions
for the tables/views in the MySQL database. From there you build dimensions and cubes etc. about which there is plenty of information on the web.
http://bi-logger.blogspot.com/

Cubes - how to extract a single dimension and save it in a table

Hi,
I am new to the cubes concept, although I've used it several times in the past to analyse the data but never explored options beyond that. using excel, I can get different dimentions from the cube such as customer information, location, etc.
is there a way to extract (automatically) a single dimension and save it in a table...? e.g I want to pull customer name and revenues only from the cube, how would I do it?
Thanks

Hi,
tparvaiz wrote:
Hi,
I am new to the cubes concept, although I've used it several times in the past to analyse the data but never explored options beyond that. using excel, I can get different dimentions from the cube such as customer information, location, etc.
is there a way to extract (automatically) a single dimension and save it in a table...? Sure, you can do that.
Say you had a table with many customers, and you were interested in only one of those customers: what would you do? You'd write a query with a WHERE clause that included only the customer you wanted to see.
A cube is a table with many dimensions. You're interested in only one of those dimensions, so what can you do? You can write a query with a WHERE clause to include only the dimension you want to see.
e.g I want to pull customer name and revenues only from the cube, how would I do it?Exactly how to do it depends on the table(s), your requirements and your Oracle version. As the others have said, post a little sample data (CREATE TABLE and INSERT statements to simulate what your real table looks like), and the results you want from that data.
Always say which version of Oracle you're using (e.g. 11.2.0.2.0).
See the forum FAQ {message:id=9360002}

Write-back dimensions and how do they affect other users of the cube?

If write-back is enabled on a cell or dimension and a value is changed, will it affect other users of that data as well?
When the cube is rebuilt will those new values/updates be overwritten?

Hi Shifrbit,
Writeback is implemented as ROLAP partition. Analysis Services creates a table in relational database where it stores writeback data. User do not need to worry about the mechanism Analysis Server is using to store writeback data. You can re-process your
cube without concern of loosing data. Writeback will not disappear after process the cube. For the detail information about it, please refer to the link below to see
Affect of Cube Changes section.
http://msdn.microsoft.com/en-us/library/ms145568.aspx
Hope this helps.
Regards,
Charlie Liao
TechNet Community Support

OWB 11.2.0.1 dimension and cube operators + ODBC target database

Similar Messages

Maybe you are looking for