OWB10gR2

Hello,
I was trying to upgrade Source locations to Control Center. It was giving version control problem. My source is Oracle 9.2. Why it is not upgrading into control center? Source can be any type or any version. Why it is giving error saying that Version problem. If it is Target it should be 10g. If it is source it can take any version right. Please anybody can solve this?
Thanks
Santi

Hello,
You are right that source can be any thing.
But someone has to define what is the source format? so if your source has changed you should notify this.
Hope this answer your question.

Similar Messages

Dynamically generating flat file using OWB10gr2

Hi,
I am trying to generated an XML file using OWB10gR2.
It is achievable to create a predefined file ie with static name or add sysdate into the file name,but can we name the file depending on the Request Id which can be provided as an Input to the mapping.
Any suggestions will be helpful.
Regards,
PHD.

You can define expressions which you might be able to be creative with;
http://blogs.oracle.com/warehousebuilder/2007/07/dynamically_generating_target.html
Cheers
David

Always "Read-only" in dimension detailed view, OWB10gR2

In OWB10gR2, let's get any dimension open in the "Data Object Editor", then click on dimension object, right button menu and select "Detail View". The editor shows as expected, the dimension itself and the underlying table, however in the lower pane where we can select tabs(Storage, Attributes, Levels, etc.) it always says "Read-only". Why is that? According to my security settings, I do have full control over these objects.
Can anyone explain this to me?
Thanks,
vr

Everyone, the "detail view" is read only becuase you aren't allowed to change settings here. If you notice, there should be a set of tabs at the top that say "relational", "dimensional", "business definition", and something else for the detail view (can't remember now). It appears that you can only change settings when on the "dimensional" tab - so just click there and you'll be good to go.
Hope this helps,
Scott

Mainframes - OWB10gR2/OWB11gR1

Hi All,
We will be using OWB10gR2 running on UNIX box to extract data from Mainframes. We have two different source type (VSAM and DB2 7.0). How does OWB connect to mainframe ? Can we directory access mainframe VSAM files or we need to import them into Unix box and then read it ? Can somebody show a path of how it is to be done? How is DB2 connection on mainframe is set up?
Should we go with OWB11gR1 ?
Thanks,
Sam.
Message was edited by:
user571269

Bruno,
I know that option is available with table operator but that doen't help me. I am thinking of raising a TAR with oracle. I was waiting for response from this group but looks like its a bug. If i don't get a solution by this weekend i will raise a TAR.
Thanks,
Sam.

OWB10gR2 executions with non-default target accounts

Hi all,
Is there a way in OWB10gR2 to run the control center service with another user than the owner of the accounts, and the same for process flows that need to run with another account than the workflow user and mappings with another account then the deployment user.
The reason is that my client wants all object owning accounts to be locked and runs must be done with accounts that have no objects at all. This is in contradiction to OWB deployment and execution way of working
Peter

Hi all,
Is there a way in OWB10gR2 to run the control center service with another user than the owner of the accounts, and the same for process flows that need to run with another account than the workflow user and mappings with another account then the deployment user.
The reason is that my client wants all object owning accounts to be locked and runs must be done with accounts that have no objects at all. This is in contradiction to OWB deployment and execution way of working
Peter

OWB10gR2 process parameter error

Hi,
I have OWB 10gR2 with 2.6.4 Workflow on a 10gR2 database. I create a process flow in owb with a process parameter. The process contains a mapping with an input parameter. I bind the process parameter to the mapping parameter.
When I deploy the mapping to workflow I see that the mapping and process parameters are not deployed to workflow (wf_activity_attributes). And when I run the process from the control center manager and give a value to the process parameter this value does not appear in the runtime either (all_rt_audit_execution_params).
It works fine with OWB 9.2 and 10.1.0.4 as well.
Does anybody have an idea about this problem? What have been changed in R2 OWB in this territory? And how this problem can be solved?
Thanks,
Gabor

could you elaborate a little bit on that?
I have some issues with all my Process flows, after migrating from 10.1.0.4 to OWB10gR2.
When I try to generate the PF packages it fails with internal error:
oracle.wh.service.sdk.runtime.QueryException: null
- Internal Error Unknown System Parameter PARAM0 for executionAdapterId= 5 executionOperatorId= 1080
I can not delete this parameter from the process flow (the delete option is disabled when I click on in), and it doesn't complain about another parameter, PARAM, that I created after the migration.

OWB10gR2 and target schema a DB2 database

Does the OWB10gR2 support the target schema to be a DB2 database using a ODBC connection ?

Yes. Just add the table from the DB2 module to the map as a target. note the map still deploys to an oracle location (since the oracle db is the etl engine).

Error coming while schedle the job in OWB10gR2

Hi , I have done one pre schedule job in OWB and assigned that job to one Map named by newone. but its not working as per schedule and when manually start the exec of map it gives an error .
anybody can tell why scheduling gives an error such that
"SCOTT.MMB_NEWONE_JOB" has an invalid END_DATE
ORA-06512: at "SYS.DBMS_ISCHED", line 731
ORA-06512: at "SYS.DBMS_SCHEDULER", line 1158
ORA-06512: at line 1

Duplicated thread at schedule option in owb10gR2

OWB10gR2 - Cube with relations to a dimension with more than one hierarchy

Hi,
I have defined a time dimension with two hierarchies. The standard hierarchy with the levels year-> month-> day,
and a week hierarchy with the levels year-> week-> day.
When I define the cube i choose dim_time on the dimension tab of the cube and select the level day for that dimension since this is the lowest level of both hierarchies.
When I validate the cube I get the following error Message: VLD-0398: In the Cube test_cube, the dimension DIM_TIME has 2 hierarchies but Cube does not have reference to all lowest levels of these hierarchies.
Validation details: The Cube should refer to a leaf levels of all multiple hierarchies of the Dimension.
Do I have to add the dimension to the cube several times? or is it maybe another way to fix this? To me it seems a bit messy to add a dimension for each hierarchy.
And just as a comment, Yes i know OWB now has a time dimension wizard but I have chosen not to use this at the moment.. ;)
Regards Ragnar

Hi, i assume this logic is for Dimension formula?
If you have multiple hierarchy like ParentH1 and ParentH2 you should use FormulaH1 and FormulaH2 and not FORMULA column.
in FORMULAH1
[Account.H1].[Account_A] / [Account.H1].[Account_B]

SETTING PROPERTIES FOR A MAPPING VIA OMBPLUS ISN'T WORKING (OWB10gR2)

Hi, i have a problem with OMBPLUS:
I have a script which creates a mapping and then is supposed to change properties for the mapping. The script worked in previous releases of OWB but after upgrading to 10gR2 I get an error that DEFAULT_OPERATING_MODE property does not exist.
Does anyone know why I get the error?
/thanx Joel
When running the script the output looks like this:
CREATE MAPPING 'XXX_1_IN'... DONE
DEFAULT_OPERATING_MODE={SET BASED FAIL OVER TO ROW BASED}
ALTER MAPPING PROPERTIES FOR 'T_A_TEST_XXX_1_IN'...
OMB02902: Error setting property DEFAULT_OPERATING_MODE of T_A_TEST_XXX_1_IN: MMM1034: Property DEFAULT_OPERATING_MODE does not exist.
-- ALL DONE --
The script:
set temp_module "TMP"
set tmp_table1 "XXX_1"
set tmp_table2 "XXX_2"
set map_name "XXX_1_IN"
puts -nonewline "CREATE MAPPING '$map_name'... "
OMBCREATE MAPPING '$map_name' \
ADD TABLE OPERATOR '$tmp_table1' BOUND TO TABLE '../$temp_module/$tmp_table1' \
ADD TABLE OPERATOR '$tmp_table2' BOUND TO TABLE '../$temp_module/$tmp_table2' \
ADD CONNECTION \
FROM GROUP 'INOUTGRP1' OF OPERATOR '$tmp_table1' \
TO GROUP 'INOUTGRP1' OF OPERATOR '$tmp_table2'
OMBCOMMIT
puts "DONE"
set prop [OMBRETRIEVE MAPPING '$map_name' GET PROPERTIES (DEFAULT_OPERATING_MODE) ]
puts "DEFAULT_OPERATING_MODE=$prop"
puts -nonewline " ALTER MAPPING PROPERTIES FOR '$map_name'... "
OMBALTER MAPPING '$map_name' \
SET PROPERTIES (DEFAULT_OPERATING_MODE) \
VALUES ('SET BASED')
OMBCOMMIT
puts "-- ALL DONE --"
puts ""
OMBDISCONNECT

Hi, don't look at the script it was copied and pasted from an old thread. The problem is the error I get when trying to execute:
OMBALTER MAPPING 'map_name' \
SET PROPERTIES (DEFAULT_OPERATING_MODE) \
VALUES ('SET BASED')
OMB02902: Error setting property DEFAULT_OPERATING_MODE of map_name: MMM1034: Property DEFAULT_OPERATING_MODE does not exist.
//Joel

How to cope with surrogate id's after migrating to OWB10gR2

We are busy converting an OWB 9.2 environment to OWB 10gR2.
I already had problems with the way dimensions and cubes are used in OWB 10gR2.
Some of my dimensions will have a steep growth curve because of the level rows that are inserted into the new dimensions. These new rows exist to enable you to link cubes to dimensions at all levels and not only to the lowest level.
But when building the new mappings surrogate keys will also be used to make the join between dimension and cube but this again causes problems for existing reports.
In OWB 9.2 we prepared the cubes and dimensions in the staging area and then loaded them into the data warehouse.
We can still keep the existing columns in the newly defined dimensions we have to add the surrogate keys. But when loading data with the new dimensions and cubes the cubes will refer to the dimension with the new surrogate id’s and not with the old id’s which the business keys are now. So we are losing the relation between cube and dimension based on the business key and we have it now based on the surrogate key.
But the reports we have (made with Information Builders) are still working with the relationships based on the business id’s but since the foreign keys in the cube refer to the surrogate id’s instead of the bushiness id’s the reports will return without results.
I know I can resolve it by redesigning the reports but this is a lot of work and not the way we want to go.
My alternative solutions are
1.keep the new dimensions
but rename them
make views with the old dimension names
in the views switch the old business id and surrogate
the reports will then work with the views and the old joins will keep
on working
2.do not use dimensions and cubes
migrate the mappings to use tables , as a matter of fact this is what
you get after importing a 9.2 MDL into 10.2
no change in table names
the reports keep on working
Alternative solution 1 is rather dangerous because the column names are switched; this makes the model more difficult to understand
Alternative solutions can become a problem if we want to use slowly changing dimensions, we have to build them as we would have done in OWB 9.2, this leads to complex mappings.
Are there any other alternatives, can somebody advise for the best answer to these challenges

Well, couple of ideas here.
First off, do you HAVE to use levels in the dimension? For some of our dimensions, we just define a single "default" level, and tie all attributes to it. For example, with a time dimension, we'd define a default level, and then tie month_id, month_name, quarter_id, quarter_name, year_id, and year_name to that default level. This works out well - you basically get a "flat" dimension with all attributes on the row, thus preventing the generation of keys for the other levels. You'll still get a DEFAULT_LEVEL_KEY, but it will always equal the dimension key and you can just ignore the column.
FYI - I've just started playing with OWB 11gR1, and I discovered a few minutes ago that when setting up a dimension level, you don't appear to have to have the surrogate_id attribute turned on. Not sure if this works yet, will let you know.
Last and not least, I read your problem re: the business keys vs. surrogate keys to be "we used business keys instead of surrogate keys as the dimension PKs and fact table FKs on our initial DW, and now we have to migrate that...where OWB of course wants to use surrogates. Couple of thoughts. First off, I don't think you're going to get any auto-magic way to do this - using business keys instead of surrogate keys is definitely non-standard.
The one suggestion I would have is to do this: keep the original business IDs on the fact table as their own columns. Set them us as "measures" with a data type of varchar2 or whatever they already are. OWB will still of course create the "proper" FK columns based on the surrogate keys, but your users will still be able to join based on the "old" business id joins. The only real price you'd have to pay for this option is a) it takes more space per row on the fact table, and b) you'll probably have to do some indexing. OWB will build the proper bitmap indexes on the surrogate keys, but you'll probably want to add bitmap indexes on the business ID columns.
Hope this helps,
Scott

Dynamically changing flat file target location in OWB10gr2.

Hi,
We have a requirement where in we are suppose to load a flat file from relational tables and the location of the flat file needs to be configurable at runtime.
Please suggest if this is achievable.
Regards,
PHD
Edited by: user1662077 on Jun 17, 2009 10:08 PM

See the post here for dynamically generating target file names using the OWB file operator as a target;
http://blogs.oracle.com/warehousebuilder/2007/07/dynamically_generating_target.html
Other techniques also include using a table function as a target.
Cheers
David

OWB10GR2 - Error when try to use 'MOD' function in an Expression

Hi
I'm trying to use the MOD function in an expression, e.g. mod(44,12), however, when I validate I get the error:-
Line 2, Col 18:
PLS-00201: identifier 'MOD' must be declared
Line 0, Col 1:
PL/SQL: Statement ignored
Has anyone else come across this problem, and can anyone please suggest a solution?
Thanks
GB

Not yet, thanks for the suggestion.
If you use MOD in an expression or Constant, the expression does not validate but the mapping itself does validate, deploy and runs ok. So
This issue has been reported as a bug therefore for the time being we can just ignore the expression validation message.

How to use pluggable mappings in OWB10gR2

Sorry, yet another newbie question... (btw, boy I really wish the Users Guide was a lot more informative...)
I've created a simple pluggable mapping called "closed_date" that takes a few input data elements (closed date, account status, time since last reported) and does some simple expression logic to come up with a final "closed date" output attribute and an "open account indicator" field.
Now, when I'm trying to actually use the pluggable mapping inside of an ETL map, I get the following error:
"API8003: Connection target attribute group is already connected to an incompatible data source. Use either a Joiner or Set operator to join the upstream data first before connecting it to this operator"
Basically, all of the data is coming out of a big JOINER operator where I join 4 or 5 tables. Then I want some of the attributes to go directly to the target dimension operator, but I also want this pluggable mapping to sit between the JOINER and Dimension to do the translation.
What am I doing wrong - the expressions in the pluggable mapping are exactly the same as the ones I removed from the process flow (when it worked fine)?
Thanks,
Scott

bump!

How to schedule Process Flow in OWB10gR2 ?

Hi,
I have a mapping and a corresponding process flow that has the mapping within. Both the mapping and process flow are deployed successfully and they also execute successfully when executed from control center.
Now I want to run the process flow daily at 4 am in the morning. I have created a schedule and defined the parameters. Then for the process flow, I have added the schedule to the "Referred Calander". Then in control center I got a new object with _JOB as suffix. I deployed that as well and that was successfull. This implies that I have now a job that is scheduled to run daily at 4 am.
But the next day when I checked the target table that the mapping (wrapped in the process flow which in turn was scheduled to run at 4 am ) was supposed to insert some records, there was no record at all !!! Seemed to me that the job was not kicked off at all at the specified time.
I am using --
OWB client version : 10.2.0.1.31
OWB repository version : 10.2.0.1.0
Oracle Workflow Version : 2.6.4.0.0
Database version : 10g Enterprise edition release 10.2.0.1.0
Does anyone have any idea how do I make this arrangement running?
Regards,
Swagata

Chino -
Once you start the job, do you have to leave the "Job Details" window open in order for teh scheduled task to run?
thanks for the help ....
txb

OWB10gR2 Repository Browser hangs on report call

Hi,
after weeks of normal work with OWB Repository Browser, it started recently to hang up in the moment when an "Execution Job Report" (in column "Related Information") is called. No difference if error, mapping or workflow process report. We don't know which change in the system may have triggered this. Problem seems not to be in the database (no change in session after clicking the link is noticed). The OC4J windows gives no further log info and I can't find any log file in the J2EE directory. When trying to shut down the OC4J session regularly it brings:
06/09/15 11:41:43 Shutting down...
06/09/15 11:41:45 Thread named: Thread[HttpRequestHandler-3945515,1,ApplicationServerThreadGroup] cannot be interrupted
06/09/15 11:41:45 Thread named: Thread[HttpRequestHandler-30624226,1,ApplicationServerThreadGroup] cannot be interrupted
The DOS box has to be closed the brutal way which recovers after restarting.
some ideas around
regards
Thomas

indeed, it is likely that the report was simply hanging in SQL execution. did you check that before you purged? What can occur is that the statistics for the RT schema get out of whack if the schema is not analyzed. AFter months and months of operations, the execution plan for these reports is no longer valid and ... then you hang for a long time :)
analyze stats. and on slower systems, truncate audit data every now and then. and make sure you aren't running all your mappings in FULL audit mode.
My two cents.
Borkur

OWB10gR2

Similar Messages

Maybe you are looking for