Re: Oracle 9i - issues
John Costello <John.Costello-HKixBCOQz3hWk0Htik3J/[email protected]>
| Newsgroups | gmane.linux.redhat.taroon |
|---|---|
| Message-ID | <[email protected]> |
At 05:52 PM 9/4/2003 +0100, M A Young wrote:
>On Wed, 3 Sep 2003, Griffin, Michael (PEC) wrote:
>
> > Alright, I just finished updating the latest beta of taroon and
> > installed the latest Java sdk from Sun (1.4.2).
> >
> > I edited the oraparam.ini file to point to the Sun JRE (then
> > ./runInstaller.sh --paramFile oraparam.ini.edited). The runInstaller.sh
> > script starts and progresses through the install questions fine. When
> > the installer actually begins to copy files (the 2 (1.1 and 1.3)
> > versions of the JDK from Oracle) it prematurely "completes" the install
> > and returns me back to the screen that asks where the installation
> > directory is and where the Oracle home directory should be.
>
>Maybe it is trying to use the 1.3.1 java it has just installed to continue
>the install. I think you need to replace any 1.3 javas with a symbolic
>link to the corresponding bits of 1.4.2. I did this at the pause between
>discs 1 and 2 when I was playing with the 9iAS mid tier on severn, I don't
>know whether there is such a convenient point in the 9i install, because I
>haven't actually tried a 9i install yet.
Finally spent some time on this. Feh..
I got further "installing" Oracle 9.2.0.1.0 Enterprise Edition, minus jre
1.3.1, on Taroon beta 2 (patched as of Sept 8) by doing the following:
If you are using a cpio image, it is easier to download the .bin installer
(NOT the RPM) for j2re 1.4.2, run
chmod a+x j2re-1_4_2_01-linux-i586.bin; ./j2re-1_4_2_01-linux-i586.bin
agree to the license agreement, then replace
Disk1/stage/Components/oracle.swd.jre/1.3.1.0.0/1/DataFiles/Expanded/jre/linux
with a symlink to your j2re1.4.2_01 directory.
Assuming that your j2re directory is /home/oracle/j2re1.4.2_01 and your
cpio archive starts in /home/oradisks/Disk1, you would run the commands
mv
/home/oradisks/Disk1/stage/Components/oracle.swd.jre/1.3.1.0.0/1/DataFiles/Expanded/jre/linux
\
/home/oradisks/Disk1/stage/Components/oracle.swd.jre/1.3.1.0.0/1/DataFiles/Expanded/jre/linux.orig
ln -s /home/oracle/j2re1.4.2_01
/home/oradisks/Disk1/stage/Components/oracle.swd.jre/1.3.1.0.0/1/DataFiles/Expanded/jre/linux
The OUI does try to copy jre 1.3.1 to the oraInventory tree, and complains
about 'setting permissions' on 1.3.1's i386/green_threads directory. The
real problem is that it can't find the directory when it follows the link
to 1.4.2. I started to copy and link files from 1.3.1's bin/i386 and
lib/i386, but that turned out to be more trouble than it was
worth. Additionally, I have *no* idea what kind of mayhem would occur if
1.4.2 were use the components from 1.3.1. When OUI complains about the
i386/green_threads directory, I responded to the 'Help, Retry, Cancel'
message about green_threads with 'cancel' and then chose 'stop installation
of this component' and continued with installation of the the rest of the
product.
Run
LD_ASSUME_KERNEL=2.4.19 /home/oradisks/Disk1/runInstaller
The installer hung without LD_ASSUME_KERNEL=2.4.19. You have to jump
through the usual hoops with groups, user, etc.
I had to ignore make errors on three files under oracle/product/9.2.0.1:
network/lib/ins_oemagent.mk
rdbms/lib/ins_rdbms.mk
ctx/lib/ins_ctx.mk
I also encountered glibc and other errors when OUI tried to runnet8 and
database configuration assistants. Note that I did not perform the
recompile steps that previously were suggested on the list.
I have not had a chance to troubleshoot these last errors.
John
----
John Costello, RHCE
Disclaimer: I speak only for myself, not for my employer.
"What if nothing matters? What if everything matters?"--Hobbes
"Which would be worse?"--Calvin
--
Taroon-beta-list mailing list
[email protected]
http://www.redhat.com/mailman/listinfo/taroon-beta-list