Hi - I've never had this problem in the past (with a different Lx distribution), but cannot launch the Db2 Control Center in Fedora 8. The best I can provide is a dump of the session.
All help appreciated - George
:0.0
root ~ # su - db2inst1
db2inst1 ~ $ echo $DISPLAY
:0.0
db2inst1 ~ $ db2cc &
[1] 9817
db2inst1 ~ $ java: xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' fail                                            ed.
JVMDUMP006I Processing Dump Event "abort", detail "" - Please Wait.
JVMDUMP007I JVM Requesting System Dump using '/opt/ibm/db2/V9.5/tools/core.20080                                            608.202649.9819.dmp'
JVMDUMP010I System Dump written to /tmp/core.20080608.202649.9819.dmp
JVMDUMP007I JVM Requesting Snap Dump using '/opt/ibm/db2/V9.5/tools/Snap0002.200                                            80608.202649.9819.trc'
JVMDUMP010I Snap Dump written to /tmp/Snap0002.20080608.202649.9819.trc
JVMDUMP007I JVM Requesting Java Dump using '/tmp/javacore.20080608.202649.9819.t                                            xt'
JVMDUMP010I Java Dump written to /tmp/javacore.20080608.202649.9819.txt
JVMDUMP013I Processed Dump Event "abort", detail "".
DB2JAVIT : RC = 6
 

See if it is a linux/X problem or a db2 thing. Instead of "db2cc" try to start "xterm". If that does not work either you know you're in the wrong forum :)

Dispite of that you could try this:

ssh -X -Y db2inst1@localhost
db2cc

 

truu...thnks
I am in the KDE GUI, and running this from a cmd type window, such as konsole, terminal etc. Isn' that pretty much the same thing? Or do you suggest I run xterm from the command line after inital login to the box, before I open any kind of GUI whatsoever?
Thanks
George
P.S I used to have this OK on SLACKWARE, and I recall the commands I gave above did work. I'm no LINUX expert, esp. with "X".
 

My suggesion? Do not log in and work as "root". Just login as db2inst1 and work from there: that's the KISS approach.

When that does not work fine then you've probably asked DB2 to create that user during installation.
So a tip:
When installing DB2 on linux, 1st create the user which is going to be the instance owner yourself and then install DB2.

b.t.w. did you run DB2 ob Slackware?
 

Yes, I did run it on SLACKWARE 9, 10 successfully, but found the package management (not blessed by IBM, being .tgz) awkward, since it was not rpm based, and had to convert to rpm's with a hard-to-find utility (rpm2tgz), and was forced to use db2_install...whcih is  - in fact - fine. It's probably the best way.
George

yeah, slackware has its cons & pro's. And in case of DB2: you want a mean & lean database server, so who cares about the package manager? A base install, install DB2 and do your work in the serverroom. There are other distro's for the fancy desktops.

Truu - yes SLackware was good:lean and mean, and DBMS functioned well: they say if you learn slackware, you learn UNIX: if you learn RedHat, you learn Redhat!
George