DataBlade Module Installation and Registration Guide
chapter_name
Home
Contents
Index
Master Index
New Book
Troubleshooting Registration Problems
This appendix describes problems you may experience when registering a DataBlade module, possible solutions, and information you should supply when contacting Informix Technical Support.
Connection Problems
If BladeManager fails to connect to a database or drops a database connection, perform the following tasks before calling Informix Technical Support:
Check whether BladeManager connects to some databases but not to others.
You may not have sufficient permissions to work on the databases to which you cannot connect.
Informix software works most easily when a single, default user in an environment with full permissions creates databases and registers DataBlade modules. Using a variety of permissions may 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 may have to ask your database administrator for the location of the server log.
Check whether the connection problem is unique to BladeManager:
1. 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.
2. If you have recently installed both the Database Administrator's Kit and the DataBlade Developers Kit on your computer, you may have overwritten a
DLL
required by BladeManager. Try to reinstall the DataBlade Developers Kit, or contact Informix technical support.
3.
UNIX
Check whether you can connect to the same database using
DB
-Access. If you cannot, consult your database administrator.
Windows
Check whether you can connect to the same database using
SQL
Editor and 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 may have a problem with a high-level Informix API.
4. Check whether the
$INFORMIXDIR
/extend
and
$INFORMIXDIR
/extend/ifxmgr
directories are deleted. If these directories no longer exist, reinstall Informix Dynamic Server.
5.
UNIX
Check whether there are symbolic links to the
$INFORMIXDIR
/extend
and
$INFORMIXDIR
/extend/ifxmgr
directories. If there are symbolic links, then reinstall Informix Dynamic Server into a directory without symbolic links.
6. If you are still experiencing problems, contact Informix Technical Support.
Preparation Failure
If you receive a preparation failure error after BladeManager connects to the database, then complete the following tasks:
Create a new database and connect to it with BladeManager using the same login. If preparation does not fail, you may have a permissions problem in the original database; contact your database administrator.
Check the BladeManager logs for the preparation log:
If you do not find a preparation log, check the database server log to see if a thread failed during preparation.
Check the preparation log for "unexpected error" entries. You might be able to correct some errors (for example, if the database server ran out of disk space); otherwise, consult your database administrator about the error.
Check whether the
$INFORMIXDIR
/extend
and
$INFORMIXDIR
/extend/ifxmgr
directories are deleted. If these directories no longer exist, reinstall Informix Dynamic Server.
UNIX
Check whether there are symbolic links to the
$INFORMIXDIR
/extend
and
$INFORMIXDIR
/extend/ifxmgr
directories. If there are symbolic links, then reinstall Informix Dynamic Server into a directory without symbolic links.
Registration Problems
If BladeManager fails to register, unregister, or upgrade a DataBlade module, perform the following tasks:
Check the log that BladeManager generated for the operation. If the log has an "unexpected error" entry, then send the details from the log to the vendor of the DataBlade module.
Try to register other DataBlade modules: for instance, the DataBlade modules that ship with the database server. If you can register another DataBlade module, then your problem is probably specific to the DataBlade module that failed. Read the release notes for the that DataBlade module; some modules have special requirements, such as a named sbspace.
DataBlade Module Installation and Registration Guide
, version 3.6
Copyright © 1998, Informix Software, Inc. All rights reserved.
