Import Converted UNIX Data

After you convert your trading partner data, you can import the data into Sterling B2B Integrator.

About this task

To complete the import process:


  1. Import the final.xml file (or the renamed .xml output file) into Sterling B2B Integrator.
    Note: You may encounter the following error during the import of the .xml file into Sterling B2B Integrator:
    Code List :: [TABLE NAME  **BIG**][][] :: create ::
    FAILED :: [IBM][CLI Driver][DB2/SUN] SQL0964C  The transaction log
    for the database is full.  SQLSTATE=57011
    This error is related to conversion of the synonym tables. If this error occurs:
    1. Increase the transaction log size in the database.
    2. Increase the JVM heapsize to 2048.
    3. Stop the system.
    4. Restart the system.
    5. Retry the import.
  2. Review the import report to determine whether any errors occurred in the import process. Any object having an error associated with it (see the STATUS column) is not successfully imported. Therefore, you must correct the error and import the object again.
  3. Review the imported document envelopes, control numbers, code lists and, if necessary, modify them as needed.


You can now create complete trading partner profiles and perform related map conversion tasks. Use the Map Editor Sterling Gentran:Server for UNIX map conversion utility to convert the maps.

For more information about maps related to your converted trading partner data, see Map-Related Considerations When Converting Trading Partner Data.