|
Problem IC96261
|
Status: Closed |
PROBLEM WITH HANDLING "R" CARRIAGE RETURN ON WINDOWS DURING PARSING DB2SUPPORT.PROFILE FILE. |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
Once you create db2support.profile file on Windows like
following:
<COLLECTION>
<NAME>...</NAME>
<CMD>...</CMD>
<OUTFILE>...</OUTFILE>
<TIMEOUT>..</TIMEOUT>
</COLLECTION>
you will notice that file in binary format is following:
3c43 4f4c 4c45 4354 494f 4e3e 0d0a 3c4e <COLLECTION>..<N
414d 453e 2e2e 2e3c 2f4e 414d 453e 0d0a AME>...</NAME>..
3c43 4d44 3e2e 2e2e 3c2f 434d 443e 0d0a <CMD>...</CMD>..
3c4f 5554 4649 4c45 3e2e 2e2e 3c2f 4f55 <OUTFILE>...</OU
5446 494c 453e 0d0a 3c54 494d 454f 5554 TFILE>..<TIMEOUT
3e2e 2e3c 2f54 494d 454f 5554 3e0d 0a3c >..</TIMEOUT>..<
2f43 4f4c 4c45 4354 494f 4e3e 0d0a /COLLECTION>..
Once file similar to above will be parsed by db2support command,
you will receive an error:
Collecting user-specified profile collection
2013-04-08-11.4.50.730000 [db2supp_col.C:1179]
RC=2 Error: Parse error while reading profile file.: line 6
Cause for the error is incorrectly parsed carriage return char
"\r" (HEX 0d) in new line sequence (0d0a). Once file contains
Linux/UNIX style new line (0a) problem does not occur. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* WINDOWS *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 10.1 fixpack 3 *
**************************************************************** |
| Local Fix: |
Create db2support.profile with Linux/UNIX style new line
sequence (0a) |
| available fix packs: |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in DB2 version 10.1 fixpack 3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 25.09.2013
02.10.2013
02.10.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
