erros during export/import 
Author Message
 erros during export/import

I ran into the the following problem:

1. We have a large amount of data in some tables in the database.
The tables are related by foreign keys.

2. Now we want to change the database tables to new table definitions
which expands the sizes of some columns; some columns are just chars
and cannot be expanded by alter table command.

I ran the export and import using delimited ascii to transfer the data
from a backup copy to a new database with the new table definitions.

One table has > 248,000 rows but during the import it reported
a series of errors like below:

SQL3137W  Row "4348" is too short.  At least one input value being
loaded to a
non-nullable column is missing.  The row was not loaded.

SQL3116W  The field value in row "4349" and column "1" is missing, but
the
target column is not nullable.

SQL3137W  Row "4350" is too short.  At least one input value being
loaded to a
non-nullable column is missing.  The row was not loaded.

How can I do the import/export without losing data ?
Thanks.



Sun, 24 Aug 2003 02:53:07 GMT
 erros during export/import

you can get these type of problems if you have a character field which
contains a line-feed character. In this case the exported row will be spread
over two lines in the export file. This will cause the import utility to get
quite confused and report the type of errors you are noticing here.

Hope this helps,
Phil Castle.


Quote:
> I ran into the the following problem:

> 1. We have a large amount of data in some tables in the database.
> The tables are related by foreign keys.

> 2. Now we want to change the database tables to new table definitions
> which expands the sizes of some columns; some columns are just chars
> and cannot be expanded by alter table command.

> I ran the export and import using delimited ascii to transfer the data
> from a backup copy to a new database with the new table definitions.

> One table has > 248,000 rows but during the import it reported
> a series of errors like below:

> SQL3137W  Row "4348" is too short.  At least one input value being
> loaded to a
> non-nullable column is missing.  The row was not loaded.

> SQL3116W  The field value in row "4349" and column "1" is missing, but
> the
> target column is not nullable.

> SQL3137W  Row "4350" is too short.  At least one input value being
> loaded to a
> non-nullable column is missing.  The row was not loaded.

> How can I do the import/export without losing data ?
> Thanks.



Sun, 24 Aug 2003 09:14:16 GMT
 erros during export/import
Hi,

Try Chyfo at www.ispirer.com/chyfo.html
It converts data to text and creates DDL for tables and indexes. Edit
generated table definitions as you want. The tool also creates scripts for
load/import command.

Best regards, Dmitry.


Quote:
> I ran into the the following problem:

> 1. We have a large amount of data in some tables in the database.
> The tables are related by foreign keys.

> 2. Now we want to change the database tables to new table definitions
> which expands the sizes of some columns; some columns are just chars
> and cannot be expanded by alter table command.

> I ran the export and import using delimited ascii to transfer the data
> from a backup copy to a new database with the new table definitions.

> One table has > 248,000 rows but during the import it reported
> a series of errors like below:

> SQL3137W  Row "4348" is too short.  At least one input value being
> loaded to a
> non-nullable column is missing.  The row was not loaded.

> SQL3116W  The field value in row "4349" and column "1" is missing, but
> the
> target column is not nullable.

> SQL3137W  Row "4350" is too short.  At least one input value being
> loaded to a
> non-nullable column is missing.  The row was not loaded.

> How can I do the import/export without losing data ?
> Thanks.



Sun, 24 Aug 2003 18:39:25 GMT
 erros during export/import
It could be that your data contains a comma too.
You can export with format of ASC (fixed columns) instead of DEL (comma delimited
format).
Quote:

> you can get these type of problems if you have a character field which
> contains a line-feed character. In this case the exported row will be spread
> over two lines in the export file. This will cause the import utility to get
> quite confused and report the type of errors you are noticing here.

> Hope this helps,
> Phil Castle.



> > I ran into the the following problem:

> > 1. We have a large amount of data in some tables in the database.
> > The tables are related by foreign keys.

> > 2. Now we want to change the database tables to new table definitions
> > which expands the sizes of some columns; some columns are just chars
> > and cannot be expanded by alter table command.

> > I ran the export and import using delimited ascii to transfer the data
> > from a backup copy to a new database with the new table definitions.

> > One table has > 248,000 rows but during the import it reported
> > a series of errors like below:

> > SQL3137W  Row "4348" is too short.  At least one input value being
> > loaded to a
> > non-nullable column is missing.  The row was not loaded.

> > SQL3116W  The field value in row "4349" and column "1" is missing, but
> > the
> > target column is not nullable.

> > SQL3137W  Row "4350" is too short.  At least one input value being
> > loaded to a
> > non-nullable column is missing.  The row was not loaded.

> > How can I do the import/export without losing data ?
> > Thanks.



Sun, 21 Sep 2003 10:21:48 GMT
 
 [ 4 post ] 

 Relevant Pages 

1. Upgrading from SQL 6.5 to 2000 - error during export and import via named pipes step

2. SQL Server Upgrade Wizard Fails During Import/Export

3. Upgrading from SQL 6.5 to 2000 - error during export and import via named pipes step

4. I need to change size of constraints during export/import

5. How to create file during import / export

6. Export problem (during .exporting posttable actions)

7. Importing SAS dataset via DTS Import/Export Wizard

8. Importing text files into SQL Server 2000 Database using DTS Import/Export Wizard

9. including NULLS during export

10. Change name file during a Export data

11. ORA 06553 - PLS 561 during export from 8.1.6

12. ORA-04031 during export


 
Powered by phpBB® Forum Software