SDBI_CLUSTER_CHECK running for too long time

[Former Member]

We are doing upgrade and unicode conversion of 4.5B MDMP

system. Till now we completed successfully sandbox system, develeopment

system and Quality system upgrade and unicode conversion. In dry run andproduction we are planning to adopt twin upgrade and unicode conversion. During preparation steps of unicode conversion we ran

SDBI_CLUSTER_CHECK for all the 3 system in which sandbox and quality areproduction system copy, the SDBI_cluster_check ran for more than 48 hours

mainly for table CDCLS and RFBLG it took too long time.

Since in production we are planning to do TU&UC and reduced downtime

during weekend how to handle this? do we need to run on production or istat fine that there was no error during cluster check in Quality and

Sandbox (production copy system)? .

kindly suggest.

Regards

Vinay

[nils_buerckel]

Hi Vinay,

please have a look at the TU&UC Guide (attached to SAP note 959698):

Excerpt:

Execute report SDBI_CLUSTER_CHECK in transaction SE38 in your Twin system after the upgrade and before you start SPUMG. On the selection screen choose Execute Cluster Check and press . On the next screen select Program --> Execute in Background from the menu bar. If the overall status of the last check run contains errors, follow the instructions in SAP Note 1348055. You do not need to run the report in the production system as well, but if the check run contains errors in the Twin system, they must be corrected in the Production system, too.

Best regards,

Nils Buerckel

SAP AG

[Former Member]

Hello Nils,

Thanks for our response.

1) I scheduled SDBI_CLUSTER_CHECK in background with several jobs only.

2) For me current Quality system was twin mode system of Dry run and Production. In Quality system there was no error in SDBI_Cluster_check. So i dont have to run SDBI_CLUSTER_CHECK rite?

Regards

Vinay

[nils_buerckel]

Hi Vinay,

as stated in the Guide, it is not necessary to run the report in your PRD system.

Anyhow, in your 4.5B system, this report is not available and to run it after the upgrade would extend the downtime significantly ...

However for customers running on 4.6C or higher(as source system), I would still recommend to schedule this report on PRD before the Unicode conversion.

Best regards,

Nils Buerckel

SAP AG