Platforms and operating systems

The Mirror Replication Agent 15.0 software requires one of the platforms and operating system versions listed in Table 1-1.

A Mirror Replication Agent must be installed on a machine from which it can directly access the transaction logs of the primary database, or a mirror copy of those transaction logs.

**Table 1-1: Platform and operating system requirements**
Platform	Operating system version
HP 9000(8xx)	HP-UX 11i, 11iR2
IBM RISC System/6000	IBM AIX 5.2, 5.3
Linux/Intel x86	Red Hat Enterprise Linux 3.0: Kernel version 2.4.9-e.27 or later Red Hat Enterprise Linux 4.0: Kernel version 2.6.9-22.EL SuSE Linux Enterprise Server 9: Kernel version 2.6.5-7.191
Microsoft Windows 2000	Windows 2000 v.5.0.2195
Microsoft Windows Server 2003	Windows Server 2003 v.5.2.3790
Sun Solaris (SPARC) system	Sun Solaris 9, 10

Before you install the Mirror Replication Agent 15.0 software, you must install the most recent operating system patches recommended by your operating system vendor for Java 1.4.2 support.

Table 1-2 lists the minimum physical memory, storage, and media device requirements on the Mirror Replication Agent host machine. However, your Mirror Replication Agent configuration may require more memory and disk space than the minimums listed in Table 1-2.

Accommodating the RASD

Each Mirror Replication Agent instance uses an embedded Adaptive Server Anywhere database to manage its Mirror Replication Agent System Database (RASD).

Because the RASD stores information about primary database structure or schema objects, its size depends partly on the number of tables and procedures replicated, and the number of database users in the primary database.

**Table 1-2: Memory, disk space, and media device requirements**
Memory	Disk space	Media device
128MB RAM	300MB hard disk	CD-ROM drive

When it replicates a Data Definition Language (DDL) transaction, the Mirror Replication Agent creates a new version of the affected object’s metadata in its RASD. Over time, the size of the RASD can grow significantly, depending on the number and frequency of DDL transactions replicated.

If the RASD runs out of disk space, the Mirror Replication Agent will shut down and suspend replication. To prevent this, you must provide adequate disk space on the Mirror Replication Agent host machine to accommodate the initial size of the RASD, as well as some potential growth.

See the Mirror Replication Agent Administration Guide for more information about the RASD.