Re: Just scratching my head...
A user complains that dbexport/dbimport has repeatedly failed for them across versions (9.4, 10.0, 11.5), arguing IBM has long known about the defect; others counter that cross-version differences explain failures when moving a newer schema to an older server. Asked to narrow it down, he says the error isn't table-specific but occurs while dbimport processes the stored-procedure section of the generated SQL script. Suggestions to isolate the offending procedures in a small script, or test with dbschema -ss, were offered but not followed through (dbspaces differ between instances). No resolution is recorded.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
With full respect, no, it makes no sense.
We have been having difficulties with dbexport/dbimport for years. It fails when going from 10.0 to 10.0. Just like it failed when going from 9.4 to 9.4. And 9.4 to 10.4.
If you search this group, you can find multiple reports of the same error. IBM clearly knows about it because we reported it years ago. The tech handling our case back then even sent me a PREVIOUS, EXISTING documentation on it (may have been an internal report, but had a bug number). Point is IBM knows about it. IBM just chose to ignore it.
So, we are generally quite pleased with Informix. We are customers. I defend Informix when I can.
However, this defect has been a burr under our saddle for too many years, and I cannot excuse IBM for shipping defective product. dbexport/dbimport are just unreliable and prone to failure.
DG
"Ian Michael Gumby" <im_gumby@hotmail.com> wrote in message news:mailman.241.1225465665.874.informix-list@iiug.org...
DG,
Thats correct.
I think that the point I and others are trying to make is that you and your "consultant" are coming to a wrong conclusion.
While the basic DDL hasn't changed, there are changes/improvements/evolutions made in 11.5 that are not in 10.
So when you're going from 11.5 to 10, the odds are that there will be problems unless you just focus on the very basic table definition pieces.
So to say "Informix gets a black eye" because of this... Its a hollow argument.
Does this make sense?
with you. Try Windows Mobile® today
DGPretzel wrote:
> With full respect, no, it makes no sense.
>
> We have been having difficulties with dbexport/dbimport for years. It
> fails when going from 10.0 to 10.0. Just like it failed when going from
> 9.4 to 9.4. And 9.4 to 10.4.
>
> If you search this group, you can find multiple reports of the same
> error. IBM clearly knows about it because we reported it years ago.
> The tech handling our case back then even sent me a PREVIOUS, EXISTING
> documentation on it (may have been an internal report, but had a bug
> number). Point is IBM knows about it. IBM just chose to ignore it.
>
> So, we are generally quite pleased with Informix. We are customers. I
> defend Informix when I can.
>
> However, this defect has been a burr under our saddle for too many
> years, and I cannot excuse IBM for shipping defective product.
> dbexport/dbimport are just unreliable and prone to failure.
>
Just for curiosity, does your problem happen on a specific table?
Regards.
--
Fernando Nunes
Portugal
http://informix-technology.blogspot.com
My email works... but I don't check it frequently...
"Fernando Nunes" <domusonline@gmail.com> wrote in message
news:gegc57$vv1$1@registered.motzarella.org...
>
> Just for curiosity, does your problem happen on a specific table?
> Regards.
No. Actualy, the error usually appears while dbimport is processing the SP
portion of the dbexport-produced sql script.
DG
On 1 Nov, 06:32, "DGPretzel" <d...@gci.net> wrote:
> "Fernando Nunes" <domusonl...@gmail.com> wrote in message
>
> news:gegc57$vv1$1@registered.motzarella.org...
>
>
>
> > Just for curiosity, does your problem happen on a specific table?
> > Regards.
>
> No. Actualy, the error usually appears while dbimport is processing the SP
> portion of the dbexport-produced sql script.
>
> DG
If you take a dbschema -ss and use it to create an empty database does
it also fail to import?
DGPretzel wrote:
> "Fernando Nunes" <domusonline@gmail.com> wrote in message
> news:gegc57$vv1$1@registered.motzarella.org...
>> Just for curiosity, does your problem happen on a specific table?
>> Regards.
>
> No. Actualy, the error usually appears while dbimport is processing the SP
> portion of the dbexport-produced sql script.
>
> DG
>
>
Please see my other post. If possible try to create a small script with the
procedures. In one of your previous cases you nailed it down to two
procedures... Maybe it's still the same procedures... Strange thing is that in
9.4 it worked, accordingly to case notes...
Regards.
--
Fernando Nunes
Portugal
http://informix-technology.blogspot.com
My email works... but I don't check it frequently...
"Fernando Nunes" <domusonline@gmail.com> wrote in message news:gekv8a$j14$2@registered.motzarella.org... > > Please see my other post. Thank you. >If possible try to create a small script with the procedures. In one of >your previous cases you nailed it down to two procedures... Maybe it's >still the same procedures... Different database. >Strange thing is that in 9.4 it worked, accordingly to case notes... > We never really felt that we had a real solution. But, sometimes, you just "cut bait" on some issues. Thank you, once again. On balance, we are quite satisfied with Informix. DG
>If you take a dbschema -ss and use it to create an empty database does
>it also fail to import?
Dbspaces are different between the two instances.