To correct problems connecting to the data source from Integration Server, investigate the following possible causes:
Is Integration Server installed? Are all the required Integration Server components installed?
The following components must be installed to have a functional instance of Integration Server:
Is Integration Server running? Is it configured properly?
Start Integration Server by opening a command prompt window and typing olapisvr .
If Integration Server does not start, review the following possible problems:
Are the required environment variables set? Are they set for the correct user name?
On Windows systems, if you decide not to enable the setup program to update environment variables automatically, you must update the variables manually.
On UNIX systems, a script file (is.sh or is.csh) that sets environment variables must be included in the login script of the user who starts Integration Server.
What release of Essbase is installed?
If an incompatible version of Essbase is installed on the same computer as Integration Server and the \essbase\bin directory is in the current path, Integration Server does not start. For information on compatible versions of Essbase, see the Oracle Hyperion Enterprise Performance Management System Installation Start Here.
Integration Server uses port 3388 to communicate with the Integration Services client software. If this port is being used by another program, Integration Server does not start.
On UNIX, is more than one copy of olapisvr running? If so, all servers except one will hang indefinitely. To correct the problem, run the following command to display all programs that are currently running:
ps -fe | grep olapisvr
Many of the problems related to Integration Server not working properly may be traced to configuration steps that you may have missed. See the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide.