Resolving EPM Automate Issues

This section lists common issues that you may encounter while using EPM Automate and how to resolve them.

Resolving session failures if the environment is configured for SSO with an identity provider

The EPM Automate does not work with SSO (identity provider) credentials that you use to access Oracle Enterprise Performance Management Cloud or Oracle Smart View for Office.

If the service is configured for SSO, an Identity Domain Administrator must enable EPM Automate users to sign in with their identity domain credentials.

See Ensuring that Users Can Run EPM Cloud Utilities After Configuring SSO.

Also, see "Enabling Sign In With Identity Domain Credentials" in Administering Oracle Cloud Identity Management.

Resolving script execution failures after changing EPM Cloud password

You will receive periodic password expiry warnings from after changing your EPM Cloud password, EPM Cloud credentials are required to run EPM Cloud. Scripts that use EPM Cloud credentials will fail to run after you update identity domain password.

If you use an encrypted password file to run scrips, update your password encryption file to reflect the new password. See the encrypt command in EPM Automate Commands in Working with EPM Automate for Oracle Enterprise Performance Management Cloud for command usage and examples. If you use plain text passwords in scripts, be sure to update them.

Resolving EPMAT-11 Internal Server Error, Connection timed out

This error is displayed if a connection cannot be established because of a bad URL or invalid proxy settings on the computer.

  • Verify that you are using a valid URL

  • If your organization requires the use of a proxy server to connect to the internet, verify that the proxy setting in Internet Explorer is accurate.

    If your proxy settings require you to authenticate with the proxy server, then you must enter the proxy server domain, user name, and password as parameters to the login command. Contact your network administrator for help with proxy server domain name and credentials. See the login command in "Working with EPM Automate for Oracle Enterprise Performance Management Cloud" for usage information and examples.

Resolving EPMAT-11: Unable to connect to URL error when connecting from a Linux machine

This error can occur if proxy settings are not specified in environment variables.

On Linux computers, verify that the following environment variables are set. The utility looks for the value of these variable to determine proxy settings:

  • proxyHost

  • proxyPort

  • https.proxyHost

  • https.proxyPort

Handling login failures after switching networks

After you switch from one network to another, initial EPM Automate login attempt fails because of the change in the MAC address of the client machine. For example, this failure occurs at your first login attempt after you switch from a wifi connection to a LAN connection.

To resolve this error, sign in again to make EPM Automate use the current MAC address.

Getting Help

If your issue persists after trying the preceding tips, seek help from Oracle Support. See Getting Help From Oracle.

Submit the following:

  • A log file of the failed EPM Automate command. You can generate a log file specifying the -d at the end of the command; for example epmautomate listfiles -d. The log file is created in the directory from which the command is run.
  • A Provide Feedback submission. See Creating a Provide Feedback Submission.
  • A service request that identifies the Provide Feedback reference number. See Submitting a Service Request.