Connection problems

If BladeManager fails to connect to a database or drops a database connection, perform the following tasks before you call Software Support:
  • Check whether BladeManager connects to some databases but not to others.

    You might not have sufficient permissions to work on the databases to which you cannot connect.

    Informix® software can be managed most easily when a single, default user in an environment with full permissions creates databases and registers DataBlade® modules. Using a variety of permissions might cause some services to be denied, for security reasons.

  • Check whether the operation that fails works correctly if a user with full permissions performs all the steps.
  • Check whether BladeManager connects to databases in one GLS locale, but not in others.

    If your database and client are not connected in their respective default locales, try setting the DB_LOCALE and CLIENT_LOCALE environment variables to no locale (the default) and reconnecting to the database.

  • Check the database server log file for errors. You might have to ask your database administrator for the location of the server log.
  • Check whether the $INFORMIXDIR/extend and $INFORMIXDIR/extend/ifxmgr directories are deleted. If these directories no longer exist, reinstall your database server.
  • On UNIX™, check whether there are symbolic links to the $INFORMIXDIR/extend and $INFORMIXDIR/extend/ifxmgr directories. If there are symbolic links, reinstall your database server into a directory without symbolic links.
  • Check whether the connection problem is unique to BladeManager:
    • Check whether you have resource permissions by trying to create a table. If you cannot create a table, you do not have resource permissions: have your database administrator assign you permissions.
    • On UNIX, check whether you can connect to the same database using DB-Access. If you cannot, consult your database administrator.
    • On Windows™, check whether you can connect to the same database using a client tool, such as SQL Editor or Schema Knowledge.

      If not, check your settings in Setnet32 or consult your database administrator. If you can connect with SQL Editor, but not Schema Knowledge, you might have a problem with a high-level Informix API.

  • Check the values specified for the DB_LIBRARY_PATH configuration parameter in the onconfig file. The DB_LIBRARY_PATH configuration parameter should include the $INFORMIXDIR/extend directory for DataBlade modules.
  • Check if the server is configured so that the EXTEND role is needed to add UDRs and UDTs. If that is the case, you must be granted the EXTEND role by a DBSA (by default, user informix).

If you had recently installed other software when you began experiencing problems with BladeManager, you might have overwritten a DLL required by BladeManager. See if reinstalling BladeManager solves the problem.

If you are still experiencing problems, contact Software Support.