Planning DB Deploy aborts since "No baseline was found for transaction ID 8

Question

Not sure if this is a bug or something we caused on our end but we cannot deploy a planning database anymore. We get the message: Deploy aborted since "No baseline was found for transaction ID 85905". This happens during the export phase. We are using EPM Architect with Planning 11.1.1.10.
Curious if anyone else has ever run into this error.
Thanks,
Jeff Brown

Answer 1

We ran into a similar issue yesterday, except the transaction ID in the ds_baseline_library was greater than any transaction ID's in the or_object table.
Here's what Oracle thinks happened:
Baseline records were likely to be deleted by a baseline cleanup kicking in during application deployment. Normally, the cleanup only deletes older baselines but causes problems if run while an application is deployed.
We don't believe this is what happened as the cleanup was scheduled to run at 3:00am, so who knows what really happened. Here is the guidance we received in terms of resolving the issue (we didn't follow this, but I suspect it would work):
From your update it is clear that EPMA still looks for the same baseline records which apparently do not exist anymore.
The steps below should bring this to work.
1. Create backup of the Planning application database.
2. Create backup of the Essbase data, Calculation scripts, rule files, substitution variables.
3. Delete the affected Planning application in EPMA (this should delete it in Planning and Essbase as well).
4. Create a classic Planning application with same name as the deleted application.
5. Override the classic Planning application database (step 4) by using the Planning application database backup (step 1).
6. Using an administrator user, log into the Planning application and navigate to Administration > Manage Properties.
7. On the “Application Properties” tab, click “Add” and enter a new property “EDIT_DIM_ENABLED” with a value of “true”. Click “Save” at the bottom of the page.
8. Once you have completed steps 6 and 7, restart the Planning service.
9. Log into the Workspace and Navigate > Administer > Application Upgrade. This upgrade wizard should list the newly created classic Planning application as “Upgradeable”. Select the application and upgrade it as local dimensions.
10. The application should now be visible in the EPMA application library and its dimensions loaded as local dimensions.
11. Use EPMA to deploy the newly created Planning application.
12. Restore the Essbase data, Calculation scripts, rule files, substitution variables.
Here's what we did:
1) Export our forms.
2) Copy the app in EPMA.
3) Deploy the new app just to make sure it works.
4) Delete the old app in EPMA.
5) Copy our "copy" to the original app and re-deploy.
6) Import our forms.
We lost a few items with this approach (business rules and variables), but we hadn't developed much yet. We felt this was cleaner than copying a repository into a Classic app and then upgrading that app to EPMA. Either way, we're back iin business. FYI - it looks as though this issue may be fixed in 11.1.1.2. In the release notes, under fixed defects, check out defect # 7573567. Sounds like this is the same problem.