TxsOqDefinitionManager Error Creating Dimension in AWM 11.1.0.6 A

I have just been setting up a new install of 11g with AWM 11.1.0.6 A. I have installed all patches through Patch 7, which appears to be the last patch set. Evan with doing this I am getting the above error. Have I missed a patch?
Thanks
Mathew

Simple logic maybe, but slightly flawed (although it is easy to see why you did what you did - and you were not helped by the way Metalink presents the information)
Note:559834.1 also explicitly states that the cause of the problem is that the 11.1.0.6 A Database Patch is required.
The reason why it refers to installing the 'latest' OLAP patch is because the A patch has been superceded by the B patch for some operating systems.
Patch 7 does indeed appear at the top of the list when you search for Oracle OLAP on Metalink, but when you look again you will notice that this is flagged as an 'Oracle Database Family' patch whereas the A patch (6459753) is the latest 'Oracle OLAP' patch.
Of course, none of this explains why patch 7 and the OLAP A patch are not compatible with each other, but I'm guessing that testing every permutation of every patch for every operating system is just not feasible.
Are you able to rollback patch 7?
Thanks
Stuart

Similar Messages

Error when I try to create dimension with AWM 11.1.0.7.0B

hello, I have installed Analytic workspace manager 11g, and I have created a connection to an oracle database, but when I try to create a dimension 2 errors appears:
1.the dimension must have at least one hierarchy
2.the dimension must have at least a level
i use sys as sysdba , as a user in AWM to resolve the problem of priviliege.plz any suggestions !!??

What version of the database and AWM are you using? The failure on the <Classification> tag suggests that you may have database version 11.1.0.6. If so, then I recommend that you upgrade the server to at least version 11.1.0.7.

Error when I try to create dimension with AWM 11g

hello, I have installed Analytic workspace manager 11g, and I have created a connection to an oracle database, but when I try to create a dimension 2 errors appears by alternate :
1/
La transaction ne peut pas être validée : "Erreur sur le serveur
Classe d'erreurs : Echec dExpress
Descriptions des erreurs du serveur :
DPR : Création impossible du curseur de serveur, Générique à TxsOqDefinitionManager::generic<CommitRoot>
INI : Impossible d'analyser la chaîne XML envoyée par le client au serveur, Générique à XML Parser Errors:
Error processing subelement: <StandardDimension><Attribute><BaseAttribute><Classification>
Error processing tag: Classification:
Error returned by xsOqXmlParserExecute.
2/
Des erreurs se sont produites lors de lanalyse XML
<Ligne 3, Colonne 15> : <Line 3, Column 15>: XML-20210: (Fatal Error) Unexpected EOF.
help me stp.

Hi,
This question is missplaced in this forum.
Please ask this question again, the appropriate forum is found here:
OLAP
(OLAP forum)
thanks
Jorge

Error when building dimension using AWM

Hi Gurus,
I am trying to build a dimension using AWM 11.1.0.7.0B Standalone. My Database version is _11.1.0.6.0._
The moment i start to create a New Dimension, i get the below error.
The transaction is not committable: "An error has occurred on the server
Error class: Express Failure
Server error descriptions:
DPR: Unable to create server cursor, Generic at TxsOqDefinitionManager::g
The transaction is not committable: "An error has occurred on the server
Error class: Express Failure
Server error descriptions:
DPR: Unable to create server cursor, Generic at TxsOqDefinitionManager::generic<CommitRoot>
INI: Unable to parse XML string sent from the client to the server, Generic at XML Parser Errors:
Error processing subelement: <StandardDimension><Attribute><BaseAttribute><Classification>
Error processing tag: Classification:
Error returned by xsOqXmlParserExecute.
+"+
+at oracle.olap.awm.dataobject.dialog.PropertyViewer.doCreateAction(Unknown Source)+
+at oracle.olap.awm.dataobject.dialog.CreateDialogHostActionThread.doAction(Unknown Source)+
+at oracle.olap.awm.ui.dialog.ThreadedDialogActionThread.run(Unknown Source)+
Please help!!!!!
+*Regards,*+
+*Ravi R*+

The initial release of OLAP in 11.1.0.6 was not stable. Please upgrade to at least database 11.1.0.7, and preferably 11.2.0.3. If you move to 11.1.0.7, then you should apply the "OLAP D Patch", #9147749. See the OLAP certification page for more details.
http://www.oracle.com/technetwork/database/options/olap/olap-certification-092987.html

Is it possible to create dimension roles in AWM?

Hi,
Is it possible to create dimension roles in AWM like the way we have in OWB ?
If yes, please direct on the way to do this.
Many thanks in advance for your kind inputs.
Piyush

I think what you need is to use the ALIAS option that is part of the DEFINE DIMENSION statement
DEFINE DIMENSION ALIASOF
The DEFINE DIMENSION ALIASOF command defines a dimension alias for a simple dimension. An alias dimension has the same type and values as its base dimension. Typically, you define an alias dimension when you want to dimension a variable by the same dimension twice.
Additionally, You can use a LIMIT statement to limit alias dimensions and define variables and relations using an alias dimension. However, you cannot maintain an alias dimension directly; instead you maintain its base dimension using MAINTAIN.
Syntax
DEFINE name DIMENSION ALIASOF dimension [TEMP] [AW workspace] [SESSION]
Arguments
name
The name of the object you are defining. For general information about this argument, see the main entry for the DEFINE command.
DIMENSION ALIASOF
If you look at this example if provides a great example of how to use this feature:
http://download.oracle.com/docs/cd/B19306_01/olap.102/b14346/dml_x_decimal006.htm#ABC1485326
But of course the main issue here is how to generate the standard form metadata required to support this feature and make the dimension alias avaliable and visible within AWM. That is the difficult (and I would say impossible) part of the process since this feature is not supported by the AW XML API (at least I don't think it is, you could check the API docs to see if this is supported). if it is not supported then the management of this feature would all have to be controlled via OLAP DML commands (load dimension members etc) but you would still not be able to include it within a cube definition and then maintain that cube using AW XML API.
Does that help?
Keith

Creating Flat Dimensions in AWM

Hi,
We have a proposed cube structure with 8 dimensions (apart from the TIME dimension) as follows:
3 Dimensions have a Level-Based Hierarchy
2 Dimensions have a Value-Based Hierarchy
3 Dimensions are flat with no levels or hierarchy.
We are using Oracle Analytic Workspace Manager v10.2.0.3.0A for formulating the cube structure.
We want to introduce a top level “All” column in all the dimensions so as to facilitate analysis of data by eliminating the dimension itself (by selecting its “all” level). Inclusion of such a top level “All” level seems intuitive for Level based and value based hierarchy as we can just introduce the new level.
However, we are not sure of how we can create a “flat” dimension and also have the top level “all” column in it by using AWM. Any insights on the process of creating a flat dimension in AWM would be much appreciated.
Thanks,
Piyush

I am not sure what the problem is? You simply create a dimension with two levels:
- Top level
- Base level
Assign an 'All Members" description to the top level and all all other members are assigned to the base level.
Keith Laker
Oracle EMEA Consulting
BI Blog: http://oraclebi.blogspot.com/
DM Blog: http://oracledmt.blogspot.com/
BI on Oracle: http://www.oracle.com/bi/
BI on OTN: http://www.oracle.com/technology/products/bi/
BI Samples: http://www.oracle.com/technology/products/bi/samples/

Unable to create dimension in Analytic Workspace manager

Hi all,
I am trying to create dimension using Analytic Workspace Manager(AWM) and it throws the following error.
*"The transaction is not committable: "java.lang.RuntimeException: org.xml.sax.SAXException: Missing XML attribute: Attribute for tag: <Metadata><StandardDimension><Organization><AWPrimaryDimensionOrganization><AttributeOrganization>"*
Kindly share your comments.
I am using Oracle 11g r1 client to connect with oracle 11g R2 database.
Please let me know the steps to create a OLAP cube using AWM
Regards
Mukhil

It sounds like a mismatch between an old version of AWM and a new version of the server. Please try a more recent version of AWM.
http://www.oracle.com/technetwork/database/options/olap/olap-downloads-098860.html

Error creating Universe from BW query

Hi
Creating the Universe connected to BW query (BI 7).
Connection is proper and universe designer is connected to BW system without any problem. I have already used many queries to connect to universe and webi documents has been developed.
The only difference in this BW query is, it is using hierarchy with 'derivation type' in 'select hierarchy date'.
BW query is working as expected in BEx designer.
This is the error message when trying to create the universe from BW query -
Error getting dimensions for cube <infoprovider name>/<query name>(catalog <infoprovider name>): Unknown error when executing MDX
Product name : SAP BusinessObjects Enterprise XI 3.1 Client Tools SP3
Please respond how this can be resolved.
Thanks
Sreedh

Sreedh,
I was wondering whether you could resolve this error?
Would appreciate if you can convey the resolution.
I am getting the same error - ( BOE XI 3.1 ).
Thank you,
PK

Problem while creating Dimension in AW...

Hi
I m facing error while creating the Dimension in AW.
i have done the following steps.
1.I have created the AW name "myfirstaw" and i can see the AW in my DB.
2.I have a DIm table Products.
3.i have attached the AW using below command
EXECUTE DBMS_AW.AW_ATTACH('MYFIRSTAW', TRUE);
4.Atlast i m trying to create dimension using
execute dbms_awm.create_awdimension ('OMTEST', 'PRODUCTS', 'OMTEST','MYFIRSTAW', 'AW_PROD');
then i m getting error :
SQL> execute dbms_awm.create_awdimension ('OMTEST', 'PRODUCTS', 'OMTEST','MYFIRSTAW', 'AW_PROD');
ERROR Create_AWDimension. ___AW_CREATE_DIMENSION
The Source Dimension of
OMTEST.PRODUCTS does not exist.
BEGIN dbms_awm.create_awdimension ('OMTEST', 'PRODUCTS', 'OMTEST','MYFIRSTAW', 'AW_PROD'); END;
ERROR at line 1:
ORA-06510: PL/SQL: unhandled user-defined exception
ORA-06512: at "OLAPSYS.DBMS_AWM", line 975
ORA-06512: at line 1
Anyone knows why it is coming..
Pls help me to simulate the problem
Thanks in Advance.
Regards,
Anwar

Hi
I m facing error while creating the Dimension in AW.
i have done the following steps.
1.I have created the AW name "myfirstaw" and i can
see the AW in my DB.
2.I have a DIm table Products.
3.i have attached the AW using below command
EXECUTE DBMS_AW.AW_ATTACH('MYFIRSTAW', TRUE);
4.Atlast i m trying to create dimension using
execute dbms_awm.create_awdimension ('OMTEST',
'PRODUCTS', 'OMTEST','MYFIRSTAW', 'AW_PROD');
then i m getting error :
SQL> execute dbms_awm.create_awdimension ('OMTEST',
'PRODUCTS', 'OMTEST','MYFIRSTAW', 'AW_PROD');
ERROR at line 1:
ORA-06510: PL/SQL: unhandled user-defined exception
ORA-06512: at "OLAPSYS.DBMS_AWM", line 975
ORA-06512: at line 1
Anyone knows why it is coming..
Pls help me to simulate the problem
Thanks in Advance.
Regards,
AnwarI m also facing the same problem. Has anyone got a solution to this?

Cannot create AW using AWM from Schema Sales History in Oracle 10.1.0.3.0

Hi,
I have installed Oracle DB Enterprise Edition and Client 10.1.0.3.0 on Linux.
I create the schema SH using the scripts sh_main.sql, csh_v3.sql, lsh_v3.sql, psh_v3.sql and olp_v3.sql from the directory $ORACLE_HOME/demo/schema/sales_history. So far, everything is ok.
Next, I tried to create an analytic workspace from this schema using the analytic workspace manager. An error ocurred (see AAA...), because of the string "e-mail" in the dimension attribute of CUSTOMERS_DIM. Changing "e-mail" to "email" solved this problem.
During the next try, an error occured because of the PERIOD_END_DATE attribute (see BBB...). Can somebody find a solution to this problem?
Best regards,
Ralph
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
Creating analytic workspace...
Processing cube SALES_CUBE
Processing Creating Dimension : CHANNELS_DIM
Processing Creating Dimension : CUSTOMERS_DIM
Error Message from Server = ___AW_REFRESH_DIMENSION
E-MAIL is not allowed to contain non-standard form characters SH_AW.MYAW
Problem getting Attributes for:
SH
CUSTOMERS_DIM
You provided extra input starting at '$'.
In SYS.AWXML!__XML_VAL_PREFIX PROGRAM:
exists = exists(name)
Problem creating dimension:
CUSTOMERS_DIM
You provided extra input starting at '$'.
In SYS.AWXML!__XML_VAL_PREFIX PROGRAM:
exists = exists(name)
SqlException = ORA-06510: PL/SQL: unhandled user-defined exception
ORA-06512: at "OLAPSYS.DBMS_AWM", line 975
ORA-06512: at line 1
Error Code = 6510
Sql State = 65000
BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB
Creating analytic workspace...
Processing cube SALES_CUBE
Processing Creating Dimension : CHANNELS_DIM
Processing Creating Dimension : CUSTOMERS_DIM
Processing Creating Dimension : PRODUCTS_DIM
Processing Creating Dimension : PROMOTIONS_DIM
Processing Creating Dimension : TIMES_DIM
Processing Defining Load for Dimension: CHANNELS_DIM
Processing Refreshing Dimension : CHANNELS_DIM
Processing Defining Load for Dimension: CUSTOMERS_DIM
Processing Refreshing Dimension : CUSTOMERS_DIM
Processing Defining Load for Dimension: PRODUCTS_DIM
Processing Refreshing Dimension : PRODUCTS_DIM
Processing Defining Load for Dimension: PROMOTIONS_DIM
Processing Refreshing Dimension : PROMOTIONS_DIM
Processing Defining Load for Dimension: TIMES_DIM
Processing Refreshing Dimension : TIMES_DIM
Error Message from Server = Problem refreshing dimension:
TIMES_DIM
TIMES_DIM.PERIOD_END_DATE.ATTRIBUTE is not a Valid Attribute.
(AW$XML) AW$XML
In SYS.AWXML!__XML_HANDLE_ERROR PROGRAM:
then signal 'AW$XML' 'AW$XML'
SqlException = ORA-06510: PL/SQL: unhandled user-defined exception
ORA-06512: at "OLAPSYS.DBMS_AWM", line 1012
ORA-06512: at line 1
Error Code = 6510
Sql State = 65000

Please apply the OLAP 10.1.0.3.0A or OLAP 10.1.0.3.0B patch to both the Database Server and Database Client. Do not run Oracle OLAP on the RDMBS 10.1.0.3 patch set without either one of these OLAP specific patches:
OLAP 10.1.0.3.0A patch (PS #3769360 on MetaLink)
OLAP 10.1.0.3.0B patch (PS #4045047 on MetaLink)
The B patch contains all the fixes found in the A patch, plus additional fixes. Therefore, I would recommend B over A.

Unable to create dimensions in schemas that use synonyms

I have three schemas (s1, s2 and s3) that use synonyms to reference different tables. S1 and S2 have all tables, equally distributed in their schema. S3 is an end user who has just synonyms.
I tried creating dimensions in any of them, table or view not found error is encountered.
I created required tables in my schema (user: meka) and I was successfully able to create dimensions. The following command worked in "meka", not any of the three schemas (s1, s2 and s3).
CREATE DIMENSION country
     level city_id is lu_city.CITY_ID
          level state_id is lu_state.STATE_ID
          level country_id is lu_country.COUNTRY_ID
hierarchy country_hier (
city_id CHILD OF
state_id CHILD OF
country_id
JOIN KEY lu_city.STATE_ID references state_id
JOIN KEY lu_state.COUNTRY_ID references country_id
ATTRIBUTE city_id DETERMINES (lu_city.CITY_NAME)
ATTRIBUTE state_id DETERMINES (lu_state.STATE_NAME)
I tried a few combinations, including specifying fully qualified table names (s1.lu_city.city_id, etc); created views at user S3 tried the same. All of them were unsuccessful. I am using Oracle 11g R2, here is screen shot:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Data Mining and Real Application Testing options
Q: How can I create a dimension in a schema where tables do not exist. They exist in another schema.
Edited by: user8967661 on Jan 12, 2010 2:12 PM

This is resolved.

OBIEE Evaluate - "Essbase error : Repeated dimension in MDX query"

Hi,
I'm using OBIEE 11.1.1.6.2 BP1 on top of Essbase.
I have a project dimension in Essbase with three levels - Total Project -> Project Class -> Project. I have created a new logical column in OBIEE to query two levels from project dimension, using evaluate function as below:
Evaluate('%1.Members, %2.Members', "Oracle Hyperion Planning"."ASOCUBE".""."Planning"."Gen2,Project" , "Oracle Hyperion Planning"."ASOCUBE".""."Planning"."Gen4,Project" ).
The above column when used in analysis, works fine, returning "Total Project" and all the projects. It breaks however when any filter is applied on project dimension with the following error:
"[nQSError: 96002] Essbase Error: Repeated dimension [Project] in MDX query".
I donot have any MDX skills and would appreciate if anyone can explain this error and provide any workaround for this. Here's the MDX that fails:
With
set [_Project0] as '{[Project].Generations(2).Members, [Project].Generations(4).Members }'
select
{} on columns,
{{[_Project0]}} properties GEN_NUMBER on rows
from [ASOCUBE.Planning]
where ([Project].[1000000-Treatment Plant])
Many Thanks

This issue regarding BIEE
because MDX is wrong
With
set [_Project0] as '{[Project].Generations(2).Members, [Project].Generations(4).Members }'
select
{} on columns,
{{[_Project0]}} properties GEN_NUMBER on rows
from [ASOCUBE.Planning]
where ([Project].[1000000-Treatment Plant])

Universe Designer: Error getting dimensions for cube

-Using Business Objects Edge 3.1 SP2
-SAP BW 7.0 (patch level 21)
This is quite odd behavior that seemed at first an authorization issue, but now I am uncertain.
-Attempting to create a Universe based on a Infocube.
-Universe connection is created with no problem using user 'ABC'
-Using Universe Designer on the BOBJ server, no issues creating the Universe
-Using Universe Designer on a users desktop, the Universe fails to create with error message:
A runtime exception has occurred. (Error getting dimensions for cube $0SD_C03 (catalog $INFOCUBE): Unknown error)
-Change the connection to use user 'DEF', the Universe creates just fine on the desktop
-Behavior is not exclusive to one BW object, happens no matter what 'ABC' tries to access from this desktop
So, at first I am thinking authorizations, but then the universe create would fail on the server as well. If it is environmental, what could possibly affect this behavior.
Any ideas before I submit to SAP Support?
Edited by: Kevin Smolkowicz on May 5, 2010 12:40 PM
Edited by: Kevin Smolkowicz on May 5, 2010 12:41 PM

Oddly enough it was an authorization issue.
When authenticating against the SAP source system from Universe Designer on either the workstation or server, both traces show a missing authorization for RFC_NAME = RASB
This setting is not found in referenced SAPu2019s guides or whitepapers under suggested authorizations for Universe create. What remains unexplained is why using the same credentials from 2 different computers had a different response.

Creating dimension

create dimension location_DIM
LEVEL REPORT IS (ACTIVITY_COUNTS.REPORT_ID)
LEVEL POST_CODE IS (ACTIVITY_COUNTS.POST_CD)
level district IS (ACTIVITY_COUNTS.DISTRICT_CD)
LEVEL county IS (ACTIVITY_COUNTS.COUNTY_CD)
LEVEL CITY_TOWNSHIP IS (ACTIVITY_COUNTS.city_TWNSHIP_NUM)
HIERARCHY REP_ROLLUP
(REPORT CHILD OF
POST_CODE CHILD OF
DISTRICT CHILD OF
COUNTY CHILD OF
CITY_TOWNSHIP
ATTRIBUTE POST_CODE DETERMINES (activity_counts.POST_DESC)
ATTRIBUTE DISRICT DETERMINES (activity_counts.DISTRICT_desc)
ATTRIBUTE COUNTY DETERMINES (activity_counts.COUNTY_desc)
ATTRIBUTE CITY_TOWNSHIP DETERMINES (activity_counts.CITY_TWNSHIP_DESC);
I followed this example.
CREATE DIMENSION products_dim
LEVEL product IS (products.prod_id)
LEVEL subcategory IS (products.prod_subcategory)
LEVEL category IS (products.prod_category)
HIERARCHY prod_rollup (
product CHILD OF
subcategory CHILD OF
category
ATTRIBUTE product DETERMINES
(products.prod_name, products.prod_desc,
prod_weight_class, prod_unit_of_measure,
prod_pack_size,prod_status, prod_list_price, prod_min_price)
ATTRIBUTE subcategory DETERMINES
(prod_subcategory, prod_subcat_desc)
ATTRIBUTE category DETERMINES
(prod_category, prod_cat_desc);
But I get this error
Error at Command Line:15 Column:12
Error report:
SQL Error: ORA-30342: referenced level is not defined in this dimension
30342. 00000 - "referenced level is not defined in this dimension"
*Cause: A reference to a level not defined within the dimension was found.
------------------------------Even this one is giving me reference error. The two tables do not have referential integrity constraints
create dimension location
LEVEL REPORT IS (ACTIVITY_COUNTS.REPORT_ID)
LEVEL POST_CODE IS (DISTRICT_COUNTY_POST_CITY.POST_CODE)
level district_code IS (DISTRICT_COUNTY_POST_CITY.DISTRICT_CODE)
LEVEL county_nbr IS (DISTRICT_COUNTY_POST_CITY.COUNTY_NBR)
LEVEL CITY_TOWNSHIP IS (DISTRICT_COUNTY_POST_CITY.city_township_nbr)
HIERARCHY GEOG_ROLLUP
(report CHILD OF
post_CODE CHILD OF
DISTRICT_CODE CHILD OF
COUNTY_NBR CHILD OF
CITY_TOWNSHIP
JOIN KEY (activity_counts.CITY_TWNSHIP_NUM) REFERENCES CITY_TOWNSHIP)
ATTRIBUTE POST_CODE DETERMINES (DISTRICT_COUNTY_POST_CITY.POST_DESC)
ATTRIBUTE DISRICT_CODE DETERMINES (DISTRICT_COUNTY_POST_CITY.DISTRICT_NAME)
ATTRIBUTE COUNTY_NBR DETERMINES (DISTRICT_COUNTY_POST_CITY.COUNTY_NAME)
ATTRIBUTE CITY_TOWNSHIP DETERMINES (DISTRICT_COUNTY_POST_CITY.CITY_TOWNSHIP_NAME);
tried to create this but not getting through got stuck in reference key
CREATE DIMENSION customers_dim
LEVEL customer IS (customers.cust_id)
LEVEL city IS (customers.cust_city)
LEVEL state IS (customers.cust_state_province)
LEVEL country IS (countries.country_id)
LEVEL subregion IS (countries.country_subregion)
LEVEL region IS (countries.country_region)
HIERARCHY geog_rollup (
customer CHILD OF
city CHILD OF
state CHILD OF
country CHILD OF
subregion CHILD OF
region
JOIN KEY (customers.country_id) REFERENCES country
ATTRIBUTE customer DETERMINES
(cust_first_name, cust_last_name, cust_gender,
cust_marital_status, cust_year_of_birth,
cust_income_level, cust_credit_limit)
ATTRIBUTE country DETERMINES (countries.country_name)
;

Using the CWM1 views through Enterprise Manager Dimensions/Lookups must be TABLES, fact tables can be VIEWS
In the CWM2 set up you can utilise VIEWS for all componenets. Furthermore, my data mart has a distributed environment where reference data is physically located in a remote database.
In order to reference the remote tables I have considered database synonyms, but this did not work.
Secondly, we created a number of views containing DBLINKS to the remote database. This works but performance can be poor because the SQL generated by the BI Beans, makes several calls to the complex view to create hierarchies, retrieve selections etc. which can be inefficient.
I think my next steps will be to create Materialized views on the data mart from the remote reference database.
Finally, run the following statement before your CWM2 statements. cwm2_olap_manager.Set_Echo_ON will provide a complete output from your statements rather than just "Procedure Completed Sucessfully"
SET ECHO ON
SET LINESIZE 120
SET PAGESIZE 50
SET SERVEROUTPUT ON
execute cwm2_olap_manager.Set_Echo_ON;

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

TxsOqDefinitionManager Error Creating Dimension in AWM 11.1.0.6 A

Similar Messages

Maybe you are looking for