OWB 9i Upgrade
Hi
Could Some one advise Is it possible to migrate OWB 9i Code to OWB 11G?
Thanks
Hi
Have you done this upgrade, if yes, would you please advise what are all the things i need to stress on as i need to do the upgrade from owb 9i to 11gR2.
Thanks
Similar Messages
-
We have OWB server on SUN Solaris 8 and OWB client on Windows XP.
The website for downloading OWB : http://www.oracle.com/technology/software/products/warehouse/index.html
shows OWB for SUN, OWB for windows etc.
The question is do I have to download (both the SUN Solaris and Windows versions of OWB 10G) and install / upgrade them completely even though all I need for the SUN Solaris environment is the OWB server component and for Windows XP all I need is the OWB client?
My earlier installs (version 9i) were from a CD so I didnt have that issueHi,
You will have to upgrade both sides and will have to download both copies therefore.
Jean-Pierre -
Hello, I have owb 10.2.0.4 with 10.2.0.4 db and need to upgrade to owb 11.1.0.7 and 11.1.0.7 db. Can anyone shares the step by step upgrade instruction ? Greatly appreciate for any help. Thanks in advance.
Hi,
look here [url http://download.oracle.com/docs/cd/B28359_01/owb.111/b31280/upgrade_03.htm#i1002327]OWB installation guide, upgrading
Regards,
Oleg -
Sorry if this is a redundant post. The search function doesn't seem to be functioning at this point.
I'm using Warehouse Builder 9.2.0.2.8 on a 9.2 database at the moment. I need to add a column to a dimension in my datamart. The problem is that the 'Upgrade' option simply doesn't function.
I tried updating the table in the database and importing it into OWB. The problem with that trick is that it appears as a table, not a dimension.
So here I am, the new column is in the database and in metadata of owb, but the deployment manager thinks that they don't agree with each other and therefore won't deploy the new version of the mapping.
Any idea how I can beat owb into behaving? Any way I can brainwash the deployment manager?
Thanks,
DavidHi David,
Beating your PC probably won't help in this case. The way this is supposed to work is allowing OWB to upgrade. Since that does not seem to work (can you file an iTar on this to support), here is a workaround...
- Rename the old dimension table in the DB
- Drop the old dimension object in the DB
- Use the new metadata in OWB, in the deployment manager, press create for the dimension
- Deploy
Copy the data from the renamed table into the new dimension table.
You should be good to go.
Jean-Pierre -
RPE-01008: Recovery of this request is in progress--while a table deploymen
Hi friends....
I am getting this error when I want to redeploy a modified table.
The steps I did as follows.
1. I created a destination and source modules.
2. I import a table from source.
3. I create a tbale in destination module in owb.
4. I deploy the table in owb.
5. Deployment wass success.
6. I created a simple mapping.
7. It was successful. Data is transfered from source to module.
8. Now I added a new field in the table which in destination module.
9 I want to upgrade the table in target schema.
10. I deployed the table in destination module in owb.
Then it gives the error
"The object you are trying to deploy is invalid. Please review the generated scripts for errors"
When I opened the generated scripts the messages are as follows.
RPE-01008: Recovery of this request is in progress. RTC-5351: A serious error occured whilst generating the Impact Report. Please review the Runtime Service Log.
Thanks in advance.
Gowtham SenHi,
If you are trying to deploy the table from Client straight, OWB generates UPGRADE statement,and this never worked. It is a bug.
go to Deployment manager, select the table in question and then use the "Replace" action. this should work. But, the data you have loaded previously will be vanished, as "Replace" drops the table and re-creates it.
Thanks
mahesh -
RPE-01008: Recovery of this request is in progress, while executing
While I am trying to execute a mapping I am getting the following error..RPE-01008: Recovery of this request is in progress... The deployment went fine, but execution throws this error. The log file looks like
2007/10/13-21:22:20-JST [1B8E059] Error creating the temp directory C:\OraHome_1/owb/temp
2007/10/13-21:22:22-JST [1B8E059] Free Memory(bytes)=738744 Total Memory(bytes)=2031616 Used Memory(bytes)=1292872 Used Memory(percent)=64%
2007/10/13-21:22:23-JST [1B8E059] Runtime Platform Service Version 10.2.0.2.8 starting
2007/10/13-21:22:23-JST [1B8E059] Client-side startup request
2007/10/13-21:22:23-JST [1B8E059] Platform Repository Name dwhownr on Service icgdwh at Host 10.109.65.67
2007/10/13-21:22:23-JST [1B8E059] Explicit garbage collection - every 1 execution(s)
2007/10/13-21:22:23-JST [1B8E059] Recovery starting
2007/10/13-21:22:23-JST [1B8E059] Recovering execution with audit ID 4109
2007/10/13-21:22:23-JST [1B8E059] Explicit garbage collection - requested
2007/10/13-21:22:23-JST [1B8E059] AuditId=4109: Processing execute request
2007/10/13-21:22:23-JST [1B8E059] Free Memory(bytes)=1149088 Total Memory(bytes)=2162688 Used Memory(bytes)=1013600 Used Memory(percent)=47%
2007/10/13-21:22:23-JST [1B8E059] Recovering execution with audit ID 4117
2007/10/13-21:22:23-JST [157AA53] Connection Manager - off
2007/10/13-21:22:23-JST [1B8E059] Explicit garbage collection - requested
2007/10/13-21:22:23-JST [1B8E059] AuditId=4117: Processing execute request
2007/10/13-21:22:23-JST [1B8E059] Free Memory(bytes)=1122832 Total Memory(bytes)=2162688 Used Memory(bytes)=1039856 Used Memory(percent)=49%
2007/10/13-21:22:23-JST [1B8E059] Service startup complete
2007/10/13-21:22:23-JST [157AA53] Thin driver connection time - 94 millisecond(s)
2007/10/13-21:22:23-JST [1DF8B99] Thin driver connection time - 94 millisecond(s)
2007/10/13-21:22:23-JST [1DF8B99] Initializing execution for auditId= 4117 parentAuditId= null topLevelAuditId=4117 taskName=ICDMAPFCTAWB
2007/10/13-21:22:23-JST [157AA53] Initializing execution for auditId= 4109 parentAuditId= null topLevelAuditId=4109 taskName=ICDMAPFCTAWB
2007/10/13-21:22:24-JST [1DF8B99] oracle.wh.runtime.platform.service.controller.RecoveryInProgress: RPE-01008: Recovery of this request is in progress.
at oracle.wh.runtime.platform.service.controller.AdapterContextImpl.initialize(AdapterContextImpl.java:1570)
at oracle.wh.runtime.platform.service.controller.ExecutionContextImpl.initialize(ExecutionContextImpl.java:1508)
at oracle.wh.runtime.platform.service.controller.ExecutionController.initialize(ExecutionController.java:32)
at oracle.wh.runtime.platform.service.controller.ExecutionController.execute(ExecutionController.java:50)
at oracle.wh.runtime.platform.service.controller.ExecutionController.execute(ExecutionController.java:23)
at oracle.wh.runtime.platform.service.ExecutionManager.run(ExecutionManager.java:36)
at java.lang.Thread.run(Thread.java:534)
2007/10/13-21:22:24-JST [157AA53] oracle.wh.runtime.platform.service.controller.RecoveryInProgress: RPE-01008: Recovery of this request is in progress.
at oracle.wh.runtime.platform.service.controller.AdapterContextImpl.initialize(AdapterContextImpl.java:1570)
at oracle.wh.runtime.platform.service.controller.ExecutionContextImpl.initialize(ExecutionContextImpl.java:1508)
at oracle.wh.runtime.platform.service.controller.ExecutionController.initialize(ExecutionController.java:32)
at oracle.wh.runtime.platform.service.controller.ExecutionController.execute(ExecutionController.java:50)
at oracle.wh.runtime.platform.service.controller.ExecutionController.execute(ExecutionController.java:23)
at oracle.wh.runtime.platform.service.ExecutionManager.run(ExecutionManager.java:36)
at java.lang.Thread.run(Thread.java:534)
2007/10/13-21:22:24-JST [1DF8B99] Attempting to create adapter 'class.RuntimePlatform.0.NativeExecution'
2007/10/13-21:22:24-JST [157AA53] Attempting to create adapter 'class.RuntimePlatform.0.NativeExecution'
2007/10/13-21:22:24-JST [157AA53] Attempting to create native operator 'class.RuntimePlatform.0.NativeExecution.PLSQL'
2007/10/13-21:22:24-JST [1DF8B99] Attempting to create native operator 'class.RuntimePlatform.0.NativeExecution.PLSQL'
2007/10/13-21:22:24-JST [157AA53] Native execution operator initiating recovery by recoverable operator oracle.wh.runtime.platform.operator.plsql.NativePLSQLOperator
2007/10/13-21:22:24-JST [1DF8B99] Native execution operator initiating recovery by recoverable operator oracle.wh.runtime.platform.operator.plsql.NativePLSQLOperator
2007/10/13-21:22:24-JST [157AA53] Native PLSQL Operator recovery starting
2007/10/13-21:22:24-JST [1DF8B99] Native PLSQL Operator recovery starting
2007/10/13-21:22:24-JST [1DF8B99] Thin driver connection time - 94 millisecond(s)
2007/10/13-21:22:25-JST [1DF8B99] PLSQL callspec: declare "$MAP_ENV$" wb_rt_mapaudit.wb_rt_name_values;begin "$MAP_ENV$"(1).param_name := 'OBJECT_ID';"$MAP_ENV$"(1).param_value := 1170;"$MAP_ENV$"(2).param_name := 'AUDIT_ID';"$MAP_ENV$"(2).param_value := 4117;"$MAP_ENV$"(3).param_name := 'OPERATING_MODE';"$MAP_ENV$"(3).param_value := '3';"$MAP_ENV$"(4).param_name := 'PURGE_GROUP';"$MAP_ENV$"(4).param_value := 'WB';"$MAP_ENV$"(5).param_name := 'MAX_NO_OF_ERRORS';"$MAP_ENV$"(5).param_value := '1000';"$MAP_ENV$"(6).param_name := 'COMMIT_FREQUENCY';"$MAP_ENV$"(6).param_value := '1000';"$MAP_ENV$"(7).param_name := 'AUDIT_LEVEL';"$MAP_ENV$"(7).param_value := '2';"$MAP_ENV$"(8).param_name := 'BULK_SIZE';"$MAP_ENV$"(8).param_value := '1000'; ? := "ICDMAPFCTAWB"."MAIN"(p_env=>"$MAP_ENV$");end;
2007/10/13-21:22:25-JST [157AA53] Thin driver connection time - 110 millisecond(s)
2007/10/13-21:22:25-JST [157AA53] PLSQL callspec: declare "$MAP_ENV$" wb_rt_mapaudit.wb_rt_name_values;begin "$MAP_ENV$"(1).param_name := 'OBJECT_ID';"$MAP_ENV$"(1).param_value := 1170;"$MAP_ENV$"(2).param_name := 'AUDIT_ID';"$MAP_ENV$"(2).param_value := 4109;"$MAP_ENV$"(3).param_name := 'OPERATING_MODE';"$MAP_ENV$"(3).param_value := '3';"$MAP_ENV$"(4).param_name := 'PURGE_GROUP';"$MAP_ENV$"(4).param_value := 'WB';"$MAP_ENV$"(5).param_name := 'MAX_NO_OF_ERRORS';"$MAP_ENV$"(5).param_value := '1000';"$MAP_ENV$"(6).param_name := 'COMMIT_FREQUENCY';"$MAP_ENV$"(6).param_value := '1000';"$MAP_ENV$"(7).param_name := 'AUDIT_LEVEL';"$MAP_ENV$"(7).param_value := '2';"$MAP_ENV$"(8).param_name := 'BULK_SIZE';"$MAP_ENV$"(8).param_value := '1000'; ? := "ICDMAPFCTAWB"."MAIN"(p_env=>"$MAP_ENV$");end;
it shows Error creating the temp directory C:\OraHome_1/owb/temp, but the temp folder is alreadt there in the <OWB_HOME>/owb.
Can somebody help me to solve this issue? The owb repository version is 10.2.0.2 ..A few mappings got executed. The error is coming for a mapping which is quite a big one...Hi,
If you are trying to deploy the table from Client straight, OWB generates UPGRADE statement,and this never worked. It is a bug.
go to Deployment manager, select the table in question and then use the "Replace" action. this should work. But, the data you have loaded previously will be vanished, as "Replace" drops the table and re-creates it.
Thanks
mahesh -
Reviewer's Guide: Review.mdl file for demo
Hi,
I downloaded OWB904 from technet, and am going through the reviewer's guide. To do the demos, it calls out importing metadata from Review.mdl on the install drive.
I have searched all through my computer, and all through the OWB site, and can't seem to find the files for the demos.
Where can one obtain these files? We are very excited about trying out this new release of OWB.
Thanks,
Scott RappoportI'm also going through the Reviewer's Guide, and I'm trying to load the metadata repository with the Review.mdl file located in the Reviewer's Guide zip. When I try to import Review.mdl using the OWB Client I get the following error:
"Error: MDL1194: Import data file for Metadata Loader release 9.2 not supported by Metadata Loader release 3.1. Use OWB MDL Upgrade Utility to convert older MDL data files to the latest supported format."
I tried using the OWB MDL File Upgrade Utility to convert Review.mdl as suggested by the error message and received another error message as follows:
"CNV0002-0023(ERROR): MDLRELEASE value is not compatible with the driver file version."
At this point I'm stuck. Please advise as soon as possible on how to proceed with loading the metadata repository.
Thanks in advance.
...Phillip -
Owbsys.wb_rt_api_exec.open fails after upgrade to OWB 11gR2
The following code is used as a PLSQL wrapper to execute OWB mappings and is based on the good old run_my_own_stuff.sql. We have been mandated to use Tivoli as the corporate scheduler, meaning we do not have Workflow as a solution. We have implemented the audit_execution_id as an input parameter to all the mappings to be able to link the data to the OWBSYS audit tables, as well as return mapping performance and success info to the execution process/session. I have implemented this exact same procedure in 10gR1, 10gR2 and 11gR1 (current dev env) with no problems at all - the code ports easily. However following an upgrade (actually an export/import of the repository from 11gR1 on a 64bit solaris to 11gR2 on Exadata running enterprise linux 5) - actually the test server (I know, I know, I said the same thing!), the code now fails on the wb_rt_api_exec.open line (highlighted).
CREATE OR REPLACE PROCEDURE bi_ref_data.map (p_map_name IN VARCHAR2)
-- Procedure to execute ETL mapping package via command line call
-- Mapping names are held in the BI_REF_DATA.MAP_NAME table
-- with the mapping type and location data
AS
v_repos_owner VARCHAR2 (30) := <repository_owner>;
v_workspace_owner VARCHAR2 (30) := <workspace_owner>;
v_workspace_name VARCHAR2 (30) := <workspace_name>;
v_loc_name VARCHAR2 (30);
v_map_type VARCHAR2 (30);
v_map_name VARCHAR2 (30) := UPPER (p_map_name);
v_retval VARCHAR2 (255);
v_audit_execution_id NUMBER; -- Audit Execution Id
v_audit_result NUMBER;
v_start_time timestamp := LOCALTIMESTAMP;
v_end_time timestamp;
v_execution_time NUMBER;
v_record_rate NUMBER := 0;
v_records_selected NUMBER;
v_records_inserted NUMBER;
v_records_updated NUMBER;
v_records_deleted NUMBER;
v_records_merged NUMBER;
v_errors NUMBER;
v_failure VARCHAR2 (4000);
e_no_data_found_in_audit exception;
v_audit_exec_count NUMBER;
e_execution_id_error exception;
BEGIN
SELECT UPPER (loc_name), UPPER (map_type)
INTO v_loc_name, v_map_type
FROM bi_ref_data.owb_map_table
WHERE UPPER (map_name) = UPPER (v_map_name);
IF UPPER (v_map_type) = 'PLSQL'
THEN
v_map_type := 'PLSQL';
ELSIF UPPER (v_map_type) = 'SQL_LOADER'
THEN
v_map_type := 'SQLLoader';
ELSIF UPPER (v_map_type) = 'SAP'
THEN
v_map_type := 'SAP';
ELSIF UPPER (v_map_type) = 'DATA_AUDITOR'
THEN
v_map_type := 'DataAuditor';
ELSIF UPPER (v_map_type) = 'PROCESS'
THEN
v_map_type := 'ProcessFlow';
END IF;
-- Changed code for owb11gr2
-- owbsys.wb_workspace_management.set_workspace (v_workspace_name, v_workspace_owner);
owbsys.wb_rt_script_util.set_workspace (v_workspace_owner || '.' || v_workspace_name);
v_audit_execution_id := owbsys.wb_rt_api_exec.open (v_map_type, v_map_name, v_loc_name);
IF v_audit_execution_id IS NULL
OR v_audit_execution_id = 0
THEN
RAISE e_execution_id_error;
END IF;
v_retval := v_retval || 'audit_execution_id=' || TO_CHAR (v_audit_execution_id);
v_audit_result := owbsys.wb_rt_api_exec.execute (v_audit_execution_id);
IF v_audit_result = owbsys.wb_rt_api_exec.result_success
THEN
v_retval := v_retval || ' --> SUCCESS';
ELSIF v_audit_result = owbsys.wb_rt_api_exec.result_warning
THEN
v_retval := v_retval || ' --> WARNING';
ELSIF v_audit_result = owbsys.wb_rt_api_exec.result_failure
THEN
v_retval := v_retval || ' --> FAILURE';
ELSE
v_retval := v_retval || ' --> UNKNOWN';
END IF;
DBMS_OUTPUT.put_line (v_retval);
owbsys.wb_rt_api_exec.close (v_audit_execution_id);
v_end_time := LOCALTIMESTAMP;
v_execution_time := bi_ref_data.get_seconds_from_interval (v_end_time - v_start_time);
v_retval := 'Execution time = ' ||
v_execution_time ||
' seconds.';
DBMS_OUTPUT.put_line (v_retval);
SELECT COUNT (w.rta_select)
INTO v_audit_exec_count
FROM owbsys.owb$wb_rt_audit w
WHERE w.rte_id = v_audit_execution_id;
IF v_audit_exec_count = 0
THEN
RAISE e_no_data_found_in_audit;
END IF;
SELECT w.rta_select,
w.rta_insert,
w.rta_update,
w.rta_delete,
w.rta_merge,
rta_errors
INTO v_records_selected,
v_records_inserted,
v_records_updated,
v_records_deleted,
v_records_merged,
v_errors
FROM owbsys.owb$wb_rt_audit w
WHERE w.rte_id = v_audit_execution_id;
v_retval := v_records_selected || ' records selected';
DBMS_OUTPUT.put_line (v_retval);
IF v_records_inserted > 0
THEN
v_retval := v_records_inserted || ' inserted';
DBMS_OUTPUT.put_line (v_retval);
END IF;
IF v_records_updated > 0
THEN
v_retval := v_records_updated || ' updated';
DBMS_OUTPUT.put_line (v_retval);
END IF;
IF v_records_deleted > 0
THEN
v_retval := v_records_deleted || ' deleted';
DBMS_OUTPUT.put_line (v_retval);
END IF;
IF v_records_merged > 0
THEN
v_retval := v_records_merged || ' merged';
DBMS_OUTPUT.put_line (v_retval);
END IF;
IF v_errors > 0
THEN
v_retval := v_errors || ' errors';
DBMS_OUTPUT.put_line (v_retval);
END IF;
IF v_execution_time > 0
THEN
v_record_rate := TRUNC ( (v_records_inserted + v_records_updated + v_records_deleted + v_records_merged) / v_execution_time, 2);
v_retval := v_record_rate || ' records/sec';
DBMS_OUTPUT.put_line (v_retval);
END IF;
IF (v_audit_result = owbsys.wb_rt_api_exec.result_failure
OR v_audit_result = owbsys.wb_rt_api_exec.result_warning)
THEN
FOR cursor_error
IN (SELECT DISTINCT aml.plain_text
FROM owbsys.owb$wb_rt_audit_messages am
INNER JOIN
owbsys.owb$wb_rt_audit_message_lines aml
ON am.audit_message_id = aml.audit_message_id
WHERE am.audit_execution_id = v_audit_execution_id)
LOOP
DBMS_OUTPUT.put_line (cursor_error.plain_text);
END LOOP;
END IF;
-- OWBSYS.wb_rt_api_exec.close (v_audit_execution_id);
COMMIT;
EXCEPTION
WHEN e_execution_id_error
THEN
raise_application_error (-20011, 'Invalid execution ID returned from OWB');
-- RAISE;
WHEN e_no_data_found_in_audit
THEN
raise_application_error (-20010, 'No data found in audit table for execution_id - ' || v_audit_execution_id);
-- RAISE;
WHEN NO_DATA_FOUND
THEN
raise_application_error (-20001, 'Error in reading data from OWBSYS tables.');
-- RAISE;
END;
Does anyone out there know if there is a difference between 11gR1 and R2 in the way that the wb_rt_api_exec function works?
Is there a simple way to retrieve the audit_id before executing the mapping, or at a push during the mapping so that we can maintain the link between the session data and the OWBSYS audit data?
MartinHi David, I have been reading some of your posts and blogs around OWB and I still have not found the answer.
OK, thereis/was a script that Oracle Support/forums/OTN sent out a while ago called "run_my_iowb_stuff" - I am sure you will be familiar with it. I based the code I uploaded on it and added additional functionality. In essence, I wanted to use the audit_id as an input parameter tot he mapping, so that I can register the audit_id in the management tables, and associate each row of loaded data with a specific mapping_id which would allow a simple link to the owbsys audit tables to complete the audit circle. To that end, I used the owbsys.wb_rt_api_exec.open procedure to register the mapping execution, and then on the execute procedure of the same package, I passed this audit_id in as a custom parameter:
<<snip>>
owbsys.wb_workspace_management.set_workspace (v_workspace_name, v_workspace_owner);
v_audit_execution_id := owbsys.wb_rt_api_exec.open (v_map_type, v_map_name, v_loc_name, 'PLSQL');
IF v_audit_execution_id IS NULL
OR v_audit_execution_id = 0
THEN
RAISE e_execution_id_error;
END IF;
v_retval := v_retval || 'audit_execution_id=' || TO_CHAR (v_audit_execution_id);
IF v_include_mapping_id > 0 -- if non-zero, submit owb execution id as an input parameter to the map process
THEN
owbsys.wb_rt_api_exec.override_input_parameter (
v_audit_execution_id,
'p_execution_id',
TO_CHAR (v_audit_execution_id),
owbsys.wb_rt_api_exec.parameter_kind_custom
END IF;
<<snip>>
The execution is closed, also by the use of the audit_id ( "owbsys.wb_rt_api_exec.close (v_audit_execution_id)" )
I can also use the audit_id to inspect the audit tables to retrieve the records processed as well as any associated error messages, and format them for the calling application (owSQL*Plus, which is normally the context of our current use).
This procedure has been working weel up to now until we moved over to 11gR2 when all of a sudden the audit_id is not returned when executing "v_audit_execution_id := owbsys.wb_rt_api_exec.open (v_map_type, v_map_name, v_loc_name);". Prior to 11gR2 this worked like a charm - now it has crashed to a halt.
As an interesting twist, I have tried to substitute a sequence number for the audit_id, and then tried to get the audit_id after the mapping completes, so that I can put both the sequence and audit id in a table so it maintains the link. However in attempting to use the owbsys.wb_rt_script_util.run_task procedure which now appears to be the only thing left working, I was astonished to see the following output in sqlplus:
SQL> exec map1('stg_brand')
Stage 1: Decoding Parameters
| location_name=STAGE_MOD
| task_type=PLSQLMAP
| task_name=STG_BRAND
Stage 2: Opening Task
| l_audit_execution_id=2135
Stage 3: Overriding Parameters
Stage 4: Executing Task
| l_audit_result=1 (SUCCESS)
Stage 5: Closing Task
Stage 6: Processing Result
| exit=1
--> SUCCESS
Execution time = .647362 seconds.
records/sec
PL/SQL procedure successfully completed.
SQL>
This output seems so identical to the "run_my_owb_stuff" that either Oracle support generated their "run_my_owb_stuff" as a lightweight owbsys.wb_rt_script_util.run_task procedure, or Oracle incorporated the "run_my_owb_stuff" script into their owbsys.wb_rt_script_util.run_task procedure! Which way round I cannot say, but it is surely one or the other! To make matters worse, I have raised this with Oracle Support, and they have the temerity to claim that they do not support the "run_my_owb_stuff" script, but think enough of it to incorporate it into their own package in a production release!
To overcome my problems, in the short term, I need to be able to access the audit_id either during or after the execution of the mapping, so that I can at least associate that with a sequence number I am having to pass in as a parameter to each mapping. In the longer term, i would like a solution to be able to access the audit_id before I execute the mapping, as I could by calling the "owbsys.wb_rt_api_exec.open " procedure. Ideally this would be solved first and I would not need to use a sequence at all.
Hope this clarifies things a bit.
Regards
Martin -
Post-upgrade tasks for OWB 10g Release 2
Hi,
we're planning to upgrade from OWB 10.1.0.2 to 10.2.x.
Now, I'm trying to get a clear view on what will be the "post-upgrade" tasks, in terms of manual adaptations, corrections, etc. to get everything back up and running after the upgrade ...
E.g. : by means of test al already exported a dimension, and imported it in the 10.2 repository ... Turned out that in the pre-10.2 version, there were no validation problems, but as from 10.2 (although the upgrade and import were successful), I got 19 warnings and 2 errors ... because each level needs to have a business or surrogate key ...
It' s things like that I'm especially interested in, in order to determine the workload after the upgrade ...
So, feel free to share your experiences ; I'm looking forward to read them!
Thanks!
Grtz.Here are some from my list. I stopped maintaining it a while ago, we have lots more where this came from. Some of it also apply to older versions of OWB.
Key lookup You are to choose input and output attributes BEFORE being able to choose loookup table, all in a time consuming wizard
Expressions Copy and paste into expression editor, validation fails for expressions using lowercase (such as "upper" or "substr")
Renaming attributes Not possible anymore, you need to open details
Adding a table component You must browse in a tree structure (time consuming), not search functionality anymore
Import Import converting from 9.2 hangs after 15% in about 10% of all imports
Import Some mappings are not possible to import, a total rewrite is necessary
Deployment You can only deploy about 5-10 times before you need to restart OWB
Memory leak If something goes wrong in OWB, memory is never cleared - JAWAW.exe needs to be removed manually from memory
Import Importing mappings one by one (as this is sometimes needed due to OWB), the last directory used is OF COURSE not default when importing the next time
OWB GUI / mapping editor When working with components in the mapping editor, an object hidden behind the object you are actually working with is selected prior to the object in visual focus to the user
BUG! Urgent: CASE - wrong generated Code
ANSI JOINS Remove ANSI-SQL from mapping configuration, otherwise (+) outer joins will not work
Transformations Not possible to enter a transformation such as "sysdate", you must find it in a huge tree structure list (no search available) -
The mis-mapping problem when upgrading OWB from 11.1 to 11.2.0.2.
Hi all,
Our OWB ETL program was developed initially on OWB 11.1 platform.
Then after upgrading it from 11.1 to 11.2.0.2, several mappings are mismatched in the deployment PL/SQL package as below:
CREATE OR REPLACE PACKAGE BODY "MAP_PRODUCT_LIFE_CRT" AS
CURSOR "T_T_PRODUCT_LIFE_c" IS
SELECT
/* T_PRODUCT_LIFE.T_T_PRODUCT_LIFE.INOUTGRP1 */
"T_T_PRODUCT_LIFE"."INS_TYPE" "ORGAN_ID$1",
"T_T_PRODUCT_LIFE"."START_DATE" "HOSPITAL_TYPE$1",
"T_T_PRODUCT_LIFE"."END_DATE" "UNIT_FLAG$1",
"T_T_PRODUCT_LIFE"."LIFE_RATE" "INS_TYPE",
You can see that the field mapping is wrong! We have about 100 mappings, but only some of them go wrong.
We have tried the Metadata Loader and Repository Assistant for the upgrading, but the results are the same.
We have released all OWB patches on 11.2.0.2, but the results are the same.
Please help on it!Hi David,
Besides the mega patch 10185523, we also have applied other tens of patches, e.g. 10225308, 11671955, 11705023, 1768535, etc.
Now we find that the wrong field mapping just appears in the row-based part of the mapping package. So if the set-based mode works well for the mapping execution, no error will happen. That's why we just found the problems in several mappings.
And one thing is even worse. In the patched OWB 11.2.0.2 env., we tried creating totally new mapping. The result is the same: the wrong field mapping still appears in the row-based part of the mapping package.
So this problem seems not related to the upgrading.
Regards. -
Upgrading OWB from 10.1.0.4 to 11.2
Hi,
We have plans to upgrade OWB in our environment.
OWB - 10.1.0.4
DB instance - 10.2.0.4
OWF - 2.6.4
Planned OWB upgrade -> 10.1.0.4 to 11.2.0.2 (as most of the bugs were fixed in this version)
As far as my study, I have learnt that we got to do an intermediate upgrade for this
10.1.0.4 -> 10.2.0.5 -> 11.2
Our database version is currently 10.2.0.4. We are upgrading our Database too - to 11.1.0.7
Please clarify my below questions,
1. How can I do the intermediate upgrade from 10.1.0.4 to 10.2.0.5?
2. OWF 2.6.4 will work with OWB 11.2?
3. Below is the path, we have planned for this migration
a. Upgrade OWB from 10.1.0.4 to 10.2.0.5
b. Upgrade the DB instance from 10.2.0.4 to 11.1.0.7
c. Upgrade OWB from 10.2.0.5 to 11.2
will this path work?
4. OWB 11.2 will be compatible with DB instance version of 11.1.0.7?
Any assistance would be greatly appreciated.
Thanks in Advance!!
Many Thanks,
Parthy.
Edited by: Parthy on Mar 3, 2011 8:07 AMHi Parthy,
Here are the answers for your queries:
1. How can I do the intermediate upgrade from 10.1.0.4 to 10.2.0.5?
It will be there in the install& admin guide of OWB 10.2, refer the below URL:
http://download.oracle.com/docs/cd/B31080_01/doc/install.102/b28224/upgrade_03.htm#i1002327
2. OWF 2.6.4 will work with OWB 11.2?
Yes, it will work
3. Below is the path, we have planned for this migration
a. Upgrade OWB from 10.1.0.4 to 10.2.0.5
b. Upgrade the DB instance from 10.2.0.4 to 11.1.0.7
c. Upgrade OWB from 10.2.0.5 to 11.2
will this path work?
It should work perfectly
4. OWB 11.2 will be compatible with DB instance version of 11.1.0.7?
Yes, it is compatiable you can have the OWB 11.2 workspace on 11.1 database
Regards,
Pnreddy -
Upgrade to 10.1.0.4 owb and 10grl2 db - mapping fail
Hi,
Have recently upgraded owb from 10.1.02 to 10.1.0.4 and db from 9.2 to 10.2 and now am getting a mapping failing with ORA-00972: identifier is too long. The sql in the cursor being generated is failing, have tried to reduce operator field names but with no luck. Any ideas ????
Cheers,
BrandonI had the same problem.
The problem is related the length of the database link
for one of the test data tables.
You have, for that test data, to use the button that creates a
new database link, use a shorter name and use it.
Regards,
Joao Noronha -
OWB considerations after the db upgrade
We did out of place db upgrade (moving to new oracle home) from 11.2.0.3.4 to 11.2.0.3.5. are there any special
considerations needed for the OWB during or after the db upgrade?
1225254.1 docs describes steps needed for owb for db upgrade from 11.2.0.2-> 11.2.0.3,
but I don't see any docs from 11.2.0.3.x to 11.2.0.3.y.
Thanks for your time.880674 wrote:
our os is Solaris
Basically we create new oracle home.Patch that oracle home with latest psu(jan 2013)then we
Move the database from the old oracle home to the new oracle home
It is not clear as to why you take this approach - it is not required - all you need to do is apply the PSU patch to the current home by following the instructions in the PSU patch README.
1.log in as Oracle
2.. oraenv
a.TS11
b.sss
i.shutdown immediate
c.cd $ORACLE_HOME/dbs
d.l TS11
e.cp TS11 $NEW_ORACLE_HOME/dbs
i.cd $ORACLE_HOME/network/admin
ii.vi listener.ora
1.edit the line for TS11 to listen for the new oracle home
2.lsnrctl reload
3.cp *.ora $NEW_ORACLE_HOME/network/admin
iii.vi /var/opt/oracle/oratab
iv.change the oracle home for TS11 to the new oracle home
3.log out
4.log in as oracle
a.set the oraenv to TS11
b.cd $ORACLE_HOME/rdbms/admin
c.sss
d.startup
[email protected] psu apply
f.@utlrp
in this process do we have to do anything special for owb
update wb_rt_service_nodes set SERVER_SIDE_HOME='/ora/SW/db/11.2.0.3.5';
update owbrtps set VALUE='/ora/SW/db/11.2.0.3.5';I do not have any experience with OWB, but pl see if these MOS Docs can help
How to Change The OWB Home on the Same Server [ID 968712.1]
How To Update Warehouse Builder After A Database Cloning [ID 434272.1]
HTH
Srini -
Unable to upgrade from OWB 10.2.0.1 to OWB 10.2.0.3
Hi
After installing OWB 10.2.0.1, i tried to upgrade to OWB 10.2.03. But the installation fails mid-way. It didn't give any error msg. Pls help
Last few Text from the error log
INFO: *** Install Page***
INFO: Install mode is not fastcopy.
INFO: HomeSetup JRE files in Scratch :699
INFO: Setting variable 'ROOTSH_LOCATION' to 'C:\OWB_10G\root.sh'. Received the value from a code block.
INFO: 02/12/08 14:41:31 GMT: Starting install Install Phase 1 of component Patch of Windows JDK
INFO: *** Error Dialog: Error occurred ***
INFO: User Selected: Stop installation of all products.
INFO: java.io.IOException: The system cannot find the path specified
INFO: Setting variable 'PREREQ_CONFIG_LOCATION' to ''. Received the value from variable association.
INFO: Setting variable 'PREREQ_CONFIG_LOCATION' to ''. Received the value from variable association.
INFO:
*** Welcome Page***
INFO: Initializing install inventory
INFO: Setting up install inventory
INFO:
*** Specify Source Location Page***
WARNING: Do you really want to exit?
INFO: User Selected: Yes/OKfollow this link
http://www.orafaq.com/forum/t/119954/2/
http://wiki.oracle.com/search/threads/10.2.0.1?contains=10.2.0.1
http://www.oraclealchemist.com/oracle/patching-from-10201-to-10203/
also i assume there is no RAC involved in your case.
Edited by: Darthvader-647181 on Dec 2, 2008 8:13 AM
Edited by: Darthvader-647181 on Dec 2, 2008 8:14 AM -
Upgrade patches from OWB 10.2.0.1 to OWB 11.2.0.3
We are upgrading from OWB 10.2.0.1 to OWB 11.2.0.3
We have upgraded database from 10.2.0.1 to 11.2.0.3
What are the patches that needs to be applied before upgrading the repository?
What are the patches that needs to be applied after upgrading repository?follow this link
http://www.orafaq.com/forum/t/119954/2/
http://wiki.oracle.com/search/threads/10.2.0.1?contains=10.2.0.1
http://www.oraclealchemist.com/oracle/patching-from-10201-to-10203/
also i assume there is no RAC involved in your case.
Edited by: Darthvader-647181 on Dec 2, 2008 8:13 AM
Edited by: Darthvader-647181 on Dec 2, 2008 8:14 AM
Maybe you are looking for
-
Very urgent!!! Please help! Anybody from Oracle who can help?
I am using Oracle9i with oracle pool in my JSP for database handling. I am using OracleConnectionCacheImpl and OracleConnectionCacheImpl.DYNAMIC_SCHEME. I am also setting max and min limit for connections ocacheimpl.setMinLimit (5); ocacheimpl.setMax
-
Is there a way to remove all of my contacts from the iCloud? My phone has my correct contacts list. When I sync with iCloud it pulls down 50+ contacts that I do not want. I went to iCloud to remove the unwanted contacts and it takes nearly 1 minute f
-
Hierarchy restrictons not working with Basis servicepack upgrade to 14
Hi All, We recently upgraded our system with basis sp 14, and we having the below problems with out hierarchy restrictions: Problem #1 We recently upgraded our system from then onwards hierarchy restrictions not working, users are getting authorizat
-
How do I get to settings to check and unckeck playlists?
OK..running Yosemite, latest version of iTunes. This is the first sync on yosemite. Back on Mavericks, there was a window where I could click on the ipod icon and go to wjat's on the ipod, and check and uncheck playlists while I manually manage the l
-
After the server reboot I can't bring CPS back up in Windows server. Can anyone tell me how to start CPS? i have tried start from JRun but didn't work. Below are the error i got. 10/28 09:22:42 error Deployer Service failed to deploy C:\Program Fi