9.0.2 - 9.0.3 repository upgrade

I recently upgraded from OWB 9.0.2 to 9.0.3.0.1. After the upgrade, I tried to use the Repository Assistant to upgrade my old repository but got the following error message:
"This repository cannot be upgraded to add more languages to support object translations. You must have a version 9.0.3.0.1 repository to upgrade."
It seems like the upgrade handles the addition of languages to support object translations rather than from one OWB version to another. My questions:
i) Is there any way to upgrade a 9.0.2 repository to 9.0.3 (I've already uninstalled 9.0.2...)
ii) When I tried to workaround by creating a new repository owned by a new user, the packages WBPRTI,WBPRTIP,WBPRTIQ and WBPRTIU are still owned by the old owner. This prevents me from deploying as the new user. Should I change the owner of these packages on the Oracle server? Who should own these packages when there are several repositories owned by different users on a database?
thanks,
Ulf

I had the same problem. After many frustrating hours, in my case it appeared to be some old QuickTime files on my PC that were causing the issue.
Did the following:
If ITunes 9.0.2 hangs while trying to download or constantly getting errors that QuickTime needs to be updated, try the following:
1. Uninstall QuickTime via Control Panel (Add or Remove Programs)
2. After this is complete go to the following website and remove all files accordingly:http://www.codecguide.com/quicktime_removal.htm.
Details below:
2a. Go to the folder c:\windows\system32 and delete the files QuickTime.qts and QuicktimeVR.qtx
2b. Go to the folder c:\windows and delete the files QTFont.for and QTFont.qfn
2c. Delete the folder c:\program files\quicktime
3. While in c:\windows\system32, also remove any other QuickTime files (I had a QuickTimeMusicInstrument file from 2001) and make sure there is no QuickTime folder now
4. If downloading new version of ITunes: Uninstall ITunes v8 or earlier.
5. Download ITunes 9 + QuickTime. I was successfully able to install both at this point.

Similar Messages

  • Repository upgrade fails 11.1.0.7 db -10.2.0.5 GC patchset

    Installing GridControl 10.2.0.5 on Windows 2003 Server SP2. Initial install successful of 10.2.0.2 using existing database 11.1.0.7. The database was created new to use for GC. Patchset no problems until Configuration Assitant step "Repository Upgrade" failed with errors:
    rem Copyright (c) 1999, 2009, Oracle. All rights reserved.
    oracle.sysman.emcp.oms.RepositoryPatchUpgrade -verbose
    oracle.sysman.emcp.oms.OmsPatchUpgrade -configureOms
    oracle.sysman.emcp.aggregates.ConfigPlugIn
    oracle.sysman.emcp.oms.StartOMS -configureOms
    oracle.sysman.emcp.oms.EMCLISetup
    oracle.sysman.ccr.configCCR.ConfigCCRPlugIn
    oracle.sysman.ccr.configCCR.ConfigRepeaterPlugIn
    Tried to find cause of errors and cannot seem to understand why this step failed.
    Considering uninstalling GC and Oracle 11g and reinstalling GC with "new database" option.
    Anyone successful at installing GC 10.2.0.5 with an 11g database?
    Thank you,
    Curt Swartzlander
    DBA

    pasinc wrote:
    Can anyone help me figure out why the domU is just hanging/blocked?It's not hanging (blocked just means it doesn't need the CPU) -- it's just switched into a graphic mode that the console view can't display. You can either VNC into the guest, or change the kernel boot parameters by removing rhgb quiet and replacing them with console=xvc0 -- this should allow you to see the full boot process and answer the first-boot interview questions without using VNC.
    You can get the VNC details by running: virsh dumpxml <domain ID> and you can get the domain ID from the xm list output.

  • 9.0.2.6 Portal Repository Upgrade Patch problems.

    We got some problem with Portal when tryed to apply
    9.0.2.6 Upgrade. Could anybody give advice on this issue:
    Initial configuration:
    Solaris8, Portal 9.0.2.2.14, Oracle 9iAS R2 v.9.0.2.0, RDBMS 9.0.1.3. The infrastructure and midtier work on different SPARC-servers.
    Accordingly upgrade procedure we succesfully applied:
    a) Infrastructure: 9.0.1.4 Patchset for Oracle RDBMS server, 9.0.2.2 Patchset for OID, Oracle 9iAS SSO-server
    migration to 9.0.2.5, 9.0.2.2 Patchset for 9iAS Core.
    b) 9.0.1.4 Patchset for Oracle RDBMS server, 9.0.2.2 Patchset for OID, Oracle 9iAS SSO-server migration to 9.0.2.5, 9.0.2.2 Patchset for 9iAS Core, Portal 9.0.2.6
    patch.
    After this we needed to make just one last step:
    Portal 9.0.2.6 Repository Upgrade Patch (2981297) for
    changing Portal's repository schemes. It worked but
    like a result we got the next errors after patch upgrade
    was done:
    a) "The following invalid non-Portal objects exist in the Portal Schema: INDEX ABC (the name of portal object), PACKAGE BODY WWMON_REP_REPOSITORY, PACKAGE BODY WWMON_REP_REPOSIT_DTL, PLS-00103: Encountered the symbol "," when expecting one of the following: (-+case mod not null <an identifier>,...) The symbol "null" was substituted for "," to continue.)" See upgtmp/nonportal.log
    b) "ERROR: 1 invalid objects remain; ERROR: Failed while updating the new portlet IDS..."
    c) "ERROR: ORA-01407: cannot update ("PORTAL"."WWSBR_URL$"."URL") to NULL.
    d) Two package body of packages at PORTAL scheme became invalid: WWMON_REP_REPOSITORY, WWMON_REP_REPOSIT_DTL. About 20 package body of packages at PORTAL_DEMO became invalid (It seems like initial portlet ID's disappeared
    and except of pportlet_id there is nothing:
    Example:
    inital statement at body:
    xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
    PORTAL.wwpro_api_invalidation.invalidate_cache(
    p_provider_id => p_provider_id,
    p_portletid => 1065753336,
    p_instance_id => p_reference_path,
    p_subscriber_id => PORTAL.wwctx_api.get_subscriber_id ,
    p_user => PORTAL.wwctx_api.get_user);
    xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
    after upgrade repository patch:
    xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
    PORTAL.wwpro_api_invalidation.invalidate_cache(
    p_provider_id => p_provider_id,
    p_portletid => ,
    p_instance_id => p_reference_path,
    p_subscriber_id => PORTAL.wwctx_api.get_subscriber_id ,
    p_user => PORTAL.wwctx_api.get_user);
    xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
    Like a result after 9.0.2.6 Portal Repository Upgrade Patch application we lost the possibility to edit user's
    profiles at Portal and other nesessary features. It seems
    like some portlet ID's just dissapeared from Portal scheme. Could anybody had the same problem with Portal Upgrade 9.0.2.6? Quite possible that we missed some important element at during upgrade but ,really, we didn't wait so unlucky result. Advice something, please...
    Regards. Igor.

    Igor,
    Since you've encountered undocumented errors, your repository upgrade has failed. You'll want to leave the repository as is for troublshooting, if at all possible, and log a TAR with support if you haven't already. They'll ask you to upload your upgrade log file and your upgrade tmp directory.
    Regards

  • Portal repository upgrade problems

    I upgraded a ORACLE 8.1.6.3.0 database to 8.1.7.2.0 and JVM but 9 classes remained invalid, removing and reinstalling jvm I lost all Portal30 JAVA stuffs. Who has found a clue to make it correct.

    Igor,
    Since you've encountered undocumented errors, your repository upgrade has failed. You'll want to leave the repository as is for troublshooting, if at all possible, and log a TAR with support if you haven't already. They'll ask you to upload your upgrade log file and your upgrade tmp directory.
    Regards

  • Errors running MRUA for Metadata Repository Upgrade to version 10.1.2.0.2

    Hi,
    I am encountering the following errors trying to run the MRUA for our Metadata Repository Upgrade on an AIX 5.3 box:
    <mrua_runs> ../mrua/mrua.sh -oracle_home /u01/oracle/product/9.2.0.8 -oid_host ourhost.domain.com -oid_ssl_port 3130
    Executing mrua.pl
    Running on UNIX
    OracleAS Metadata Repository Upgrade Assistant 10.1.4.0.1
    Enter the password for SYS: <syspw>
    Enter the password for cn=orcladmin: <pwd>
    Exception in thread "main" java.lang.NoClassDefFoundError: oracle/sysman/oii/oiio/oiiol/OiiolTextLogger
    at oracle.ias.repqueries.RepositoryQueries.formatGlobalDBName(RepositoryQueries.java:603)
    at oracle.ias.mrua.RepQueries.getDBInfo(RepQueries.java:180)
    at oracle.ias.mrua.Util.getTheDBInfo(Util.java:50)
    at oracle.ias.mrua.MRUA.getInfoFromOID(MRUA.java:690)
    at oracle.ias.mrua.MRUA.driver(MRUA.java:297)
    at oracle.ias.mrua.MRUA.main(MRUA.java:193)
    MRUA detected an error at /mnt/MRUA/mrua/mrua.pl line 237.
    <mrua_runs>
    Before running the MRUA for the Metadata Repository:
    1. I have just recently completed a Middle Tier and Identity Mangement upgrade to 10.1.2.0.2 from version 9.0.4.1.
    2. I was able to successfully run the MRUA upgrade script for upgrading our Portal Repository (customer database).
    Our Metadata Repository database is at version 9.2.0.8. Has anyone seen these errors or had this problem?
    The MRUA CD that I have is labelled "Oracle Metadata Repository Upgrade Assistant and Utilities 10g (10.1.2.0.2) for AIX based systems".
    But in the errors I see "OracleAS Metadata Repository Upgrade Assistant 10.1.4.0.1". Is something wrong there? Should it say 10.1.2.0.2?
    Any help would be greatly appreciated.
    Thanks.
    CV
    Hi,
    I have downloaded the 10.1.2.0.2 version of the MRUA and tried the upgrade again. This time I see the following errors:
    Executing mrua.pl
    Running on UNIX
    OracleAS Metadata Repository Upgrade Assistant 10.1.2.0.2
    Enter the password for SYS: <syspwd>
    Enter the password for cn=orcladmin: <pwd>
    Exception in thread "main" java.lang.NoClassDefFoundError: oracle/sysman/oii/oiio/oiiol/OiiolTextLogger
    at oracle.ias.repqueries.RepositoryQueries.formatGlobalDBName(RepositoryQueries.java:603)
    at oracle.ias.mrua.RepQueries.getDBInfo(RepQueries.java:180)
    at oracle.ias.mrua.Util.getTheDBInfo(Util.java:50)
    at oracle.ias.mrua.MRUA.getInfoFromOID(MRUA.java:784)
    at oracle.ias.mrua.MRUA.driver(MRUA.java:290)
    at oracle.ias.mrua.MRUA.main(MRUA.java:186)
    MRUA detected an error at /mnt/MRUA_downloaded/ohome/mrua/mrua.pl line 239.
    Thanks.
    CV
    Edited by: CV on Jul 28, 2009 1:37 PM

    Hi,
    Found out from Oracle that the "oracle/sysman/oii/oiio/oiiol/OiiolTextLogger" class is in the $ORACLE_HOME/oui/jlib/OraInstaller.jar file and as per their suggestion added the jar file to the $classpath list of jar files in the mrua.pl script. I tried running the MRUA again, and ran into the following errors:
    Exception in thread "main" java.lang.NullPointerException
    at oracle.ias.mrua.MRUA.formatHostPortSid(MRUA.java:1449)
    at oracle.ias.mrua.MRUA.getInfoFromOID(MRUA.java:794)
    at oracle.ias.mrua.MRUA.driver(MRUA.java:290)
    at oracle.ias.mrua.MRUA.main(MRUA.java:186)
    MRUA detected an error at /u01/oracle/mrua_runs/MRUA_downloaded/ohome/mrua/mrua.pl line 243.
    I am still troubleshooting. So if you have any ideas please let me know.
    Thanks.
    CV

  • 9.0.2 to 9.0.2.6 Upgrade - Repository Upgrade

    Hi,
    I am unable to do the Repository Upgrade for the 9026 Portal Upgrade. I have successfully done all the pre-requisite patchset upgrades as well as the actual 9026 Portal upgrade. But when I run the upgrade.pl, I get an error. Here are the steps:
    Enter Schema Name: portal
    Enter Schema Pwd: portal
    Enter SYS Pwd: change_on_install
    Enter TNS String: iasdb
    ### ERROR: Connection to Portal repository failed.
    ### DBI->Connect(iasdb) failed: ORA-01017: invalid username/password; log on denied (DBD ERROR: OCISessionBegin) at /u02/app/oracle/product/IAS20MT/portal/admin/plsql/utils/perl/sqlutils.pm line 197
    ### Upgrade aborted
    I granted SYSDBA to SYS schema and tried. That did not work either.
    Any suggestions?
    Thanks in advance...
    -- Shravan

    Shravan
    Are you sure the PORTAL schema password is portal. By default on a 902 install it is a scrambled sequence of letters that you can figure out by looking up the entry in OID. This value is different from the Portal user as stored in OID. Check out the password by logging onto the account with sqlplus. Don't change the password from the sys account if you find out that it is not portal. Look it up in OID and use that value. I would check the sys password by the same technique to be absolutely sure it is correct.
    Check the upgrade first by running
    perl upgrade.pl -precheck
    If you are sure that both of your passwords are correct then I would get in touch with support and log a TAR for addition assistance.
    Regards

  • R3 - Repository Upgrade failed

    Hi,
    AIX5, EM10gR2 upgrade to R3.
    (Fresh installation of R2, applied patch 4329444, proceed with R3 upgrade)
    At the Configuration Assistants screen:
    "Repository Upgrade failed"
    $ cat configToolFailedCommands
    # Copyright (c) 1999, 2007, Oracle. All rights reserved.
    oracle.sysman.emcp.oms.RepositoryPatchUpgrade -verbose
    oracle.sysman.emcp.oms.OmsPatchUpgrade -configureOms
    oracle.sysman.emcp.aggregates.ConfigPlugIn
    oracle.sysman.emcp.oms.StartOMS -configureOms
    oracle.sysman.ccr.configCCR.ConfigCCRPlugIn
    Not sure what to do.
    Any hints how to proceed?
    Thx,
    Dobby

    Same problem but on RHEL4 when trying to upgrade to 10.2.0.3. Fresh install with database already 10.2.0.3 and OMS was installed with option "existing DB".
    Database and listener were left running but all other processes were shutdown with opmnctl stopall.
    Any ideas?
    This is the end of $OMS_HOME/sysman/log/emoms.trc:
    2007-10-04 10:23:14,204 [Job Dispatcher Thread] WARN jdbc.ConnectionCache _getConnection.353 - Got a fatal exeption when getting a connection; Error code = 17002; Cleaning up cache and retrying
    2007-10-04 10:23:14,220 [Job Dispatcher Thread] ERROR em.jobs preTask.2292 - Cannot get id: Io exception: The Network Adapter could not establish the connection
    2007-10-04 10:23:18,248 [NotificationMgrThread] WARN jdbc.ConnectionCache _getConnection.352 - Io exception: The Network Adapter could not establish the connection
    java.sql.SQLException: Io exception: The Network Adapter could not establish the connection
    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:137)
    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:174)
    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:286)
    at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:327)
    at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:433)
    at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:150)
    at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:31)
    at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:571)
    at oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:217)
    at oracle.jdbc.pool.OracleConnectionPoolDataSource.getPhysicalConnection(OracleConnectionPoolDataSource.java:108)
    at oracle.jdbc.pool.OracleConnectionPoolDataSource.getPooledConnection(OracleConnectionPoolDataSource.java:76)
    at oracle.jdbc.pool.OracleImplicitConnectionCache.makeCacheConnection(OracleImplicitConnectionCache.java:1344)
    at oracle.jdbc.pool.OracleImplicitConnectionCache.getCacheConnection(OracleImplicitConnectionCache.java:435)
    at oracle.jdbc.pool.OracleImplicitConnectionCache.getConnection(OracleImplicitConnectionCache.java:330)
    at oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:285)
    at oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:253)
    at oracle.sysman.util.jdbc.ConnectionCache._getConnection(ConnectionCache.java:336)
    at oracle.sysman.util.jdbc.ConnectionCache._getConnection(ConnectionCache.java:322)
    at oracle.sysman.util.jdbc.ConnectionCache.getUnwrappedConnection(ConnectionCache.java:575)
    at oracle.sysman.emSDK.svc.conn.FGAConnectionCache.getFGAConnection(FGAConnectionCache.java:207)
    at oracle.sysman.emSDK.svc.conn.ConnectionService.getSystemConnection(ConnectionService.java:1304)
    at oracle.sysman.emdrep.notification.NotificationMgr.getConnection(NotificationMgr.java:403)
    at oracle.sysman.emdrep.notification.NotificationMgr.run(NotificationMgr.java:1453)
    2007-10-04 10:23:18,251 [NotificationMgrThread] WARN jdbc.ConnectionCache _getConnection.353 - Got a fatal exeption when getting a connection; Error code = 17002; Cleaning up cache and retrying                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • DAC 10.1.3.4.1 First Time Login Repository Upgrade Failure

    Hi all,
    We are upgrading from DAC shipped with Siebel Analytics Applications 7.8.4 to DAC 10.1.3.4.1, platform and repository. This is combined with OBIEE upgrade from Analytics 7.8.5.2 to OBIEE 11g (11.1.1.5.0) and OBIA upgrade from Analytics Applications 7.8.4 to OBIA 7.9.6.3. Additionally, the database was upgraded from Oracle 10.2.0.2 to 11.2.0.2.
    We've just installed DAC 10.1.3.4.1 on a Windows 2008 (32bit) Server and this completed without issue. When logging in to the DAC Client and making a connection to the existing DAC Repository, after 'Yes' when prompted to upgrade the existing repository, we get a message saying, ["Upgrade didn't complete! Please check log file "log/upgrade.txt" for details."] Upon checking the log file, it states the following:
    ###start of message###
    =======================================
    Upgrade from DAC 1.0 to Dactopus format
    =======================================
    reading upgrade stage...
    nothing found - starting upgrade
    No upgrade from DAC 1.0 to Dactopus is currently available.
    If you want to have a Dactopus repository at the current connection,
    you should first drop existing one using 7.8.2.4 DAC build.
    upgrade failed
    ###end of message###
    Please, can someone shed some light on the situation?
    Many thanks.
    PS. We were able to create a new Oracle user, create a new DAC Repository on this new schema and import the OBIA 7.9.6.3 DAC Repository without apparent issue.

    Hello all,
    I have a conclusion to this question.
    Whilst Oracle Support did not explain the error message per se, they did state that one cannot upgrade a DAC 7.8.4 Repository via the First Time Login prompt, but rather to use the Upgrade/Merge Wizard, option 'Repository Upgrade (DAC 784)'. if the customisations are substantial. If the customisations are simple, they can be done manually - see upgrade guides.
    Whilst this is indeed stated in the upgrade documentation, I had been confused by other statements in the documents which appeared to be contradictory and ultimately lead me down the wrong upgrade path.
    Just do add, the documentation recommends using the Upgrade/Merge Wizard 'Repository Upgrade (DAC 784)' option if the customisations are substantial and unknown. If the customisations are simple and known, they can be done manually - see upgrade guides.
    Thanks.

  • 10.2.0.1.1 upgrade to 10.2.0.2 failed in Repository Upgrade.

    RHEL4.8 x86
    10.2.0.1.1 upgrade to 10.2.0.2 failed in Repository Upgrade.
    Applying patch to OMS. Configuration Assistants failed in "Repository Upgrade".
    OracleHomes/oms10g/cfgtoollogs/configToolFailesCommands shows:
    oracle.sysman.emcp.oms.RepositoryPatchUpgrade -verbose
    oracle.sysman.emcp.oms.OmsPatchUpgrade -configureOms
    oracle.sysman.emcp.oms.ConfigPlugIn
    Any idea?

    Check at the log OMSHOME/sysman/log/*.err/

  • Repository upgrade from 8i to 10g database

    We are currently upgrading from the 9i developer suite to the 10g developer suite. The repository for the designer tool resides on an 8i database and I want to migrate to a 10g database. Does anyone have any suggestions on how to best do this?

    Bruce,
    You could take a Complete Export of the repository on the 8i Database and then import it back into an new Repository user on the 10g Database using the RAU.
    Please take care that proper Import/Export utilities are used to perform this action.
    Regards,
    Ritu

  • ODI 10g to 11g repository upgrade: problem while reusing schema

    Hi,
    I have successfully upgraded 10g repository to 11g using UA.  To incorporate some changes in the 10g repository, we need to drop the existing 11g repository and re-upgrade the original 10g repository.
    I have truncated  the upgraded 11g schemas(master and work repo) in the database and copied the 10g contents into the empty schemas.
    But while trying to upgrade the schemas using UA, the UA is showing that the ODI schema is already upgraded!!
    It seems the UA is looking into some log of previous upgrade.
    Is there any way to identify / modify the previous upgrade logs so that I can use the same schema details in UA and upgrade again.
    Regards,
    Saby

    Hi Saby,
      I think you can delete such records from SCHEMA_VERSION_REGISTRY table.
      You will find this table under SYSTEM account in your 11g database.
      Hope this helps.
    Thanks,
    Santy.

  • SUNOPSIS to ODI migration : AS/400 error in work repository upgrade

    Hi,
    We're migrating SUNOPSIS v3.2.02.19 to ODI 10.1.3.5.0, with repositories on DB2 AS/400.
    We achieve to migrate master repository without any problem, and we try now to migrate the work repository and we have the following error :
    +java.sql.SQLException: [SQL0404] La valeur destinée à la colonne ou la variable TABLE_NAME est trop longue.+
    at com.ibm.as400.access.JDError.throwSQLException(JDError.java:520)
    at com.ibm.as400.access.AS400JDBCStatement.commonExecute(AS400JDBCStatement.java:822)
    at com.ibm.as400.access.AS400JDBCPreparedStatement.executeUpdate(AS400JDBCPreparedStatement.java:1179)
    at com.sunopsis.sql.SnpsQuery.executeUpdate(SnpsQuery.java)
    at com.sunopsis.dwg.xml.DwgXmlSession.execute(DwgXmlSession.java)
    It seems that as column name, table name or variable name in migration process is too long, but i don't have any ideas of which. What can i solve this problem ? Any solution or workaround ?
    thanks for help !
    Edited by: julienpeltier on 19 oct. 2010 04:12
    Edited by: julienpeltier on 19 oct. 2010 04:13

    Check out the metalink document for upgrade
    Best Practices For Upgrading From Sunopsis To Oracle Data Integrator [ID 437223.1]
    Important things to be aware of if you are upgrading from Sunopsis V3:
    Sunopsis V3 uses JVM 1.3.1 while ODI 10.1.3 requires a minimum of JVM 1.4.2. This is not an issue if you are upgrading from Sunopsis v4.
    Sunopsis V3 allows mixed-case Context Codes, which are automatically converted to upper-case in V4 and ODI versions. To fix the Issue, manual updates of all Context Codes referenced in the Work Repository must be performed. These updates should be made on all Work Repositories related to a same Master Repository.
    In Sunopsis V3 DB2UDB Technology definition (\lib\scripts\xml\TECH_IBMDB2UDB.xml), The BLOB is defined with a size of 2G. The Master Repository creation fails at
    CREATE TABLE SNP_DATA ( I_DATA NUMERIC(10) NOT NULL, DATA_CONTENTS BLOB(2G)
    with error message :
    SQLCODE -355 SQLSTATE 42993 SQLERRMC: DATA_CONTENTS
    The error means that the column is too large for logging. 2G exceeds DB2 1G limit for Blob datatypes. This is fixed in Sunopsis 4.0.
    After upgrading Sunopsis v3 Master to ODI, the user will still run into this issue if he tries to export this upgraded Master and import it into another Master using mimport.bat.
    Solution: Modify the upgraded V3 Master Repository TECH_IBMDB2UDB.xml file and change the 2g to 100M. i.e.
    <Field name="DdlLongrawMask" type="java.lang.String"><![CDATA[BLOB(100M)]]></Field>
    Then try the import again.

  • Metadata Repository upgrade

    Is it possible to upgrade Metadata Repository running on 9.0.1.5.0 database to 9.2.0.4.0 without installing new 9.2.0.4.0 database and running Metadata Repository Creation Assistant?

    We have two different cases:
    1- DB created using normal default Application Server Installation:
    In this case, DB version can't be upgraded. When the infrasturcure will be upgraded, the DB will be upgraded automatically.
    2- It is a Customer DB, Metadata repository is created using MRCA:
    In this case, The DB is a normal DB and can be upgraded to any supported DB
    version.
    mmm.. some quick research on metalink shows even more steps with certain components. Please make sure you do a proper query on metalink before you start upgrading.
    Message was edited by:
    Jacco Landlust

  • Work/Master Repository upgrade error!! SOS!!

    We give production support for a project. We installed ODI and configured it to accept the existing Work and Master repositories. It worked as it should. But when we installed ODI in another m/c with the same connections and Work and Master repositories, it threw an error stating that Master Repository is not up to date and that we need to upgrade it. We upgraded both master and work repositories but the error still persists. We are unable to open any of the GUIs- Designer/Operator/Topology Manager.
    Help!!

    Hi,
    Try just copy the odi install directory from the place where is working to the new one.... (alll orahome_1) and launch Designer from it.
    Works for you?

  • Solaris 11.1 - 11.2 (SRU) local repository upgrade problem

    Hello,
    We have had several attempts at upgrading a previously working local IPS repository.  The repository started as an 11.1 repository, then was upgraded with SRUs to 11.1.13.  At this stage the repo server itself and all other machines were able to ‘pkg update’ successfully.
    However we now want to pick up 11.2.
    We tried two ways of doing this:
    Upgrade existing 11.1.13 repo to 11.2 release then upgrade again to 11.2.2.8.0 SRU.
    Start with a clean 11.2 release repo then apply 11.2.2.8.0 SRU.
    In both cases, the repo server and all other machines do not correctly ‘pkg update’, they abort early with the following message:
    http protocol error: code: 404 reason: Not Found               
    URL: 'http://repo-test/s11_2_sru/repo/solaris/manifest/0/install%[email protected]%2C5.11-0.175.2.0.0.42.2%3A20140624T184445Z' (happened 4 times)
    It looks like the catalog and filesystem contain the actual packages:
    pkgadm@repo-test:/repo/repo$ pkgrepo -s /repo/repo list archive
    PUBLISHER NAME                                          O VERSION
    solaris install/archive 0.5.11,5.11-0.175.2.0.0.42.2:20140624T184445Z
    pkgadm@repo-test:/repo/repo$ pkgrepo -s /repo/repo list entire
    PUBLISHER NAME                                          O VERSION
    solaris   entire 0.5.11,5.11-0.175.2.2.0.8.0:20140926T190209Z
    solaris   entire 0.5.11,5.11-0.175.2.0.0.42.0:20140624T193832Z
    However pkg.depotd doesn't seem to be able to extract the manifests on demand, despite multiple attempts at:
    pkgrepo rebuild
    pkgrepo refresh
    svcadm refresh pkg/server
    svcadm restart pkg/server
    svcadm refresh apache22
    svcadm restart apache22
    reboot
    and so on.
    Browsing the repo via the web does indicate *some* manifests are available, just not all of them.

    Hi Erik,
    Thanks for your update. We've now managed to resolved this. It turned out to be apache getting confused by the '/' in the path:
    [Fri Oct 17 14:32:53 2014] [info] [client 192.168.30.130] found %2f (encoded '/') in URI (decoded='/s11_2/solaris/manifest/0/install/[email protected],5.11-0.175.2.0.0.42.2:20140624T184445Z'), returning 404
    We've now resolved this by turning on the AllowEncodedSlashes option for apache:
    1. add "AllowEncodedSlashes On" at the end of /etc/apache2/2.2/httpd.conf
    2. sudo svcadm refresh svc:/network/http:apache22
    3. sudo svcadm restart svc:/network/http:apache22
    'pkg update' on client now works successfully.
    We have asked Oracle to augment their online instruction with this information.
    Thanks for trying to help.
    JW

Maybe you are looking for