cancel
Showing results for 
Search instead for 
Did you mean: 

Error during Export in SQL2008

Former Member
0 Kudos

Hi All,

During Export of SQL 2008 we are getting error as Program Migration Monitor Exits with error code 103

Checked the Export Log

Unloading of 'SAPAPPL1_1' export package: ERROR

Unloading of 'SAPAPPL1_3' export package: ERROR

Kindly find the attachment of the screen shot of the error,SAPAPPL1_1 and  SAPAPPL1_3 log file.

Looking for the Solution

Thanks and Regards,

Mathan A

Accepted Solutions (1)

Accepted Solutions (1)

former_member218805
Participant
0 Kudos

Hi Mathan,

From the error:

(EXP) ERROR: DbSlPrepare/BegRead failed

  rc = 103, table "/1CPMB/DU4P2XMAS"

  (SQL error 208)

  error message returned by DbSl:

Invalid object name '/1CPMB/DU4P2XMAS'.

(DB) INFO: disconnected from DB

It seems R3load tried to export the table '/1CPMB/DU4P2XMAS' from the database, but it was not able to find it. Could you please check whether ti exists at DB level?

If not, this means there is an inconsistency between the ABAP dictionary and DB. To fix that, you can re-create this table in transaction SE14 and restart the export.

Best Regards,

Alessandro Parolin

Former Member
0 Kudos

Hi Alessandro,

As Checked this table was not there. Created the Table using SE14.

Restarted the Export.

Getting similar error but different table name

Created that table also and restarted the export.

Now I have a few questions

1.Is it required to activate and adjust the table which we create using SE14.?

2. Can we check the inconsistency between ABAP Dictionary and DB is that possible?

Thanks and Regards,

Mathan A

former_member184473
Active Contributor
0 Kudos

Hello Mathan,

You can check the missing tables in transaction DBACockpit:

DBACockpit -> Diagnostics -> Missing Tables and Indexes

Regards,

Eduardo

Reagan
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello

1.Is it required to activate and adjust the table which we create using SE14.?

Yes. It is required

2. Can we check the inconsistency between ABAP Dictionary and DB is that possible?

http://help.sap.com/saphelp_nwpi711/helpdata/en/33/5b277b8b0745b8b60e67ca04c77ebb/content.htm

Regards

RB

Answers (5)

Answers (5)

former_member184473
Active Contributor
0 Kudos

Hello Mathan,

Which SWPM version are you using during this export?

Regards,

Eduardo Rezende

Former Member
0 Kudos

Hi Eduardo,

Using the latest version of SWPM 70SWPM10SP03_1-20009707.sar released on 17.07.2013

Thanks and Regards,

Mathan A

Sriram2009
Active Contributor
0 Kudos

Hi Mathan

Are you planning to do the system copy Homogeneous or Heterogeneous?

Thanks

Sriram

Former Member
0 Kudos

Hi Sri,

   Heterogeneous System Copy

Thanks and Regards,

Mathan A

Sriram2009
Active Contributor
0 Kudos

Hi

Kindly go thru the SAP Note and also did you execute the SMIGR_CREATE_DDL before system export?

Note 1814306 - R3load/MaxDB unsorted export (index all columns of table)

Could you share SAP system kernel and stack details?

Thanks

Sriram

Former Member
0 Kudos

Hi ,

Downloaded and used the latest DBSL patch.

The kernel is already Upgraded to the latest patch.

Still getting the same error

Any other solution is welcome

Thanks and Regards,

Mathan A

former_member185239
Active Contributor
0 Kudos

Hi Mathan,

Can you please paste the logs for export_import.java.log and export_monitor.log

With Regards

Ashutosh Chaturvedi

Former Member
0 Kudos

Hi Ashutosh,

Kindly find the attachment of the log files you have asked for.

Thanks and Regards,

Mathan A

former_member185239
Active Contributor
0 Kudos

Hi Mathan,

you need to apply the latest dbsl patches for MSS.

Note 1118628 - Connection check on SQL208 (dbobject unknown)

The below note is not applicable to your environment but you will manage to get clear idea about the issue.

Note 1642058 - Adapt SAPInst Oracle Client 11.2.0.x

With Regards

Ashutosh Chaturvedi

Sriram2009
Active Contributor
0 Kudos

Hi Ayyappan

Update the Latest kernel & DBSL patch and then repeat the same

Thanks

Sriram

AtulKumarJain
Active Contributor
0 Kudos

Hi,

Please check

SAP  Note 846672

Br

Atul

Former Member
0 Kudos

Hi Atul,

    Already Tried that note 846672.Still getting same error.

Thanks and Regards,

Mathan A