About Me

Anjum Ara I am a technology enthusiast, an ardent reader. My latest interest is virtualization. In my free time, I love understanding child nutrition, child holistic development. I bake, read, paint, and do whatever it takes to improve myself every day.

Tuesday, June 23, 2020

Changing User PoV for all users in Financial Reports

We migrated applications from one server to another and noticed that in FR, the POV setting is not migrated via LCM.

If the change needs to be done for just one user this can be done from the Workspace. 
Go to Workspace > File > Preferences > Financial Reports and toggle the POV setting


This is cumbersome for hundreds of users. In order to change it for all users to follow the below steps
1. Go to E:\Oracle\Middleware\EPMSystem11R1\products\financialreporting\bin on the FR server or wherever you have installed the software
2. Edit the setInstance.cmd and set the EPM Instance home correctly



3. Launch the FRConfig.cmd > Mbeans >com.hyperion.reporting.HRprefs.previewuserpov and change the value to TRUE.





Restart the FR services. Validate if the POV setting has changed. 

In my case, it is done. 
Share:

Sunday, June 14, 2020

FDMEE Configuration Fails to create service in services panel



I have experienced this in more than 3 environments at different clients. I thought the first time it was just this server but repeatedly facing it made me realize its something from the OS that is missing.

I noticed there was ATL100.DLL missing. Copied it from the other servers as the Internet on client servers are generally blocked. This DLL is basically for Visual C++ 2010 Redistributable x86. In case you find it missing just install the Visual C++ and you are good to go.

In case, you do NOT have the Internet then go-ahead and copy from the server that has it. 
C:\Windows\System32\ATL100.dll and C:\Windows\Systemwow64\ATL100.dll
and redeploy FDMEE.



Share:

Wednesday, April 15, 2020

FCM Schema Migration

Post FCM schema migration the service won't start due to the Weblogic domain name. This value is stored in a table that needs an update.

Error:
<The logging last resource (LLR) data source accountreconciliation_datasource will not function when it is a participant in a global transaction that spans multiple WebLogic Server instances because remote JDBC support is disabled. LLR will function in single-server configurations.>
####<Apr 14, 2020 12:09:16 PM AST> <Critical> <JTA> <BEC12-ENCX-V357> <FinancialClose0> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000N5rwmI73Z7Qay_EgMG1U_Nqq000002> <1586855356559> <BEA-110482> <A logging last resource failed during initialization. The server cannot boot unless all configured logging last resources (LLRs) initialize. Failing reason:
weblogic.transaction.loggingresource.LoggingResourceException: java.sql.SQLException: JDBC LLR, table verify failed for table 'DEV1_FCM.WL_LLR_FINANCIALCLOSE0', row 'JDBC LLR Domain//Server' record had unexpected value 'Prod_EPMSystem//FinancialClose0' expected 'base_domain//FinancialClose0'*** ONLY the original domain and server that creates an LLR table may access it ***

weblogic.transaction.loggingresource.LoggingResourceException: java.sql.SQLException: JDBC LLR, table verify failed for table 'DEV1_FCM.WL_LLR_FINANCIALCLOSE0', row 'JDBC LLR Domain//Server' record had unexpected value 'Prod_EPMSystem//FinancialClose0' expected 'base_domain//FinancialClose0'*** ONLY the original domain and server that creates an LLR table may access it ***
at weblogic.jdbc.wrapper.JTSLoggableResourceImpl.recoverXARecords(JTSLoggableResourceImpl.java:248)
at weblogic.transaction.internal.ServerTransactionManagerImpl$RegisteredLoggingResourceTransactions.registerLoggingResourceTransactions(ServerTransactionManagerImpl.java:801)
at weblogic.transaction.internal.ServerTransactionManagerImpl.registerLoggingResourceTransactions(ServerTransactionManagerImpl.java:767)
at weblogic.jdbc.common.internal.RmiDataSource.recoverLoggingResourceTransactions(RmiDataSource.java:400)
at weblogic.jdbc.common.internal.DataSourceManager.createAndStartDataSource(DataSourceManager.java:146)
at weblogic.jdbc.common.internal.DataSourceManager.createAndStartDataSource(DataSourceManager.java:101)
at weblogic.jdbc.module.JDBCModule.activate(JDBCModule.java:385)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
at weblogic.application.internal.flow.DeploymentCallbackFlow


Solution:

Go to the <FCMSCHEMA>.WL_LLR_FINANCIALCLOSE0 table and update the value from the incorrect Weblogic Domain name to the correct one. The one from the destination server.Restart the FCM services.

Share:

Saturday, April 11, 2020

EPM 11.2.1 is out!




Downloading the files:
The version number still shows 11.2.0.0 on selecting the following components but do not fret over it click 'continue'. This will lead to the right version of the software i.e 11.2.1. 

The following are the components:

Oracle Enterprise Performance Management System - Client Installers 11.2.0.0.0
 Oracle Hyperion Financial Close Suite 11.2.0.0.0
 Oracle Enterprise Performance Management System - Oracle HTTP Server 11.2.0.0.0
 Oracle Data Integrator 12.2.1.3.0
 Oracle Hyperion Financial Data Quality Management, Enterprise Edition 11.2.0.0.0
 Oracle Enterprise Performance Management System - Part 1 - 6 11.2.0.0.0 
 Oracle Data Relationship Management 11.2.0.0.0

The download files do show the right version:



What’s new:
· These files can be used to install the latest version or update the previous version  11.2.0.0
·  Google Chrome is supported now. Microsoft Edge is also added to the list of supported browsers
· Officially supports Microsoft Windows 2016 OS
·  EPM System Installer has a new feature “Apply Update” to move from 11.2.0.0 to 11.2.1.0
 

Supported Paths to this Release
· Release 11.1.2.4
This is out of place migration.
· Release 11.2.0.0
In-place migration but this does NOT support a rollback yet so better keep all the backups handy.  No configuration required.







I will be upgrading the 11.2.0.0 watch out this space for further updates. 


Share:

Sunday, January 5, 2020

Registry Edit from the workspace is messy

Since registry edit is a job to be done carefully I prefer using the epmsys_registry utility in my black&white command prompt rather than the fancy UI.
This morning I decided let's edit from the front end as it was only about updating one single property for each component.
All the updates looked fine at first glance until I found that using notepad and updating the property may lead to incorrect values either added or removed from the existing registry.


Here is one example, I exported the components.property for LWA Workspace and updated just the isSSL=false property and imported it back without making any other changes.
Booooom!
I not only see a new entry but I also see that the value for ExtraTokenKey is incorrect now.




After Edit:




This is because of the settings on the notepad editor. I have tried all the ways possible to upload back with correct values but it does not change.


Hence sticking to the command prompt is the best thing:
Here are the sample commands:


epmsys_registry updateproperty #591e3add208ffef174b3659b1578e982994S7cbe/@isSSL false



Share: