Results 1 to 10 of 10
  1. #1
    Join Date
    Aug 2002
    Location
    Chennai, India
    Posts
    184

    Unanswered: DEL import fails across platforms

    Platform 1: Sun Sparc Solaris 2.8
    Platform 2: Windows
    DB2 UDB v7.2

    Command used for EXPORT in Solaris:
    Code:
    db2 "export to statep.del of del lobs to /export/home/db2inst1/plus/lobs/ lobfile lobs1 modified by lobsinfile 
    select * from esp.statep fetch first 10 rows only with ur"
    Command used for IMPORT in Solaris:
    Code:
    $ db2 "import from statep.del of del lobs from /export/home/db2inst1/plus/lobs/ modified by lobsinfile insert into esp.statep"
    
    SQL3109N  The utility is beginning to load data from file "state.del".
    SQL3110N  The utility has completed processing.  "10" rows were read from the input file.
    SQL3221W  ...Begin COMMIT WORK. Input Record Count = "10".
    SQL3222W  ...COMMIT of any database changes was successful.
    SQL3149N  "10" rows were processed from the input file.  "10" rows were successfully inserted into the table.  "0" rows were rejected.
    
    Number of rows read         = 10
    Number of rows skipped      = 0
    Number of rows inserted     = 10
    Number of rows updated      = 0
    Number of rows rejected     = 0
    Number of rows committed    = 10
    $
    Command used for IMPORT into Windows after binary transfer of DEL file & lobfile.
    Code:
    db2 "import from statep.del of del lobs from D:\export\home\db2inst1\lobs\ modified by lobsinfile replace into esp.statep"
    
    SQL3109N  The utility is beginning to load data from file "statep.del".
    SQL3512W  The file named in row "1" and column "37" cannot be found, but the target column is not nullable. The row was not loaded.
    SQL3512W  The file named in row "2" and column "37" cannot be found, but the target column is not nullable. The row was not loaded.
    SQL3512W  The file named in row "3" and column "37" cannot be found, but the target column is not nullable. The row was not loaded.
    SQL3512W  The file named in row "4" and column "37" cannot be found, but the target column is not nullable. The row was not loaded.
    SQL3512W  The file named in row "5" and column "37" cannot be found, but the target column is not nullable. The row was not loaded.
    SQL3512W  The file named in row "6" and column "37" cannot be found, but the target column is not nullable. The row was not loaded.
    SQL3512W  The file named in row "7" and column "37" cannot be found, but  the target column is not nullable. The row was not loaded.
    SQL3512W  The file named in row "8" and column "37" cannot be found, but the target column is not nullable. The row was not loaded.
    SQL3512W  The file named in row "9" and column "37" cannot be found, but the target column is not nullable. The row was not loaded.
    SQL3512W  The file named in row "10" and column "37" cannot be found, but the target column is not nullable. The row was not loaded.
    SQL3110N  The utility has completed processing.  "10" rows were read from the input file.
    
    SQL3221W  ...Begin COMMIT WORK. Input Record Count = "10".
    SQL3222W  ...COMMIT of any database changes was successful.
    SQL3149N  "10" rows were processed from the input file.  "0" rows were successfully inserted into the table.  "10" rows were rejected.
     
    
    Number of rows read         = 10
    Number of rows skipped      = 0
    Number of rows inserted     = 0
    Number of rows updated      = 0
    Number of rows rejected     = 10
    Number of rows committed    = 10
    
    D:\export\home\db2inst1\lobs>
    Any idea why it fails for BLOB only? The import across platforms works for tables that do not contain BLOBs.

    TIA.

  2. #2
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    Check that the LOB locator strings match their actual paths. Check that the file permissions allow IMPORT to access them.

  3. #3
    Join Date
    Aug 2002
    Location
    Chennai, India
    Posts
    184
    Quote Originally Posted by n_i
    Check that the LOB locator strings match their actual paths. Check that the file permissions allow IMPORT to access them.
    Checked that LOB locator strings match their actual paths.
    So also, file permissions are OK.

    Any idea? Is this a bug / PMR ?

    TIA.

  4. #4
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    Quote Originally Posted by ggnanaraj
    ...after binary transfer of DEL file
    I'm not sure it was a good idea... Try transferring the text file in a text mode.

  5. #5
    Join Date
    Jun 2003
    Location
    Chennai
    Posts
    26

    Use ixf format from one os to another.

    Hi,

    I have always used ixf format to move data from unix servers to windows. It worked fine.

    MS
    MS

  6. #6
    Join Date
    Aug 2002
    Location
    Chennai, India
    Posts
    184
    Quote Originally Posted by msundaram
    Hi,

    I have always used ixf format to move data from unix servers to windows. It worked fine.

    MS

    I have also done the same. It did work fine. However, when BLOB is being moved, I'm facing a problem. I suspect the issue to be with XP & Windows 2003 Advanced Server; as the data was being moved from Sparc Solaris to Windows XP and Windows 2003 Advanced Server.

  7. #7
    Join Date
    May 2003
    Location
    USA
    Posts
    5,737
    If you use db2move, the blob data will be exported into a separate file and then use db2move to load it back. It should work fine.
    M. A. Feldman
    IBM Certified DBA on DB2 for Linux, UNIX, and Windows
    IBM Certified DBA on DB2 for z/OS and OS/390

  8. #8
    Join Date
    Aug 2002
    Location
    Chennai, India
    Posts
    184
    Quote Originally Posted by Marcus_A
    If you use db2move, the blob data will be exported into a separate file and then use db2move to load it back. It should work fine.
    Nope! Even db2move (DB2 UDB v7.2) fails when moving data from Sparc Solaris to Windows XP or Windows 2003.

    After 'Binding' it fails with the following information in the event viewer...

    Faulting application db2move.exe, version 7.1.0.60, faulting module db2sys.dll, version 0.0.0.0, fault address 0x00056e15.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    TIA.

  9. #9
    Join Date
    May 2003
    Location
    USA
    Posts
    5,737
    It appears that you are using DB2 V7.2 FP6. Version 7 is no longer supported, but you can upgrade to FP14.
    M. A. Feldman
    IBM Certified DBA on DB2 for Linux, UNIX, and Windows
    IBM Certified DBA on DB2 for z/OS and OS/390

  10. #10
    Join Date
    Aug 2002
    Location
    Chennai, India
    Posts
    184
    Thanks for the input.

    db2move works now but on Windows 2000, it failed initially on Windows XP & Windows 2003.

    All data exported from sun sparc solaris loads successfully into windows 2000, but for LOB data. Get errors and no data is loaded.

    I tried doing a DEL export and import, even that fails, as shown below:

    Error when using db2move for LOB data
    SQL3104N The Export utility is beginning to export data to file "tab90.ixf".
    SQL3105N The Export utility has finished exporting "2530" rows.
    SQL3150N The H record in the PC/IXF file has product "DB2 02.00", date
    "20060320", and time "154724".
    SQL3050W Conversions on the data will be made between the IXF file code page
    "819" and the application code page "1252".
    SQL3153N The T record in the PC/IXF file has name "tab90.ixf", qualifier "",
    and source " ".
    SQL3109N The utility is beginning to load data from file "tab90.ixf".
    SQL3148W A row from the input file was not inserted into the table. SQLCODE
    "-423" was returned.
    SQL0423N Locator variable "18" does not currently represent any value.
    SQLSTATE=0F001
    SQL3185W The previous error occurred while processing data from row "1" of
    the input file.
    ....
    ....
    ....
    SQL3148W A row from the input file was not inserted into the table. SQLCODE
    "-423" was returned.
    SQL0423N Locator variable "18" does not currently represent any value.
    SQLSTATE=0F001
    SQL3185W The previous error occurred while processing data from row "2530" of
    the input file.
    SQL3110N The utility has completed processing. "2530" rows were read from
    the input file.
    SQL3221W ...Begin COMMIT WORK. Input Record Count = "2530".
    SQL3222W ...COMMIT of any database changes was successful.
    SQL3149N "2530" rows were processed from the input file. "0" rows were
    successfully inserted into the table. "2530" rows were rejected.
    Error when using DEL export & import also:
    SQL3109N The utility is beginning to load data from file "exportrequest.del".
    SQL3512W The file named in row "1" and column "18" cannot be found, but the
    target column is not nullable. The row was not loaded.
    ...
    ...
    ...
    SQL3512W The file named in row "2539" and column "18" cannot be found, but
    the target column is not nullable. The row was not loaded.
    SQL3110N The utility has completed processing. "2539" rows were read from
    the input file.
    SQL3221W ...Begin COMMIT WORK. Input Record Count = "2539".
    SQL3222W ...COMMIT of any database changes was successful.
    SQL3149N "2539" rows were processed from the input file. "0" rows were
    successfully inserted into the table. "2539" rows were rejected.
    Number of rows read = 2539
    Number of rows skipped = 0
    Number of rows inserted = 0
    Number of rows updated = 0
    Number of rows rejected = 2539
    Number of rows committed = 2539

    Any idea how to load LOB data successfully?

    TIA.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •