EBS Customizations (MOSC)

MOSC Banner

How can we migrate or deploy the code without having adop cycle in EBS 12.2.5?

edited Dec 8, 2016 9:57PM in EBS Customizations (MOSC) 17 commentsAnswered

The new feature ADOP of EBS 12.2 and above seems very beneficial for applying the patches into Production but it seems that it 's causing the drawback for deployment or migration of code in EBS 12.2. Every single bug fix or deployment of single Oracle forms is going to cause a significant increase in the overall timelines of deployment of such codes. Moreover the cutover phase will cause the downtime of the application to see the changes in the production application , basically on Run file system of EBS 12.2.

Does anybody have any approach to reduce the migration or deployment timelines in such situation by avoiding the execution of adop cycle , like compiling the Oracle forms in both file systems ( RUN and Patch) or using the rsync command to copy the deployed file from patch file system to RUN file system?.. This feature seems pain for using greatest and latest EBS 12.2.5

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center