ODI Client to Repository Compatibility

Hi All, I've downloaded the ODI compatibility spreadsheet from Oracle but it does not answer my oddball question...
Can you safely use the ODI Studio 11.1.1.5 against an ODI 11.1.1.6 Repository?
I've upgraded the main server and repository, but all development work in my clients site must be done on VM clients with the ODI studio on.
All developers have an allocated client machine.
Mine does not currently have sufficient disk space to upgrade ODI Studio (it's that bad).
So, for the interim, until I get some more disk allocated, am I safe to run the ODI 11.1.1.5 studio against the 11.1.1.6 repository.
Come on someone, illuminate me, and I'll get the beers in next time I'm down your way.
Cheers
Jon

Please get me the beer 1st.
I am using 11.1.1.6 repository with 11.1.1.5 odi studio. So answer is a big YES for you.
Bhabani
http://dwteam.in

Similar Messages

  • How to improve odi client performance

    We use ODI 10.1.3.6.2.
    Whenever we use the client on a local machine, the performance is very slow.
    But when we connect directly to the server(remote into it) and use ODI there, it is very fast.
    Are there any ways to improve odi client's operating speed?

    ODI 10g has a lot of repository communication that causes things to slow down on a network.
    So, if you have ODI client on a network different than the remote machine, then you are out of luck.
    You can try following instructions in this blog:
    http://www.business-intelligence-quotient.com/?p=1205
    Even though the examples point out to ODI 11g, this holds true for 10g as well.
    Else, another option is to upgrade to ODI 11.1.1.5.0. This has improved in terms of repository communication(repository chattiness is reduced).

  • ODI-10150: Work repository with ID 7 is not bound to master

    Hi all,
    I am upgrading from 10g to 111.1.1.6 and getting the below error, can any say how to bound this work repository to the master repository.
    [2012-10-01T11:44:14.626-05:00] [eclipse] [NOTIFICATION] [org.eclipse.persistence.default] master-session logout successful
    [2012-10-01T11:44:14.897-05:00] [ODI] [INCIDENT_ERROR] [upgrade.ODI] [[--------- ODIPlugin.doUpgrade called]]
    [2012-10-01T11:44:14.897-05:00] [ODI] [INCIDENT_ERROR] [upgrade.ODI] [[
    oracle.odi.core.config.RepositoriesNotBoundException: ODI-10150: Work repository with ID 7 is not bound to master:
         Definition in master ID:800, Name:ODI_WORK_DEV, Timestamp:1321921754567
         Definition in work ID:1, Name:ODI_WORK, Timestamp:1181331962726.
         at oracle.odi.core.repository.support.RepositoryUtils.assertRepositoryBinding(RepositoryUtils.java:430)
         at oracle.odi.core.repository.Repository.getWorkRepository(Repository.java:228)
         at oracle.odi.core.OdiInstance.createWorkRepository(OdiInstance.java:504)
         at oracle.odi.core.OdiInstance.<init>(OdiInstance.java:581)
         at oracle.odi.core.OdiInstance.createInstance(OdiInstance.java:521)
         at oracle.ias.mrua.plugin.odi.ODIPlugin.doUpgrade(ODIPlugin.java:611)
         at oracle.ias.mrua.MRUA.executePlugins(MRUA.java:3576)
         at oracle.ias.mrua.MRUA.internal_driver(MRUA.java:2357)
         at oracle.ias.mrua.MRUA.driver(MRUA.java:1621)
         at oracle.ias.upgrade.gui.UAUpgradeThread.run(UAUpgradeThread.java:390)
    [2012-10-01T11:44:14.902-05:00] [ODI] [NOTIFICATION] [upgrade.ODI] --------- ODIPlugin.doUpgrade finished[[]]

    Hi,
    It should not really create any problem , if you create a two work repositories with differenct IDs. But, the error messae you gave suggests , it is something to do with repository IDs. Usually, we get this message , when we try to migrate ODI code within enviroments. However, it does not throw as an error message, it just gives as an information and asks us if we want to register the new work repository ID. We just need to say Yes and continue.
    I would suggest to redo everything, recreate repositories again. May be something went wrong while creating repositories.
    Regards,
    k

  • ODI-10150: Work repository with ID 1 is not bound to master

    Hello,
    ODI 11g (11.1.1) with database 11g r2
    I have created Master repository (odimrep) and
    work repository(odiwrep), created from Topology
    Before the next step, during this time I was able to login to connect to work repository and able to do all work
    Then I went on to created Execution repository (odierep) from topology, created successfully.
    After that I could not able to connect to work repository, as I am getting the following error message
    oracle.odi.core.config.RepositoriesNotBoundException: ODI-10150: Work repository with ID 1 is not bound to master:
         Definition in master ID:1, Name:ODIWREP, Timestamp:1337006142714
         Definition in work  ID:2, Name:ODIEREP, Timestamp:1337006565503.
    .....Could you please let me know what I am doing wrong to configure the Execution repository, do I need to drop everything and start re-create
    Any help would be greatly appreciated.
    Thanks,

    Hi,
    It should not really create any problem , if you create a two work repositories with differenct IDs. But, the error messae you gave suggests , it is something to do with repository IDs. Usually, we get this message , when we try to migrate ODI code within enviroments. However, it does not throw as an error message, it just gives as an information and asks us if we want to register the new work repository ID. We just need to say Yes and continue.
    I would suggest to redo everything, recreate repositories again. May be something went wrong while creating repositories.
    Regards,
    k

  • ODI agent and Repository

    Hi,
    I would like to know what is exactly role of ODI agent and repository?
    If i am creating a new ODI environment using OLD one having slight chages at Target Database can i use same Agent for both th repositories?
    Thanks,
    Mahesh

    how would i create data servers and how can i use it?
    In ODI terms data server is the connection to one or many data store present under a connection.
    You need to create data server from Topology .
    You need to create a physical data server where you need to provide the physical connection info .
    You need to have a logical data serrver created which will connect to the physical dataserver via a given context .

  • ODI Client cannot connect the datebase after the datebase IP changed

    ODI Client cannot connect the datebase after the datebase IP changed.
    1,the datebase on mac A,the mac changed ip
    2,on the client, tnsping db is ok.
    3,use pl/sql ,can connect on the db
    4,with odi,changed the repostry URL to the new db IP,throw the exception below
    java.sql.SQLException: Io Exception: The Network Adapter could not establish the connection
         at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:125)
         at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:162)
         at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:274)
         at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:328)
         at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:361)
         at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:151)
         at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:32)
         at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:595)
         at com.sunopsis.sql.SnpsConnection.u(SnpsConnection.java)
         at com.sunopsis.sql.SnpsConnection.c(SnpsConnection.java)
         at com.sunopsis.sql.h.run(h.java)
    Is anything we need to config after change db machine IP?

    yeah,I got it.Everything is ok now.
    After change IP,we must open TopologyManager:change the JDBC connection of workrepository which must chose in Designer.
    when we open the Designer ,it will connect to db.then coonect to workrepository with original IP.So,we must rechange workrepository's JDBC first!

  • Need info regarding ODI Client tools

    Out of Designer,Agent,Topology Manager,Security Manager
    what all are required by a developer?
    Is it posssible to put one or more of these centrally?
    why / why not have the client installed centrally and have everyone access it (like jdeveloper)?

    Hi,
    No you dont need OC4J as long as you are not using Web Services, Metadata Navigator, Lightweight Designer (Web component of ODI).
    Before Agent Installation 3 facts have to be clear,
    The GUI system : The machine where your ODI GUI is installed on
    The Agent system : The machine where your Agent is going to run
    The Repository system : The machine where your ODI Repository resides
    Note that all these three components can actually reside on a single machine; likewise, they can be three separate machines or any other combination.
    The Agent uses an internal, proprietary protocol based on TCP/IP..
    So you can have Agent running in client and access different IP with full access permissions. It can be installed on Server also and accessed by clients.
    But its recommended to install agent in Target warehouse for better performance and accessibility.
    Thanks,
    G

  • ODI Client Type

    We are looking at Oracle Data Integator for our data integration solution and had a question regarding the client UI. Could someone provide some information on the type of client such as thin client, Java applet, windows thick client, etc.
    Also, what about access through a firewall. If using a browser based thin client or applet then the traffic would flow through a proxy. Would a thick client need special firewall configuration. All users are expected to be internal.

    The main ODI development client is a fat Java-based client, which stores all it's data in the repository. The repository is in a database, shared by the developers. There is also a web-browser based interface to the repository, the Metadata Navigator, but this is primarily a read-only/browse interface. The application for this is a servlet-based application in a J2EE appserver.
    The repository database should be LAN rather than WAN- accessible.
    The execution-time process, the agent, is also Java-based. It reads the definition of tasks from the repository, and logs all actions and results to the repository.
    Communication with the agent is via a java network protocol.

  • 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

  • Configuration Manager Client Agent Backwards Compatibility - Remote Control

    Hello all,
    I'm not seeing this anywhere so I'll ask it here.  Once I complete the R2 upgrade from SP1 and the clients begin to upgrade using the Automatic Client Upgrade option there will be a number of clients upgraded to R2 and a number still at SP1.  Do
    the client agent components on those that are still at SP1 continue to function?  In particular I'm wondering about Remote Control.  My thought is the answer is yes.  Is there backwards compatibility until all client agents are upgraded?
    Thanks!

    Yes, there is.
    Torsten Meringer | http://www.mssccmfaq.de

  • Two clients, one repository

    Morning, all,
    We're running iFS 1.1.6 on an 8.1.7 database on an NT 4.0 SP 6 server. We're just trialling 9iAS. In the Standard and Enterprise Editions of 9iAS an iFS client is installed. Looks like it's possible to configure the 9iAS iFS client to the remote repository - the question we have is if it's possible to restrict the view of the repository to predetermined folder structures for the remote client? At present the 9iAS client has to be started with administrative priviledges and this allows "God" mode to the repository. We'd like to be able to run a remote iFS client for 9iAS, but with restricted views of the repository (for example, read only on a nominated public mount point).
    Thanks for your time,
    Regards
    Geoff.

    geoff
    The Protocol servers have to establish administrator enabled sessions in order to register with ServerManager etc. User with Admin privlidges running in privlidged mode are not restricted on ACL. Consequently they can always see the entire contents of the repository
    However, given the above, I'm still not sure that I quite understand what your concerns are here ...
    Any user connecting to the protocol server will be required to authenticate against the iFS repository. Although each protocol server has threads running in admin mode the users will always be serviced by threads that run with the permissions appropriate to the user. Thus any user connected to the protocol server, regardless of whether the protocol server is visable to the internet will only be able to see the documents they are entitled to see.
    Note that in general the Protcols Servers assume that when a user with admin capability connects to the ifs they will want to run in Admin mode.
    If you have further clarification of the percvied problem please let me know. An example would be much appreciated.

  • NX Client and Leopard compatibility

    Anybody else use NX ("No Machine") client? It's much like VNC, a desktop sharing program (but it is much faster) that uses X11.
    Well, after upgrade to Leopard, it doesn't work very well. Lots of redraw problems for me (on an iMac G5), one Intel MacBook user reports jumbled characters.
    Any insight would be appreciated.
    Bark!

    An update: macoshints.com has a thread on this:
    http://forums.macosxhints.com/showthread.php?t=80129
    One user said:
    Yes, Apple knows about all these problems with Leopard X11 (please read the FAQs at the top of the page), and they are working hard to fix the bugs.
    In separate news, someone reported that reverting to the 10.4 version of X11 solved the problem.
    So....I guess I wait.
    Bark!

  • ODI 11g - Work Repository Creation via Script

    Hi!
    Do you have any suggestions how to create work repositories via script?
    My idea is to create all database objects in the schema for the new work repository and insert the repository specific information into the tables
    - SNP_REM_REP (master repository)
    - SNP_CONNECT (master reppository)
    - SNP_LOC_REPW (work repository)
    Am i missing something?
    Thanks in advance & kind regards
    Michael

    Why do you want to do it this way ?
    I dont think your idea is going to work as there are 87 other tables (maybe not all of them) in Work Rep that need to be populated. And only the Work repository creation menu in the Topology would do it for you. There are relationship among those tables that need to be satisfied.
    What version are you on ? In 11g you can write Java code to do the things I mentioned above. Whatever you can click and do in 10g can be done using Java programming in 11g.

  • ODI Import Work Repository Issue

    Hi All,
    AS part of implementation of OBI Apps 7.9.5.2. I was trying to import the Oracle BI Applications Work Repository but when i was following the process of importing using the ZIP file. I was getting error.
    The error details were
    Oracle Data Integrator Error -----> java.lang.OutOfMemoryError
    Can Any one help me resolve this error ?
    Thanks and Regards,
    Krishna Prasad.

    Hi All,
    i got the issue. Need to increase the java heap memory size in the parameter file.... which resolves this issue

  • RWD uPerform 4.10 client & Windows 7 compatibility

    Hi
    Is RWD uPerform 4.10 client supported on Windows 7 32 bits?
    I didn't have install issues on Windows 7

    Hello
    It can work, but it's not supported by the version "technical papers". If you want to be sure, its better to migrate to latest version like 4.3 or 4.4
    Greeting
    Gustavo

Maybe you are looking for