Skip to Content
0

Program 'Migration Monitor' exits with error code 103 MSSQL

Sep 28, 2017 at 07:26 AM

87

avatar image

Hi Gurus,

We are using Solution Manager 7.1 SPS15 with MSQL 2012 & received error "Program 'Migration Monitor' exits with error code 103" when performing System Copy --> MS SQL Server --> Source System Export --> Central System --> Based on AS ABAP and AS JAVA --> Database and Central Instance Export

Please help.

Thanks,
Fadzly Iqbal

sapinst_dev:
https://drive.google.com/file/d/0B62cNgHiqy9INXdzTjNFZkowLTQ/view?usp=sharing

Export Monitor jobs: running 3, waiting 26, completed 12, failed 0, total 41.
Unloading of 'SAPAPPL1_1' export package: ERROR

export_monitor:
https://drive.google.com/file/d/0B62cNgHiqy9IU3JMR3luT1A1bUk/view?usp=sharing

ERROR: 2017-09-28 13:05:04 com.sap.inst.migmon.LoadTask run
Unloading of 'SAPAPPL1_1' export package is interrupted with R3load error.
Process 'E:\usr\sap\SMQ\DVEBMGS00\exe\R3load.exe -e SAPAPPL1_1.cmd -datacodepage 4103 -l SAPAPPL1_1.log -stop_on_error' exited with return code 2.
For mode details see 'SAPAPPL1_1.log' file.

export_monitor.java:
https://drive.google.com/file/d/0B62cNgHiqy9IRk9oZDdwNVVXWVE/view?usp=sharing

Export Monitor jobs: running 3, waiting 26, completed 12, failed 0, total 41.
Unloading of 'SAPAPPL1_1' export package: ERROR

SAPAPPL1_1:
https://drive.google.com/file/d/0B62cNgHiqy9IazlaWkI0MWkyRGs/view?usp=sharing

(EXP) ERROR: DbSlPrepare/BegRead failed
rc = 103, table "/BI0/0600000002"
(SQL error 208)
error message returned by DbSl:
Invalid object name '/BI0/0600000002'.
(DB) INFO: disconnected from DB

riigd.png (260.8 kB)
10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Best Answer
Prithviraj Rajpurohit Sep 28, 2017 at 11:03 AM
0

Hi

Check the sap note

2290203 - System Copy / Export stops because table/object does not exist

Regards,

Prithviraj

Show 2 Share
10 |10000 characters needed characters left characters exceeded
Former Member

I check table "/BI0/0600000002" in SE14.
The short text shows "Temporary SID table" and status is "Does not exist in database".

When I click "create database table", it shows:


Do not edit the object with standard tools

Message no. GT320

Diagnosis

This is an object whose database definition does not have to
agree with the definition in the ABAP/4 Dictionary.
Such objects are entered in exception table DBDIFF.




I still can ignore the warning and create it in DB level.



But, Is it advisable to do that?
Please advise.

Thanks,

Fadzly Iqbal

ijfhs.png (66.5 kB)
ytut1.png (69.3 kB)
0

Hi

Check sap note 33814 - Warnings of inconsistencies between database <=> R/3 DDIC

If temporary BW objects (/BI0/0*, /BIC/0*) are reported as inconsistent, refer to Note 449891 and execute report SAP_UPDATE_DBDIFF. The report SAP_UPDATE_DBDIFF can also eliminate inconsistencies regarding BW objects

Also the right way to activating table is

a) Log on as user DDIC.

b) Call transaction SE14.

c) Enter the name of the table and choose "Edit".

d) In the menu, choose: "Table" -> "Reconstruct".

e) Confirm the execution as an emergency repair.

f) Select the radio button for the processing type as follows: "Direct" or (for very large tables) "Background".

g) Select the "Save data" radio button.

h) Choose "Activate and adjust database" to activate the table.

Regards

Prithviraj.

0