A Running the adsplice Utility

The adsplice utility operates by reading information specific to a product and splices that product into the Oracle Applications database. This also includes the creation of a new schema. The way this utility functions is impacted by whether or not Oracle Automatic Table Management (OATM) is implemented. If you are performing a fresh installation on a database created using the latest rapidwiz for the 12.0.4 E-Business Suite, you will have OATM enabled. If you are applying it to an older E-Business Suite installation that has been upgraded to the required release, your tablespaces may not have OATM enabled.

To check whether your instance is OATM enabled, run the following commands from SQL*Plus:

select tablespace_name from dba_tablespaces  where tablespace_name in ('APPS_TS_TX_DATA','APPS_TS_TX_IDX');   TABLESPACE_NAME  ------------------------------   APPS_TS_TX_DATA   APPS_TS_TX_IDX 
  select distinct default_tablespace from dba_users  where username in (select oracle_username from apps.fnd_oracle_userid  where oracle_username not in('CTXSYS','ODM'));  DEFAULT_TABLESPACE  ------------------------------  APPS_TS_TX_DATA

If the above outputs are present then it is an OATM enabled environment, otherwise it is not.

Navigate to the directory, where the patch was unzipped, For example, $HOME/patch/ 5497423
From this location change the directory to [product_name]/admin

Open newprods.txt and change the content as follows:For OATM enabled environment:

main_tspace=APPS_TS_TX_DATA       index_tspace=APPS_TS_TX_IDX      temp_tspace=TEMP <-- check this from DB       default_tspace=APPS_TS_TX_DATA

For Non-OATM enabled environment:

main_tspace=[PRODUCT_NAME]D       index_tspace=[PRODUCT_NAME]X     temp_tspace=TEMP <-- check this from DB        default_tspace=[PRODUCT_NAME]D

Example for Non-OATM enabled environment and CTB product:

main_tspace=CTBD        index_tspace=CTBX        temp_tspace=TEMP        default_tspace=CTBD

Save the modified newprods.txt and position it in $APPL_TOP for use.
Copy *.txt from [product_name]/admin in $APPL_TOP/admin
Create the DATA and INDEX tablespaces (only for Non-OATM enabled environment). Skip step 7 to 9 if OATM is enabled.

Verify the default location for product data tablespaces by running the following from SQL*Plus:

select distinct TABLESPACE_NAME, FILE_NAME from dba_data_files;

Example (for CTB):

SQL> select distinct TABLESPACE_NAME, FILE_NAME from dba_data_files  2 where TABLESPACE_NAME like 'CTB%';  TABLESPACE_NAME  ------------------------------  FILE_NAME  --------------------------------------------------------------------------------  CTBD  /dppoli/oradata/data01/ctbd01.dbf
   
  CTBX
  
  /dppoli/oradata/data01/ctbx01.dbf

The default location usually looks like '/[sid]/oradata/data[nn]'

If the tablespace, you are specifying as the default tablespace does not exist, create the tablespaces as follows:

create tablespace [PROD_NAME]D datafile '/[sid]/oradata/data[nn]/[prod]d01.dbf'size [nn]M AUTOEXTEND ON NEXT 5M MAXSIZE [nn]M;

Create tablespace [PROD_NAME]X datafile '/[sid]/oradata/data[nn]/[prod]x01.dbf' size [nn]M AUTOEXTEND ON NEXT 5M MAXSIZE [nn]M;

Example (for CTB):

create tablespace CTBD datafile '/dsslti/oradata/data01/ctbd01.dbf'size 50M AUTOEXTEND ON NEXT 5M MAXSIZE 75M;create tablespace CTBX datafile '/dsslti/oradata/data01/ctbx01.dbf'size 50M AUTOEXTEND ON NEXT 5M MAXSIZE 75M;

Back up of the following configuration files:
- $CONTEXT_FILE
- environment file
Run ADSPLICE utility as follows:
1. Change directory to $APPL_TOP/admin
2. Run adsplice
3. Select newprods.txt as AD Splicer control file
4. Note that when AD Splicer asks: "Do you wish to regenerate your environment file?", answer No.You can specify Yes to regenerate the environment file when you run adsplice with the last product you want to add with the splicer.
After the last product is added using adsplice, and the environment file has been regenerated, check the $CONTEXT_FILE as follows:
1. Open $CONTEXT_FILE and locate the section where all product tops are defined
2. Check the new product top entry has been added into this section with respect to the alphabetical order
  
  For CTB - When environment file has been regenerated after all products have been spliced:
```
...<HCT_TOP oa_var="s_hcttop" oa_type="PROD_TOP" oa_enabled="FALSE">/u01/appmgr/apps/apps_st/appl/hct/12.0.0</HCT_TOP><HCP_TOP oa_var="s_hcptop" oa_type="PROD_TOP" oa_enabled="FALSE">/u01/appmgr/apps/apps_st/appl/hcp/12.0.0</HCP_TOP><CTB_TOP oa_var="s_ctbtop" oa_type="PROD_TOP" oa_enabled="FALSE">/u01/appmgr/apps/apps_st/appl/ctb/12.0.0</CTB_TOP>  ...
```
If multiple MTs are used: If the APPL_TOP is not shared, repeat all the steps 5, 6, and 7 for the remaining MTs. For shared APPL_TOP installations repeat only the steps 5 and 7 for the remaining MTs. You do not need to re-run ADSPLICE.
Log out and log in again in Unix for the changes to take effect

Verify that the new product has been spliced properly by checking:

if environment variable for $PRODUCT_TOP is set
the directory structure

if the new product has been spliced properly into the FND_PRODUCT_INSTALLATIONS table by running the following from SQL*Plus:

COL app_s_name FORMAT a16  COL inst_status FORMAT a15  COL product_version FORMAT a12  COL patchset FORMAT a15  COL appl_id FORMAT 99999  select fav.application_id APPL_ID,  fav.application_short_name app_s_name,  decode(fpi.status,'I','Installed','S','Shared','N','No', fpi.status) inst_status,  fpi.product_version,  nvl(fpi.patch_level, 'Not Available') patchset  from  fnd_application_vl fav, fnd_product_installations fpi  where fav.application_id = fpi.application_id  and fav.application_short_name = '&product_name';  Check if both DATA and INDEX tablespaces exist

Example (for CTB):

$ echo $CTB_TOP  /u01/appmgr/apps/apps_st/appl/ctb/12.0.0
$ ls -lrt $CTB_TOP  total 32  drwxr-xr-x 2 apdclo4i aadclo4i 4096 Apr 16 2006 sql  drwxr-xr-x 2 apdclo4i aadclo4i 4096 Apr 16 2006 out  drwxr-xr-x 2 apdclo4i aadclo4i 4096 Apr 16 2006 mesg  drwxr-xr-x 2 apdclo4i aadclo4i 4096 Apr 16 2006 log  drwxr-xr-x 4 apdclo4i aadclo4i 4096 Apr 16 2006 admin  drwxr-xr-x 3 apdclo4i aadclo4i 4096 Apr 16 2006 patch  drwxr-xr-x 3 apdclo4i aadclo4i 4096 Jul 15 23:29 bin  drwxr-xr-x 2 apdclo4i aadclo4i 4096 Jul 15 23:29 html

SQL> select fav.application_id APPL_ID,  fav.application_short_name app_s_name,  decode(fpi.status,'I','Installed','S','Shared','N','No', fpi.status) inst_status,  fpi.product_version,  nvl(fpi.patch_level, 'Not Available') patchset  from fnd_application_vl fav, fnd_product_installations fpi  where fav.application_id = fpi.application_id  and fav.application_short_name = '&product_name';

Enter value for product_name: CTB

old 8: and fav.application_short_name = '&product_name'  new 8: and fav.application_short_name = 'CTB'APPL_ID APP_S_NAME INST_STATUS PRODUCT_VERS PATCHSET  ------- ---------------- --------------- ------------ ---------------  3002       CTB           Installed        12.0.0       R12.CTB.A.1