This is for reference only, databases are as of 2008 provideded and maintained by OIS database services. See wiki pages under https://wikis.mit.edu/confluence/display/STLRP/Home for current information.
Do gzcat FILE|cpio -idmv e.g.
mkdir -p /var/local/oracle-cds/10.2.0/ cd /var/local/oracle-cds/10.2.0/ gzcat ../10gr2_db_sol.cpio.gz | cpio -idmv mkdir ../10.2.0-companion cd ../10.2.0-companion gzcat ../10gr2_companion_sol.cpio.gz | cpio -idmv mkdir ../agent cd ../agent gzcat ../Solaris_Grid_Control_agent_download_10_2_0_1.cpio.gz | cpio -idmv
Patches are often zip files, e.g.
mkdir ../489 cd ../489 unzip ../p4898608_10201_GENERIC.zip mkdir ../504 cd ../504 unzip ../p5049080_10201_SOLARIS64.zip
Documentation from Oracle is at http://www.oracle.com/technology/documentation/database10gr2.html notably the Quick Installation Guide
Kernel configuration parameters may be fine in Athena 9.3 and 9.4, but check, the following may need to be added to /etc/system and the server rebooted.
set noexec_user_stack=1 set noexec_user_stack_log=1 set shmsys:shminfo_shmmax=4294967295 set shmsys:shminfo_shmmin=1 set shmsys:shminfo_shmmni=100 set shmsys:shminfo_shmseg=10 set semsys:seminfo_semmni=100 set semsys:seminfo_semmsl=256 set semsys:seminfo_semmns=1024 set semsys:seminfo_semopm=100 set semsys:seminfo_semvmx=32767
Do:
cd / mkdir var/local mkdir var/local/oracle mkdir var/local/oracle/u1 mkdir var/local/oracle/u2 mkdir var/local/oracle/u3 ln -s /var/local/oracle/* . chown oracle var/local/oracle/u? mkdir -p /u1/oracle/app/oracle mkdir /u2/oradata chown -R oracle:oinstall /u1/oracle/app/oracle chown -R oracle:oinstall /u2/oradata mkdir /var/local/bin
Create /var/local/oracle-user directory, provide oracle .profile, give oracle a password with 'passwd oracle'. Do:
mkdir /var/local/oracle-user cp /mit/stellar/components/oracle/oracle-profile10 /var/local/oracle-user/.profile chown oracle /var/local/oracle-user/.profile chown oracle /var/local/oracle-user chgrp oinstall /var/local/oracle-user/.profile chgrp oinstall /var/local/oracle-user passwd oracle
Have two xterms: one as root, one as oracle (log in as root, open an xterm and su - oracle), see server setup document for details on using X remotely logging in to secure servers.
set -o emacs unset ORACLE_HOME cd /tmp /var/local/oracle-cds/10.2.0/runInstaller
ORACLE_HOME should not be set, but ORACLE_BASE should be, the .profile has a good location: /u1/oracle/app/oracle
Do an enterprise install, create a test database.
Ignore any warning about noexec_user_stack.
When running the /u1/oracle/app/oracle/product/10.2.0/Db_1/root.sh script as root (this is the last step of installation), use /var/local/bin as the local bin directory.
Oracle Installation is now complete
Set ORATAB (ORATAB=/var/opt/oracle/oratab) and ORACLE_HOME_LISTNER (ORACLE_HOME_LISTNER=/u1/oracle/app/oracle/product/10.2.0/Db_1) in dbstart and dbshut edit oratab to start databases automatically add 'dbora' to /etc/init.d and make symlinks
emacs /u1/oracle/app/oracle/product/10.2.0/Db_1/bin/dbstart /u1/oracle/app/oracle/product/10.2.0/Db_1/bin/dbshut cp /mit/stellar/components/oracle/dbora10 /etc/init.d/dbora chmod 755 /etc/init.d/dbora ln -s /etc/init.d/dbora /etc/rc0.d/K04dbora ln -s /etc/init.d/dbora /etc/rc2.d/S94dbora
Add warehouse from tnsnames.ora in /mit/stellar/components/oracle/emcc2 to the tnsnames.ora in /u1/oracle/app/oracle/product/10.2.0/Db_1/network/admin/. Security recommendation is to change the name to the ip address in listner.ora. Also, set SQLNET.ALLOWED_LOGON_VERSION=10 in sqlnet.ora.
Apply any patches to the oracle software needed.
On Athena 9.4 / Solaris 10, patch installation fails. See metalink Note:353150.1 and skip verify:
$ORACLE_HOME/OPatch/opatch apply OPatch.SKIP_VERIFY=true
On Athena 9.3 / Solaris 9, Grid Control can be used to apply the patch.
Follow instructions in the ./README
Only on one server, which will then manage all other servers and databases.
This is "Oracle Enterprise Manager 10g Grid Control Release 2 (10.2.0.1)" and is a separate 4-cd installation.
Note that the grid control installation destination must not include any symbolic link, each step in the path must be a real directory.
Documentation from Oracle is at http://download-east.oracle.com/docs/cd/B16240_01/doc/install.102/b16228/toc.htm.
The distribution Solaris_Grid_Control_agent_download_10_2_0_1.cpio.gz was unpacked above into /var/local/oracle-cds/agent.
mkdir -p /u3/local/OracleHomes chown -R oracle:oinstall /u3/local/OracleHomes
As above, have two xterms: one as root, one as oracle (log in as root, open an xterm and su - oracle), see server setup document for details on using X remotely logging in to secure servers.
As user "oracle"
unset ORACLE_SID unset ORACLE_HOME unset ORACLE_BASE cd /var/local/oracle-cds/solaris/agent ./runInstaller
At the Specify installation Type page select "additional management agent." Select /u3/local/OracleHomes as parent directory.
Supply the Grid Control server host name, e.g. amps-prog-6.mit.edu as host name for Management Service on the Specify Oracle Management Service Location page. Use the default port.
Give the password of the system user from the grid control repository database on the server host as the required password for management service connection.
Click install.
When prompted, execute /u3/local/OracleHomes/agent10g/root.sh as root. Select /var/local/bin as the local bin directory. The dbhome, oraenv and coraenv are identical to any which may have been installed earlier. When the script is done, click ok.
The installation log file is e.g. /u1/oracle/app/oracle/oraInventory/logs/installActions2006-04-11_10-40-46AM.log and release notes are located at /u3/local/OracleHomes/agent10g/relnotes/README.txt
After installation, within a few minutes the new database and host are automatically shown in target list of grid control but with an error indication.
Select the new database from the list under target-database. This leads to Database instance page. In the lower left corner, click the "monitoring configuration" link and fill the password for user dbsnmp which is same as we used for system and click submit at the next page. This will save the target process.
When an agent is installed on the machine, it puts script called gcstartup in /etc/init.d directory so that the agent will startup automatically when the machine startsup.
$Revision: 31385 $ $Date: 2008-11-26 11:39:46 -0500 (Wed, 26 Nov 2008) $