APAR status
Closed as program error.
Error description
When doing a dbimport of a database you may run out of available space in the dbspace designated for the load. This can have several reasons, of course. In this scenario we look at a movement of a database from one dbspace to another one with both having the same page size. The target dbspace does have the same or even more contiguous free space than the database consumes on the dbspace it was exported from. When even with a substantial larger dbspace the dbimport is not going to work because of exhausted space in the target dbspace then you may want to have a look at maximum rows sizes of the tables in the database. When dbexport is used without the option "-ss" the create table statements do not include the "EXTENT SIZE" "NEXT SIZE" clauses. In this case dbimport will try to calculate an appropriate first extent size by using the maximum row size information multiplied with the number of rows for each table. When having tables with large maximum row sizes, for example when including columns of type LVARCHAR, this can end up in large first extent sizes which in turn can lead to the failure during dbimport. If the column has the type LVARCHAR with no size information the default size used for the calculation of this column length will be 2048 bytes. The SQL script created by dbexport does include the row size information in the comment line before the table creation statement. This can be used to calculate a quick estimate. If the source database is still available you may want to try the option "-ss" for dbexport. If it is no longer available you will need to change the create table statements by adding an appropriate "EXTENT SIZE" and "NEXT SIZE" clause, at least for the tables which have a large result for the calculation of row size times number of rows.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * All users * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Update to IDS-11.70.xC9 * ****************************************************************
Problem conclusion
Problem Fixed In IDS-11.70.xC9
Temporary fix
Comments
APAR Information
APAR number
IT00771
Reported component name
INFORMIX SERVER
Reported component ID
5725A3900
Reported release
B70
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-04-02
Closed date
2017-06-09
Last modified date
2017-06-09
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
INFORMIX SERVER
Fixed component ID
5725A3900
Applicable component levels
RB70 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSGU8G","label":"Informix Servers"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B70","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
09 June 2017