Informix - Problem description
Problem IT29670 | Status: Closed |
WINDOWS:ONTAPE BACKUP TO DIRECTORY WILL FAIL IF BACKUP FILE IS BIGGER THAN 2GB | |
product: | |
INFORMIX SERVER / 5725A3900 / E10 - | |
Problem description: | |
When doing an ontape backup to a directory, the backup file will have a temporary name which will be changed to *.LO after the successful completetion of that backup. The last backup before that will be renamend with a time stamp. This process does not work if the backup file gets bigger than 2GB, the backup will fail with this error message: >ontape -s -L 0 10 percent done. 20 percent done. 30 percent done. 40 percent done. 50 percent done. 60 percent done. 70 percent done. 100 percent done. Backup to directory error: Cannot rename file from y:/ONTA_COMP-1636-1_0_Fri_Jun_28_01_12_39_2019_a03036 to y:/COMP-1636-1_0_L0, errno = 17 Archive failed - here is an example. The backup progress worked until the file size increased to > 2GB 28.06.2019 00:36 1.021.820.928 COMP-1636-1_0_20190628_003603_L0 28.06.2019 00:40 1.989.017.600 COMP-1636-1_0_20190628_003957_L0 28.06.2019 00:46 2.151.874.560 COMP-1636-1_0_L0 28.06.2019 00:47 2.152.005.632 ONTA_COMP-1636-1_0_Fri_Jun_28_00_46_44_2019_a06252 28.06.2019 01:13 2.176.090.112 ONTA_COMP-1636-1_0_Fri_Jun_28_01_12_39_2019_a03036 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users of IDS 14.10.xC2. * **************************************************************** * PROBLEM DESCRIPTION: * * ONTAPE BACKUP TO DIRECTORY WILL FAIL IF BACKUP FILE IS * * BIGGER THAN 2GB * **************************************************************** * RECOMMENDATION: * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 10.07.2019 19.09.2019 19.09.2019 |
Problem solved at the following versions (IBM BugInfos) | |
14.10.xC2 | |
Problem solved according to the fixlist(s) of the following version(s) |