cancel
Showing results for 
Search instead for 
Did you mean: 

Issue with SUM tool in pre-processing phase:

Former Member
0 Kudos

Dear Experts,

We are in the process of upgrading ECC system from SP11 to SP23 using SUM tool. We were in the middle of Pre-processing stage, but the process got hanged and when we try to restart it using STARTUP.BAT file of SUM tool DSU services is not starting. When i click STARTUP.BAT , starting DSUI screen will popup and it will terminate in few seconds.Please find the attached screen shot and jump.trace file for your reference and kindly help us to resolve this issue as soon.

Regards,

SURYA

View Entire Topic
Former Member
0 Kudos

Hi,

This has been done already as we have a backup of SUM and we restored those two files from the backup earlier which works fine now.But now we are facing a different error. DB clone jobs are getting failed because of the spool error as shown below

Kindly help me how to resolve the issue...

Regards,

SURYA

Reagan
Product and Topic Expert
Product and Topic Expert
0 Kudos

Delete all obsolete spool requests.

Run a spool consistency check and delete the entries.

Regards

RB

Former Member
0 Kudos

Perform SP12 -> TemSe database -> consisyency check.

Sriram2009
Active Contributor
0 Kudos

Hi Surya

Since you are system having SAP ECC6 Support package level 11. I thing SUM will not support on your version. its require minimum SP level should be on 14 onwards, kindly refer the SUM tool reference pdf file (Required Suser id)

https://websmp206.sap-ag.de/~sapidb/011000358700000783572011E

Regards

Sriram

sivakumar_kilari3
Active Contributor
0 Kudos

Hi Surya,

Can you check sm21 logs or sm37 job logs.

Thanks

Siva

Former Member
0 Kudos

Hi Siva,

Thanks for the reply. I checked the SM21 logs it's stating that Transaction log is full and the jobs are getting cancelled. We are Using DB2 Database.

Regards,

SURYA

sivakumar_kilari3
Active Contributor
0 Kudos

Hi Surya,

Increase the online log file size and number of online logs.

Thanks

Siva

Former Member
0 Kudos

Hi,

Thanks for the reply. Issue has resolved after increasing the log file size and number of primary log files.

Regards,

SURYA