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

Last updated on NOVEMBER 22, 2023

Applies to:

Symptoms

Actual Behavior:
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.

Expected Behavior
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. Implement a custom Application using the following Note:
  Creating a Custom Application in Oracle E-Business Suite Release 12.2 (Doc ID 1577707.1)

2. Updated newprods.txt with following values:
product=xxebs
base_product_top= *APPL_TOP*
oracle_schema=xxebs
sizing_factor=100
main_tspace= XXEBS_DATA
index_tspace=XXEBS_IDX
temp_tspace=TEMP
default_tspace= XXEBS_DATA

3. Ran adsplice.

Changes

 Custom applications were not created using the standard OATM model

Cause

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