Administrator
|
This is a new behaviour..
This is the expected behavior of adsplice on 12.2. Any new application, be it offered by Oracle as a seeded application or any new custom one, will abide by the mandatory OATM model.
So, my advice -> stick with what Oracle says..
So, it is normal that your custom tbs entries in newprods.txt are ignored.
Use adsplice to create a new custom application and let it create the new application custom objects with the 12. 2 OATM tablespaces model.
As said in :12.2 adsplice Ignores Custom Tablespaces For New Custom Application Configuration and Only Uses OATM Tablespaces (Doc ID 1987906.1)
Here is the adsplice newprods.txt example to follow for 12.2:
product=xxebs <<< Note that the product_top name used to be 8 characters maximum but is now 16 chars max
base_product_top=*APPL_TOP*
oracle_schema=xxebs
sizing_factor=100
main_tspace=USER_DATA <<< this is going to be ignored but you should anyway set it properly APPS_TS_TX_DATA
index_tspace=USER_IDX <<< this is going to be ignored but you should anyway set it properly
temp_tspace=TEMP
default_tspace=USER_DATA <<< this should be APPS_TS_TX_DATA which is the default tablespaces that must be setup for the new user XXEBS
<<< This last line is not ignored by adsplice and need to be aligned to the user created default tablespace which starting with 12.2 will always be APPS_TS_TX_DATA.
|