RE: Moving from UNIX, IDS 9.3 to Windows 11.70.FC2
Larry reported that after migrating from UNIX IDS 9.3 to IDS 11.x on Windows 2003, dbexport consistently failed near the end (during the GRANT/permissions phase) for some databases but not others, always stopping at the same point for a given database, for both the informix user and ordinary Informix-group members; IBM support couldn't reproduce it and offered little help. Art Kagel suggested running dbexport on the UNIX side and copying the files over, or using his myschema -l tool to generate a dbimport-compatible schema, pushing IBM to escalate the case, and upgrading off the early 11.50 release. Guy asked whether the informix user was properly in the Administrators group with required advanced user rights or had been created manually outside the IDS install. No resolution is recorded in the thread.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
We have the environment created on the Windows 2003. Everything seems to be
working properly; however, when we run dbexport against certain databases, it
fails during the end when it is granting permissions. Both databases are
fairly small (under 1 GB).
The dbexports always seem to die in the same place for a given database, but
not EVERY database,
one would expect the .out and .sql file sizes to be the same size each time
for the same database, but......
Example:I have one database, dbexport gl, that dies each time with those file
sizes at 257KB.
Example:I have one database, dbexport hr, that dies each time with those file
sizes at 21KB.
Counter-Example:I have one database, dbexport admin, that does NOT die and the
files sizes are 42KB
Counter-Example:I have one database, dbexport flight_ops, that does NOT die
and the files sizes are 17KB
Of course I am running from the dos prompt and the <service>.cmd invoked.
Tech support runs the dbexport in a dos environment like I have been doing
he does not have a problem completing dbexport successfully. When he logs in
as a regular user who is a member of the Informix group, he sees a similar
problem, but when he logs in as informix, he sees no problem. We tried this,
but it still does not work for either user. (informix nor regular)
Has anyone seen this behavior before? It is driving us crazy.
Larry
I assume you are exporting from the UNIX based database, have you tried
running the dbexport on UNIX and then just copying the files to the Windows
system? You can also use my dbschema replacement tool, myschema, with the
-l option to get a schema file that will be compatible with dbimport of your
database export. Since the dbexport dies after exporting all of the tables
successfully, you should be able to use the file myschema produces for the
import instead of the partial dbexport schema file (you may have to edit the
file to correct the row counts in the comments preceding each table's CREATE
statement if there's been activity since the export was made - the newest
dbimports will abort if the count in the schema files does not match the
actual number of rows in the import data files). Also, you may have trouble
compiling myschema on Windows, no one has tried it seriously in several
years. You may have to run it on a UNIX/Linux system pointed at the
Informix instance.
I won't ask why anyone would want to run their database on Windows when a
Linux system will run the database faster and less expensively.
Art
Art S. Kagel
Advanced DataTools (www.advancedatatools.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 my employer, Advanced DataTools, 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 Tue, Aug 9, 2011 at 11:12 AM, LARRY SORENSEN <lsorensen25@msn.com> wrote:
> We have the environment created on the Windows 2003. Everything seems to be
> working properly; however, when we run dbexport against certain databases,
> it
> fails during the end when it is granting permissions. Both databases are
> fairly small (under 1 GB).
>
> The dbexports always seem to die in the same place for a given database,
> but
> not EVERY database,
> one would expect the .out and .sql file sizes to be the same size each time
> for the same database, but......
>
> Example:I have one database, dbexport gl, that dies each time with those
> file
> sizes at 257KB.
> Example:I have one database, dbexport hr, that dies each time with those
> file
> sizes at 21KB.
> Counter-Example:I have one database, dbexport admin, that does NOT die and
> the
> files sizes are 42KB
> Counter-Example:I have one database, dbexport flight_ops, that does NOT die
> and the files sizes are 17KB
> Of course I am running from the dos prompt and the <service>.cmd invoked.
>
> Tech support runs the dbexport in a dos environment like I have been doing
> he does not have a problem completing dbexport successfully. When he logs
> in
> as a regular user who is a member of the Informix group, he sees a similar
> problem, but when he logs in as informix, he sees no problem. We tried
> this,
> but it still does not work for either user. (informix nor regular)
>
> Has anyone seen this behavior before? It is driving us crazy.
>
> Larry
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--20cf307d075ac98d7504aa1494bd
Thank you for the input. I don't know why Windows was chosen as well.
So, other than using your utilities, you can't think of any
parameter/configuration issues that might cause the results that we are
seeing? IDS Technical support is basically throwing up their collective hands
and telling us to find debugging tools to figure this one out ourselves. I
didn't know they did that. Anyway, although we may use your tools in the
future, I would like to see that we have everything else correct and that the
native tools are at least operational.
Larry
> To: ids@iiug.org
> From: art.kagel@gmail.com
> Subject: Re: Moving from UNIX, IDS 9.3 to Windows 11.70.FC2 [24569]
> Date: Tue, 9 Aug 2011 11:54:43 -0400
>
> I assume you are exporting from the UNIX based database, have you tried
> running the dbexport on UNIX and then just copying the files to the Windows
> system? You can also use my dbschema replacement tool, myschema, with the
> -l option to get a schema file that will be compatible with dbimport of your
> database export. Since the dbexport dies after exporting all of the tables
> successfully, you should be able to use the file myschema produces for the
> import instead of the partial dbexport schema file (you may have to edit the
> file to correct the row counts in the comments preceding each table's CREATE
> statement if there's been activity since the export was made - the newest
> dbimports will abort if the count in the schema files does not match the
> actual number of rows in the import data files). Also, you may have trouble
> compiling myschema on Windows, no one has tried it seriously in several
> years. You may have to run it on a UNIX/Linux system pointed at the
> Informix instance.
>
> I won't ask why anyone would want to run their database on Windows when a
> Linux system will run the database faster and less expensively.
>
> Art
>
> Art S. Kagel
> Advanced DataTools (www.advancedatatools.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 my employer, Advanced DataTools, 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 Tue, Aug 9, 2011 at 11:12 AM, LARRY SORENSEN <lsorensen25@msn.com> wrote:
>
> > We have the environment created on the Windows 2003. Everything seems to be
> > working properly; however, when we run dbexport against certain databases,
> > it
> > fails during the end when it is granting permissions. Both databases are
> > fairly small (under 1 GB).
> >
> > The dbexports always seem to die in the same place for a given database,
> > but
> > not EVERY database,
> > one would expect the .out and .sql file sizes to be the same size each time
> > for the same database, but......
> >
> > Example:I have one database, dbexport gl, that dies each time with those
> > file
> > sizes at 257KB.
> > Example:I have one database, dbexport hr, that dies each time with those
> > file
> > sizes at 21KB.
> > Counter-Example:I have one database, dbexport admin, that does NOT die and
> > the
> > files sizes are 42KB
> > Counter-Example:I have one database, dbexport flight_ops, that does NOT die
> > and the files sizes are 17KB
> > Of course I am running from the dos prompt and the <service>.cmd invoked.
> >
> > Tech support runs the dbexport in a dos environment like I have been doing
> > he does not have a problem completing dbexport successfully. When he logs
> > in
> > as a regular user who is a member of the Informix group, he sees a similar
> > problem, but when he logs in as informix, he sees no problem. We tried
> > this,
> > but it still does not work for either user. (informix nor regular)
> >
> > Has anyone seen this behavior before? It is driving us crazy.
> >
> > Larry
> >
> >
> >
> >
>
*******************************************************************************
> > Forum Note: Use "Reply" to post a response in the discussion forum.
> >
> >
>
> --20cf307d075ac98d7504aa1494bd
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
I couldn't agree more. The 'official' tools should be working. You have to
manage your cases with IBM. I would have the case escalated so that they
assign someone senior and agree to log into your system, install a debugging
version of dbexport, and figure out what's wrong themselves. It shouldn't
be up to you to fix IBM's software.
What version of Informix is this?
Art
Art S. Kagel
Advanced DataTools (www.advancedatatools.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 my employer, Advanced DataTools, 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 Tue, Aug 9, 2011 at 1:00 PM, LARRY SORENSEN <lsorensen25@msn.com> wrote:
> Thank you for the input. I don't know why Windows was chosen as well.
>
> So, other than using your utilities, you can't think of any
> parameter/configuration issues that might cause the results that we are
> seeing? IDS Technical support is basically throwing up their collective
> hands
> and telling us to find debugging tools to figure this one out ourselves. I
> didn't know they did that. Anyway, although we may use your tools in the
> future, I would like to see that we have everything else correct and that
> the
> native tools are at least operational.
>
> Larry
>
> > To: ids@iiug.org
> > From: art.kagel@gmail.com
> > Subject: Re: Moving from UNIX, IDS 9.3 to Windows 11.70.FC2 [24569]
> > Date: Tue, 9 Aug 2011 11:54:43 -0400
> >
> > I assume you are exporting from the UNIX based database, have you tried
> > running the dbexport on UNIX and then just copying the files to the
> Windows
> > system? You can also use my dbschema replacement tool, myschema, with the
> > -l option to get a schema file that will be compatible with dbimport of
> your
> > database export. Since the dbexport dies after exporting all of the
> tables
> > successfully, you should be able to use the file myschema produces for
> the
> > import instead of the partial dbexport schema file (you may have to edit
> the
> > file to correct the row counts in the comments preceding each table's
> CREATE
> > statement if there's been activity since the export was made - the newest
> > dbimports will abort if the count in the schema files does not match the
> > actual number of rows in the import data files). Also, you may have
> trouble
> > compiling myschema on Windows, no one has tried it seriously in several
> > years. You may have to run it on a UNIX/Linux system pointed at the
> > Informix instance.
> >
> > I won't ask why anyone would want to run their database on Windows when a
> > Linux system will run the database faster and less expensively.
> >
> > Art
> >
> > Art S. Kagel
> > Advanced DataTools (www.advancedatatools.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 my employer, Advanced DataTools, 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 Tue, Aug 9, 2011 at 11:12 AM, LARRY SORENSEN <lsorensen25@msn.com>
> wrote:
> >
> > > We have the environment created on the Windows 2003. Everything seems
> to
> be
> > > working properly; however, when we run dbexport against certain
> databases,
> > > it
> > > fails during the end when it is granting permissions. Both databases
> are
> > > fairly small (under 1 GB).
> > >
> > > The dbexports always seem to die in the same place for a given
> database,
> > > but
> > > not EVERY database,
> > > one would expect the .out and .sql file sizes to be the same size each
> time
> > > for the same database, but......
> > >
> > > Example:I have one database, dbexport gl, that dies each time with
> those
> > > file
> > > sizes at 257KB.
> > > Example:I have one database, dbexport hr, that dies each time with
> those
> > > file
> > > sizes at 21KB.
> > > Counter-Example:I have one database, dbexport admin, that does NOT die
> and
> > > the
> > > files sizes are 42KB
> > > Counter-Example:I have one database, dbexport flight_ops, that does NOT
> die
> > > and the files sizes are 17KB
> > > Of course I am running from the dos prompt and the <service>.cmd
> invoked.
> > >
> > > Tech support runs the dbexport in a dos environment like I have been
> doing
> > > he does not have a problem completing dbexport successfully. When he
> logs
> > > in
> > > as a regular user who is a member of the Informix group, he sees a
> similar
> > > problem, but when he logs in as informix, he sees no problem. We tried
> > > this,
> > > but it still does not work for either user. (informix nor regular)
> > >
> > > Has anyone seen this behavior before? It is driving us crazy.
> > >
> > > Larry
> > >
> > >
> > >
> > >
> >
>
>
*******************************************************************************
> > > Forum Note: Use "Reply" to post a response in the discussion forum.
> > >
> > >
> >
> > --20cf307d075ac98d7504aa1494bd
> >
> >
> >
>
>
*******************************************************************************
> > Forum Note: Use "Reply" to post a response in the discussion forum.
> >
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--bcaec501628116817e04aa15b9eb
Never mind, forgot to look back at the Subject line. 11.50.FC2. You might
consider going up to 11.70FC3 or 11.50.FC9. 11.50.FC2 is a very early 11.50
release and was rather buggy. Dynamic SQL for example was very flaky until
11.50.xC4 also you are missing several features implemented in .xC4, .xC5,
.xC6 and in 11.70.xC1 and .xC3. Finally, 11.70 is about 10-15% faster than
11.50 for many queries.
Art
Art S. Kagel
Advanced DataTools (www.advancedatatools.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 my employer, Advanced DataTools, 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 Tue, Aug 9, 2011 at 1:16 PM, Art Kagel <art.kagel@gmail.com> wrote:
> I couldn't agree more. The 'official' tools should be working. You have
> to manage your cases with IBM. I would have the case escalated so that they
> assign someone senior and agree to log into your system, install a debugging
> version of dbexport, and figure out what's wrong themselves. It shouldn't
> be up to you to fix IBM's software.
>
> What version of Informix is this?
>
> Art
>
> Art S. Kagel
> Advanced DataTools (www.advancedatatools.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 my employer, Advanced DataTools, 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 Tue, Aug 9, 2011 at 1:00 PM, LARRY SORENSEN <lsorensen25@msn.com>wrote:
>
>> Thank you for the input. I don't know why Windows was chosen as well.
>>
>> So, other than using your utilities, you can't think of any
>> parameter/configuration issues that might cause the results that we are
>> seeing? IDS Technical support is basically throwing up their collective
>> hands
>> and telling us to find debugging tools to figure this one out ourselves. I
>> didn't know they did that. Anyway, although we may use your tools in the
>> future, I would like to see that we have everything else correct and that
>> the
>> native tools are at least operational.
>>
>> Larry
>>
>> > To: ids@iiug.org
>> > From: art.kagel@gmail.com
>> > Subject: Re: Moving from UNIX, IDS 9.3 to Windows 11.70.FC2 [24569]
>> > Date: Tue, 9 Aug 2011 11:54:43 -0400
>> >
>> > I assume you are exporting from the UNIX based database, have you tried
>> > running the dbexport on UNIX and then just copying the files to the
>> Windows
>> > system? You can also use my dbschema replacement tool, myschema, with
>> the
>> > -l option to get a schema file that will be compatible with dbimport of
>> your
>> > database export. Since the dbexport dies after exporting all of the
>> tables
>> > successfully, you should be able to use the file myschema produces for
>> the
>> > import instead of the partial dbexport schema file (you may have to edit
>> the
>> > file to correct the row counts in the comments preceding each table's
>> CREATE
>> > statement if there's been activity since the export was made - the
>> newest
>> > dbimports will abort if the count in the schema files does not match the
>> > actual number of rows in the import data files). Also, you may have
>> trouble
>> > compiling myschema on Windows, no one has tried it seriously in several
>> > years. You may have to run it on a UNIX/Linux system pointed at the
>> > Informix instance.
>> >
>> > I won't ask why anyone would want to run their database on Windows when
>> a
>> > Linux system will run the database faster and less expensively.
>> >
>> > Art
>> >
>> > Art S. Kagel
>> > Advanced DataTools (www.advancedatatools.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 my employer, Advanced DataTools, 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 Tue, Aug 9, 2011 at 11:12 AM, LARRY SORENSEN <lsorensen25@msn.com>
>> wrote:
>> >
>> > > We have the environment created on the Windows 2003. Everything seems
>> to
>> be
>> > > working properly; however, when we run dbexport against certain
>> databases,
>> > > it
>> > > fails during the end when it is granting permissions. Both databases
>> are
>> > > fairly small (under 1 GB).
>> > >
>> > > The dbexports always seem to die in the same place for a given
>> database,
>> > > but
>> > > not EVERY database,
>> > > one would expect the .out and .sql file sizes to be the same size each
>> time
>> > > for the same database, but......
>> > >
>> > > Example:I have one database, dbexport gl, that dies each time with
>> those
>> > > file
>> > > sizes at 257KB.
>> > > Example:I have one database, dbexport hr, that dies each time with
>> those
>> > > file
>> > > sizes at 21KB.
>> > > Counter-Example:I have one database, dbexport admin, that does NOT die
>> and
>> > > the
>> > > files sizes are 42KB
>> > > Counter-Example:I have one database, dbexport flight_ops, that does
>> NOT
>> die
>> > > and the files sizes are 17KB
>> > > Of course I am running from the dos prompt and the <service>.cmd
>> invoked.
>> > >
>> > > Tech support runs the dbexport in a dos environment like I have been
>> doing
>> > > he does not have a problem completing dbexport successfully. When he
>> logs
>> > > in
>> > > as a regular user who is a member of the Informix group, he sees a
>> similar
>> > > problem, but when he logs in as informix, he sees no problem. We tried
>> > > this,
>> > > but it still does not work for either user. (informix nor regular)
>> > >
>> > > Has anyone seen this behavior before? It is driving us crazy.
>> > >
>> > > Larry
>> > >
>> > >
>> > >
>> > >
>> >
>>
>>
*******************************************************************************
>> > > Forum Note: Use "Reply" to post a response in the discussion forum.
>> > >
>> > >
>> >
>> > --20cf307d075ac98d7504aa1494bd
>> >
>> >
>> >
>>
>>
*******************************************************************************
>> > Forum Note: Use "Reply" to post a response in the discussion forum.
>> >
>>
>>
>>
>>
*******************************************************************************
>> Forum Note: Use "Reply" to post a response in the discussion forum.
>>
>>
>
Is informix a member of the Administrators group with all the Advanced User
rights it needs, or was the informix user created manually and not part of the
IDS install process?
________________________________
From: LARRY SORENSEN <lsorensen25@msn.com>
To: ids@iiug.org
Sent: Tuesday, August 9, 2011 8:12 AM
Subject: RE: Moving from UNIX, IDS 9.3 to Windows 11.70.FC2 [24568]
We have the environment created on the Windows 2003. Everything seems to be
working properly; however, when we run dbexport against certain databases, it
fails during the end when it is granting permissions. Both databases are
fairly small (under 1 GB).
The dbexports always seem to die in the same place for a given database, but
not EVERY database,
one would expect the .out and .sql file sizes to be the same size each time
for the same database, but......
Example:I have one database, dbexport gl, that dies each time with those file
sizes at 257KB.
Example:I have one database, dbexport hr, that dies each time with those file
sizes at 21KB.
Counter-Example:I have one database, dbexport admin, that does NOT die and the
files sizes are 42KB
Counter-Example:I have one database, dbexport flight_ops, that does NOT die
and the files sizes are 17KB
Of course I am running from the dos prompt and the <service>.cmd invoked.
Tech support runs the dbexport in a dos environment like I have been doing
he does not have a problem completing dbexport successfully. When he logs in
as a regular user who is a member of the Informix group, he sees a similar
problem, but when he logs in as informix, he sees no problem. We tried this,
but it still does not work for either user. (informix nor regular)
Has anyone seen this behavior before? It is driving us crazy.
Larry
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.