check_sql_list() failed for Table during ABAP Import

[Former Member]

Hello Gurus,

While doing a system copy via R3Load method for a ECC6.0 EHP6 on Win 2008 R2 , Oracle 11.2.0.3  system , I got an error during the ABAP Import phase on the target system for the last 2 packages

SAPAPPL0_1 & SAPAPPL0_2

Error Details for SAPAPPL0_1

--------------------------------------------

START OF LOG: 20140527194315

D:\usr\sap\DEV\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#17 $ SAP

D:\usr\sap\DEV\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]

Compiled Jan 16 2013 17:01:57

patchinfo (patches.h): (0.324) SYB: migration to sybase using unsorted unload/load (note 1734039)

process id 1556

D:\usr\sap\DEV\SYS\exe\uc\NTAMD64\R3load.exe -i SAPAPPL0_1.cmd -dbcodepage 4103 -l SAPAPPL0_1.log -stop_on_error

DbSl Trace: ORA-1403 when accessing table SAPUSER

(DB) INFO: connected to DB

(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF16

(GSI) INFO: dbname   = "DEV20140526020559                                                                                                               "

(GSI) INFO: vname    = "ORACLE                          "

(GSI) INFO: hostname = "ORSAPDEV02                                                      "

(GSI) INFO: sysname  = "Windows NT"

(GSI) INFO: nodename = "ORSAPDEV02"

(GSI) INFO: release  = "6.1"

(GSI) INFO: version  = "7601 Service Pack 1"

(GSI) INFO: machine  = "2x AMD64 Level 6 (Mod 44 Step 2)"

(RTF) ########## WARNING ###########

  Without ORDER BY PRIMARY KEY the exported data may be unusable for some databases

(SQL) INFO: Searching for SQL file SQLFiles.LST

(SQL) INFO: SQLFiles.LST not found

(SQL) INFO: Searching for SQL file S:\SBX_Export_dump\ABAP\DB/SQLFiles.LST

(SQL) INFO: found S:\SBX_Export_dump\ABAP\DB/SQLFiles.LST

(SQL) INFO: Trying to open S:\SBX_Export_dump\ABAP\DB/SQLFiles.LST

(SQL) INFO: S:\SBX_Export_dump\ABAP\DB/SQLFiles.LST opened

(SQL) INFO: Searching for SQL file APPL0.SQL

(SQL) INFO: APPL0.SQL not found

(SQL) INFO: Searching for SQL file S:\SBX_Export_dump\ABAP\DB/ORA/APPL0.SQL

(SQL) INFO: found S:\SBX_Export_dump\ABAP\DB/ORA/APPL0.SQL

(SQL) INFO: Trying to open S:\SBX_Export_dump\ABAP\DB/ORA/APPL0.SQL

(SQL) INFO: S:\SBX_Export_dump\ABAP\DB/ORA/APPL0.SQL opened

(SQL) ERROR: Invalid entry at line 5 in file S:\SBX_Export_dump\ABAP\DB/ORA/APPL0.SQL

(SQL) ERROR: SQL list was not built successfully

(DDL) ERROR: check_sql_list() failed for /1CN/CPASAP00001

(IMP) INFO: a failed DROP attempt is not necessarily a problem

(SQL) ERROR: SQL list was not built successfully

(DDL) ERROR: check_sql_list() failed for /1CN/CPASAP00001

(DB) INFO: disconnected from DB

D:\usr\sap\DEV\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)

D:\usr\sap\DEV\SYS\exe\uc\NTAMD64\R3load.exe:

END OF LOG: 20140527194325

Error log for package SAPAAPL0_2

---------------------------------------------------------

D:\usr\sap\DEV\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20140527194315

D:\usr\sap\DEV\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#17 $ SAP

D:\usr\sap\DEV\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]

Compiled Jan 16 2013 17:01:57

patchinfo (patches.h): (0.324) SYB: migration to sybase using unsorted unload/load (note 1734039)

process id 5028

D:\usr\sap\DEV\SYS\exe\uc\NTAMD64\R3load.exe -i SAPAPPL0_2.cmd -dbcodepage 4103 -l SAPAPPL0_2.log -stop_on_error

DbSl Trace: ORA-1403 when accessing table SAPUSER

(DB) INFO: connected to DB

(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF16

(GSI) INFO: dbname   = "DEV20140526020559                                                                                                               "

(GSI) INFO: vname    = "ORACLE                          "

(GSI) INFO: hostname = "ORSAPDEV02                                                      "

(GSI) INFO: sysname  = "Windows NT"

(GSI) INFO: nodename = "ORSAPDEV02"

(GSI) INFO: release  = "6.1"

(GSI) INFO: version  = "7601 Service Pack 1"

(GSI) INFO: machine  = "2x AMD64 Level 6 (Mod 44 Step 2)"

(RTF) ########## WARNING ###########

  Without ORDER BY PRIMARY KEY the exported data may be unusable for some databases

(SQL) INFO: Searching for SQL file SQLFiles.LST

(SQL) INFO: SQLFiles.LST not found

(SQL) INFO: Searching for SQL file S:\SBX_Export_dump\ABAP\DB/SQLFiles.LST

(SQL) INFO: found S:\SBX_Export_dump\ABAP\DB/SQLFiles.LST

(SQL) INFO: Trying to open S:\SBX_Export_dump\ABAP\DB/SQLFiles.LST

(SQL) INFO: S:\SBX_Export_dump\ABAP\DB/SQLFiles.LST opened

(SQL) INFO: Searching for SQL file APPL0.SQL

(SQL) INFO: APPL0.SQL not found

(SQL) INFO: Searching for SQL file S:\SBX_Export_dump\ABAP\DB/ORA/APPL0.SQL

(SQL) INFO: found S:\SBX_Export_dump\ABAP\DB/ORA/APPL0.SQL

(SQL) INFO: Trying to open S:\SBX_Export_dump\ABAP\DB/ORA/APPL0.SQL

(SQL) INFO: S:\SBX_Export_dump\ABAP\DB/ORA/APPL0.SQL opened

(SQL) ERROR: Invalid entry at line 5 in file S:\SBX_Export_dump\ABAP\DB/ORA/APPL0.SQL

(SQL) ERROR: SQL list was not built successfully

(DDL) ERROR: check_sql_list() failed for KALM

(IMP) INFO: a failed DROP attempt is not necessarily a problem

(SQL) ERROR: SQL list was not built successfully

(DDL) ERROR: check_sql_list() failed for KALM

(DB) INFO: disconnected from DB

D:\usr\sap\DEV\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)

D:\usr\sap\DEV\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20140527194334

Further Details

==============

Had chosen to split tables before copy and had also executed SMIGR_CREATE_DDL report prior to DB export with target - Oracle DB.

Copied the resultant .SQL files into Export_dump/ABAP/DB directory.

After getting the error, and reading the guides and the posts on SCN , I copied the .SQL files into ABAP/DB/ORA directory as well and then restarted the Import again for the failed packages, but the import fails again.

Any clues/ suggestions would really be helpful.

Regards

Prashant

[former_member188883 · Accepted solution]

Hi Prashant,

From the error logs

(SQL) INFO: S:\SBX_Export_dump\ABAP\DB/ORA/APPL0.SQL opened
(SQL) ERROR: Invalid entry at line 5 in file S:\SBX_Export_dump\ABAP\DB/ORA/APPL0.SQL
(SQL) ERROR: SQL list was not built successfully
(DDL) ERROR: check_sql_list() failed for /1CN/CPASAP00001
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(SQL) ERROR: SQL list was not built successfully

You did not execute SMIGR_CREATE_DDL on the source system and copied the resulting SQL files over...

You need to execute this report before the export and copy these files to target system export dump location before starting the import.

Hope this helps.

Regards,

Deepak Kori

[Former Member · Accepted solution]

Hi Deepak,

Thanks for the quick response,

I have executed the  SMIGR_CREATE_DDL report prior to DB export with target - Oracle DB.

Copied the resultant .SQL files into Export_dump/ABAP/DB directory.

This has worked for us in the past when our ECC 6.0 system was unupgraded  , however post the EHP6 upgrade, this is the 1st System copy via R3load method.

After getting the error, and reading the guides and the posts on SCN , I copied the .SQL files into ABAP/DB/ORA directory as well and then restarted the Import again for the failed packages, but the import fails again.

I think we may have to restart the import from scratch.

Regards

Prashant

[lars_jung · Accepted solution]

Hi Prashant,

please check line 5 in file  "APPL0.SQL"

(Invalid entry at line 5 in file S:\SBX_Export_dump\ABAP\DB/ORA/APPL0.SQL)

If the entry are only "ind:" try to delete this enty and retry the import

Regards

Claas

[Former Member · Accepted solution]

There is also a know issue within SAP where the .SQL files are created in error and include on line 5 for the .SQL fillles the entry ind:

....

Dear Chris,

It was wrongly generating the .SQL files as we can see in the log of each package from import, as I mentioned before:

"(SQL) ERROR: Invalid entry at line 5 in file

/<export dump location>/ABAP/DB/ORA/APPL0.SQL"

Edit all the .SQL files generated and remove the line 5:, that have the content:

ind:

Just remove the line and save the files. After that restart the import from scratch.

.....

[former_member340931]

Hi to all,

I get exactly the same problem as yours Prashants.

I made a lot of OS/DB Migrations since years without this problem before (I'm used to run SMIGR and so on).

This problem Its follows an SAP Upgrade to ECC6 Ehp7.

After an SAP Upgrade ECC6 Ehp6 it was not the case !

My log files show exactly the same errors :

(RDI) INFO: /EXPORT_DB/ABAP/DATA/SAP0000.STR has format version 3

(SQL) INFO: Searching for SQL file SQLFiles.LST

(SQL) INFO: SQLFiles.LST not found

(SQL) INFO: Searching for SQL file /EXPORT_DB/ABAP/DB/SQLFiles.LST

(SQL) INFO: found /EXPORT_DB/ABAP/DB/SQLFiles.LST

(SQL) INFO: Trying to open /EXPORT_DB/ABAP/DB/SQLFiles.LST

(SQL) INFO: /EXPORT_DB/ABAP/DB/SQLFiles.LST opened

(SQL) INFO: Searching for SQL file SLEXC.SQL

(SQL) INFO: SLEXC.SQL not found

(SQL) INFO: Searching for SQL file /EXPORT_DB/ABAP/DB/ORA/SLEXC.SQL

(SQL) INFO: found /EXPORT_DB/ABAP/DB/ORA/SLEXC.SQL

(SQL) INFO: Trying to open /EXPORT_DB/ABAP/DB/ORA/SLEXC.SQL

(SQL) INFO: /EXPORT_DB/ABAP/DB/ORA/SLEXC.SQL opened

(SQL) ERROR: Invalid entry at line 5 in file /EXPORT_DB/ABAP/DB/ORA/SLEXC.SQL

(SQL) ERROR: SQL list was not built successfully

(DDL) ERROR: check_sql_list() failed for REPOLOAD

(IMP) INFO: a failed DROP attempt is not necessarily a problem

(SQL) ERROR: SQL list was not built successfully

(DDL) ERROR: check_sql_list() failed for REPOLOAD

(DB) INFO: disconnected from DB

I've never seen this message, not sure to have to delete the line 5 with "ind:".

Any help would be appreciated. Did you solve your problem ? How ?

Regards,

Stéphan

[former_member340931]

To all,

Be informed that I looked again.

My generated SQL files by SMIGR_CREATE_DDL on SAP ECC6 EHP7 are bad files.

They are truncated and contain a "ind:" at line number 5 of the SQL files.

I tried to run again SMIGR_CREATE_DDL on an SAP ECC6 EHP6 and the generated SQL files are OK.

So, problem linked to a report bug certainly arrived between EHP6 and EHP7 or with SAP NW 7.40.

Regards,

Stéphan

[charles_koekemoer2]

Hello,

I am also facing the same issue and using the latest 70SWPM since I am exporting and now importing a 731 or in simple terms NW7.0 EHP 3. Anyone with a any clue as I have logged an incident and the SAPAG wants silly logs to delay my process?

Regards,

CK

[Former Member]

Hello Charles,

As Stephan  rightly pointed out, this is most likely due to bad / incomplete .SQL files generated from the SMIGR report run.

I also was in similar situation and had to cancel the import and regenerate the SQL files via the SMIGR_CREATE_DDL [after logging off all users and ensuring no further changes , this part is important]

Then we retried the Import again and it went through like a charm.

You may also try and identify the problem with the .SQL file as  Class mentioned above, but we didnt take a chance as this might mess things up and we started from scratch again to avoid inconsistencies  and I would recommend the same.

Cheers

Prashant

[charles_koekemoer2]

Prashant,

Thank you for your feedback and experience on this issue. I have locked out all users and ensured that nothing was running at the time. the funny part is the when doing the import, the tablespace PSAPSR3USR is also not created thus I think we have a bug on these latests SWPM. I have tried the same with table splitting and the other without splitting the tables and the results are the same which is unfortunate as I have lost time.

Kind regards,

CK

[charles_koekemoer2]

Team,

Is there a note that we should implement prior to running the "SMIGR_CREATE_DDL"?

Kind regards,

CK

[former_member340931]

Hi all,

The export is KO if you do not restart all process after correcting the SMIGR_CREATE_DDL report bug.

In my case, following SAP recommandation, I had to :

- Implement SAP Note 1991576 to correct SMIGR_CREATE_DDL report.

- Remake all the SAP database export process, including the run of SMIGR_CREATE_DDL of course.

Hope it helps.

Regards,

Stéphan

[charles_koekemoer2]

Stephan,

Thanx for the note which is applicable to my system, the question that I have now noticed is the the report 'SMIGR_CREATE_DDL' only created three <TABART>.SQL instead of the 21 that I have on table '"TAORA": Any clue experts?

Regards,

CK

[former_member340931]

The SMIGR_CREATE_DDL creates only files as needed.

On mine I get the following SQL files generated:

- APPL0.SQL

- APPL1.SQL

- APPL2.SQL

- SDIC.SQL

- SLEXC.SQL

- SLOAD.SQL

- SPROT.SQL

- SSEXC.SQL

- SSRC.SQL

Edit : it could be that your system contains only standard database objects.

[charles_koekemoer2]

This I found to be strange

............................

#

# ORACLE : LIST OF .SQL FILES OF NATIVE SQL EXPORT GENERATED AT 20150314073320

#

APPL0.SQL

APPL1.SQL

APPL2.SQL

........................................

Can you check the table TAORA on your system and confirm if the TABART is equivalent to the generated .SQL files?

Regards,

CK

[former_member340931]

Charles,

Of course I get more entries in TAORA table than the number of SQL files generated.

As SAP say in TADM70 cursus :

SMIGR_CREATE_DDL : generates <TABART>.SQL files containing DDL statements for non-standard ABAP database objects.

My understanding of your case : you get only few non standard objects in your SAP system. If they are only contained in class APPL0, 1 and 2, I think it is just normal that you only get those 3 files.

Hope it helps.

Stéphan

[charles_koekemoer2]

Stephan,

Excellent point, I did check and you are 100% correct which have now cleared the issue of .SQL generated by the SMIGR program.

The log is complaining about "Invalid entry at line 5 in file /export/Export2/ABAP/DB/ORA/APPL1.SQL" and below is the few entries of the .APPL1.SQL

................................................

#

# ORACLE : NATIVE SQL EXPORT GENERATED AT 20150314073320

#

ind:

tab: GVD_BGPROCESS

sql:    CREATE TABLE "GVD_BGPROCESS"

      ("SNAPSHOT_ID" VARCHAR2 (000030)

        DEFAULT '0000000000' NOT NULL,

       "INST_ID" NUMBER (000022, 000000)

        DEFAULT 0 NOT NULL,

       "NAME" VARCHAR2 (000015)

        DEFAULT ' ' NOT NULL,

       "PADDR" RAW (000008),

       "DESCRIPTION" VARCHAR2 (000192)

        DEFAULT ' ' NOT NULL,

       "ERROR" NUMBER (000022, 000000)

        DEFAULT 0 NOT NULL)

      PCTFREE 00

      PCTUSED 00

      INITRANS 001

      TABLESPACE &APPL1&

   COMPRESS BASIC

   STORAGE (INITIAL     0000000064 K

               NEXT        0000001024 K

               MINEXTENTS  0000000001

               MAXEXTENTS  UNLIMITED

               PCTINCREASE 0000

               FREELISTS   001

               FREELIST GROUPS 01) ;

tab: GVD_BUFF_POOL_ST

sql:    CREATE TABLE "GVD_BUFF_POOL_ST"

      ("SNAPSHOT_ID" VARCHAR2 (000030)

        DEFAULT '0000000000' NOT NULL,

       "INST_ID" NUMBER (000022, 000000)

        DEFAULT 0 NOT NULL,

       "ID" NUMBER (000022, 000000)

        DEFAULT 0 NOT NULL,

       "NAME" VARCHAR2 (000060)

        DEFAULT ' ' NOT NULL,

       "BLOCK_SIZE" NUMBER (000022, 000000)

        DEFAULT 0 NOT NULL,

       "SET_MSIZE" NUMBER (000022, 000000)

......................

What can be done to correct the problem.

Regards,

CK

[charles_koekemoer2]

Team,

I have removed line 5 (ind) and the import is running fine again.

Regards,

CK

[former_member340931]

Exact.

I would have suggested 2 different solutions :

1. repare SMIGR report with a SAP note and rerun it

2. comment line 5 of the SQL file and retry

You applied the second one by yourself.

Good to read when someone found a solution with help of the forum !

Stéphan

[charles_koekemoer2]

Stephan,

Thank you very much sir for your time and assistance.

Regards,

CK

[former_member340931]

You're welcome.

Couple of times people helped me to solve my problems on this forum.

It's my turn.

Stéphan