Database migration with dbexport/dbimport
Solaris 10 SPARC
IDS 11.50.FC5
I am trying to migrate a database. I am using dbexport and dbimport. The
dbexport seems to have worked just fine. The dbimport, however, gets stuck on
a large table.
{ TABLE "Informix.table_name" row size - 1941 number of columns = 86 index =
138}
{unload file name = eclai01786.unl number of rows = 93759159}
create table "Informix.table_name
(
.......
) lock mode row;
*** prepare sqlobj
19836 - Extent size is too large. Maximum size of an extent is 33554430k.
At first I thought it was because of a following alter table statement.
Alter table table_name extent size some_number next size some_number.
So I began changing those extent size number, and finally got rid of the
entire alter table statement in the .sql file of the dbexport.
I still get the same error. Has anyone run across this before?
Larry
Hi Larry,
Looks like APAR IC65930
Was addressed in 11.50.xC7
--
Gerry Cousins
HCL Technologies
Phone: 1-913-599-8673<tel:19135998673>
E-mail: gcousins@hcl.com<mailto:gcousins@hcl.com>
From: <ids-bounces@iiug.org> on behalf of LARRY SORENSEN <LSORENSEN25@msn.com>
Reply-To: "ids@iiug.org" <ids@iiug.org>
Date: Thursday, June 29, 2017 at 9:02 AM
To: "ids@iiug.org" <ids@iiug.org>
Subject: Database migration with dbexport/dbimport [39477]
Extent size is too large
::DISCLAIMER::
--------------------------------------------------------------------------------
--------------------------------------------------------------------
The contents of this e-mail and any attachment(s) are confidential and
intended for the named recipient(s) only.
E-mail transmission is not guaranteed to be secure or error-free as
information could be intercepted, corrupted,
lost, destroyed, arrive late or incomplete, or may contain viruses in
transmission. The e mail and its contents
(with or without referred errors) shall therefore not attach any liability on
the originator or HCL or its affiliates.
Views or opinions, if any, presented in this email are solely those of the
author and may not necessarily reflect the
views or opinions of HCL or its affiliates. Any form of reproduction,
dissemination, copying, disclosure, modification,
distribution and / or publication of this message without the prior written
consent of authorized representative of
HCL is strictly prohibited. If you have received this email in error please
delete it and notify the sender immediately.
Before opening any email and/or attachments, please check them for viruses and
other defects.
--------------------------------------------------------------------------------
--------------------------------------------------------------------
Larry:
That can happen if the initial extent size is very small (like the default
of 8 pages). Extent doubling kicks in and there are so many small extents
that eventually the doubled size gets too big. You can try editing the
CREATE TABLE statement to set a reasonable initial extent and next size forthe table that should avoid the problem.
Art
Art S. Kagel, President and Principal Consultant
ASK Database Management
www.askdbmgt.com
Blog: http://informix-myview.blogspot.com/
Disclaimer: Please keep in mind that my own opinions are my own opinions
and do not reflect on the IIUG, nor any other organization with which I am
associated either explicitly, implicitly, or by inference. Neither do
those opinions reflect those of other individuals affiliated with any
entity with which I am affiliated nor those of the entities themselves.
On Thu, Jun 29, 2017 at 10:02 AM, LARRY SORENSEN <LSORENSEN25@msn.com>
wrote:
> Solaris 10 SPARC
>
> IDS 11.50.FC5
>
> I am trying to migrate a database. I am using dbexport and dbimport. The
> dbexport seems to have worked just fine. The dbimport, however, gets stuck
> on
> a large table.
>
> { TABLE "Informix.table_name" row size - 1941 number of columns = 86 index
> =
> 138}
>
> {unload file name = eclai01786.unl number of rows = 93759159}
>
> create table "Informix.table_name
>
> (
>
> ........
>
> ) lock mode row;
>
> *** prepare sqlobj
>
> 19836 - Extent size is too large. Maximum size of an extent is 33554430k.
>
> At first I thought it was because of a following alter table statement.
>
> Alter table table_name extent size some_number next size some_number.>
> So I began changing those extent size number, and finally got rid of the
> entire alter table statement in the .sql file of the dbexport.
>
> I still get the same error. Has anyone run across this before?
>
> Larry
>
>
> ************************************************************
> *******************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
Ok. There was no initial extent being set. There was only the alter statement
after the database creation. I will try setting the initial extent right in
the table create statement and go from there.
Thank you.
Larry
________________________________
From: ids-bounces@iiug.org <ids-bounces@iiug.org> on behalf of Art Kagel
<art.kagel@gmail.com>
Sent: Thursday, June 29, 2017 8:33 AM
To: ids@iiug.org
Subject: Re: Database migration with dbexport/dbimport [39479]
Larry:
That can happen if the initial extent size is very small (like the default
of 8 pages). Extent doubling kicks in and there are so many small extents
that eventually the doubled size gets too big. You can try editing the
CREATE TABLE statement to set a reasonable initial extent and next size forthe table that should avoid the problem.
Art
Art S. Kagel, President and Principal Consultant
ASK Database Management
www.askdbmgt.com<http://www.askdbmgt.com>;
ASK Database Management - Home<http://www.askdbmgt.com/>;
www.askdbmgt.com
Database Consulting and Support ... This is the site for Art S. Kagel's
consultancy. The soaring majesty and beauty in the image above hides the
complex ecology and ...
Blog: http://informix-myview.blogspot.com/
Informix - My view<http://informix-myview.blogspot.com/>;
informix-myview.blogspot.com
A place to share my views and ideas which may be of interest to the Informix
user Community.
Disclaimer: Please keep in mind that my own opinions are my own opinions
and do not reflect on the IIUG, nor any other organization with which I am
associated either explicitly, implicitly, or by inference. Neither do
those opinions reflect those of other individuals affiliated with any
entity with which I am affiliated nor those of the entities themselves.
On Thu, Jun 29, 2017 at 10:02 AM, LARRY SORENSEN <LSORENSEN25@msn.com>
wrote:
> Solaris 10 SPARC
>
> IDS 11.50.FC5
>
> I am trying to migrate a database. I am using dbexport and dbimport. The
> dbexport seems to have worked just fine. The dbimport, however, gets stuck
> on
> a large table.
>
> { TABLE "Informix.table_name" row size - 1941 number of columns = 86 index
> =
> 138}
>
> {unload file name = eclai01786.unl number of rows = 93759159}
>
> create table "Informix.table_name
>
> (
>
> ........
>
> ) lock mode row;
>
> *** prepare sqlobj
>
> 19836 - Extent size is too large. Maximum size of an extent is 33554430k.
>
> At first I thought it was because of a following alter table statement.
>
> Alter table table_name extent size some_number next size some_number.>
> So I began changing those extent size number, and finally got rid of the
> entire alter table statement in the .sql file of the dbexport.
>
> I still get the same error. Has anyone run across this before?
>
> Larry
>
>
> ************************************************************
> *******************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.