Troubleshooting
Problem
To be able to create a database during the profile creation process, the user that runs the profile creation task needs access to the DB2 instance. Without the DB2 instance access you see a "DB2 not found " exception during the profile creation process.
Symptom
During the profile creation process on a UNIX-based operating system, you are unable to complete the WebSphere Process Server Deployment Manager or Stand-alone profile creation process. This issue occurs when the option to create the common database on a local DB2 instance is selected and the user does not have access to the DB2 instance.
Profile creation fails with the following exception:
<message>/opt/ibm/WebSphere/ProcServer/util/dbUtils/profileHelpers/commo
nDBUtility.ant:896: Execute failed: java.io.IOException: db2: not found
at org.apache.tools.ant.taskdefs.ExecTask.runExec(ExecTask.java:620)
at org.apache.tools.ant.taskdefs.ExecTask.execute(ExecTask.java:452)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
Cause
The user that creates the profile does not have access to create a database and tables.
Environment
This issue occurs in the following environments:
- You create a WebSphere Process Server stand alone profile or deployment manager.
- You can use the option to create a commonDB database on a local DB2 installation during the profile creation process.
- The user that creates the profile does not have access to create a database and tables.
Resolving The Problem
Regardless of the user ID that is selected for JDBC drivers, the user ID that is used for creating the profile (and also logged into operating system) needs access to the database,
If you are configuring a DB2 database on a local Linux or UNIX-based operating system, source the database environment by completing the following steps:
- Modify the /etc/group and make sure that the user ID that installed the product is in the same group as the db2instance.
- Source the database environment by running the db2instance/sqllib/db2profile script, but replace db2instance with the path and name of your database instance.
How to source the db2profile script before starting the Profile Management Tool (PMT)
- You can add <db2instance>/sqllib/db2profile to the .profile and log into the operating system again.
- You can also source the db2profile by running the following command from the command prompt before starting the Profile Management Tool (PMT).
" . <db2instance>/sqllib/db2profile " (dot and space required)
Note: Make sure to prefix <dot and space> before the command to make the current shell inherit the variables from the db2profile.
If you do not use <dot and space>, the child process runs, but when it returns the parent it does not have the variables defined in the db2profile script. You will notice the same problem when you try to create the new profile again.
Alternate Solution:
Select the option to postpone the database creation process during the profile creation process and use the generated scripts to create the database before starting the respective server (stand-alone profile or the Deployment Manager).
Related Information
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21383715