cancel
Showing results for 
Search instead for 
Did you mean: 

MAIN_SHDCRE/DBCLONE is taking too much of space in log file

Former Member
0 Kudos

hello sir

on EHP 4 installation

MAIN_SHDCRE/DBCLONE is taking too much of space in log file,

i have assigned 20 gb to <SID>log1.ldf ,

and it was full twice and the process was stoped at MAIN_SHDCRE/DBCLONE phase

pls tell me what to do i have MSSQL 2005 on windows 2003 enterprice.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

hello

i was stuck on MAIN_SHDCRE/DBCLONE phase from last 5 hr .

1 hr before the log file and database files r increasing but now there is noo movement ,

but in DBCLONE.log file it was still showing that it is working in present time.

"

4 ETQ010 Date & Time: 20100630134140

4 ETQ230 Starting RFC Login to: System = "DVA", GwHost = "one", GwService = "sapgw00"

4 ETQ359 RFC Login to: System="DVA", Nr="00", GwHost="one", GwService="sapgw00"

4 ETQ232 RFC Login succeeded

4 ETQ233 Calling function module "SUBST_CHECK_BATCHJOB" by RFC

4 ETQ234 Call of function module "SUBST_CHECK_BATCHJOB" by RFC succeeded

4 ETQ239 Logging off from SAP system

4 ETQ264 Batchjob "DBCLONE3" still running

2 ETQ399 2010/06/30 13:41:40: sleeping 30 seconds"

markus_doehr2
Active Contributor
0 Kudos

> i was stuck on MAIN_SHDCRE/DBCLONE phase from last 5 hr .

> 1 hr before the log file and database files r increasing but now there is noo movement ,

> but in DBCLONE.log file it was still showing that it is working in present time.

This is not uncommom - depending on the size of your source system.

You can check in the main instance in SM50/SM66 if there are still jobs of user DDIC running or in SM37.

Markus

Former Member
0 Kudos

should i reset the installation , but is there any other solution for this problem

markus_doehr2
Active Contributor
0 Kudos

Please check the jobs of user DDIC in SM37.

Markus

Former Member
0 Kudos

in sm37 the jobs of DDIC

dbclone3 is active

n all other are finished

like dbclone1, dbclone2 n so on

what to do wait or some thingelse

markus_doehr2
Active Contributor
0 Kudos

> in sm37 the jobs of DDIC

> dbclone3 is active

select it and select "check status" in the menu.

Markus

Former Member
0 Kudos

now it shows status canceled

markus_doehr2
Active Contributor
0 Kudos

And what is your upgrade saying?

Markus

Former Member
0 Kudos

SEVERE ERROR: Batch jobs (DBCLONE1) may still be running:

See transaction SM37 for details, check SM21

markus_doehr2
Active Contributor
0 Kudos

> SEVERE ERROR: Batch jobs (DBCLONE1) may still be running:

> See transaction SM37 for details, check SM21

So the upgrade noticed the phase was cancelled, good.

Now you need to provide more disk space for the log area of the database and then repeat the phase.

Markus

Former Member
0 Kudos

now my other log file is started working

thanks bro

can u tell me how to empty these log files i have MSSQL 2005

Former Member
0 Kudos

friend

the drive where the first log file was it shows low disk space again but the second log file is increasing rapidly like 1 gb in 5 to 10 min.

second log file has near about 100 gb free space.;

markus_doehr2
Active Contributor
0 Kudos

That's fine. You just must not run out of log space, then everything will run through.

Markus

Former Member
0 Kudos

thank u

i will see through the rest of the installation phase.

Answers (2)

Answers (2)

Former Member
0 Kudos

i have checked the SM50 no job beside one dialog process , Sm66 nothing is there, Sm37 no job is there.

markus_doehr2
Active Contributor
0 Kudos

There's not much you can do about that. Since you don't want to risk a data loss in your still running production you can't switch the logmode.

I would temporarily create a new logfile on a location where you have space and remove that logfile after the upgrade is finished.

Markus