12.2 adsplice Ignores Custom Tablespaces For New Custom Application Configuration and Only Uses OATM Tablespaces
(Doc ID 1987906.1)
Last updated on JUNE 12, 2017
Applies to:Oracle Applications Manager - Version 12.2 and later
Information in this document applies to any platform.
On Oracle Applications 12.2.4:
adsplice is not using custom Application configuration as per supplied parameters in newprods.txt.
adsplice ignores the tablespaces specified in the configuration file - newsprod.txt (XXEBS_DATA and XXEBS_IDX) for default data and default index.
Not only were quotas not granted, the product installations table suggests that custom objects will be placed in other E-Business Suite (EBS) table spaces
APPLICATION_ID ORACLE_ID TABLESPACE INDEX_TABLESPACE
50001 50001 APPS_TS_TX_DATA APPS_TS_TX_IDX
The custom user (schema) was created with a default custom tablespaces so we would have expected adsplice to create the objects in the XXEBS_DATA tablespace.
Expect AD Splice to work as in Release 12.1 and lower and create the custom objects in the custom tablespace as per the newprods.txt that was edited with the custom configuration.
The issue can be reproduced at will with the following steps:
1. Trying to Implement a custom Application using the following Notes:
Creating a Custom Application in Oracle E-Business Suite Release 12.2 (Doc ID 1577707.1)
Create And Register CUSTOM Schema On EBS 12.2 (Doc ID 1929668.1)
2. Updated newprods.txt with following values:
3. Ran adsplice.
The issue has the following business impact:
Due to this issue, the custom Application is not successfully implemented.
Custom applications were not created using the standard OATM model
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