If you have problems connecting to OLAP Metadata Catalog or to the external data source with Essbase Integration Services Console, review the following list of common problems:
Are you using the correct user name and password?
Does the user name you used have the correct privileges to access both OLAP Metadata Catalog and the data source at the database level?
If you are trying to connect to OLAP Metadata Catalog, did you use the same user name and password as the user who created the tables in OLAP Metadata Catalog?
If you create an OLAP Metadata Catalog when logged in as one user name, you cannot access the tables in OLAP Metadata Catalog using a different user name unless you create an alias for the user name (for Microsoft SQL Server) or synonyms for the tables (for IBM DB2 and Oracle).
Is the database client software installed and configured on the computer where Integration Server is installed?
Do the database client software utility programs, such as the command-line SQL utility, run? Can you connect to databases with them?
Does the user who starts Integration Server have the correct environment variables set and the necessary access privileges to run the database client software?
Are the required environment variables for the database client software, such as the path (and the library path on UNIX), configured on the computer where Integration Server is installed?
On UNIX, use ivtestlib (32-bit) or ddtestlib (64-bit) to confirm that the library path contains all files required by the open database connectivity (ODBC) driver.
ivtestlib is located in common/odbc/Merant/6.0/bin
ddtestlib is located in common/odbc64/Merant/6.0/bin
If necessary, is the bin directory for each database in the operating system path of the user who is running Integration Server?
Does the ODBC data source name (DSN) configuration identify the name of the data source client?
Are OLAP Metadata Catalog and the data source configured as ODBC data sources on the Integration Server computer? For information on configuring ODBC data sources, see Configuring Data Sources.
Are you using the ODBC data source names for OLAP Metadata Catalog and the data source databases as configured on the Integration Server computer? Do not assume that the data source database name is the same as the ODBC data source name for that database.
Are you experiencing time-out problems when connecting to the external data source?
Wait and retry the action when the data source is less busy. To avoid the problem, increase the ODBC driver time-out limit using ODBC Administrator on Windows systems. See the ODBC documentation.
Did you create tables in OLAP Metadata Catalog? For information on creating tables for the catalog, see Creating, Upgrading, and Deleting OLAP Metadata Catalogs.
Are you having problems related to ODBC while you are creating an Essbase outline? If so, turn on tracing, perform the action again, and analyze the results in the tracing log file. See Using ODBC Tracing on Windows Systems.
If you experience problems connecting to the data source, view the log for the data source for information about why the connection failed. See your data source documentation.
If none of the above steps help, review the list of database-specific problems in Database-Specific Problems.