Who's On?

	Membership:
	Latest: cat andrews
	Past 24 Hours: 0
	Prev. 24 Hours: 0
	Overall: 5215

	People Online:
	Visitors: 0
	Members: 0
	Total: 0

Name	Points
Greg Moeller	4184
David Williams	3349
Kat V	2984
Woozy	1973
Jimmy Chiu	1883
Kwane McNeal	1437
Ragu Raghavan	1377
Roger French	1315
mark.cook	1244
Chesca	1042

IMPEXP ERROR

6 Replies

0 Subscribed to this topic

28 Subscribed to this forum

Sort:

Author

Messages

Chris12

Veteran Member

Posts: 150

New Poster

6/20/2011 7:26 PM

We are loading data from our prod product line to our test product line using expsysdb / impexp commands. When we run the impexp command it loads 900 rows in the GLCONTROL table and dies with the following error

impexp: error at line 1145: A row in the input file is truncated.

This occured from 2 different data pulls.

GSC said that have never seen this.
Any help is greatly appreciated.

Ragu Raghavan

Veteran Member

Posts: 477

New Poster

Engaged Poster

Avid Poster

Engaged Reader

Avid Reader

6/20/2011 7:52 PM

Special characters in one of the fields, perhaps ?
I would dump the GLCONTROL table using rngdbdump and view row# 901 using textpad or some other tool that will show the hex values.

John Henley

Posts: 3364

New Poster

Engaged Reader

Avid Reader

6/20/2011 9:09 PM

Are the PROD and TEST product lines on different servers?
If so, and you're on Unix, did you use FTP to move it?
How big is the export file?

Chris12

Veteran Member

Posts: 150

New Poster

6/21/2011 11:35 AM

Thanks rngdbdump caused the issue

Ragu Raghavan

Veteran Member

Posts: 477

New Poster

Engaged Poster

Avid Poster

Engaged Reader

Avid Reader

6/21/2011 12:20 PM

Could you please eloborate? How did rngdbdump cause the issue ? How did you resolve it ?

Kwane McNeal

Veteran Member

Posts: 479

6/21/2011 7:57 PM

Ragu,
I'm thinking (only a guess, of course...) that Chris was using rngdbdump CSV export to load into impexp, instead of expsysdb.

Kwane

Chris12

Veteran Member

Posts: 150

New Poster

6/24/2011 12:17 PM

It was a data integrity issue which cause out load process (expsysdb / impexp) not to run. When we ran rngdbdump in production (source product line) we were able to see where exactly the data integrity issue was correct it in production (the rngdbdump actuall stopped running when it hit the record in question), run a new expsysdb and run the inmport again. THANKS EVERYONE FOR ALL THEIR HELP