ODI Upgradation

HI ,
My curent enviromen tis ODI 11.1.1.5 G ORACLE databse 11g .so i want to upgrade to ODI 11.1.1.6 ,
Please let me know the what all steps are required.
I need to install any pacth for ODI 11.1.1.6 or need to create new ODI 11.1.1.6 installer and what about database reposotiries.
I have only one database user for master and work repository.
Regards.
Srini

Hi Srinivas,
You need to go for fresh 11.6 installation(Its not a patch release which is discussed in the forum earlier). Its not required to uninstall 11.5 version.But it depends on you if you want to uninstall the previous version.
Then after 11.6 installation call the ua.bat to upgrade your repositories.
Thanks.

Similar Messages

Upgrade ODI Upgrade 10.1. 3.4 to 10.1. 3.5

On windows 64bit 2003 server, with oracle db server 11.1.0.6 we have ODI Upgrade version 10.1. 3.4 in Dev Env.
We have many projects/models and 100 interfaces in the current version 10.1.3.4
We want to upgrade ODI to 10.1. 3.5
1. What are the upgrade steps?
2 Is all interfaces will be work ok after upgrade?
3. Will the export/import work?
Thanks

Take a backup of your existing ODI 10.1.3.4
Copy /paste the ODI 10.1.3.5 "oracledi " into your existing ODI 10.1.3.4
You need to upgrade your master repository using oracledi\bin\mupgrade.bat ot .sh script .
Then upgrade your work repository from Topology .
You can now run interfaces, packages, etc developed with previous versions of Oracle Data Integrator.
Thanks,
Sutirtha

ODI upgrade from 10.1.3.5 to 11.1.1.7 Issue

Hi guys,
My first attempt to upgrade from ODI 10.1.3.5 fails, so I drop users that I clone and recover. But my second attempt it is failing with the following error:
0000JxxDbgPDc_RMuY6EUH1HmVgL000004,0] Target Work Repository ODIWORK upgrade is started.
[2013-06-25T16:23:07.011-05:00] [ODI] [ERROR] [UPGCMP-00332] [upgrade.ODI] [tid: 13] [ecid: 0000JxxDbgPDc_RMuY6EUH1HmVgL000004,0] Work Repository has invalid state.
[2013-06-25T16:23:07.011-05:00] [ODI] [ERROR] [] [upgrade.ODI] [tid: 13] [ecid: 0000JxxDbgPDc_RMuY6EUH1HmVgL000004,0] Cause: Previous upgrade of Work Repository was unsuccessful. Action: Restore Work Repository from Backup and try to upgrade again.
[2013-06-25T16:23:07.011-05:00] [eclipse] [NOTIFICATION:16] [] [org.eclipse.persistence.default.connection] [tid: 13] [ecid: 0000JxxDbgPDc_RMuY6EUH1HmVgL000004,0] disconnect
[2013-06-25T16:23:07.011-05:00] [eclipse] [NOTIFICATION] [] [org.eclipse.persistence.default] [tid: 13] [ecid: 0000JxxDbgPDc_RMuY6EUH1HmVgL000004,0] master-session logout successful
So please, any help will be appreciated.

duplicate of Issue at upgrade 10g to 11.1.1.7

ODI upgrade issue - 10.1.3.5 to 10.1.3.6

Hi,
I have tried to Upgrade to upgrade ODI 10.1.3.5 to version 10.1.3.6 using patch p9377717_101360_Generic.
But facing issue while starting the master repository upgrade - the messages are coming as below -
"error detected during repository upgrade "
"com.sunopsis.tools.core.exception.SnpsRuntimeException: java.lang.NullPointerException" and so on...all weird messages.
Can anybody please help me on this please?
Also, I am upgrading ODI to 10.1.3.6 as we are supposed to load data into Essbase 11.1.2, will the existing version
i.e. 10.1.3.5 will work with Essbase 11.1.2?

Hi ORV,
If I remember well, you can skip the repository creation as the upgrade assistant will upgrade your 10g cloned reps to 11g reps.
You only need to install 11g standalone agent(s) to replace the 10g runtime agent(s).
Regards,
JeromeFr

ODI upgrade from 10.1.3.5 to 11.1.1.6

Hi guys I have a doubt with one step of the upgrade guide from ODI 10.1.3.5 to 11.1.1.6. The step say that after back up and clone the ODI repositories we must install and configure ODI 11.1.1.6.
At this step will I create the master and work repositories new( or I must specify the cloned repositories)?
Thanks

Hi ORV,
If I remember well, you can skip the repository creation as the upgrade assistant will upgrade your 10g cloned reps to 11g reps.
You only need to install 11g standalone agent(s) to replace the 10g runtime agent(s).
Regards,
JeromeFr

ODI upgrade master repository 10.1.3.5.0 - 10.1.3.6.1

Hello,
i am facing problem with upgrade of master repository ODI 10.1.3.5.0 -> 10.1.3.6.1 odi_patch_10.1.3.6.1 (p9377717_101360_Generic)
i followed steps as described in upgrade procedure (Remove the content of the oracledi/lib/scripts/ sub-directory your Oracle Data Integrator installation directory.
Copy the content of the oracledi sub-directory of the temporary directory to your Oracle Data Integrator installation directory. The temporary directory content should overwrite the Oracle Data Integrator installation directory content.)
when running upgrade script (./mupgrade.sh) there is NO ORACLE Technologies appearing in the wizard....
only Hypersonic SQL and Informix left
same in Windows XP and Linux.....

i just downloaded and unpacked odi_patch_10.1.3.6.1 (p9377717_101360_Generic.zip) from support.oracle.com
how can i check? there is the structure of the patch
bin
demo
doc
drivers
impexp
lib
tools
./bin:
startcmd.bat
./demo:
xml
./demo/xml:
personal.xsd
./doc:
index_km.htm
km
webhelp
./doc/km:
odiafm_93110_readme.pdf
odiap_93110_readme.pdf
odiess_readme.pdf
odiess_users.pdf
odigs_sapabapbw.pdf
odigs_sapabap.pdf
odi_km_ref_guide v1.3.pdf
./doc/webhelp:
en
./doc/webhelp/en:
index.hhc
index.hhk
printable
ref_tools
release_snps.htm
setup
usermanual
whgdata
whxdata
./doc/webhelp/en/printable:
snps_ref_tools.pdf
snps_setup.pdf
snps_users.pdf
./doc/webhelp/en/ref_tools:
odiftpget.htm
odiftpput.htm
odiscpget.htm
odiscpput.htm
odisftpget.htm
odisftpput.htm
snpsfiledelete.html
./doc/webhelp/en/setup:
setup.htm
sunopsis.log
./doc/webhelp/en/usermanual:
technos
./doc/webhelp/en/usermanual/technos:
how_to.htm
jms
jms_xml
./doc/webhelp/en/usermanual/technos/jms:
creating_a_jms_data_server.htm
creating_a_physical_schema_for_jms.htm
defining_a_jms_model.htm
choosing_the_right_kms_for_jms.htm
jms_standard_properties.htm
using_jms_properties.htm
./doc/webhelp/en/usermanual/technos/jms_xml:
creating_a_jms_xml_data_server.htm
creating_and_reverse-engineering_a_jms_xml_model.htm
creating_a_physical_schema_for_jms_xml.htm
choosing_the_right_kms_for_jms_xml.htm
./doc/webhelp/en/whgdata:
whlstfl0.htm
whlstfl11.htm
whlstfl16.htm
whlstfl18.htm
whlstfl20.htm
whlstfl21.htm
whlstfl22.htm
whlstfl23.htm
whlstfl24.htm
whlstfl25.htm
whlstfl26.htm
whlstfl3.htm
whlstfl4.htm
whlstfl7.htm
whlstfl8.htm
whlstf0.htm
whlstf1.htm
whlstf10.htm
whlstf11.htm
whlstf12.htm
whlstf13.htm
whlstf14.htm
whlstf15.htm
whlstf16.htm
whlstf17.htm
whlstf18.htm
whlstf19.htm
whlstf2.htm
whlstf20.htm
whlstf21.htm
whlstf22.htm
whlstf23.htm
whlstf24.htm
whlstf25.htm
whlstf26.htm
whlstf27.htm
whlstf28.htm
whlstf29.htm
whlstf3.htm
whlstf30.htm
whlstf31.htm
whlstf32.htm
whlstf33.htm
whlstf34.htm
whlstf35.htm
whlstf36.htm
whlstf37.htm
whlstf38.htm
whlstf39.htm
whlstf4.htm
whlstf40.htm
whlstf41.htm
whlstf42.htm
whlstf43.htm
whlstf44.htm
whlstf45.htm
whlstf46.htm
whlstf47.htm
whlstf48.htm
whlstf49.htm
whlstf5.htm
whlstf50.htm
whlstf51.htm
whlstf52.htm
whlstf53.htm
whlstf54.htm
whlstf55.htm
whlstf56.htm
whlstf57.htm
whlstf58.htm
whlstf59.htm
whlstf6.htm
whlstf60.htm
whlstf61.htm
whlstf62.htm
whlstf63.htm
whlstf64.htm
whlstf65.htm
whlstf66.htm
whlstf67.htm
whlstf68.htm
whlstf69.htm
whlstf7.htm
whlstf70.htm
whlstf71.htm
whlstf72.htm
whlstf8.htm
whlstf9.htm
whlsti0.htm
whlsti1.htm
whlsti2.htm
whlstt0.htm
whlstt1.htm
whlstt10.htm
whlstt100.htm
whlstt101.htm
whlstt102.htm
whlstt103.htm
whlstt104.htm
whlstt11.htm
whlstt12.htm
whlstt13.htm
whlstt14.htm
whlstt15.htm
whlstt16.htm
whlstt17.htm
whlstt18.htm
whlstt19.htm
whlstt2.htm
whlstt20.htm
whlstt21.htm
whlstt22.htm
whlstt23.htm
whlstt24.htm
whlstt25.htm
whlstt26.htm
whlstt27.htm
whlstt28.htm
whlstt29.htm
whlstt3.htm
whlstt30.htm
whlstt31.htm
whlstt32.htm
whlstt33.htm
whlstt34.htm
whlstt35.htm
whlstt36.htm
whlstt37.htm
whlstt38.htm
whlstt39.htm
whlstt4.htm
whlstt40.htm
whlstt41.htm
whlstt42.htm
whlstt43.htm
whlstt44.htm
whlstt45.htm
whlstt46.htm
whlstt47.htm
whlstt48.htm
whlstt49.htm
whlstt5.htm
whlstt50.htm
whlstt51.htm
whlstt52.htm
whlstt53.htm
whlstt54.htm
whlstt55.htm
whlstt56.htm
whlstt57.htm
whlstt58.htm
whlstt59.htm
whlstt6.htm
whlstt60.htm
whlstt61.htm
whlstt62.htm
whlstt63.htm
whlstt64.htm
whlstt65.htm
whlstt66.htm
whlstt67.htm
whlstt68.htm
whlstt69.htm
whlstt7.htm
whlstt70.htm
whlstt71.htm
whlstt72.htm
whlstt73.htm
whlstt74.htm
whlstt75.htm
whlstt76.htm
whlstt77.htm
whlstt78.htm
whlstt79.htm
whlstt8.htm
whlstt80.htm
whlstt81.htm
whlstt82.htm
whlstt83.htm
whlstt84.htm
whlstt85.htm
whlstt86.htm
whlstt87.htm
whlstt88.htm
whlstt89.htm
whlstt9.htm
whlstt90.htm
whlstt91.htm
whlstt92.htm
whlstt93.htm
whlstt94.htm
whlstt95.htm
whlstt96.htm
whlstt97.htm
whlstt98.htm
whlstt99.htm
./doc/webhelp/en/whxdata:
whftdata0.xml
whftdata1.xml
whftdata2.xml
whftdata3.xml
whfts.xml
whfwdata0.xml
whfwdata1.xml
whfwdata10.xml
whfwdata11.xml
whfwdata12.xml
whfwdata13.xml
whfwdata14.xml
whfwdata15.xml
whfwdata16.xml
whfwdata17.xml
whfwdata18.xml
whfwdata19.xml
whfwdata2.xml
whfwdata20.xml
whfwdata21.xml
whfwdata22.xml
whfwdata23.xml
whfwdata24.xml
whfwdata25.xml
whfwdata26.xml
whfwdata27.xml
whfwdata28.xml
whfwdata29.xml
whfwdata3.xml
whfwdata30.xml
whfwdata31.xml
whfwdata32.xml
whfwdata4.xml
whfwdata5.xml
whfwdata6.xml
whfwdata7.xml
whfwdata8.xml
whfwdata9.xml
whidata0.xml
whidata1.xml
whidata2.xml
whidata3.xml
whidata4.xml
whidata5.xml
whidata6.xml
whidx.xml
whtdata0.xml
whtdata7.xml
./drivers:
ess_es_server.jar
ess_japi.jar
HFMDriver.dll
HFMDriver64.dll
odihapp_common.jar
odihapp_essbase.jar
odi_hfm.jar
odi-sap.jar
snpsfile.jar
snpsxmlo.jar
./impexp:
GAC_Hypersonic SQL Default.xml
GAC_Informix Default.xml
KM_CKM Teradata.xml
KM_IKM File to Teradata (TTU).xml
KM_IKM Oracle Slowly Changing Dimension.xml
KM_IKM SQL to Hyperion Essbase (DATA).xml
KM_IKM SQL to Teradata (TTU).xml
KM_IKM Teradata Control Append.xml
KM_JKM DB2 400 Simple (Journal).xml
KM_JKM Oracle to Oracle Consistent (OGG).xml
KM_LKM DB2_400 Journal to SQL .xml
KM_LKM File to Netezza (NZLOAD).xml
KM_LKM File to Oracle (SQLLDR).xml
KM_LKM File to Teradata (TTU).xml
KM_LKM MSSQL to Oracle (BCPSQLLDR).xml
KM_LKM SQL to Teradata (TTU).xml
KM_RKM MSSQL.xml
KM_RKM Oracle Olap (Jython).xml
KM_RKM Oracle.xml
KM_ RKM Salesforce.com.xml
KM_RKM Teradata.xml
LANG_SQL.xml
PROF_DESIGNER.xml
PROF_METADATA ADMIN.xml
PROF_NG DESIGNER.xml
PROF_NG METADATA ADMIN.xml
PROF_NG REPOSITORY EXPLORER.xml
PROF_NG VERSION ADMIN.xml
PROF_OPERATOR.xml
PROF_REPOSITORY EXPLORER.xml
PROF_SECURITY ADMIN.xml
PROF_TOPOLOGY ADMIN.xml
PROF_VERSION ADMIN.xml
TECH_Attunity.xml
TECH_BTrieve.xml
TECH_DBase.xml
TECH_Derby.xml
TECH_File.xml
TECH_Generic SQL.xml
TECH_Hyperion Essbase.xml
TECH_Hyperion Financial Management.xml
TECH_Hyperion Planning.xml
TECH_Hypersonic SQL.xml
TECH_IBM DB2 UDB.xml
TECH_IBM DB2400.xml
TECH_Informix.xml
TECH_Ingres.xml
TECH_Interbase.xml
TECH_JMS Queue.xml
TECH_JMS Queue XML.xml
TECH_JMS Topic.xml
TECH_JMS Topic XML.xml
TECH_LDAP.xml
TECH_Microsoft Access.xml
TECH_Microsoft Excel.xml
TECH_Microsoft SQL Server.xml
TECH_MySQL.xml
TECH_Netezza.xml
TECH_Operating System.xml
TECH_Oracle BAM.xml
TECH_Oracle.xml
TECH_Paradox.xml
TECH_PostgreSQL.xml
TECH_Progress.xml
TECH_Salesforce.com.xml
TECH_SAP ABAP.xml
TECH_SAP Java Connector.xml
TECH_SAS.xml
TECH_Sunopsis Engine.xml
TECH_Sybase AS Anywhere.xml
TECH_Sybase AS Enterprise.xml
TECH_Sybase AS IQ.xml
TECH_Teradata.xml
TECH_Universe.xml
TECH_XML.xml
./lib:
scripts
snpshelp.zip
snpsws.zip
sunopsis.zip
./lib/scripts:
DERBY
HYPERSONIC_SQL
IBM_DB2_UDB
IBM_DB2_400
INFORMIX
MICROSOFT_SQL_SERVER
ORACLE
POSTGRESQL
SYBASE_AS_ANYWHERE
SYBASE_AS_ENTERPRISE
SYBASE_AS_IQ
xml
./lib/scripts/DERBY:
E_CREATE.xml
E_DROP.xml
M_CREATE.xml
M_DROP.xml
patches
W_CREATE.xml
W_DROP.xml
./lib/scripts/DERBY/patches:
E_04.02.02.01_04.02.03.01.xml
E_410201_420101.xml
E_420101_420201.xml
M_04.02.02.01_04.02.03.01.xml
M_410201_420101.xml
M_420101_420201.xml
W_04.02.02.01_04.02.03.01.xml
W_410201_420101.xml
W_420101_420201.xml
./lib/scripts/HYPERSONIC_SQL:
E_CREATE.xml
E_DROP.xml
M_CREATE.xml
M_DROP.xml
patches
W_CREATE.xml
W_DROP.xml
./lib/scripts/HYPERSONIC_SQL/patches:
E_04.02.02.01_04.02.03.01.xml
E_300101.xml
E_300101_300102.xml
E_300102_300103.xml
E_300103_300104.xml
E_300104_310101.xml
E_310101_320301.xml
E_320301_400101.xml
E_400101_410101.xml
E_410101_410201.xml
E_410201_420101.xml
E_420101_420201.xml
M_04.02.02.01_04.02.03.01.xml
M_300101.xml
M_300101_300102.xml
M_300102_300103.xml
M_300103_300104.xml
M_300104_300105.xml
M_300105_310101.xml
M_310101_310201.xml
M_310201_320301.xml
M_320301_400101.xml
M_400101_410101.xml
M_410101_410201.xml
M_410201_420101.xml
M_420101_420201.xml
W_04.02.02.01_04.02.03.01.xml
W_300101.xml
W_300101_300102.xml
W_300102_300103.xml
W_300103_310101.xml
W_310101_310201.xml
W_310201_320301.xml
W_320301_400101.xml
W_400101_410101.xml
W_410101_410201.xml
W_410201_420101.xml
W_420101_420201.xml
./lib/scripts/IBM_DB2_UDB:
E_CREATE.xml
E_DROP.xml
M_CREATE.xml
M_DROP.xml
patches
W_CREATE.xml
W_DROP.xml
./lib/scripts/IBM_DB2_UDB/patches:
E_04.02.02.01_04.02.03.01.xml
E_300101.xml
E_300101_300102.xml
E_300102_300103.xml
E_300103_300104.xml
E_300104_310101.xml
E_310101_320301.xml
E_320301_400101.xml
E_400101_410101.xml
E_410101_410201.xml
E_410201_420101.xml
E_420101_420201.xml
M_04.02.02.01_04.02.03.01.xml
M_300101.xml
M_300101_300102.xml
M_300102_300103.xml
M_300103_300104.xml
M_300104_300105.xml
M_300105_310101.xml
M_310101_310201.xml
M_310201_320301.xml
M_320301_400101.xml
M_400101_410101.xml
M_410101_410201.xml
M_410201_420101.xml
M_420101_420201.xml
W_04.02.02.01_04.02.03.01.xml
W_300101.xml
W_300101_300102.xml
W_300102_300103.xml
W_300103_310101.xml
W_310101_310201.xml
W_310201_320301.xml
W_320301_400101.xml
W_400101_410101.xml
W_410101_410201.xml
W_410201_420101.xml
W_420101_420201.xml
./lib/scripts/IBM_DB2_400:
E_CREATE.xml
E_DROP.xml
M_CREATE.xml
M_DROP.xml
patches
W_CREATE.xml
W_DROP.xml
./lib/scripts/IBM_DB2_400/patches:
E_04.02.02.01_04.02.03.01.xml
E_300101.xml
E_300101_300102.xml
E_300102_300103.xml
E_300103_300104.xml
E_300104_310101.xml
E_310101_320301.xml
E_320301_400101.xml
E_400101_410101.xml
E_410101_410201.xml
E_410201_420101.xml
E_420101_420201.xml
M_04.02.02.01_04.02.03.01.xml
M_300101.xml
M_300101_300102.xml
M_300102_300103.xml
M_300103_300104.xml
M_300104_300105.xml
M_300105_310101.xml
M_310101_310201.xml
M_310201_320301.xml
M_320301_400101.xml
M_400101_410101.xml
M_410101_410201.xml
M_410201_420101.xml
M_420101_420201.xml
W_04.02.02.01_04.02.03.01.xml
W_300101.xml
W_300101_300102.xml
W_300102_300103.xml
W_300103_310101.xml
W_310101_310201.xml
W_310201_320301.xml
W_320301_400101.xml
W_400101_410101.xml
W_410101_410201.xml
W_410201_420101.xml
W_420101_420201.xml
./lib/scripts/INFORMIX:
E_CREATE.xml
E_DROP.xml
M_CREATE.xml
M_DROP.xml
patches
W_CREATE.xml
W_DROP.xml
./lib/scripts/INFORMIX/patches:
E_04.02.02.01_04.02.03.01.xml
E_300101.xml
E_300101_300102.xml
E_300102_300103.xml
E_300103_300104.xml
E_300104_310101.xml
E_310101_320301.xml
E_320301_400101.xml
E_400101_410101.xml
E_410101_410201.xml
E_410201_420101.xml
E_420101_420201.xml
M_04.02.02.01_04.02.03.01.xml
M_300101.xml
M_300101_300102.xml
M_300102_300103.xml
M_300103_300104.xml
M_300104_300105.xml
M_300105_310101.xml
M_310101_310201.xml
M_310201_320301.xml
M_320301_400101.xml
M_400101_410101.xml
M_410101_410201.xml
M_410201_420101.xml
M_420101_420201.xml
W_04.02.02.01_04.02.03.01.xml
W_300101.xml
W_300101_300102.xml
W_300102_300103.xml
W_300103_310101.xml
W_310101_310201.xml
W_310201_320301.xml
W_320301_400101.xml
W_400101_410101.xml
W_410101_410201.xml
W_410201_420101.xml
W_420101_420201.xml
./lib/scripts/MICROSOFT_SQL_SERVER:
E_CREATE.xml
E_DROP.xml
M_CREATE.xml
M_DROP.xml
patches
W_CREATE.xml
W_DROP.xml
./lib/scripts/MICROSOFT_SQL_SERVER/patches:
E_04.02.02.01_04.02.03.01.xml
E_300101.xml
E_300101_300102.xml
E_300102_300103.xml
E_300103_300104.xml
E_300104_310101.xml
E_310101_320301.xml
E_320301_400101.xml
E_400101_410101.xml
E_410101_410201.xml
E_410201_420101.xml
E_420101_420201.xml
M_04.02.02.01_04.02.03.01.xml
M_300101.xml
M_300101_300102.xml
M_300102_300103.xml
M_300103_300104.xml
M_300104_300105.xml
M_300105_310101.xml
M_310101_310201.xml
M_310201_320301.xml
M_320301_400101.xml
M_400101_410101.xml
M_410101_410201.xml
M_410201_420101.xml
M_420101_420201.xml
W_04.02.02.01_04.02.03.01.xml
W_300101.xml
W_300101_300102.xml
W_300102_300103.xml
W_300103_310101.xml
W_310101_310201.xml
W_310201_320301.xml
W_320301_400101.xml
W_400101_410101.xml
W_410101_410201.xml
W_410201_420101.xml
W_420101_420201.xml
./lib/scripts/ORACLE:
E_CREATE.xml
E_DROP.xml
M_CREATE.xml
M_DROP.xml
patches
W_CREATE.xml
W_DROP.xml
./lib/scripts/ORACLE/patches:
E_04.02.02.01_04.02.03.01.xml
E_300101.xml
E_300101_300102.xml
E_300102_300103.xml
E_300103_300104.xml
E_300104_310101.xml
E_310101_320301.xml
E_320301_400101.xml
E_400101_410101.xml
E_410101_410201.xml
E_410201_420101.xml
E_420101_420201.xml
M_04.02.02.01_04.02.03.01.xml
M_300101.xml
M_300101_300102.xml
M_300102_300103.xml
M_300103_300104.xml
M_300104_300105.xml
M_300105_310101.xml
M_310101_310201.xml
M_310201_320301.xml
M_320301_400101.xml
M_400101_410101.xml
M_410101_410201.xml
M_410201_420101.xml
M_420101_420201.xml
W_04.02.02.01_04.02.03.01.xml
W_300101.xml
W_300101_300102.xml
W_300102_300103.xml
W_300103_310101.xml
W_310101_310201.xml
W_310201_320301.xml
W_320301_400101.xml
W_400101_410101.xml
W_410101_410201.xml
W_410201_420101.xml
W_420101_420201.xml
./lib/scripts/POSTGRESQL:
E_CREATE.xml
E_DROP.xml
M_CREATE.xml
M_DROP.xml
patches
W_CREATE.xml
W_DROP.xml
./lib/scripts/POSTGRESQL/patches:
E_04.02.02.01_04.02.03.01.xml
E_320301_400101.xml
E_400101_410101.xml
E_410101_410201.xml
E_410201_420101.xml
E_420101_420201.xml
M_04.02.02.01_04.02.03.01.xml
M_320301_400101.xml
M_400101_410101.xml
M_410101_410201.xml
M_410201_420101.xml
M_420101_420201.xml
W_04.02.02.01_04.02.03.01.xml
W_320301_400101.xml
W_400101_410101.xml
W_410101_410201.xml
W_410201_420101.xml
W_420101_420201.xml
./lib/scripts/SYBASE_AS_ANYWHERE:
E_CREATE.xml
E_DROP.xml
M_CREATE.xml
M_DROP.xml
patches
W_CREATE.xml
W_DROP.xml
./lib/scripts/SYBASE_AS_ANYWHERE/patches:
E_04.02.02.01_04.02.03.01.xml
E_300101.xml
E_300101_300102.xml
E_300102_300103.xml
E_300103_300104.xml
E_300104_310101.xml
E_310101_320301.xml
E_320301_400101.xml
E_400101_410101.xml
E_410101_410201.xml
E_410201_420101.xml
E_420101_420201.xml
M_04.02.02.01_04.02.03.01.xml
M_300101.xml
M_300101_300102.xml
M_300102_300103.xml
M_300103_300104.xml
M_300104_300105.xml
M_300105_310101.xml
M_310101_310201.xml
M_310201_320301.xml
M_320301_400101.xml
M_400101_410101.xml
M_410101_410201.xml
M_410201_420101.xml
M_420101_420201.xml
W_04.02.02.01_04.02.03.01.xml
W_300101.xml
W_300101_300102.xml
W_300102_300103.xml
W_300103_310101.xml
W_310101_310201.xml
W_310201_320301.xml
W_320301_400101.xml
W_400101_410101.xml
W_410101_410201.xml
W_410201_420101.xml
W_420101_420201.xml
./lib/scripts/SYBASE_AS_ENTERPRISE:
E_CREATE.xml
E_DROP.xml
M_CREATE.xml
M_DROP.xml
patches
W_CREATE.xml
W_DROP.xml
./lib/scripts/SYBASE_AS_ENTERPRISE/patches:
E_04.02.02.01_04.02.03.01.xml
E_300101.xml
E_300101_300102.xml
E_300102_300103.xml
E_300103_300104.xml
E_300104_310101.xml
E_310101_320301.xml
E_320301_400101.xml
E_400101_410101.xml
E_410101_410201.xml
E_410201_420101.xml
E_420101_420201.xml
M_04.02.02.01_04.02.03.01.xml
M_300101.xml
M_300101_300102.xml
M_300102_300103.xml
M_300103_300104.xml
M_300104_300105.xml
M_300105_310101.xml
M_310101_310201.xml
M_310201_320301.xml
M_320301_400101.xml
M_400101_410101.xml
M_410101_410201.xml
M_410201_420101.xml
M_420101_420201.xml
W_04.02.02.01_04.02.03.01.xml
W_300101.xml
W_300101_300102.xml
W_300102_300103.xml
W_300103_310101.xml
W_310101_310201.xml
W_310201_320301.xml
W_320301_400101.xml
W_400101_410101.xml
W_410101_410201.xml
W_410201_420101.xml
W_420101_420201.xml
./lib/scripts/SYBASE_AS_IQ:
E_CREATE.xml
E_DROP.xml
M_CREATE.xml
M_DROP.xml
patches
W_CREATE.xml
W_DROP.xml
./lib/scripts/SYBASE_AS_IQ/patches:
E_CREATE.xml
E_DROP.xml
E_04.02.02.01_04.02.03.01.xml
E_300101.xml
E_300101_300102.xml
E_300102_300103.xml
E_300103_300104.xml
E_300104_310101.xml
E_310101_320301.xml
E_320301_400101.xml
E_400101_410101.xml
E_410101_410201.xml
E_410201_420101.xml
E_420101_420201.xml
M_CREATE.xml
M_DROP.xml
M_04.02.02.01_04.02.03.01.xml
M_300101.xml
M_300101_300102.xml
M_300102_300103.xml
M_300103_300104.xml
M_300104_300105.xml
M_300105_310101.xml
M_310101_310201.xml
M_310201_320301.xml
M_320301_400101.xml
M_400101_410101.xml
M_410101_410201.xml
M_410201_420101.xml
M_420101_420201.xml
W_CREATE.xml
W_DROP.xml
W_04.02.02.01_04.02.03.01.xml
W_300101.xml
W_300101_300102.xml
W_300102_300103.xml
W_300103_310101.xml
W_310101_310201.xml
W_310201_320301.xml
W_320301_400101.xml
W_400101_410101.xml
W_410101_410201.xml
W_410201_420101.xml
W_420101_420201.xml
./lib/scripts/xml:
CONN_SecurityConnection.xml
CONVDT_CONVDATATYPESLST.xml
DT_DATATYPESLST.xml
FIELD_FIELD_LST.xml
FLOOK_LOOKUP_LST.xml
LANG_SQL.xml
LOCREP_MASTERREPOSITORY.xml
OBJ_Column.xml
OBJ_DataServer.xml
OBJ_Datastore.xml
OBJ_Model.xml
OBJ_OBJ_SNPOPENTOOL_7800.xml
OBJ_OBJ_SNPSCENFOLDER_7700.xml
OBJ_Solution.xml
PROF_DESIGNER.xml
PROF_METADATAADMIN.xml
PROF_NGDESIGNER.xml
PROF_NGMETADATAADMIN.xml
PROF_NGREPOSITORYEXPLORER.xml
PROF_NGVERSIONADMIN.xml
PROF_OPERATOR.xml
PROF_REPOSITORYEXPLORER.xml
PROF_SECURITYADMIN.xml
PROF_TOPOLOGYADMIN.xml
PROF_VERSIONADMIN.xml
TECH_Attunity.xml
TECH_File.xml
TECH_HyperionEssbase.xml
TECH_HyperionFinancialManagement.xml
TECH_HypersonicSQL.xml
TECH_Informix.xml
TECH_SAPABAP.xml
TECH_SAPJavaConnector.xml
TECH_SAS.xml
./tools:
cdc_iseries
web_services
./tools/cdc_iseries:
SAVPGM0110
./tools/web_services:
odi-public-ws.aar

Jyhton issue with ODI upgrade

Hi,
I am trying to execute the jython script but when i execute this part
d = glob.glob(src + os.sep + 'd33*cts.txt') i am getting the following error :Traceback (innermost last):
File "<console>", line 1, in ?
AttributeError: class 'org.python.modules.os' has no attribute 'sep'
We have upgraded the repository from SunopsisV3 to ODI 10.1.3.4.2 version.
Can anyone what has to be done with this issue.

I also have the same problem. I have a shell script that is being called by ODI. The last line within that shell script is an ESSCMD batch script. I verified that the paths to all files are fully qualified. However I can't get the script to run in ODI. Did anyone ever find the solution to getting ESSCMD batch scripts to run within ODI?

Accessing the ETL Getting Started after ODI Upgrade - SOLVED

Connected to the topology manager as SUPERVISOR and upgraded the work repository.
Thanks
Fabio D'Alfonso
Hi,
I was going back to take a look at the Getting started with ETL.
After the upgrade to 10.1.3.5.3 (and also 10.1.3.6.0) I cannot access the sample environment.
I upgraded the sample repository but the message still states that the repository is outdated.
Should I setup a full new environment to get back the ability to look at the getting started?
Thanks
Fabio D'Alfonso
Edited by: Fabio D'Alfonso on Jun 9, 2010 2:33 PM

Connected to the topology manager as SUPERVISOR and upgraded the work repository.
Thanks
Fabio D'Alfonso
Hi,
I was going back to take a look at the Getting started with ETL.
After the upgrade to 10.1.3.5.3 (and also 10.1.3.6.0) I cannot access the sample environment.
I upgraded the sample repository but the message still states that the repository is outdated.
Should I setup a full new environment to get back the ability to look at the getting started?
Thanks
Fabio D'Alfonso
Edited by: Fabio D'Alfonso on Jun 9, 2010 2:33 PM

Upgrading ODI from 11.1.1.5.0 to 11.1.1.6.4

Hello,
Did anyone upgraded ODI from 11.1.1.5 to 11.1.1.6.4? Is there any documentation available for this patching?
Can someone please advise me the steps I need to follow?
Thanks.

Thanks, when I am trying to update under examine scree it says it says oracle data integrator failed
error message in logs:
+[2013-03-27T15:57:59.556-04:00] [Framework] [NOTIFICATION] [upgrade.Framework] Database driver version: 11.2.0.3.0+
+[2013-03-27T15:57:59.556-04:00] [ODI] [NOTIFICATION] [upgrade.ODI.ODI1] [[+
--------- ODIPlugin.examine called
+]]+
+[2013-03-27T15:57:59.587-04:00] [ODI] [ERROR] [UPGCMP-00339] [upgrade.ODI.ODI1] SCHEMA_VERSION_REGISTRY does not contain an entry for the Oracle ODI schema TDWH_SM_1.+
+[2013-03-27T15:57:59.587-04:00] [ODI] [ERROR] [upgrade.ODI.ODI1] Cause: ODI PSA is meant for upgrade of ODI repository created using RCU+
+[2013-03-27T15:57:59.587-04:00] [ODI] [ERROR] [upgrade.ODI.ODI1] Action: Please use ODI Upgrade Assisant to perform the upgrade operation from current version to 11.1.1.6.0.+
+[2013-03-27T15:57:59.587-04:00] [Framework] [NOTIFICATION] [UPGAST-00236] [upgrade.Framework] There is no schema version registry entry for component ODI+
+[2013-03-27T15:57:59.587-04:00] [Framework] [NOTIFICATION] [upgrade.Framework] Finished examining ODI.ODI1 with status: FAILURE.+
+[2013-03-27T15:57:59.587-04:00] [Framework] [NOTIFICATION] [upgrade.Framework] Finished examining components.+

Reverse engineer issues in ODI 11g

Hello gurus,
We are testing ODI upgrade and we have an issue while reversing a data model.Its an existing sql server table and in ODI when we click on the reverse engineer ODI datastore doesnt sync with sql server DB table.
Please help ?
Thanks,
Mastan.

Thank you so much for your reply....Yes thats exactly right it is not considering the deleted columns....when i try to remove the the data store it gives me an error saying
"object column : workflow_activity_identifier is referenced by: Txt CrossRef : 12142111, Txt CrossRef : 20617111
Cannot remove"
i think i have to edit my interfaces which is using the data store ? is there any way i can know how many interfaces are using this data store?
Thanks for your help.

Upgrading Hyperion 11.1.2.2 to 11.1.2.3

Hi All,
we are using Hyperion 11.1.2.2(64 bit), ODI 11.1.1.6 with SQL Server 2008 R2.
Now we are planning to apply maintainence release to upgrade 11.1.2.2 to 11.1.2.3 version.
(we are going to use ERP Integrator in 11.1.2.3 version)
But, in this process i have some clarity regarding below:
We have ODI 11.1.1.6 version now with Hyperion 11.1.2.2.
If we upgrade 11.1.2.3 version, EPM will install ODI also(if we select FDMEE). which version we will get? Can we use ODI 11.1.1.6 with new 11.1.2.3 version?
Thanks,
mady

I think you can upgrade ODI 11.1.1.6 to ODI 11.1.1.7 using Patch Set Assistant(psa.bat) which comes with ODI.
Have a read of this: Oracle&reg; Fusion Middleware Patching Guide 11g Release 1 (11.1.1.5.0) - Contents
You can have fresh repositories for ODI 11.1.1.7 along with FDMEE (fresh environment of EPM 11.1.2.3)& later should be able to import-export the Projects, Models, Topology, etc. or simply import-export the Master & Work repositories from the ODI upgraded to 11.1.1.7 above.
Regards,
Santy.

ODI 11g Client

Hi All,
How can i install Oracle Data Integrator 11g 32 bit client? Please can you refer me any links or PDF's?
Thanks,
Jun
Edited by: 925687 on Jun 19, 2012 11:54 PM
Edited by: 925687 on Jun 19, 2012 11:55 PM

Hi,
Even we are having the same issue. After the ODI upgrade we are not able to test the agent or run any interface/scenario using the agent and it is hanging the whole application. I tried to look at the SR # 3-3543895337 but I guess, I dont have access to the SR.
Can you provide the resolution steps, so that we can work on it.
Thanks in advance,
Mallesh

ODI Procedures not working after upgrading from 10G to 11G

Hello Gurus,
We have run into a scenario where the procedures in ODI are not working after we upgraded it from 10G to 11G (11.1.1.6). However we can make it to run if we create the procedure from scratch.
Also we are having issues related to packages where in the packages were running before we applied the patch 11.1.1.6.3. And after applying the patches they are not running.
Any help will be appreciated.
Thanks

If you want someone to help you, please be elaborate in the exact errors you are getting.
A general statement would do nothing but guess work.
What is the error that you get while executing the procedure.
What are the exact issues that you get while executing packages ?

Issue while upgrading ODI 10g to 11g

Hello Gurus,
I am upgrading repositories of ODI 10.1.3.5 to ODI 11.1.1.6 using Upgrade Assistant utility.
We have cloned/replicated the database repositories for ODI Master & Work.
After giving all details it checks for schema version registry, ODI version & succeeds.
but when I see the Target database details, the information like schema name, connection string about Work Repository is pointing to Production i.e. ODI 10.1.3.5 actual repository.
whereas it should show target details for replicated database.
What could be done to make it point to replicated?
Please help.
Thanks,
Santy.

Hi Santy
Change the work repository credentials, see post below;
https://blogs.oracle.com/dataintegration/entry/odi_11g_changing_the_work
Cheers
David

Need to connect to upgraded Oracle EBS R12 version from R11. The current ODI set up is pointing to R11, Can i use the same connection to point to R12? Please hele experts..

Need to connect to upgraded Oracle EBS R12 version from R11. The current ODI set up is pointing to R11, Can i use the same connection to point to R12? Please hele experts...
Rp

1. in physical connections part can i use the same work schema
2. Can i use same contexts created or do i need to create everything as new and then try?
Thanks,
Rp.
Hi,
As you mentioned that you just upgraded the database, so the data is same and schema is same you can connect with the same work schema.
Yes, you can use the same contexts , but need to do Reverse Engineering for your new database.
And about data server, i think you also have no need to create new data server, if hostname,sid and port etc are same as these were with R11(consult with your DBAs regarding it)

ODI Upgradation

Similar Messages

Maybe you are looking for