How to Mount USB storage in Solaris

Some times your Solaris operating System won't mount automatically, so you have mount manually.

Below are some simple steps to mount the USB storage device manually.

Step 1: Make sure that your USB storage is using FAT file system

Step 2: Check whether your Solaris operating system detected USB storage by executing below command

SPARC
          #rmformat

x86
         #fdisk -l
           Device       Boot      Start      End      Blocks      Id  System
            /dev/sdb1     *           1        1016     3903763+   b  W95 FAT32

Step 3: Verify whether the USB storage is automatically mounted or not
   
          #df -h

Note: if not mounted, then follow the below steps.

Step 4: Choose the existing empty mount point or create new mount point, here i'm using "/mnt" which is a empty mount point.

         #ls -l /mnt

         total 0

         #mount -F pcfs /dev/dsk/c2t0d0s2:c /mnt

   pcfs - Solaris file system

   c2t0d0s2 - is the device name, you will get this name when you run "rmformat"
   ":c" - it will search for fat file system.

Step 5: Verify whether the USB storage is mounted or not

          #df -h

Mount NTFS file system in Linux/Unix

There is a situation you need to mount USB Hard Disk into Linux Server, below are the simple steps to mount USB Hard Disk.

Step 1: download the ntfs-3g package from tuxera

Step 2: copy to Linux server if you downloaded from different machine.

Step 3: I have copied to the /opt folder

            [root@Server opt]#tar zxvf ntfs-3g-xxxx.tgz

Step 4: Compile & install the ntfs-3g package.

            [root@Server opt]#cd ntfs-3g-xxxx

            [root@Server ntfs-3g-xxxx]#./configure

            [root@Server ntfs-3g-xxxx]#make

            [root@Server ntfs-3g-xxxx]#make install

Step 5:After successful installation you can mount the NTFS file system in Linux

           You can identify the NTFS Hard Disk by executing below command.

           [root@Server ~]#fdisk -l

           Create mount point for the NTFS Hard Disk.

           [root@Server ~]#mkdir /mnt/ntfs

           After identifying the NTFS Hard Disk, you can mount the partition using below command.

           [root@Server ~]#mount -t ntfs-3g /dev/sdb1 /mnt/ntfs

          You can verify the mounted devices by using below command.

           [root@Server ~]#df -h

SSH Login Without Password

You can login to remote without password, these is very useful when you want to schedule remote copy process.
This is easy to setup, just follow the below steps...

Scenario:- You want to schedule copy process from Server A using user account ram to Server B to krish home directory.

Step 1:- Login to System B using krish account.
             krish@ServerB$pwd
             /export/home/krish
Note:- On solaris system user home directory will be under /export/home
           On linux system user home directory will be under /home

Step 2:- Generating public/private key pair using ssh-keygen
            krish@ServerB$ssh-keygen -t rsa
            Generating public/private rsa key pair.
            Enter file in which to save the key (/export/home/krish/.ssh/id_rsa):
            [Enter]
            Created directory '/export/home/krish/.ssh'.
            Enter passphrase (empty for no passphrase): [Enter]
            Enter same passphrase again: [Enter]
            Your identification has been saved in /export/home/krish/.ssh/id_rsa.
            Your public key has been saved in /export/home/krish/.ssh/id_rsa.pub.
            The key fingerprint is:
            62:65:7f:32:ff:33:a4:ae:5f:f5:14:b1:da:5d:7b:24 krish@ServerB

           krish@ServerB$ ls -la .ssh/
           total 8
           drwx------   2 krish    other        512 Dec 25 17:39 .
           drwxr-xr-x   3 krish    other        512 Dec 25 17:38 ..
           -rw-------   1 krish    other        887 Dec 25 17:39 id_rsa
           -rw-r--r--   1 krish    other        223 Dec 25 17:39 id_rsa.pub

Note:- Here -t is the type of algorithm (rsa or dsa)

Step 3:- Now we have to copy public key to Server A, ram home directory under .ssh folder
          krish@ServerB$cd .ssh
          krish@ServerB$pwd
          /export/home/krish/.ssh
          krish@ServerB$scp id_rsa.pub ram@ServerA:/export/home/ram/.ssh/

Step 4:- Login to Server A as ram user & copy content inside id_rsa.pub to authorized_keys
          ram@ServerA$cd .ssh
          ram@ServerA$pwd
          /export/home/ram/.ssh
          ram@ServerA$ls -la

          total 6
          drwxr-xr-x   2 ram      other        512 Dec 25 18:02 .
          drwxr-xr-x   3 ram      other        512 Dec 25 18:01 ..
          -rw-r--r--   1 ram      other        223 Dec 25 18:02 id_rsa.pub
          ram@ServerA$cat id_rsa.pub
          ssh-rsa                 AAAAB3NzaC1yc2EAAAABIwAAAIEA1oGmYkRu9/mijvJPSeYprcvDZfJzM21o/BmfSkoLn4rwkSNGg1KIdmXyzKiQcu3kKHNjMe9f6nL8gKOD5Wa2GWfoeac/CPEkD/Q/laS8oP4XwXCHsYO/lLiJ8w3JPg/fzDimUPLcLR50S7jFziP/dzMJTx8aUnAhmc+pQiUfLw8= krish@ServerB
          ram@ServerA$cat id_rsa.pub > authorized_keys
          ram@ServerA$cat authorized_keys

ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAIEA1oGmYkRu9/mijvJPSeYprcvDZfJzM21o/BmfSkoLn4rwkSNGg1KIdmXyzKiQcu3kKHNjMe9f6nL8gKOD5Wa2GWfoeac/CPEkD/Q/laS8oP4XwXCHsYO/lLiJ8w3JPg/fzDimUPLcLR50S7jFziP/dzMJTx8aUnAhmc+pQiUfLw8= krish@ServerB

Step 5:- Testing from Server A to Server B
ram@ServerA$scp test.txt krish@ServerB:/export/home/krish

Note:- without asking the password, it will copy the file test.txt from ServerA to ServerB

Basic Cisco Router Configuration

The basic CLI modes that we will be referring below are as following:

When you connect to the router it will enter into User EXEC mode

Router> ← User EXEC Mode

To Enter into Privileged EXEC mode

Router> enable (if password is enabled it prompt for password)

Router# ← Privileged EXEC mode

To Enter into Global Configuration mode

In Global Configuration Mode you configure parameters that affect the whole router device

Router# Config terminal

Router(config)# ← Global Configuration Mode

To Configure any Interface

Router(config)# Interface Serial1

Router(config-if)# ← Interface Configuration Mode

To Configure Line Interface

Router(config)# line vty 0

Router(config-line)# ← Line Configuration Mode

The first step is to secure your access to the router by configuring a global secret password and also passwords for Telnet or Console

Router# Config terminal

Here we will configure the Enable Secret password for Privileged EXEC Mode

Router(config)# enable secret "secretpassword"

Router(config)# end

Configuring password for the Telnet Lines (VTY lines) which will secure your access when connecting via Telnet

Router(config)# line vty 0 4

Router(config-line)# password "Telnetpassword"

Configuring Hostname for your device

Router(config)# hostname "Routername"

Routername(config)#

Network Load Balancer (NLB)

The Network Load Balancing Manager is a stand-alone management application that you use to create and manage NLB clusters from a single management point

Configuring NLB on the First Host (Primary Application Server)

1. If you are configuring NLB on windows 2008 you need to check NLB driver version it should be (6.0.6001.22374), other wise install NLB patch (Windows6.0-KB960916-x64).
2. Launch the Network Load Balancing Manager (Start -> All Programs -> Administrative Tools).
3. Under the Cluster Menu option select New.

1. Enter the first node in the Cluster (Server1 IP).
2. Click Connect.
3. You will have the option to choose which network adapter you want to use; the NIC should be on the same subnet as the other servers in the NLB cluster
4. Click Next.
5. Enter the Priority ID as, 1 (each node in the NLB cluster should have a UNIQUE ID).
6. Make sure the correct adapter was selected under "Dedicated IP Address".
7. Select "Started" for the "Initial host state" (this tells NLB whether you want this node to participate in the cluster at start-up).
8. Click Next.
9. Click Add.

9.1 Enter the Cluster IP (192.168.1.250).

9.2 Enter the Subnet mask (255.255.255.0).

9.3 Click OK.

10. Click Next.
11. Select the IP Address for this cluster.
12. Enter the Full Internet Name (www.example.com).
13. Select Multicast as the "Cluster operation mode".
14. Click Next.
15. Click the Edit button.
16. Select the Single Host from the Filtering Mode and click OK.
17. Click the Finish button.
18. You should see a couple of things in the NLB Manager; this will let us know that this node successfully converged on our new Server1 NLB Cluster.

18.1 Make sure the node’s status changes to Converged.

18.2 Make sure you see a Succeeded message in the log window.

Configuring NLB on the Second Host (Secondary Application Server)

1. Right click the cluster name and select Add Host to Cluster.

1. Enter Server2 and Click Connect.
2. Select the network adapter you want to use for Load Balancing.
3. Click Next.
4. Enter the Priority ID as, 2 (each node in the NLB cluster should have a UNIQUE ID).
5. Make sure the correct adapter was selected under "Dedicated IP Address".
6. Select "Started" for the "Initial host state" (this tells NLB whether you want this node to participate in the cluster at start-up).
7. Click Next.
8. Click Finish.
9. You should see a couple of things in the NLB Manager; this will let us know that both nodes successfully converged on our new Server2 NLB Cluster.

9.1 Make sure that both nodes’ status changes to Converged.

9.2 Make sure each node has a unique host priority ID.

9.3 Make sure each node is started under initial host state.

9.4 Make sure you see a Succeeded message in the log window for the second node.

NLB Verification

• Go to the command prompt and type "wlbs query", as you can see HOST 1 and HOST 2 converged successfully on the cluster. This means things are working well.
• Ping each server locally and remotely.
• Ping the virtual IP locally and remotely – you should do this three times from each location. If you cannot ping remotely you may need to add a static ARP entry in your switches and/or routers where the host machines reside.
• 1 – Both nodes up
• 2 – Node 1 down
• 3 – Node 2 down

NOTE: Add the Virtual IP and the Virtual Hostname to the DNS Server to be able to Ping or Access the servers via the Virtual Hostname.

DB2 SQL Replication

SQL replication Keywords Explanation and Basic Terms

Source Database

The replication source is the table in a database from which you want to extract data to replicate to a table in your replication target

Capture Control

The Capture program records changes to the tables that you register as source tables

Capture control tables must be created in the source database

Apply Control

Apply control tables. These tables will store information that the Apply program needs to know to apply changes to the target.

Target Database

The replication target is the table in a database to which you want to replicate data from your replication source

Registered Tables

After you create a set of Capture control tables, you can tell the Capture program which tables you want to replicate by registering them. These tables will be your source tables

Subscription Sets

A subscription set defines the relationship between the replication source database and a target database

Subscription-set member

Subscription-set member defines the relationship between the replication source tables and one or more target tables

CDTable

(Change Data Table) The Replication Center creates a change-data (CD) table, which the Capture program uses to record changes made to the registered table.

Networking requirements

A system running the Replication Center must be able to access:

All DB2 Capture Control Servers, Apply Control Servers, Monitor Servers, and DB2 target servers

Requirements at replication servers

DB2 on the systems with the Capture Control tables, Apply Control Tables, Monitor Control Tables, and the target tables needs to be able to accept connections from the DB2 Client on the Replication Center workstation and you will need a user id on those systems that can read the DB2 system catalog, create Capture, Apply, and Monitor Control tables, staging tables and target tables.

The Replication Center user will also need a user id on these systems that can read the DB2 system catalog, can create the Capture, Apply, Monitor, staging and target tables, and can bind packages.

Installing DB2 Server for SQL Replication

To install a DB2 Server or DB2 Connect product, it should be with an account in the Administrators group

Before Configuring SQL Replication we need to catalog entries for the remote system on both the servers

Note: Be sure to use the user ID that you used to create the Source DB and Target DB databases. That user ID has the authority (DBADM or SYSADM) that is required to perform replication tasks.

Commands to catalog remote entries on Source server (SERVER1)

Ø db2 catalog admin tcpip node SERVER2 remote SERVER2 system SERVER2 [ostype WIN]

Ø db2 catalog tcpip node DB2_SERVER2 remote SERVER2 server 50000 remote_instance DB2 system SERVER2 [ostype NT64]

Ø db2 catalog database MDS_DR as MDS_DR at node SERVER2

Commands to catalog remote entries on Target server (SERVER2)

Ø db2 catalog admin tcpip node SERVER1 remote SERVER1 system SERVER1 [ostype WIN]

Ø db2 catalog tcpip node DB2_SERVER1 remote SERVER1 server 50000 remote_instance DB2 system SERVER1 [ostype NT64]

Ø db2 catalog database MDS as MDS at node SERVE

Planning the SQL Replication

Replication options

You can choose replication options that, for example, determine where the change-data (CD) table, target table, and control tables are stored, how often you want replication to occur,

and which records (based on the criteria you specify) you want to delete from the IBMSNAP_APPLYTRAIL table after each replication cycle.

For the purpose of this tutorial, store the CD table, the target table, and the control tables in their respective default table spaces.

Typically, you create the CD table in a table space separate from that of the source table space (USERSPACE1) to reduce potential contention at the table-space level. To do so, accept the defaults (or define a profile within the Replication Center) for the table spaces of the replication control tables. In a production environment, be sure to create each table space on a separate device to reduce potential contention.

For this tutorial, schedule SQL replication to check for any changes in the source table every minute, and then replicate the changes to the target table. Although a report-generating application does not require this frequency of checking, for this tutorial, you want to be able to test the replication environment and verify that everything is working correctly.

Also, you decide that after each replication cycle, you want to delete any records from the IBMSNAP_APPLYTRAIL table that are older than one week (seven days). This pruning prevents the table from growing too large.

Replication source

The replication source is the table in a database from which you want to extract data to replicate to a table in your replication target. Before you set up your environment, you must decide what you want to replicate from that table.

Replication target

The replication target is the table in a database to which you want to replicate data from your replication source. You can create a new table in your target database or use an existing target table. For this tutorial, you will create a new table.

The replication target will be a table in the new database, MDS_DR, which you created. Currently, no target table exists in that database, and you decide to use the Replication Center to create the target table according to your specifications. This method of automatically generating a target table is preferred because it ensures correct mapping to the replication source.

Setting up the replication environment

After planning the replication model, the next steps you complete in this tutorial involve setting up the replication environment.

Because almost all of the following steps use the Replication Center, be sure that it is running. From the Windows® Start menu: select Start > All Programs > IBM DB2 > DB2_copy > General Administration Tools > Replication Center

Step 1: Create control tables for the Capture program

The first step in setting up the replication environment is to create control tables for the Capture program.

About this task

The Capture program reads the control tables for current registration information and then stores its status in these tables. Any database that acts as a Capture control server must contain the Capture control tables.

Procedure

To create Capture control tables:

1. Expand the SQL Replication folder.
2. Expand the Definitions folder.
3. Right-click the Capture Control Servers folder and select Create Capture Control Tables > Quick. (You could also customize the Capture control tables by selecting Create Capture Control Tables > Custom.)
4. In the Select a Server window, select the MDS database. This database will be your Capture control server. Click OK.
5. In the Create Control Tables - Quick - Server Information window, select Host sources for replication and capture changes to those sources. Then, click Next.
6. In the Create Control Tables - Quick - Replication Details window, click Next. You do not need to change any of the information in this window.
7. In the Create Control Tables - Quick - Table Spaces window, enter the table space specification for the TSASNCA table space. For example, set the buffer pool to IBMDEFAULTBP. For the purposes of this tutorial, click OK and accept the default control table schema, ASN.
8. In the Create Control Tables - Quick - Table Spaces window, enter the table space specification for the TSASNUOW table space.
9. After you enter information for both table spaces in the Create Control Tables - Quick - Table Spaces window, click OK.
10. Click Close on the Messages and SQL Scripts window. This window shows the results of generating the SQL script that creates the Capture control tables. If there are any errors, they are displayed in this window.
11. Enter a valid user ID and password in the Run Now or Save SQL window and click OK to process the SQL script immediately. You should see a message in the DB2® Message window stating that the script ran successfully.
12. Click Close.
13. Expand the Capture Control Servers folder. The MDS database should be displayed under the folder.

Note: If your database is already in Archive log mode skip step 2

Step 2: Enable the source database for replication

The next step is to enable the source database for replication. The Capture program reads the DB2® log for records that reflect changes to registered tables. The log must be an archive log type (as opposed to a circular log type) to avoid having DB2 overwrite the log before the Capture program can read it.

About this task

For Linux®, UNIX®, and Windows® environments, the DB2 default is circular logging. Use the following procedure to change this setting to archive logging.

Procedure

To enable the source database for replication:

1. Expand the Capture Control Servers folder.
2. Right-click the MDS database and select Enable Database for Replication.
3. Click OK on the Enable Database for Replication window to use archive logging for the MDS database and to initiate a backup for the database.
4. In the Backup window, specify the information for the database backup, and click Backup Now.

After you back up the database, you could start the Capture program. However, for this tutorial, do not start it yet.

Step 3: Register a replication source

After you create the Capture control tables and enable the database for replication, you need to register the table in your replication source database as a replication source.

About this task

Use the following steps to register the tables in the MDS database as a replication source. When you register the table, a change-data (CD) table named CDTABLENAME (example EMP table will be CDEMP) is automatically created to receive changes from the registered source table. The Apply program then fetches the changes from the CD table.

Procedure

To register a table as a replication source:

1. Expand the SQL Replication folder.
2. Expand the Definitions folder.
3. Expand the Capture Control Servers folder.
4. Expand the MDS database.
5. Expand the Capture Schemas folder.
6. Expand the ASN schema.
7. Right-click the Registered Tables folder and select Register Tables.
8. In the Add Registerable Tables window, click Retrieve All to list all of the tables in the MDS database that you can register as replication sources. Select the tables and click OK
9. In the Register Tables window, click the CD Table tab. Specify the following information for the CD table space:
10. In the Specification for the table space area, clicke the container name field and specify the container name for the TABLESPACE (use existing table space name) table space.
11. In the Specification for table space area, change the Size field entry to.
12. In the Specification for table space area, change the Unit field entry to MB.
13. Specify the other information for this new table space; for example, set the buffer pool to IBMDEFAULTBP.
14. After you enter the table-space information, click OK.
15. Click OK on the Run Now or Save SQL window to process the SQL script immediately. You should see a message in the DB2® Message window stating that the script ran successfully.
16. Click Close.
17. The contents pane for the MDS database folder should now show the selected tables as a registered table.

The selected tables are now defined as a replication source. When you ran the SQL script, the Replication Center creates the CD tables and CD-table indexes for this replication source, and it updated the Capture control tables

Step 4: Create control tables for the Apply program

After you create control tables for the Capture program, you need to create control tables for the Apply program.

About this task

The Apply program reads the control tables for current subscription-set information and stores its status in these tables. Any database that acts as an Apply control server must contain the Apply control tables.

Procedure

To create Apply control tables:

1. Expand the SQL Replication folder.
2. Expand the Definitions folder.
3. Right-click the Apply Control Servers folder and select Create Apply Control Tables > Quick. Alternatively, you could customize the Apply control tables by selecting Create Apply Control Tables > Custom.
4. In the Select a Server window, select the MDS_DR database. This database will be your Apply control server. Click OK.
5. In the Create Control Tables - Quick - Server Information window, select Apply captured changes to target tables and then click Next.
6. In the Create Control Tables - Quick - Replication Details window, click Next. You do not need to change any of the information in this window.
7. In the Create Control Tables - Quick - Table Spaces window, enter the table space specification for the TSASNAA table space. For example, set the buffer pool to IBMDEFAULTBP. Click OK.
8. Click Close on the Messages and SQL Scripts window. This window shows the results of generating the SQL script that will create the Apply control tables. If there are any errors, they are displayed in this window.
9. Enter a valid user ID and password in the Run Now or Save SQL window and click OK to process the SQL script immediately. You should see a message in the DB2® Message window stating that the script ran successfully.
10. Click Close.
11. Expand the Apply Control Servers folder. The MDS_DR database should be displayed under the folder.

Step 5: Create a subscription set and a subscription-set member

After you register the source table, you need to create a subscription set and a subscription-set member to define relationships between the replication source database and a target database and between the replication source table and one or more target tables.

About this task

A subscription set defines the relationship between the replication source database (MDS in this tutorial) and a target database (MDS_DR in this tutorial). A subscription-set member defines the relationship between the replication source tables and one or more target tables

Procedure

To create a subscription set and a subscription-set member:

1. Expand the SQL Replication folder.
2. Expand the Definitions folder.
3. Expand the Apply Control Servers folder.
4. Expand the COPYDB database.
5. Right-click the Subscription Sets folder and select Create.

You can also create a subscription set by selecting the Registered Tables folder of the SAMPLE database, right-clicking the DEPARTMENT table in the contents pane, and selecting Create Subscription Set.

6. In the Set Information page of the Create Subscription Set window, enter the following information:
1. In the Set name field, enter MDS_DR_SUB. This string identifies the subscription set and must be unique for a particular Apply qualifier.
2. In the Apply qualifier field, enter MDS_DR_QUAL. This string identifies the replication definitions that are unique to the instance of the Apply program that will run this subscription set.
3. Tip: The Apply qualifier is case-sensitive. If you want the Apply qualifier to be in lowercase characters, you must delimit it when you type it; for example,
   "mds_dr_qual". If you simply type mds_dr_qual, the Replication Center converts the value to uppercase characters by default.
4. Click the browse button [...] for the Capture control server alias field. In the Select a Capture Control Server window, select the MDS database and click OK.
5. Click the browse button [...] for the Target server alias field. In the Select a Target Server window, select the MDS_DR database and click OK. The MDS_DR database is both the target server and the Apply control server.
6. Select the Activate the subscription set check box.

7. On the Source-to-Target Mapping tab of the Create Subscription Set window, enter the following information:

1. Click Add to add a registered source to the subscription-set member.
2. In the Add Registered Sources window, click Retrieve All to display all registered sources in the MDS database.
3. In the Add Registered Sources window, select the tables and click OK.
4. In the Source-to-Target Mapping tab of the Create Subscription Set window, change the name of the target table by removing TG (TGEMP to EMP: select TGEMP in the Target Name column of the Subscription-set members table, and change it to EMP)

Do not change the target type because you want to create a user copy target table.

5. Click Change to open the Member Properties window. From this window, you can define the properties for the subscription-set member.

Because, for the purposes of this tutorial, you want to replicate all columns and create the same columns in the target table as in the source table, you do not need to make any changes to the Column Selection or Column Mapping tabs of the Member Properties window. By default, the target table contains all of the columns that you registered for the source.

Tip for federated: If your company's replication configuration maps a source table to an existing target table and at least one of the tables is from a non-DB2 relational database, see the Federated Systems Guide for more information on how to map the source columns to columns in the existing target table.

8. On the Target-Table Index tab of the Member Properties window:

1. Click Create your own index.
2. Select the any column from the Available columns in the target list.
3. Click the move button (>) to move the selected column to the Columns used in the index list.
4. Make sure that Use selected columns to create primary key is selected to use the any one column as the primary key for the target table.

9. On the Target-Table Table Space tab of the Member Properties window, specify the following information for the existing table space.
10. Click OK to close the Member Properties window. For the purposes of this tutorial, you do not need to do anything on the Target load options tab.
11. On the Schedule tab of the Create Subscription Set window, change the number of minutes to 1 so that the Apply program will process this subscription set every minute. To change the number of minutes, use the spin button on the Minutes field in the Frequency of replication area to select one-minute intervals (or type 1 in the field).

Keep the default values for Start date, Start time, Time-based, and Use relative timing.

12. On the Statements tab of the Create Subscription Set window, click Add to open the Add SQL Statement or Procedure Call window. Use this window to define the SQL statements that will be processed when the subscription set is run. In the Add SQL Statement or Procedure Call window, enter the following information:

1. In the SQL Statement field, enter:
2. DELETE FROM ASN.IBMSNAP_APPLYTRAIL WHERE LASTRUN < (CURRENT TIMESTAMP - 7 DAYS)

This statement deletes any records in the IBMSNAP_APPLYTRAIL table that are older than seven days.

The Apply program executes the SQL statement that you added at the target server after the subscription set is processed. The SQL statement must run on the target server because the Apply control server and target server are co-located, and the IBMSNAP_APPLYTRAIL table is on the Apply control server.

Tip: The Apply program runs SQL statements or procedures that you add to a subscription set during every subscription cycle. This example is inefficient because the Apply program will execute this statement every minute, even though the statement will only delete data from the IBMSNAP_APPLYTRAIL table, at most, once every 24 hours.

a. In the SQLSTATE field, enter 02000 and click Add. This SQL state indicates that a "row not found" error is acceptable and that the Apply program should ignore such errors.

Tip: You can define as many as ten SQL states that you want the Apply program to ignore for this subscription set.

b. Click OK to close the Add SQL Statement or Procedure Call window.

13. Click OK to close the Create Subscription Set window.
14. Click Close on the Messages and SQL Scripts window. This window shows the results of generating the SQL script that will update the Apply control tables and create the target table. If there are any errors, they are displayed in this window.
15. Click OK on the Run Now or Save SQL window to process the SQL script immediately.

Alternately, to save the SQL script to a file for future uses and also run it now:

1. Select Save to file.
2. Fill in the information in the Save specifications area, such as the file name.
3. Click Apply to save the file. If the script has multiple parts, and you did not select the Save multiple scripts in one file check box, each part is saved to a separate file that uses the name that you specify plus a number. The Run Now or Save SQL window remains open.
4. Select Run now.
5. Click OK to run the script and close the Run Now or Save SQL window.

You should see a message in the DB2® Message window stating that the script ran successfully at both the MDS and MDS_DR servers.

16. Click Close

17. Expand the Apply Control Servers folder and the MDS_DR database, and then click the Subscription Sets folder. The contents pane for the Subscription Sets folder should now show the MDS_DR_SUB subscription set.

Step 6: Create an Apply password file

Because the Apply program needs to connect to the Capture control server, the Apply control server, and the target server, you must create a password file for user authentication. Because the contents of the password file are encrypted, only the Apply program can read the file, although you can modify the file.

Procedure

To create an Apply password file:

1. Open a Windows® command prompt window and change to the C:\..\sqllib\bin directory.
2. Enter the following command to create a default password file:

3. asnpwd init using " path"

Where path is the fully specified directory path and file name that you want to use when you create the password file. You should see message ASN1981I, confirming that the command completed successfully.

For example, if you want to store the password file in the c:\repl directory and name the file asnpwd.aut, enter the following command:

asnpwd init using "c:\repl\asnpwd.aut"

Where c:\repl\asnpwd.aut represents the fully specified directory path and file name of the password file.

Tip: Create the password file in the directory in which you will start the Apply program. When you start the Apply program, you specify the file name for the password file (using the PWDFILE keyword) and the value for the directory in which the Apply program will store its log and work files (using the APPLY_PATH keyword). One of the Apply program's work files is the password file.

Enter the following command to add the user ID and password information for each

database to which the Apply program must connect:

asnpwd add alias MDS id db2admin password db2admin using "c:\repl\asnpwd.aut "

Where userid is a valid DB2® user ID with sufficient authority to update the Capture and Apply control tables, password is the password for the valid DB2 user ID, and path is the fully specified directory path and file name that you entered when you created the password file. You should see message ASN1981I, confirming that the command completed successfully.

Step 7: Replicate the data for the tutorial scenario

After you register the replication source and create the subscription set, you are ready to replicate the data for this tutorial.

Procedure

To start the Capture and Apply programs, which will perform the initial full refresh for the target table and begin change-capture replication:

1. Start the Capture program:
1. Expand the SQL Replication folder.
2. Expand the Operations folder.
3. Select the Capture Control Servers folder. The SAMPLE database should be displayed in the contents pane for Capture control servers.
4. Right-click the MDS database and select Start Capture.
5. In the Start Capture window, select ASN in the Capture schema field.
6. Click OK on the Start Capture window.
7. When prompted, insert the user ID and password in the Run specifications section, and then Click OK on the Run Now or Save Command window to process the command immediately.
8. You should see a message in the DB2® Message window stating that the command ran successfully. Click Close. The Capture program is now running, but will not begin capturing changes for registered tables until the Apply program completes a full refresh for all registered tables.
2. Start the Apply program

1. Expand the SQL Replication folder.
   
2. Expand the Operations folder.
3. Expand the Apply Control Servers folder.
4. Expand the MDS_DR database.
5. Select the Apply Qualifiers folder. The MDS_DR_QUAL Apply qualifier for subscription set MDS_DR_SUB should be displayed in the contents pane for Apply qualifiers.
6. Right-click the MDS_DR_QUAL Apply qualifier and select Start Apply.
7. In the Start Apply window, click the browse button for the Where Apply is running field to select the system or IP address on which to run the Apply program.
8. Click OK on the Start Apply window.
9. If necessary, type a valid user ID and password for the system on which you will run the Apply program in the Run Now or Save Command window.
10. Click OK on the Run Now or Save Command window to process the command immediately.
11. You should see a message in the DB2 Message window stating that the command ran successfully. Click Close. The Apply program is now running.

If you view the target tables after one replication cycle, you should see results that match the source data. You can use any of the following methods to view the contents of the table:

• Use the Replication Center:
1. Expand the SQL Replication folder.
2. Expand the Definitions folder.
3. Expand the Apply Control Servers folder.
4. Expand the MDS_DR database.
5. Right-click the Dependent Targets folder and select View Selected Contents.
• Use the DB2 Control Center:
1. Expand the databases folder for your DB2 instance.
2. Expand the MDS_DR database.
3. Select the Tables folder.
4. Right-click the any table in the contents pane and select Sample Contents.
• Use the DB2 Command Center or a DB2 command window to issue the following SQL statement:

SELECT * FROM schema.TABLENAME