+

Search Tips   |   Advanced Search

Troubleshoot database connection

A faulty JDBC driver or data source can prevent you from accessing a Connections application. To troubleshoot and correct these problems, test the database connections.

If we encounter an HTTP 500 - Internal Server Error when attempting to access a Connections application for the first time, ensure that we are using the correct web address. If the web address is correct and you still experience problems, continue with this task.

(Oracle only) Set the Statement cache size for the data sources on WAS to be no larger than 50. A higher value could lead to Out Of Memory errors on the application server instance.

To test a database connection:

  1. Log on to the WAS console of the dmgr and select...

  2. Check the values of the database name, server name, and port number.

    If we discover an error, change the incorrect value. Click OK and Save, and then retest the database connection.

  3. Select the check box for the application whose data source to test. Data source names:

      Activities activities
      Blogs blogs
      Communities communities
      Bookmarks dogear
      Files files
      Forums forums
      Home page homepage
      Metrics metrics
      Mobile mobile
      News news
      OAuth oauth provider
      Profiles profiles
      Search search
      Wikis wikis

  4. Click Test connection.

  5. If the connection fails, verify the JAAS Auth alias information is correct.

    1. Click a data source to review its settings.

    2. Click JAAS - J2C authentication data and then click the JAAS entry for the application. The JAAS entries are named :

        Activities activitiesJAASAuth
        Blogs blogsJAASAuth
        Communities communitiesJAASAuth
        Bookmarks dogearJAASAuth
        Files filesJAASAuth
        Forums forumJAASAuth
        Home page homepageJAASAuth
        Metrics metricsJAASAuth
        Mobile mobileJAASAuth
        News newsJAASAuth
        Profiles profilesJAASAuth
        Search searchJAASAuth
        Wikis wikisJAASAuth

    3. Make sure the ID in the user ID field is the same User ID that you provided during installation when we were asked to specify a user ID for the database connector.

      The user ID should be one of the following default IDs:

      Application DB2 database DB2 User ID Oracle database Oracle User ID SQL Server database SQL Server User ID
      Activities OPNACT lcuser ORCL ACTIVITIES OPNACT OAUSER
      Blogs BLOGS lcuser ORCL BLOGS BLOGS BLOGSUSER
      Communities SNCOMM lcuser ORCL SNCOMMUSER SNCOMM SNCOMMUSER
      Dogear DOGEAR lcuser ORCL DOGEARUSER DOGEAR DOGEARUSER
      Files FILES lcuser ORCL FILESUSER FILES FILESUSER
      Forums FORUM lcuser ORCL DFUSER FORUM DFUSER
      Home page HOMEPAGE lcuser ORCL HOMEPAGE HOMEPAGE HOMEPAGEUSER
      Metrics METRICS lcuser ORCL METRICSUSER METRICS METRICSUSER
      Mobile MOBILE lcuser ORCL MOBILEUSER MOBILE MOBILEUSER
      News HOMEPAGE lcuser ORCL HOMEPAGE HOMEPAGE HOMEPAGEUSER
      Profiles PEOPLEDB lcuser ORCL PROFUSER PEOPLEDB PROFUSER
      Search HOMEPAGE lcuser ORCL HOMEPAGE HOMEPAGE HOMEPAGEUSER
      Wikis WIKIS lcuser ORCL WIKISUSER WIKIS WIKISUSER

      Consider reentering the password to verify the value specified at installation is correct.

    4. After applying any changes, click OK. Return to the data source properties page, and then click Test connection.

  6. If the connection fails again, verify the JDBC driver library location information is being detected by WebSphere Application Server.

    1. From the Integrated Solution Console navigation bar, expand Environment, and then click WebSphere Variables.

    2. Scroll down the list to find the database location variable. The variables are named :

      • Activities: ACTIVITIES_JDBC_DRIVER_HOME
      • Blogs: BLOGS_JDBC_DRIVER_HOME
      • Communities: COMMUNITIES_JDBC_DRIVER_HOME
      • Dogear: DOGEAR_JDBC_DRIVER_HOME
      • Files: FILES_JDBC_DRIVER_HOME
      • Forums: FORUMS_JDBC_DRIVER_HOME
      • Home page: HOMEPAGE_JDBC_DRIVER_HOME
      • Metrics: MOBILE_JDBC_DRIVER_HOME
      • Mobile: NEWS_JDBC_DRIVER_HOME
      • News: NEWS_JDBC_DRIVER_HOME
      • Profiles: PROFILES_JDBC_DRIVER_HOME
      • Search: SEARCH_JDBC_DRIVER_HOME
      • Wikis: WIKIS_JDBC_DRIVER_HOME

    3. Ensure the corresponding file path in the Value column is the same file path specified in the JDBC driver library field when we ran the installation wizard. For example:

        C:\IBM\DB2\SQLLIB\java

      If the file path is incorrect, click the variable name and edit the file path in the Value field.

    4. Select JDBC > Data sources to return to the data source. Select the check box next to the data source, and then click Test connection.


Parent topic:
Troubleshooting tips

Related reference:

Search error messages