Code

Changes between Version 8 and Version 9 of OracleTestSetup


Ignore:
Timestamp:
11/14/10 05:16:31 (3 years ago)
Author:
ramiro
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • OracleTestSetup

    v8 v9  
    1010suite against Oracle by: 
    1111 
    12   * Providing a step by step setup guide to achieve that. 
    13   * Hopefully collecting information (best practices, tuning tips) to do that 
    14     as efficiently as possible. 
     12* Providing a step by step setup guide to achieve that. 
     13* Hopefully collecting information (best practices, tuning tips) to do that 
     14  as efficiently as possible. 
    1515 
    1616Chosen components are: 
     
    134134   ``sudo service xe start``) 
    135135 
    136 #. Make sure the Oracle environment vars needed by its client libraries 
    137    are set (Bash shell):: 
     136 
     137#. Make sure the Oracle environment vars needed by its client libraries are set. You need to do this in all systems 
     138   where you will be running client apps (e.g. the django test runner, the Oracle ''sqlplus'' CLI admin tool, etc.): 
     139   the system where the DB engine will run and/or other systems connected to it through the network (see next item). 
     140 
     141   I use the Bash shell, see the Oracle docs for instructions for other shells:: 
    138142 
    139143    $ echo "source /usr/lib/oracle/xe/app/oracle/product/10.2.0/server/bin/oracle_env.sh" >> ~/.bashrc 
    140144    $ source /usr/lib/oracle/xe/app/oracle/product/10.2.0/server/bin/oracle_env.sh 
    141  
    142145 
    143146#. Decide if you will perform the following two tasks 
     
    154157   * By default no access of any type (SQL sessions, admin web app) is allowed through the network to the DB engine, you need to change that by using the administrative web interface or possibly using the `sqlplus` tool. 
    155158 
    156 #. Access the DB engine administration web app by pointing our Web browser to ``http://localhost:8080/apex`` (or ``http://server:8080/apex``) 
     159#. Access the DB engine administration web app by pointing your Web browser to ``http://localhost:8080/apex`` (or ``http://server:8080/apex``) 
    157160   and using the ``SYSTEM`` user plus the password you chose above. 
    158161 
     
    244247 
    245248In my particular case I've implemented this setup by using a KVM virtual machine  
    246 (host system is a workstation running Debian unstable *Sid*). The VM got two CPUs, 1 GiB of RAM 
    247 and a 30 GiB hard disk. Platform is GNU/Debian Linux 5.0 aka *Lenny* (stable as of Nov 2010) 
    248 because it still is in its support period and as a bonus contains Python 2.4 in pre-packaged 
    249 form. 
     249(host system is a workstation running Debian unstable *Sid*). The VM got: 
     250 
     251* one CPU (Oralce XE won't use any additional CPU). 
     252* 512 MiB of RAM (initially it was 1GiB but the Django test suite execution doesn't push memory usage above that at all). 
     253* 30 GiB hard disk. 
     254 
     255Platform is GNU/Debian Linux 5.0 aka *Lenny* (stable as of Nov 2010) because it still is in 
     256its support period and as a bonus contains Python 2.4 in pre-packaged form. 
    250257 
    251258Things to review: 
    252259 
    253260* How much does the Oracle installation pollutes the system?. If it result to be confined and easy to undo/cleanup, maybe this setup doesn't need to be done inside a VM. 
    254 * System resource (CPU, RAM usage while running the full test suite). Maybe I can reduce the RAM assigned to the VM to 512 MiB and the virtual CPU count from two to one. 
    255261}}}