Calculation Manager Rules that are still on Planning don't show up on Calculation Manager

In my 11.1.2.3.500 setup, I recently faced an issue with Calculation Manager Rules that were present on Planning forms inside the Planning Application, but however, on expanding the Calculation Manager->Planning App->Plan Type->Rules, it did not display the rules inside. These rules were imported manually earlier and suddenly disappeared. I could not really find what caused it but here are the steps to recover the BR's from planning tables to calculation manager:

1. Access the appropriate Planning application repository and its table HSP_CALC_MGR_RULES

2. Create a new text file with following content

3. Copy the contents in the Body column of the HSP_CALC_MGR_RULES table and paste its contents between the tag in the file created in step 2.
4. Save file as XML file
5. Within the Calculation Manager navigate to “File” -> “Import…” to import the Business Rule into Calculation Manager .

Using this I could restore all the rules back.

"Error executing query: -1" When Running Financial Reporting (FR) Reports

When we performed the migration to 11.1.2.3 since it was a new install some of the reports failed with the error "Error executing query:-1" .In addition to this a lot of the missing values were also being generated as a result. To resolve this issue, We had applied a fix in the previous environment as this issue seemed to exist there as well. We found out that this was due to the MDX query setting on FR Server and it was set to the default 'True' value. To carry out the same, follow the steps below.

1. Navigate to C:\Oracle\Middleware\EPMSystem11R1\products\financialreporting\bin and launch FRConfig.cmd

In some instances, this utility doesn't open and throws a java error. To fix that, follow step 2 below.

2. Edit setInstance.cmd and add the

set EPM_ORACLE_INSTANCE=C:\Oracle\Middleware\user_projects\epmsystem1

3. Now, it opens the FRConfig.cmd. In the MBeans tab, expand the Financial Reporting tab and scroll to the EssbaseUseMDX setting.

4. Restart FR services. This should fix the issue. 

I had found that on a parallel environment since it had loopback adapters present for the VIP, It did not work out for me. In that case, launch the enterprise manager module and correct it from there.Click on System MBean Browser.

Navigate to the Application MBeans

Also a side note, PreviewUserPOV can be set to True, so that end users don't have to set their FR Preferences to On. We can make the change on FRStudio.cmd

BI+ distributed setup "startup document does not exist " "GSM unable to acquire LSM"

We have a network deployment for Foundation and BI+ in our environment and the 2nd node when operated on its own stopped being accessible. RAF agent service kept going to "stopping" mode when stopped and not completely stopped. The RAF Agent service and the Foundation Service was set to the installer account.

I thought it will be a good idea to compile a few things I verified in the hopes that it will help anyone with some troubleshooting ideas.

Ensure to set HyS9RaFrameworkAgent_epmsystem1 service to start with Domain account instead of Local System on both RAF servers and also make sure the domain account has local administrator rights .

Before starting services on Server2 make sure server1 is up and running and Workspace is accessible

Verify that HAVA ID in EPM registry matched in css_provisioning_info table

1: Execute the following query against the Shared Services registry database:
2: select application_id from css_provisioning_info where lower(application_id) like 'hava%';
o note this application id, e.g. HAVA:0000012b3072bf63-0000-6717-0acc1bac

3: Run epmsys_registry.bat from \Oracle\Middleware\user_projects\epmsystem1\bin
Open EPM registry.xml and search for HAVA and compare the HAVA ID using the ID above

4: If there is a mismatch, edit the Shared Services Registry:
Go to EPM_ORACLE_INSTANCE/bin and run the following command:
epmsys_registry updateproperty RA_FRAMEWORK/@applicationId

Where applicationId is the id returned from the query above. For example, using the id above:

epmsys_registry updateproperty RA_FRAMEWORK/@applicationId HAVA: 0000012b3072bf63-0000-6717-0acc1bac

5. Restart all services on Server1 and ensure Shared Services and Workspace are accessible

6: Enable the Service Broker service and the GSM on the second server
- Log on to EPM Workspace on Server1
- Select Navigate, then Reporting and Analysis, and then Services.
- Right-click Reporting and Analysis for server2 , and then select Properties.
- On the Services tab, set GSM to Enabled (Yes) and Service Broker to Enable (Yes).

Reproduce the issue and attach the logs from these locations from both servers 1/2
- \Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\ReportingAnalysis

and run epmsys_registry.bat from \Oracle\Middleware\user_projects\epmsystem1\bin
For my issue however, everything seemed to tie up quite nicely and I was still running into the issue.
This was the log entry from the server 2  raframework_stdout_console.log when started on its own:

Finally, when I started digging a little deeper, I could understand what was causing this to happen.
While Configuring the RAF for the 2nd node, We normally point to the shared server 1 RM1 directory while configuring.

The second Workspace agent was not able to locate the RM1 directory on server 1 .An issue with DNS could not resolve the server 1 hostname correctly.On second Workspace Agent server, add the server 1 hostname/IP address into the HOSTS file

On server 2, update the hosts file (which is under C:/Windows/System32/etc/drivers/hosts folder) with the ipaddress and the hostname of server1 where RM1 directory stored.
xx.xx.xx.xx server1.domain.com

This helped in resolving the issue.

.

Merge Cells Issue on Workspace Report

We have users that run the reporting out of Workspace and then export into Excel. Historically , The reports were formatted the same between Workspace and Smart View so you could easily pull from either and end up with consistent reporting.

Since the upgrade to 11.1.2.3, It appeared the new Workspace reports are no longer formatted the same. They had merged cells.


To fix the issue,

1. On your FR server, navigate to Oracle\Middleware\user_projects\epmsystem1\FinancialReporting\lib\FOProcessor
2. Save a copy of the existing xdo.cfg file.
3. Open xdo.cfg in a text editor.
4. Toward the top of the file, locate this line:

5. Immediately below it (above the
tag), add this line:


6. Save the file.
7. Restart the FR Web service (wait a few minutes to allow the service to fully render).