Making Custom Top Work After Upgrade from R12.1.1 to R12.2.6

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Making Custom Top Work After Upgrade from R12.1.1 to R12.2.6

vkkgooner
Hello Erman,

We have successfully upgrade our ebs application from R12.1.1 to R12.2.6
Now, we have 1 custom application which obviously not working after upgradation.

So, I have some doubts which hopefully I am able to ask appropriately.

Currently, I am following document 1577707.1 for the purpose of
a) Registering my custom application on recently upgraded system which is R12.2.6
--> For this I will run adsplice after downloading patch 3636980

Now, my doubt!

In total we have 1645 custom objects under our custom schema named XXCU.
Obviously metadata of all those objects, showing that they are created under custom tablespace named XXCU.

Now, in R12.2.6, custom objects should reside under tablespaces named APPS_TS_TX_DATA and APPS_TS_TX_IDX.

So, do we need to drop the custom schema and all objects which has created under it?
If yes, we will need to get metadata of all those objects and recreate again?


Reply | Threaded
Open this post in threaded view
|

Re: Making Custom Top Work After Upgrade from R12.1.1 to R12.2.6

ErmanArslansOracleBlog
Administrator
Read the following note, carefully:

12.2 adsplice Ignores Custom Tablespaces For New Custom Application Configuration and Only Uses OATM Tablespaces (Doc ID 1987906.1)

Don't bother the name of the document, it gives you the details about the things that your are asking..
Reply | Threaded
Open this post in threaded view
|

Re: Making Custom Top Work After Upgrade from R12.1.1 to R12.2.6

vkkgooner
Hi Erman,

It was lovely on your part to reply and help. The metalink notes turned out to be very useful. Thanks.