maintaining 9.2 UDO's when doing a data refresh

nkuebelbeck

nkuebelbeck

VIP Member
Scenerio: User creates UDO grid format in PD, get's shared. User is happy.

neither PY/DV have this object unless we do this. (per oracle)E1: OMWWEB: How to Promote an User Defined Object (UDO) Created in Production (PD) Environment to Development (DV) Environment? (Doc ID 2181973.1)

Ideally we want these to be part of the standard data refresh. So that, say PY, has the same data UDO's as PD.
 
The optimal way to configure this process is to have a process that demotes the UDOs from PD to PY and DV. The demotion process is much easier to manage than a data refresh where you will invariably run into contention with object naming.
 
Any oracle reference for demoting? first i'm hearing of this.

EDIT: found an enhancement request Bug 24691939 : ENHANCEMENT REQUEST - SIMPLIFY THE PROCESS FOR MIGRATING UDOS FROM PD
 
Last edited:
No Oracle doc. We put together a process flow back in 2015, when UDOs were in beta, for this exact scenario. Shoot me an email and I'll send it your way. [email protected]
 
Back
Top