home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
14.10.xC11 FixList
12.10.xC16.X5 FixList
11.70.xC9.XB FixList
11.50.xC9.X2 FixList
11.10.xC3.W5 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

Informix - Problem description

Problem IT08009 Status: Closed

ONTAPE BACKUP TO REMOTE DEVICE FAILS WITH 'COMBINATION OF REMOTE
TAPEDEV AND TAPESIZE 0 IS NOT ALLOWED' ALTHOUGH TAPESIZE IS NOT

product:
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10
Problem description:
Starting with 12.10.xC5, even with TAPESIZE / LTAPESIZE not set 
to 0, 
you get the following error message when trying to backup 
remotely: 
 
Combination of remote TAPEDEV and TAPESIZE 0 is not allowed. 
or 
Combination of remote LTAPEDEV and LTAPESIZE 0 is not allowed. 
 
This applies to both storage space and logical log backups, 
if you specified a remote location for your onconfig parameter 
TAPEDEV / LTAPEDEV.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Al users.                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to IBM Informix Server 12.10.xC6                      * 
****************************************************************
Local Fix:
A possible workaround for storage space backups is to specify 
the -t option with the ontape command, 
while setting TAPEDEV to a non remote location in the ONCONFIG.
Solution
Problem Fixed In IBM Informix Server 12.10.xC6
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
30.03.2015
30.12.2015
30.12.2015
Problem solved at the following versions (IBM BugInfos)
12.10.xC6
Problem solved according to the fixlist(s) of the following version(s)
12.10.xC5.W1 FixList
12.10.xC6 FixList