cancel
Showing results for 
Search instead for 
Did you mean: 

Solman upgrade 7.1 error

Former Member
0 Kudos

Hi,

I'm currently running a Solman upgrade from 7.01 to 7.1 on a system running on windows 2008 and SQL server 2008. Yesterday evening the trans. log partition was full so SUM gave me a DB connection error and I stopped the SUM.

I added storage but when I started SUM again gave me this error:

On the SLOG702 this error appears:

### Phase MAIN_NEWBAS/XPRAS_AIMMRG:

### Phase MAIN_NEWBAS/XPRAS_AIMMRG:

### Phase MAIN_NEWBAS/XPRAS_AIMMRG:

START REMOVE STOPMARK      MQS        20160305161026              MQSADM       MTN34HUSBONE 20160305161026002324

STOP  REMOVE STOPMARK      MQS        20160305161026              MQSADM       MTN34HUSBONE 20160305161026002324

START put                  MQS        20160305161027              MQSADM       MTN34HUSBONE 20160305161026004960

START cleanbuffer(sorting) MQS        20160305161027              MQSADM       MTN34HUSBONE 20160305161026004960

STOP  cleanbuffer(sorting) MQS        20160305161027              MQSADM       MTN34HUSBONE 20160305161026004960

START SET STOPMARK         MQS        20160305161027              MQSADM       MTN34HUSBONE 20160305161026004960

INFO: Buffer saved as E:\Software\SUM\abap\buffer\MQSSAV.

STOP  SET STOPMARK         MQS        20160305161027              MQSADM       MTN34HUSBONE 20160305161026004960

LIST  put                  MQS 8nRd

INFO: apg locked (anticipatory program generation)

START MAIN IMPORT          MQS I      20160305161028              MQSADM       MTN34HUSBONE 20160305161026004960

INFO: apg unlocked (anticipatory program generation)

STOP  MAIN IMPORT          MQS I      20160305161028              MQSADM       MTN34HUSBONE 20160305161026004960

START tpbuffreset          MQS 8      20160305161028              MQSADM       MTN34HUSBONE 20160305161026004960

STOP  tpbuffreset          MQS 8      20160305161230              MQSADM       MTN34HUSBONE 20160305161026004960

INFO  TBATG CREATION OF EN MQS n      not needed                  MQSADM       MTN34HUSBONE 20160305161026004960

START tp_getprots          MQS R      20160305161231              MQSADM       MTN34HUSBONE 20160305161026004960

ERROR: System MQS. Error detected  20160305161740 :

WARNING:       Background job is aborted. Function: R  Jobcount: 17220800  Status: A.

      Please check the system. Use transactions SM21, SM37, SM50.

      Check that background job RDDIMPDP is scheduled.

Does anyone know what can be happening?

Thanks a lot, Carolina

Accepted Solutions (0)

Answers (1)

Answers (1)

yakcinar
Active Contributor
0 Kudos

Hello,

You have problem with STMS in you system.

RDDIMPDP cannot be scheduled on your system.

Check BGD wps whether all of them are busy.

Check background jobs using SM37.

You can chekc below link also.

What is RDDIMPDP ..... | SCN

Regards,

Yuksel AKCINAR

Former Member
0 Kudos

Hi,

BGD process are all free , nothing is running on the system and job  RDDIMPDP is scheduled on the system .

I already tried to schedule and execute it again , but no luck. Reg. STMS, we removed the configuration and configure it again , but same error.

Do you have any other idea?

Thanks a lot, Carolina

Sriram2009
Active Contributor
0 Kudos

Hi Carolinas.

1.  You can run the MS Sql truncate log backup to remove the trans log, keep an eye on the log space. and then start the upgrade.

2. Kindly check the background job RDDIMPDP in DDIC user id any job cancelled ?

Regards

SS

Former Member
0 Kudos

Hi,

Could you explain me how truncate the log backup? Do you mean to truncate the transactional log?

RDDIMPDP is being executed properly and there is no job cancelled on the system.

Thanks a lot, Carolina

Sriram2009
Active Contributor
0 Kudos

Hi


Could you explain me how truncate the log backup? Do you mean to truncate the transactional log?

Yes, You can refer the Microsoft link Back Up a Transaction Log (SQL Server)

Regards

SS

Former Member
0 Kudos

Hi,

You mean to delete it,. All the problems started when trans. log partition was full and we had to stop and start everything again (including the DB).

Do you think that removing the trans. log it's going to help to the SUM to re-cover the connection or repeat the step?

thanks a lot, Carolina

Sriram2009
Active Contributor
0 Kudos

Hi

As you said that beginning log partition was full.that is reason to clear the current transaction log and then try again in the same phase. still if your are facing same issue, Kindly update the latest log.

BR

SS