ABAP Import Phase DDL Statement Error

[Former Member]

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

[former_member182657]

Hi,

Could you check for SCN thread

Regards,
Gaurav

[Former Member]

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

[Former Member]

HI,

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

Ayan

[Frank-Martin]

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

[Former Member]

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

[Former Member]

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

[Former Member]

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

[Former Member]

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

[Frank-Martin]

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

[Former Member]

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

[Frank-Martin]

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

[Former Member]

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