I think about exactly the same way.
may be, it is reasonable to make 2 improvements:
- use WEBMIN for appliance management
- have a relinking script so that when you install RPM, and if system is
very different from original one,
you can relink oracle (but I'd better avoid it).
I always guess, when Oracle make the same (use RPM) instead of complicated
and slow 'runInstaller' method of installation.
----- Original Message -----
From: "Clemens Bleile" <clemens.bleile@(protected)>
To: <ajbrown2007@(protected)>
Cc: <suse-oracle@(protected)>
Sent: Friday, February 09, 2007 10:36 AM
Subject: Re: [suse-oracle] Opinions wanted for Oracle Installation,
integration with AutoYast
>
> Hi Alan,
>
> some time ago we built rpm-files to install oracle. We had 3 rpms: One
> for the software, one for a dummy database and one for the scripts we
> used for backups and other stuff.
>
> With this method we setup Oracle (Software, Database, Backup setup) with
> 3 simple "rpm -ivh" within 10 to 15 minutes. Prerequisite was that the
> OS is setup and an OS-user oracle is available.
>
> The important thing is to clone the Oracle-Home. Please read Metalink
> Note 300062.1 for this purpose. I.e. for 9i you may have to install a
> patch before putting the ORACLE_HOME in the rpm-file.
>
> Here's an example spec-file to build an rpm of an Oracle-Home installed
> on "/opt/oracle/product/ora10201ee":
>
> #
> # Spec file for installing Oracle 10.2.0.1
> #
> Summary: Oracle 10.2.0.1
> Name: Oracle_10201_EE
> Version: 1
> Release: 1
> Copyright: Clemens
> Group: Applications/Database
> Source: http://www.oracle.com
> URL: http://www.oracle.com
> Distribution: Oracle on Linux
> Vendor: Clemens
> Packager: Clemens Bleile <clemens.bleile@(protected)>
>
> %description
> Oracle 10.2.0.1 EE packaged in rpm.
>
> %prep
>
> %build
>
> %install
>
> %files
> /opt/oracle/product/ora10201ee
>
> %pre
>
> %post
> chown -R oracle:oinstall /opt/oracle
> su - oracle -c "export ORACLE_BASE=/opt/oracle; cd
> /opt/oracle/product/ora10201ee/clone/bin; perl clone.pl
> ORACLE_HOME=\"/opt/oracle/product/ora10201ee\"
> ORACLE_HOME_NAME=\"H10201EE\""
> if [ ! -f /etc/oraInst.loc ]; then
> /opt/oracle/oraInventory/orainstRoot.sh
> fi
> /opt/oracle/product/ora10201ee/root.sh -silent
>
> %preun
> su - oracle -c "export ORACLE_BASE=/opt/oracle; cd
> /opt/oracle/product/ora10201ee/oui/bin; ./runInstaller -silent
> -deinstall -ignoreSysPrereqs
> REMOVE_HOMES={\"/opt/oracle/product/ora10201ee\"}"
>
> %postun
> rm -rf /opt/oracle/product/ora10201ee
>
>
> Here are the commands I used to build and install the rpm:
>
> # Build the rpm:
> rpmbuild -bb <spec-file>
> # To install it on the new machine do the following:
> rpm -ivh <rpm-file> --nodeps
> # To delete the package do the following:
> rpm -e <package-name>
>
> At that time we built it on Redhat, but it shouldn't be different on Suse.
>
> Clemens
>
> ajbrown2007@(protected):
> > 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
>
>
--
To unsubscribe, email: suse-oracle-unsubscribe@(protected)
For additional commands, email: suse-oracle-help@(protected)
Please see http://www.suse.com/oracle/ before posting
