Hmm, I recommend agains following ORACLE's installations guides - they are
buggy, do not rely to teh modern Linux versions, and inconsistant (and have
not startup scripts, are not well designed to make reliable startup /
shutdown and so on). Good example - open 'dbstart' script from Oracle 10.2
and look inside - they forgot to print out startup output, they used
developer's home directory to start listener, they put 'css' startupo in the
wrong place in inittab, and so on... -:) No, Oracle installation guides have
grade C- and should not be used without full review. /RAC cluster is an
exception/
But I usually modify orarun script a little and use 100% automated
installation (which runs all steos without any manual input - one by one).
Of course, you will need to do the same if installing collaboration suite.
----- Original Message -----
From: "Chris Black" <cblack@(protected)>
To: <suse-oracle@(protected)>
Sent: Tuesday, January 17, 2006 8:26 AM
Subject: [suse-oracle] Startup scripts for DB in one $OH and AS in another
$OH (OCS/Collab)
> Hello, I am setting up Oracle Collaboration Suite 10g on a SLES9 SP3
> machine. I have used the installers and followed the docs (so I ended up
> creating oracle users, setting kernel params, modifying limites, etc
> myself). I am now trying to figure out how to get this setup to start on
> boot. I found the orarun package but the Oracle Collaboration Suite
> (OCS) docs seem to recommend against this. I am willing to use it if it
> works, however. I have also looked at the ocsctl_sample script that is
> installed in the apps tier, but that doesn't seem to handle starting a
> db in a different $OH and can not be run by root. I wrote a wrapper to
> use "su oracle -c cmd" but that didn't work out either.
> The setup I have is a database instance in one $ORACLE_HOME, and then
> the app server and apps in a separate $ORACLE_HOME (infrastructure/OID
> is on another server). Both of these $OH instances are listed in
> /etc/oratab of course. Since OCS handles mail it listens on privileged
> ports (25, 143, etc), so this listener may need to be started by root. I
> am thinking I only want one opmn instance, one apache instance, and one
> em instance on the system as well. I read through the init.d/oracle
> script from the orarun package and it seems like it only looks at the
> first $OH found in /etc/oratab if the /etc/profile.d/oracle.sh file is
> not found (I moved it out of the way as I have two scripts I use to set
> oracle environments depending on whether I'm working on the db or the as).
> Has anyone either used orarun or developed other scripts for starting a
> db instance in one $OH and an app server in another? Any tips?
>
> Thanks in advance,
> Chris
>
> --
> 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
