java.lang.Exception: No object were successfully created. This can be caused by any of the following: The OLAP Server is not running, The DBMS is not running, the DBMS is running on a diffe rent machine that the one specified, the name and password provided were incorrect.

Oracle Community | 1059384 | 1 year ago
tip
Do you know that we can give you better hits? Get more relevant results from Samebug’s stack trace search.
  1. 0

    Hyperion planning intermittently lsoing connection from Essbase

    Oracle Community | 1 year ago | 1059384
    java.lang.Exception: No object were successfully created. This can be caused by any of the following: The OLAP Server is not running, The DBMS is not running, the DBMS is running on a diffe rent machine that the one specified, the name and password provided were incorrect.

    Root Cause Analysis

    1. java.lang.Exception

      No object were successfully created. This can be caused by any of the following: The OLAP Server is not running, The DBMS is not running, the DBMS is running on a diffe rent machine that the one specified, the name and password provided were incorrect.

      at com.hyperion.planning.HspPool.getObject()
    2. com.hyperion.planning
      HspEssbasePool.getConnectionInternal
      1. com.hyperion.planning.HspPool.getObject(HspPool.java:147)
      2. com.hyperion.planning.olap.HspEssbasePool.getObject(HspEssbasePool.java:524)
      3. com.hyperion.planning.olap.HspEssbasePool.getConnectionInternal(HspEssbasePool.java:358)
      3 frames