 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
| HomeDiscussion Groups Database Servers DB2InformixIngresMS SQLOraclePervasive.SQLPostgreSQLProgressSybaseDesktop Databases FileMakerFoxProMS AccessParadoxGeneral General DB TopicsDatabase TheoryRelated Topics Java Development.NET DevelopmentVB DevelopmentMore Topics ... |
Database Forum / DB2 Topics / March 2004DB2 8.1 db2cc DB2JAVIT : RC = 11 Error // SuSE 9.0 Kernel 2.4.25
I searched far and wide for more information on how to correct this problem, but did not find any information on what to do. We have successfully installed DB2 8.1 on Linux. SuSE 9.0. Kernel 2.4.25 Dell PowerEdge 6650 Filesystem jfs DB2 software installed perfectly as root, but cannot run db2cc when becoming db2inst1. We get the following error: DB2JAVIT : RC = 11 We do have Sun's Java installed. We did a search in YaST2 and found the java2-jre installed version 1.4.2-35 URL ( http://java.sun.com/j2se/1.3/download-linux.html ) RPM ( java2-jre-1.4.2-35.i586.rpm ) We also have installed java2-jre-1.4.2-35.i586.rpm, which is the GNU runtime library for gcc. This is the only Java RPM we have installed outside of IBM's Java software. Yast reports IBMJava2-1.3.1, Java Help, Java Support, Java Common files installed, from the DB2 installation. Environment: db2inst1@xxxxxxx:~> env | sort | grep -i JAVA CLASSPATH=/db2home/db2inst1/sqllib/java/db2java.zip:/db2home/db2inst1/sqllib/java/db2jcc.jar: /db2home/db2inst1/sqllib/java/sqlj.zip:/db2home/db2inst1/sqllib/function:. JAVA_BINDIR=/usr/lib/java/jre/bin JAVA_HOME=/usr/lib/java/jre JAVA_ROOT=/usr/lib/java JRE_HOME=/usr/lib/java/jre PATH=/db2home/db2inst1/bin:/usr/local/bin:/usr/bin:/usr/X11R6/bin:/bin:/usr/games:/opt/gnome/bin: /opt/kde3/bin:/usr/lib/java/jre/bin:/db2home/db2inst1/sqllib/bin:/db2home/db2inst1/sqllib/adm:/db2home/db2inst1/sqllib/misc Before you suggest things, we unset all JAVA_ related env vars as root before installing, and everything went real smooth, and successfully installed, and the engine is up and running, no problems. We just can't get the db2cc running. We installed DB2 before with db2cc running on another server, but can't seem to debug why it doesn't work on this one. Your help would be greatly appreciated. Please post to the group as I can't always get to netscape. -DG- > I searched far and wide for more information on how to correct this > problem, but did not find any information on what to do. [quoted text clipped - 12 lines] > > DB2JAVIT : RC = 11 Try the following: Set the environment variable LD_ASSUME_KERNEL by export LD_ASSUME_KERNEL=2.2.5 Then start db2cc. -- Peter Becker >> I searched far and wide for more information on how to correct this >> problem, but did not find any information on what to do. [quoted text clipped - 21 lines] > -- > Peter Becker Peter, Although that may work, I'm not sure that "pretending" to be a 2.2 kernel is the best answer. Alternatively, try the workarounds for Red Hat Enterprise Linux 3 in the "Errata" on the "Validation" page - http://www-306.ibm.com/software/data/db2/linux/validate/pdfs/errata.pdf Java versions used by DB2 are very specific (not only does the system expect you to have the IBM JDK, but also a specific version of it). One of the things I've noticed is that if you have a Sun JDK newer than the IBM JDK supplied with DB2 then the install will fail. You have, as per the doc above, to ensure that the Sun JDK isn't found during the install. You also have to, after the install, set DBM CFG parameter JDK_PATH to point to the IBM JDK. HTH Phil  SignaturePhilip Nelson ScotDB Limited http://www.scotdb.com (teamdba@scotdb.com) For what it's worth, db2cc is now working, and here's my env: db2inst1@xxxxxx:~> cat sqllib/userprofile PATH=/db2home/db2inst1/bin PATH=$PATH:/db2home/db2inst1/sqllib/bin PATH=$PATH:/db2home/db2inst1/sqllib/adm PATH=$PATH:/db2home/db2inst1/sqllib/misc PATH=$PATH:/usr/local/bin PATH=$PATH:/usr/bin PATH=$PATH:/usr/X11R6/bin PATH=$PATH:/bin PATH=$PATH:/opt/gnome/bin PATH=$PATH:/opt/kde3/bin export PATH # unset JAVA_BINDIR # unset JAVA_HOME # unset JAVA_ROOT # unset JRE_HOME export LD_ASSUME_KERNEL=2.2.5 You'll notice I had previously tried to unset the JAVA_ vars but it had no effect. The LD_ASSUME_KERNEL=2.2.5 did the trick, and we're on the air. But I do agree that we should be pointing to the right JDK. The biggest problem as everyone knows is that every time a java application is installed it seems like I need yet another version of the JDK that somebody made just for their software. "Java, write once, run everywhere but be sure to use our version of the JDK" If you have some specific vars I should be using for IBM DB2 please let me know, otherwise it appears to be working correctly. We'll also be applying the FixPacks shortly. Thanks! -DG- >>>I searched far and wide for more information on how to correct this >>>problem, but did not find any information on what to do. [quoted text clipped - 44 lines] > > Phil > For what it's worth, db2cc is now working, and here's my env: > [quoted text clipped - 9 lines] > PATH=$PATH:/opt/gnome/bin > PATH=$PATH:/opt/kde3/bin I'm very curious about these. Why are you clearing out the PATH, only to reset it to include what dbprofile has? What would happen if IBM changed db2profile to add another directory to your PATH? > export PATH > # unset JAVA_BINDIR [quoted text clipped - 4 lines] > > You'll notice I had previously tried to unset the JAVA_ vars but it had That's because db2javit (which is called by db2cc) resets its own environment to use the Java that is specified by the instance's dbm cfg (check for the JDK_PATH entry). You can actually point this to any Java you wish - but if it's not one certified by IBM, you are running at your own risk. > no effect. The LD_ASSUME_KERNEL=2.2.5 did the trick, and we're on the > air. But I do agree that we should be pointing to the right JDK. The > biggest problem as everyone knows is that every time a java application > is installed it seems like I need yet another version of the JDK that > somebody made just for their software. DB2 doesn't need one made just for it - but it is only validated against certain JVMs. > "Java, write once, run everywhere but be sure to use our version of the > JDK" Yes, something like that. Problem is that the JVMs aren't really as compatable with each other as some would like ;-) > If you have some specific vars I should be using for IBM DB2 please let > me know, otherwise it appears to be working correctly. We'll also be > applying the FixPacks shortly. Amazingly this did the trick! Thanks! -DG- >>I searched far and wide for more information on how to correct this >>problem, but did not find any information on what to do. [quoted text clipped - 21 lines] > -- > Peter Becker > Amazingly this did the trick! FYI: The reason why db2cc did not work without LD_ASSUME_KERNEL=2.2.5 is a floating stack feature of the glibc which is incompatible with some JDKs. Unfortunately, this feature ist enabled in the SuSE 9.0 distribution (SuSE 8.2 would work). By setting LD_ASSUME_KERNEL=2.2.5 you disable this floating stack feature. -- Peter Becker You're right, we had DB2 running with no problems on an 8.2 system. We're about to rebuild that system shortly so it'll be 9.0 before too long. So...We got that problem solved, but then had problems with clustering, which we then figured out were NFS issues. We have two 9.0 systems we are clustering as MPP, with node A being the NFS server, and then n-servers as clients mounting a /db2home directory. Strange thing about NFS on SuSE 9.0, node B could mount and see and use the /db2home on node A, but kept getting the SQL6048N error. It was figured out by Toronto Tech Support, we hadn't started rpcd.statd, even though it appears it wasn't really necessary--to my mind at least--and we didn't catch that we needed rpc.statd in any documentation. But now things are working, and hopefully we will be smokin' shortly with a lot of data. ( I have to say that the nuts-b-bolts aspects of DB2 are becoming more appealing over time. Hopefully my enthusiasm will be rewarded, keep your fingers crossed! ) I'm not too thrilled that we have to use the r-commands to make things work, there should be a better way than rlogin, etc. -DG- >>Amazingly this did the trick! > [quoted text clipped - 5 lines] > -- > Peter Becker This is really a shot in the dark, but could you try removing the -l option in sqllib/db2cc? The '-l' option is a single JVM option but it didn't work on UNIX before FP4. With FP4, the option has been fixed but it might never have been tried on SuSE 9, so you should probably report this to service. > I searched far and wide for more information on how to correct this > problem, but did not find any information on what to do. [quoted text clipped - 28 lines] > > db2inst1@xxxxxxx:~> env | sort | grep -i JAVA CLASSPATH=/db2home/db2inst1/sqllib/java/db2java.zip:/db2home/db2inst1/sqllib /java/db2jcc.jar: > /db2home/db2inst1/sqllib/java/sqlj.zip:/db2home/db2inst1/sqllib/function:. > JAVA_BINDIR=/usr/lib/java/jre/bin > JAVA_HOME=/usr/lib/java/jre > JAVA_ROOT=/usr/lib/java > JRE_HOME=/usr/lib/java/jre PATH=/db2home/db2inst1/bin:/usr/local/bin:/usr/bin:/usr/X11R6/bin:/bin:/usr/ games:/opt/gnome/bin: /opt/kde3/bin:/usr/lib/java/jre/bin:/db2home/db2inst1/sqllib/bin:/db2home/db 2inst1/sqllib/adm:/db2home/db2inst1/sqllib/misc > Before you suggest things, we unset all JAVA_ related env vars as root > before installing, and everything went real smooth, and successfully [quoted text clipped - 6 lines] > > -DG- |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.