USE PROD instance
------- Pre-install Tasks -----------
You must shut down all Application tier services before performing the tasks in this section.
--------AD Splicer---------
• AD Splicer registers off-cycle product as a valid Oracle Applications product for the given release
• The splicing process enables AutoPatch and AD Administration to recognize the off-cycle product
• AD Splicer uses control files to manage the splicing process
– These are not related to the database control files
AD Splicer Control Files
Off-cycle products are generally released as patches. All product files and control files necessary to splice in the product are included in the patch.
There is one product configuration file, called newprods.txt. The product configuration file must be edited for your specific system before the off-cycle product can be properly spliced.
Note: The product definition files must not be altered.
There are two product definition files per off-cycle product. They are
• <prod>prod.txt: which contains language-independent information for product <prod>
• <prod>terr.txt: which contains language-dependent information for product <prod> <prod> represents the product abbreviation for an Applications product. For example GL for General Ledger and PO for Purchasing.
The AD Splicer control files must copied from the patch to the APPL_TOP/admin directory.
-------Editing newprod.txt (Controlfile)-------------
-bash-3.2$ more newprods.txt
%%% Splicer control file format 12.0.A
#
# $Header: newprods.txt 120.1 2006/09/20 12:57:45 jaobrien noship $
#
#
# Section for Oracle Support Diagnostic Tools
product=izu
base_product_top=*APPL_TOP*
oracle_schema=izu
sizing_factor=100
main_tspace=APPS_TS_TX_DATA
index_tspace=APPS_TS_TX_IDX
temp_tspace=TEMP1
default_tspace=APPS_TS_TX_DATA
# end of Oracle Support Diagnostic Tools
------Post-Splice Steps--------
After the new product is spliced in, the files and objects for this product can be installed. To do this you need to:
• Log out and log back in so that you are using the new environment file (or registry entries) to set up your environment
• Verify that <PROD>_TOP environment variables are set for your newly-spliced product
• Run AutoPatch to install files and database objects for your new product
Example : Patch - ADSPLICE PATCH FOR IZU - Release 12 - 6280873
IZU Splice Preparation Tasks for R12
Customers with multi-node installations of eBusiness Suite should apply this
adsplice patch on all nodes.
Before you run adpatch you must complete the steps below:
1. Unzip this patch and you will get directory 6280873.
2. Copy the following text files from 6280873/izu/admin to the admin directory under APPL_TOP.
izuprod.txt
izuterr.txt
newprods.txt
3. Change directory to the admin directory under APPL_TOP.
Review newprods.txt and verify that the tablespaces listed exist and are the ones planned for use by this product. If changes are required, edit the file as appropriate and save it.
cd $APPL_TOP/admin
vi newprod.txt
4. You must run "adsplice" from the admin directory under your APPL_TOP.
When you are asked to enter the name of your AD Splicer control file, enter newprods.txt
adsplice
Filename [adsplice.log]
**********************************************************************************************************************
-bash-3.2$ cd $APPL_TOP/admin
-bash-3.2$ adsplice
Copyright (c) 2002 Oracle Corporation
Redwood Shores, California, USA
AD Splicer
Version 12.0.0
NOTE: You may not use this utility for custom development
unless you have written permission from Oracle Corporation.
Your default directory is '/u01/oracle/VIS/apps/apps_st/appl'.
Is this the correct APPL_TOP [Yes] ?
AD Splicer records your AD Splicer session in a text file
you specify. Enter your AD Splicer log file name or press [Return]
to accept the default file name shown in brackets.
Filename [adsplice.log] : izu_adsplice.log
************* Start of AD Splicer session *************
AD Splicer version: 12.0.0
AD Splicer started at: Sun Jan 25 2015 12:39:45
APPL_TOP is set to /u01/oracle/VIS/apps/apps_st/appl
Change DB = YES.
Please enter the name of the Oracle Applications System that this
APPL_TOP belongs to.
The Applications System name must be unique across all Oracle
Applications Systems at your site, must be from 1 to 30 characters
long, may only contain alphanumeric and underscore characters,
and must start with a letter.
Sample Applications System names are: "prod", "test", "demo" and
"Development_2".
Applications System Name [VIS] : VIS *
NOTE: If you do not currently have certain types of files installed
in this APPL_TOP, you may not be able to perform certain tasks.
Example 1: If you don't have files used for installing or upgrading
the database installed in this area, you cannot install or upgrade
the database from this APPL_TOP.
Example 2: If you don't have forms files installed in this area, you cannot
generate them or run them from this APPL_TOP.
Example 3: If you don't have concurrent program files installed in this area,
you cannot relink concurrent programs or generate reports from this APPL_TOP.
Do you currently have or want to install files used for installing or upgrading
the database in this APPL_TOP [YES] ? YES *
Do you currently have or want to install Java and HTML files for HTML-based
functionality in this APPL_TOP [YES] ? YES *
Do you currently have or want to install Oracle Applications forms files
in this APPL_TOP [YES] ? YES *
Do you currently have or want to install concurrent program files
in this APPL_TOP [YES] ? YES *
Please enter the name Oracle Applications will use to identify this APPL_TOP.
The APPL_TOP name you select must be unique within an Oracle Applications
System, must be from 1 to 30 characters long, may only contain
alphanumeric and underscore characters, and must start with a letter.
Sample APPL_TOP Names are: "prod_all", "demo3_forms2", and "forms1".
APPL_TOP Name [oracle] : oracle *
You are about to install or upgrade Oracle Applications product tables
in your ORACLE database 'VIS'
using ORACLE executables in '/u01/oracle/VIS/apps/tech_st/10.1.2'.
Is this the correct database [Yes] ?
AD Splicer needs the password for your 'SYSTEM' ORACLE schema
in order to determine your installation configuration.
Enter the password for your 'SYSTEM' ORACLE schema:
The ORACLE username specified below for Application Object Library
uniquely identifies your existing product group: APPLSYS
Enter the ORACLE password of Application Object Library [APPS] :
AD Splicer is verifying your username/password.
The status of various features in this run of AD Splicer is:
<-Feature version in->
Feature Active? APPLTOP Data model Flags
------------------------------ ------- -------- ----------- -----------
CHECKFILE Yes 1 1 Y N N Y N Y
PREREQ Yes 6 6 Y N N Y N Y
CONCURRENT_SESSIONS No 2 2 Y Y N Y Y N
PATCH_TIMING Yes 2 2 Y N N Y N Y
PATCH_HIST_IN_DB Yes 6 6 Y N N Y N Y
SCHEMA_SWAP Yes 1 1 Y N N Y Y Y
JAVA_WORKER Yes 1 1 Y N N Y N Y
CODELEVEL Yes 1 1 Y N N Y N Y
Reading product information from file...
Reading language and territory information from file...
Reading language information from applUS.txt ...
AD Splicer warning:
Product Data File
/u01/oracle/VIS/apps/apps_st/appl/admin/zfaprod.txt
does not exist for product "zfa".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AD Splicer warning:
Product Data File
/u01/oracle/VIS/apps/apps_st/appl/admin/zsaprod.txt
does not exist for product "zsa".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AD Splicer warning:
Product Data File
/u01/oracle/VIS/apps/apps_st/appl/admin/jtsprod.txt
does not exist for product "jts".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
Reading database to see what industry is currently installed.
Reading FND_LANGUAGES to see what is currently installed.
Currently, the following language is installed:
Code Language Status
---- --------------------------------------- ---------
US American English Base
Your base language will be AMERICAN.
Setting up module information.
Reading database for information about the modules.
Saving module information.
Reading database for information about the products.
Reading database for information about how products depend on each other.
Reading topfile.txt ...
Saving product information.
Please enter the directory where your AD Splicer control file is located.
The default directory is [/u01/oracle/VIS/apps/apps_st/appl/admin] :
Please enter the name of your AD Splicer control file [newprods.txt] :
Processing file /u01/oracle/VIS/apps/apps_st/appl/admin/newprods.txt...
Loading information for product 'izu'...
Warning: Because the database is in new tablespace mode, AD Splicer is ignoring the tablespace settings in your control file!
Successfully read file /u01/oracle/VIS/apps/apps_st/appl/admin/newprods.txt.
Verifying localizations...
Validating inter-product dependency information...
Re-organizing product information lists...
Adding new languages into FND_LANGUAGES...
Saving module actions...done.
Saving product actions...done.
Product top directory for product "izu" exists.
Directory is /u01/oracle/VIS/apps/apps_st/appl/izu/12.0.0
Directory "log" for product "izu" exists.
Directory "out" for product "izu" exists.
Directory "mesg" for product "izu" exists.
Directory "sql" for product "izu" exists.
File "sql/IZUNLINS.sql" for product "izu" exists.
Directory "admin/sql" for product "izu" exists.
File "admin/sql/IZUNLADD.sql" for product "izu" exists.
Directory "admin/driver" for product "izu" exists.
Do you wish to regenerate your environment file [Yes] ?
Checking if AutoConfig is enabled....
Running AutoConfig on : All products ...
The log file is located at:
/u01/oracle/VIS/apps/apps_st/appl/admin/VIS/log/autoconfig_1.log
Please check the log file for more details about the run of AutoConfig.
AD Splicer is complete.
Errors and warnings are listed in the log file
/u01/oracle/VIS/apps/apps_st/appl/admin/VIS/log/izu_adsplice.log
and in other log files in the same directory.
You have new mail in /var/spool/mail/oraapp
-bash-3.2$
**********************************************************************************************************************
5. AD Splicer will regenerate the environment file or registry. If you have made manual modifications to your environment file or your registry, you will need to apply those changes again.
APPLY THE PATCH
----------------------------
1. cd $ADMIN_SCRIPTS_HOME
sh adstpall.sh apps/apps
2. Enable Maintenance Mode
3. adpatch
Verifying splicing of IZU
---------------------------------
A. Log out and log back in so that you are using the new environment
file (or registry entries ) to set up your environment
exit
su - oraapp
. ./APPSVIS_oracle.env
B. Verify that IZU_TOP environment variable is set for your newly-spliced product IZU
C. Verify that the product has been correctly created in the database by connection as "APPS" user.
select fa.APPLICATION_ID, STATUS
from fnd_application fa, fnd_product_installations fpi
where fa.APPLICATION_ID=fpi.APPLICATION_ID and APPLICATION_SHORT_NAME = 'IZU' ;
This statement should return one row:
APPLICATION_ID S
-------------- -
278 I
D. Verify you can connect to the database as izu/izu using SQLPLUS.
------- Pre-install Tasks -----------
You must shut down all Application tier services before performing the tasks in this section.
--------AD Splicer---------
• AD Splicer registers off-cycle product as a valid Oracle Applications product for the given release
• The splicing process enables AutoPatch and AD Administration to recognize the off-cycle product
• AD Splicer uses control files to manage the splicing process
– These are not related to the database control files
AD Splicer Control Files
Off-cycle products are generally released as patches. All product files and control files necessary to splice in the product are included in the patch.
There is one product configuration file, called newprods.txt. The product configuration file must be edited for your specific system before the off-cycle product can be properly spliced.
Note: The product definition files must not be altered.
There are two product definition files per off-cycle product. They are
• <prod>prod.txt: which contains language-independent information for product <prod>
• <prod>terr.txt: which contains language-dependent information for product <prod> <prod> represents the product abbreviation for an Applications product. For example GL for General Ledger and PO for Purchasing.
The AD Splicer control files must copied from the patch to the APPL_TOP/admin directory.
-------Editing newprod.txt (Controlfile)-------------
-bash-3.2$ more newprods.txt
%%% Splicer control file format 12.0.A
#
# $Header: newprods.txt 120.1 2006/09/20 12:57:45 jaobrien noship $
#
#
# Section for Oracle Support Diagnostic Tools
product=izu
base_product_top=*APPL_TOP*
oracle_schema=izu
sizing_factor=100
main_tspace=APPS_TS_TX_DATA
index_tspace=APPS_TS_TX_IDX
temp_tspace=TEMP1
default_tspace=APPS_TS_TX_DATA
# end of Oracle Support Diagnostic Tools
------Post-Splice Steps--------
After the new product is spliced in, the files and objects for this product can be installed. To do this you need to:
• Log out and log back in so that you are using the new environment file (or registry entries) to set up your environment
• Verify that <PROD>_TOP environment variables are set for your newly-spliced product
• Run AutoPatch to install files and database objects for your new product
Example : Patch - ADSPLICE PATCH FOR IZU - Release 12 - 6280873
IZU Splice Preparation Tasks for R12
Customers with multi-node installations of eBusiness Suite should apply this
adsplice patch on all nodes.
Before you run adpatch you must complete the steps below:
1. Unzip this patch and you will get directory 6280873.
2. Copy the following text files from 6280873/izu/admin to the admin directory under APPL_TOP.
izuprod.txt
izuterr.txt
newprods.txt
3. Change directory to the admin directory under APPL_TOP.
Review newprods.txt and verify that the tablespaces listed exist and are the ones planned for use by this product. If changes are required, edit the file as appropriate and save it.
cd $APPL_TOP/admin
vi newprod.txt
4. You must run "adsplice" from the admin directory under your APPL_TOP.
When you are asked to enter the name of your AD Splicer control file, enter newprods.txt
adsplice
Filename [adsplice.log]
**********************************************************************************************************************
-bash-3.2$ cd $APPL_TOP/admin
-bash-3.2$ adsplice
Copyright (c) 2002 Oracle Corporation
Redwood Shores, California, USA
AD Splicer
Version 12.0.0
NOTE: You may not use this utility for custom development
unless you have written permission from Oracle Corporation.
Your default directory is '/u01/oracle/VIS/apps/apps_st/appl'.
Is this the correct APPL_TOP [Yes] ?
AD Splicer records your AD Splicer session in a text file
you specify. Enter your AD Splicer log file name or press [Return]
to accept the default file name shown in brackets.
Filename [adsplice.log] : izu_adsplice.log
************* Start of AD Splicer session *************
AD Splicer version: 12.0.0
AD Splicer started at: Sun Jan 25 2015 12:39:45
APPL_TOP is set to /u01/oracle/VIS/apps/apps_st/appl
Change DB = YES.
Please enter the name of the Oracle Applications System that this
APPL_TOP belongs to.
The Applications System name must be unique across all Oracle
Applications Systems at your site, must be from 1 to 30 characters
long, may only contain alphanumeric and underscore characters,
and must start with a letter.
Sample Applications System names are: "prod", "test", "demo" and
"Development_2".
Applications System Name [VIS] : VIS *
NOTE: If you do not currently have certain types of files installed
in this APPL_TOP, you may not be able to perform certain tasks.
Example 1: If you don't have files used for installing or upgrading
the database installed in this area, you cannot install or upgrade
the database from this APPL_TOP.
Example 2: If you don't have forms files installed in this area, you cannot
generate them or run them from this APPL_TOP.
Example 3: If you don't have concurrent program files installed in this area,
you cannot relink concurrent programs or generate reports from this APPL_TOP.
Do you currently have or want to install files used for installing or upgrading
the database in this APPL_TOP [YES] ? YES *
Do you currently have or want to install Java and HTML files for HTML-based
functionality in this APPL_TOP [YES] ? YES *
Do you currently have or want to install Oracle Applications forms files
in this APPL_TOP [YES] ? YES *
Do you currently have or want to install concurrent program files
in this APPL_TOP [YES] ? YES *
Please enter the name Oracle Applications will use to identify this APPL_TOP.
The APPL_TOP name you select must be unique within an Oracle Applications
System, must be from 1 to 30 characters long, may only contain
alphanumeric and underscore characters, and must start with a letter.
Sample APPL_TOP Names are: "prod_all", "demo3_forms2", and "forms1".
APPL_TOP Name [oracle] : oracle *
You are about to install or upgrade Oracle Applications product tables
in your ORACLE database 'VIS'
using ORACLE executables in '/u01/oracle/VIS/apps/tech_st/10.1.2'.
Is this the correct database [Yes] ?
AD Splicer needs the password for your 'SYSTEM' ORACLE schema
in order to determine your installation configuration.
Enter the password for your 'SYSTEM' ORACLE schema:
The ORACLE username specified below for Application Object Library
uniquely identifies your existing product group: APPLSYS
Enter the ORACLE password of Application Object Library [APPS] :
AD Splicer is verifying your username/password.
The status of various features in this run of AD Splicer is:
<-Feature version in->
Feature Active? APPLTOP Data model Flags
------------------------------ ------- -------- ----------- -----------
CHECKFILE Yes 1 1 Y N N Y N Y
PREREQ Yes 6 6 Y N N Y N Y
CONCURRENT_SESSIONS No 2 2 Y Y N Y Y N
PATCH_TIMING Yes 2 2 Y N N Y N Y
PATCH_HIST_IN_DB Yes 6 6 Y N N Y N Y
SCHEMA_SWAP Yes 1 1 Y N N Y Y Y
JAVA_WORKER Yes 1 1 Y N N Y N Y
CODELEVEL Yes 1 1 Y N N Y N Y
Reading product information from file...
Reading language and territory information from file...
Reading language information from applUS.txt ...
AD Splicer warning:
Product Data File
/u01/oracle/VIS/apps/apps_st/appl/admin/zfaprod.txt
does not exist for product "zfa".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AD Splicer warning:
Product Data File
/u01/oracle/VIS/apps/apps_st/appl/admin/zsaprod.txt
does not exist for product "zsa".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AD Splicer warning:
Product Data File
/u01/oracle/VIS/apps/apps_st/appl/admin/jtsprod.txt
does not exist for product "jts".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
Reading database to see what industry is currently installed.
Reading FND_LANGUAGES to see what is currently installed.
Currently, the following language is installed:
Code Language Status
---- --------------------------------------- ---------
US American English Base
Your base language will be AMERICAN.
Setting up module information.
Reading database for information about the modules.
Saving module information.
Reading database for information about the products.
Reading database for information about how products depend on each other.
Reading topfile.txt ...
Saving product information.
Please enter the directory where your AD Splicer control file is located.
The default directory is [/u01/oracle/VIS/apps/apps_st/appl/admin] :
Please enter the name of your AD Splicer control file [newprods.txt] :
Processing file /u01/oracle/VIS/apps/apps_st/appl/admin/newprods.txt...
Loading information for product 'izu'...
Warning: Because the database is in new tablespace mode, AD Splicer is ignoring the tablespace settings in your control file!
Successfully read file /u01/oracle/VIS/apps/apps_st/appl/admin/newprods.txt.
Verifying localizations...
Validating inter-product dependency information...
Re-organizing product information lists...
Adding new languages into FND_LANGUAGES...
Saving module actions...done.
Saving product actions...done.
Product top directory for product "izu" exists.
Directory is /u01/oracle/VIS/apps/apps_st/appl/izu/12.0.0
Directory "log" for product "izu" exists.
Directory "out" for product "izu" exists.
Directory "mesg" for product "izu" exists.
Directory "sql" for product "izu" exists.
File "sql/IZUNLINS.sql" for product "izu" exists.
Directory "admin/sql" for product "izu" exists.
File "admin/sql/IZUNLADD.sql" for product "izu" exists.
Directory "admin/driver" for product "izu" exists.
Do you wish to regenerate your environment file [Yes] ?
Checking if AutoConfig is enabled....
Running AutoConfig on : All products ...
The log file is located at:
/u01/oracle/VIS/apps/apps_st/appl/admin/VIS/log/autoconfig_1.log
Please check the log file for more details about the run of AutoConfig.
AD Splicer is complete.
Errors and warnings are listed in the log file
/u01/oracle/VIS/apps/apps_st/appl/admin/VIS/log/izu_adsplice.log
and in other log files in the same directory.
You have new mail in /var/spool/mail/oraapp
-bash-3.2$
**********************************************************************************************************************
5. AD Splicer will regenerate the environment file or registry. If you have made manual modifications to your environment file or your registry, you will need to apply those changes again.
APPLY THE PATCH
----------------------------
1. cd $ADMIN_SCRIPTS_HOME
sh adstpall.sh apps/apps
2. Enable Maintenance Mode
3. adpatch
Verifying splicing of IZU
---------------------------------
A. Log out and log back in so that you are using the new environment
file (or registry entries ) to set up your environment
exit
su - oraapp
. ./APPSVIS_oracle.env
B. Verify that IZU_TOP environment variable is set for your newly-spliced product IZU
C. Verify that the product has been correctly created in the database by connection as "APPS" user.
select fa.APPLICATION_ID, STATUS
from fnd_application fa, fnd_product_installations fpi
where fa.APPLICATION_ID=fpi.APPLICATION_ID and APPLICATION_SHORT_NAME = 'IZU' ;
This statement should return one row:
APPLICATION_ID S
-------------- -
278 I
D. Verify you can connect to the database as izu/izu using SQLPLUS.
