No catalog upgrade

For us Lightroom enthusiasts I find it ridiculous that we don't have the feature to upgrade our current catalogs to the new v4 format.
Don't treat us as being stupid. We know that we can't downgrade later if we choose not to move up to the new v4 once it gets released.
We know to backup our catalogs prior to upgrading like all good people should and to have backups stored on a secondary device in case of a disaster.
Currently there is no point to me using the new Lightroom 4 and providing feedback if I can't use my current catalogs.
Please fix this clear oversight.

Thanks for the reply back so quickly.
Fortunately I've been in the computer industry for over 15 years and have considerable programming experience. Beta should already be a well tested product which is ready for consumer testing where an alpha version requires rigorous testing to fix any gaping holes in the programming whilst release candidate is final bugcheck stage with some minor updates and improvements.
So in theory as long as Adobe is mindful of development lifecycle of programming and maintenance then the Beta should be very stable and the catalog database should have already been thorough tested. Not only that, the catalog database should have been decided upon quite some time ago as part of the scope of the project with minor changes occurring through the development of the software.
I know that bugs do still creep in from time to time but nothing tests systems better than actually running a production database which has over 20,000 photographs, countless modifications and so on. You won't get any better feedback than that.
Adobes' licensing agreements already cover them for any data loss incurred and secondary it's a beta. So data loss is only the fault of the user not maintaining adequate backups. This isn't the responsibility of Adobe and Adobe encourages users to regularly backup their data as part of the programs general operations. So users to ignore such notifications is their own ignorance and is indicative of not a lack of understanding but ignorance. The immortality syndrome comes into play here where the mentality is that it will never happen to them. So no matter what, users will be ignorant until data loss does occur to them and thinking that shielding them from this is in itself ignorant. Education is best and that's what I try to empower people with knowledge. Hell, just put a big disclaimer when you first download the beta, when you install it and when the user is about to upgrade about how important backups are and that it's a beta and how downgrade is not possible unless you have a valid backup prior to the upgrade blah blah blah.
But really only the cutting edge prosumers and pro photographers would be willing to cut their teeth on the latest versions and I'm pretty sure that these beta releases would be speaking straight to the heart of the Lightroom users who understand the risks involved away. So most of this post becomes moot in the end.

Similar Messages

  • RMAN Catalog Upgrade Understanding.

    Hi,
    We just upgraded our target database from oracle version 9.2.0.7 to 9.2.0.8 and our catalog database is still in 9.2.0.7 . Do we need to upgrade the recovery catalog schema in the catalog database If so then how to do that.
    I tried running upgrade catalog command on the recovery schema of the catalog database and it is upgrading to the 9.2.00 version packages.
    reldb3d:instra /opt/app/oracle/product/9.2.0.8/rdbms/admin> rman catalog instra/[email protected]
    Recovery Manager: Release 9.2.0.8.0 - 64bit Production
    Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
    connected to recovery catalog database
    RMAN> upgrade catalog;
    recovery catalog owner is INSTRA
    enter UPGRADE CATALOG command again to confirm catalog upgrade
    RMAN> upgrade catalog;
    recovery catalog upgraded to version 09.02.00
    DBMS_RCVMAN package upgraded to version 09.02.00
    DBMS_RCVCAT package upgraded to version 09.02.00
    Right now I am skeptical is it the correct way of upgrading the catalog schema in the catalog database.
    Any suggestions/advice will be highly appreciated.
    Thanks,
    Raheem

    The schema version (or the objects therein) is different from the version of the database in which the rc schema resides. As long as oracle wouldn't force you to upgrade the database, upgrading the schema is enough. The same applies to the the repository database for grid control. The version of the grid repository schema can be different from the version of the database software.
    Whatever you did is correct.

  • Faled Catalog upgrading to 11g

    Hi all,
    I've got a problem migrating the web catalog to 11g.
    I made all the process with the update assistant (ua.bat) to upgrade repository & catalog... for the repository is everithing ok but the catalog upgrade fails with error:
    "Upgrading catalog failed.[[Path not found (/shared/_ibots)]]"
    Like this blog http://www.skurabigroup.com/blog/?p=759 suggest i created an empty folder for delivers since i never used that part of web catalog before.
    Any suggestions
    Thanks
    Francesco
    Edited by: Francesco on Sep 22, 2010 2:50 PM

    Hi Gurus,
    I am also getting the following error during catalog upgrade..
    'Presentation Services should have been DOWN after catalog upgrade but was left in state: ALIVE'
    Any idea what should i do?
    Thanks
    coolmesh84

  • OBIEE Repository and Catalog Upgrade(11.1.1.5 to 11.1.1.7)

    Hi,
    I see a lot of documentation on upgrade but I just couldn't find this. I installed OBI 11.1.1.7 and trying to test it on our own repository and reports.
    I want to upgrade OBI 11.1.1.5 repository and catalog to 11.1.1.7 and run those in my new installation. Is this possible?
    Regards

    Hi
    I found this ...
    the text shown, belongs to an oracle document
    Link: Post-Patching Procedures - 11g Release 1 (11.1.1.7.0)
    The text starts here...
    ->
    5.12.2 Updating Oracle BI Presentation Catalogs
    When updating your Oracle Business Intelligence (BI) software from Release 11.1.1.3.0, 11.1.1.5.0 or 11.1.1.6.x, you must manually update your Oracle BI Presentation Catalogs. Instructions are provided below:
    Stop Oracle BI Presentation Services using Oracle Enterprise Manager.
    For details, see "Using Fusion Middleware Control to Start and Stop Oracle Business Intelligence System Components and Java Components" in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.
    Back up your Release 11.1.1.3.0, 11.1.1.5.0 or 11.1.1.6.x catalogs by using the 7-Zip utility to create a compressed file for it.
    Create a backup copy of the instanceconfig.xml file.
    The instanceconfig.xml file is located in the ORACLE_INSTANCE/config/OracleBIPresentationServicesComponent/coreapplication_obipsn (on UNIX operating systems) or ORACLE_INSTANCE\config\OracleBIPresentationServicesComponent\coreapplication_obipsn (on Windows operating systems) directory.
    Change the upgradeAndExit option to true in the instanceconfig.xml file.
    Find the following code:
    <Catalog>
       <UpgradeAndExit>false</UpgradeAndExit>
    </Catalog>
    Change it to the following:
    <Catalog>
       <UpgradeAndExit>true</UpgradeAndExit>
    </Catalog>
    Start Oracle BI Presentation Services using the following OPMN command to update the catalogs:
    opmnctl startproc ias-component=coreapplication_obipsn
    For example, on a UNIX operating system:
    cd ORACLE_INSTANCE/bin
    ./opmnctl startproc ias-component=coreapplication_obips1
    On a Windows operating system:
    cd ORACLE_INSTANCE\bin
    opmnctl startproc ias-component=coreapplication_obips1
    After the catalogs are updated, edit the instanceconfig.xml file again and change the upgradeAndExit option back to false.
    Restart Oracle BI Presentation Services using Fusion Middleware Control.
    ->
    Ends here...
    In my opinion, is the same answer, as Seth mentioned
    -> Seth 29-abr-2013 8:52
    Regards
    Miguel F

  • RPD and Catalog Upgrade to 11.1.1.6

    Hi,
    We have a project to upgrade from OBIEE 10.1.3.4.1 to 11.1.1.6.0. The OBIEE installation is on RHEL 5.8 x86-64 server. I have the following questions reagarding this upgrade.
    1) Can I upgrade the RPD and Catalog straight from 10.1.3.4.1 to 11.1.1.6.0 or
    2) Do I have to upgrade the RPD and Catalog from 10.1.3.4.1 to a intermediate version of OBIEE 11g say (11.1.1.5.0) and then upgrade it to 11.1.1.6.0?
    Responses are appreciated.
    Thanks in advance.

    Yes. You can go to 11.1.1.6
    Check this
    http://docs.oracle.com/cd/E23943_01/bi.1111/e16452/bi_plan.htm#CACIBFHF
    If helps pls mark as correct
    Edited by: Srini VEERAVALLI on Feb 11, 2013 3:55 PM

  • Warning - Lightroom 5 catalog upgrade issue

    I had opened one of my LR4 catalogs in LR5 to do some testing. Knowing that it would upgrade and not kill my original catalog.
    However I had created 1:1 previews for the catalog, about an 8gb file, and didn't realize that the upgrade process actually renamed the preview file to match the LR5 new catalog.
    When I reopened in LR4 to work on my production job, all previews were gone. This was a wedding with about 2,000 images so it takes some time to rebuild.
    Not sure if I could have just copied and renamed it or not. I'll have to test that out on a smaller catalog.
    So if you are going to test some catalogs just beware that this happens and you may want to backup your preview file first.
    Dave Doeppel
    Lightroom 4 ACE

    Yeah I just tested it again and watched it.  So in the folder was test.lrcat and "test Previews.lrdata" after the upgrade I now had the original test.lrcat and the new test-2.lrcat and only "test-2 PReviews.lrdata"
    I just looked at the dialogue box for the upgrade and it indeed indicates that the Preview files will be moved.

  • BIG CATALOG UPGRADE LR 3 TO 5...

    I have a BIG Lightroom 3 Catalog stored on an external hard drive. I upgraded to Lightroom 5 last month, have experimented/familiarized myself with new version the last few weeks & am now ready to consolidate last few weeks work with master catalog, aka upgrade the master catalog. Anything i should be worried about/ aware of before I do this?... Lots of work in the old catalog, don't want to make any mistakes.

    Watching this video first helped calm some of my pre-upgrade jitters... How to Upgrade to Lightroom 5 | Laura Shoe's Lightroom Training, Tutorials and Tips
    (I'd already read the help text in the Adobe Lightroom catalog FAQ )
    Here it goes though! :-)

  • Can I open Lightroom without upgrading my catalog?

    Unfortunately I'm not sure how to do a screen capture, so I'll try to type what I'm seeing.
    When I click on the LIghtroom icon, I get a message box that says "Please upgrade the catalog file "Lightroom Catalog 3" for use with Lightroom 3.  It continues "Lightroom will create a new catalog file in the destination indicated below.  The previews will also be moved to the location and converted for use in Lightroom 3"  Upgrade destination C:/Documents and Settings/...../Lightroom 3 Catalog-7.lrcat
    There is a button to choose a different catalog, upgrade or exit.
    When I open the button to change catalogs, it gives me one option, but when I click on it, I go back to the "Lightroom will create a new catalog"
    My concern with upgrading is that I've a workflow for the catalog that's at C:/Documents and Settings/..../Lightroom 3 Catalog-5.lrcat  Earlier today, I clicked on the dialog that resulted in a catalog at Lightroom Catalog-6.lrcat, but when I opened it, I'd lost all the listings for the Free Agent drive (usually G:/ where I do my daily uploads.  I could still see the external hard drive (E:) where I save edited work, but it indicated that I would have to locate all of the folders I'd created on the E: drive.  I saw only the default collections on the left hand side -- (smart collections, last month, etc.).
    I finally was able to get back to Lightroom 3 Catalog-5, which had all the work, but I'm not sure how to recover all my collections and folders if I Lightroom creates a new catalog at a destination that has a different number.  The problem is that now I can't seem to open Lightroom 3 at all -- when I click on Change, I don't see my catalog 5  in the default folder.  I know I found it once before, and it became an option on the pulldown menu.  But I don't want to have to keep finding it on the drive where I store it so I can keep my indexing and folder and catalog organization. 
    Lightroom 3 Catalog 5.lrcat works fine for me.  My default for backing up is whenever I close the program, so I'm confident in it's integrity.  How can I open Lightroom with the catalog that works for me --without getting messages that seem to force me to do an upgrade I don't want to do.
    Thanks for your help!

    I've been using Lightroom 3 for about a year.    Right now I'm going
    back to the folder with my backups and opening Lightroom 3 Catalog-5.  I
    think I've tried to reconstruct my left side panel with earlier
    Lightroom 3 Catalog x versions.  I don't have all the collections and
    folders I had with my Lightroom 2 catalog.    That catalog seemed to
    have been corrupt when I moved to Lightroom 3.  I don't recall how I did
    it, but I guess I imported the photos and tried to start over with my
    collections.
    Jan

  • Upgraded LR1 - LR3 Catalog: blank Grid, non functioning app

    I've been dealing with support on this, but they're utterly useless, taking days to get back to me and spinning me over troubleshooting 101 stuff.
    Problem:
    Upgraded a perfectly working LR1 catalog to LR3.  No issues during upgrade.
    Upon trying to use the LR3, the first thousand or so of my photos show up in Grid, but everything after that is blank. By that I mean, a grid cell is drawn, but LR3 doesn't display a thumbnail, or any cell extras or metadata.
    Clicking on one of these empty cells gives me a thumbnail frame and some metadata (slowwwwly).
    Going to Loupe View on a non-empty cell gives me a "Loading..." spinner and an unrendered thumbnail preview (CPU is not ramping up at all)
    Going to Loupe View on an empty cell just gives me a blank screen (CPU is not ramping up at all)
    Develop module does load the picture, but slowly.
    When I quit, the app freezes up completely, with beachball.  Must force-quit (after giving it 20 minutes in case it was actually trying to do something)
    Initially, when I load LR3, my CPU runs high, 75%, like it's working on something.  Then it just cuts out as if it's given up.
    Console output when this happens is the following:
    6/17/10 7:27:38 PM Adobe Lightroom 3[518] ServerProcess [AsyncDataServer( Lightroom 3 Catalog.lrcat )] ERRORSERVER<AsyncDataServer( Lightroom 3 Catalog.lrcat )>: A command threw an exception.
    6/17/10 7:27:38 PM Adobe Lightroom 3[518] ServerProcess [AsyncDataServer( Lightroom 3 Catalog.lrcat )] ERROR Error: ?:0: attempt to perform arithmetic on field '?' (a nil value)
    6/17/10 7:27:38 PM Adobe Lightroom 3[518] Error initializing alternate universe. bad argument #1 to 'pairs' (table expected, got nil)
    System:
    MacBook Pro Core2Duo 2.1Ghz 3GB RAM, 500GB Drive.
    Initially Mac OS 10.5.8, but I tried upgrading to 10.6.3 and 10.6.4 (no luck).
    Library: 21,000 photos
    Other things I've tried:
    Trashing all LR3 prefs, caches (running YASU), LR preview caches, plists, extensions, reinstalling, restarting -- no luck
    Noticed it was copying the LR1 prefs plist, so I archived that.  LR3 generated a new pref, but no help
    Downloaded LR2 Demo, upgraded LR1 Catalog to LR2 Catalog (which works perfectly, no issues), and then LR2 Cat -> LR3 -- no luck
    Checking integrity of Catalog in LR1 and LR2 (no problems) and LR3 when upgrading (no problems)
    LR3 runs fine on an empty catalog and if I point it at my photo folder and import everything, it's ok (with none of my 3 years of modifications of course).
    Is my only option to write out LR1 data to sidecar files and then setup a new Catalog in LR3?

    Well, on top of having full access to the photo files, LR obviously has proper permissions to affect the files it generates in the AppSupport>Adobe>Lightroom folder, the Caches>Lightroom folder, the Pictures>Lightroom folder and the Preferences> folder, otherwise it wouldn't be able to build a new catalog, new prefs, new caches and so forth when I generate a new empty catalog.
    I really doubt this is a permissions voodoo issue or a monitor profile issue.
    LR3 works fine with a brand new catalog (and all the same Photo files).
    LR1 and LR2 have absolutely no problem with my catalog and photo files. 
    LR2 upgrades my LR1 Catalog without issue.
    LR3 fails with my upgraded catalog (and all the same photo files)
    Unless I'm missing something in my logic tree here, it seems to me this is obviously a problem with LR3 upgrading my Catalog. 
    Other people's catalogs upgrade fine, and that's dandy, but my catalog doesn't upgrade AND it fails with exactly the same error message every time in the Console (See original post), which seem to be related to some internal db issue, dividing by zero, nil values. 
    Something ain't being handled right by LR3 that previous versions of LR had no problem with. 

  • Upgrade catalog

    Hello all,
    After upgrading my 10.2.0.3 database (configured Rman backup to TAPE) to 10.2.0.4,
    i got the bellow message when i connected to RMAN:
    PL/SQL package RMAN.DBMS_RCVCAT version 10.02.00.03 in RCVCAT database is not current
    PL/SQL package RMAN.DBMS_RCVMAN version 10.02.00.03 in RCVCAT database is not current
    Then is issued the following comamnd
    RMAN> upgrade catalog;
    recovery catalog owner is RMAN
    enter UPGRADE CATALOG command again to confirm catalog upgrade
    RMAN>upgrade catalog;
    recovery catalog upgraded to version 10.02.00.04
    DBMS_RCVMAN package upgraded to verison 10.02.00.03
    DBMS_RCVCAT package upgraded to verison 10.02.00.03
    I want to confirm whether my stpes are correct or i have missed any steps in upgrading my
    recovery catalog.
    Please assist me,

    user12133150 wrote:
    Hi,
    i want to upgrade my recovery catalog database to version 10.2.0.4. Is it helpful to take backup of recovery catalog database before upgrading.
    thanks & regards,As it is suggested to take backup before any upgrade/migrate procedure, I would be good if you do it

  • Will my catalog safely Upgrade from Elements 5 to Elements 8?

    I have over 16,000 photos tagged in my Elements 5 catalog.  I am hesitant to upgrade to 8 for fear of not being able to reconnect to the catalog.  Any assurances or tips?  Chet
    Message title was edited by: Brett N

    As long as there is nothing currently wrong with your catalog and nothing interferes with the conversion process, you should have a save catalog conversion.
    Besides, when the conversion takes place, a copy of your catalog is created. So even if the conversion fails for some reason, you'll still have your original catalog working in PSE5.
    More info here:
    Common catalog upgrade issues | Organizer| Elements 6 or later
    Troubleshoot catalog backup, upgrade | Organizer | Elements 6 or later
    Troubleshoot catalog issues | Organizer | Elements 6 and later

  • Forgotten to upgrade recovery catalog

    hi ,
    i sucessfully upgraded from 11.2.0.1 to 11.2.0.3. BUt forgotten to upgrade the catalog.
    which is the below steps..... (copy from a blogs, not mine)
    lnx04ora.bai.com: FITSD>/opt/app/oracle/product/11.2.0.3/db_1/bin/rman target / catalog ......
    Recovery Manager: Release 11.2.0.3.0 - Production on Fri Feb 10 04:33:40 2012
    Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: FITSD (DBID=3617642037)
    connected to recovery catalog database
    recovery catalog is partially upgraded to 11.02.00.03
    RMAN> upgrade catalog;
    recovery catalog owner is RMAN11GR2
    enter UPGRADE CATALOG command again to confirm catalog upgrade
    RMAN>  upgrade catalog;
    recovery catalog upgraded to version 11.02.00.03
    DBMS_RCVMAN package upgraded to version 11.02.00.03
    DBMS_RCVCAT package upgraded to version 11.02.00.03
    RMAN>not too sure can it be done llive, meaning any need to shut the databse down?

    damorgan wrote:
    Then, by definition, you did not successfully upgrade anything.
    Open an SR at MyOracleSupport and ask them to advise you as to how to safely fix the mess.
    If you follow a blog post and something goes terribly wrong who is going to lose their job? You or the blogger?oh no no, not going to follow blindly. JUst copy the command out and paste here so that i can show the command.
    I am clearifying whether is there any thing i need pre- task. NOt too sure i need to shutdown completely, backup the rman catalog schema, etc.

  • RMAN - upgrade catalog taking too long

    Hello ,
    I am trying to upgrade the rman catalog and it is taking too long to upgrade , infact after 4 hours wait time it is still excuting the upgrade command .
    Target database is : 11.2.0.3 PSU1
    catalog database : 11.2.0.2
    upgrading the rman catalog to 11.2.0.3 .
    I tried executing the command at a very quiet time of the day when catalog is not been used by any database . Please advice if you have encountered the similar issue and fixed it .
    Thanks
    Venkat

    After some time into execution of "upgrade catalog" i got the output as below , and after that i let all the jobs of rman execute completely from diff databases that are connected to catalog and re-executed the "upgrade catalog" command , which finally completed the upgrade process with out the issues .
    Error :
    RMAN> upgrade catalog;
    error creating upgcat_strt_0
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-06004: ORACLE error from recovery catalog database: ORA-00060: deadlock detected while waiting for resource
    Re-executed when no sessions are connected to catalog and the upgrade process is successful .
    RMAN> connect catalog rman/rman@database
    connected to recovery catalog database
    PL/SQL package RMAN.DBMS_RCVCAT version 11.02.00.02 in RCVCAT database is not cu
    PL/SQL package RMAN.DBMS_RCVMAN version 11.02.00.02 in RCVCAT database is not cu
    RMAN> upgrade catalog;
    recovery catalog owner is RMAN
    enter UPGRADE CATALOG command again to confirm catalog upgrade
    RMAN> upgrade catalog;
    recovery catalog upgraded to version 11.02.00.03
    DBMS_RCVMAN package upgraded to version 11.02.00.03
    DBMS_RCVCAT package upgraded to version 11.02.00.03
    Thanks
    Venkat

  • We need to upgrade your catalog for use with Lightroom 6.

    Adobe CC member.  Downloaded new LR CC.  Shows as installed in Adobe creative cloud.  Wouldn't run at first, but logged out and back in.  Now upon launch I get a dialogue box named Lightroom Catalog Upgrade, asking to click to upgrade my catalog, but this freezes with an unending blue circle  and the program never launches.  I have tried deleting and reloading the entire program.  I still have LR 5 on my machine.  Is this normal?  I thought CC replaced 5.  Help appreciated.

    To 3110,
    I am facing a similar situation here. The description that you posted matches my requirement more or less.
    So... which option did u choose? And any suggestions on how to go about it for people who are implementing a similar architecture?
    Cheers,
    V

  • Upgrade 10G to 11.1.1.5 in Clustered environment

    I successfully ran the upgrade assistant on a single server install. Both RPD and Catalog upgraded with no issues. I scaled out to a 2 node cluster and attempted the upgrade with the assistant again. This time it fails. Here is log entries:
    [2011-07-20T15:16:07.861-04:00] [Framework] [NOTIFICATION] [upgrade.Framework] Starting to upgrade components.
    [2011-07-20T15:16:07.861-04:00] [Framework] [NOTIFICATION] [upgrade.Framework] Retain Source Ports: false
    [2011-07-20T15:16:07.861-04:00] [Framework] [NOTIFICATION] [upgrade.Framework] Stop 10g Components: false
    [2011-07-20T15:16:07.861-04:00] [Framework] [NOTIFICATION] [upgrade.Framework] Start 11g Components: false
    [2011-07-20T15:16:07.876-04:00] [Framework] [NOTIFICATION] [upgrade.Framework] Managed server bi_server2 state is: RUNNING
    [2011-07-20T15:16:07.876-04:00] [Framework] [NOTIFICATION] [upgrade.Framework] Starting to upgrade BIEE.
    [2011-07-20T15:16:07.954-04:00] [Framework] [ERROR] [UPGAST-00138] [upgrade.Framework] upgrade exception occurred
    [2011-07-20T15:16:07.954-04:00] [Framework] [ERROR] [upgrade.Framework] Cause: An unexpected upgrade exception has occurred. Action: See the secondary error message for additional details.
    [2011-07-20T15:16:07.954-04:00] [Framework] [ERROR] [upgrade.Framework] UPGCMP-02712: Expected oracle.biee.admin:oracleInstance=*,type=BIDomain.OracleInstance,group=Service Oracle instance, found 2
    [2011-07-20T15:16:07.954-04:00] [Framework] [ERROR] [upgrade.Framework] UPGCMP-02712: Expected oracle.biee.admin:oracleInstance=*,type=BIDomain.OracleInstance,group=Service Oracle instance, found 2
    [2011-07-20T15:16:07.954-04:00] [Framework] [NOTIFICATION] [upgrade.Framework] Finished upgrading BIEE with status: Failure.
    [2011-07-20T15:16:07.954-04:00] [Framework] [NOTIFICATION] [upgrade.Framework] Finished upgrading components.
    [2011-07-20T15:16:07.954-04:00] [Framework] [NOTIFICATION] [upgrade.Framework] 0 components upgraded with success.
    [2011-07-20T15:16:07.954-04:00] [Framework] [NOTIFICATION] [upgrade.Framework] 1 components upgraded with failure.
    Question….can you use upgrade assistant in clustered environment?
    Thanks!

    You can only use the upgrade assistant to upgrade to a single instance Oracle BI 11g server. Typically this is a sandbox server environment or a VM that can simply be wiped clean after the upgrade. Then move the RPD,WebCat, etc. and AppRoles that get created during the upgrade process to a development server. The UA is looking for a single instance installation environment and that environment should be clean/fresh to avoid confusion and conflicts.
    Please award points if helpful.

Maybe you are looking for

  • Switch to Open Item Management at a Line Item Level

    Hi Guru's, I want to change a non Open Item G/L account to an Open Item  at Line Item level, we are on version 6.4 We have activated New G/L and I checked OSS note 175960, it says its not applicable if New G/L activated. I tried program FAGL_SWITCH_T

  • VM Error when starting up or deleting

    Hi, we got a virtual machine which can not be started neither deleted (for reinstallation). Our current OVS version is 2.2.1. Trying to startup or delete this virtual machine from the OVS Manager is giving the following error: ##### STARTING UP Start

  • Apex_collection.create_collection_from_query and ORA-00900 Invalid SQL

    I am very new to collections and I am having an issue creating my first collection.  When I execute the following code I get ORA-00900  invalid sql. apex_collection.create_collection_from_query ('TEST', 'select * from apex_collections', 'NO'); Any gu

  • Message status showing "WAIT TRANSMIT" for longer time!!!

    Hi Gurus, The message status is showing as WAIT TRANSMIT in Oracle B2B reports, after long time (after even 12 hrs, this is the ack message(MDN)). I have bounced the Oracle B2B server, but the status is still the same? :-( What may be cause for this?

  • Essbase exports

    Is it better to export in column format or without columns for data backups?