cancel
Showing results for 
Search instead for 
Did you mean: 

SMIGR_CREATE_DDL Long runtime

rahulrdeo
Explorer
0 Kudos

Hi All

We are performing a CU&UC project. Requirement is to create a copy of PRD perform upgrade and pre-unicode task then create a new client with SAP_UCUS profile from the source main client. Delete the source client and then export the data and import it in target system, so that this new target system could be used as new Development system.

We have deleted the client and now as a pre migration step we have executed SMIG_CREATE_DDL which has already passed more than 40 hours of execution time and still running, though before client deletion same process was completed in an hour.

We could see that the SMIGR_CREATE_DDL is stuck on user_indexes table. I could not find any specific SAP note mentioning it as a known issue for SAP_BASIS 731 PL14.

I am not sure if due to client deletion the user_indexes table is impacted and since we have not performed any DB re-org that might be the cause. Please do let me know if someone has faced the similar issue and what was the resolution.

Regards

Rahul

Accepted Solutions (0)

Answers (3)

Answers (3)

former_member182657
Active Contributor
0 Kudos

Hi Rahul,

As you've already on the latest kernel with updated database stats,if possible could you share system logs from SM21.

Regards,

former_member188883
Active Contributor
0 Kudos

Hi Rahul,

Could you try updating the latest kernel file as well as updating DB statistics.

Regards,

Deepak Kori

rahulrdeo
Explorer
0 Kudos

Hi Deepak

We have latest kernel and we have also gathered all relevant statistics before executing SMIGR. Also with same kernel earlier (before client deletion) the SMIGR report ran fine.

Regards

Rahul

stefan_koehler
Active Contributor
0 Kudos

Hi Rahul,

> We could see that the SMIGR_CREATE_DDL is stuck on user_indexes table. I am not sure if due to client deletion the user_indexes table is impacted ...

No, a SAP client removal has no impact on user_indexes as the database objects remain the same. If your query is running on user_indexes since round about 40 hours or so, i would assume an execution plan issue. You can verify this by using SQLd360 on the particular SQL ID.

However just as a wild guess (and no systematic troubleshooting approach at all). Have you gathered Oracle DDIC statistics at some time?

Regards

Stefan

rahulrdeo
Explorer
0 Kudos

Hi Stefan

Thanks for the reply...Yes we have gathered the Oracle DDIC statistics just before executing SMIGR report.

Will try the sql script you have shared.

Thanks

Rahul