cancel
Showing results for 
Search instead for 
Did you mean: 

Problem with ECC 5.0 Upgrade in JOB_RASUVAR1 phase of PREPARE

Former Member
0 Kudos

I am upgrading 4.6B system (copy of production to build QA system) on Tru64 with 3TB Oracle DB. The JOB_RASUVAR1 phase of PREPARE in running for about 115 hours. This phase saves existing variants for future conversion. There is a job running at the SAP level which using a lot of CPU, but no active Oracle session for this job. The same job took less than an hour on development system (200GB DB). So far the response from SAP has been like "Unfortunatly there is no possibility to improve the performance of the reports RASUVAR1 and RASUVAR2 during the upgrade" because this phase does not happen during production downtime.

Did anyone else face similar problem?

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Kausik,

we recently upgrade our client systems from 4.6c to ECC 5.0, on unix environment. we too faced similar kind of problem, our job_rasuvar1 in prepare phase took almost 70hrs. after raising a msg with SAP, we were asked some correction in function module.."FASU_RS_VARIANT_CONTENTS"..check whether the following changes are already available..or not

<b>the necessary change:</b>

replace the line

PERFORM fill_tables_ps TABLES objects

with the line

PERFORM fill_tables_ps(saplsvar) TABLES objects "CHANGE

in function module FASU_RS_VARIANT_CONTENTS

2) To fix this issue I would recomment, that you stop the JOB_RASUVAR1.

Then please implement the corrections of note 712297. After this please

clear out all the entries in DB tables TASUVCAT, TASUVSVO and TASUVSVD.

You can do thie for example via transaction SE14.

Then implement the following modification to ABAP RASUVAR1:

...

FORM return_content USING taskname.

RECEIVE RESULTS FROM FUNCTION 'FASU_V_VARIANT_CONTENTS'

TABLES

valutab = gt_params

OBJECTS = gt_objects

EXCEPTIONS

syst_except = 1

communication_failure = 2

system_failure = 3

variant_non_existent = 4

variant_obsolete = 5

error = 6.

g_error = sy-subrc.

g_returned = 'X'.

data: l_count type i. "INSERT MOD

describe table gt_params lines l_count. "INSERT MOD

if l_count gt 20000. "INSERT MOD

g_error = 7. "INSERT MOD

endif. "INSERT MOD

ENDFORM. " return_content

...

After this you can restart the JOB_RASUVAR1 by just call report

please try with this & let me know. and 1 more thing, this phase again depends on database size (in our case, for 1.8TB it took 6hrs).

with regards,

Raj