Problems With Workflows; Db2 Universal Database Errors Occur When You Deploy Resources; Db2 Universal Database Creates A Database State Error - IBM 51 Troubleshooting Manual

6. Change your password again based on the specified password syntax.

Problems with workflows

This section includes troubleshooting scenarios for the following problems:
v "DB2 Universal Database errors occur when you deploy resources"
v "DB2 Universal Database creates a database state error"
v "DB2 Universal Database deadlocks occur when the system runs a logical
v "Shell command error: Resource temporarily unavailable" on page 65
v "IBM Tivoli Software Support personnel have requested a copy of a workflow"
v "A workflow does not install" on page 67
v "Cannot run workflows if the PS1 environment variable is altered" on page 68
DB2 Universal Database errors occur when you deploy
resources
When you run a workflow to deploy resources, you might see a DB2 Universal
Database error telling you that an SQL exception has occurred.
Cause
This error can occur when the application heap size is not large enough to process
the request.
Solution
Increase the application heap size, rebind the packages, terminate all connections,
and restart the Tivoli Intelligent Orchestrator server. To complete this task:
1. Log on to the DB2 Universal Database server as the DB2 Universal Database
2. Open a DB2 Universal Database command window and enter the following
3. Under the sqllib\bnd directory, run the following command to rebind the
4. Run the following command to terminate all connections:
5. Restart the Tivoli Intelligent Orchestrator server.

DB2 Universal Database creates a database state error

Tivoli Intelligent Orchestrator displays a DB2 Universal Database error. For
example:
com.ibm.tivoli.orchestrator.de.dao.PersistentStateException: COPDEX038E A
persistent/database state error: [IBM][CLI Driver][DB2/NT] SQL0302N EXECUTE
<DB text> SQLSTATE=22001 occurred.
64
Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide
operation" on page 65
on page 65
instance owner.
command to increase the application heap size:
db2 update db cfg for $DB2_DB_NAME using applheapsz 3072
where $DB2_DB_NAME is the name of the database you want to modify.
packages:
db2 connect to $DB2_DB_NAME db2 "bind @db2ubind.lst blocking
all grant public" db2 "bind @db2cli.lst blocking all grant public CLIPKG 6"
db2 force applications all