Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The 64 bit version of the minimal install of Centos 6.5 is used for the Rep Attack RepAttack operating system. This is a minimal install with no X Windows software or graphical user interface. The ISO image used for the install can be found by following the links on the Centos isoredirect page.

...

Warning

These machines have deliberately been configured with very little security. The passwords are the same as the userids, there is no SELinux or firewalls running. Treat them as disposable machines. In fact, you can remove them completely when finished as it only takes about 10 minutes to re-create them again if needed. Please don't use them for anything real.

 

 

Oracle Express Edition

Oracle Express Edition has already been installed via it's RPM package using all default values.
An additional tablespace called REPOE_DATA has been added to hold the application data used by Rep AttackRepAttack

It can be downloaded from the Oracle Database Express Edition 11g Release 2 downloads page. It requires you to sign up for a (free) Oracle Account if you don't already have one.

...

Each machine has the default Oracle XE database installed as it it's default configuration. The default database installed with Oracle XE always has the ORACLE_SID of XE but to make it less confusing between the source and target databases, two TNS alias have been set up in the tnsnames.ora files of both the source and target machines.

No Format
sourcettorcl_src =
  (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = source)(PORT = 1521))
    (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SERVICE_NAME = XE)
    )
  )
targetttorcl_trg =
  (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = target)(PORT = 1521))
    (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SERVICE_NAME = XE)
    )
  )
Tip
If you want to use these TNS entries on your host machine to connect to the databases, you will have to place source and target entries into the hosts file on the host machine or replace the hostnames with the hardcoded IP addresses.

Database User Passwords

These are the same on both the source and target databases. The passwords are set not to expire and are case sensitive in lowercase.

UsernamePassword
SYSchange_on_install
SYSTEMmanager
REPOErepoe
Tip

If you want to use these tns entries on your host machine to connect to the databases, you will have to place source and target entries into the hosts file on the host machine or replace the hostnames with the hardcoded IP addresses.

 

ARCHIVELOG Mode

One of the requirements for Dbvisit Replicate is that the source database be in ARCHIVELOG mode. The database on the RepAttack source machine has been placed into ARCHIVELOG mode and is using the USE_DB_RECOVERY_FILE_DEST as it's archive destination which is /u01/app/oracle/fast_recovery_area and has been sized at 10 Gb.

Warning

There is no automatic deletion of the archived redo log files from the source database.

The database on the RepAttack target machine is not in ARCHIVELOG mode.

SwingBench

SwingBench is a free load generator and benchmark utility designed by Dominic Giles to stress test an Oracle database (10g,11g,12c).  Rep Attack .  SwingBench version 2.5.0.932 has been installed on the RepAttack source machine in /u01/app/oracle/swingbench. RepAttack uses SwingBench to generate test data and provide a transaction load for the Dbvisit Replicate. 

 

REPOE Schema

The Rep Attack RepAttack machines come pre-loaded with an application schema and test data generated by SwingBench that you will 'll be using to perform the Rep Attack RepAttack exercises.

The schema is called REPOE and it's based on the Order Entry (OE) example schema that comes with Oracle. It's Entity Relationship diagram is shown below.

...

No Format
oewizard -cl -create -cs //source-int/orclXE -scale 0.5 -u repoe -p repoe -ts users -tc 7 -v -dba system -dbap manager

...

For example, this is the output of the script at the start of Rep AttackRepAttack. The source schema (REPOE) has been created with the tables and loaded with the initial data, while the target schema (also called REPOE) has been created but contains no tables.

No Format
[oracle@source replicate]$ ./record_count.bash
TABLE_NAME                     SOURCETTORCL_SRC DB   TARGET DB
TTORCL_TRG
------------------------------ ----------- -----------
ADDRESSES                      750000      *No Table*
CARD_DETAILS                   750000      *No Table*
CUSTOMERS                      500000      *No Table*
INVENTORIES                    900131      *No Table*
LOGON                          1191492     *No Table*
ORDERENTRY_METADATA            4           *No Table*
ORDERS                         714895      *No Table*
ORDER_ITEMS                    2143687     *No Table*
PRODUCT_DESCRIPTIONS           1000        *No Table*
PRODUCT_INFORMATION            1000        *No Table*
WAREHOUSES                     1000        *No Table*
11 rows selected.

Sum of orders         TTORCL_SRC SOURCE DB          TARGET DB
TTORCL_TRG
------------- ------------------ ------------------
ORDERS         $3,572,944,731.00               $.00
[oracle@source replicate]$

...

In the $HOME/replicate directory of the oracle user on the source machine is a script called run_swingbench.bash. This script is used on the source machine to generate DML transactions against the REPOE schema so Dbvisit Replicate has something to do.

...

Info

Sounds funny, but the Rep Attack RepAttack machines don't come with Dbvisit Replicate installed! The first exercise after you have the source and target machines running is to install Dbvisit Replicate.