The DB2® Java daemon (db2jd) is not started on UNIX® platforms automatically.

On UNIX systems, you have to start the JDBC listener manually by running "db2jstrt 6789" (where 6789 is the port that the Java listener will be listening on). If you want to start the listener automatically, you have to put "db2jstrt 6789" in a script file and run this script each time you log in or during system startup. Another option is to modify /etc/inittab to start this listener on reboot.

To enable sql tracing:

On Windows: 

1) Help-> About Optim 
2) Double click on the Optim Logo 
3) Select the checkbox for NEC Dynamic SQL (DSQ) 
4) Select the checkbox for Option 25 (Trace sql statements...) 
5) Click on enable tracing. 
6) Reproduce the problem.

Add the following to either the pstserv.cfg or the pstlocal.cfg, 
dependant on whether you are using optim server or client (pr0cmnd): 


trace DSQ 25 
trace enable


If using server you will need to restart it to pick up these changes. 

Method 1:

Using “+c” option turns off auto-commit for the current command ; rollback will undo this uncommitted change

[db2inst1@frodo ~]$ db2 +c "update tec_t_evt_rep set source=‘changeme'"
DB20000I The SQL command completed successfully.
[db2inst1@frodo ~]$ db2 rollback
DB20000I The SQL command completed successfully.
[db2inst1@frodo ~]$ db2 terminate
DB20000I The TERMINATE command completed successfully.


Method 2: 
Example: using DB2OPTIONS env variable with +c (off) or -c (on)

[db2inst1@frodo ~]$ export DB2OPTIONS='+c -a'
[db2inst1@frodo ~]$ db2 list command options
Command Line Processor Option Settings

Backend process wait time (seconds) (DB2BQTIME) = 1
No. of retries to connect to backend (DB2BQTRY) = 60
Request queue wait time (seconds) (DB2RQTIME) = 5
Input queue wait time (seconds) (DB2IQTIME) = 5
Command options (DB2OPTIONS) = +c -a

Option Description Current Setting
------ ---------------------------------------- ---------------
-a Display SQLCA on
-c Auto-Commit OFF


Method 3:
Example: Turning off/on auto-commit for session only

Turning off:
C:\SQLLIB\BIN>db2 update command options using c OFF 

Turning on:
C:\SQLLIB\BIN>db2 update command options using c on 

Note: Method 3 only used for temporary change during interactive mode 
(The db2=> prompt). It affects the current interactive session only. With
c on, other users will see the changes made; with c OFF, other users will
be locked out of seeing the change until the commit is made..

Method 4: Using db2cli.ini configuration file

[mydatabase_alias] 
autocommit=0 

Note:
Env Variable Overrides to db2cli.ini are:
SQL_ATTR_AUTOCOMMIT= 1 or 0 (on or off)

PROBLEM

Shadow passwords are not supported in either IBM® IDS versions 7.31 or 9.40. This operating system enhancement is not available until the release of HP-UX® 11i (11.11), and for purposes of backward compatibility IDS 7.31 and 9.40 are ported to earlier releases of HP-UX 11. 


SCOPE

The following products and operating systems are affected:

• Use Trusting Computing Based (TCB) as an alternative password shadowing scheme.
• Upgrade to IBM® Informix® Dynamic Server™ version 10

db2icrt/db2idrop hangs when executing db2isrv

DB2 port entries in /etc/services file are missing or in wrong order etc.

Example 1:
DB2_db2instance1 entry is missing:

DB2_db2instance1_1 60045/tcp 
DB2_db2instance1_2 60046/tcp 
DB2_db2instance1_END 60047/tcp

DB2_db2instance2_1 60001/tcp 
DB2_db2instance2_2 60002/tcp 
DB2_db2instance2_END 60003/tcp 
DB2_db2instance2 5914/tcp

1. Remove DB2 port entries related to the instance name in /etc/services file

2. Run db2icrt/db2idrop command again.

The full output when running rtserver is:

optim@myserver:> ./rtserver start

Seems that there are no applications running.
No display defined - don't clean xprops
Seems that there are no applications running.
No display defined - don't clean xprops
Core Services are not running.
Failed to start Core Services: Failed to launch rpcss.

The MainWin log file may show the following error:

RPCSS ServiceMain failed with 1702

This problem is typically caused by a network conflict.

The following have resolved this issue:

• Run "rtserver verify"
• Ensure that the rtservername entry in pstserv.cfg matches that in /etc/hosts
• Ensure that the rtservername only appears once in /etc/hosts
• Ensure that the IP address associated with the server only appears once in /etc/hosts