Single scrape events and errors
The following events are explicitly generated by single scrape and are visible in the IBM InfoSphere Change Data Capture (InfoSphere CDC) Event Log:
•I_SHAREDSCRAPE_COMPONENT_STARTED 2920 EventCategory.INFORMATION, EventSeverity.INFO
The single scrape component has started. The staging store is {0}% full.
•I_SHAREDSCRAPE_COMPONENT_STARTED_EMPTY 2921, EventCategory.INFORMATION, EventSeverity.INFO
The single scrape component has started. The staging store is empty.
•I_SHAREDSCRAPE_SUBSCRIPTION_STARTED 2922, EventCategory.INFORMATION, EventSeverity.INFO
Subscription {0} has started using the single scrape staging store.
•I_SHAREDSCRAPE_SUBSCRIPTION_REJECTED 2923 EventCategory.INFORMATION, EventSeverity.INFO
Subscription {0} ca not use the single scrape staging store. It runs with a private log reader and log parser.
•I_SHAREDSCRAPE_SUBSCRIPTION_KICKED_OUT 2924 EventCategory.INFORMATION, EventSeverity.INFO
Subscription {0} has stopped using the single scrape staging store, and is now using a private log reader and log parser.
•W_SINGLESCRAPE_STAGINGSTORE_INCORRECT_VERSION 2927 EventCategory.INFORMATION, EventSeverity.WARNING
Incorrect single scrape staging store version. This version: {0} Expected version: {1}.
•W_SINGLESCRAPE_STAGINGSTORE_DISK_WRITE_ERROR 2928 EventCategory.INFORMATION, EventSeverity.WARNING
The single scrape staging store experienced an IOException when writing data to disk. This error is most likely an out-of-disk-space error. No data has been lost, as the data is still in memory. No further operations will be stored until some of the data in the staging store is no longer needed. Consider refreshing subscription tables with stale data, unconfiguring any unneeded subscription tables, or deleting any unneeded subscriptions. Do not stop the instance until this problem is rectified.
•W_SINGLESCRAPE_STAGINGSTORE_DISK_SPACE_QUOTA_EXCEEDED 2929 EventCategory.INFORMATION, EventSeverity.WARNING
The single scrape staging store disk space usage has exceeded the quota. No further operations will be stored until the disk space usage is below the quota again. This situation could affect source performance, and could be because of poor target apply performance. Consider increasing the quota, refreshing subscription tables with stale data, unconfiguring any unneeded subscription tables, or deleting any unneeded subscriptions.
•W_SINGLESCRAPE_STAGINGSTORE_DISK_SPACE_QUOTA_EXCEEDED_INDEPENDENT 2950, EventCategory.INFORMATION, EventSeverity.WARNING
The single scrape staging store disk space usage has exceeded the quota. Some of the oldest data will be deleted from the store. Some subscriptions that were using the single scrape staging store might now need to run with a private scraper.
•W_SINGLESCRAPE_STAGINGSTORE_DISK_WRITE_ERROR_INDEPENDENT 2951 EventCategory.INFORMATION, EventSeverity.WARNING
The single scrape staging store experienced an IOException when writing data to disk. This situation is most likely an out-of-disk-space error. No data has been lost, as the data is still in memory. Some of the oldest data will be deleted from the store. Some subscriptions that were using the single scrape staging store might now need to run with a private scraper.
•E_SINGLESCRAPE_STAGINGSTORE_CORRUPT 2930 EventCategory.FATAL, EventSeverity.ERROR
The single scrape staging store is corrupted. To resolve this issue, you must clear the staging store using the dmclearstagingstore command-line utility.
•E_SINGLESCRAPE_STAGINGSTORE_CLEAR_WHILE_RUNNING 2931 EventCategory.FATAL, EventSeverity.ERROR
The single scrape staging store cannot be cleared while subscriptions
are mirroring.
are mirroring.
•E_SINGLESCRAPE_ERROR 2933 EventCategory.FATAL, EventSeverity.ERROR
Exception in single scrape.
Single scrape error events
The following events are explicitly generated by single scrape errors and are visible in the InfoSphere CDC Event Log:
•SingleScrape_StagingStore_TamperedWith =The single scrape staging store block file {0} is corrupted or has been tampered with.
•SingleScrape_StagingStore_FileNotDeleted =The deletion of the single scrape staging store block file {0} failed.
•SingleScrape_StagingStore_PersistAborted=The {0} instance was shut down with the abort option while the single scrape staging store was being written to disk.
•SingleScrape_DisconnectedScrape_NotAllowedWithIndependentSubs=The Single scrape staging store disconnected scrape feature cannot be enabled if subscriptions can run independently. To enable disconnected scrape, you must set the system property staging_store_can_run_independently to false, and then restart the engine.
Entries within braces, such as {0}, are placeholders for input values supplied to the event text at run time.
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.