Thank you for supporting the Cloud Customer Connect Community in 2024. It's a gift to work with you!

Look back
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 with Redwood for Oracle Cloud HCM   Begin Now
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.

For more information, please refer to this announcement explaining best practices for getting answers to questions.

Refreshing our staging environment

Summary:

Refreshing our staging environment

Content (please ensure you mask any confidential information):

A couple years ago we had a staging environment (NVRINC_STG) spawned as a copy of our Production environment (NVRINC). We'd like to know what it would entail to "refresh" that STG environment from Production. To be clear, we DO NOT want to necessarily do it, we're just exploring the option to understand the time and effort involved. Is there any way to specify what parts/areas of the environment are refreshed/overwritten?

Version (include the version you are using, if applicable):

TBE

Code Snippet (add any code snippets that support your topic, if applicable):

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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