Migrate OIM repository

Hi All,
i need to migrate the OIM (9.2.0.1) repository to a new Oracle database.
is there some document / metalink note - that describe what exactly need to be done ?
I guess there is more to it than :
- migrate theschema
- change the xconfig.xml
.,... it is ?
thanks
S.

You can export just the OIM user schema. Then run the prepare script on your new database to create a new schema. Then you'll want to update your xlconfig.xml file to point to the new database. Also, in your application server, you'll want to change your JDBC resources as well. This should be all you need to do.
I would also suggest you make sure there isn't anything going on in the jms queues. This would be the table labeled adminstore_wlserver. If you only have a single server, there should be only 31 records in here.
-Kevin

Similar Messages

Migrating Designer Repository 6i to Repository 10g

My client has an Oracle Designer repository 6i Version 6.5.92.1.9 Release 4.7.(Repository 9i).
He has created an Oracle Designer repository 10g (latest version) onto another server.
He wants to migrate his Repository 6i into his new repository 10g.
Is it possible to do this, if not could you tell me more.
Thanks

He ought to be able to use the Export in the Repository Administration Utility (RAU) in 6i to export the repository and Import in the RAU in 10g to import it. Two caveats:
1. Don't try to go from a versioned repository to a non-versioned one. I think the other way around works, but I don't have mine versioned, so I don't know for sure.
2. Make absolutely sure that you are using the right EXP for the database version in which the 6i repository is stored and the right IMP for the database version in which the 10g repository is stored. Check the EXECUTE_EXP and EXECUTE_IMP registry settings on each. I've seen a lot of problems that could be avoided by using the right export and import.

MIGRATION DESIGNER REPOSITORY 6.0 to 6i

I've tried to migrate repository 6.0 to 6i but in process i recive the error message:
ORA-03232 unable to allocate extent to tablespace ...
ORA-02063 error from link ...
RME-02124 failed to excute SQL statement CREATE TABLE UPG_RM_TEXT_LINES ...
I have read the solution of note but the problem persist.
Someone can help Me
Thanks in adv
Domenico Navarra
Italy

This sounds like you dont have enough space to do the migration and Oracle cannot extend a data file. Make sure you have autoextend on in the target database (I'm guessing it's the target).
Steve

Error migrating Master Repository from Dev. to Prd, Environment

Hi,
We are trying to migrate our development environment (dev_env) to production (prd_env), so for this we are doing the following:
- We create a Execution Work Repository (prd_env)
- We create a Master Repository (prd_env) with different internal ID (dev_env)
- We export one scene from dev_env and import to prd_env
- We export Master Repository from dev_env and import to prd_env, but in this point we have problem with the import wich say
"com.sunopsis.tools.core.exception.SnpsSimpleMessageException: ### KEY com.sunopsis.res.object / DwgDuplicationTools.GeneralImportObjectFailureMsg### a"...".run(Unknown Source)Caused by: java.sql.SQLException: ORA-02291: integrity constraint (....) violated - parent key not found"
Please, some one help us with this issue, thanks!!!

Hi,
Both your Prod and Dev are in same platforms?
Normally Dev we do on windows and production in Linux.
IF, your case is above. then create another schema in same platform(DB and OS ) and import the master and work repositories in Insert update mode from dev.
After import, re-export this newly created repositories and try importing into your production.
I have faced the similar issue and after following the above process, I am able to import my master and work properly.
If you are still not able to resolve this issue after following the above way.
Then try export you Logical and Physical Schema instead of master repository.
While importing , please import the Physical topology(Topology) and then the Logical Topology.
Thanks,
Nagarjuna

How to migrate 10gR1 repository to OWB 11gR2?

We are trying to migrate OWB 10gR1 repository to OWB 11gR2?
But are being faced with version compatibility issues.
Is there any work-around for the same?

This is a bit before my time, so I'm not very familiar with how the repository worked in 10gR1, but you might have a look at this... assuming you at least have the database credentials for the repository owner, it looks like you can perform user management tasks through this helper package that might get you an OWB user that can access everything, and let you move your design into 10.2 (from which you can migrate on to 11.2).
http://download.oracle.com/docs/cd/E10926_01/doc/owb.101/b12146/extending.htm#i1088387
Maintaining Repository Users
Multiple identifiable Warehouse Builder users can access the same central repository schema when they are registered by the repository owner.
Warehouse Builder includes utility procedures for the following maintenance tasks:
* Update the role protecting password
Although the repository owner does not explicitly use the protecting password for the role, it is recommended that the repository owner change the password often.
The repository owner must connect to the repository schema using SQL Plus and issue the following statement:
Call WBSecurityHelper.updateRolePwd('newpwd');
where'newpwd' is the new password used to protect the role chosen by repository owner. The changed password encryption appears in the table called OWB_ROLE_INFO table.
* Register repository users
Warehouse Builder users must be database users located in the same database instance as the repository. The database user's default role should not be ALL. Use 'After user xxx DEFAULT Role x' to set the default role property.
To register a repository user, execute the following statement in SQL Plus:
call WBSecurityHelper.registerOWBUser ('username')
* Unregister repository users
To unregister a user from a repository, execute the following statement in SQL Plus:
Call WBSecurityHelper.unregisterOWBUser('username');
* List all repository users
The repository owner must connect to the database containing the repository and issue the following statement:
Set serveroutput on;
Call WBSecurityHelper.listOWBUser( );
Set serveroutput on is required since listOWBUser() uses the DBMS_OUTPUT.put_line for the output to dump the data to the user interface. Otherwise, DBMS_OUTPUT.put_line only dumps the output into an intermediate data structure.
The preceding user maintenance tasks should be performed in the repository by the repository owner.

WHEN MIGRATING SQLSERVER REPOSITORY TO ORACLE MODEL USING OraMigWrkBnch

I have captured the the SQLServer database to the omwb repository and migrated it to the Oracle Model. Some of the views,
triggers and stored procedures are not migrated and the followind messages are provided.
Has somebody done this before and got the same messages?, does someone know how to solve this problem(s)?, is there a
standard way?
Please help, anyone.
VIEW
[1] Error occured on line 1:oracle.mtg.sqlserver2k.parser.ParseException: Parse error at line 1, column 106. Encountered:
from
TRIGGERS
[2] Error occured on line 9:oracle.mtg.sqlserver2k.parser.ParseException: Parse error at line 9, column 10. Encountered: of
[3] Error occured on line 17:oracle.mtg.sqlserver2k.parser.ParseException: Parse error at line 17, column 3. Encountered:
update
[4] Error occured on line 183:oracle.mtg.sqlserver2k.parser.ParseException: Parse error at line 183, column 5. Encountered:
cross
[5] Error occured on line 7:oracle.mtg.sqlserver2k.parser.ParseException: Parse error at line 7, column 1. Encountered:
create
STORED PROCEDURES
[6] Error occured on line 26:oracle.mtg.sqlserver2k.parser.ParseException: Parse error at line 26, column 5. Encountered:
update
[7] Error occured on line 163:oracle.mtg.sqlserver2k.parser.ParseException: Parse error at line 163, column 17. Encountered:
where
[8] Error occured on line 66:oracle.mtg.sqlserver2k.parser.ParseException: Parse error at line 66, column 47. Encountered:
@ac_any_type_code
[9] Error occured on line 69:oracle.mtg.sqlserver2k.parser.ParseException: Parse error at line 69, column 28. Encountered: =
[10] Error occured on line 70:oracle.mtg.sqlserver2k.parser.ParseException: Parse error at line 70, column 7. Encountered: (
[11] Error occured on line 9:oracle.mtg.sqlserver2k.parser.ParseException: Parse error at line 9, column 1. Encountered:
[12] Error occured on line 64:oracle.mtg.sqlserver2k.parser.ParseException: Parse error at line 64, column 5. Encountered:
delete
[13] Error occured on line 60:oracle.mtg.sqlserver2k.parser.ParseException: Parse error at line 60, column 35. Encountered:
as
[14] Error occured on line 1:oracle.mtg.sqlserver2k.parser.ParseException: Parse error at line 1, column 55. Encountered:
create
[15] Error occured on line 65:oracle.mtg.sqlserver2k.parser.ParseException: Parse error at line 65, column 7. Encountered:
from
[16] Error occured on line 56:oracle.mtg.sqlserver2k.parser.ParseException: Parse error at line 56, column 51. Encountered: +
[17] Error occured on line 112:oracle.mtg.sqlserver2k.parser.ParseException: Parse error at line 112, column 1. Encountered:
null
[18] Error occured on line 27:oracle.mtg.sqlserver2k.parser.ParseException: Parse error at line 27, column 3. Encountered:
select
[19] Error occured on line 74:oracle.mtg.sqlserver2k.parser.ParseException: Parse error at line 74, column 10. Encountered:
and
[20] Error occured on line 19:oracle.mtg.sqlserver2k.parser.ParseException: Parse error at line 19, column 6. Encountered: ,
[21] Error occured on line 194:oracle.mtg.sqlserver2k.parser.ParseException: Parse error at line 194, column 10. Encountered:
exists
[22] Error occured on line 269:oracle.mtg.sqlserver2k.parser.ParseException: Parse error at line 269, column 9. Encountered:
declare
[23] Error occured on line 49:oracle.mtg.sqlserver2k.parser.ParseException: Parse error at line 49, column 7. Encountered:
order
[24] Error occured on line 244:oracle.mtg.sqlserver2k.parser.ParseException: Parse error at line 244, column 41. Encountered:
rtrim

The following trigger created:
CREATE OR REPLACE TRIGGER tr_prs16_ins
AFTER INSERT
ON progress_state_16
FOR EACH ROW
DECLARE
/* COMMENT */
BEGIN
     BEGIN
               INSERT INTO logtable
                    SELECT :NEW.code, sf_language.code,
RPAD(CASE WHEN fg1.id IS null THEN '' ELSE RTRIM(fg1.id) END ||
CASE WHEN pg1.id IS null THEN '' ELSE ': ' || RTRIM(pg1.id) END ||
CASE WHEN fg2.id IS null THEN '' ELSE ', ' || RTRIM(fg2.id) END ||
CASE WHEN pg2.id IS null THEN '' ELSE ': ' || RTRIM(pg2.id) END ||
CASE WHEN fg3.id IS null THEN '' ELSE ', ' || RTRIM(fg3.id) END ||
CASE WHEN pg3.id IS null THEN '' ELSE ': ' || RTRIM(pg3.id) END ||
CASE WHEN fg4.id IS null THEN '' ELSE ', ' || RTRIM(fg4.id) END ||
CASE WHEN pg4.id IS null THEN '' ELSE ': ' || RTRIM(pg4.id) END ||
CASE WHEN fg5.id IS null THEN '' ELSE ', ' || RTRIM(fg5.id) END ||
CASE WHEN pg5.id IS null THEN '' ELSE ': ' || RTRIM(pg5.id) END ||
CASE WHEN fg6.id IS null THEN '' ELSE ', ' || RTRIM(fg6.id) END ||
CASE WHEN pg6.id IS null THEN '' ELSE ': ' || RTRIM(pg6.id) END ||
CASE WHEN fg7.id IS null THEN '' ELSE ', ' || RTRIM(fg7.id) END ||
CASE WHEN pg7.id IS null THEN '' ELSE ': ' || RTRIM(pg7.id) END ||
CASE WHEN fg8.id IS null THEN '' ELSE ', ' || RTRIM(fg8.id) END ||
CASE WHEN pg8.id IS null THEN '' ELSE ': ' || RTRIM(pg8.id) END ||
CASE WHEN fg9.id IS null THEN '' ELSE ', ' || RTRIM(fg9.id) END ||
CASE WHEN pg9.id IS null THEN '' ELSE ': ' || RTRIM(pg9.id) END ||
CASE WHEN fg10.id IS null THEN '' ELSE ', ' || RTRIM(fg10.id) END ||
CASE WHEN pg10.id IS null THEN '' ELSE ': ' || RTRIM(pg10.id) END ||
CASE WHEN fg11.id IS null THEN '' ELSE ', ' || RTRIM(fg11.id) END ||
CASE WHEN pg11.id IS null THEN '' ELSE ': ' || RTRIM(pg11.id) END ||
CASE WHEN fg12.id IS null THEN '' ELSE ', ' || RTRIM(fg12.id) END ||
CASE WHEN pg12.id IS null THEN '' ELSE ': ' || RTRIM(pg12.id) END ||
CASE WHEN fg13.id IS null THEN '' ELSE ', ' || RTRIM(fg13.id) END ||
CASE WHEN pg13.id IS null THEN '' ELSE ': ' || RTRIM(pg13.id) END ||
CASE WHEN fg14.id IS null THEN '' ELSE ', ' || RTRIM(fg14.id) END ||
CASE WHEN pg14.id IS null THEN '' ELSE ': ' || RTRIM(pg14.id) END ||
CASE WHEN fg15.id IS null THEN '' ELSE ', ' || RTRIM(fg15.id) END ||
CASE WHEN pg15.id IS null THEN '' ELSE ': ' || RTRIM(pg15.id) END ||
CASE WHEN fg16.id IS null THEN '' ELSE ', ' || RTRIM(fg16.id) END ||
CASE WHEN pg16.id IS null THEN '' ELSE ': ' || RTRIM(pg16.id) END
, 255, ' ')
from dual
left outer join function_group fg1 on fg1.code = :new.function_group_1_code
left outer join function_group fg2 on fg2.code = :new.function_group_2_code
left outer join function_group fg3 on fg3.code = :new.function_group_3_code
left outer join function_group fg4 on fg4.code = :new.function_group_4_code
left outer join function_group fg5 on fg5.code = :new.function_group_5_code
left outer join function_group fg6 on fg6.code = :new.function_group_6_code
left outer join function_group fg7 on fg7.code = :new.function_group_7_code
left outer join function_group fg8 on fg8.code = :new.function_group_8_code
left outer join function_group fg9 on fg9.code = :new.function_group_9_code
left outer join function_group fg10 on fg10.code = :new.function_group_10_code
left outer join function_group fg11 on fg11.code = :new.function_group_11_code
left outer join function_group fg12 on fg12.code = :new.function_group_12_code
left outer join function_group fg13 on fg13.code = :new.function_group_13_code
left outer join function_group fg14 on fg14.code = :new.function_group_14_code
left outer join function_group fg15 on fg15.code = :new.function_group_15_code
left outer join function_group fg16 on fg16.code = :new.function_group_16_code
left outer join progress pg1 on pg1.code = :new.progress_1_code
left outer join progress pg2 on pg2.code = :new.progress_2_code
left outer join progress pg3 on pg3.code = :new.progress_3_code
left outer join progress pg4 on pg4.code = :new.progress_4_code
left outer join progress pg5 on pg5.code = :new.progress_5_code
left outer join progress pg6 on pg6.code = :new.progress_6_code
left outer join progress pg7 on pg7.code = :new.progress_7_code
left outer join progress pg8 on pg8.code = :new.progress_8_code
left outer join progress pg9 on pg9.code = :new.progress_9_code
left outer join progress pg10 on pg10.code = :new.progress_10_code
left outer join progress pg11 on pg11.code = :new.progress_11_code
left outer join progress pg12 on pg12.code = :new.progress_12_code
left outer join progress pg13 on pg13.code = :new.progress_13_code
left outer join progress pg14 on pg14.code = :new.progress_14_code
left outer join progress pg15 on pg15.code = :new.progress_15_code
left outer join progress pg16 on pg16.code = :new.progress_16_code
cross join sf_language
     END;
END TEST_IF;
given the following tables exist:
create table logtable(newcode varchar2(10),
sfcode varchar2(10),
other varchar2(10)
create table sf_language(code varchar2(10),
id varchar2(10));
create table progress(code varchar2(10),
id varchar2(10));
create table function_group(code varchar2(10),
id varchar2(10));
create table progress_state_16 (code varchar2(10),
function_group_1_code varchar2(10),
function_group_2_code varchar2(10),
function_group_3_code varchar2(10),
function_group_4_code varchar2(10),
function_group_5_code varchar2(10),
function_group_6_code varchar2(10),
function_group_7_code varchar2(10),
function_group_8_code varchar2(10),
function_group_9_code varchar2(10),
function_group_10_code varchar2(10),
function_group_11_code varchar2(10),
function_group_12_code varchar2(10),
function_group_13_code varchar2(10),
function_group_14_code varchar2(10),
function_group_15_code varchar2(10),
function_group_16_code varchar2(10),
progress_1_code varchar2(10),
progress_2_code varchar2(10),
progress_3_code varchar2(10),
progress_4_code varchar2(10),
progress_5_code varchar2(10),
progress_6_code varchar2(10),
progress_7_code varchar2(10),
progress_8_code varchar2(10),
progress_9_code varchar2(10),
progress_10_code varchar2(10),
progress_11_code varchar2(10),
progress_12_code varchar2(10),
progress_13_code varchar2(10),
progress_14_code varchar2(10),
progress_15_code varchar2(10),
progress_16_code varchar2(10))
SQL> insert into progress_state_16 values ('1','1','1','1','1','1','1','1','1','1','1','1','1','1','1','1','1','1','1','1','1','1','1','1','1','1','1','1','1','1','1','1','1');
1 row created.
SQL> select * from logtable;
no rows selected
SQL>
The data to make the select produce a result was not added. I hope your database difficulties are resolved. I hope the fact that the trigger builds gives you more confidence.
Regards,
Turloch
Oracle Migration Workbench Team

Migrating Informatica Repository and Rolling back the changes.

Hi all,
I am new to Informatica. We are working on Migrating the Informatica repository from DEV to PROD using Repository manager's Copy & Paste method.
Could anyone suggest whether we are using the right method or not. Is there any other efficient way to migrate the Informatica stuff( Mappings/mapplets/workflows & Sessions)
Please let us know the ROLLBACK Techniques also so that we can rollback if something goes wrong.
Thanks in Advance
Anand.

If you are migrating everything for the first time I assume there is no need for "roll back"..you can just export/import the entire repository. However, as the last user pointed out, you can use a deployment group to do subsequent migrations. You can use a combination of Labels/Deployment groups and these can be static or dynamic (based on a query). The informatica guides have good documentation on deployment group. I would avoid the cut/paste method..try to use import/export or deployment groups.

Migration BIEE repository from Windows to Unix

Hi,
has someone experience with migrating repository objects from a windows to Unix environment or vice versa? Are there any problems (different XML generated etc.)?
Background: We are developing in a Windows environment but later we want to move to Unix. Until now no Unix server is available.
Thanks,
Marcus

How is it at the GiantEagle (worked in Cranberry last year)?
How exactly do you do a short-deck migration/promotion to UAT or PROD? How do you ensure that changes in the DAC make it into the UAT/PROD without killing the existing objects?
Currently we have 3 env, DEV/INT/UAT/PROD and we're trying to write a policy manual to ensure that what goes on in DEV gets all the way into PROD without damaging INT, UAT or PROD.
jrod.

Migrating Oracle repository Database with the existing Database

Hi
I have a grid installed in a machine and is it possible to create the repository database in different machine using the existing database.
Please help me in this

Thanks for the reply i got the Solution. We can use the "Install Grid usisng Existing Database" option but when we are tyring this it is throwing the error that DBSPOOL Package has to be run but dodn't know how to run that.

Oim 9.1.0.2 migration to 11.1.1.5

hi friends,
I am looking to migrate oim 9.1.0.2 to 11.1.1.5
can any post me the links regarding this migration task.
Thanks & Regards
srikanth

Use Upgrade Assistant tool
go through below link
Re: OIM 9102 to 11g upgrade
--nayan

OIM Migration from version 9.1.0 to 9.1.0.2

Hello Everybody,
I'm working in a migration process of Oracle Identity Manager from 9.1.0 to 9.1.0.1 and them to 9.1.0.2.
The process works Ok with the core of OIM but we having a problem with the migration of the AD connector.
At the first time, we applied the process directly (according to the oracle documentation) and the object "user" looks corrupt.
We call Oracle and they told us that the correct way to install a new version of the connector is importing it from a OIM new instalation (with the new connector), but this process corrupt the object "user".
Did somebody work in a OIM migration process? Does somebody know the correct way to migrate OIM?
Thanks.
Regards.
Walter.

First you need to determine the Upgrade Path and methods available to the New Oracle Database 10g Release.
http://download.oracle.com/docs/cd/B19306_01/server.102/b14238/preup.htm#i1007814
Refer the Oracle Upgrade Documentations on more information.
Oracle® Database Upgrade Guide 10g Release 2 (10.2)
http://download.oracle.com/docs/cd/B19306_01/server.102/b14238/toc.htm
Regards,
Sabdar Syed.

DB quries wrt migration from oim 9.1 to oim 11g (11.1.1.5)

Hi All,
We have to do migration from oim9.1 to oim 11g (11.1.1.5) with new DB and AppServers.
High level Steps are as follows
1. import the existing OIm9.1 DB to new DB.
2. Create Additional schemas (SOA,MDS) on new DB.
3. Install OIm 11g and SOA applications on new servers
4. Migrate new DB's OIm 9.1 Schema to support oim 11g (by running Oracle_IDM_Home/bin/ua.sh)
5. Some other releated tasks (As mentioned in the upgrade guide)
6. Migrate OIM application middlte tier
7. Other tasks (As mentioned in the upgrade guide)
Our requirement is
Step 1, we have to import DevDB data to new tempDB and will proceed with new tempDB for migration.
Then after, we wanted to import the tempDB to NewDevDB and then wanted to replace newDevDB data(which is imported from tempDB) with QA DB's data (its QA oim 9.1 DB). (We have limitations to take QADB at first time itself, thats why, we are taking Dev DBdata in step 1).
My questions are
1. What are the required changes required for Moving oim11g DB to another DB (by dumping the same DB).
2. After, performing the migration, can we dump only the OIm 9.1 DBdata(QA) to OIm 11g DB? if yes, will it affect the oim 11g DB Schema.
Please suggest me, or do let me know, if you need any other information.
Thanks.

I think, I can consider my Question #1 is as equal to Oracle Identity Manager Database Host and Port Changes, So I can use the steps mentioned in the link http://download.oracle.com/docs/cd/E21764_01/doc.1111/e14308/handlinglcm.htm#CIAJBHHH (Section: 13.1.1 Oracle Identity Manager Database Host and Port Changes). Do we need to do any additional modification with in any configuration files? Please, can any one confirm it.
And Can any one help on my question #2.
Edited by: user13285646 on Aug 11, 2011 12:46 PM

Data Miner Extension in SQL Developer 4.0 EA3 Release: EA3 Repository Migration Failure

The Data Miner extension in the SQL Developer 4.0 EA3 release fails when attempting to migrate the repository to EA3. This posting contains instructions on how to recover from this failure as well as to successful migrate the repository from EA2 to EA3. There are no problems when just installing a fresh Data Miner repository.
Sorry about the difficulty if this has caused you any problems.
Mark
Failure message displayed in log when migrating to EA3:
Error report -
ORA-06550: line 96, column 40:
PLS-00382: expression is of wrong type
ORA-06550: line 96, column 7:
PL/SQL: Statement ignored
06550. 00000 - "line %s, column %s:\n%s"
*Cause:    Usually a PL/SQL compilation error.
*Action:
Instructions on how to recover from failure and continue using original version of SQL Developer:
1) Execute the following sql as SYS in order to allow the Data Miner repository to be open for use again:
UPDATE ODMRSYS.ODMR$REPOSITORY_PROPERTIES
SET PROPERTY_STR_VALUE = 'LOADED'
WHERE PROPERTY_NAME = 'REPOSITORY_STATUS';
COMMIT;
2) During attempted migrationto EA3 failed, access priviliges to the Data Miner repository are revoked from users. In order to use Data Miner again, these grants must be reapplied. You can either use the UI guided process to accomplish this, which requires the SYS password, or you can run the usergrants.sql script, again as the SYS user. For instructions on how to run the usergrants.sql script, or any adminstrative script, review the instructions contained in the install_scripts_readme.html file. You can find this file in the SQL Developer directories created when you unzipped SQL Developer. It is located in the following relative directory: \<SQL Developer Install Directory>\sqldeveloper\dataminer\scripts.
Instructions on how to successfully migrate to EA3.
If you have already attempted to migrate to EA3 and failed, then you need to perform the recovery instructions noted above, after which you can continue with the instructions below.
If you have not yet attempted to migrate to EA3, then just following the instructions below.
1) Replace all contents the script file createxmlworkflowsbackup.sql with specification contained at the end of this posting. The file to edit can be found in the \<SQL Developer Install Directory>\sqldeveloper\dataminer\scripts directory.
2) After completing the edit to createxmlworkflowsbackup.sql, you can proceed with the UI guided migration or perform the migration using the appropriate migration script. Review the install_scripts_readme.html file in the /dataminer/scripts directory for instructions on how to perform the migration using the script. For the UI migration, simply open any user connection in your Data Miner navigator, and you will be prompted to perform the migration.
WHENEVER SQLERROR EXIT SQL.SQLCODE;
DEFINE MAX_VERSIONS = 30
EXECUTE dbms_output.put_line('Start Backup Data Miner Workflows ' || systimestamp);
DECLARE
table_cnt NUMBER;
BEGIN
SELECT count(*) INTO table_cnt FROM all_tables WHERE owner='ODMRSYS' AND table_name='ODMR$WORKFLOWS_BACKUP';
IF (table_cnt = 0) THEN
    EXECUTE IMMEDIATE '
      CREATE TABLE ODMRSYS.ODMR$WORKFLOWS_BACKUP
        USER_NAME VARCHAR2(30 CHAR) NOT NULL
      , PROJECT_ID NUMBER NOT NULL
      , PROJECT_NAME VARCHAR2(30 CHAR) NOT NULL
      , PJ_CREATION_TIME TIMESTAMP(6) NOT NULL
      , PJ_LAST_UPDATED_TIME TIMESTAMP(6)
      , PJ_COMMENTS VARCHAR2(4000 CHAR)
      , WORKFLOW_ID NUMBER NOT NULL
      , WORKFLOW_NAME VARCHAR2(30 CHAR) NOT NULL
      , WORKFLOW_DATA SYS.XMLTYPE
      , CHAIN_NAME VARCHAR2(30 CHAR)
      , RUN_MODE VARCHAR2(30 CHAR)
      , STATUS VARCHAR2(30 CHAR) NOT NULL
      , WF_CREATION_TIME TIMESTAMP(6) NOT NULL
      , WF_LAST_UPDATED_TIME TIMESTAMP(6)
      , BACKUP_TIME TIMESTAMP(6) NOT NULL
      , VERSION NUMBER NOT NULL
      , WF_COMMENTS VARCHAR2(4000 CHAR)
      , CONSTRAINT ODMR$WORKFLOWS_BACKUP_PK PRIMARY KEY
          PROJECT_ID
        , WORKFLOW_ID
        , VERSION
        ENABLE
      LOGGING
      PCTFREE 10
      INITRANS 1
      XMLTYPE COLUMN "WORKFLOW_DATA" STORE AS BASICFILE CLOB';
END IF;
END;
DECLARE
schema_old_ver VARCHAR2(30);
schema_ver   VARCHAR2(30);
patch        VARCHAR2(30);
db_ver       VARCHAR2(30);
v_storage    VARCHAR2(30);
schema_data CLOB;
v_db_11_2_0_2 NUMBER; -- db is <= 11.2.0.2?
row_cnt      NUMBER;
ver_num      NUMBER := 1;
maintaindom NUMBER;
workflow_rec ODMRSYS.ODMR$WORKFLOWS_BACKUP%ROWTYPE;
BEGIN
SELECT STORAGE_TYPE INTO v_storage FROM ALL_XML_TAB_COLS WHERE OWNER='ODMRSYS' AND TABLE_NAME='ODMR$WORKFLOWS' AND COLUMN_NAME='WORKFLOW_DATA';
if (db is >= 11.2.0.3 AND SQL Dev > 3.0) OR (db is <= 11.2.0.2 AND MAINTAIN_DOM_PATCH_INSTALLED)
    back up all workflows
end if
IF (v_storage != 'BINARY') THEN
    -- determine xml schema version
    SELECT XMLSerialize(CONTENT SCHEMA AS CLOB) INTO schema_data
    FROM DBA_XML_SCHEMAS WHERE schema_url = 'http://xmlns.oracle.com/odmr11/odmr.xsd' AND owner = 'ODMRSYS';
    maintaindom := INSTR(schema_data, 'xdb:maintainDOM="false"', 1, 1);
    -- determine database version
    SELECT version INTO db_ver FROM product_component_version WHERE product LIKE 'Oracle Database%';
    --- Check schema compatibility
    schema_old_ver := '11.2.0.1.9'; -- default value
    BEGIN
      SELECT property_str_value INTO schema_ver
      FROM "ODMRSYS"."ODMR$REPOSITORY_PROPERTIES" WHERE property_name = 'WF_VERSION';
      IF schema_old_ver = schema_ver THEN
        IF NOT (db_ver = '11.2.0.1' OR db_ver = '11.2.0.2') THEN
          dbms_output.put_line('WARNING: The backup process can not be done, The workflows need to be migrated first');
        RETURN;
        END IF;
      END IF;
    EXCEPTION WHEN NO_DATA_FOUND THEN
      schema_ver := schema_old_ver;
      dbms_output.put_line('No WF_VERSION found. Defaults to: ' || schema_old_ver);
    END;
    -- determine if MAINTAIN_DOM_PATCH_INSTALLED
    IF (INSTR(db_ver, '11.2.0.2') > 0 OR INSTR(db_ver, '11.2.0.1') > 0 OR INSTR(db_ver, '11.2.0.0') > 0) THEN
      v_db_11_2_0_2 := 1;
      BEGIN
        SELECT PROPERTY_STR_VALUE INTO patch FROM ODMRSYS.ODMR$REPOSITORY_PROPERTIES WHERE PROPERTY_NAME = 'MAINTAIN_DOM_PATCH_INSTALLED';
        patch := UPPER(patch);
      EXCEPTION WHEN NO_DATA_FOUND THEN
        patch := 'FALSE';
      END;
    ELSE
      v_db_11_2_0_2 := 0;
    END IF;
END IF;
IF (   v_storage = 'BINARY'
      OR (v_db_11_2_0_2 = 0) -- db is >= 11.2.0.3
      OR ((v_db_11_2_0_2 > 0) AND ((patch = 'TRUE') OR (maintaindom = 0))) ) THEN -- db is <= 11.2.0.2 AND (MAINTAIN_DOM_PATCH_INSTALLED OR maintaindom="true")
    SELECT count(*) INTO row_cnt FROM ODMRSYS.ODMR$WORKFLOWS_BACKUP;
    IF (row_cnt > 0) THEN
      SELECT NVL(MAX(VERSION)+1,1) INTO ver_num FROM ODMRSYS.ODMR$WORKFLOWS_BACKUP;
    END IF;
    FOR wf IN (
      SELECT
        p.USER_NAME "USER_NAME",
        p.PROJECT_ID "PROJECT_ID",
        p.PROJECT_NAME "PROJECT_NAME",
        p.CREATION_TIME "PJ_CREATION_TIME",
        p.LAST_UPDATED_TIME "PJ_LAST_UPDATED_TIME",
        p.COMMENTS "PJ_COMMENTS",
        x.WORKFLOW_ID "WORKFLOW_ID",
        x.WORKFLOW_NAME "WORKFLOW_NAME",
        xmlserialize(DOCUMENT x.WORKFLOW_DATA as CLOB indent size = 2) "WORKFLOW_DATA",
        x.CHAIN_NAME "CHAIN_NAME",
        x.RUN_MODE "RUN_MODE",
        x.STATUS "STATUS",
        x.CREATION_TIME "WF_CREATION_TIME",
        x.LAST_UPDATED_TIME "WF_LAST_UPDATED_TIME",
        x.COMMENTS "WF_COMMENTS"
      FROM ODMRSYS.ODMR$PROJECTS p, ODMRSYS.ODMR$WORKFLOWS x
      WHERE p.PROJECT_ID = x.PROJECT_ID
    LOOP
      workflow_rec.USER_NAME := wf.USER_NAME;
      workflow_rec.PROJECT_ID := wf.PROJECT_ID;
      workflow_rec.PROJECT_NAME := wf.PROJECT_NAME;
      workflow_rec.PJ_CREATION_TIME := wf.PJ_CREATION_TIME;
      workflow_rec.PJ_LAST_UPDATED_TIME := wf.PJ_LAST_UPDATED_TIME;
      workflow_rec.PJ_COMMENTS := wf.PJ_COMMENTS;
      workflow_rec.WORKFLOW_ID := wf.WORKFLOW_ID;
      workflow_rec.WORKFLOW_NAME := wf.WORKFLOW_NAME;
      workflow_rec.WORKFLOW_DATA := SYS.XMLTYPE(wf.WORKFLOW_DATA);
      workflow_rec.CHAIN_NAME := wf.CHAIN_NAME;
      workflow_rec.RUN_MODE := wf.RUN_MODE;
      workflow_rec.STATUS := wf.STATUS;
      workflow_rec.WF_CREATION_TIME := wf.WF_CREATION_TIME;
      workflow_rec.WF_LAST_UPDATED_TIME := wf.WF_LAST_UPDATED_TIME;
      workflow_rec.BACKUP_TIME := SYSTIMESTAMP;
      workflow_rec.VERSION := ver_num;
      workflow_rec.WF_COMMENTS := wf.WF_COMMENTS;
      BEGIN
        -- Output the ids (proj name, workflow name, proj id, workflow id)
        dbms_output.put_line('Backup workflow: ('||wf.PROJECT_NAME||', '||wf.WORKFLOW_NAME||', '||wf.PROJECT_ID||', '||wf.WORKFLOW_ID||')');
        INSERT INTO ODMRSYS.ODMR$WORKFLOWS_BACKUP VALUES workflow_rec;
        COMMIT;
      EXCEPTION WHEN OTHERS THEN
        dbms_output.put_line('Backup workflow failed: ('||wf.PROJECT_NAME||', '||wf.WORKFLOW_NAME||', '||wf.PROJECT_ID||', '||wf.WORKFLOW_ID||')');
      END;
    END LOOP;
END IF;
-- keep the latest 30 versions
EXECUTE IMMEDIATE 'DELETE FROM ODMRSYS.ODMR$WORKFLOWS_BACKUP WHERE VERSION <= :1' USING (ver_num - &MAX_VERSIONS);
COMMIT;
EXCEPTION WHEN OTHERS THEN
ROLLBACK;
RAISE_APPLICATION_ERROR(-20000, 'Workflow backup failed. Review install log.');
END;
EXECUTE dbms_output.put_line('End Backup Data Miner Workflows. ' || systimestamp);

823006 wrote:
5.a. XLS export of big number columns looses precision, for example a number(38) column with all digits used.
I believe excel only holds 15 digits of precision.
Edited by: 823006 on Jan 18, 2011 8:14 AMThen it would be nice if you can define the "excel type" of each column. So you can make this number a "string" in the XLS.
Edited by: user9361780 on Jan 18, 2011 9:12 AM

Created Migration Repository by accident as Apps User! Can I undo it?

I am a very stupid fool, and I am scared that I might have done something to one of our clones on PROD via something I just did in SQL Developer. I am too much of a coward to mention it to one of our DBAs as violence may result from my admission!
I was following this guide:
http://www.oracle.com/technology/obe/11gr1_db/appdev/msamigrate/msamigrate.htm
In case you need it, this is the result from "select * from v$version":
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
PL/SQL Release 10.2.0.4.0 - Production
CORE 10.2.0.4.0 Production
TNS for IBM/AIX RISC System/6000: Version 10.2.0.4.0 - Productio
NLSRTL Version 10.2.0.4.0 - Production
Anyway, I got to this bit, while connected to the DB as apps user (yes, stupid I know).
On the web guide, I got to this step:
Creating the Migration Repository > 3 > Now you can create the repository in this users connection. Right click on the omwbrep_orcl connection and select Associate Migration Repository
As soon as I clicked it, and it started churning away, I realised I was way, way, way out of my depth, creating stuff on the DB as an apps user (aaaaah, I am a fool).
I cancelled the operation, and was told that something had been created.
I am now really worried I've done something really bad on the database, but I have no idea what I just did, how to check what I did, and if possible, how to undo it.
Any advice much appreciated, and my apologies for being so stupid, and doing stuff as an Apps user without knowing what I was doing.
Thanks

Aaah. I just read this in the JDeveloper help doc:
Delete or Truncate Repository
The Delete Repository dialog box is displayed if you click Migration, then Repository Management, then Delete Repository; the Truncate Repository dialog box is displayed if you click Migration, then Repository Management, then Truncate Repository.
Deleting a repository removes all schema objects that are used for the migration repository. Truncating a repository deletes all data from schema objects that are used for the migration repository, but does not delete the schema objects themselves, effectively leaving you with an empty repository.
Repository: Name of the database connection in which to delete or truncate the migration repository.
I therefore went to Migration Repository > Delete Migration Repository, thinking I would be able to confirm / view anything first, but it just went ahead and deleted a load of stuff.
Can anyone advise please if I have just done something even more stupid than creating a repository in the first place, and then cancelling the operating part way through?
Good grief, I am so stupid :(

Migration to an existing 6i repository

We updated the repository from 1.3.2 to 6 (the repository owner is AAA). At the same time, we created a new 6i target repository (the repository owner is BBB). We now plan to migrate the repository from 6 to 6i.
Two questions:
1. The repositories have different owners. Will that cause a problem or can the repository have more than one owner?
2. Will it cause a problem if there is already an id for a user and that user has objects in the repository?
Thank you in advance.
Kyle
null

Kyle,
Repository 6 and 6i can have different owners. Ensure you read the migration section in the install guide. You should be migrating between databases, thus you will need to recreate the database users in the new database. Scripts are provided and documented in the migration guide.
David

Migrate OIM repository

Similar Messages

Maybe you are looking for