5 Administering an Oracle Streams Replication Environment

Starting and Stopping a Capture Process

This topic contains instructions for starting and stopping a capture process in Enterprise Manager.

A capture process might stop automatically if it encounters an error, such as an unsupported data type. When this happens, the error is displayed on the Capture subpage of the Manage Replication page in Enterprise Manager. In this case, you should correct the error and restart the capture process.

Also, it is important to remember that a capture process can capture changes that were made to database objects while the capture process was stopped. These changes are recorded in the redo log, and a capture process finds the changes that it is configured to capture in the redo log after it restarts. If you want to avoid capturing specific changes to database objects, then you should use tags to accomplish this. See "About Tags for Avoiding Change Cycling".

To start or stop a capture process: 

1. In Oracle Enterprise Manager, log in to the database as the Oracle Streams administrator.

2. Go to the Database Home page.

3. Under High Availability, click the number link in Streams Components.

   The Manage Replication page appears, showing the Overview subpage.

4. Click Streams to open the Streams subpage.

   
   Description of the illustration tdpii_strrms_strms.gif
   
   

5. Select the capture process to start or stop in the list of components. If necessary, use the search tool to find the capture process, and then select it.

6. In the Action list, select Enable to start a disabled or aborted capture process, or select Disable to stop an enabled capture process.

7. Click Go.

8. If you are disabling the capture process, then click Yes on the confirmation page to finish disabling it.

Setting a Capture Process Parameter

This topic contains instructions for setting capture process parameters in Enterprise Manager. Capture process parameters control the way a capture process operates. You can set a parameter to change a specific way in which a capture process operates. For example, you can change the parallelism capture process parameter to control the number of processes that capture changes. Typically, you adjust capture process parallelism to achieve the best capture process performance.

To set a capture process parameter: 

1. In Oracle Enterprise Manager, log in to the database as the Oracle Streams administrator.

2. Go to the Database Home page.

3. Under High Availability, click the number link in Streams Components.

   The Manage Replication page appears, showing the Overview subpage.

4. Click Streams to open the Streams subpage.

   
   Description of the illustration tdpii_strrms_strms.gif
   
   

5. Select the capture process to modify in the list of components. If necessary, use the search tool to find the capture process, and then select it.

6. Select Configurations in Action.

7. Click Go to open the Configurations subpage.

8. Click Edit to open the Edit Capture Configuration page.

   
   Description of the illustration tdpii_edit_capture.gif
   
   

9. Modify one or more capture process parameters in the Parameters section.

   See Oracle Database PL/SQL Packages and Types Reference for information about the parameters. If you change the parallelism parameter, then the capture process automatically stops and restarts when you click Apply.

10. Click Apply to save your changes.

Starting and Stopping an Apply Process

This topic contains instructions for starting and stopping an apply process in Enterprise Manager.

An apply process might stop automatically if it encounters an error, such as attempting to update a row that does not exist in a table. When this happens, the status of the apply process is ABORTED on the Apply subpage of the Manage Replication page in Enterprise Manager. In this case, you should correct the error and restart the apply process.

To start or stop an apply process: 

1. In Oracle Enterprise Manager, log in to the database as the Oracle Streams administrator.

2. Go to the Database Home page.

3. Under High Availability, click the number link in Streams Components.

   The Manage Replication page appears, showing the Overview subpage.

4. Click Streams to open the Streams subpage.

   
   Description of the illustration tdpii_strrms_strms.gif
   
   

5. Select the apply process to start or stop in the list of components. If necessary, use the search tool to find the apply process, and then select it.

6. In the Action list, select Enable to start a disabled or aborted apply process, or select Disable to stop an enabled apply process.

7. Click Go.

8. If you are disabling the apply process, then click Yes on the confirmation page to finish disabling it.

Setting an Apply Process Parameter

This topic contains instructions for setting apply process parameters in Enterprise Manager. Apply process parameters control the way an apply process operates. You can set a parameter to change a specific way in which an apply process operates. For example, you can change the parallelism apply process parameter to control the number of processes that apply changes. Typically, you adjust apply process parallelism to achieve the best apply process performance.

To set an apply process parameter: 

1. In Oracle Enterprise Manager, log in to the database as the Oracle Streams administrator.

2. Go to the Database Home page.

3. Under High Availability, click the number link in Streams Components.

   The Manage Replication page appears, showing the Overview subpage.

4. Click Streams to open the Streams subpage.

   
   Description of the illustration tdpii_strrms_strms.gif
   
   

5. Select the apply process to modify in the list of components. If necessary, use the search tool to find the apply process, and then select it.

6. Select Configurations in Action.

7. Click Go to open the Configurations subpage.

8. Click Edit to open the Edit Apply Configuration page.

   
   Description of the illustration tdpii_edit_apply.gif
   
   

9. Modify one or more apply process parameters in the Parameters section.

   See Oracle Database PL/SQL Packages and Types Reference for information about the parameters. If you change the parallelism parameter, then the apply process automatically stops and restarts when you click Apply.

10. Click Apply to save your changes.

Viewing Information About a Capture Process

You can use Enterprise Manager to view information about a capture process. This information includes the capture process status and state and other information about the capture process.

To view detailed information about a capture process in Enterprise Manager: 

1. In Oracle Enterprise Manager, log in to the database as the Oracle Streams administrator.

2. Go to the Database Home page.

3. Under High Availability, click the number link in Streams Components.

   The Manage Replication page appears, showing the Overview subpage.

4. Click Streams to open the Streams subpage.

   
   Description of the illustration tdpii_strrms_strms.gif
   
   

   The Steams subpage shows general information about each capture process in the database. This information includes capture process status, state, latency, and throughput.

5. Select the capture process to monitor in the list of components. If necessary, use the search tool to find the capture process, and then select it.

6. Select View Details in Action.

7. Click Go to open the View Capture Details page.

The View Capture Details page includes detailed information about the capture process.

Viewing Statistics for a Capture Process

You can use Enterprise Manager to view statistics for a capture process. The statistics include the number of messages in the capture process's queue, the number of messages captured and enqueued by the capture process, and other statistics relating to the capture process.

To view statistics for a capture process in Enterprise Manager: 

1. In Oracle Enterprise Manager, log in to the database as the Oracle Streams administrator.

2. Go to the Database Home page.

3. Under High Availability, click the number link in Streams Components.

   The Manage Replication page appears, showing the Overview subpage.

4. Click Streams to open the Streams subpage.

   
   Description of the illustration tdpii_strrms_strms.gif
   
   

   The Streams subpage shows general information about each capture process in the database. This information includes capture process status, state, latency, and throughput.

5. Select the capture process to monitor in the list of components. If necessary, use the search tool to find the capture process, and then select it.

6. Select View Statistics in Action.

7. Click Go to open the View Capture Statistics page.

The View Capture Statistics page includes the following information:

• The Queue Statistics graph shows the number of messages currently in the capture process's queue. The No of Enqueued Messages line in the graph shows the total number of messages currently in the buffered queue. The No of Spilled Messages line in the graph shows the total number of messages that have spilled from memory into the persistent queue table.

• The Message Statistics graph shows the total number of changes enqueued and captured by the capture process since it last started. Total Messages Enqueued shows the number of changes enqueued by the capture process. Total Messages Captured shows the number of changes that were evaluated in detail against the capture process rules. If a change does not satisfy the capture process rules, then the change is not enqueued.

• The Capture Statistics section includes the current state of the capture process, and statistics related to time and changes (messages) captured. See the documentation for the V$STREAMS_CAPTURE dynamic performance view in Oracle Database Reference for more information about these statistics.

Viewing Active Capture Process Transactions

You can use Enterprise Manager to view the transactions that are currently being processed by a capture process. Enterprise Manager displays the following information:

• Transaction ID: The transaction ID of each transaction

• Cumulative Messages: The cumulative number of messages in the transaction

  In an Oracle Streams replication environment, each message is a logical change record (LCR). If the Streams process is restarted while the transaction changes are being captured, then this column shows the number of LCRs captured in the transaction since the Streams process was started.

• First SCN: The system change number (SCN) for the first message in the transaction

• Last SCN: The SCN for the last message in the transaction

• Active Since: The time when the first message in the transaction was recorded

  In an Oracle Streams replication environment, changes captured by a capture process are recorded in the database redo log.

• Active For (Seconds): The amount of time that the transaction in the stream, which is the amount of time between the Active Since time and the current time

To view the active capture process transactions: 

1. In Oracle Enterprise Manager, log in to the database as the Oracle Streams administrator.

2. Go to the Database Home page.

3. Under High Availability, click the number link in Streams Components.

   The Manage Replication page appears, showing the Overview subpage.

4. Click Streams to open the Streams subpage.

   
   Description of the illustration tdpii_strrms_strms.gif
   
   

   The Capture subpage shows general information about each capture process in the database. This information includes capture process status, state, latency, and throughput.

5. Click the number link in the Current Transactions Active field for the capture process to open the View Capture Statistics page.

   The Active Streams Transactions List section displays the active capture process transactions.

   
   Description of the illustration tdpii_active_cap_trans.gif
   
   

   The Session ID and Total Messages fields do not apply to capture processes.

6. To drill-down for more information about a transaction, select the transaction and click View Transaction Details.

7. On the LogMiner page, click Continue.

8. On the LogMiner Results page, click the Transaction ID link in the table in the Transaction Results section.

   The Transaction Details page displays detailed information about the changes in the transaction.

   
   Description of the illustration tdpii_cap_trans_detailes.gif
   
   

Viewing Information About a Propagation

You can use Enterprise Manager to view information about a propagation. This information includes the propagation status, whether the propagation has failed, and other information about the propagation.

To view information about a propagation in Enterprise Manager: 

1. In Oracle Enterprise Manager, log in to the database as the Oracle Streams administrator.

2. Go to the Database Home page.

3. Under High Availability, click the number link in Streams Components.

   The Manage Replication page appears, showing the Overview subpage.

4. Click Streams to open the Streams subpage.

   
   Description of the illustration tdpii_strrms_strms.gif
   
   

5. Select the propagation to monitor in the list of components. If necessary, use the search tool to find the propagation, and then select it.

6. Select View Details in Action.

7. Click Go to open the View Propagation Details page.

The View Propagation Details page includes detailed information about the propagation.

Viewing Statistics for a Propagation

You can use Enterprise Manager to view statistics for a propagation. The statistics include the number of messages in the propagation source queue, the number of messages sent by the propagation, and other statistics relating to the propagation.

To view statistics for a propagation in Enterprise Manager: 

1. In Oracle Enterprise Manager, log in to the database as the Oracle Streams administrator.

2. Go to the Database Home page.

3. Under High Availability, click the number link in Streams Components.

   The Manage Replication page appears, showing the Overview subpage.

4. Click Streams to open the Streams subpage.

   
   Description of the illustration tdpii_strrms_strms.gif
   
   

5. Select the propagation to monitor in the list of components. If necessary, use the search tool to find the propagation, and then select it.

6. Select View Statistics in Action.

7. Click Go to open the View Propagation Statistics page.

The View Propagation Statistics page includes the following subpages:

• The Buffered Queue option shows propagation statistics for messages that were enqueued into the buffered queue portion of the queue used by the propagation. Use this subpage to view propagation statistics if the propagation sends changes captured by a capture process.

• The Persistent Queue option shows propagation statistics for messages that were enqueued into the persistent queue portion of the queue used by the propagation. Use this subpage to view propagation statistics if the propagation sends changes captured by a synchronous capture.

Both options contain graphs that show the number of messages in the queue and the number of messages sent by the propagation over several hours. Both options also contain other propagation statistics, such as the total number of messages and bytes propagated since the propagation was last started.

Viewing Information About an Apply Process

You can use Enterprise Manager to view information about an apply process. This information includes the apply process status and state and other information about the apply process.

To view information about an apply process in Enterprise Manager: 

1. In Oracle Enterprise Manager, log in to the database as the Oracle Streams administrator.

2. Go to the Database Home page.

3. Under High Availability, click the number link in Streams Components.

   The Manage Replication page appears, showing the Overview subpage.

4. Click Streams to open the Streams subpage.

   
   Description of the illustration tdpii_strrms_strms.gif
   
   

5. Select the apply process to monitor in the list of components. If necessary, use the search tool to find the apply process, and then select it.

6. Select View Details in Action.

7. Click Go to open the View Apply Details page.

The View Apply Details page includes detailed information about the apply process.

Viewing Statistics for an Apply Process

You can use Enterprise Manager to view statistics for an apply process. The statistics include the number of messages in the apply process's queue, the number of messages applied by the apply process, and other statistics relating to the apply process.

To view statistics for an apply process in Enterprise Manager: 

1. In Oracle Enterprise Manager, log in to the database as the Oracle Streams administrator.

2. Go to the Database Home page.

3. Under High Availability, click the number link in Streams Components.

   The Manage Replication page appears, showing the Overview subpage.

4. Click Streams to open the Streams subpage.

   
   Description of the illustration tdpii_strrms_strms.gif
   
   

5. Select the apply process to monitor in the list of components. If necessary, use the search tool to find the apply process, and then select it.

6. Select View Statistics in Action.

7. Click Go to open the View Apply Statistics page.

The View Apply Statistics page includes the following subpages:

• The Queue subpage shows the number of messages over the past several hours in both the persistent queue portion and the buffered queue portion of the apply process's queue. If the apply process applies changes captured by a synchronous capture, then analyze the persistent queue statistics. If the apply process applies changes captured by a capture process, then analyze the buffered queue statistics.

• The Reader subpage shows statistics for the reader server. The reader server dequeues messages from the apply process's queue and assembles them into separate transactions.

• The Coordinator subpage shows statistics for the coordinator process. The coordinator process gets transactions from the reader server and passes them to apply servers.

• The Server subpage shows statistics for the apply servers. The apply servers apply changes to database objects or pass the changes to apply handlers. To view details about a specific apply server, select it and click View Details.

Viewing Active and Spilled Apply Process Transactions

You can use Enterprise Manager to view the transactions that are currently being processed by an apply process. Active transactions are transactions with messages that are currently in the buffered queue for the apply process. Spilled transactions are transactions with messages that have spilled from the buffered queue to the hard disk.

Enterprise Manager displays the following information for active transactions:

• Transaction ID: The transaction ID of each transaction

• Session ID: The session ID of the apply process's coordinator process

• Total Messages: The total number of messages in the transaction

  The total number of messages in the transaction is calculated only for apply processes. In an Oracle Streams replication environment, each message is a logical change record (LCR).

• Cumulative Messages: The cumulative number of messages in the transaction

  If the Streams process is restarted while the transaction is being received, then this column shows the number of LCRs received in the transaction since the Streams process was started.

• First SCN: The system change number (SCN) of the first message in the transaction

• Last SCN: The SCN of the last message in the transaction

• Active Since: The time when the first message in the transaction was recorded

  In an Oracle Streams replication environment, changes captured by a capture process are recorded in the database redo log.

• Active For (Seconds): The amount of time that the transaction in the stream, which is the amount of time between the Active Since time and the current time

Enterprise Manager displays the following information for spilled transactions:

• Transaction ID: The transaction ID of each transaction

• Session ID: The session ID of the apply process's reader server

• First SCN: The SCN for the first message in the transaction

• Message Count: The number of spilled messages in the transaction

  In an Oracle Streams replication environment, each message is a logical change record (LCR).

• First Message Create Time: The time when the first message in the transaction was recorded

  In an Oracle Streams replication environment, changes captured by a capture process are recorded in the database redo log.

• Spill Create Time: The time when the first message in the transaction spilled from the buffered queue to the hard disk (spill create time)

To view active and spilled apply process transactions: 

1. In Oracle Enterprise Manager, log in to the database as the Oracle Streams administrator.

2. Go to the Database Home page.

3. Under High Availability, click the number link in Streams Components.

   The Manage Replication page appears, showing the Overview subpage.

4. Click Streams to open the Streams subpage.

   
   Description of the illustration tdpii_strrms_strms.gif
   
   

5. Perform one of the following actions:

   • To view the active apply process transactions, click the number link in the Current Transactions Active field for the apply process.

     The Active Streams Transactions List section on the View Apply Statistics page displays the active apply process transactions.

     
     Description of the illustration tdpii_active_app_trans.gif
     
     

   • To view the spilled apply process transactions, click the number link in the Current Transactions Spilled field for the apply process.

     The Spilled Streams Transactions List section on the View Apply Statistics page displays the spilled apply process transactions.

     
     Description of the illustration tdpii_spilled_app_trans.gif
     
     

Displaying the Configured Update Conflict Handlers

In a replication environment, update conflict handlers automatically resolve conflicts that occur when the same row is updated at two different databases at nearly the same time. You can use the ALL_APPLY_CONFLICT_COLUMNS data dictionary view to list the update conflict handlers.

To display the configured update conflict handlers: 

1. Open SQL*Plus and connect to the database as the Oracle Streams administrator.

   See Oracle Database 2 Day DBA for more information about starting SQL*Plus.

2. Run the following query:

   COLUMN OBJECT_OWNER HEADING 'Table|Owner' FORMAT A5
   COLUMN OBJECT_NAME HEADING 'Table Name' FORMAT A12
   COLUMN METHOD_NAME HEADING 'Method' FORMAT A12
   COLUMN RESOLUTION_COLUMN HEADING 'Resolution|Column' FORMAT A13
   COLUMN COLUMN_NAME HEADING 'Column Name' FORMAT A30
    
   SELECT OBJECT_OWNER, 
          OBJECT_NAME, 
          METHOD_NAME, 
          RESOLUTION_COLUMN, 
          COLUMN_NAME
     FROM ALL_APPLY_CONFLICT_COLUMNS
     ORDER BY OBJECT_OWNER, OBJECT_NAME, RESOLUTION_COLUMN;
   

   The output will be similar to the following:

   Table                           Resolution
   Owner Table Name   Method       Column        Column Name
   ----- ------------ ------------ ------------- ------------------------------
   HR    COUNTRIES    MAXIMUM      TIME          TIME
   HR    COUNTRIES    MAXIMUM      TIME          REGION_ID
   HR    COUNTRIES    MAXIMUM      TIME          COUNTRY_NAME
   HR    DEPARTMENTS  MAXIMUM      TIME          TIME
   HR    DEPARTMENTS  MAXIMUM      TIME          MANAGER_ID
   HR    DEPARTMENTS  MAXIMUM      TIME          LOCATION_ID
   HR    DEPARTMENTS  MAXIMUM      TIME          DEPARTMENT_NAME
   

   The output in this example shows that latest time conflict resolution is configured for the hr.countries and hr.departments tables. When a conflict occurs for any column listed under Column Name, the change with the maximum, or latest, time in the TIME resolution column is used, and the other change is discarded.

Capture Aborts Alert

This alert indicates a critical error. The capture process stops and any replication that depends on the capture process also stops. Also, the capture process makes no further progress in scanning the redo log until it is restarted.

Response

Obtain the exact error message in one of the following ways:

• In Enterprise Manager, see "Viewing Information About a Capture Process" for instructions.

• In SQL*Plus, query the ALL_CAPTURE view.

Take the appropriate action for the error.

After taking the appropriate action, restart the capture process in one of the following ways:

• In Enterprise Manager, see "Starting and Stopping a Capture Process" for instructions.

• In SQL*Plus, run the DBMS_CAPTURE_ADM.START_CAPTURE procedure.

Propagation Aborts Alert

This alert indicates a critical error. The propagation stops, and the messages that are normally sent from one queue to another by the propagation remain in the source queue. Replication that depends on the propagation also stops. Eventually, the source queue can grow too large, and messages can spill to disk. When messages spill to disk, it degrades Oracle Streams performance.

Response

Obtain the exact error message in one of the following ways:

• In Enterprise Manager, see "Viewing Information About a Propagation" for instructions.

• In SQL*Plus, query the DBA_QUEUE_SCHEDULES view.

Take the appropriate action for the error.

After taking the appropriate action, restart the propagation in one of the following ways:

• In Enterprise Manager, see "Enabling and Disabling a Propagation" for instructions.

• In SQL*Plus, run the DBMS_PROPAGATION_ADM.START_PROPAGATION procedure.

Apply Aborts Alert

This alert indicates a critical error. The apply process stops, and the messages that are normally dequeued by the apply process remain in the apply process's queue. Replication that depends on the apply process also stops. Eventually, the apply process's queue can grow too large, and messages can spill to disk. Other queues that send messages to the apply process's queue might also grow and spill messages to disk. When messages spill to disk, it degrades Oracle Streams performance.

Response

Obtain the exact error message in one of the following ways:

• In Enterprise Manager, see "Viewing Information About an Apply Process" for instructions.

• In SQL*Plus, query the ALL_APPLY view.

Take the appropriate action for the error. If the error is an ORA-26714 error, then consider setting the DISABLE_ON_ERROR apply process parameter to N to avoid aborting on future user errors. See "Setting an Apply Process Parameter" for instructions.

After taking the appropriate action, restart the apply process in one of the following ways:

• In Enterprise Manager, see "Starting and Stopping an Apply Process" for instructions.

• In SQL*Plus, run the DBMS_APPLY_ADM.START_APPLY procedure.

Apply Error Alert

This alert indicates that the apply process encountered an error when it was applying a transaction. The apply process moves all of the messages in the transaction to the error queue. Other transactions that depend on the error transaction might also result in apply errors, and the error queue might grow quickly. Therefore, an administrator should resolve the apply errors as soon as possible.

Response

Manage the apply errors in the error queue in one of the following ways:

• In Enterprise Manager, see "Managing Apply Errors" for instructions.

• In SQL*Plus, query the ALL_APPLY_ERROR view to view the errors, resolve the errors, and either execute or delete the errors using procedures in the DBMS_APPLY_ADM package.

Oracle Streams Pool Alert

A metric is a unit of measurement used to report the health of the system. This alert is generated when the memory usage of the Oracle Streams pool has exceeded the percentage specified by the STREAMS_POOL_USED_PCT metric.

This alert can be raised only if the database is not using Automatic Memory Management or Automatic Shared Memory Management. Specifically, this alert can only be raised if the following initialization parameters are set to 0 (zero) or are unset:

• MEMORY_TARGET

• SGA_TARGET

Response

This metric threshold can be set automatically by the alert infrastructure, or you can set it using Enterprise Manager. If the currently running workload is typical, then consider increasing the size of the Oracle Streams pool. Some of the links under the Related Topics heading on the Database Home page enable you to manage metrics. See Oracle Database 2 Day DBA for information about viewing and setting metric thresholds.

Correcting Apply Errors in Database Objects

You might need to make data manipulation language (DML) or data definition language (DDL) changes to database objects to correct the conditions that caused one or more apply errors before you retry error transactions. If you must make changes to a database object, but you do not want to replicate these changes, then set a session tag in the session that makes the changes.

For example, to update the hr.employees table to correct an apply error: 

1. Open SQL*Plus and connect as a user who can update the hr.employees table.

   See Oracle Database 2 Day DBA for more information about starting SQL*Plus.

2. Set a session tag:

   BEGIN
      DBMS_STREAMS.SET_TAG(
         tag  =>  HEXTORAW('1D'));
   END;
   /
   

   Ensure that you set the tag to a value that prevents changes from being captured by capture processes and synchronous captures.

3. Update the hr.employees table to correct the error.

4. Exit the SQL*Plus session.

After you correct the problem that caused one or more error transactions, you can retry the error transactions or delete them. See "Retrying or Deleting Apply Error Transactions" for instructions.

For information about specific apply errors and how to correct them, see Oracle Streams Concepts and Administration.

Retrying or Deleting Apply Error Transactions

"Correcting Apply Errors in Database Objects" describes correcting the problem that caused one or more error transactions. After you correct the problem, you can retry the error transactions or delete them:

• Retry the transactions if the changes in the transaction should be made to the destination table. Retry them only if you have not already modified the data in the table to make these changes.

• Delete the transactions if you made all of the changes in the transactions to the destination table, or if the changes should not be made to the table.

To retry or delete apply error transactions: 

1. In Oracle Enterprise Manager, log in to the database as the Oracle Streams administrator.

2. Go to the Database Home page.

3. Under High Availability, click the number link in Streams Components.

   The Manage Replication page appears, showing the Overview subpage.

4. Click Streams to open the Streams subpage.

   
   Description of the illustration tdpii_strms_ap_error.gif
   
   

   When an apply process has one or more errors, the Status icon changes to include a warning symbol. Also, an apply error might cause an apply process to abort. When an apply process aborts, the status of the apply process is ABORTED.

5. Select the apply process with error transactions in the list of components. If necessary, use the search tool to find the apply process, and then select it.

6. Select View Errors in Action.

7. Click Go to open the View Apply Details page.

   The errors appear in the Errors section, under Transaction Errors.

   
   Description of the illustration tdpii_apply_errors.gif
   
   

   You can view detailed information about an error by clicking the icon in the View Error LCRs field for the error transaction. The detailed information appears on the View Error LCRs page and includes each change in the transaction.

   
   Description of the illustration tdpii_view_error_lcrs.gif
   
   

   To drill down further, select a row change and click Compare Values. The Compare Values page appears and compares the row change with the data in the table to which the change should be applied.

   
   Description of the illustration tdpii_compare_error_values.gif
   
   

8. If you drilled down to more information about an error, then go back to the Apply Errors page by clicking the View Apply Details link and expanding Transaction Errors.

9. On the Apply Errors page, complete one of the following actions:

   • To retry all error transactions, click Retry all Errors.

   • To delete all error transactions, click Delete All.

   • To retry a specific error transaction, select the error transaction and click Retry Error.

   • To delete a specific error transaction, select the error transaction and click Delete.