cancel
Showing results for 
Search instead for 
Did you mean: 

Error in phase MAIN_SHDCRE/DBCLONE - EHP Installer

joo_migueldimas
Active Participant
0 Kudos

Hello,

I´m faccing with an error in upgrade system to EHP4 (SPS6) with EHP Installer (EHPi) at phase MAIN_SHDCRE/DBCLONE. After running one day in this same phase the wizard of EHPi stops and display the following message:

SEVERE ERROR: Batch jobs (DBCLONE1) may still be running:
              See transaction SM37 for details, check SM21
Severe error(s) occured in phase MAIN_SHDCRE/DBCLONE!
Last error code set: Single errors (code <= 😎 found in logfile 'DBCLONE.ELG'

I checked some log files such as the following (SAPehpi.log | DBCLONE.LOG | DBCLONE.ELG):

-- SAPehpi.log --

CURRENTPHASE MAIN_SHDCRE/DBCLONE
...started at 20100623143411
# Using phase log file 'DBCLONE.LOG'.
...begin dialogue at 20100624071651
...end dialogue at 20100624092753
# Error message set: 'Single errors (code <= 😎 found in logfile 'DBCLONE.ELG''
...begin dialogue at 20100624092754

-- DBCLONE.LOG --

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/24 07:16:19: sleeping 30 seconds
4 ETQ010 Date & Time: 20100624071649  
4 ETQ230 Starting RFC Login to: System = "QAS", GwHost = "SAPQAS", GwService = "sapgw00"
4 ETQ359 RFC Login to: System="QAS", Nr="00", GwHost="SAPQAS", 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
2EETQ262 Batchjob "DBCLONE3" aborted
3 ETQ399 log analyse: search for '^.[^WT ]' in 'DBCLONE*.QAS'

-- DBCLONE.ELG --

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CLONING ERRORS and RETURN CODE in DBCLONE01.QAS
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1EETG011 "DYNPSOURCE"

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CLONING ERRORS and RETURN CODE in DBCLONE02.QAS
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1EETG011 "DOKCLU"

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CLONING ERRORS and RETURN CODE in DBCLONE03.QAS
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1EETG011 "FUPARAREF"
1EETG011 "IACMU_C"
1EETG011 "IACR_C"
1EETG011 "IACS"

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CLONING ERRORS and RETURN CODE in DBCLONE04.QAS
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CLONING ERRORS and RETURN CODE in DBCLONE05.QAS
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CLONING ERRORS and RETURN CODE in DBCLONE06.QAS
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1EETG011 "HRT1212"
1EETG011 "KWTIDXSTA"
1EETG011 "LAW_TIME"
1EETG011 "LAW_UTYPES"
1EETG011 "LCA02_BTC"

...

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CLONING ERRORS and RETURN CODE in DBCLONE01.QAS
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1EETG011 "DYNPSOURCE"

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CLONING ERRORS and RETURN CODE in DBCLONE02.QAS
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1EETG011 "REPOSRC"

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CLONING ERRORS and RETURN CODE in DBCLONE03.QAS
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1EETG011 "SFDG"
1EETG011 "SIDL_TEST_DATA"
1EETG011 "SLIN_DESC"

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CLONING ERRORS and RETURN CODE in DBCLONE04.QAS
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CLONING ERRORS and RETURN CODE in DBCLONE05.QAS
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CLONING ERRORS and RETURN CODE in DBCLONE06.QAS
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Can you help me please to solve this problem..?!

Best regards,

João Dimas - Portugal

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi everyone,

I'm installing SAP EHP4 and the EHPI is on MAIN_SHDCRE/SUBMOD_SHDDBCLONE/DBCLONE since ten or eleven hours ago, I've never installed this EHP and I want to know if it's normal to take several hours?

I know you have installed EHP succesfully, cauld you replay this question?

Thanks.

This is a part of the DBCLONE.log

2 ETQ399 2010/12/14 11:28:21: sleeping 30 seconds

4 ETQ010 Date & Time: 20101214112851

4 ETQ230 Starting RFC Login to: System = "GEQ", GwHost = "SVRGISAPQS", GwService = "sapgw00"

4 ETQ359 RFC Login to: System="GEQ", Nr="00", GwHost="SVRGISAPQS", 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 "DBCLONE2" still running

4 ETQ010 Date & Time: 20101214112851

4 ETQ230 Starting RFC Login to: System = "GEQ", GwHost = "SVRGISAPQS", GwService = "sapgw00"

4 ETQ359 RFC Login to: System="GEQ", Nr="00", GwHost="SVRGISAPQS", 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/12/14 11:28:51: sleeping 30 seconds

4 ETQ010 Date & Time: 20101214112921

4 ETQ230 Starting RFC Login to: System = "GEQ", GwHost = "SVRGISAPQS", GwService = "sapgw00"

4 ETQ359 RFC Login to: System="GEQ", Nr="00", GwHost="SVRGISAPQS", 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 "DBCLONE2" still running

4 ETQ010 Date & Time: 20101214112921

4 ETQ230 Starting RFC Login to: System = "GEQ", GwHost = "SVRGISAPQS", GwService = "sapgw00"

4 ETQ359 RFC Login to: System="GEQ", Nr="00", GwHost="SVRGISAPQS", 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/12/14 11:29:21: sleeping 30 seconds

joo_migueldimas
Active Participant
0 Kudos

Hello Oved Cervantes,

Sorry... I didn´t see your message here, when threads are closed we don´t receive the email alert!!

So... you are with the same problem... and you don´t know how to solve that... first I will assume that you are in phase roadmap -- Preprocessing -- in phase MAIN_SHDCRE/SUBMOD_SHDDBCLONE/DBCLONE... in this phase there is a lot of commits on database and although you put the SIMPLE option in recovery mode of your SQL Server DB, in this particulary phase the LOGFILE increases a lot!

First, if you didn´t put the recovery mode to SIMPLE option (on upgrade preparation) and if you still use the FULL option, you have to change that to SIMPLE!! Second thing is, you have to create another Logfile in other device/disk... file system...whatever... that it have volume space to increase (20 - 30Gb depends of database size)!! This two actions, you can do both in at SQL Server Management Studio, go there with your adm user, and go to properties of your database instance = SID !!

Attention: If EHP Installer it is still running, first you have to stop it!! Go to SM37 and search the job DBCLONE*, cancel all that jobs (I think there are six jobs (DBCLONE1; DBCLONE2 ; ...; etc). After this your EHPI stops, and from this point, you can do everything that I mentioned above...

I hope this help you.

Best regards,

João Dimas - Portugal

gurpreet
Explorer
0 Kudos

Thanks João.  Your explanation helped me with stuck phase of MAIN_SHDCRE/SUBMOD_SHDDBCLONE/DBCLONE when archive log filled up.  Checking and resetting status of these jobs triggered activity and progress.

Cheers

Gurpreet

jorge_velasquez
Contributor
0 Kudos

Hi,

I have the same error.

Recovery mode SIMPLE!

I added space to LOG and still got this error.

Please help

Former Member
0 Kudos

Use at your own risk in Dev or QAS system, set TF to 610 Global and restart from the point it fails, with db in simple or bulk logged mode, this tf reduces or almost NO logging, I used this trick to get past that error.
I will not do it in production.

former_member227283
Active Contributor
0 Kudos

Hi,

check the log file DBCLONE01.QAS and paste the error content in forum.

Thanks

Anil

joo_migueldimas
Active Participant
0 Kudos

Hi Anil,

Ok, here you have it, the last lines of that file - DBCLONE01.QAS :

...

3 ETG011 "START WDY_WB_VD_ADD_F -> WDY_WB_VD_ADD_F~"
3 ETG011 "WDY_WB_VD_ADD_F~ : primary key according to ddic"
3 ETG011 "WDY_WB_VD_ADD_F has 30 rows."
3 ETG011 "WDY_WB_VD_ADD_F DONE""0"
3 ETG011 "START WDY_WINDOW -> WDY_WINDOW~"
3 ETG011 "WDY_WINDOW~ : primary key according to ddic"
3 ETG011 "WDY_WINDOW has 8 rows."
3 ETG011 "WDY_WINDOW DONE""0"
3 ETG011 "START WSHEADER_DARK -> WSHEADER_DARK~"
3 ETG011 "WSHEADER_DARK~ : primary key according to ddic"
3 ETG011 "WSHEADER_DARK has 9 rows."
3 ETG011 "WSHEADER_DARK DONE""1"
3 ETG011 "START WSRMB_ID_MAPPING -> WSRMB_ID_MAPPING~"
3 ETG011 "WSRMB_ID_MAPPING~ : primary key according to ddic"
3 ETG011 "WSRMB_ID_MAPPING has 0 rows."
3 ETG011 "WSRMB_ID_MAPPING : only client 000"
3 ETG011 "WSRMB_ID_MAPPING DONE""0"
3 ETG011 "START WSRMB_SEQ_IA3_P -> WSRMB_SEQ_IA3_P~"
3 ETG011 "WSRMB_SEQ_IA3_P~ : primary key according to ddic"
3 ETG011 "WSRMB_SEQ_IA3_P has 0 rows."
3 ETG011 "WSRMB_SEQ_IA3_P : only client 000"
3 ETG011 "WSRMB_SEQ_IA3_P DONE""0"
9 ETG011 "CLONING TABLES FAILED"
3 ETG011 "************(212610)************"
3 ETG011 "************(163412)************"
8 ETG011 "START CLONING TABLES"
3 ETG011 "Cannot read G:\usr\sap\QAS\EHPI\abap\mem\TAIATRANS"
3 ETG011 ".DAT"
3 ETG011 "START DYNPSOURCE -> DYNPSOURCE~"
3 ETG011 "DYNPSOURCE~ : primary key according to ddic"
3 ETG011 "DYNPSOURCE has 179325 rows."
3 ETG011 "[Microsoft][SQL Server Native Client 10.0][SQL Ser"
3 ETG011 "ver]The transaction log for database 'QAS' is full"
3 ETG011 ". To find out why space in the log cannot be reuse"
3 ETG011 "d, see the log_reuse_wait_desc column in sys.datab"
3 ETG011 "ases"
1EETG011 "DYNPSOURCE"
3 ETG011 " "
9 ETG011 "CLONING TABLES FAILED"
3 ETG011 "************(170618)************"
4 EPU202XEND OF SECTION BEING ANALYZED

But I'm not sure if the problem comes from there because another person (SAP administrator) did this upgrade in DEV (development system) about two weeks ago and now I check the DBCLONE.ELG file from that server and as I see in there this next error was shown

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CLONING ERRORS and RETURN CODE in DBCLONE01.QAS
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1EETG011 "DYNPSOURCE"

Thank you,

Best regards,

Jou00E3o Dimas - Portugal

former_member227283
Active Contributor
0 Kudos

Hi,

3 ETG011 "[Microsoft][SQL Server Native Client 10.0][SQL Ser"
3 ETG011 "ver]The transaction log for database 'QAS' is full"
3 ETG011 ". To find out why space in the log cannot be reuse"

Log says what is a exact problem.

Increase the size of transcation log file and retry the steps of EHP.

Thanks

Anil

RajeevP
Advisor
Advisor
0 Kudos

Hi,

As the log says, the issue lies with the transaction log.

1. Check that the transaction log is set to autogrow and there is no limit

2. Check that the drive where the transaction log file is kept has plenty of space

3. Alternativelly, clear the transaction log if it is very large.

Rajeev

joo_migueldimas
Active Participant
0 Kudos

Hello Anil,

Yeah you´re right... DAMN!! I could even swear that I already checked this value in past... I don´t know how I didn´t noticed this!!!

But tell me one thing, this is weird because, before I start this upgrade, I put the SQL DB in Simple mode in recovery model option and it still have it! So... tell me, it´s possible to delete it whenever I see the logs increasing ?

Thank you,

João Dimas - Portugal

former_member227283
Active Contributor
0 Kudos

Hi,

Its better , increase the log file manually or add addtional log file.

Once your EHP activity get completed, you can shrink the log file.

Thanks

Anil

joo_migueldimas
Active Participant
0 Kudos

Hello Rajeev P,

1. Yes the autogrow is set and there is no limit.

3. I did a shrink to that TLog, but after a few minutes the TLog increase again and the wizard of SAP EPHi stops again!!

So I guess the alternative way is to create other TLog file in other drive (because it doesn´t have space). I will apply other TLog file but tell me one thing, for this action I must stop the sap system and the SAP EHP Installer will also stop, isn´t it?

Best regards,

João Dimas - Portugal

former_member227283
Active Contributor
0 Kudos

Hi,

No need to stop SAP or EHPI , you can add the new log file on the file.

Thanks

Anil

joo_migueldimas
Active Participant
0 Kudos

Hello,

Yeah... you are right! The problem was in Transaction Logs that increased and the drive had no space!

Solution: I create another Transaction Log in other drive (Via Management Studio at SLQ Server 2008) and the problem was solve!

Thank you for your help!

Best regards,

Joao Dimas - Portugal