cancel
Showing results for 
Search instead for 
Did you mean: 

Program 'Migration Monitor' exits with error code 103

Former Member
0 Kudos

      An error occurred while processing option SAP Business Suite 7i 2013 Support Release 2 > EHP7 for SAP ERP 6.0 ABAP Support Release 2 > SAP ASE > SAP Systems > Application Server ABAP > Standard System > Standard System( Last error reported by the step: Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.).

Hi,

   I'm installing EHP7 for SAP ERP 6.0-IDES system in 2012 R2 windows server. while installing i am getting this error in IMPORT ABAP phase. Please help me on this.

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi All,

   Can you please mention the commands clearly.

Regard's

Trinath.

Sriram2009
Active Contributor
0 Kudos

Hi Trinath


During the SAP installation process your database transaction log is full(There no free space available to write a log)

1. you have to stop the installation

2. From the DB either clear the log or increase the log space.

3. Continue the installation where it stopped.

BR

SS

Former Member
0 Kudos

Hi Sriram ,

   How to increase the log space. Please forward the commands .

Regard's,

Trinath.

former_member182034
Active Contributor
0 Kudos

Dear,

Check the link which i shared with you.

Regards,

Former Member
0 Kudos

Hi ,

  The below command is not working for me .

dump transaction SID using config = 'SIDLOG'


Regard's

Trinath.

former_member182034
Active Contributor
0 Kudos

dear,

change the command as per your system SID and logs file name and execute.

Regards,

Former Member
0 Kudos

Dear Abdul,

   I have tried same command, But i am not getting anything. Please check the screen shot.

Regard's,

Trinath.

Sriram2009
Active Contributor
0 Kudos

Hi Trinath.

I think you do log is full you may not use the DB to add free space. you have to clear the log refer the link SyBooks Online

BR

SS

former_member182034
Active Contributor
0 Kudos

Dear Trinagh,

FYA....

The 3051 message, "The dump configuration '' supplied for DUMP DATABASE is invalid",can be mistakenly returned for the valid dump configuration which has a 30 bytes long name.


Reference:

https://apps.support.sap.com/sap/support/knowledge/preview/en/2080750


Regards,


former_member212573
Participant
0 Kudos

Hi Trinath,

Please follow the below steps for sybase backup configuration on windows:-

Step 1

Ensure you have the folders created for backup say

E:\backup\db

E:\backup\log

Step 2

Login with sapsso user

1>sp_locklogin 'sa', 'unlock'

2>go

Step 3

Login with sa user

isql64 -Usa -PpAssword@123 -SEH1 -X

Step 4

You are only allowed to create the backup config in master database, the below command will help you create a config to be used for database backup

  1>use master

  2>go

  1>sp_config_dump @config_name = 'EH1DB' ,

  2>@stripe_dir = 'E:\backup\db' ,

  3>@compression = '101' ,

  4>@verify = 'header'

  5>go #watch out for the ','

Step 5

You are only allowed to create the backup config in master database, the below command will help you create a config to be used for transaction backup

  1>sp_config_dump @config_name='EH1LOG' ,

  2>@stripe_dir = 'E:\backup\log' ,

  3>@compression = '101' ,

  4>@verify = 'header'

  5>go

Step 6

   You can set the truncate option to false as below:

  1>sp_dboption IDS,'trunc',false

  2>go

Step 7

After this you will be prompted to execute checkpoint in <SID> database which is done as below:

  1>use EH1

  2>go

  1>checkpoint

  2>go

Step 8

Once you are done with this, you may go back to master database and fire the dump transaction (YOu will have to executre dump database before you can use dump transaction) as shown below:

  1>dump database EH1 using config='EH1SDB'

  2>go

  1>dump transaction EH1 using config='EH1LOG'

  2>go

Regards,

Pankaj

Sriram2009
Active Contributor
0 Kudos

Hi Trinath.

1 .What is the version SWPM with SP level?

2. Have you tired restarting the full system? and then start the same phase?

3, Kindly refer the SAP KBA for analyze migration monitor.

2146357 - How to analyze Migration Monitor issues in SWPM

BR

SS

Former Member
0 Kudos

Hi Sriram,

 

   Thanks for the reply.

1) SWPM SP17.

2) I have done the full system restart and restated the same phase. But i am getting same error.

Regard's,

Trinath.

Former Member
0 Kudos

Hi Trinath,

From the logs you have attached it appears that many packages failed during the import. Can you please share the below logs to analyze further.

SAPUSER1.log

SAPCLUST.log

SAP0000.log

Thanks,

Manas

Former Member
0 Kudos

Hi Manas,

    Here is the enclosed logs what you ask about.

Regard's,

Trinath.

former_member182034
Active Contributor
0 Kudos

Dear,


DbSlExecute: rc = 99

  (SQL error 1105)

  error message returned by DbSl:

[ASE Error SQL1105][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Can't allocate space for object '

You are getting issue due to less space. Please increase space as per this note and link.

1802842 - SYB: Error 1105 and Error 3475 in ASE error log

Regards,


Sriram2009
Active Contributor
0 Kudos

Hi Trinath.

Kindly refer error message clear the transaction log or increase the log space.

Can't allocate space for object 'syscolumns' in database 'EN1' because 'system' segment is full/has no free extents. If you ran out of space in syslogs, dump the transaction log. Otherwise, use ALTER DATABASE to increase the size of the segment.

Regards

SS

Former Member
0 Kudos

Hello Sriram,

    If you have any commands for this please share with me.

Regard's

Trinath