Troubleshooting.Pdf
Total Page:16
File Type:pdf, Size:1020Kb
Troubleshooting4 Troubleshooting a problem7 Understanding where to find troubleshooting information10 Searching knowledge bases11 Using Support Assistant in Management Console12 To collect source and target information using Support Assistant13 Locating event messages14 To change the number of messages in the event log15 To remove event messages daily16 Locating log files17 Enabling detailed tracing for InfoSphere CDC for z/OS18 Enabling detailed InfoSphere CDC tracing for distributed systems19 To enable tracing using Management Console20 To enable tracing using the dmset command line utility21 To disable tracing using Management Console23 To disable tracing using the dmset command line utility24 Using trace options in Management Console25 To enable tracing for Management Console messages26 To enable tracing for Access Server messages27 To enable tracing for Access Server log information28 To disable tracing for Management Console messages29 To disable tracing for Access Server messages30 To disable tracing for Access Server log information31 Troubleshooting installation and configuration32 Encountering a previous instance of InfoSphere CDC in the instance list33 Encountering an ./oraclenativeapi.dll is not a valid win2k application message34 Encountering problems while using InfoSphere CDC for InfoSphere DataStage with Direct Connect35 Encountering a You must perform a FULL DATABASE BACKUP to start the FULL or BULK- LOGGED RECOVERY MODEL message when configuring InfoSphere CDC for DB2 for LUW37 Encountering a You must perform a FULL DATABASE BACKUP to start the FULL or BULK- LOGGED RECOVERY MODEL message when configuring InfoSphere CDC for Microsoft SQL Server38 Encountering a The RECOVERY MODEL for the database must be FULL or BULK-LOGGED message when configuring InfoSphere CDC for Microsoft SQL Server39 Encountering a Microsoft SQL Server is not configured for distribution. You must configure distribution in Microsoft SQL Server message when configuring InfoSphere CDC for Microsoft SQL Server40 Encountering a Cannot bulk load because the file "\\<server_name>\<directory_name>\<bcp_file_name>.bcp" could not be opened. Operating system error code 5 (Access is denied.) message when configuring InfoSphere CDC for Microsoft SQL Server41 Encountering a Failed to initialize SMO message when configuring InfoSphere CDC for Microsoft SQL Server42 Configuration tool hangs during instance creation43 Encountering an Invalid internal file structure contents detected in file <file_name> message and InfoSphere CDC for Oracle databases shuts down44 Encountering an com.datamirror.ts.commandlinetools.config.TsConfigError: IBM InfoSphere Change Data Capture communication failure error during configuration45 Troubleshooting Access Server and Management Console46 Encountering a Your account has been locked because the number of consecutive log-in failures exceeded the maximum allowed message when logging into Management Console47 Encountering a Could not connect to Access Server using the <server name> and <port number>. Access Server may be down or the host name and/or port number may be incorrect message when logging into Management Console or connecting to Access Server49 Encountering an Access Server could not connect to the database. Do you want to retry with a new name or password? or Management Console could not establish a connection to the datastore. An error has occurred while communicating with agent: java.net.ConnectException: Connection refused: connect message when connecting to a datastore in Management Console 51 Encountering an An error occurred during communication initialization message after changing the host name or port for a source datastore and attempting to replicate to the target53 Changing the host name or port for a target datastore shows duplicate subscriptions in Management Console54 Troubleshooting data replication55 Encountering a The single scrape staging store is corrupted. To resolve this issue, you must clear the staging store using the dmclearstagingstore command line utility message after running dmclearstagingstore56 Encountering a IBM InfoSphere Change Data Capture has encountered a critical data definition (DDL) change for source table <table name> and will shutdown message57 Encountering errors after applying DDL changes to in-scope tables for InfoSphere CDC for z/OS 58 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/OS61 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/OS63 Replicating tables without a primary key (event ID 9604) on InfoSphere CDC for Microsoft SQL Server64 Troubleshooting mirroring replication65 Mirroring stops when InfoSphere CDC encounters an apply error66 To set conflict detection and resolution for source row wins67 To map source and target tables for Adaptive Apply68 To ignore database errors when applying data changes to the target for all subscriptions using InfoSphere CDC for z/OS70 To ignore database errors when applying data changes to the target for all subscriptions71 Encountering a 911 SQL error message when configuring a table for mirror replication on InfoSphere CDC for z/OS72 Replication of tables containing LOB columns is slow73 Encountering an An error occurred while turning on supplemental logging for <table_name>. Unable to get exclusive lock on table <table_name> message when configuring a table for mirror replication on InfoSphere CDC for Oracle databases74 Troubleshooting refresh replication76 Refreshing fails with a referential integrity constraint violation reported in the event log77 Refreshing data to the target on InfoSphere CDC and encountering database errors78 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 databases79 Troubleshooting latency80 Experiencing increased latency and no data is replicating to the target database81 Experiencing increased latency and no data is replicating to the target database on InfoSphere CDC for z/OS82 Troubleshooting data replication maintenance84 Running dmshowlogdependency on InfoSphere CDC for Oracle databases references a dated log file85 Encountering a CHC9214E DB2 Trace could not be started. All OPx trace buffers are in use or CHC9217E DB2 CAF Message: [<DB2 CAF error>] message in the event log on InfoSphere CDC for z/OS87 Troubleshooting network and connectivity issues88 Encountering communication interruptions89 Getting fixes from Fix Central91 Subscribing to Support updates92 Understanding types of Support updates93 To subscribe to InfoSphere CDC RSS feeds94 To subscribe to My Notifications95 Contacting IBM Support96 Determining your version of InfoSphere CDC97 To determine your version of InfoSphere CDC98 Collecting InfoSphere CDC information for IBM Support99 To collect InfoSphere CDC information100 Collecting performance statistics on a subscription for IBM Support101 To collect performance statistics on a subscription102 Exchanging information with IBM Support103 To send information to IBM Support104 To receive files from IBM Support105 Reporting a problem to IBM Support106 To contact IBM Support107 Troubleshooting108 Using the IBM Support Assistant (ISA DC)109 To use ISA DC to collect data for a product problem (command line)110 To use ISA DC to collect data for a product problem (GUI)113 To use ISA DC to collect data for a question or an enhancement request (command line)115 To use ISA DC to collect data for a question or an enhancement request (GUI)117 Contacting IBM Support119 Troubleshooting a problem The first step in good problem analysis is to describe the problem completely. Without a problem description, you will not know where to start investigating the cause of the problem. This step includes asking yourself such basic questions as: - What are the symptoms? - Where is the problem happening? - When does the problem happen? - Under which conditions does the problem happen? - Is the problem reproducible? - Is this the first time the problem has happened? Was the system running acceptably before the problem occurred, and what were the last things that changed on the system before the problem occurred? - Is this a recurring problem? Answering these and other questions will lead to a good description to most problems, and is the best way to start down the path of problem resolution. What are the symptoms? When starting to describe a problem, the most obvious question is "What is the problem?" This might seem like a straightforward question; however, it can be broken down into several other questions to create a more descriptive picture of the problem. These questions can include: - Who or what is reporting the problem? - What are the error codes and error messages? - How does it fail? For example, loop, hang, stop, performance degradation, or incorrect result? - What is the affect on business? Where is the problem happening? Determining where the problem originates is not always easy, but is one of the most important steps in resolving a problem. Many layers of technology can exist between the reporting and failing components. Networks, disks, and drivers are only a few components to be considered