Initializing the Replication Agent Instance

Initialize the Replication Agent instance.

The pdb_xlog init command verifies that the primary IBM DB2 Universal Database is correctly configured to provide archived logging and that the IBM DB2 Universal Database user ID used by the Replication Agent has the necessary permissions. The pdb_xlog init command also creates objects in the primary database to support replication.

Note: If, in your resource file, you set initialize_instance to yes, skip step 1 and continue to step 2.

Initialize the Replication Agent instance:
```
pdb_xlog init
```
```
go
```
You see a message indicating that the procedure was successful.

Enter:

resume

go

If the Replication Agent successfully transfers to a replicating state, you see:

State        Action

-----------  -----------------------

REPLICATING  Ready to replicate data.

Replication Agent returns REPLICATION DOWN state if an error occurs:

1> resume
2> go
Msg 32000, Level 20, State 0:
Server 'rao', Procedure 'resume', Line 1:
Command <resume> failed - Desired state <REPLICATE>
could not be achieved. Current state: <REPLICATION
DOWN>

The ra_status command returns the state of the Replication Agent. It is good practice to verify that the Replication Agent remains in replication state, even after the resume command executes successfully.
To detect an error that occurred after replication start-up, execute:
```
ra_status
```
```
go
```
If the Replication Agent is in replicating state, ra_status returns:
```
State        Action
```
```
------------ -------------------------
```
```
REPLICATING  Ready to replicate data.
```
Replication Agent goes to the REPLICATION DOWN state if an error has occurs:
```
1> ra_status
```
```
2> go
```
```
State             Action
```
```
----------------- -------------------------
```
```
REPLICATION DOWN  Waiting for operator command.
```

Validate that both primary and replicate connections are active:

isql -Usa -P -SSAMPLE_RS

admin who

go

Note:

Be aware that:

The DSI connection for the primary database connection is usually down because you are not replicating data back to the primary database.
The Replication Agent connection, if established for the replicate database connection, is usually down, because you are not replicating data from the replicate database.

Do not proceed until admin who returns thread status similar to:

Spid Name  State Info

---- ----- ----- ---------------

--------------------------------

13 DSI EXEC Awaiting Command 101(1)

SAMPLE_RS_ERSSD.SAMPLE_RS_ERSSD

9 DSI Awaiting Message 101

SAMPLE_RS_ERSSD.SAMPLE_RS_ERSSD

8 SQM Awaiting Message 101:0

SAMPLE_RS_ERSSD.SAMPLE_RS_ERSSD

54 DSI EXEC Awaiting Command 102(1)

DCService.rdb

53 DSI Awaiting Message 102 DCService.rdb

17 SQM Awaiting Message 102:0 DCService.rdbDSI

EXEC Suspended 103(1) NY.NYudb9

DSI Suspended 103 NY.NYudb9

24 DIST Awaiting Wakeup 103 NY.NYudb9

25 SQT Awaiting Wakeup 103:1 DIST NY.NYudb9

23 SQM Awaiting Message 103:1 NY.NYudb9

22 SQM Awaiting Message 103:0 NY.NYudb9

62 REP AGENT Awaiting Command NY.NYudb9