Upgrading Repository to 11.1.1.6?

I set up a new install of OBIEE 11.1.1.6 (new box, everything) and wanted to move our 11.1.1.5 RPD and Catalog onto it. I do the repository deployment, update the GUIDs, set the new catalog, and do a refresh on the catalog and can log in and see my subject areas in Answers. Weird thing is this: some of my subject areas work fine and bring back data but others do not. It's as if the joins between the physical tables are not being see as correct.
Even when I paste the physical SQL code into my editor (Toad, etc) I get the same error message - that there is an invalid identifier on one of my IDs. The SQL is not identical between servers but nothing has changed. The column that is erroring is valid and this same exact RPD works on the 11.1.1.5 install of OBI.
Here's the whole error from nqquery.log:
[2012-03-14T15:04:54.000+00:00] [OracleBIServerComponent] [TRACE:2] [USER-34] [] [ecid: 5e76954936b44c3c:3552ebbe:1361322affe:-8000-0000000000001225] [tid: 740] [requestid: 704d0003] [sessionid: 704d0000] [username: weblogic] -------------------- Query Status: [nQSError: 17010] SQL statement preparation failed. [[
[nQSError: 17001] Oracle Error code: 904, message: ORA-00904: "T7886"."MYTABLE_ID": invalid identifier
at OCI call OCIStmtExecute.
[nQSError: 43119] Query Failed:
Has anyone else experienced this? Is there something different in the way this version handles joins or is executing the physical SQL? Do I need to re-do all my physical joins where I'm having these problems?

Hi Thejame,
As per my understanding, Invalid identifiers are due to a variety of reasons like invalid character in the column name like :, etc or even the column itself is not present. Also, when there are some extra keywords, I think they have to be enclosed in double quotes (I think BI does it by default too).
I suggest you to create a simple report using the problematic subject area and see if there are any unknown column names (or if your 11115 has fully qualified name checked in the connection pool)
Hope this helps.
Thank you,
Dhar

Similar Messages

  • How to upgrade repository database from 10.1.0.4 to 10.2.0.3?

    I installed EM10gR3 on Linux. I chose Install Grid Control using a New Database option. The database is 10.1.0.4. How can I upgrade repository database to 10.2.0.3? Shall I install Oracle 10.2.0.3 and then use dbua to upgrade?
    Thanks,
    Kevin

    Yes. But first of all check that the 10.2.0.3 Repository is compartible with 10.2.0.3 database. You will find this in the Installation Guide. Then use any upgrade type (DBUA, Upgrade Script etc) to upgrade the database.

  • Error upgrading repository to 11gR2

    Have a 10.2.0.4 repository and trying to upgrade to 11gR2.
    Ran the cat_owb.sql script, and unlocked the OWBSYS and OWBSYS_AUDIT acounts
    Ran the reset_owbcc_home.sql script
    Started the repository admin tool, selected "Upgrade Repository...", then "Export entire repository..."
    Entered credentials for the 10.2.0.4 repository owner
    Set the file information, and clicked Finish to start the export.
    At 21% complete, a SQL Exception is thrown. The log file reports:
    SQLException
    Persistent Layer Error: SQL Exception..
    Class Name: CMPPersist.
    Method Name: queryObjNameInfo.
    Persistent Layer Error Message: ORA-00904: "OWNINGPLATFORMTYPESET": invalid identifier
    SELECT elementid, classname, name, ..., iconObject, OwningPlatformTypeSet from CMPDatatype_V where elementid=?.Any ideas would be appreciated.

    Needed to apply patch 9201820

  • Disturbing message when upgrading repository

    I'm doing some testing of an upgrade from DI 11.5 to version 12.1 in preparation for our development environment upgrade. When upgrading a repository from version 11.5 to 12.1 I get the follow message at the end of the upgrade log:
    Adding 12.0.0 functions... (BODI-300001)
    Upgrading repository objects (BODI-300071)
    Adding Data Services new substitution configuration ... (BODI-300123)
    Adding Data Quality new substitution configuration... (BODI-300133)
    Adding Data Cleanse transform... (BODI-300125)
    Adding Country IDs transform... (BODI-300126)
    Adding Global Address Cleanse transform... (BODI-300127)
    Adding Global Suggestion List transform... (BODI-300128)
    Adding Match transform... (BODI-300129)
    Adding Associate transform... (BODI-300130)
    Adding USA Regulatory Address Cleanse transform... (BODI-300131)
    Adding User Defined transform... (BODI-300132)
    Fixing the UI_mapping_text... (BODI-300124)
    The local repository upgrade was cancelled. (BODI-300056)
    What is the meaning of this message? Does it indicate an error? Should I be concerned?
    Logging into the repository with Designer, everything behaves fine and I am able to run a simple job from the repository.

    Found this message, and this thread when upgrading 11.7.0.1 repositories to 12.2.1.0. Worryingly the above posts refer to DS 12.1 and service packs that you'd have thought would already be in 12.2.1.0!
    I was upgrading about 14 local repositories and 11 central repos and I struggled to find the common error as to why the fabulous "The central repository upgrade was cancelled. (BODI-300022)u201D message appeared. There seemed to be nothing wrong with the repositories and after the upgrade failed DS thought they were 12.2.
    Anyway, to cut a long story short, I solved it thus.
    *Close the SAPBO Data Services Repository Manager after each upgrade. Reopen for the next upgrade and it works.*
    hmmmm.

  • 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

  • Upgrading Repository - import error

    I've got Oracle Repository 4.0.12.100.2, and I'm upgrading to the latest release. The upgrade utility in RAU is trying to run IMP and stopping on an import error. The error flashes by so fast I can't see what the problem might be. and it doesn't seem to be logging the output from IMP. Is there any way that I can make it use the LOGFILE parameter, or at least do a pause before closing the window?
    Or if you have an idea what is wrong - that works for me too.

    Never mind - with some information from Oracle Support I found the log of the failed import. Then with the error message, I found out that I was using the import for Oracle 10gR2, but the database on which the repository is installed is 10gR1. So I needed the import for 10gR1 - which I didn't have and you can't download it anymore. Some scrounging around the office finally turned up an installation disk. I installed 10gR1 client - reconfigured RAU to use it - and the upgrade worked.
    Guess I'll need to upgrade the database to 10gR2 some day in the near future.

  • How to upgrade Repository?

    I have Oracle Warehouse Builder 10.1.0.2.0 and Repository 10.1.0.1.0, I applied patch 10.1.0.3 but I can't connect to repository because it isn't compatible.
    I hace Oracle Warehouse Builder client on Windows XP and the repository on Solaris, Database 9.2.0.1.0
    I tried to find patch for warehouse builder in Solaris but I can't
    Any help ?
    Thanks
    fernando.

    Hi,
    We have similar setup (XP and AIX). The Win32 10.1.0.3 has been out for a while but my understanding is that you need to upgrade the repositories as well as the front end. The 10.1.0.3 patch for UNIX platforms only become available recently.
    You can get it from metalink
    Click on "Patches and updates"
    Click "Quick Links to the Latest Patchsets, Mini Packs, and Maintenance Packs"
    Hover over Warehouse builder (bottom right hand side of page) and it shows Solaris Sparc 64 bit -> 10.1.0.3
    If this is not the right version of Solaris, I guess you would need to downgrade your XP until the correct patch becomes available.
    I have not yet patched front and back end so would be keen to know if it all hangs together.
    Steven

  • Error upgrading repository V4.2.01.01 to repository V04.03.02.04 for ODI11g

    I am following bellow link's step to upgrade my repository(MSSQL Server 2005):
    [ http://odiexperts.com/tag/repository ]
    After completing Work Repository credential I am getting following error:
    [2011-03-22T14:45:55.219+05:30] [ODI] [ERROR] [UPGCMP-00303] [upgrade.ODI] Target Work Repository ODI_WREP is invalid.
    [2011-03-22T14:45:55.219+05:30] [ODI] [ERROR] [upgrade.ODI] Cause: Target Work Repositority wasn't found in the given schema. Action: Define valid Target Work Repository credentials.
    [2011-03-22T14:45:55.219+05:30] [FrameworkMR] [ERROR] [UPGAST-01008] [upgrade.FrameworkMR] Schema examination failed for Oracle Data Integrator.
    [2011-03-22T14:45:55.219+05:30] [FrameworkMR] [ERROR] [upgrade.FrameworkMR] Cause: Repository upgrade framework determined that the examination phase of upgrade failed for the named component. This is often due to a failed prerequisite check. No schemas changes have been made to the component that failed. Action: Check the upgrade log files for the cause of the message. Correct the source of the problem if possible, and retry the examination. Do not go on to perform an actual upgrade in upgrade mode unless all components succeed during examination.
    [2011-03-22T14:45:55.219+05:30] [FrameworkMR] [NOTIFICATION] [upgrade.FrameworkMR] failure_total 1 m_upgradeMode N
    [2011-03-22T14:45:55.219+05:30] [FrameworkMR] [NOTIFICATION] [upgrade.FrameworkMR] failure_total 1 m_upgradeMode N
    [2011-03-22T14:45:55.219+05:30] [FrameworkMR] [ERROR] [UPGAST-01015] [upgrade.FrameworkMR] Some repository upgrade component-specific software modules report failure.
    [2011-03-22T14:45:55.219+05:30] [FrameworkMR] [ERROR] [upgrade.FrameworkMR] Cause: One or more component-specific software modules returned an error status during repository upgrade. Some other components might have upgraded successfully. Action: Review the upgrade logs to determine which components have failed, and pinpoint the source of the errors for each component. Correct the conditions that caused the errors. It may be possible to rerun the upgrade.
    [2011-03-22T14:45:55.219+05:30] [Framework] [NOTIFICATION] [upgrade.Framework] Finished examining components.
    [2011-03-22T14:45:55.422+05:30] [FrameworkMR] [NOTIFICATION] [upgrade.FrameworkMR] finalize() instance 1 of 1
    Please help out to solve this problem.
    Thanks in Advance
    Biswajit

    I believe you are getting the error in Step No 6 . For the corresponding already existing Work repository you would need to provide the new database so that UA can use that to copy the settings .

  • Migrate or upgrade repository?

    Hi
    We are moving to WinXP from WinNT and we have to upgrade to Designer 4.6.
    In the installation guide it gives a list that the Repository status should be if you are going to upgrade an existing 6i repository:
    4.0.12.30.25 (Production)
    4.0.12.40.3 (Release 2)
    4.0.12.46.1 (Release 3)
    4.0.12.52.1 (Release 4)
    4.0.12.69.2 (Release 4.1 or 4.1.1)
    4.0.12.80.6 (Release 4.2)
    4.0.12.88.2 (Release 4.3)
    4.0.12.89.9 (Release 4.4)
    4.0.12.90.11 (Release 4.5)
    When I checked, the repository status says:
    Oracle Designer/2000 (TM): Release 7.0.4.0.0 - Production.
    I presume then that the repository is version 6.0 rather than 6i.
    Am I correct? Will I have to migrate rather than upgrade?
    Thanks for any clarification on this.
    Cheers
    Ciaran

    Ciaran
    Oracle Designer/2000 (TM): Release 7.0.4.0.0 - Production.
    is not a 6i release, you will need to use the migration facility to get to 4.6
    With Repository 6i, there is no way to directly upgrade the old Repository (the structure of the Repository is too different to allow the upgrade); you need to first install the new Repository 6i, and to migrate your applications from 6.0 to 6i. The migration reads data from the old Repository via a database link and inserts it into 6i. At the end of the migration, 2 repositories still exist: the
    old Repository 6.0 (or 2.1.2) and the new Repository 6i.
    There are Migration Guides on both OTN and Metalink which should assist you with this process
    Oracle Designer 6i Migration Guide - April 2002
    on Metalink:
    - Click button "Top Tech Docs" (on the left)
    - Click hyperlink "Internet Developer Tools"
    - Click hyperlink "Oracle Designer"
    - Click hyperlink "White Papers"
    - Click hyperlink "Oracle Designer 6i Migration Guide - April 2002"
    Or from the Documentation link on OTN from the Designer Product
    Regards
    Paula Cope
    Designer QA Manage

  • Upgrade repository 9i windows to 10gR2 Linux

    I've got a 9i repository on a windows platform that I want to move to a 10gR2 Linux platform. The 10gR2 linux platform doesn't have the developer suite installed. Where do I start?

    Essentially use are just moving the repository database on Linux. The software for Designer only exists on Windows. You would therefore (briefly):
    - Export your existing repository using the 9i designer software.
    - Install the new designer 10g software on a Windows PC and set up the SQL*Net connection to the unix platform.
    - Use the Designer admin tools in 10g to do the import with the data going onto the linux database.
    That's only me thinking on the fly - you should read the migration guide so tell you exactly how to create the new repository. I'd have both in parrallel and switch off the 9i version once everything has migrated sucessfully.
    HTH
    Steve

  • 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

  • RPE-01012 after upgrade to 9.2.0.4

    LS,
    After upgrading OWB from 9.2.0.2.8 to 9.2.0.4, I'm getting the an error when trying to deploy code.
    Getting the following error:
    RPE-01012: Cannot deploy to the target location because it is owned by a different runtime platform.
    I've read that I need to tell OWB that now it has to use the new (upgraded) repository, so I created a new repository runtime connection, pointing to the new rep-owner, but that was -obviously- to no avail.
    Is there something else that needs to be done before code can be deployed again?
    Cheers, Patrick

    Good morning Nikolai,
    I've read that the only new user/schema that needs to be created is for the runtime repository. Somewhere further in the coming 'story' it will appear (bold).
    Let me explain how the upgrade went.
    This is what the readme says for general steps:
    1. Patch the Client Side (Design Time) install
    2. Patch the Server Side install
    3. Upgrade the Client Side (Design Time) Repository
    4. Upgrade the Runtime Repository
    5. Re-create the Runtime Repository connections
    Also it states the following:
    Note: Make sure that you have obtained the patch for the platform where your Server Side install is located. This may not be the same platform as your Client Side (Design Time) install. E.g. If you perform Design Time tasks on Windows, but deploy and execute on Solaris, you will need both the Windows and Solaris versions of the patch.
    Since our database (9i) is running on AIX (5L) and the client is Windows 2000 Pro, both patches have been applied.
    The DBA's have applied the AIX-patch for the server side, but also for the client (remark of one of the DBA's: "The runntime is installed on database and the client also installed on AIX side. I will do both."), so also "II.4. Upgrading the Design Time Repository".
    On Windows I patched client as well as server installation (i.e. the copying of new files to OWB-home with two batch-files).
    I did NOT run owb\bin\win32\DTupg92to9204.bat as stated in section II.4.1, because the DBA's had already done this... on AIX though.
    Section II.5 has also been performed by the DBA's. Note the following here: "Create a new Runtime Repository in same database as the old Runtime Repository. DO NOT create new Target Schema(s) or new Runtime Access User(s). The In-place Migration will re-associate your current Target Schema(s) and Runtime Access User(s) to the new Runtime Repository. This step must be performed on the Server Side install." I assume the DBA's performed the in-place migration.
    After this I was NOT allowed to run the indicated next three steps on the windows environment (I guess that makes sense since the new repository has already been created... but the owb home on my PC therefore is unchanged, don't know whether that matters, I guess it shouldn't).
    In II.6 I have to connect to new environment. I therefore connect with my OWB-client using the same usr/pwd as always (since that didn't change), and in OWB I could see my project straight away (therefore I did NOT import the project that I have exported prior to the entire upgrade process).
    I created a new runtime repository connection pointing at the new user.
    And now the situation where deploying a mapping results in RPE-01012.
    The funny thing is that I deployed 3 sequences (which have been defined BEFORE the upgrade), and that worked well. I also created a new table definition and deployed that, also no problem.
    So... what's the verdict?
    Cheers, Patrick

  • NEW 9iAS PORTAL UPGRADE SCRIPTS NOW AVAILABLE

    Based on detailed customer and internal feedback, Oracle9iAS Portal Product Development is now making available NEW and significantly IMPROVED versions of the 9iAS Portal Upgrade Scripts as of 4/20/2001.
    [list]
    [*]Oracle9iAS Portal Upgrade Scripts (2.2/3.0.3.3.3 -> 3.0.6) for Windows NT
    [*]Oracle9iAS Portal Upgrade Scripts (2.2/3.0.3.3.3 -> 3.0.6) for Solaris
    [list]
    The upgrade scripts provided here (at the links above) will allow you to upgrade the following environments:
    a) Your existing WebDB 2.2 installations to Oracle9iAS Portal 3.0.6.
    b) Your existing Oracle Portal Early Adopters Release (3.0.3.3.3) to Oracle9iAS Portal 3.0.6.
    For specific upgrade documentation (also updated!), please consult the links below:
    [list]
    [*]Release notes for Oracle9iAS Portal 3.0.6 Upgrade
    [*]Oracle9iAS Portal Upgrade Guide for NT/2000
    [*]Oracle9iAS Portal Upgrade Guide for Solaris
    [list]
    NOTE: For the final step of the upgrade process, you will also need to download additional upgrade scripts to take you from Oracle9iAS Portal 3.0.6 to the current 3.0.8.9.8 Oracle9iAS Portal release.
    NOTE: Scripts and Doc for the 9iAS Portal 3.0.6 to 3.0.8 Upgrade are expected to be made available later this week (April 24-27)
    The following is a list of bugs and issues addressed with the latest 9iAS Portal 3.0.6 upgrade scripts.
    Upgrade Bugs Fixed for the 2.2 -> 3.0.6 upgrade
    1697813 - NT SCRIPT IS ASKING FOR VALUES 3 AND 4
    1697862 - APPIMP.CSH
    1697863 - UNEXPECTED ERROR ENCOUNTERED ERRORS OCCURED IN APPIMP.CSH
    1697828 - SB: MISSING LINKS FOR THE FOR ITEMS
    1697781 - MIGRATION FAILED
    1714261 : APPLICATION IMPORT SCRIPT FAILS
    1716379 : IMPORT SCRIPT TERMINATES ABNORMALLY
    1712877 : EXPORTING A APPLICATION FAILS
    1715551 : NO ACTION LINKS FOR LOVS WHEN IMPORTED FROM WEBDB SCHEMA !!
    1740211 : AFTER UPGRADE EDITING THE SCHEMA GIVING ERROR
    1697795 - MISSING TEMPLATE AFTER UPGRADE (DOC BUG)
    1697839 - 22-306:DOC: NEEDS TO DOCUMENT
    1697835 - 22-306:DOC: NEEDS TO DOCUMENT
    Additional Bug Fixes
    1703032 - IMPROVE PERFORMANCE FOR THE FOLDER IN EDIT-MODE.
    1703040 - EDIT LINKS APPEAR ON FOLDERS EVEN THOUGH USER DOES NOT HAVE PRIVILEGES.
    1703052 - SUBFOLDERS UNDER THE FOLDERS NOT ALIGNED PROPERLY
    1703063 - PERSPECTIVE PAGE RENDERS SLOWLY
    1703070 - NAVBAR LOGON/LOGOFF LINKS IS HARDCODED TO GO THE CONTENT AREA ROOT FOLDER
    1703072 - NAVBAR LOGON/LOGOFF LINKS DOES NOT WORK FOR PERSONAL FOLDERS.
    1689813 - ITEM LINK IN SEARCH RESULTS SHOULD BE DIRECT ACCESS URL
    null

    Richard,
    You'll need to have 1.0.2.2 to be installed on the middle tier before performing the upgrade for your portal 3.0.9 upgrade repository on the database end. So that means, you'll need to wait for the Linux download of iAS 1.0.2.2 to be available before beginning your upgrade of the portal repository, assuming that your middle tier of iAS is also on a Linux box.
    iAS 1.0.2.2 does indeed include Portal 3.0.9, of which Portal 3.0.9 components will be installed during the upgrade process along with the upgrade of the middle tier. During the upgrade process, the installer (from my personal experience on NT), will notify you that it is performing an upgrade installation of your middle tier, provided that you specified the middle tier's ORACLE_HOME when executing the oracle installer.
    Just be sure to read and follow the 9iAS Migration guide before beginning your upgrade of the middle tier to iAS 1.0.2.2. After upgrading the middle tier to 1.0.2.2, the actual upgrade of the portal repository was extremely simple by comparison.
    The upgrade of the portal repository took a few hours (my recommendation is to invoke it off before leaving for the evening), and it will leave a detailed logfile for you to peruse afterwards, if you choose).
    Best Regards,
    Harry

  • ImageUltra Builder 5 - Can't get new computers to connect to repository

    Greetings.  I've recently (finally) upgraded from IUB 3 to IUB 5 and while our older PC's connect to the upgraded repository and image just fine, I can't get newer PC's to even grab an IP in the WinPE environment after booting off a disc (for network distribution).
    I know this is because I need to figure out how to get the latest NIC drivers (for like a T520) into the repository for IUB 5, but I've followed the instructions in the manual for it and no matter what I try I cannot get them loaded properly.
    I found another post in these forums that appeared to address this, but after following the (somewhat muddy) instructions there I still cannot get it working.
    So far I'm placing all my drivers for the T520 etc. into \repositoryshare\drvs_7pe\drivers\preboot\drivers AND \repositoryshare\drvs_7pe\wim\drivers\windows\system32.
    Note that these drivers worked just great on my IUB 3 boot discs.  So I guess I don't have the \repositoryshare\... folder structure setup correctly (?)
    Thanks for the help in advance!

    kimnarakasa wrote:
    same problem when i install this wireless router. Im doing it for 2 days. Sometimes its successful but when I am browsing I see my browser disconnected intermitently. Cisco must do something about this. Because its really annoying
    Make sure firmware is updated to the latest version. You can download it here http://homesupport.cisco.com/en-us/support/routers/WRT120N.  Just reset and reconfigure the router. That should fix it.
    * Setting up a Linksys router for DSL Internet connection
    http://www6.nohold.net/Cisco2/ukp.aspx?vw=1&docid=20ee1457387f40178cd5f41d4b585db4_3687.xml&pid=80&r...
    * Setting up a Linksys router with Cable Internet service
    http://www6.nohold.net/Cisco2/ukp.aspx?vw=1&docid=0ff4c94586a345d082828ec2161aaecf_3686.xml&pid=80&r...

  • How to deploy repository in OBIEE 11g

    I installed Oracle BI on a 32 bit system. Used the upgrade assistant to upgrade the repository from 10g to 11g. Everything went well and I could see all my dashboard.
    Now my question is I need to do this installation on my clients computer so I installed BI on it. But now instead of going thru upgrade process can I just use the upgraded repository from my system? If so how should I do the deployment?
    Many thanks

    Thanks for the link. It did work.
    However I need to do this on few systems. Is there a way to do without using UI. I mean can i just copy few files or update existing once to do this? Or do in silent mode. Basically I don't want to connect client computer every time if they want to install BI on a seperate box. So looking for some automated way....
    Also when I tired to open this RPD in Admin tool I was keep getting invalid username/password. This is error in
    [2011-02-25T18:25:00.000+00:00] [OracleBIServerComponent] [ERROR:1] [] [] [ecid: 00hyvMvD9ezFw0zvBP0DRz1ldOy2jkIx60001S800000a] [tid: 157c] Error Message For Administrator: User not authenticated.
    [2011-02-25T18:25:00.000+00:00] [OracleBIServerComponent] [ERROR:1] [] [] [ecid: 00hyvMvD9ezFw0zvBP0DRz1ldOy2jkIx60001S800000a] [tid: 157c] [nQSError: 43126] Authentication failed: invalid user/password.

Maybe you are looking for