To refresh your target tables: 1. Start Management Console and log into Access Server. 2. Ensure that the subscription has at least one table mapping with replication method set to Mirror. You set this when mapping tables in the Map Tables wizard. 3. Ensure that you have ended any active replication on the subscription. 4. Click Configuration > Subscriptions. 5. Select the subscription that contains the mapped source and target tables. 6. Select the mapped source and target tables in the Table Mappings view. 7. Right-click on the table and click Flag for Refresh .... 8. Select Full Refresh from the Flag for Refresh dialog.
When you are ready to start mirroring, InfoSphere CDC will send all changes from the source table to the target table so that both tables are synchronized. InfoSphere CDC will then mirror subsequent changes to the target.
57 Encountering errors after applying DDL changes to in-scope tables for InfoSphere CDC for z/OS Environment InfoSphere® CDC for z/OS®. Symptoms Replication stops and one or more of the following event messages are issued: - CHC0068E - CHC0598W - CHC0599W - CHC0604W - CHC0605E - CHC0839W - CHC0799W - CHC0801W - CHC0802W - CHC0803W - CHC0804W - CHC0805W - CHC0859E - CHC1503E
Causes You performed DDL changes that significantly affected the structure of the source table and you have not enabled DATA CAPTURE CHANGES on the SYSIBM.SYSTABLES system catalog table in DB2®. These operations cause data to be written to the log which will not be received by InfoSphere CDC or cause the log record format of the table to change (that is, the layout of the data in the database logs change). For operations where the log record format changes, the log reader must be directed on how to proceed when a change is encountered. InfoSphere CDC metadata must be modified to accommodate the new log record format; otherwise the log reader will fail to properly decode log records after the point of the DDL change. Changes that do not materially affect the physical structure of the table in the log or the DATA CAPTURE CHANGES setting for the table will not interrupt replication. InfoSphere CDC is able to continue when columns are added to tables, however there are some limitations. Refer to the InfoSphere Change Data Capture for z/OS End-User Documentation to understand the factors affecting this capability. Resolution InfoSphere CDC can detect most DDL changes on in-scope tables only if DATA CAPTURE CHANGES is enabled on the SYSIBM.SYSTABLES system catalog table in DB2. If it is not enabled, InfoSphere CDC will be aware of DDL changes when it encounters a log record that does not match the definition in the metadata. In this case, its actions will depend on the type of DDL operation and the version of DB2.If InfoSphere CDC detects a DDL operation being performed on a table which is in-scope for replication, it will analyze the change made. If no material change is detected, it executes an auto-read and replication continues. If a column has been added, the information is added to the InfoSphere CDC for z/OS metadata and replication continues; however, the new column is no longer selected for replication. Any other 58 material change to the table will either end replication for the subscription or idle the table and continue replication as configured by the ONSCHEMACHANGE parameter. This applies to InfoSphere CDC for z/OS version 6.5 and 6.2 with current maintenance applied. See the end-user documentation for details. To make DDL changes without a refresh: 1. Quiesce the tables for which the DDL change is needed. 2. Ensure that mirroring is running with zero latency, at head of log. 3. Ensure that all changes for these tables have been applied to the target tables. 4. Make the DDL changes, changing the target table if required. 5. Start Management Console and log into Access Server. 6. Click Configuration > Subscriptions. 7. Select the subscription containing the tables affected by the DDL change. 8. Right click on a table and select Update Table Definition > Source. 9. Check table mappings for correctness.When DDL modifies columns, make sure the target table can accommodate the new data format (for example, going from CHAR(1) to CHAR(10)). 10. Start replication.The database may now be opened for data changes at this time for all tables in-scope for replication.
If InfoSphere CDC is not running and DML statements occur between DDL statements, or you perform an action to cause a section of the log to be skipped (such as running SETLOGPOS), perform a refresh to resynchronize tables. Consider the following scenario: - DDL statements were issued. - InfoSphere CDC detected the DDL statements and ended replication. - While replication was down, DDL and DML operations were performed on the table (for example, insert a row, add another column, insert a row, drop a column). - The table definition was updated within the product.
Here, the table definition would have been updated to the latest structure of the table, and will not account for all operations that occurred while replication was down. You will need to update the source table definition, verify the table mappings and refresh the affected tables. To recover from DDL changes if DML statements occur between DDL statements: 1. Run a REORG on the tablespaces containing the changed tables. 2. Start Management Console and log into Access Server. 3. Click Configuration > Subscriptions. 4. Select the subscription containing the tables affected by the DDL change. 5. Right click on a table and select Update Table Definition > Source. 6. Check table mappings for correctness.When DDL modifies columns, make sure the target table can accommodate the new data format (for example, going from CHAR(1) to CHAR(10)). 7. Select all affected tables and set them to Mirror Refresh. 8. Start replication.If Mirroring is selected, the Refresh will complete before InfoSphere CDC begins mirroring changes for all tables.
60 Encountering a The oldest open commit group in the staging space for subscription name opened at time has exceeded the open commit group warning age of maximum minutes by exceeds minutes message for long running Units of Recovery (URs) on InfoSphere CDC for z/OS Environment InfoSphere® CDC for z/OS®. Symptoms While replicating, you encounter the following warning: CHC0051W The oldest open commit group in the staging space for subscription name opened at time has exceeded the open commit group warning age of maximum minutes by exceeds minutes. Causes Long running transactions or URs pose a challenge for all replication software. All changes must be collected for the unit of work until the disposition of the UR is known (commit or rollback).InfoSphere CDC checks for long running URs every 15 minutes. This warning occurs when a UR has been open in the database for longer than the amount of time set by the OPENCOMMITWARNAGE parameter (the default is 60 minutes). If a subscription is stopped when a long running UR has not completed, InfoSphere CDC will need to re-read the log beginning at the time when this UR began. You should resolve this before stopping the subscription. Resolution A staging space report will provide details about the UR including the URID. This report is requested using the REPORT,TYPE=STGSP console command, and the report is written to the CHCREPRT SPOOLed output data set.Each subscription has its own staging space and you can request a unique report for each subscription. Each report describes the following details about the staging space: - A description of the UR, including the UR ID, the member identifier (if running in a Data Sharing Group mode), and the date and time when the UR first entered the staging space. - Security information about the UR, including the address space name, the security identifier of the originating job, and the name of the DB2® plan used to create the UR. - SQL operations contained in the staging space for the UR. The report also tracks all the INSERT, UPDATE, and DELETE operations, and the UR’s current disposition. The disposition indicates the status of the UR: whether the UR is currently being collected into the staging space, is being or has been committed or rolled back, is queued for transmission to the target, or is being transmitted to the target.
With the URID, you can run a DSN1LOGP report (see the DB2 documentation for instructions) to retrieve details about the UR from the database. With this information you can determine the user who is running the job and take steps to ensure they end the UR in a timely manner. Under certain conditions, it is possible to write an incomplete UR (that is, one that does not have the full complement of UR control records that describe how it was disposed of) to the DB2 log. In this case, the UR can remain idle and be stalled in the staging space. You can see stalled URs in the staging space report. Issue the 61 ENDUR console command against the stalled UR to force a commit (and transmit its contents to the target) or roll back (and purge its contents from the staging space). Issuing this command does not disrupt replication activities. After resolving a stalled UR, open a PMR with IBM® Support and provide the output from the staging space report and the DSN1LOGP report.
62 Encountering a CHC9219E DB2 IFI has returned non-zero status in a Log Record at position, QW0306RC = return, QW0306RS = reason, QW0306DG = code decompression error on InfoSphere CDC for z/OS Environment InfoSphere® CDC for z/OS®. Symptoms The subscription ends and this message is found in the event log: CHC9219E DB2 IFI has returned non-zero status in a Log Record at position, QW0306RC = return, QW0306RS = reason, QW0306DG = code. Causes DB2® has failed to successfully read a record from the DB2 Log. The most common reason is a failure in decompression of the log record. This is indicated by these values showing in this message:QW0306RC = X'00000008', QW0306RS = X'00C90063', QW0306DG =X'00C90064' The X’00C90063’ indicates a failure to decompress a record read from the log and the X’00C90064’ is the code indicating the compression dictionary was unavailable. Resolution The likely cause of this error is that a REORG has been run on the tablespace containing a table in-scope for replication. One method to avoid this is to use the KEEPDICTIONARY option when running a REORG.InfoSphere CDC uses the DB2 Instrumentation Facility Interface (IFI) to read the data from the log for tables that are in-scope for replication. The IFI decompresses the data from compressed table spaces before providing it to InfoSphere CDC. The IFI has the ability to detect a change in compression dictionary and handle it under certain conditions. Other reason codes may be returned. Refer to your DB2 documentation or contact the IBM® DB2 support organization for assistance with these errors.
63 Replicating tables without a primary key (event ID 9604) on InfoSphere CDC for Microsoft SQL Server Environment InfoSphere® CDC for Microsoft SQL Server. Symptoms When mapping a table in Management Console without a primary key you receive the following error: ERROR: An error has occurred while setting the replication method for [An error occurred while turning on supplemental logging for . Microsoft SQL Server encountered a problem while turning on data capture for table ’’ due to the fact that the table has no primary key. IBM InfoSphere Change Data Capture strongly recommends creating a primary key on the table. If a primary key can not be created on the table then you have to enable and take responsibility to maintain Microsoft SQL Server Change Data Capture feature for the table ’’.]. For more information, see error messages in the Event Log view. Causes You are replicating a table without a primary key. Resolution There are two possible solutions to this problem: - Add a primary key to the table. - Enable Microsoft Change Data Capture in Microsoft SQL Server. Do this for both the table that does not have a primary key, and the database that contains that table. Contact your database administrator or refer to your Microsoft SQL Server documentation for more information on how to perform this task. Note: If you are using Microsoft SQL Server 2008, replicating data in a table without a primary key will cause all the changed row data to be logged to a table in the Microsoft SQL Server database. This can result in a dramatic performance decrease. Consult your Microsoft SQL Server documentation for further details on how the Change Data Capture feature is implemented and its likely performance impact on your database.
64 Troubleshooting mirroring replication InfoSphere® CDC replicates data using two methods: mirroring or refreshing data. When InfoSphere CDC mirrors data for replication, it continuously replicates changed data from a source system to the target system. In this section, you will learn:
- Mirroring stops when InfoSphere CDC encounters an apply error - Encountering a 911 SQL error message when configuring a table for mirror replication on InfoSphere CDC for z/OS - Replication of tables containing LOB columns is slow - Encountering an An error occurred while turning on supplemental logging for . Unable to get exclusive lock on table message when configuring a table for mirror replication on InfoSphere CDC for Oracle databases
65 Mirroring stops when InfoSphere CDC encounters an apply error Environment InfoSphere® CDC for all replication engines. Symptoms InfoSphere CDC stops mirroring when it encounters an apply error. Causes There are two reasons why InfoSphere CDC would be unable to apply data to a target table: - Other applications or users are changing data on a target database. - A table capture point was marked incorrectly; that is, at a point where the target table was not actually synchronized with the source table contents. Resolution Operational issues such as resource constraints and some data synchronization issues can be related to having applications other than InfoSphere CDC change the target tables. Apply errors can manifest through such symptoms as lock time outs, which would be classified as operational issues, or as row operations (insert, update, and delete) failing. Unintentional changes to the target database by applications other than InfoSphere CDC can be resolved by preventing the applications from working with the target database. If having the target database updated by applications other than InfoSphere CDC in intentional behavior, then there are multiple ways to resolve: - Enable conflict detection and resolution to resolve conflicts. - Enable bidirectional replication and set up the appropriate conflict detection and resolution rules if the changes made to the target database by applications other than InfoSphere CDC should also be replicated to the source. - Remap the tables using Adaptive Apply. There may also be very specific situations in which the database reports an error that causes InfoSphere CDC to stop, but which you have determined replication should proceed. In these situations, configure InfoSphere CDC to ignore specific database errors. See also:
- To set conflict detection and resolution for source row wins - To map source and target tables for Adaptive Apply - To ignore database errors when applying data changes to the target for all subscriptions using InfoSphere CDC for z/OS - To ignore database errors when applying data changes to the target for all subscriptions Parent topic:Troubleshooting mirroring replication
1. Select the subscription that contains the mapped source and target tables. 2. Click the Table Mappings view and select the table mapping containing the target table you want to continue mirroring to. The tables should be mapped for Standard Replication. 3. Right-click Open Mapping Details. 4. Click the Conflicts tab.The Target Column displays all of the columns in the target table.
5. Select the columns on which you want to detect conflicts. 6. Select Source Wins from the Conflict Resolution Method list. 7. Click Apply.When you start replication on the subscription, if InfoSphere® CDC detects a conflict in the target column, the source data is replicated to the target.
1. Start Management Console and log into Access Server. 2. Click Configuration > Subscriptions. 3. Select a subscription, right-click and select Map Tables. 4. Select Custom Table Mapping > Adaptive Apply and click Next. 5. Select the source table from the Source Tables list and click Next.If you want to hide columns so that the target is not aware of them, click Filter Columns and clear the check box for the column you want to hide.
6. Select a table from the Target table list and click Next. 7. Choose one of the following and click Next: 8. Choose a replication method from the following and click Next: - Mirror (Change Data Capture)—Immediately replicates changes made to the source table to the target table or accumulate source table changes and replicate at a later time. If your configuration requires you to prevent recursive updates when mirroring, enable the Prevent Recursion check box. This check box is only available in versions of InfoSphere® CDC that support both source and target databases. - Refresh (Snapshot)—Replicates a snapshot of the source table to the target table.
9. If you are replicating source database changes using InfoSphere CDC for Oracle databases (trigger) and want to use a journal table to mirror database operations from the source to the target table, then enable one of the following: - Use Default Journal—Enable when you want InfoSphere CDC for Oracle databases to use the default journal table provided with InfoSphere CDC for Oracle databases: .DMCJRN. InfoSphere CDC uses this journal table to detect and replicate database changes from the source to the target. - Use Selected Journal—Enable when you want InfoSphere CDC for Oracle databases to use another journal table other than the default journal table provided with InfoSphere CDC for Oracle databases. When you select the database owner and provide a name for the journal table, InfoSphere CDC for Oracle databases creates this new journal table and uses it to detect and replicate database changes from the source to the target. - Owner—Lists the database owner of the journal table. - Name—Lists the name of the journal table.
10. Click Next. 11. Review the mapping summary. 12. Choose one of the following options and click Finish: - Define column mappings—Continues with the column mapping. - Create a new table mapping—Allows you to start a new table mapping. - Return to current view—Returns you to the current view.
69 To ignore database errors when applying data changes to the target for all subscriptions using InfoSphere CDC for z/OS Procedure
1. Ensure that you your target database is using InfoSphere® CDC for z/OS®. 2. Modify the setting for ENDONERROR in the CHCCFGxx member. ENDONERROR=(YES,YES,YES) is the default, indicating the settings for Refresh, Mirroring, and Auditing, respectively. Changing the values for one of the settings will cause InfoSphere CDC to continue replication after encountering an error while applying data to the target database during the corresponding type of replication activity.
3. Override the global settings for a subscription replicating from InfoSphere CDC for z/OS to InfoSphere CDC for z/OS by selecting Subscriptions > Properties > Advanced within Management Console.
70 To ignore database errors when applying data changes to the target for all subscriptions Procedure
1. Ensure that you your target database is not using InfoSphere® CDC for z/OS®. 2. Ensure you know the database error code which is returned by the SQLException class in JDBC. This error code is database vendor-specific and always an integer, such as "ORA-00001". 3. Start Management Console and log into Access Server. 4. Click Configuration > Datastores. 5. Right-click on the datastore for your target database and select Properties. 6. Select mirror_expected_errors_list from the System Parameters tab. 7. Click Modify. 8. Type the integer error code returned by the SQLException class in JDBC that you want to ignore, in the Value box. Specify multiple error codes with a comma separated list.Notes: - Ensure that you only configure the parameter to ignore errors that you are certain are safe to ignore (such as unique constraint ORA-00001). - Latency may increase when using this system parameter since InfoSphere CDC will not use JDBC array apply in order to track the errors specified.
71 Encountering a 911 SQL error message when configuring a table for mirror replication on InfoSphere CDC for z/OS Environment InfoSphere® CDC for z/OS®. Symptoms While configuring a table for mirroring in Management Console, InfoSphere CDC issues message showing a 911 SQL error, which indicates a deadlock or timeout. Causes This error occurs when you attempt to mirror a source table in Management Console but since there are one or more URs running against the table, DB2® cannot lock the table to complete the ALTER TABLE
ADD DATA CAPTURE CHANGES SQL statement issued by InfoSphere CDC. InfoSphere CDC requires DATA CAPTURE CHANGES to replicate tables properly and this can only be completed when the table is not being updated or locked by other users. Resolution Enable DATA CAPTURE CHANGES during a maintenance window. If DATA CAPTURE CHANGES is already configured on a table, InfoSphere CDC will detect this and will not need a lock on the table during configuration for mirroring. You can configure the table for mirroring during a maintenance window, or manually enable the DATA CAPTURE CHANGES during the window and complete the table configuration later. Parent topic:Troubleshooting mirroring replication
72 Replication of tables containing LOB columns is slow Environment InfoSphere® CDC for z/OS® Symptoms Replication for a subscription that has source tables that contain LOB columns is very slow. Sometimes it might appear that replication is stalled. Causes The ROWID column that is associated with the LOB column or columns might not have an index defined on it. When InfoSphere CDC selects the LOB column data from the source table, DB2® might use a table space scan to retrieve the LOB data. Resolution Apply the PTF for APAR PH13842. This PTF extends the LOB data selection logic to use any qualifying unique index, not just the index over the LOB's ROWID column, to access the LOB's auxiliary table space. When no suitable index is found, a warning message is issued to notify you of the possible poor performance.
Parent topic:Troubleshooting mirroring replication
73 Encountering an An error occurred while turning on supplemental logging for . Unable to get exclusive lock on table message when configuring a table for mirror replication on InfoSphere CDC for Oracle databases Environment InfoSphere® CDC for Oracle databases. Symptoms While configuring a table for mirroring in Management Console, InfoSphere CDC issues the following message: [ERROR] An error occurred while turning on supplemental logging for . Unable to get exclusive lock on table Causes This error occurs when you attempt to mirror a source table in Management Console but since there are many open transactions, InfoSphere CDC cannot lock the table and add supplemental logging. InfoSphere CDC requires supplemental logging to replicate tables properly and this can only be completed when the table is not being updated or locked by other users.In addition, when InfoSphere CDC executes an ALTER TABLE command to enable supplemental logging, it requires exclusive lock on the target table. Ensure there are no locked transactions or shared locks. Resolution You can resolve this issue in one of the following ways: - Locate open transactions on the specific source table. If there are locks, either wait for the transactions to complete, or terminate. Here is an example or how to terminate the transaction:select B.SID, C.USERNAME, C.OSUSER,C.TERMINAL, DECODE(B.ID2, 0, A.OBJECT_NAME, 'Trans-'||to_char(B.ID1)) OBJECT_NAME, B.TYPE, DECODE(B.LMODE,0,'--Waiting--', 1,'Null', 2,'Row Share', 3,'Row Excl', 4,'Share', 5,'Sha Row Exc', 6,'Exclusive', 'Other') "Lock Mode", DECODE(B.REQUEST,0,'', 1,'Null', 2,'Row Share', 3,'Row Excl', 4,'Share', 5,'Sha Row Exc', 6,'Exclusive', 'Other') "Req Mode" from DBA_OBJECTS A, V$LOCK B, V$SESSION C where A.OBJECT_ID = B.ID1 and a.object_id = 67491 (get object_id from dba_objects) and B.SID = C.SID From this example, determine the SID and serial number, and then run this SQL 74 command:alter system kill session <'SID, serial number>’; - Continue to replicate the source table until the transaction completes and InfoSphere CDC adds logging. Once the transaction completes, configure the table. - Manually terminate Oracle sessions with open transactions on the specific source table. Note: You may lose hours of database processing time when you terminate a session. In addition, it may take some time for the work of that session to be rolled back by Oracle. Only proceed when you have understood the impact of closing your transactions in this way.
Parent topic:Troubleshooting mirroring replication
75 Troubleshooting refresh replication InfoSphere® CDC replicates data using two methods: mirroring or refreshing data. When InfoSphere CDC refreshes data for replication, it synchronizes the target system with the current contents of a source system. In this section, you will learn:
- Refreshing fails with a referential integrity constraint violation reported in the event log - Refreshing data to the target on InfoSphere CDC and encountering database errors - Encountering a A SQL exception has occurred. The SQL error code is '0'. The SQL state is: HY000. The error message is: [CDC][Oracle JDBC Driver]Object has been closed message on InfoSphere CDC for Oracle databases
76 Refreshing fails with a referential integrity constraint violation reported in the event log Environment InfoSphere® CDC for all replication engines. Symptoms You encounter a referential integrity constraint violation error in the event log. Causes The referential integrity constraints in the target database conflict with the order in which InfoSphere CDC is refreshing the tables. Resolution Ensure that you have truncated or cleared all target tables, then refresh your tables by logical order (for example, parent, then child). InfoSphere CDC will not truncate the parent table if the child table contains data.Also, ideally, the parent and child tables should be part of the same replication, with proper ordering.
Parent topic:Troubleshooting refresh replication
77 Refreshing data to the target on InfoSphere CDC and encountering database errors Environment InfoSphere® CDC for all replication engines other than InfoSphere CDC for z/OS®. Symptoms While refreshing data to the target, you encounter database errors. In some cases, refresh also fails. Causes You can safely ignore some informational database errors since they do not affect replication; however, accumulating too many of these errors can cause InfoSphere CDC to stop replication. For example, if you are using InfoSphere CDC for Oracle databases or InfoSphere CDC for Oracle databases (trigger), you can ignore the following error during mirroring:ORA-00001: unique constraint violated (.) Resolution Configure InfoSphere CDC to ignore specified database errors when refreshing data to the target: 1. Ensure you know the database error code for the error you want InfoSphere CDC to ignore. The error code is returned by the SQLException class in JDBC. This error code is database vendor-specific and always an integer, such as "ORA- 00001" specifies a specific Oracle error. 2. Start Management Console and log into Access Server. 3. Click Configuration > Datastores. 4. Right-click on a datastore and select Properties. 5. On the System Parameters tab, select refresh_expected_errors_list. 6. Click Modify. 7. In the Value box, type the integer error code returned by the SQLException class in JDBC that you want to ignore. Specify multiple error codes with a comma separated list.Note: Latency may increase when using this system parameter since InfoSphere CDC will not use JDBC array apply in order to track the errors specified.
Parent topic:Troubleshooting refresh replication
78 Encountering a A SQL exception has occurred. The SQL error code is '0'. The SQL state is: HY000. The error message is: [CDC][Oracle JDBC Driver]Object has been closed message on InfoSphere CDC for Oracle databases Environment InfoSphere® CDC for Oracle databases. Symptoms You attempt to replicate subscriptions, and receive the following error:Failed to apply DDL ''{1}'' on table {0}. Database operation failed. A SQL exception has occurred. The SQL error code is '0'. The SQL state is: HY000. The error message is: [CDC][Oracle JDBC Driver]Object has been closed. Causes Typically, a message containing Object has been closed indicates that the session was abruptly ended, likely due to an internal Oracle error. Resolution Check Oracle’s alert log and the user dump destination. Refer to the background_dump_dest and user_dump_dest parameters for the locations of these files.
Parent topic:Troubleshooting refresh replication
79 Troubleshooting latency Latency is calculated as the difference in time between when a particular operation was applied to the source database, and when that same operation is applied to the target database by InfoSphere® CDC. In this section, you will learn:
- Experiencing increased latency and no data is replicating to the target database - Experiencing increased latency and no data is replicating to the target database on InfoSphere CDC for z/OS
80 Experiencing increased latency and no data is replicating to the target database Environment InfoSphere® CDC for all replication engines. Symptoms Latency is increasing and no data is being replicated to the target database. Causes This can occur when InfoSphere CDC is processing a large transaction that has recently executed on the source database. Resolution Complete either of the following resolutions: - Confirm that InfoSphere CDC is processing a large transaction by clicking Collect Statistics in Management Console. This feature displays various metrics reflecting different stages of the flow of replication data from the source to the target. When Management Console is processing a large transaction you will see that the source side metrics are changing. - Use the Performance view within the Monitoring perspective in Management Console. This allows you to view, investigate and diagnose the performance of subscriptions or tables within them to determine the causes of unexpected or unacceptable levels of latency.
Parent topic:Troubleshooting latency
81 Experiencing increased latency and no data is replicating to the target database on InfoSphere CDC for z/OS Environment InfoSphere® CDC for z/OS®. Symptoms There is a sudden increase in latency with subscriptions. You know that there have been many changes made to the source DB2® database on z/OS. InfoSphere CDC for z/OS reports that it is operating normally, yet you find no changes on the target system. Causes There are two probable causes: - Large group of changes in progress—If a very large UR was committed before the UR with your current changes, InfoSphere CDC may still be busy processing the first UR. Once completed and processed on the target system, the following URs will be replicated in the order they were committed. - Time latency value for your environment is too narrow—InfoSphere CDC uses a DB2 trace so that it is notified of all changes written to the DB2 log. This notification is sent when a percentage of the OPx buffer has been filled by DB2. If you have not allocated an appropriate size and threshold for the OPx buffer, notification of changes will be less frequent. These values can be set for InfoSphere CDC using the keywords BUFTHRESHOLD and BUFSIZE. If the value for BUFTHRESHOLD is set too high, then InfoSphere CDC does not notify subscriptions of new data efficiently and therefore, increases latency. For instance, if you have a BUFSIZE of 1 GB and set the BUFTHRESHOLD to 50%, InfoSphere CDC receives change notification only when 500 MB of data has been written to the DB2 log. Only then will it inform the active subscriptions that they can resume scraping log data. Resolution Depending on the cause of the replication failure, resolve it as follows: - Run staging space report for the subscription showing latency—When a large UR is being assembled in the staging space (located in the source installation of InfoSphere CDC), or being transmitted to the target system, observe its progress using the staging space report. This report is requested using the REPORT,TYPE=STGSP console command, and the report is written to the CHCREPRT SPOOLed output data set. Each subscription has its own staging space and you can request a unique report for each subscription. Each report describes the following details about the staging space: - A description of the UR, including the UR ID, the member identifier (if running in a Data Sharing Group mode), and the date and time when the UR first entered the staging space. - Security information about the UR, including the address space name, the security identifier of the originating job, and the name of the DB2 plan used to create the UR. - SQL operations contained in the staging space for the UR. The report also tracks all the INSERT, UPDATE, and DELETE operations, and the UR’s current disposition. The disposition indicates the status of the UR: whether the UR is currently being collected into the staging space, is being or has been committed or rolled back, is queued for transmission to the target, or is being transmitted to the target. 82
Consecutive staging space reports obtained for the same subscription with a short interval between them will show the progress of a large UR, through the staging space and out to the target. Under certain conditions, it is possible to write an incomplete UR (that is, one that does not have the full complement of UR control records that describe how it was disposed of) to the DB2 log. If a very large UR was committed before the UR with your current changes, InfoSphere CDC may still be busy processing the first UR. Once completed and processed on the target system, the following URs will be replicated in the order they were committed. - Increase the time latency value for your environment—Determine an appropriate time latency value for your environment. When a higher value is specified for BUFTHRESHOLD, that percentage of the OPx buffer must contain DB2 log data before InfoSphere CDC notifies subscriptions of data to be processed. If the default for BUFSIZE is used (the optimal value is 132 KB), then a BUFTHRESHOLD value of 50% means that at least 66 KB of DB2 log data must have been written to the DB2 log before InfoSphere CDC can start to process the new data. This 66 KB of data represents the DB2 Log data latency. If you know the average rate at which the DB2 log is being extended, then a data latency of 66 KB can be converted to a time latency value that can be calculated using the following formulas: TimeLatency = DataLatency / DB2LogDataRate
DataLatency = TimeLatency * DB2LogDataRate
To obtain an acceptable time latency value, use the preferred time latency value in the second formula and calculate an appropriate value for the data latency. Next, convert the data latency value to a percentage of the value of the BUFSIZE keyword, and use the calculated percentage as the value of the BUFTHRESHOLD keyword. Contact your DB2 database administrator to determine the DB2 log data rate. The maximum and minimum DB2 log data rates within a cyclical period (for example, a day, a week, month-end peak) may also be a consideration when determining the preferred value for BUFTHRESHOLD. A smaller time latency value is desirable when real-time, continuous mirroring of data is being performed. If real-time, continuous mirroring is not being used, then time latency has no significance for determining the value of the BUFTHRESHOLD keyword.
Parent topic:Troubleshooting latency
Related concepts - Encountering a The oldest open commit group in the staging space for subscription name opened at time has exceeded the open commit group warning age of maximum minutes by exceeds minutes message for long running Units of Recovery (URs) on InfoSphere CDC for z/OS
83 Troubleshooting data replication maintenance You may have ongoing maintenance issues, such as maintaining log files or cleaning up your system. In this section, you will learn:
- Running dmshowlogdependency on InfoSphere CDC for Oracle databases references a dated log file - Encountering a CHC9214E DB2 Trace could not be started. All OPx trace buffers are in use or CHC9217E DB2 CAF Message: [] message in the event log on InfoSphere CDC for z/OS
84 Running dmshowlogdependency on InfoSphere CDC for Oracle databases references a dated log file Environment InfoSphere® CDC for Oracle databases. Symptoms You have issued the dmshowlogdependency command and it returns a list of log files that you must keep. This list includes old log files. Causes This issue is usually indicative of one of two things: - You have a subscription in your replication environment (with at least one table) that you have not replicated in an extended period of time. For example, you may have created a test subscription before promoting your tables to another subscription in a production environment. The dmshowlogdependency command will include the log files that InfoSphere CDC would need to use if that subscription was started. - You have occasionally long running transactions in your database. Long running transactions affect log dependency regardless of whether or not they include tables that are being replicated. A long running transaction may be from a batch job that requires a significant period of time to execute, but may also be from an application or interactive user session that makes a small number of data changes and waits a long time before committing those changes. Note that when one or more of your subscriptions has some latency, log dependency may be affected by a transaction that was long running but has recently been committed. Resolution If you have test subscriptions and would like to keep them, you can change the data replication method for the table mappings from Mirror to Refresh. Note that this would mean that if you want to use this subscription in the future, all the tables would need to be refreshed. If there are occasional long running transactions in your database, you may want to monitor the database and determine if those long running transactions are necessary.To change the data replication method of a table: 1. Ensure that you have ended any active replication on the subscription. 2. Start Management Console and log into Access Server. 3. Click Configuration > Subscriptions. 4. Select the subscription that contains the tables you want to remove from mirroring activity. 5. On the Table Mappings view, select all the table mappings within the subscription. 6. Right-click and select Change replication method. 7. Enable Refresh (Snapshot). This changes the replication method and status of each mapped table to Refresh.
You can also set the bookmark at source for the test subscription, which will not look for long running transactions. To identify open transactions that may be long running, run the following query against the source database: select a.USERNAME,a.PROGRAM,a.PROCESS,a.CLIENT_INFO,b.START_DATE from gv$session a inner join gv$transaction b on a.saddr=b.ses_addr order by b.START_DATE asc; 85
Parent topic:Troubleshooting data replication maintenance
86 Encountering a CHC9214E DB2 Trace could not be started. All OPx trace buffers are in use or CHC9217E DB2 CAF Message: [] message in the event log on InfoSphere CDC for z/OS Environment InfoSphere® CDC for z/OS®. Symptoms InfoSphere CDC for z/OS stops DB2® activity. One of the following errors displays in the Management Console event log: - CHC9214E DB2 Trace could not be started. All OPx trace buffers are in use. - CHC9217E DB2 CAF Message: []. Causes InfoSphere CDC requires DB2 tracing to run so that it can be notified when the DB2 log is extended. These errors indicate that InfoSphere CDC was unable to start a trace because none of the DB2 OPx trace buffers are available for use. There are several possible causes for this for DB2 version 8 or earlier: - For DB2, cancelling the InfoSphere CDC address space leaves the trace active. This does not allow InfoSphere CDC to stop the trace in the OPx buffer it is using, and DB2 tracing can fail to start. - If you configured InfoSphere CDC to use a specific OPx buffer, and that buffer is being used by something else (such as another instance of InfoSphere CDC), DB2 tracing can fail to start. - If you configured InfoSphere CDC to select the first available OPx buffer, but there are no available OPx buffers (the maximum is 8 buffers), then DB2 tracing can fail to start. Resolution If you receive the CHC9214E error, request that your DBA release at least one of the allocated DB2 OPx buffers and then restart InfoSphere CDC using the START command. If you receive the CHC9217E error, contact your DBA to review the DB2 CAF (Call Attach File) error message. If the CAF message indicates that an error has occurred, your database administrator should correct the problem. Once the correction is made, restart the InfoSphere CDC address space using the START command.
Parent topic:Troubleshooting data replication maintenance
87 Troubleshooting network and connectivity issues Network connectivity issues can cause data replication to terminate. In this section, you will learn:
- Encountering communication interruptions
88 Encountering communication interruptions Environment InfoSphere® CDC for all replication engines. Symptoms InfoSphere CDC cannot work because of a lost connection. You may receive errors issued in the InfoSphere CDC Event Log, similar to the following ones: For InfoSphere CDC for z/OS®: - CHC6503E (DTSPROD) Communications link to ADDRESS.IBM.COM:0 abnormally terminated by remote system (link <#>, process <#>) - CHC9500E TCP/IP name(string) service call has failed. The returned error is < description of error returned by TCP/IP> for value of . For all other InfoSphere CDC replication engines: - COMMS : send failed -- link tag=<#> is not found - IBM InfoSphere Change Data Capture heartbeat timeout has occurred. Replication will end. The timeout is currently <#> minutes. There may be a network problem or a problem on the remote system. Resolve the problem and then restart replication. - CHANNEL: [tag=<#>, name="", type=]: Connection reset - COMMS : send failed -- link tag=<#> is not found Causes A network connection failed. A network can disconnect because of several scenarios: - Your firewall detects an idle connection and proceeds to close it. This condition is unknown to the application until it tries to use the connection (such as sending a message to the remote system). - Your firewall configurations have changed, which can cause an already established connection to be dropped. - There is a network disruption, such as a planned maintenance window or unplanned power outage, which may cause the connection to be dropped. If the cause is in the network, generally both sides of the connection will receive connection reset errors, but the timing may differ as the two sides will not know (or be informed) of the connection reset error until there is an attempt to use the connection. Therefore, the connection drop may be detected at different times. Resolution A reset connection error indicates that the communication link to InfoSphere CDC has been terminated by the server to which InfoSphere CDC was connected. This error is not caused by the instance of InfoSphere CDC which has reported the problem. Determine if the connection reset error is reported for a remote connection to Access Server or to InfoSphere CDC installed on your source or target system. If the connection terminated was to Access Server, you would receive the following error message: Access Server has detected that the connection to datastore has been lost. Management Console will now disconnect from the datastore. Monitor agent connection (host: < > port < >) lost. For a connection terminated to a peer installation of InfoSphere CDC, investigate the event log in Management Console for any errors there. If errors have occurred in Access Server or the InfoSphere CDC peer instance, which appear to have caused the problem, attempt to resolve the problem reported on that system. If you are 89 unable to resolve the problem, then log a PMR with IBM® Support for the Access Server or peer InfoSphere CDC instance on which the problem occurred. If both InfoSphere CDC and the remote end of the connection report a communications error (that is an ECONNRESET error), contact your network administrator to investigate the cause of the problem. This type of error generally means that the server or some router or firewall in between the two servers has caused the connection reset error to occur. Contact your administrator to complete the following tasks: - Investigate the connection and reset more reasonable firewall idle timeout values. If the problem is because of the firewall closing the connection due to idle timeout, try decreasing the KEEP_ALIVE_TIMEOUT system parameter for InfoSphere CDC . The suggested value is 20 seconds. - Check for viruses which may inject connection-reset packets into an established stream, causing the operating system to behave as if the connection was terminated by the remote.
Parent topic:Troubleshooting network and connectivity issues
90 Getting fixes from Fix Central You can use Fix Central to find the fixes that are recommended by IBM Support for a variety of products, including InfoSphere® CDC. With Fix Central, you can search, select, order, and download fixes for your system with a choice of delivery options. A InfoSphere CDC product fix might be available to resolve your problem. To find and install fixes for InfoSphere CDC for z/OS 1. Go to www.ibm.com/ibmlink. 2. View a list of fixes available for InfoSphere CDC for z/OS® by selecting Service Information Search and entering the FMID for your version. The FMID is shown in your program directory (for example HCHC650 for version 6.5). A list of all available PTFs will be displayed which you can order. 3. Optionally, configure your user profile to have notifications sent when new PTFs become available by selecting Automatic Software Alert Process. To find and install fixes for all InfoSphere CDC for all replication engines other than InfoSphere CDC for z/OS 1. Obtain the tools that are required to get the fix. If not installed, obtain your product update installer. The installer can be downloaded from Fix Central.This site provides download, installation, and configuration instructions for the update installer. 2. Select InfoSphere CDC as the product, and select one or more check boxes that are relevant to the problem that you want to resolve. 3. Identify and select the fix that is required. 4. Download the fix: A. Open the download document and follow the link in the Download Package section. B. When downloading the file, ensure that the name of the maintenance file is not changed. This change might be intentional, or it might be an inadvertent change that is caused by certain Web browsers or download utilities. 5. Apply the fix: A. Follow the instructions in the Installation Instructions section of the download document. B. For more information, see the Installing fixes with the Update Installer topic in the product documentation.
91 Subscribing to Support updates To stay informed of important information about the IBM products that you use, you can subscribe to updates. By subscribing to receive updates, you can receive important technical information and updates for specific IBM Support tools and resources. In this section, you will learn:
- Understanding types of Support updates You can subscribe to Support updates by using one of two approaches: RSS feeds or My Notifications.
92 Understanding types of Support updates You can subscribe to Support updates by using one of two approaches: RSS feeds or My Notifications. - RSS feeds - You can subscribe to the InfoSphere® CDC RSS feed to obtain current support information about the product.For general information about RSS, including steps for getting started and a list of RSS-enabled IBM web pages, visit the IBM Software Support RSS feeds site. - My Notifications - With My Notifications, you can subscribe to Support updates for any IBM product. (My Notifications replaces My Support, which is a similar tool that you might have used in the past.) With My Notifications, you can specify that you want to receive daily or weekly email announcements. You can specify what type of information you want to receive (such as publications, hints and tips, product flashes (also known as alerts), downloads, and drivers). My Notifications enables you to customize and categorize the products about which you want to be informed and the delivery methods that best suit your needs.
Until you modify your RSS feeds and My Notifications preferences, you receive notifications of updates that you have requested. You can modify your preferences when needed (for example, if you stop using one product and begin using another product). See also:
- To subscribe to InfoSphere CDC RSS feeds - To subscribe to My Notifications Parent topic:Subscribing to Support updates
93 To subscribe to InfoSphere CDC RSS feeds Procedure
1. Go to IBM® Support RSS Feeds Web site. 2. Click RSS feeds for Information Management productsInfoSphere® Change Data Capture. 3. Click Subscribe Now.
Parent topic:Understanding types of Support updates
Related information - IBM Software Support RSS feeds - Subscribe to My Notifications support content updates - My notifications for IBM technical support - My notifications for IBM technical support overview
94 To subscribe to My Notifications Procedure
1. Go to the IBM® Support Portal. 2. Click My Notifications in the Notifications portlet. 3. Sign in using your IBM ID and password, and click Submit. 4. Click the Subscribe tab. 5. Select the appropriate software brand or type of hardware. 6. Select one or more products by name and click Continue. 7. Select your preferences for how to receive updates, whether by email, online in a designated folder, or as an RSS or Atom feed. 8. Select the types of documentation updates that you want to receive, for example, new information about product downloads and discussion group comments. 9. Click Submit.
Parent topic:Understanding types of Support updates
Related information - IBM Software Support RSS feeds - Subscribe to My Notifications support content updates - My notifications for IBM technical support - My notifications for IBM technical support overview
95 Contacting IBM Support IBM® Support provides assistance with product defects. Before contacting support, ensure you have the appropriate information for IBM Support. Also, your company must have an active IBM software maintenance contract, and you must be authorized to submit problems to IBM. For information about the types of maintenance contracts available, see Enhanced Support in the Software Support Handbook at: techsupport.services.ibm.com/guides/services.html In this section, you will learn:
- Determining your version of InfoSphere CDC Before contacting support, ensure you identify the version and build number of the InfoSphere® CDC product you are currently running. - Collecting InfoSphere CDC information for IBM Support To help IBM Support understand and troubleshoot your problem, provide as much InfoSphere CDC information to them as possible. - Collecting performance statistics on a subscription for IBM Support When encountering a performance issue with your subscriptions, the IBM Support team requires statistics information to properly analyze the subscription. By default, collecting statistics for a subscription is automatically enabled. - Exchanging information with IBM Support To diagnose or identify a problem, it is sometimes necessary to provide IBM Support with data and information from your system. In other cases, IBM Support might provide you with tools or utilities to use for problem determination. Submitting diagnostic information to IBM can help IBM Support begin a Problem Management Report (PMR). If you have a problem and have opened a PMR to find a solution, problem determination data is needed to find a solution. - Reporting a problem to IBM Support You can contact IBM Support with a problem. Parent topic:Troubleshooting
96 Determining your version of InfoSphere CDC Before contacting support, ensure you identify the version and build number of the InfoSphere® CDC product you are currently running. Use the dmshowversion command to display the version and build number of InfoSphere CDC. Run this command before you contact your IBM® representative. Note: This command is not available for InfoSphere CDC for z/OS®. For z/OS version information, consult the SPOOLed output. A complete description of the installation, including all maintenance (PTFs) applied is available there. See also:
- To determine your version of InfoSphere CDC Parent topic:Contacting IBM Support
97 To determine your version of InfoSphere CDC Procedure
Enter the following command:dmshowversion [-L ] where is the name of the language locale used for the InfoSphere® CDC instance. The default is your machine's locale.
Parent topic:Determining your version of InfoSphere CDC
98 Collecting InfoSphere CDC information for IBM Support To help IBM® Support understand and troubleshoot your problem, provide as much InfoSphere® CDC information to them as possible. Collecting InfoSphere CDC information on InfoSphere CDC for z/OS All SPOOLed output for the InfoSphere CDC for z/OS® address space should be collected. If a dump has been generated, the output from the dump should be collected as well. All data from the mainframe should be sent in TERSED format as this retains the formatting of the data for the mainframe while it is transferred using non-mainframe systems, ensuring the data is useful for IBM Support. It has the added advantage of reducing the size of the files. Files should be named with the extension .trs. See the documentation for AMATERSE, if you need assistance. Collecting InfoSphere CDC information on all replication engines other than InfoSphere CDC for z/OS You can collection information by running the dmsupportinfo command, which creates a ZIP file containing InfoSphere CDC information useful to a Support personnel. Send this file to IBM Support when contacting them regarding your problem.In some cases, you may not be able to start your InfoSphere CDC instance. You can run the dmsupportinfo command without a running instance; however, the command will collect a limited scope of data. If you are unclear as to whether the problem is on the source or target, you can run the command on both sides. Once you run this command, it outputs the name and location of the generated ZIP file to provide to IBM Support.
- To collect InfoSphere CDC information Parent topic:Contacting IBM Support
99 To collect InfoSphere CDC information Procedure
1. Ensure that your InfoSphere® CDC is running. 2. Switch to the /bin directory. 3. Run dmsupportinfo -I . Note: If you are not be able to start your InfoSphere CDC instance, you can run this command withou the -I parameter; however, the command will collect a limited scope of data.
Parent topic:Collecting InfoSphere CDC information for IBM Support
100 Collecting performance statistics on a subscription for IBM Support When encountering a performance issue with your subscriptions, the IBM® Support team requires statistics information to properly analyze the subscription. By default, collecting statistics for a subscription is automatically enabled. Note: Collecting performance statistics is not supported with InfoSphere® CDC for z/OS®. InfoSphere CDC collects statistics information on each subscription every 30 seconds. This is ideal if you have a subscription that is replicating a day's worth of data (that is, 24 hours of data). See also:
- To collect performance statistics on a subscription Parent topic:Contacting IBM Support
101 To collect performance statistics on a subscription Procedure
1. Start Management Console and log into Access Server. 2. Ensure you are connected to the datastore for the subscription for which you want to collect information. 3. Click Help > Service Information > Support Assistant. 4. Select the Enable Collection check box for the datastore for which you want to collect information. 5. Click Options and click Detailed to collect detailed information for the selected datastore. 6. Click OK. 7. Select the location where you want Support Assistant to store the output file for the generated information. 8. Allow Support Assistant to clean up diagnostic files after collection by selecting Clean-up diagnostic files after collection. 9. Click Collect Now to start collecting the messages.
Parent topic:Collecting performance statistics on a subscription for IBM Support
102 Exchanging information with IBM Support To diagnose or identify a problem, it is sometimes necessary to provide IBM Support with data and information from your system. In other cases, IBM Support might provide you with tools or utilities to use for problem determination. Submitting diagnostic information to IBM® can help IBM Support begin a Problem Management Report (PMR). If you have a problem and have opened a PMR to find a solution, problem determination data is needed to find a solution. See also:
- To send information to IBM Support - To receive files from IBM Support Parent topic:Contacting IBM Support
103 To send information to IBM Support Procedure
1. Open a problem management record (PMR). 2. Collect the diagnostic data that you need. Diagnostic data helps reduce the time that it takes to resolve your PMR. You can collect the diagnostic data manually (through logs) or automatically (using Support Assistant): - Collect the data automatically by using Support Assistant - On z/OS®, collect all SPOOLed output for the InfoSphere® CDC address space. - On Linux, UNIX, and Windows, collect the data manually by referring to trace logs and event messages. 3. Compress the files by using the TRS format and the TRSMAIN utility on z/OS; use the ZIP or TAR format on Linux, UNIX, and systems. 4. Transfer the files to IBM. You can use one of the following methods to transfer the files to IBM: - Support Assistant - The Service Request tool - Standard data upload methods: FTP, HTTP - Secure data upload methods: FTPS, SFTP, HTTPS - Email If you are using a z/OS product and you use ServiceLink / IBMLink to submit PMRs, you can send diagnostic data to IBM Support in an email or by using FTP. All of these data exchange methods are explained on the IBM Support site.
Parent topic:Exchanging information with IBM Support
104 To receive files from IBM Support Procedure
1. Ensure that your IBM technical-support representative has provided you with the preferred server to use for downloading the files and the exact directory and file names to access. 2. Use FTP to connect to the site that your IBM technical-support representative provided and log in as anonymous. Use your email address as the password. 3. Change to the appropriate directory: A. Change to the /fromibm directory. cd fromibm
B. Change to the directory that your IBM technical-support representative provided:cd nameofdirectory
4. Enable binary mode for your session:binary
5. Use the get command to download the file that your IBM technical-support representative specified:get filename.extension
6. End your FTP session:quit
Parent topic:Exchanging information with IBM Support
105 Reporting a problem to IBM Support You can contact IBM® Support with a problem. See also:
- To contact IBM Support Parent topic:Contacting IBM Support
106 To contact IBM Support Procedure
1. Define the problem, gather background information, and determine the severity of the problem. For help, see the Contacting IBM® in the Software Support Handbook: techsupport.services.ibm.com/guides/beforecontacting.html 2. Gather diagnostic information. 3. Submit your problem to IBM Support in one of the following ways: - Using IBMSupport Assistant (ISA): - Online: Click the Report problems tab on the IBM Software Support site: www.ibm.com/software/support/probsub.html - By phone: For the phone number to call in your country, go to the Contacts page of the Software Support Handbook: techsupport.services.ibm.com/guides/contacts.html What to do next
If the problem you submit is for a software defect or for missing or inaccurate documentation, IBM Support creates an Authorized Program Analysis Report (APAR). The APAR describes the problem in detail. Whenever possible,IBM Support provides a workaround that you can implement until the APAR is resolved and a fix is delivered. IBM publishes resolved APARs on the IBM Support web site daily, so that other users who experience the same problem can benefit from the same resolution. Parent topic:Reporting a problem to IBM Support
107 Troubleshooting If you encounter issues while running InfoSphere® CDC, you have a number of options for tracking and troubleshooting issues to help with problem resolution. There are three methods that you can use in InfoSphere CDC for tracking and troubleshooting issues: - Data Collection with the IBM® Support Assistant (ISA DC) - Management Console Support Assistant - The dmsupportinfo command, which is executed on the replication engine If you are trying to troubleshoot issues with InfoSphere CDC version 10.2 or later on Linux, UNIX and Windows operating systems, you should use the ISA DC tool unless otherwise instructed by IBM Technical Support. In this section, you will learn:
- Using the IBM Support Assistant (ISA DC) - Contacting IBM Support IBM Support provides assistance with product defects.
108 Using the IBM Support Assistant (ISA DC) You can use the IBM® Support Assistant Data Collection tool (ISA DC) to collect InfoSphere® CDC data to provide to IBM Technical Support to assist you in troubleshooting issues with InfoSphere CDC, to request a product enhancement or to ask a question about InfoSphere CDC. ISA DC can be used with InfoSphere CDC replication engines that are version 10.2 or later, except InfoSphere CDC for z/OS®. The ISA DC tool is included in the InfoSphere CDC installation process, and does not require configuration. The executable files are located in the isa folder in the InfoSphere CDC directory. Simply run the isadc.bat, isadc.sh or index.html file, as appropriate, to launch the tool. Prerequisites and considerations for using ISA DC The following prerequisite must be satisfied on the machine on which ISA DC will be run, in order to successfully use the tool: - IBM JRE/JDK version 1.6 or later The following issues should be taken into consideration before you attempt to use ISA DC: - ISA DC cannot be run remotely. It must be run on the machine where the instance is configured. - ISA DC cannot be used to collect data from InfoSphere CDC for z/OS. - If InfoSphere CDC is installed but you have not configured an instance or are unable to configure an instance, ISA DC can still be used to collect minimal data to assist IBM Technical Support in resolving the issue. See also:
- To use ISA DC to collect data for a product problem (command line) - To use ISA DC to collect data for a product problem (GUI) - To use ISA DC to collect data for a question or an enhancement request (command line) - To use ISA DC to collect data for a question or an enhancement request (GUI) Parent topic:Troubleshooting
109 To use ISA DC to collect data for a product problem (command line) Procedure
1. Launch the IBM® Support Assistant.Run the isadc.bat or isadc.sh file, located in the isa\isadc folder in the root directory of the InfoSphere® CDC instance.
2. Enter 1 to accept the license agreement and press Enter.After the license agreement has been accepted, it will not be shown again.
3. Provide a file name and press Enter.The name provided will be given to the .zip file containing the data collection results. If you do not want to assign a name to the data collection results, press Enter and a default name will be used.
4. Enter 1 to confirm your chosen file name and press Enter to continue. 5. Enter 1 to run the InfoSphere Change Data CaptureSupport Assistant Data Collector and press Enter.The Welcome page is displayed.
6. Read the Welcome page information and enter 1 to proceed. Press Enter. 7. Enter 1 to collect data for a product problem and press Enter. 8. Enter 1 to process your input and continue collecting data. Press Enter.If you want to cancel the collection, enter 2 and press Enter. If you want to go back and change your input for the previous step, enter 3 and press Enter.
9. Select the name of the InfoSphere CDC instance for which data will be collected. If you have multiple instances of InfoSphere CDC configured, you will be asked to select which instance for which you want to collect. Enter the corresponding number for the instance name and press Enter. If you have a single InfoSphere CDC instance configured, it will be selected automatically and this step will be skipped. Even if you do not have an instance configured, ISA DC will still collect what data is available. If no instance is configured, you can skip to Step 14.
10. Enter 1 to process your input and continue collecting data. Press Enter.If you want to cancel the collection, enter 2 and press Enter. If you want to go back and change your input for the previous step, enter 3 and press Enter.
11. If your selected instance is not running, you will be alerted by ISA DC. As only minimal data is available if the instance is stopped, it is preferable that the instance be running during data collection.Try to start your instance. When the instance is running, enter 1 and press Enter. If you cannot start your instance and want to continue the data collection process, enter 2 and press Enter.
110 12. Enter 1 to process your input and continue collecting data. Press Enter.If you want to cancel the collection, enter 2 and press Enter. If you want to go back and change your input for the previous step, enter 3 and press Enter.
13. If the instance is running, you will be asked for information regarding when the problem occurred. A. Enter the date and time when you think the problem began and press Enter. This information must be entered in the following format: yyyy-mm-dd hh:mm:ss
B. Enter 1 to process your input and continue collecting data. Press Enter.If you want to cancel the collection, enter 2 and press Enter. If you want to go back and change your input for the previous step, enter 3 and press Enter.
C. Determine the period of time for which the data will be collected and press Enter.The amount specified will be applied as a before value and an after value to the date and time specified previously. For example, if you select 1 Day as the time period, data will be collect for 24 hours before the specified date and time and for the 24 hours after the specified date and time.
D. Enter 1 to process your input and continue collecting data. Press Enter.If you want to cancel the collection, enter 2 and press Enter. If you want to go back and change your input for the previous step, enter 3 and press Enter.
14. Select the method to transfer the data collection archive file and press Enter. Choose one of the following options: - Send using secure transfer to IBM Support (HTTPS)—Sends the .zip file to IBM Support using a secure protocol. - Send using FTP to IBM Support (unencrypted)—Sends the .zip file to IBM Support using an unencrypted protocol. - Send using FTP to another location (unencrypted)—Sends the .zip file to a recipient of your choice, using an unencrypted protocol. - End the collection without sending—Ends the data collection and creates the .zip file, but does not transfer it.
15. Enter 1 to process your input and continue collecting data. Press Enter.If you want to cancel the collection, enter 2 and press Enter. If you want to go back and change your input for the previous step, enter 3 and press Enter.
16. If you chose to end the collection without sending the output, ISA DC will notify your when the .zip file has been successfully created. Enter 1 and press Enter to exit the application. 17. If you chose to transfer the file using HTTPS, follow these steps: A. If you want to receive a confirmation email when the upload was successful, 111 enter an email address and press Enter. If you do not want to receive confirmation, press Enter to continue. B. Enter 1 to process your input and continue collecting data. Press Enter.If you want to cancel the collection, enter 2 and press Enter. If you want to go back and change your input for the previous step, enter 3 and press Enter.
C. Enter the PMR number that was given to you by IBM Technical Support and press Enter. Ensure that the PMR number follows the required naming convention of PMRNumber.BranchNumber.CountryCode. If an unknown PMR number is entered, you will be asked to correct the PMR number and re-send the data.
D. Enter 1 to process your input and continue collecting data. Press Enter.If you want to cancel the collection, enter 2 and press Enter. If you want to go back and change your input for the previous step, enter 3 and press Enter.
18. If you chose to transfer the file to IBM Technical Support using unencrypted FTP, follow these steps: A. Enter the PMR number that was given to you by IBM Technical Support and press Enter. Ensure that the PMR number follows the required naming convention of PMRNumber.BranchNumber.CountryCode. If an unknown PMR number is entered, you will be asked to correct the PMR number and re-send the data.
B. Enter 1 to process your input and continue collecting data. Press Enter.If you want to cancel the collection, enter 2 and press Enter. If you want to go back and change your input for the previous step, enter 3 and press Enter.
19. If you chose to transfer the file using unencrypted FTP, follow these steps: A. Enter the FTP host name and press Enter. B. Enter the user name and press Enter. C. Enter the password for the user name and press Enter. D. Enter the path for the directory on the FTP server and press Enter. E. Enter 1 to process your input and continue collecting data. Press Enter.If you want to cancel the collection, enter 2 and press Enter. If you want to go back and change your input for the previous step, enter 3 and press Enter.
20. When you receive notice that the operation has completed successfully, enter 1 and press Enter to exit the application.
Parent topic:Using the IBM Support Assistant (ISA DC)
112 To use ISA DC to collect data for a product problem (GUI) Procedure
1. Launch the IBM® Support Assistant.Run the index.html file, located in the isa\isadc folder in the root directory of the InfoSphere® CDC instance.
2. Read the license agreement and click OK to accept it.After the license agreement has been accepted, it will not be shown again.
3. Click Start.The Welcome screen opens.
4. Click OK. 5. Select A product problem from the drop down box. 6. Click OK. 7. Select the name of an InfoSphere CDC instance from the drop down list and click OK.If you have multiple instances of InfoSphere CDC configured, you will be asked to select which instance for which you want to collect. If you have a single InfoSphere CDC instance configured, it will be selected automatically and this step will be skipped.
8. If your selected instance is not running, you will be alerted by ISA DC. As only minimal data is available if the instance is stopped, it is preferable that the instance be running during data collection.Try to start your instance. When the instance is running, select Yes, I have started the instance from the drop down box and click OK. If you cannot start your instance and want to continue the data collection process, select No, continue with minimal data collection from the drop down box and click OK.
9. If the instance is running, you will be asked for information regarding when the problem occurred. Enter the date and time when you think the problem began and click OK.This information must be entered in the following format: yyyy-mm- dd hh:mm:ss.
10. Determine the period of time for which the data will be collected and click OK. Choose one of the following values: - 6 hours - 12 hours - 1 Day - 2 Days - 7 Days The amount specified will be applied as a before value and an after value to the date and time specified previously. For example, if you select 1 Day as the time period, data will be collect for 24 hours before the specified date and time and for the 24 hours after the specified date and time.
113 11. If you chose to end the collection without sending the output, select Do not transfer data to IBM. ISA DC will notify you when the .zip file has been successfully created. 12. If you want to transfer the data to IBM using a secure transfer (HTTPS), select the Transfer to IBM option. A. Choose the HTTPS transfer type option. B. Enter the PMR number that was given to you by IBM Technical Support. Ensure that the PMR number follows the required naming convention of PMRNumber.BranchNumber.CountryCode. If an unknown PMR number is entered, you will be asked to correct the PMR number and re-send the data.
C. Enter your email address. D. Click Transfer. 13. If you want to transfer the data to IBM using unencrypted FTP, select the Transfer to IBM option. A. Choose the FTP transfer type option. B. Enter the PMR number that was given to you by IBM Technical Support. Ensure that the PMR number follows the required naming convention of PMRNumber.BranchNumber.CountryCode. If an unknown PMR number is entered, you will be asked to correct the PMR number and re-send the data.
C. Click Transfer. 14. If you choose to send the data to a location other than IBM using unencrypted FTP, click Transfer to another server via FTP A. Enter the email address or IP address of the recipient in the Hotmail/IP Address field. B. Enter the user name. C. Enter the password. D. Enter the path for the directory on the FTP server. E. Click Transfer. 15. When you receive notice that the operation has completed successfully, click Browse directory if you want to see the file you created or click Start New Collection to collect more data.To exit the application, close your browser tab or window.
Parent topic:Using the IBM Support Assistant (ISA DC)
114 To use ISA DC to collect data for a question or an enhancement request (command line) Procedure
1. Launch the IBM® Support Assistant.Run the isadc.bat or isadc.sh file, located in the isa\isadc folder in the root directory of the InfoSphere® CDC instance.
2. Enter 1 to accept the license agreement and press Enter.After the license agreement has been accepted, it will not be shown again.
3. Provide a file name and press Enter.The name provided will be given to the .zip file containing the data collection results. If you do not want to assign a name to the data collection results, press Enter and a default name will be used.
4. Enter 1 to confirm your chosen file name and press Enter to continue. 5. Enter 1 to run the InfoSphere Change Data CaptureSupport Assistant Data Collector and press Enter.The Welcome page is displayed.
6. Read the Welcome page information and enter 1 to proceed. Press Enter. 7. Enter 2 to collect data for a question or an enhancement request and press Enter. 8. Enter 1 to process your input and continue collecting data. Press Enter.If you want to cancel the collection, enter 2 and press Enter. If you want to go back and change your input for the previous step, enter 3 and press Enter.
9. Select the method to transfer the data collection archive file and press Enter. Choose one of the following options: - Send using secure transfer to IBM Support (HTTPS)—Sends the .zip file to IBM Support using a secure protocol. - Send using FTP to IBM Support (unencrypted)—Sends the .zip file to IBM Support using an unencrypted protocol. - Send using FTP to another location (unencrypted)—Sends the .zip file to a recipient of your choice, using an unencrypted protocol. - End the collection without sending—Ends the data collection and creates the .zip file, but does not transfer it.
10. Enter 1 to process your input and continue collecting data. Press Enter.If you want to cancel the collection, enter 2 and press Enter. If you want to go back and change your input for the previous step, enter 3 and press Enter.
11. If you chose to end the collection without sending the output, ISA DC will notify your when the .zip file has been successfully created. Enter 1 and press Enter to exit the application. 12. If you chose to transfer the file using HTTPS, follow these steps: A. If you want to receive a confirmation email when the upload was successful, 115 enter an email address and press Enter. If you do not want to receive confirmation, press Enter to continue. B. Enter 1 to process your input and continue collecting data. Press Enter.If you want to cancel the collection, enter 2 and press Enter. If you want to go back and change your input for the previous step, enter 3 and press Enter.
C. Enter the PMR number that was given to you by IBM Technical Support and press Enter. Ensure that the PMR number follows the required naming convention of PMRNumber.BranchNumber.CountryCode. If an unknown PMR number is entered, you will be asked to correct the PMR number and re-send the data.
D. Enter 1 to process your input and continue collecting data. Press Enter.If you want to cancel the collection, enter 2 and press Enter. If you want to go back and change your input for the previous step, enter 3 and press Enter.
13. If you chose to transfer the file to IBM Technical Support using unencrypted FTP, follow these steps: A. Enter the PMR number that was given to you by IBM Technical Support and press Enter. Ensure that the PMR number follows the required naming convention of PMRNumber.BranchNumber.CountryCode. If an unknown PMR number is entered, you will be asked to correct the PMR number and re-send the data.
B. Enter 1 to process your input and continue collecting data. Press Enter.If you want to cancel the collection, enter 2 and press Enter. If you want to go back and change your input for the previous step, enter 3 and press Enter.
14. If you chose to transfer the file using unencrypted FTP, follow these steps: A. Enter the FTP host name and press Enter. B. Enter the user name and press Enter. C. Enter the password for the user name and press Enter. D. Enter the path for the directory on the FTP server and press Enter. E. Enter 1 to process your input and continue collecting data. Press Enter.If you want to cancel the collection, enter 2 and press Enter. If you want to go back and change your input for the previous step, enter 3 and press Enter.
15. When you receive notice that the operation has completed successfully, enter 1 and press Enter to exit the application.
Parent topic:Using the IBM Support Assistant (ISA DC)
116 To use ISA DC to collect data for a question or an enhancement request (GUI) Procedure
1. Launch the IBM® Support Assistant.Run the index.html file, located in the isa\isadc folder in the root directory of the InfoSphere® CDC instance.
2. Read the license agreement and click OK to accept it.After the license agreement has been accepted, it will not be shown again.
3. Click Start.The Welcome screen opens.
4. Click OK. 5. Select A question or enhancement request from the drop down box. 6. Click OK. 7. If you chose to end the collection without sending the output, select Do not transfer data to IBM. ISA DC will notify you when the .zip file has been successfully created. 8. If you want to transfer the data to IBM using a secure transfer (HTTPS), select the Transfer to IBM option. A. Choose the HTTPS transfer type option. B. Enter the PMR number that was given to you by IBM Technical Support. Ensure that the PMR number follows the required naming convention of PMRNumber.BranchNumber.CountryCode. If an unknown PMR number is entered, you will be asked to correct the PMR number and re-send the data.
C. Enter your email address. D. Click Transfer. 9. If you want to transfer the data to IBM using unencrypted FTP, select the Transfer to IBM option. A. Choose the FTP transfer type option. B. Enter the PMR number that was given to you by IBM Technical Support. Ensure that the PMR number follows the required naming convention of PMRNumber.BranchNumber.CountryCode. If an unknown PMR number is entered, you will be asked to correct the PMR number and re-send the data.
C. Click Transfer. 10. If you choose to send the data to a location other than IBM using unencrypted FTP, click Transfer to another server via FTP A. Enter the email address or IP address of the recipient in the Hotmail/IP Address field. B. Enter the user name. C. Enter the password. D. Enter the path for the directory on the FTP server. E. Click Transfer. 11. When you receive notice that the operation has completed successfully, click Browse directory if you want to see the file you created or click Start New Collection to collect more data.To exit the application, close your browser tab or 117 window.
Parent topic:Using the IBM Support Assistant (ISA DC)
118 Contacting IBM Support IBM® Support provides assistance with product defects. Before contacting support, ensure you have the appropriate information for IBM Support. Also, your company must have an active IBM software maintenance contract, and you must be authorized to submit problems to IBM. For information about the types of maintenance contracts available, see Enhanced Support in the Software Support Handbook at: techsupport.services.ibm.com/guides/services.html In this section, you will learn:
- Determining your version of InfoSphere CDC Before contacting support, ensure you identify the version and build number of the InfoSphere® CDC product you are currently running. - Collecting InfoSphere CDC information for IBM Support To help IBM Support understand and troubleshoot your problem, provide as much InfoSphere CDC information to them as possible. - Collecting performance statistics on a subscription for IBM Support When encountering a performance issue with your subscriptions, the IBM Support team requires statistics information to properly analyze the subscription. By default, collecting statistics for a subscription is automatically enabled. - Exchanging information with IBM Support To diagnose or identify a problem, it is sometimes necessary to provide IBM Support with data and information from your system. In other cases, IBM Support might provide you with tools or utilities to use for problem determination. Submitting diagnostic information to IBM can help IBM Support begin a Problem Management Report (PMR). If you have a problem and have opened a PMR to find a solution, problem determination data is needed to find a solution. - Reporting a problem to IBM Support You can contact IBM Support with a problem. Parent topic:Troubleshooting
119
