9ir2 on Debian Woody installation hints (when dbca fails)

Question

"Woody" is the soon-to-be-released Debian 3.0, and contains glibc 2.2.5. The current 'stable' Debian release, Potato, has glibc2.1, so that won't work. The installation went fairly smooth, until the configuration assistants were supposed to be fired up. A solution that worked for me was changing Oracle's installed JRE.
The j2sdk is not part of standard Debian. You have to add a mirror of the blackdown debian package to /etc/apt/sources.list. Add a line like this to your sources.list:
deb ftp://ftp.nluug.nl/pub/os/Linux/java/jdk/debian woody non-free
Now use dselect, update and select the following packages:
locales
libstdc++2.9-glibc2.1
j2sdk1.3
Ofcourse the easiest way to do this is cut and paste the following commands:
apt-get update
apt-get install locales
apt-get install libstdc++2.9-glibc2.1
apt-get install j2sdk1.3
Changing kernel parameters; use sysctl.conf, I added this to mine:
kernel.sem = 250 32000 101 128
kernel.shmmax = 500000000
fs/file-max = 65536
Use sysctl -p, or reboot to activate the changes.
Start the installation, and do stuff UNTIL is asked for execution of root.sh
Now do the following:
cd $ORACLE_HOME/JRE/bin
rm jre javakey rmiregistry
ln -s /usr/bin/jre .
ln -s /usr/bin/javakey .
ln -s /usr/bin/rmiregistry .
After this, follow the root.sh instuctions and the rest of the installation should work fine.
Output of /usr/bin/java -version on my machine:
java version "1.3.1"
Java(TM) 2 Runtime Environment, Standard Edition (build Blackdown-1.3.1-FCS)
Java HotSpot(TM) Client VM (build Blackdown-1.3.1-FCS, mixed mode)

Answer 1

Hmm don't rm Oracla's java stuff, it's better to rename them and put the back after installation is complete. The above procedure works for installing and I assumed if the replaced jre would execute dbca and netca, oemapp would work as well.
But that's not the case :( Maybe the original would have worked but I cannot verify that at the moment.