Hi All,

I have a major problem on Production box, recently we have changed the
server,
and exported and imported the database to new server from old box.

In one table there are 10 fields of datatype LVARCHAR, in export file
(.unl)
the data is present , but when it is loaded to the table the data is
truncated, not all the rows , it has happened very randomly.

To test this , i have created a separate table, and used
LOAD from ...
INSERT INTO command
again the same problem ,it is loaded with trucated data.

Is anybody has come across with the above problem? Is it bcoz of
Datablades?
In the new box we do not have any datablades? Is LVARCHAR anything to
do with Datablades?

Any help would be highly appreciated. As it is on the production i
need to find out the reason, bcoz we are exporting every night with
DBEXPORT command.

If we use dbimport , and if it truncates the data, Is export is
relaible?
Early reply would be much helpful.
Thanks in Advance
Kalpana Pai

KalpanaPai wrote:
> I have a major problem on Production box, recently we have changed
> the server, and exported and imported the database to new server
> from old box.
>
> In one table there are 10 fields of datatype LVARCHAR, in export
> file (.unl) the data is present , but when it is loaded to the
> table the data is truncated, not all the rows, it has happened
> very randomly.

Not good. Random behaviour in databases is almost always bad.

> To test this , i have created a separate table, and used LOAD from
> ... INSERT INTO command again the same problem, it is loaded with
> trucated data.

Same pattern, or different pattern? That is using DB-Access or
DB-Load or something else?

> Is anybody has come across with the above problem? Is it bcoz of
> Datablades? In the new box we do not have any datablades? Is
> LVARCHAR anything to do with Datablades?

LVARCHAR is used by datablades, but otherwise is not related. The
absence of datablades in the new system should not affect this.

> Any help would be highly appreciated. As it is on the production i
> need to find out the reason, bcoz we are exporting every night with
> DBEXPORT command.

Judging from what you say, the export is reliable enough - it unloads
what is in the database.

> If we use dbimport, and if it truncates the data, is export is
> reliable?

It appears that the DB-Import is unreliable, not the DB-Export.

Since you've not given us any version or platform information, there's
nothing else we can do to help you - other than point you to where you
should have gone in the first place.

--
Jonathan Leffler #include <disclaimer.h>
Email: jleffler@earthlink.net, jleffler@us.ibm.com
Guardian of DBD::Informix v2003.04 -- http://dbi.perl.org/

On Wed, 29 Oct 2003 19:02:58 -0500, KalpanaPai wrote:

Probably due to embedded newlines in the unload file.

Art S. Kagel

> Hi All,
>
> I have a major problem on Production box, recently we have changed the server,
> and exported and imported the database to new server from old box.
>
> In one table there are 10 fields of datatype LVARCHAR, in export file (.unl)
> the data is present , but when it is loaded to the table the data is
> truncated, not all the rows , it has happened very randomly.
>
> To test this , i have created a separate table, and used LOAD from ... INSERT
> INTO command
> again the same problem ,it is loaded with trucated data.
>
> Is anybody has come across with the above problem? Is it bcoz of Datablades?
> In the new box we do not have any datablades? Is LVARCHAR anything to do with
> Datablades?
>
> Any help would be highly appreciated. As it is on the production i need to
> find out the reason, bcoz we are exporting every night with DBEXPORT command.
>
> If we use dbimport , and if it truncates the data, Is export is relaible?
> Early reply would be much helpful.
> Thanks in Advance
> Kalpana Pai