|
Problem IC74893
|
Status: Closed |
SQL1143N ERROR MAY BE ENCOUNTERED IF A PREVIOUS FIRST OCCURRENCE DATA CAPTURE (FODC) OPERATION DOES NOT COMPLETE PROPERLY. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Problem Description:
When an outage or a specific event occurs first occurrence data
capture (FODC) is enabled automatically and data is collected
based on symptoms. Once the data collection is complete the FODC
state should be disabled.
In this case the FODC state was not disabled following the FODC
data collection. As a result future DB2 logging will look for
the old FODC directory created during the initial FODC
collection. Removing or archiving the FODC directory could lead
to failures for DB2 tasks executing.
Diagnostics:
Here is an example of a failure using the DB2 inspect command:
$ db2 inspect check table tbspaceid 2966 objectid 2 results keep
outfile
SQL1143N The operation cannot complete because a file error
occurred for the file "outfile".
In this case the inspect command failed to create the output
file "outfile" in the FODC directory
/db2inst1/dump/FODC_BadPage_2011-01-23-00.22.22.816367/ because
the directory had been deleted. The
FODC_BadPage_2011-01-23-00.22.22.816367 directory was created
during a previous logging event. Because the FODC state was not
disabled DB2 continued to look for the old FODC directory to
complete logging of the DB2 inspect command. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* Problem Description: *
* When an outage or a specific event occurs first occurrence *
* data capture (FODC) is enabled automatically and data is *
* collected based on symptoms. Once the data collection is *
* complete the FODC state should be disabled. *
* In this case the FODC state was not disabled following the *
* FODC data collection. As a result future DB2 logging will *
* look for the old FODC directory created during the initial *
* FODC collection. Removing or archiving the FODC directory *
* could lead to failures for DB2 tasks executing. *
* *
* Diagnostics: *
* Here is an example of a failure using the DB2 inspect *
* command: *
* $ db2 inspect check table tbspaceid 2966 objectid 2 results *
* keep outfile *
* SQL1143N The operation cannot complete because a file error *
* occurred for the file "outfile". *
* *
* In this case the inspect command failed to create the output *
* file "outfile" in the FODC directory *
* /db2inst1/dump/FODC_BadPage_2011-01-23-00.22.22.816367/ *
* because the directory had been deleted. The *
* FODC_BadPage_2011-01-23-00.22.22.816367 directory was *
* created during a previous logging event. Because the FODC *
* state was not disabled DB2 continued to look for the old *
* FODC directory to complete logging of the DB2 inspect *
* command. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to V9.7 FP5. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Fixed in V9.7 FP5. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC76820
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 07.03.2011
09.12.2011
09.12.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.5
|
 |
