SUM stuck in phase MAIN_SHDCRE/SUBMOD_SHDDBCLONE/DBCLONE

[Former Member]

Hello,

I'm facing a problem with the upgrade of a support package stack in solution manager 7.1 with Windows / Sybase.  I'm upgrading from SPS08 to SPS10 and the upgrade is stuck in the phase MAIN_SHDCRE/SUBMOD_SHDDBCLONE/DBCLONE for about 3 days.  The log DBCLONE.LOG keeps updating almost like once a minute and it shows the following message:

4 ETQ264 Batchjob "DBCLONE2" still running

2 ETQ399 'SUBST_CHECK_BATCHJOB' for JOBNAME='DBCLONE3' JOBCOUNT='15375700' returns 'R'.

4 ETQ264 Batchjob "DBCLONE3" still running

2 ETQ399 2014/02/20 10:06:06: sleeping 30 seconds

2 ETQ399 'SUBST_CHECK_BATCHJOB' for JOBNAME='DBCLONE2' JOBCOUNT='15375700' returns 'R'.

4 ETQ264 Batchjob "DBCLONE2" still running

2 ETQ399 'SUBST_CHECK_BATCHJOB' for JOBNAME='DBCLONE3' JOBCOUNT='15375700' returns 'R'.

4 ETQ264 Batchjob "DBCLONE3" still running

2 ETQ399 2014/02/20 10:06:36: sleeping 30 seconds

2 ETQ399 'SUBST_CHECK_BATCHJOB' for JOBNAME='DBCLONE2' JOBCOUNT='15375700' returns 'R'.

4 ETQ264 Batchjob "DBCLONE2" still running

2 ETQ399 'SUBST_CHECK_BATCHJOB' for JOBNAME='DBCLONE3' JOBCOUNT='15375700' returns 'R'.

4 ETQ264 Batchjob "DBCLONE3" still running

2 ETQ399 2014/02/20 10:07:06: sleeping 30 seconds

I checked the database if there was space missing but everything checks OK with the space.

Any help would be greatly appreciated.

Regards,

Jesus Rodriguez

[Former Member]

Hi all, thanks for your contributions but I finally ended making a restore and restarting the whole process.

Regards,

Jesus Rodriguez

[mamartins]

Hi,

Is your problem solved?

Regards,

MM

[former_member220071]

Hi Jesus ,

Your are using sybase database , please take transaction log backup it may be full that's why you are facing this issue.

Thanks & Regards,

Abhijit Siras

[Reagan]

Hello

This is not an error. The upgrade tool says that the DBCLONE jobs are running in the main system.

Connect to the main system and check the status of the DBCLONE jobs.

Once the DBCLONE jobs have been finished the upgrade tool will move to the next phase.

Regards

RB

[Former Member]

Hi Reagan,

So you say it's normal to be on this phase for over 3 days?  This system is a fresh install so the database has a small size...

Regards,

Jesus Rodriguez

[Reagan]

Connect to the main SAP system and perform a "Check Status" for all the running DBCLONE jobs from Tx SM37.

Check whether they change.

Regards

RB

[Former Member]

I had to go back 3 days to check the DBCLONE jobs and I see that the DBCLONE1 is finished but the 2 and 3 are still active and running. I ran a check status for both and they were OK so this maybe means that I'll have to keep waiting?

Regards,

Jesus Rodriguez

[Reagan]

Hello Jesus

If the jobs are still under execution then you may wait but for sure the duration of 3 days is not acceptable.

I would consider checking the activities at the database level. I am not really sure how Sybase works with the Transaction logs.

If there is no real change in the status of the jobs then I would terminate the WP's and restart them (Last thing to do).

Regards

RB

[Former Member]

Hi Jesus,

During the DBCLONE phase, if you do a quick check in transaction SM66, you will see some background jobs are running. The number of background jobs is determined by the parameter MAX BATCH PROCESSES you set during the configuration or the no of BTC processes configured on the server (whichever lower).

Also, at the same time, it depends on your hardware/system - which sometimes could be the bottleneck.

Thanks,
Henry

[mamartins]

Hi Jesus,

I have experience only on MSSQL, but the symptom your report usually happens when the DB or the Transaction Log are full.

If it's the case, you need to backup the TLOG, then restart the Sybase service and wait until the DB recovers to restart again the SUM.

Regards,

MM

[Former Member]

Hi Manuel,

The process stopped because of this error earlier in the process, I did a backup of the DB and the Logs and then deactivated the logs.

Regards,

Jesus Rodriguez

[mamartins]

Hi Jesus,

Must be something wrong with the DB.

If you have a good DB backup done before you started the SUM, I suggest to kill the SUM, stop the instance and restart the Sybase. After that run a CHECKDB against it to see if nothing is wrong.

Check also if there is enough memory using the task scheduler and see if the used memory reaches the available memory limit. Otherwise increase the pagefile.

Good luck!

MM

[Former Member]

I had exactly the same problem with patching dualstack Solution Manager 7.1 Linux/ Sybase, DBCLONE jobs look to be running fine for 5 hours.

I checked SM37 and I saw there all 3 jobs running in status "active".

But when I checked SM66 I see no batch processes running, so got back to SM37 and selected all 3 jobs and checked status: Jobs -> Check status. After that all 3 jobs got to the status "Cancelled".

Then I scheduled archiving of the DB logs more often and made the phase  DBCLONE in SUM to run again. Everything successfully finished within one hour.