(Aside of licensing issues).
I'd better install Oracle, then tar it into the tgz file, create short
script which set up few files around the system, and install as 'tar xzf'.
You can even create RPM for this purpose.
There is not any sense in fully scaled Oracle installation with all these
questions, linking and so on.
I use this method to install Oracle 8 client onto SLES9 Sp3 x86_64. Oracle
have something like this for NFS installation.
Another method is 'silent Oracle installation', but it i svery error - prune
and very slow.
Btw, you can install Oracle OEM agent for monitoring and management
purposes, it works well on SLES9 SP3.
----- Original Message -----
From: <ajbrown2007@(protected)>
To: <suse-oracle@(protected)>
Sent: Friday, February 09, 2007 5:51 AM
Subject: [suse-oracle] Opinions wanted for Oracle Installation, integration
with AutoYast
Hello,
I have a somewhat long post looking for architectural insights. I am
interested in opinions of how I may install Oracle software during the
manufacturing process I describe later in the email.
My goal is to install Oracle DB onto an appliance and hide all complexities
of that install from the manufacturer and the end user. The function of an
appliance is the same at every site. The system is not configured in any way
until it gets to the end user site. At that time the end user will push some
buttons on an LCD, access the appliance with a browser to complete the SUSE
configuration, i.e., hostname, domainname, smtp gateway, DNS servers, etc.
This appliance is ‘manufactured’ using AutoYast as follows:
+++ PHASE1: Download SLES 9 RPMS (SLES original release) specified in
autoinst.xml, plus some additional custom scripts and RPMs for the next
steps, then reboots.
+++ PHASE2: Using a custom script, install latest SLES RPMs, i.e., patches
and upgrade RPMs, then reboots.
+++ PHASE3: Using a custom script install 'our' software, e.g., webapps,
UIs, etc) onto the appliance, then reboot.
+++ FINAL: During this boot AutoYast completes the configuration and now the
appliance is ready for the end user.
This manufacturing process works well with MySQL, the MySQL RPMs install the
software in the phase 3, like all other NON SUSE software on the system. In
addition the MySQL database is created at that time.
Configuration of all software (configuration files and MySQL replication
tables) happens at the end user site.
It is not obvious to me how this could be done with Oracle. (Please keep in
mind my Oracle experience is a whole two weeks <grin>).
As a test I have done the followingi to my manufacturing process:
+ Download the Oracle Linux ZIP file and an Oracle RPM file (I built)
at the end of phase 1 of my manufacturing process. This home made RPM sets
up the user env, runs the Oracle Install in silent mode and runs root.sh at
the end. This RPM works well if installed AFTER AutoYast is all done and the
system has an IP plus hostname. It does not work as part of AutoYast.
Before I dig into why it fails, I am interested in any insight, links,
documents or experiences anyone has had trying to install Oracle as I
describe above. I may be looking in the wrong direction all together and
would appreciate understanding that also.
My goal is to integrate the Oracle install into my manufacturing process.
During the manufacturing process Oracle software would be installed and the
DB created. Later during the box configuration Oracle would be configured
using local networking information specific to that site.
Hopefully I have explained well. I appreciate any thoughts.
Thanks
Alan
--
To unsubscribe, email: suse-oracle-unsubscribe@(protected)
For additional commands, email: suse-oracle-help@(protected)
Please see http://www.suse.com/oracle/ before posting
