Home » RDBMS Server » Server Administration » Common Oracle install folder
Common Oracle install folder [message #58221] Thu, 07 August 2003 11:42
Tony
Messages: 190
Registered: June 2001
Senior Member
Hello,
We have been using oracle 7.3.4 and 8.1.7 across different solaris servers, but similar configuaration. What we have now is a common oracle folder (/opt/oracle/8.17) with all the files that are shared across 3 different servers. The reason why it was done this way is because /opt directory structure is centrally located and has limited space and carries only binaries and configurations for all appllications on the solaris. It cannot be used for data or log storage. Also to prevent securing of binary files and configuration objects. So the whole /opt/structure is readonly file system.
However symbolic links are created to locations that have changes pertaining to various servers. For example, /opt/oracle/8.1.7/dbs points to /var/oracle/8.1.7/dbs (where /var/... directory structure is specially for logs/and changing configuration info etc, but not data). Similarly /opt/oracle/8.1.7/network/admin -> points to /var/oracle/<servername>/network/admin
....and so on and so forth.
Now I've had few issues in 8.1.7 when trying to invoke certain oracle utilities (such as odma, oms, oracle intelligent agent etc, ) where it tries to write to the /opt directory structure. So I have to create symbolic link for all of them to /var.
Now the question is, how feasible is to continue this in 9.2.0? Should we have 9.2.0 work with common /opt/oracle/9.2.0 directories across servers, or is it good to a separate installation per server?
Remember, that all our oracle servers are configured with the same hardware/system configuration.

Thanks for your patience.
Previous Topic: distributed data files
Next Topic: Ping a table in the keep buffer pool
Goto Forum:
  


Current Time: Fri Sep 20 06:51:14 CDT 2024