Prev
Next
Forums S3 Systems Administration

IMPEXP ERROR

Sort:
You are not authorized to post a reply.
Author
Messages
Chris12
Veteran Member
Posts: 150
Veteran Member
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: 469
    Veteran Member
    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
      Senior Member
      Posts: 3348
      Senior Member
      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?
        Thanks for using the LawsonGuru.com forums!
        John
        Chris12
        Veteran Member
        Posts: 150
        Veteran Member
        6/21/2011 11:35 AM
          Thanks rngdbdump caused the issue
          Ragu Raghavan
          Veteran Member
          Posts: 469
          Veteran Member
          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
            Veteran Member
            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
              Veteran Member
              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
                You are not authorized to post a reply.