| Upgrading the platform (on reporting side atleast, not to | | | | are available in "OBI Apps Upgrade.pdf" page 6-37 to |
| mix with ETL side) is often straight forward and easy. | | | | page 6-44. |
| You may encounter a bug or a minor glitch which will | | | | We had multiple errors during merge process. The goal |
| either have a bug fix or at least a work around | | | | here is to minimize this so that least manual work is |
| solution. Its often a good idea to wait couple of week | | | | required later. Way to do this is notice pattern of error |
| after release of upgrade platform so that most | | | | and then change the custom RPD (equalized custom |
| common bugs are reported and a solution available. | | | | RPD) before merging and making the objects same |
| That being said, same may not be true about | | | | as in 7.9.6.1 RPD, so that the algorithm treats the object |
| upgrading the pre-built business intelligence applications. | | | | as equal. |
| We recently performed upgrade from version 7.9.2 to | | | | 4. After RPDs are successfull merged, consistency |
| version 7.9.6.1. The process is complex and time | | | | check needs to be performed. Here again there will be |
| consuming, can take weeks if not months depending | | | | patterns of error, some can be fixed by making |
| on magnitude of customizations and scope of existing | | | | changed to RPD before merging and then merging |
| implementation. We had to upgrade the platform first, | | | | again, others will need to be fixed manually. |
| the RPD definition, the catalog, then finally perform | | | | We faced an unusuall error that read: "[nQSError: |
| extensive regression testing. For benefit of other | | | | 42001] Missing repository object with ID=3003:338714". |
| individuals I list here steps we took to upgrade the | | | | This error completely halted the process as we could |
| RPD: | | | | not fix the error without knowing where the error is |
| 1. We will need three repositories to begin with, 7.9.2 | | | | comming from. To fix this issue we followed three |
| original RPD, 7.9.2 customized RPD and 7.9.61 RPD. Its | | | | step process: |
| important than in 7.9.6.1 all OOTB modules from 7.9.2 | | | | StepA: export merged RPD to udml using following |
| should also be installed in addition to new SAs. | | | | syntax:nqudmlgen.exe -u Administrator -p |
| 2. Equalize repositories - when installing OBI apps, | | | | custompwd-r |
| oracle ships with map files that are requried to | | | | nalyticsApps.RPD -o |
| equialize the RPDs. These have two steps: | | | | C:OracleBIUpgrade04AfterManualWorkmerged.udml |
| StepA: Equalize 7961 to 792, command for this | | | | StepB: convert udml file back to RPD file using |
| is:equalizeRPDs -A Administrator -B SADMIN -C | | | | following command:nQUDMLExec -u Administrator -p |
| OracleBIAnalyticsApps792.RPD -D Administrator -E | | | | customRPD -i |
| SADMIN -F OracleBIAnalyticsApps7961.RPD -J | | | | C:OracleBIUpgrade04AfterManualWorkmerged.udml -o |
| rename792796new.map -O | | | | nalyticsApps1.RPD |
| oracleBIAnalyticsApps.RPD | | | | This will create the RPD back, except that it will not |
| StepB: Equalize CustomRPD to 792equalizeRPDs -A | | | | bring in objects that was causing unusual errors. |
| Administrator -B SADMIN -C | | | | StepC: Compare the new RPD with RPD that was |
| OracleBIAnalyticsApps792.RPD -D Administrator -E | | | | give unusual error. This should be able to point all |
| custompwd -F OracleBIAnalyticsAppscustom.RPD -J | | | | object which need to be fixed in order to proceed. |
| rename792796new.map -O | | | | 5. Once all errors and warnings are resolved, RPD is |
| customoracleBIAnalyticsApps.RPD | | | | ready for regression testing. Any errors there after will |
| 3. Next step is to use three way merge and create a | | | | need to be manually fixed. |
| new RPD. AdminTool has inbuilt merge option which | | | | I will be writing more as we achieve next phase of |
| will need to be used. Details of merge and other steps | | | | implementations. |