Hyperion Infrastructure Technology

Issue: Essbase Application Creation Fails with Fatal Error on Oracle ADB 19

Workaround: To resolve the issue,

  1. Use Secure Shell (SSH) to connect to the server with the user account that installed and configured Essbase.
  2. Create the folder "dbwallet"
    $ mkdir /MIDDLEWARE_HOME/oracle_common/dbwallet
    
  3. Create a Wallet using the command below:
    $ MIDDLEWARE_HOME/oracle_common/bin/orapki wallet create -wallet "Wallet_location" -pwd <wallet_password> -auto_login_local
    
  4. Import DB Certificates to Wallet:
    $ MIDDLEWARE_HOME/oracle_common/bin/orakpki wallet add -wallet wallet_location -trusted_cert -cert certificate_location -pwd <wallet_password>
    
    $ MIDDLEWARE_HOME/oracle_common/bin/orakpki wallet add -wallet wallet_location -trusted_cert -cert certificate_location -pwd <wallet_password>
    
    $ MIDDLEWARE_HOME/oracle_common/bin/orakpki wallet add -wallet wallet_location -trusted_cert -cert certificate_location -pwd <wallet_password>
    
  5. Create sqlnet.ora file under
    $ MIDDLEWARE_HOME/network/admin
  6. Add the following entries in sqlnet.ora:
    NAMES.DIRECTORY_PATH= (TNSNAMES, EZCONNECT)
    SQLNET.AUTHENTICATION_SERVICES= (BEQ, TCPS, NTS)
    SSL_VERSION = 0
    SSL_CLIENT_AUTHENTICATION = FALSE
    sqlnet.encryption_server=REQUIRED
    sqlnet.encryption_types_server=(RC4_256,AES256,AES192,3DES168,RC4_128,AES128,3DES112,RC4_56,DES,RC4_40)
    sqlnet.crypto_checksum_server=REQUIRED
    sqlnet.crypto_checksum_types_server=(MD5)
    
    WALLET_LOCATION =(SOURCE =(METHOD = FILE)(METHOD_DATA = (DIRECTORY = $MIDDLEWARE_HOME/dbwallet)))
See Doc ID 2772035.1.

Issue: Unable to log into Essbase JET UI after upgrading to 11.2.15

Workaround: This behavior is expected, as JET UI is not accessible on APS servers. APS-specific properties can be modified directly on the same instance without using JET UI.

Issue:

  • Config Tool does not set up Oracle HTTP Server (OHS) with Essbase aliases.

  • EAS unaccessible on Oracle HTTP Server (OHS) port.

Workaround: Update the mod_wl_ohs.conf file.

Using a text editor, open mod_wl_ohs.conf file located under this folder:

EPM_ORACLE_INSTANCE/httpConfig/ohs/config/fmwconfig/components/OHS/ohs_component and add the following aliases:
<LocationMatch ^/essbase>
   SetHandler weblogic-handler
   WeblogicCluster essbaseServer1:9010,essbaseServer2:9010
</LocationMatch>
<LocationMatch ^/aps>
   SetHandler weblogic-handler
   WeblogicCluster essbaseServer1:9010,essbaseServer2:9010
</LocationMatch>
<LocationMatch ^/eas>
   SetHandler weblogic-handler
   WeblogicCluster essbaseServer1:9110
</LocationMatch>
<LocationMatch ^/easconsole>
   SetHandler weblogic-handler
   WeblogicCluster essbaseServer1:9110
</LocationMatch>

Issue: Upgrade to EPM 11.2.15 : Essbase Configuration Failed due to "temp" Space Issues

Workaround: See Solution - Upgrade to EPM 11.2.15 : Essbase Configuration Failed due to "temp" space issues to resolve this issue.