000027505 - Checking the RSA Authentication Manager CAPTURE  APPLY and PROPAGATION queues.

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000027505
Applies ToRSA Authentication Manager 7.1 Service Pack 4
RSA SecuriD Appliance 3.0 Service Pack 4
Replication.
IssueChecking the RSA Authentication Manager CAPTURE, APPLY and PROPAGATION queues.
Replication status shows 'Needs Action'.
Data is no longer being replicated between the primary and replica instances.
Resolution

Checking the CAPTURE, APPLY and PROPAGATION queues

 

In an effort to investigate a replication issue the following information will generate an HTML report on the status of the replication queues and whether these queues have any relating errors. The returned HTML report may determine if a reset is required on the replication between the primary and replica instances or whether the appropriate queue can be stopped and started to release the error condition.

 

Further commands on stopping and starting the CAPTURE, APPLY and PROPAGATION queues is found in the Diagnostic Evidence Worksheet (DEW) found in knowledge article a61006.

 

Below is the SQL script and usage instructions that will help determine if the CAPTURE, APPLY and PROPAGATION queues on any RSA Authentication Manager 7.1 software deployment have any errors.

 

SQL script code:

 

set markup HTML ON entmap off

alter session set nls_date_format='HH24:Mi:SS MM/DD/YY';

spool Qreport.html;

set heading off

 

set heading on timing off

set lines 180

set numf 9999999999999999

set pages 9999

 

prompt

prompt ++ Replication Queue Check ++

COL LOGINUID FORMAT A10

 

select status, capture_name, error_message from dba_capture;

select status, apply_name, error_message from dba_apply;

select status, propagation_name, error_message from dba_propagation;

 

set timing off

 

set markup html off

clear col

clear break

spool

spool off

 

 

NOTE: the commands in the script can also be found in a Diagnostic Evidence Worksheet (DEW); knowledge article a61006

 

Usage:

 

1.

Acquire the password allowing for database access with the SQLplus program in a command prompt window.

 

Open a Command Prompt and navigate to the <AMHOME>/utils folder and run the following commands as the user who has file ownership of the RSA Authentication Manager 7.1 software.

 

UNIX Usage

./rsautil manage-secrets -a get com.rsa.db.root.password

Enter Master password: ***********

com.rsa.db.root.password: <password>

Windows Usage

rsautil manage-secrets -a get com.rsa.db.root.password

Enter Master password: ***********

com.rsa.db.root.password: <password>

 

Setup the environment using the rsaenv program found in the <AMHOME>/utils folder

 

UNIX Usage

. ./rsaenv

Windows Usage

rsaenv.cmd

 

 

NOTE: <AMHOME> by default on a supported Windows platform is C:\Program Files\RSA Security\RSA Authentication Manager and on supported UNIX platforms (& SecurID Appliance) /usr/local/RSASecurity/RSAAuthenticationManager

 

2.

In the <AMHOME>/utils folder create a text file called Qcheck.sql and copy the SQl script above into that text file.

 

3.

Use the sqlplus program to run the script using the following instructions.

 

Connect to the RSA Authentication Manager database with the sqlplus program from the <AMHOME>/utils folder using the command: sqlplus sys/<password> as sysdba

 

NOTE: substitute <password> with the com.rsa.db.root.password found earlier.

 

Example:

 

sqlplus sys/<password> as sysdba

 

SQL*Plus: Release 10.2.0.5.0 - Production on Wed Mar 27 10:17:54 2013

 

Copyright (c) 1982, 2010, Oracle.  All Rights Reserved.

 

 

Connected to:

Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - Production

With the Partitioning, Data Mining and Real Application Testing options

 

SQL>

 

 

Enter the command @Qcheck.sql to run the SQL script

 

Example:

 

SQL> @Qcheck.sql

 

 

You will notice HTML code being displayed and you are returned to a SQL > prompt

 

Example:

 

?

?

?

ENABLED

</td>

<td>

RSA_STREAMS_PROPAGATION_7

</td>

<td>

 

</td>

</tr>

<tr>

<td>

ENABLED

</td>

<td>

RSA_STREAMS_PROPAGATION_8

</td>

<td>

 

</td>

</tr>

</table>

<p>

 

currently spooling to Qreport.html

SQL>

 

 

To leave the sqlplus program type in the command exit

 

Example:

 

SQL> exit

Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - Production

With the Partitioning, Data Mining and Real Application Testing options

-bash-3.00$

 

 

 

4.

A report file called Qreport.html is generated in the <AMHOME>/utils folder

 

Display the report in a web browser

 

Should there be any errors in the ERROR_MESSSAGING column or the STATUS column shows ERROR or ABORTED for any of the queues then there is need for further action.

 

5.

 

Further action will initially require using SQL commands to stop/start and re-check the status of the CAPTURE, APPLY and PROPAGATION queues

 

CAPTURE stop command

EXEC DBMS_CAPTURE_ADM.STOP_CAPTURE(capture_name => 'RSA_STREAMS_CAPTURE');

CAPTURE start command

EXEC DBMS_CAPTURE_ADM.START_CAPTURE(capture_name => 'RSA_STREAMS_CAPTURE');

CAPTURE status command

select status, capture_name, error_message from dba_capture;

APPLY stop command

EXEC DBMS_APPLY_ADM.STOP_APPLY(apply_name => '<APPLY_NAME>');

 

** where <APPLY_NAME> is the actual name of the APPLY queue displayed in the HTML report **

 

APPLY start command

EXEC DBMS_APPLY_ADM.START_APPLY(apply_name => '<APPLY_NAME>');

 

** where <APPLY_NAME> is the actual name of the APPLY queue displayed in the HTML report **

 

APPLY status command

select status, apply_name, error_message from dba_apply;

PROPAGATION stop command

EXEC DBMS_PROPAGATION_ADM.STOP_PROPAGATION(propagation_name => '<PROPAGATION_NAME>');

 

** where <PROPAGATION_NAME> is the actual name of the PROPAGATION queue displayed in the HTML report **

 

PROPAGATION start command

EXEC DBMS_PROPAGATION_ADM.START_PROPAGATION(propagation_name => '<PROPAGATION_NAME>');

 

** where <PROPAGATION_NAME> is the actual name of the PROPAGATION queue displayed in the HTML report **

 

PROPAGATION status command

select status, propagation_name, error_message from dba_propagation;

 

Should any of the CAPTURE, APPLY and PROPAGATION queues still show any errors in the ERROR_MESSSAGING or the STATUS shows ERROR or ABORTED then it is highly likely that the replica instance(s) will need to be removed from the deployment, the primary instance cleaned up (with a reset on the replication) and the replica instance(s) attached back, one by one with a new replica package.

 

 

 

Legacy Article IDa67500

Attachments

    Outcomes