Question Re: ABAP Import Phase DDL Statement Error in Technology Q&A

ABAP Import Phase DDL Statement Error

Former Member — Mon, 25 Aug 2014 06:10:31 GMT

Hi Experts!

I am installing SAP Netweaver PI 7.3 EHP1 and encountered an error in the ABAP import phase.

I checked the import monitor logs and found a clue about SAPVIEW.log.

I have checked the SAPVIEW.log and found out the following:

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

ERROR: DDL statement failed

( DROP VIEW "APPL_MODS" )

dsql_exec_immediate returned DS_DBOBJECTUNKNOWN

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

(DB) ERROR: DDL statement failed

( CREATE VIEW "APPL_MODS" ( "NAME", "TYP", "MEMBER", "DEVCLASS" ) AS SELECT T0001."NAME", T0001."TYP", T0001."MEMBER", T0002."DEVCLASS" FROM "MODSAP" T0001, "MODSAPA" T0002 WHERE T0001."NAME" = T0002."NAME" AND T0002."MIGRATED" <> 'X' )

dsql_exec_immediate returned DS_DBOBJECTUNKNOWN

(DB) INFO: disconnected from DB

/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: job finished with 1 error(s)

/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: END OF LOG:

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

Please help!

Also please let me know if any further detail is required.

Regards,

Ayan

Re: ABAP Import Phase DDL Statement Error

former_member182657 — Mon, 25 Aug 2014 06:26:56 GMT

Hi Ayan,

Kindly follow SAP Note 1837199 - DB6: Error DS_DBOBJECTUNKNOWN during ABAP import and share complete SAPVIEW.log file for analysis,also try to execute command


CREATE VIEW "APPL_MODS" ( "NAME", "TYP", "MEMBER", "DEVCLASS" ) AS SELECT T0001."NAME", T0001."TYP", T0001."MEMBER", T0002."DEVCLASS" FROM "MODSAP" T0001, "MODSAPA" T0002 WHERE T0001."NAME" = T0002."NAME" AND T0002."MIGRATED" <> 'X'

at db level and retry the phase again.

Regards,

Gaurav

Re: ABAP Import Phase DDL Statement Error

Former Member — Mon, 25 Aug 2014 06:35:43 GMT

Hi Gaurav,

Thanks for your quick response!

The SAP note asks to create a support incident, which can only be created if I register my system.

Since my installation is not complete, so I cannot raise an incident.

Well, I have tried to execute the command in the DB level and it gives the following error:

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

db2 => CREATE VIEW "APPL_MODS" ( "NAME", "TYP", "MEMBER", "DEVCLASS" ) AS SELECT T0001."NAME", T0001."TYP", T0001."MEMBER", T0002."DEVCLASS" FROM "MODSAP" T0001, "MODSAPA" T0002 WHERE T0001."NAME" = T0002."NAME" AND T0002."MIGRATED" <> 'X'

DB21034E The command was processed as an SQL statement because it was not a

valid Command Line Processor command. During SQL processing it returned:

SQL0204N "DB2PID.MODSAP" is an undefined name. SQLSTATE=42704

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

Please suggest!

Regards,

Ayan

Re: ABAP Import Phase DDL Statement Error

Former Member — Mon, 25 Aug 2014 06:41:09 GMT

Gaurav,

Please find the below pasted trace from SAPVIEW.log

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

/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: START OF LOG: 20140823014048

/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: sccsid @(#) $Id: //bas/721_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP

/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: version R7.20/V1.6 [UNICODE]

Compiled Dec 4 2013 12:54:08

/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load -ctf I /backup/NW7.3_EHP1/ABAP_Inst_EXP/51043228/DATA_UNITS/EXP3/DATA/SAPVIEW.STR /tmp/sapinst_instdir/NW731/DB6/INSTALL/STD/AS/DDLDB6.TPL SAPVIEW.TSK DB6 -l SAPVIEW.log

/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: job completed

/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: END OF LOG: 20140823014048

/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: START OF LOG: 20140823014048

/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: sccsid @(#) $Id: //bas/721_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP

/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: version R7.20/V1.6 [UNICODE]

Compiled Dec 4 2013 12:54:08

/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load -i SAPVIEW.cmd -dbcodepage 4102 -l SAPVIEW.log -stop_on_error -loadprocedure fast LOAD:DEF_CRT

(DB) INFO: connected to DB

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

(SQL) INFO: SQLFiles.LST not found

(SQL) INFO: Searching for SQL file /backup/NW7.3_EHP1/ABAP_Inst_EXP/51043228/DATA_UNITS/EXP3/DB/SQLFiles.LST

(SQL) INFO: /backup/NW7.3_EHP1/ABAP_Inst_EXP/51043228/DATA_UNITS/EXP3/DB/SQLFiles.LST not found

(SQL) INFO: Searching for SQL file .SQL

(SQL) INFO: .SQL not found

(SQL) INFO: Searching for SQL file /backup/NW7.3_EHP1/ABAP_Inst_EXP/51043228/DATA_UNITS/EXP3/DB/DB6/.SQL

(SQL) INFO: /backup/NW7.3_EHP1/ABAP_Inst_EXP/51043228/DATA_UNITS/EXP3/DB/DB6/.SQL not found

(DB) INFO: /BI0/MHIER_VERS created #20140823014054

(DB) INFO: /BI0/RALEAFNODCH created #20140823014054

(DB) INFO: /BI0/RALEAFNODSP created #20140823014054

(DB) INFO: /BI0/RBUCKET created #20140823014054

(DB) INFO: /BI0/RCALMONTH created #20140823014054

(DB) INFO: /BI0/RCALMONTH2 created #20140823014054

(DB) INFO: /BI0/RCALQUART1 created #20140823014054

(DB) INFO: /BI0/RCALQUARTER created #20140823014054

(DB) INFO: /BI0/RCALWEEK created #20140823014054

(DB) INFO: /BI0/RCALYEAR created #20140823014054

(DB) INFO: /BI0/RCHNGID created #20140823014054

(DB) INFO: /BI0/RCURRENCY created #20140823014054

(DB) INFO: /BI0/RDATE created #20140823014054

(DB) INFO: /BI0/RFISCPER created #20140823014054

(DB) INFO: /BI0/RFISCPER3 created #20140823014054

(DB) INFO: /BI0/RFISCVARNT created #20140823014054

(DB) INFO: /BI0/RFISCYEAR created #20140823014054

(DB) INFO: /BI0/RHALFYEAR1 created #20140823014054

(DB) INFO: /BI0/RHIENM created #20140823014054

(DB) INFO: /BI0/RHIER_HIEID created #20140823014054

(DB) INFO: /BI0/RHIER_NODE created #20140823014054

(DB) INFO: /BI0/RHIER_VERS created #20140823014054

(DB) INFO: /BI0/RINFOPROV created #20140823014054

(DB) INFO: /BI0/RIOBJNM created #20140823014054

(DB) INFO: /BI0/RLANGU created #20140823014054

(DB) INFO: /BI0/RLOGSYS created #20140823014054

(DB) INFO: /BI0/RNODEPOSIT created #20140823014054

(DB) INFO: /BI0/RNORESTNODE created #20140823014054

(DB) INFO: /BI0/RRATE_TYPE created #20140823014054

(DB) INFO: /BI0/RRECORDMODE created #20140823014054

(DB) INFO: /BI0/RRECORDTP created #20140823014054

(DB) INFO: /BI0/RREQUID created #20140823014054

(DB) INFO: /BI0/RSIGNCH created #20140823014054

(DB) INFO: /BI0/RSOURSYSTEM created #20140823014054

(DB) INFO: /BI0/RTIME created #20140823014054

(DB) INFO: /BI0/RTXTLG created #20140823014054

(DB) INFO: /BI0/RTXTMD created #20140823014054

(DB) INFO: /BI0/RTXTSH created #20140823014054

(DB) INFO: /BI0/RUNIT created #20140823014054

(DB) INFO: /BI0/RWEEKDAY1 created #20140823014054

(DB) INFO: /BI0/ZBUCKET created #20140823014054

(DB) INFO: /BI0/ZCALMONTH created #20140823014054

(DB) INFO: /BI0/ZCALMONTH2 created #20140823014054

(DB) INFO: /BI0/ZDATE created #20140823014054

(DB) INFO: /BI0/ZFISCPER created #20140823014055

(DB) INFO: /BI0/ZHALFYEAR1 created #20140823014055

(DB) INFO: /BI0/ZINFOPROV created #20140823014055

(DB) INFO: /BI0/ZIOBJNM created #20140823014055

(DB) INFO: /GC1/VXXX created #20140823014055

(DB) INFO: /OSP/V_RAUI_CHRD created #20140823014055

(DB) INFO: /OSP/V_RAUI_CMVD created #20140823014055

(DB) INFO: /OSP/V_RAUI_CPVD created #20140823014055

(DB) INFO: /OSP/V_RAUI_CSED created #20140823014055

(DB) INFO: /OSP/V_RAUI_DCDB created #20140823014055

(DB) INFO: /OSP/V_RAUI_GRPD created #20140823014055

(DB) INFO: /OSP/V_RAUI_MTD created #20140823014055

(DB) INFO: /OSP/V_RAUI_MVDB created #20140823014055

(DB) INFO: /OSP/V_RAUI_PBDB created #20140823014055

(DB) INFO: /OSP/V_RAUI_RDDB created #20140823014055

(DB) INFO: /OSP/V_RAUI_RFCD created #20140823014055

(DB) INFO: /OSP/V_RAUI_RMTD created #20140823014055

(DB) INFO: /OSP/V_RAUI_RTDB created #20140823014055

(DB) INFO: /OSP/V_RAUI_SCD created #20140823014055

(DB) INFO: /OSP/V_RAUI_SCHD created #20140823014055

(DB) INFO: /OSP/V_RAUI_SELD created #20140823014055

(DB) INFO: /OSP/V_RAUI_TMVD created #20140823014055

(DB) INFO: /OSP/V_RAUI_TPBD created #20140823014055

(DB) INFO: /OSP/V_RAUI_TPDB created #20140823014055

(DB) INFO: /OSP/V_RAUI_TPRD created #20140823014055

(DB) INFO: /OSP/V_RAUI_TRGD created #20140823014055

(DB) INFO: /OSP/V_RAUI_VARD created #20140823014055

(DB) INFO: /SAPAPO/GEWICHT created #20140823014055

(DB) INFO: /SAPAPO/TRENDAM created #20140823014055

(DB) INFO: /SAPAPO/VWALPROF created #20140823014055

(DB) INFO: /SAPPO/FULL_HINT created #20140823014055

(DB) INFO: /SAPPO/V_PPOCMPL created #20140823014055

(DB) INFO: /SAPPO/V_PPO_UPD created #20140823014055

(DB) INFO: /SAPTRX/A_CONDF4 created #20140823014055

(DB) INFO: /SAPTRX/EE_FLDS created #20140823014055

(DB) INFO: /SAPTRX/MSG_PARA created #20140823014055

(DB) INFO: /SAPTRX/MSG_PTAB created #20140823014055

(DB) INFO: /SAPTRX/STR_FLDS created #20140823014055

(DB) INFO: /SAPTRX/VDASFEV created #20140823014055

(DB) INFO: /SAPTRX/VDASFPAR created #20140823014055

(DB) INFO: /SAPTRX/VD_AOMIL created #20140823014055

(DB) INFO: /SAPTRX/VD_AOPAC created #20140823014055

(DB) INFO: /SAPTRX/VD_AOPAE created #20140823014055

(DB) INFO: /SAPTRX/VD_AOPAI created #20140823014055

(DB) INFO: /SAPTRX/VD_AOPAR created #20140823014055

(DB) INFO: /SAPTRX/VD_AOTD1 created #20140823014055

(DB) INFO: /SAPTRX/VD_AOTD2 created #20140823014055

(DB) INFO: /SAPTRX/VD_AOTDD created #20140823014055

(DB) INFO: /SAPTRX/VD_AOTYP created #20140823014055

(DB) INFO: /SAPTRX/VD_ASPAR created #20140823014055

(DB) INFO: /SAPTRX/VD_CONDL created #20140823014055

(DB) INFO: /SAPTRX/VD_EVTD1 created #20140823014055

(DB) INFO: /SAPTRX/VD_EVTD2 created #20140823014055

(DB) INFO: /SAPTRX/VD_EVTD3 created #20140823014055

(DB) INFO: /SAPTRX/VD_EVTD4 created #20140823014055

(DB) INFO: /SAPTRX/V_AODD02 created #20140823014055

(DB) INFO: /SAPTRX/V_DD03 created #20140823014055

(DB) INFO: /SAPTRX/V_DD03X created #20140823014055

(DB) INFO: /SDF/CMO_OBJ_TR created #20140823014055

(DB) INFO: /SDF/CMO_SMDCMP created #20140823014056

(DB) INFO: /SDF/CMO_SMDDVC created #20140823014056

(DB) INFO: /SDF/CMO_UMDCMP created #20140823014056

(DB) INFO: /SDF/SMODICOMP created #20140823014056

(DB) INFO: /SDF/SMODIDEVC created #20140823014056

(DB) INFO: /SDF/UMOD_COMP created #20140823014056

(DB) INFO: AKB_TRHD_DETAIL created #20140823014056

(DB) INFO: ALTEXTHIST created #20140823014056

(DB) INFO: APPL_DEVC created #20140823014056

(DB) INFO: APPL_DIAL created #20140823014056

(DB) INFO: APPL_DOMA created #20140823014056

(DB) INFO: APPL_DTEL created #20140823014056

(DB) INFO: APPL_ENQU created #20140823014056

(DB) INFO: APPL_FUGR created #20140823014056

(DB) INFO: APPL_FUGRG created #20140823014056

(DB) INFO: APPL_FUNC created #20140823014056

(DB) INFO: APPL_INDX created #20140823014056

(DB) INFO: APPL_MCOB created #20140823014056

(DB) INFO: APPL_MENU created #20140823014056

(DB) ERROR: DDL statement failed

dsql_exec_immediate returned DS_DBOBJECTUNKNOWN

(DB) INFO: disconnected from DB

/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: job finished with 1 error(s)

/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: END OF LOG: 20140823014056

/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: START OF LOG: 20140823014312

/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: sccsid @(#) $Id: //bas/721_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP

/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: version R7.20/V1.6 [UNICODE]

Compiled Dec 4 2013 12:54:08

/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load -i SAPVIEW.cmd -dbcodepage 4102 -l SAPVIEW.log -stop_on_error -loadprocedure fast LOAD:DEF_CRT

(DB) INFO: connected to DB

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

(SQL) INFO: SQLFiles.LST not found

(SQL) INFO: Searching for SQL file /backup/NW7.3_EHP1/ABAP_Inst_EXP/51043228/DATA_UNITS/EXP3/DB/SQLFiles.LST

(SQL) INFO: /backup/NW7.3_EHP1/ABAP_Inst_EXP/51043228/DATA_UNITS/EXP3/DB/SQLFiles.LST not found

(SQL) INFO: Searching for SQL file .SQL

(SQL) INFO: .SQL not found

(SQL) INFO: Searching for SQL file /backup/NW7.3_EHP1/ABAP_Inst_EXP/51043228/DATA_UNITS/EXP3/DB/DB6/.SQL

(SQL) INFO: /backup/NW7.3_EHP1/ABAP_Inst_EXP/51043228/DATA_UNITS/EXP3/DB/DB6/.SQL not found

(DB) ERROR: DDL statement failed

( DROP VIEW "APPL_MODS" )

dsql_exec_immediate returned DS_DBOBJECTUNKNOWN

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

(DB) ERROR: DDL statement failed

dsql_exec_immediate returned DS_DBOBJECTUNKNOWN

(DB) INFO: disconnected from DB

/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: job finished with 1 error(s)

/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: END OF LOG: 20140823014318

/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: START OF LOG: 20140823015246

/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: sccsid @(#) $Id: //bas/721_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP

/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: version R7.20/V1.6 [UNICODE]

Compiled Dec 4 2013 12:54:08

/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load -i SAPVIEW.cmd -dbcodepage 4102 -l SAPVIEW.log -stop_on_error -loadprocedure fast LOAD:DEF_CRT

(DB) INFO: connected to DB

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

(SQL) INFO: SQLFiles.LST not found

(SQL) INFO: Searching for SQL file /backup/NW7.3_EHP1/ABAP_Inst_EXP/51043228/DATA_UNITS/EXP3/DB/SQLFiles.LST

(SQL) INFO: /backup/NW7.3_EHP1/ABAP_Inst_EXP/51043228/DATA_UNITS/EXP3/DB/SQLFiles.LST not found

(SQL) INFO: Searching for SQL file .SQL

(SQL) INFO: .SQL not found

(SQL) INFO: Searching for SQL file /backup/NW7.3_EHP1/ABAP_Inst_EXP/51043228/DATA_UNITS/EXP3/DB/DB6/.SQL

(SQL) INFO: /backup/NW7.3_EHP1/ABAP_Inst_EXP/51043228/DATA_UNITS/EXP3/DB/DB6/.SQL not found

(DB) ERROR: DDL statement failed

( DROP VIEW "APPL_MODS" )

dsql_exec_immediate returned DS_DBOBJECTUNKNOWN

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

(DB) ERROR: DDL statement failed

dsql_exec_immediate returned DS_DBOBJECTUNKNOWN

(DB) INFO: disconnected from DB

/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: job finished with 1 error(s)

/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: END OF LOG: 20140823015250

/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: START OF LOG: 20140825011924

/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: sccsid @(#) $Id: //bas/721_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP

/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: version R7.20/V1.6 [UNICODE]

Compiled Dec 4 2013 12:54:08

/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load -i SAPVIEW.cmd -dbcodepage 4102 -l SAPVIEW.log -stop_on_error -loadprocedure fast LOAD:DEF_CRT

(DB) INFO: connected to DB

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

(SQL) INFO: SQLFiles.LST not found

(SQL) INFO: Searching for SQL file /backup/NW7.3_EHP1/ABAP_Inst_EXP/51043228/DATA_UNITS/EXP3/DB/SQLFiles.LST

(SQL) INFO: /backup/NW7.3_EHP1/ABAP_Inst_EXP/51043228/DATA_UNITS/EXP3/DB/SQLFiles.LST not found

(SQL) INFO: Searching for SQL file .SQL

(SQL) INFO: .SQL not found

(SQL) INFO: Searching for SQL file /backup/NW7.3_EHP1/ABAP_Inst_EXP/51043228/DATA_UNITS/EXP3/DB/DB6/.SQL

(SQL) INFO: /backup/NW7.3_EHP1/ABAP_Inst_EXP/51043228/DATA_UNITS/EXP3/DB/DB6/.SQL not found

(DB) ERROR: DDL statement failed

( DROP VIEW "APPL_MODS" )

dsql_exec_immediate returned DS_DBOBJECTUNKNOWN

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

(DB) ERROR: DDL statement failed

dsql_exec_immediate returned DS_DBOBJECTUNKNOWN

(DB) INFO: disconnected from DB

/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: job finished with 1 error(s)

/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: END OF LOG: 20140825011937

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

Please look into this..

Regards,

Ayan

Re: ABAP Import Phase DDL Statement Error

former_member182657 — Mon, 25 Aug 2014 06:54:08 GMT

Hi,

Could you check for SCN thread

Regards,
Gaurav

Re: ABAP Import Phase DDL Statement Error

Former Member — Mon, 25 Aug 2014 07:06:47 GMT

Hi Gaurav,

I have gone through the thread earlier too, but I'm unable to create the view manually since the tables are yet to be created.

Well, I'm curious about the ''GRANT access to sap connect user'' thing, as I have no idea how this could help..

Please suggest a way out.

Ayan

Re: ABAP Import Phase DDL Statement Error

Former Member — Mon, 25 Aug 2014 07:10:22 GMT

HI,

Should I create the tables ''MODSAP'' & ''MODSAPA'' manually and then try the DDL statement?

Ayan

Re: ABAP Import Phase DDL Statement Error

Frank-Martin — Mon, 25 Aug 2014 07:14:42 GMT

Usually all tables are created by other R3load processes before views are creates. So you need to check the other R3load log files why tables ''MODSAP'' & ''MODSAPA'' have not been created.

Regards

Frank

Re: ABAP Import Phase DDL Statement Error

Former Member — Mon, 25 Aug 2014 07:51:45 GMT

Hi Frank,

I have gone through your replies in the other threads too regarding the same issue.

Also as per your above response I have checked all the R3Load logs and found data in the MODSAPA table but there is no log where MODSAP has been mentioned. Hence the table has not been created.

Please suggest if I can create the "MODSAP" table manually..

Ayan

Re: ABAP Import Phase DDL Statement Error

former_member182657 — Mon, 25 Aug 2014 08:39:22 GMT

Hi Ayan,

I suggest you to raise an incident with SAP before any manual creations table, under other System in your landscape at SMP.

Regards,

Gaurav

Re: ABAP Import Phase DDL Statement Error

Former Member — Mon, 25 Aug 2014 08:48:18 GMT

Hi Ayan,

Have all other import jobs completed and only SAPVIEW is failing ?

This is just to ensure that required tables are imported .

Also check at DB level whether the missing tables are created or not.

Regards,

Deepak Kori

Re: ABAP Import Phase DDL Statement Error

Former Member — Mon, 25 Aug 2014 08:54:41 GMT

Hi Deepak,

SAPVIEW is the only job that is failing.

And I have checked at DB level, only MODSAP table has not been created, as per the present scenario.

Should I go with reverting the installation process?

Ayan

Re: ABAP Import Phase DDL Statement Error

Former Member — Mon, 25 Aug 2014 08:55:29 GMT

Hi Gaurav,

I have raised a ticket on the same from a similar system, and waiting for SAP response.

Ayan

Re: ABAP Import Phase DDL Statement Error

Former Member — Mon, 25 Aug 2014 09:06:31 GMT

Hi Ayan,

Suggestion here would be as follows

1) Copy the DVD dumps to location disk rather than using shared drive.

2) Clean up existing installation and perform fresh installation.

Regards,

Deepak Kori

Re: ABAP Import Phase DDL Statement Error

Frank-Martin — Mon, 25 Aug 2014 09:23:15 GMT

Does the MODSAP table exist in the source system?

If yes, is the table contained in any of the R3load STR or TSK files?

If yes, please provide the corresponding R3load log file.

SAP support will ask for the same data anyways.

Regards

Frank

Re: ABAP Import Phase DDL Statement Error

Former Member — Mon, 25 Aug 2014 09:51:44 GMT

Hi Frank,

The MODSAP does not exist in the DB.

And I have checked all the R3Load LOG and TSK files, nowhere MODSAP was mentioned.

Ayan

Re: ABAP Import Phase DDL Statement Error

Frank-Martin — Mon, 25 Aug 2014 10:44:42 GMT

Ok. In this case the APPL_MODS view does also not exist in the source database. The DDIC meta data for the view definition may still exist in the source database for whatever reason. This may be the reason why R3load exported the meta data and now tries to create it.

Since the view does not exist in the source database, I suggest to continue with your system copy and ignore this error.

Regards

Frank

Re: ABAP Import Phase DDL Statement Error

Former Member — Mon, 25 Aug 2014 10:54:24 GMT

Hi Frank,

I'm doing a fresh installation, and not a system copy.

Anyways, I have reverted the installation process and now doing the installation from scratch, I'll get back to this thread in case the same error persists, which I guess will be encountered again.

Ayan

Re: ABAP Import Phase DDL Statement Error

Former Member — Mon, 25 Aug 2014 14:51:24 GMT

Hi sir,

could you please tell me how to get user name and password for login to the link you have given..

A pop up is displayed saying authentication required.

http://service.sap.com/sap/support/notes/1837199

Re: ABAP Import Phase DDL Statement Error

Former Member — Tue, 26 Aug 2014 06:40:30 GMT

Hi All,

I have solved the issue.

There has been some problem in the server due to which some of the tables were not created successfully.

Therefore, I reverted the installation process and performed a fresh installation and thus the issue got resolved.

If the same problem is faced by anyone else then you can follow these steps:

1. Take a restart of the DB.

2. Try to execute the DDL statement manually from the DB level.

3. Check for the tables from the DB level if they are created or not.

4. Check for the R3Load.LOG and TSK, if any other errors exist.

5. If none of the above work out, then you can perform a fresh installation or else raise an incident to SAP and let them find the solution for you.

Hope you will get the results.

Thanks everyone for their valuable time and feedback.

Regards,

Ayan