Edit dimension in OWB

hi ,
i have oracle DB 10g and OWB 10g .
i have made 4 dimensions and 1 cube with OWB ( MOLAP implementation).
validate and generate and deploy all of them .
when i have made some edition in one dimension and wanted to deploy it , OWB does not let me becuse it wants to drop and create that dimension again and i have used that dimension in a cube .
what is the solution ?
how i can edit a dimension with OWB and deploy agian ?
thank u in advance for your help .
regards
Padideh

Hi Padideh
With the MOLAP implemented cubes there is no change management so you will have to drop and recreate when changing dimensions. With cubes you can build another cube with identical shape as the base cube and build measures based on the existing cube which is a nice way to define a base cube with measures and extensions.
Cheers
David

Similar Messages

Help with Skip Level dimensions in OWB 10.2 (Paris)

Hi all,
I'm trying to understand how to set up and use a skip level dimension in OWB 10.2. A simplified version of my hierarchy would be:
Plant - Equipment - Assembly - Item
Where Some Items connect directly to equipment and others connect to assemblies. How sould I define this in the Dimension wizard or editor in OWB?
Can I create a single dimension hierarchy and in the Item level put Skip Level as "Equipment"?
OR
Do I need 2 hierarchies - one Plant-Equipment-Assembly-Item and the other Plant-Equipment-Item?
There is an example in the Users guide that created 2 hierarchies -
TOTAL-GROUP-PRODUCT and TOTAL-PRODUCT
In the example, they show the PRODUCT in TOTAL-PRODUCT setting the skip level field. I don't understand why that is necessary if it is 2 seperate hierarchies.
Any help/guidance would be appreciated!
Thanks,
Mike

Hi Donna,
Perhaps JP can expand on his answer. In my case, I did go the route of seperate hierarchies. It is a bit of work defining multiple hierarchies and my example was much simplified. We actually have about 8 levels in the primary hierarchy and 6 levels in the second. It does work well with the cubes by using 2 roles for the dimension - one for each hierarchy.
I saw that truly "ragged hierarchies" or "level hierarchies" can be defined in OWB and deployed as MOLAP but MOLAP has quite a few drawbacks - no SCDs and requires analytic workspaces etc. I haven't done anything with these yet.
Our data is a classic manufacturing Bill of Material so the level hierarchy would be the easiest to manage, though I'm not sure how easy it would be to report on! I do want to shield my end-users from CONNECT-BY madness.

Spatial dimension in OWB

Hello,
Actually, I'm trying to use sdo_geometry data type in a DW dimension in OWB. But this type is not shown in the datatypes list of attributes in OWB. Does anybody have an idea how to do it ? Thanks.

But MDSYS.SDO_GEOMETRY doesn't appear in the data types list when creating a dimension, that's the point !

How to create a working day/holiday attribute in Time Dimension with OWB ?

Hello everybody,
I am trying with no success to create a Time Dimension (with the wizard it would be easier...) with a working day or holiday attribute (0 or 1) to be able to calculate measures only on working time !!! I am totally sure it's possible, obviously, but I found nothing on forums... Could you help me ??
I use OWB 11g, I need all fiscal year/quarter/month/week and all calendar year/quarter/month/week attributes so without any wizard it would be quite impossible... thank you for your help !
NB: of course I know how to define if a day is a working one or not, but I currently can't add any columns in Time dim created with wizard...
Francois
Edited by: [email protected] on Jun 15, 2009 8:24 AM

Hi,
First of all, thanks everyone for your help.
I did several tests this morning.
First of all, i've tried with time_from = 000000 and time_to = 235959 (23:59:59 CET) and the activity has been created with Time From = 04:00:00 and Time To = 03:59:59
Strange no ??
I've also tried with 230000 for time from and time to but the activity has been created with Time From = 03:00:00 and Time to = 03:00:00
I cannot understand the logic behind....
Thanks,
Johnny Baillargeaux

Edit dimensions

I run OWB 10.2.0.3 and have some problems.
I create a dimension following all the steps in Oracle Tutorial. When I later want to edit it, and double-click on the dimesion to open the editor. I get a totally empty data object editor.
What has I done wrong?
Is there anything I forgot to install?
Any parameter that should have a certain value?

When I run
SELECT *
FROM dba_registry
WHERE comP_name LIKE '%OLAP%'
I get:
0 rows selected
When I run
SELECT *
FROM dba_registry
COMP_ID COMP_NAME VERSION STATUS
CATALOG Oracle Database Catalog Views 10.2.0.3.0 VALID
CATPROC Oracle Database Packages and Types 10.2.0.3.0 VALID
JAVAVM JServer JAVA Virtual Machine 10.2.0.3.0 VALID
XML Oracle XDK 10.2.0.3.0 VALID
CATJAVA Oracle Database Java Packages 10.2.0.3.0 VALID
EXF Oracle Expression Filter 10.2.0.3.0 VALID
EM Oracle Enterprise Manager 10.2.0.3.0 VALID
7 rows selected
What am I missing and what shall I install, my problem is that I am not allowed to install anything on server level I have to ask our server group to do it. So I need instructions to pass on to them.

How to handle parent-child dimension in OWB?????

i have a dimension have many levels,and the amount of levels is varing,so i cannot use the wizard to define my dimension ,seems with OWB i can only define dimension with certain amount of levels.......
my dimension data is stored with this format:
child parent
Los Angles US
US WORLD
it is called a parent-child relation ,how can i define dimension with parent-child relation witn OWB...
Can OWB do it ?????

i have a dimension have many levels,and the amount of levels is varing,so i cannot use the wizard to define my dimension ,seems with OWB i can only define dimension with certain amount of levels.......
my dimension data is stored with this format:
child parent
Los Angles US
US WORLD
it is called a parent-child relation ,how can i define dimension with parent-child relation witn OWB...
Can OWB do it ????? You must define a dimension, define the dimension levels and the hierarchy inside the dimension (a hierarchy can have as many levels as you want, parent-child relationship is a normal hierarchy concept - no rocket science here). Then you have to map the data source for the dimension levels appropriately. Please refer to the user manual, chapter 4 ("Defining dimensianal targets") for details.
Regards:
Igor

Role Dimensions in OWB

hi,
I have a fact table linked with the same dimension table more than once. The fact got validated properly, but when trying to execute the mapping ,values are not getting populated in the fact table. I came to know that such dimensions are known are role playing dimensions and I would like to know how can this be implemented in OWB . My Project is currently using OWB (9i) and is planning to migrate to 10g R2. Can somebody plz help me? I am stuck with two of my mappings due to this issue. Plz help
thanks in advance..

Does anyone know if the bug with roles has been fixed in 11, I suspect not?
I'm doing some testing with OWB Client 11.1.0.6.0 and Server 11.1.0.1.1 and I'm hitting problems when deploying a Cube.
ORA-06510: PL/SQL: unhandled user-defined exception
ORA-06512: at "OLAPSYS.CWM2_OLAP_CUBE", line 99
ORA-06512: at line 2
The cube has 14 dimensions, 7 of which are roles (different dimensions). If I remove one of the dimensions that has 3 roles and replace it with 3 normal dimensions then the cube deploys ok.
Cheers
Si

Error Deploying Dimensions in OWB

Hi,
I am using OWB 10R2. Created an dimension with MOLAP but when i deploy the dimension i get error as :
ORA-29540: class oracle/AWAction/Interaction does not exist
ORA-06512: at "<user>.INTERACTIONEXECUTE", line 1
ORA-06512: at "<user>.OWB$XMLCLOB_<user>", line 321
ORA-06512: at line 3
I have OLAP configured with database(10.1.0.3.0) but the user with olap configured in database is olapsys and not the TARGET_USER.
I granted the role OLAP_USER to the TARGET_USER. What else i am missing.
Any help will be appreciated.
Thanks,

goto weblogic console and test the mds connection pool. It would show you whats going wrong in the database connection.
--Prasanna

How does Disco handle multiple hierarchies in dimension from OWB?

Hi,
I have a ROLAP cube developed with OWB. All the dimensions have only one hierarchy at the moment. I derive the EUL from this cube.
One of the dimensions now need another hierarchy. Does anyone know how Discoverer handles multiple hierarchies in a dimension? How would you be able to choose which hierachy to use in a Disco worksheet? Can you actually use multiple hierarchies or only the hierachy set as the default?
Thanks

Hi,
Yes, you can set up multiple hierarchies in Discoverer for the same EUL items. When you drill down you have the option to select which hierarchy you use.
Rod West

Implementing Role Dimensions in OWB 9.0.4

Hi all,
The question :
Implementation of a star schema ( cube) containing more than one time dimension role. For example; Connection Date, Disconnection Date, Order Date. These are all roles of the same time dimension.
The manual process :
If I wasn't using OWB. I would create views of the Time table and create a primary key on each view. Then within the Fact (cube) create foreign keys ( rely only) to each of the 3 views above.
Done ! The meta data and any OLAP tools would pickup the relationship.
How can this be done in OWB 9.0.4.
How can I create multiple roles for a Dimension for a cube. Given that only dimensions (not views) can be linked to the cube within the wizard.
I do not want to create multiple instances of the time table to allow multiple time dimensions ...
Can anyone help.

Thomas,
Not quite sure what you mean with "in the database design itself" but if you apply what Mark replied you will get this within the database design...
In other words you will get an fk to the time dimension for each of the roles. Hence the FK is the actual role. There is no need as far as I know to create the views. The are as I presume implemented as select * from dimension.
The additional draw back (I think) from views is that the query re-write might get less sophisticated in that it can't see the hierarchies of the dimension any more and will not some MVs leading to slow performance.
So simply create multiple keys and ensure the correctnaming. Then push it into Disco for example.
Jean-Pierre

Importing existing dimensions into OWB

Does any body know how to import an existing Dimension, created in an Oracle database into OWB so that the dimension definition appears under the dimension tab.

Hi,
I think you can't import a dimension from data base.you have to create throught OWB.
Regards
naren

Rapidly changing very large dimensions in OWB

Hello,
How is rapidly changing very large dimensions supported in OWB?
Is it supported directly by the tool or do we have to depend on PL/SQL?
If supported, Is it supported by all versions of OWB from 9.0.3 thru 10g?
TIA

Hi
Use merge (insert/update or update/insert) if you have to update and insert too.
Ott Karesz
http://www.trendo-kft.hu

Chunking + dimension operator+ owb 11g very slow

Anbody using chunking for loading SCD type 2 dimesnions in Oracle 11g.
Can it be used with dimension operator.
Also what is Max Chunk iterator count - can't see in the documentation?
Thinking about dicthing domension operator for one of our SCD type 2 as so slow.
Also doing simple thing like deploying mapping very slow - anybody seen this - other previous version used also slow but not as slow.
Other programming development tools thing on PC leads me to think problem with OWB.
Do we need to purge repository auidting tables?
If so is there a script to do this in Oracle 11g.
Any ideas/thought on above much appreciated.
Many Thanks

Hi,
Thanks for the excellent suggestion.
Have run other mapings which maintain SCD type 2 using dimesnion operator behave similary to 10g. - have raised issue with this particular mapping with Oracle - awaiting response.
One question - when look at the mappings which maintain SCD Type 2s looks to join on dimension key and the surrogate ids.
What is best practice regarding indexing of such a dimension, e.g is it recommended to index dimension key and the surrogate ids along with the natural/nbusiness keys?
Thanks

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.

OWB 10.2 - How are you handling time dimensions?

Hi all,
I am struggling with what should be a simple thing to do. I want to create a time dimension and then have many "roles" or aliases for the time dimensioin WITH UNIQUE COLUMN NAMES across all of the roles.
When the time dimensions are deployed to Discoverer, I want every one of them to have unique names and the column names within the time dimension have a unique prefix so that report users know which date column is from which table or dimension.
Here's what I've done and failed at:
1. Use the time dimension wizard - I can create any number of dimensions and corresponding tables BUT all of them have the same column names and I would have to manually change each and every one of them to get unique names (which may not even be possible with the wizard). Also, because I require ISO weeks, I can't really use the wizard at all.
2. Manually create a time dimension (that supports ISO weeks) and create multiple "roles" for it:
Thanks to a bug, I cannot exceed 4 roles without OWB crashing. Even with those 4 roles, when deployed to Discoverer, every attribute within the item folders has the same name. When I drag them to a report, there is no way to tell one from another. Is there some way I could do this without having to manually rename hundreds of columns?
3. I wrote an elaborate SQLPlus script to copy and prefix dimensions and tables from a base dimension and table. When I then import the Dimension to OWB, the metadata for business identifier and surrogate identifier is not there and any cubes using those dimensions do not work with these attributes missing. I can't find a way to cleanly reverse engineer these into OWB.
I have a cube with 12 dates - each of which should be a foreign key to a date dimension.
How can I have all of these be uniquely named with uniquely named columns?
How can I make it easy for my reporting users to select dates onto their reports?
I hope I am missing an obvious solution, because so far, I cannot see where Oracle Warehouse Builder supports such a basic data warehousing concept.

Well, since I'm the only one obsessed with time dimensions I guess, here is my ugly workaround:
1. I create a base time dimension in OWB which I named 'ATLAS_TIME_DIM'
2. I run the OMB script below which clones the dimension and table and renames the columns and attributes with a user supplied suffix. The end result is I get a full copy of the time dimension metadata with uniquely named columns.
You then have to deploy the objects, and with SQLPlus, ensure that the table gets its data copied from your original table. Hope it helps someone until we have better Time dimension support from OWB.
OMBCONNECT repos/password@SERVERNAME:1521:sidname
# Prompt for new Dimension name and prefix
puts -nonewline "Please enter name for new Dimension: "
gets stdin newDim
puts -nonewline "Enter Prefix for Dimension table columns: "
gets stdin dimPrefix
# Change into ATLAS_DW module in project ATLAS_DW
OMBCC 'ATLAS_DW'
OMBCC 'ATLAS_DW'
# Copy the ATLAS_TIME_DIM to this dimension
OMBCOPY DIMENSION 'ATLAS_TIME_DIM' TO '$newDim'
# Set the business name
OMBALTER DIMENSION '$newDim' \
SET PROPERTIES (BUSINESS_NAME) VALUES ('$newDim')
# Unbind the dimension from original table
OMBALTER DIMENSION '$newDim' \
DELETE BINDING
# Bind to new table
OMBALTER DIMENSION '$newDim' \
IMPLEMENTED BY SYSTEM STAR
# Add a prefix to all of the Dimension attributes
set attrList [OMBRETRIEVE DIMENSION '$newDim' GET DIMENSION_ATTRIBUTES]
foreach attrName $attrList {
OMBALTER DIMENSION '$newDim' \
MODIFY DIMENSION_ATTRIBUTE '$attrName' RENAME TO '$dimPrefix\_$attrName'
# Add a prefix to all level attributes of the Dimension
set levelList [OMBRETRIEVE DIMENSION '$newDim' GET LEVELS]
foreach levelName $levelList {
set levelAttrList [OMBRETRIEVE DIMENSION '$newDim' \
LEVEL '$levelName' GET LEVEL_ATTRIBUTES]
foreach levelAttr $levelAttrList {
OMBALTER DIMENSION '$newDim' MODIFY \
LEVEL_ATTRIBUTE '$levelAttr' OF LEVEL '$levelName' \
SET PROPERTIES (BUSINESS_NAME) VALUES ('$dimPrefix\_$levelAttr')
OMBALTER DIMENSION '$newDim' MODIFY \
LEVEL_ATTRIBUTE '$levelAttr' OF LEVEL '$levelName' \
RENAME TO '$dimPrefix\_$levelAttr'
# Add a prefix to all of the table columns except DIMENSION_KEY
set columnList [OMBRETRIEVE TABLE '$newDim' GET COLUMNS]
foreach colName $columnList {
if { $colName == "DIMENSION_KEY" } {
puts "$colName"
} else {
OMBALTER TABLE '$newDim' \
MODIFY COLUMN '$colName' SET PROPERTIES (BUSINESS_NAME) VALUES ('$dimPrefix\_$colName')
OMBALTER TABLE '$newDim' \
MODIFY COLUMN '$colName' RENAME TO '$dimPrefix\_$colName'
puts "$dimPrefix\_$colName"
OMBSAVE
OMBDISCONNECT
Message was edited by:
mike_fls

Edit dimension in OWB

Similar Messages

Maybe you are looking for