Monday, 2 September 2024

Cannot execute maxl statement. Essbase Error (1200448): [For Input string: "0,00"]

Cannot execute maxl statement.  Essbase Error (1200448): [For Input string: "0,00"]

Essbase 21c (EPM 11.2.18)

Error with a smartview Shared connection:



"Cannot execute maxl statement.  Essbase Error (1200448): [For Input string: "0,00"]

Do you want to connect with username/password?"

 

This cannot be use to create a private connection nor can a private connection be created manually

Cause:  Non-English install on Essbase/EPM Server

Fix:

Navigate to ..\Oracle\Middleware\user_projects\domains\essbase_domain\bin
 

Take backup and Edit file setDomainEnv.cmd


Add the parameter "-Duser.language=en" under EXTRA_JAVA_PROPERTIES:


set EXTRA_JAVA_PROPERTIES=-Duser.language=en -Djavax.management.builder.initial=weblogic.management.jmx.mbeanserver.WLSMBeanServerBuilder %EXTRA_JAVA_PROPERTIES%




Wednesday, 26 October 2022

EPM 11.2.11 - Version Palindrome

EPM 11.2.11 was relesed this week, highlights of which are: 

  • Certification of Essbase 21c (Version 21.4.0, Windows and Linux).
  • Java 8 Update 341
  • WebLogic Patch Set Update 12.2.1.4.220711.
  • Fusion Middleware (FMW) Third Party Bundle Patch Set Update 12.2.1.4.220616
  • OHS Patch Set Update 12.2.1.4.220608
  • There are no April/July patches for ODI in Release 11.2.11
  • Added a new System Settings option Workbench Export to File Format to export .XLS and .CSV files in FDMEE

    On Windows Server this is applied in the same way  that was done for the previous .9 and/or .10 releases from Powershell

    Command :  .\ApplyUpdate.ps1 <MIDDLEWARE_HOME>

    It might be worth mentioning here that you may need to run the following in order to bypass Powershell's default execution policy (run if you get anything returned about digitial signature policies)


    Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass


Wednesday, 27 April 2022

EPM 11.2.9 - The Final Frontier?

EPM 11.2.9 was dropped in the Software Delivery Cloud a few hours ago.

Here's some interesting excerpts from the readme:

1) No more maintenence releases for EPM?



This would suggest that 11.2.9 will be the last 11.2.x release and we'll go back to the OPatch method for updating...this may be a relief for some but a headache for others...

2) You can only apply to 11.2.8

It was good that 11.2.8 could be applied to anything from 11.2.2 or above.  This now means that if you're below 11.2.8, updating could be a two stage process or maybe even three...

3) Essbase, FMW and Java updates

I'll list them anyway:

  • Essbase Release 11.1.2.4.047
  • Java 8 Update 321 
  • WebLogic Patch Set Update 12.2.1.4.220105
  • ADF Bundle Patch 12.2.1.4.211221

No mention of any new functionality, even the CFO on Apex doesn't mention 11.2.9

https://apexapps.oracle.com/pls/apex/f?p=20620:1:0

4) OPatch updates are applied using 'ApplyUpdate' 

Note that ApplyUpdate has the .ps1 extension.  If you're applying from Windows then this is done via Powershell, which seems to be the first time this has been part of updating EPM. Nice that it does the lot in one go!

From this, I get the impression that 11.2.9 could well be the final EPM OP release.  Please prepare to update via OPatch for the next 9 years or so

I have an upgrade planned after the May Bank holiday, I'll let you know how I get on



Friday, 1 April 2022

FDMEE Integration to Oracle Cloud Financials with a Web Proxy

 

This works out off the box in the 11.2.x release but there's a few things to do if your web traffic is routed through a proxy.

In FDMEE add Select Source System, add Type 'Oracle Financials Cloud' and enter a Name/Desctiption

ODI Context Code 'GLOBAL'

 

 

Save and then hit 'Configure Source Connection'

Enter the URL in the format below plus username and password (must be a native user in OFC)

https://fusion-name.fa.ocs.oraclecloud.com/publicFinancialCommonErpIntegration/ErpIntegrationService?WSDL

 

Hit 'Test Connection':


Ouch....

Check the process log and you may find a similar error

INFO  [AIF]: Standard Error: javax.xml.ws.WebServiceException: Failed to access the WSDL at: https://fusion-name.fa.ocs.oraclecloud.com/publicFinancialCommonErpIntegration/ErpIntegrationService?WSDL. It failed with:
Connection timed out: connect.

The connect timed out error may indicate that your web traffic goes through a proxy.

Here's the fix on the FDMEE Server:

1) Navigate to ..\Oracle\Middleware\user_projects\epmsystem1\bin\deploymentscripts

Edit File setCustomParamErpIntegrator.bat 

a) Add the following options to the JAVA_OPTIONS section:

-Dhttps.proxyHost=<Proxy Server> -Dhttps.proxyPort=<Proxy Port>

 b) If it's a Windows server, add two more JVMOptions to the Windows registry.

First you must update the JVMOptionCount and increase the decimal value by 2.

Then add new keys:

Example:

JVMOption51       -Dhttps.proxyHost=<Proxy Server>

JVMOption52       -Dhttps.proxyPort=<Proxy Port>

 

2) Navigate to ..\Oracle\Middleware\EPMSystem11R1\products\FinancialDataQuality\bin\FusionCloud

Edit file FusionCloudAdapter.bat

a) Update the Proxy Server/Port details:

set customProxyHost=<server name>
set customProxyPort=<port>

b) Update JAVA_OPTS to remove the quotation mark ( " )

 set JAVA_OPTS="-DEPM_ORACLE_HOME=%EPM_ORACLE_HOME% -DEPM_ORACLE_INSTANCE=%EPM_ORACLE_INSTANCE% -Dhttps.proxyHost=%customProxyHost% -Dhttps.proxyPort=%customProxyPort% -Dweblogic.security.SSL.ignoreHostnameVerification=true"

to

 set JAVA_OPTS=-DEPM_ORACLE_HOME=%EPM_ORACLE_HOME% -DEPM_ORACLE_INSTANCE=%EPM_ORACLE_INSTANCE% -Dhttps.proxyHost=%customProxyHost% -Dhttps.proxyPort=%customProxyPort% -Dweblogic.security.SSL.ignoreHostnameVerification=true

Restart The FDMEE Service.

Hit the Test Connection again.

Lovely....

Note if you are using the 11.1.2.4 release you will need to update to a later version of Java as the one shipped with this release does not support TLS 1.2 or higher of which OFC uses versions 1.2 and 1.3 (Details on how to do this  in Doc ID 2351499.1).  

An indication of this would also be in the process log:

INFO  [AIF]: Standard Error: javax.xml.ws.WebServiceException: Failed to access the WSDL at: https://fusion-name.fa.ocs.oraclecloud.com/publicFinancialCommonErpIntegration/ErpIntegrationService?WSDL. It failed with: Received fatal alert: protocol_version.
 


 

Tuesday, 22 March 2022

FDMEE to Cloud Integration in 11.2.x

 FDMEE to Cloud Integration in 11.2.x

 

The instructions for FDMEE On-Prem to Cloud (PBCS, FCCS) in the 11.2.x readme are based on the method for 11.1.2.4 as it contains references to the v10 release of Weblogic and a specific jdk version.   While this could be pretty simple for the tech savvy to interpret to WebLogic 12c etc. this might save you some time.

First get the certificate from the target PBCS/FCCS Pod.  In Firefox for example:

Click the padlock -> Connection Secure -> More information




Click PEM (cert) and save under D:\Oracle\PBCSCert as pbcs.crt

Run the command prompt as 'Administrator': 

cd D:\Oracle\Middleware\wlserver\server\lib

D:\Oracle\Middleware\jdk\jre\bin\keytool -importcert -keystore DemoTrust.jks -storepass DemoTrustKeyStorePassPhrase -file D:\Oracle\PBCSCert\pbcs.crt -alias "planning-xxxxxx.pbcs.em3"

Where xxxxxx is the target pod id domain:

Note, this is the entry from the 11.2.8 FDMEE Read me (section 3-62) which is based on 11.1.2.4. The items in red are where it differs in 11.2 as the installer does not label the Weblogic or jdk versions (11.2.8)

At a command prompt, type: cd
C:\Oracle\Middleware\wlserver_10.3\server\lib.
b. Type: C:\Oracle\Middleware\jdk1.8.0_181\jre\bin\keytool -importcert -
keystore DemoTrust.jks -storepass DemoTrustKeyStorePassPhrase -file
c:/temp/pbcs.crt -alias "pbcs_pod_name"

Using the WebLogic Admin Console, modify two WLS SSL settings.

a. Login to the WebLogic Admin Console.

b. Select Lock and Edit.

c. Select Servers, and then ErpIntegrator0.

d. Select SSL and then expand Advanced. - Ignore, see below

e. Enable JSEE SSL. – not in WebLogic 12c as it uses JSEE by default and there is no option to select it

f. In Hostname Verification, select Customer Hostname Verifier.

g. In Custom Hostname Verifier, enter:

weblogic.security.utils.SSLWLSWildcardHostnameVerifier.


h. Save and activate changes.

FDMEE Target application creation (Cloud) - enter the pod details:

 

Save

Hit 'Refresh Members' and you should be good to go!

Cannot execute maxl statement. Essbase Error (1200448): [For Input string: "0,00"]

Cannot execute maxl statement.  Essbase Error (1200448): [For Input string: "0,00"] Essbase 21c (EPM 11.2.18) Error with a smartvi...