ODI Studio 11g Hangs at “Initialize Search Engine” When Opening Any Repository Object


Possible cause is the corrupt ODI layout file.

1. Remove the ODI layout file windowinglayout.xml.

It should be in %APPDATA%\odi\systemVERSION\o.ide.VERSION

Examples:

On Windows XP: C:\Documents and Settings\Application Data\odi\system11.1.1.6.0\o.ide.11.1.1.6.38.61.92
On Windows 7: C:\Users\<myUserName>\AppData\Roaming\odi\system11.1.1.6.0\o.ide.11.1.1.6.38.61.92
On Linux: home/<myUserName>/.odi/system11.1.1.6.0/o.ide.11.1.1.6.38.61.9
2. Restart ODI Studio and try again.

Thanks,
~KKT~

ODI Migration – Move repository from one instance to another


The best way to relocate an ODI Repository from one RDBMS instance/server to another is to use the standard Import / Export tools delivered with database software and set the new connection parameters for the Repository.

For example, the following procedure show how to relocate a Repository to a new Oracle instance:

Physically copying the database schemas

Use IMP/EXP or similar database tools, export the database and / or schemas containing the ODI Repositories and import them to the new database instance.

Setting the new connection parameters with ODI

1. Launch Topology Manager. In the login window, edit the login parameter set and change the connection parameters to point to the new server which hosts the Master repository and logon to Topology Manager.
2. Expand the tree structure of the repositories.
3. Edit each Work Repository that is now hosted on a new server and edit its connection parameters by clicking on the Connection button
4. Modify the connection parameters (URL and user) of the Work Repository and save it by clicking ‘OK’
5. Launch Designer. In the Login Window, edit the login properties and change the connection to the Master Repository to comply with the new server properties.
6. Modify your odiparams.bat (.sh) script to reflect the new connection parameters to your Master Repository.
7. For each ODI Agent configuration do not forget to update the odiparams.bat (.sh) script as indicated in step 6 above.

Thanks,
~KKT~