Sometimes you may run into problems
on a Solaris, Linux or AIX system that stem from an environment that has
not been initialized.
To iinitialize the DB2 execution environment
use the following command:
To find the value of the DB2INSTANCE
On Unix: env|grep DB2
On Windows: type set | find "DB2"
in a command prompt
To verify the port in use for the db2
instance (valid on all OS):
Unix: "db2 get dbm cfg" from
the instance id
Windows: use a DB2 command window
Log files are located in a "log"
directory underneath that the install directory.
Each install step will has a "*cmd.txt"
file and will produce a "*stdout.txt" and
a "*stderr.txt" files. If
ActiveInsight is installed into /opt/IBM/ActiveInsight, the log
file will be /opt/IBM/ActiveInsight/log.
When an error is encountered, it is
possible to pause the install and or the uninstall, fix the error and run
the failed command again manually. The failing command can be found
in the cmd.txt file for the current install step. After the error
has been fixed and the failing step has completed successfully, then you
can continue the install or uninstall.
ERROR: "unable to attach
to specified instance"
SOLUTION: The DB2INSTANCE variable
is set in the db2profile which should be run
before attempting the install. In addition
the root user must be in the
same group as the db2 instance.
By default this is 'db2grp1' but may
be different at your site. The
/etc/group file will show
this. If missing you can either edit
this file directly or use whatever
user management utilities are on their
server to change this.
The root user needs to be in the same
group as the DB2
instance, i.e. in the same unix group,
so that it can run the scripts
which start the database manager and
run db2 commands.
In order for the root user to be able
to run db2cmd and execute the
commands listed in the DDL file, it
must be authorized. On Unix and
Linux systems, we do this by adding
root to the same group as the DB2
instance being used.
ERROR: Portal won't start after
SOLUTION: This is usually because
the Portal cannot access the database. Determine the reason why the
DB2 instance was not successfully started.
Fix the error so that the DB2 instance
will start. Once the DB2 instance is accessible to the Portal, the
Portal will start.
If you have paused the install of Lotus
Activeinsight, you can continue it at this point.
An error occurred during configuration
of ActiveInsight properties.
Refer to the log files listed below
Press 1 for Next, 3 to Cancel or
4 to Redisplay 
SOLUTION: At that point, manually
update the file
Add a line at the bottom of the file
that identifies the Portal admin
ERROR: not enough disk space
SOLUTION: If you have made several
attempts to install Lotus Activeinisght and have not properly uninstalled
you may not have enough disc space. This can also happen if you have
installed the DB2 instance into a partition that is too small. To
resolve this, drop the LAI DB and any other unused DBs from a previous
LAI install or other unused DBs. Uninstall LAI and then reinstall
to a larger file partition.
java.io.IOException: Server returned
HTTP response code: 500 for URL:
SOLUTION: This can be the result
of an authentication problem. An authentication failure can indicate
that portal is not running properly. Start by uninstalling and restart
the Portal. Check the getUserDN_service_err.txt log for errors. This
may provide additional information about why the the authentication error
For example, you may see an error such
as the following:
[2/20/09 7:40:54:602 CST] 00000016 BPMIDFactory
Exception caught when initializing the
DSTO0064E: SQL Exception caught when
Caused by: java.sql.SQLException: Relational
database MyDatabase not in
relational database directory.DSRA0010E:
SQL State = 42705, Error Code =
This indicates the that Portal is not
starting properly because there is a problem with the database. Once
the database exception is resolved, the portal will start properly and
the authentication will be successful.
Before installing again, open the cmd.txt
file for the getUserDN_service. Test the authentication by executing
the commands in the file.
ADMG0032E: An existing JAASAuthData
entry matches alias bpmDBAuth, so a
JAASAuthData entry cannot be created
for user ID MyUser
The JAASAuthData is added by the LAI
install. This error message
indicates that there is already one
there left over from a previous
install that was not cleaned up. This
error can be ignored and the install can be continued.
java.sql.SQLException: No suitable
SOLUTION: This can be due to an
install with the wrong version of DB2. For example, Lotus Activeinsight
6.0 does not support DB2 v9.1 FP3. This is because Lotus Activeinsight
6.0 uses type 2 jdbc connections and DB2 v9.1 FP3 does not use type 2 jdbc
connections as they were deprecated in db2 version 9. When using
Lotus Activeinsight 6.0, use DB2 v8.2 FP5 instead.