
        
        How to generate database setup 
          files (Oracle 9.2.0 - Mac OS X).
        Note: More specific information is contained within 
          file#39 
          which is created during the file generation process. File#39 
          contains the actual file names of the scripts which have been custom-generated 
          for a particular database instance.
        [Note: Please ignore any references to the use or installation 
          of the OMS server or OEM Console with Developer Release 1 of Oracle 
          9.2.0 on Mac OS X because this functionality is not yet available from 
          Oracle. Also, the JServer, Ultrasearch, OLAP, native PL/SQL compilation 
          and RAC features are not yet available.]
        Hardware and OS Requirements for Mac OS X:
          The minimum configuration for installing Oracle 9.2.0 on Mac OS X is 
          to use a server with a G4 CPU and 512Mb of RAM. Mac OS X Server 10.2 
          (also called Jaguar) is the minimum version of Mac OS X which is officially 
          supported by Oracle, however the desktop non-server version of Mac OS 
          X 10.2 can be used. 2 Gb (minimum) of available disk space will also 
          be required for installing the database binaries and creating the database 
          instance.
        Pre-install Tasks:
          As with any Oracle database installation, it is necessary to perform 
          a number of pre-install tasks to prepare the server to run the Oracle 
          database software. The pre-install tasks on Mac OS X follow the same 
          basic pattern as other versions of UNIX but with differing UNIX commands 
          and options.
        Oracle 9.2.0 Developer Release 1 is only available as 
          a download from otn.oracle.com. It can be helpful to burn a CD containing 
          the downloaded software for portability between machines. This CD should 
          be named ORACLE920_MACOSX or the file#5 
          script will need to be modified with the actual name of the CD.
        Prior to attempting any remote SSH or FTP connection to 
          the server, it is necessary to enable the SSH and FTP services. Open 
          the System Preferences pane, click the "Sharing" icon, click 
          the "Services" folder tab. Enable the "Remote Login" 
          and "FTP Access" services by clicking the "On" check 
          box to the left of each service.
        Configure Ethernet settings prior to starting the database 
          installation by opening the Network preferences pane, selecting either 
          the "Built-in Ethernet" or the PCI Ethernet menu item. Enter 
          the IP Address, subnet mask, router, DNS Servers and Search Domains 
          information for this server - if this task has not previously been done.
        Note: It is recommended that a static IP address be assigned 
          so that client computers can reliably access the database server. Dynamic 
          IP addressing would also prevent reliable access to the database server 
          from Oracle Enterprise Manager Console application which uses Oracle 
          Management Servers for authentication. The IP address of each node is 
          embedded within the connection and authentication information stored 
          on the OMS server.
        Multiple IP Addresses may be assigned to the same Ethernet 
          card by selecting the Network Port Configurations menu item, then clicking 
          the "New" or "Duplicate" buttons and entering the 
          appropriate IP address information. This feature permits DHCP to be 
          used as the primary IP address for the server, but also allows a static 
          IP address to be assigned and used exclusively for Oracle access.)
        The root account in Mac OS X should also be enabled so 
          that UNIX setup scripts can be run with the proper permissions. Mac 
          OS X Server is pre-configured with the root user account enabled. However 
          this account will generally need to be enabled with the client version 
          of Mac OS X. Open the Netinfo Manager application within the Applications/Utilities 
          directory. From the Security pull-down menu (at the top of the screen), 
          select the "Enable Root User" option. Enter the root password, 
          click the "Set" button, enter the root password again, click 
          the "Verify" button.
        Energy Saver features should be disabled to prevent the 
          loss of network connections due to the lack of user activity on the 
          server. Open the System Preferences pane, click on the Energy Saver 
          icon. Under the "Sleep" folder tab, drag the timeout slider 
          to "Never" for the "Put computer asleep..." feature. 
          Click on the "Options" folder tab and select the "Restart 
          automatically after a power failure." option.
        Either use the Utilities/Terminal application or use an 
          SSH connection to log into the Mac OS X server. Use "su - root" 
          to log in as root.
        1) Open the Installgen application.
        2) Enter appropriate database creation parameters in the 
          General, 
          Backup/Recovery, 
          Files/Tablespaces, 
          Options 
          and SGA 
          tabs.
        3) Create a folder or directory which will hold the files 
          created by Installgen.
        4) Verify that the Output directory field on the General 
          tab is correct.
        5) Select Save As from the File menu to save the configuration 
          information for this particular database server.
        6) Press the Generate button to generate the setup scripts/files.
        7) Log into the Mac OS X server, then execute the commands 
          in the file#1 
          script as the root user to create additional UNIX accounts.
        8) Insert the ora_build1 
          CD into the CD-ROM drive of the computer where Installgen was run.
        9) Copy or transfer the generated files from the Installgen 
          build directory where the files were generated to the UNIX oracle owner 
          home directory on the Mac OS X server where the database will be installed. 
          Also copy the Mail::Sendmail Perl module from the ora_build1 CD to the 
          UNIX oracle owner home directory.
        10) Make the file#3 
          script executable with the command:
          chmod +x file#3.
        11) Execute file#3 on the database server to set the file 
          permissions on the rest of the files in the /Users/oracle directory.
        12) Execute the file#4 
          script as root on the database server.
          This script requests permission to install the Mail::Sendmail Perl module. 
          The script creates and installs the /Library/StartupItems/Oracle/Oracle 
          startup script, oratab file, creates top-level directories for an OFA 
          directory structure to contain the Oracle datafiles and sets permissions/ownership 
          of these directories. Permission is requested and if granted, the script 
          creates/installs .bashrc, .bash_profile, /etc/profile files, creates/installs 
          /Users/oracle/server_scripts and rotateoraclefiles.sh script for rotating/removing 
          log files.
        13) Insert the Oracle installation CD into the server, 
          then execute the file#5 
          script as root. This script copies the and decompresses the macosx_920_dev_rel.tar.gz 
          from the CD.
        14) Execute the file#7 
          script to initiate the installation process using the Oracle Java based 
          installer on the server.
        15) Select "y" when prompted by the file#7 script 
          to start the process of building the database using script file#8. 
          This process may take several hours, depending upon the number of features 
          installed and the performance of the server.
        16) Execute the file#9 
          script to create Oracle dba accounts, change default database passwords, 
          apply the latest patchfile to the database, and configure backup and 
          recovery features.
        17) Perform a full backup of the database to test the 
          backup process (and a full export too if possible).
        
        
        