SAP Knowledge Base Article - Preview

3751612 - The importing fails with "data file seems to be in old format (no header)" in SWPM

Symptom

  • During the import phase of a system copy/migration with SWPM, the process terminates with: "Data file seems to be in old format (no header)"
  • From the log Jload.trc, errors are as below:

<Date>, 2026 00:00:00 AM                       com.sap.inst.dbtools [Thread[pool-1-thread-1,5,main]] Fatal: com.sap.sql.exception.OpenSQLRecoverableException: [jcc][t4][10379][11961][4.33.32] Client disconnect exception encountered: [jcc][t4][2091][11332][4.33.32] Attempt to fully materialize lob data that is too large for the JVM.
Disable data source property "fullyMaterializeLobData" for locator-based lob implementation. ERRORCODE=-4499, SQLSTATE=null ERRORCODE=-4499, SQLSTATE=null 


Read more...

Environment

SAP Java systems.

Keywords

swpm import error, jload, jmigmon, data file seems to be in old format, no header, bc_msg, java heap space, outofmemoryerror, table split, control.xml, db2, jdbc, fullymaterializelobdata, system copy, migration , KBA , BC-INS-MIG , OS/DB Migrations with SWPM and DB refresh , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.