SAP Knowledge Base Article - Preview

3410218 - SUM-DMO - error SQL0206N "S.MANDT" is not valid in the context where it is used. SQLSTATE=42703 in phase EU_CLONE_MIG_OPTDMO_INI_RUN

Symptom

***** Consulting KBA - the following recommendations are not from solution support nor from product development *****

  • SUM DMO migration fails at phase EU_CLONE_MIG_OPTDMO_INI_RUN.
  • Downtime-optimization feature is enabled for DMO.
  • Error(s) similar to "SQL0206N  "S.MANDT" is not valid in the context where it is used.  SQLSTATE=42703" written in log file MIGRATE_OPTDMO_INI_RUN.LOG.
  • Source database is DB2-UDB/DB6.
  • Target database is SAP HANA 2.0.
  • Log file MIGRATE_OPTDMO_INI_RUN.LOG contains messages similar to the below highlighted example.

A1 EGEN 004 /migration/SUM/abap/bin/R3load: START OF LOG: 20231205235325
A1 EGEN 002 ====================================================
A1 EGEN 006 RELEASE: version lmt_022, code page [UNICODE]
A1 EGEN 008 Source ID: "@(#) $Id: //bc/lmt_022_REL/src/upg/R3ld/R3load/R3ldmain.c#30 $ SAP", compile time: "20:00:25 Nov 8 2023"
A1 EGEN 007 DBSL: version 753
A1 EGEN 016 FORMAT: data 1.28, STR-file 20, log level: 4
A1 EGEN 002 ====================================================
A1 EGEN 010 PROCENV: working directory "/migration/SUM/abap/load/migrate_optdmo_ini", process id 3408384
A1 EGEN 011 CMDLINE: "/migration/SUM/abap/bin/R3load -e /migration/SUM/abap/load/migrate_optdmo_ini/MIGRATE_OPTDMO_INI_00068_RFBLG_EXP.CMD -read_committed -table_suffix ~ -l /migration/SUM/abap/load/migrate_optdmo_ini/MIGRATE_OPTDMO_INI_00068_RFBLG_EXP.LOG"
A1 EGEN 002 ====================================================
A1 EAUX 003 Setting R3LOAD_CLUSORT_MAXFILESIZE=800000000000
A1 ETPL 002 Template '/migration/SUM/abap/load/migrate_optdmo_ini/DDLDB6_LRG.TPL' has version 4.
A2 EGEN 001 Connecting to database 'db6'.
A1 EDBS 000 Connected to DB 'DB6'.
A3 ECNV 015 Initializing code page conversion routines.
A1 EMIG 000 DB: name = '<DBSID>', vendor = 'DB6', dbhost = 'UNKNOWN'
A1 EMIG 001 DB: version = '11.05.0800', client = 'DB6_81'
A1 EMIG 002 OS: sysname = 'AIX', hostname = 'xxxxxxx0-a', machine = 'xxxxxxxxx'
A1 EMIG 003 OS: release = '2', version = '7'
A1 EMIG 004 Installation number = 'xxxxxxxx'
A1 EDAT 000 ====================================================
A1 EEXP 000 ====================================================
A3 ESTR 000 Found logical cluster description for RFBLG in /migration/SUM/abap/load/migrate_optdmo_ini/SAPRFBLG.STR.logical
A2 ETSK 000 Starting export for object "RFBLG" of type "zap rows logged for replay" #20231205235331
A3 EEXP 011 Table RFBLG will be exported with sorting (task modifier).
A1 EDBS 006 Using isolation level 'read committed'.
A3EEEXP 008 Task failed with error: (EXP) DbSlBegRead failed for table 'RFBLG'
A3EEEXP 008 (EXP) SQL error = -206
A3EEEXP 008 (EXP) SQL0206N "S.MANDT" is not valid in the context where it is used. SQLSTATE=42703
A3EEEXP 008 (EXP) ABAP table name is 'RFBLG'
A3EEEXP 008 (EXP) Additional table used is '/1CRR/LT00000006'
A1 EGEN 002 ====================================================
A1 EDAT 007 Resource usage: GENERAL times: 1.245/ 0.344/ 0.009 18.2%/99.0%/94.1% real/usr/sys
A1 EDAT 007 Resource usage: DATABASE times: 0.019/ 0.000/ 0.000 0.3%/ 0.1%/ 3.9% real/usr/sys
A1 EDAT 007 Resource usage: PIPE times: 5.572/ 0.003/ 0.000 81.5%/ 0.9%/ 2.0% real/usr/sys
A1 EDAT 006 Memory usage: 12/0/0 MB buffer/objectcache/disk (0 reused buffers)
A1EEGEN 025 Number of error(s): 1
A1EEGEN 026 Exit code: "8"
A1 EGEN 005 /migration/SUM/abap/bin/R3load: END OF LOG: 20231205235331


Read more...

Environment

  • SAP ERP 6.0 EhP8
  • IBM DB2 UDB 11.5 MP8 FP0
  • SAP HANA 2.0 rev 59.08
  • AIX 7.2 TL5 SP6
  • SUM 2.0 SP18 Patch 4

Product

SAP ERP 6.0 ; SAP HANA, platform edition 2.0 ; SAP enhancement package 8 for SAP ERP 6.0

Keywords

DDLCRR.TPL, EU_CLONE_MIG_OPTDMO_INI_RUN, SQL0206N, SQLSTATE=42703, zap rows logged for replay, DbSlBegRead, MIGRATE_OPTDMO_INI_RUN.LOG , KBA , BC-UPG-TLS-TLA , Upgrade tools for ABAP , BC-DB-DB6 , DB2 Universal Database for Unix / NT , 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.