SP2...that was easy.
Marks' mksles....script setup the file structure for my zLinux ftp
server just fine. So I did an install with the 6 base .iso files and 3
.iso files for SP2. (all on the 64 bit side)
For me, 64 bit was recently available (z/890 installed in Sept).
Prior to that I used the 31 bit SLES9. Then SP1 became available. To
upgrade a base 31 bit to SP1 required me to:
Yast
Software
Change Source of Installation
Now you should have two line items SUSE Core Version 9 and SUSE SLES
Version 9, which both have (this is to my ftp server):
Protocol FTP
Server name: 192.168.99.224
Directory on Server: sles9root//core9/CD1
Authentication: User name: suse9 Password: **********
Do an "add":
FTP (in my case)
Replicate the above stuff
When you press OK, a new source is listed at the bottom.
Bottom is no good. Apparently things are searched from the top to
bottom. (I guess that is why CORE is above SLES?) So, highlight the
new source and keep "up" until it is on the top.
Now, when you do a "system update", you will pick up the SP from your
FTP server (or where ever it is, in your case).
Tom Duerbusch
THD Consulting
Nilson Vieira wrote:
Hi Guys,
How did you install SP2 on Sles9 - 64 Bits. I have tried and didn´t work.
Thanks in advance.
----- Original Message ----- From: "Tom Duerbusch" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Thursday, October 27, 2005 2:08 PM
Subject: .bashrc vs .profile and Oracle 10g install
Suse 9 (64 bit) and the installation of Oracle 10g....
Using the Installation manual from Oracle, I installed Oracle 10g on
SLES9 with SP2. At least I think I followed it correctly.
Per the Oracle documentation, I had to interactively set a bunch of
environment variables and "export" them.
However, when I logoff the user Oracle, and log back on again (or after
a Linux reboot), these variables are not set. At reboot, the database
doesn't come back up, and I get "command not found" when trying to do
"sqlplus".
Now if I reset the variables, I can get to "sqlplus". Oracle still
doesn't come up. I currently suspect that the process that brings up
Oracle, also needs to know these environment variables to show the
location of the Oracle bin files as well as where the database files are
located.
So, that's the problem. Nothing in the Oracle Installation manual deals
with the saving of these variables. It may be that it is doing them
under the covers in some way, that failed.
Now, in the IBM Redbook, User experiences with Oracle 10g, which also
deals with the installation of Oracle 10g under SLES9, it does show
putting these variables in a .profile file in the Oracle userid...
Tried that, didn't work. Apparently, .profile isn't being executed.
The file that should be executed is the .bashrc file.
Hummmmm......
OK, the IBM manual didn't say what shell it was using.
The Oracle manual said that it was using the bash shell, but didn't say
anything about .profile or .bashrc.
Or perhaps there is a third side to this. Is there an automagical
thingie that saves environment variables across boots that is either
triggered by, perhaps the export command, or a file that is kept that
sets these variables "system wide" that the Oracle Install process might
have changed?
Or a final perhaps, that it is normal for a Linux systems programmer (is
there a systems programmer title in the Linux world?), to just know that
some things must be put in certain files (.profile or .bashrc, or ...)
and that because it is normal, no one needs to document such actions?
Just looking for a general direction to follow. (that is unless someone
has the real answer for this<G>)
So far, the Oracle Discussion groups in the Oracle website, doesn't seem
to know much, yet).
Thanks
Tom Duerbusch
THD Consulting
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390
or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
