You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register
Get Started: AI Resources for Oracle Cloud HCM – Go Here

Progress with Redwood: Redwood Resources for Oracle Cloud HCM -  Go Here

Split HCM instance from non HCM instance

Summary:


Split HCM instance from non HCM instance

Content (please ensure you mask any confidential information):

Hi Team,

Greetings!

This question is about the requirement related to splitting existing consolidated cloud instance (pod) into separate instances (pods).

HCM and ERP and non-HCM modules are currently on the same instance (pod).

This leads to performance issues at multiple occasions, especially when the non HCM period closure (or any such activity) coincides with similar high volume activity in HCM Pod.

Have anyone been involved with splitting of existing single Cloud instance into separate instances (pods) for HCM and non-HCM?
What are the key considerations, pro's and cons' and challenges and related activities?

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!