My Oracle Support Banner

Tips on Cloning, Installing, Upgrading a Demantra Schema/Database (ex. refreshing the DEV environment with PRD data or new install) (Doc ID 856857.1)

Last updated on JUNE 21, 2023

Applies to:

Oracle Demantra Demand Management - Version and later
Information in this document applies to any platform.


The purpose of this document is to describe how to create a DEV environment that matches your PRD environment as closely as possible.

This document is meant to cover just the core Demantra Database/Schema and does not take into account integration feeds into or out of Demantra to or from other systems (including but not just out of the box EBS integration) and how those might need to change to point to the DEV environment.  

Note that while traditionally a DEV environment is included within the base license cost that this document does not imply explicit approval of these new environment and any questions about licensing should be directed to your Account Manager


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
 Tips when Importing the Schema
 After doing this new import, the following objects need to be changed so that it does not continue to reflect the PRD environment. 
 SQL*Net, TNSName and ServerName
 V7.3 and above considerations (including how to change the Demantra Schema password)
 The Schema Password (Database.Password) field is now encrypted in v7.3 so how can I give a new password?
 If you are starting with a new environment
 Are there any options for only copying over certain objects like Worksheets, Workflow Schemas, etc. without cloning the entire database?

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.