Oracle EBS12.2 Registration Custom Application

I. Basic information for Oracle apps and DB

1. Application and Database environment:

Application Node in Linux7.3

Database Node on Linux 7.3

2. Oracle EBS Application version:

R12.2.6 on Linux7.3 x_86 (64bit)

3. Database information:

Oracle Database R12.1.0.2 on Linux 7.3 x_86 (64bit)

Ii. Steps of implementation

1, create a Cux user in the database, and authorize. The relevant commands are as follows:

--(1) Create Cux users     CREATE USER CUX IDENTIFIED BY CUX     default tablespace apps_ts_tx_data    temporary tablespace  temp1    profile default    account unlock; --( 2) give the user authorization to appear     GRANT CONNECT, RESOURCE TO CUX;      grant create any context to cux;     grant create  any type to cux;     grant create cluster to  CUX;     GRANT CREATE DATABASE LINK TO CUX;      grant create dimension to cux;     grant  create indextype to cux;     grant create library  to cux;   &nbSp; grant create materialized view to cux;     grant  create operator to cux;     grant create procedure  TO CUX;     GRANT CREATE PUBLIC SYNONYM TO CUX;      GRANT CREATE SEQUENCE TO CUX;      Grant create synonym to cux;     grant create table  TO CUX;     GRANT CREATE TRIGGER TO CUX;      grant create type to cux;     grant create  view to cux;2, download 3636980 patches on Oracle's official website, Patch for P3636980_r12_generic.zip. 3, Decompression patch P3636980_r12_generic.zip, and three files from the p3636980_r12_generic\3636980\izu\admin copy to the current user desktop/ . The file is as follows:     IZUPROD.TXT    IZUTERR.TXT    NEWPRODS.TXT4, Izupord.txt renamed to cuxprod.txt,izuterr.txt  Rename to Cuxterr.txt. The relevant commands are as follows:     mv  izupord.txt cuxprod.txt   mv   izuterr.txt cuxterr.txt  5, use a text editor to open the Cuxprod.txt file, replace Izu with Cux, replace Izu with cux .     %%% 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=cux    base_product_top=*appl_top*    oracle_schema=cux     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   6, use a text editor to open Cuxprod.txt, and complete the Operation:  (1) Replace all Izu in Cuxprod.txt document with Cux,izu instead.   (2) Modify the applid of the product and change the 278 to 50000 or more applid that have not been used. Check the SQL statement for applid  as follows:

    sql>select        decode (count ,0,   ' selected number is available ',  ' selected number already in         use ')  Status, &&enter_custom_applID         selected_number        from          (        select count (* )  as count from         (         select  ' x '  from fnd_oracle_userid         where oracle_id= &&enter_custom_applID         union        select  ' x '  from fnd_application         where application_id= &&enter_custom_applid)          );         If you want to change 278 to 50303, then enter 50303 in Enter_custom_applid. If selected number is available  appears, 50303 is available.

7. Open Cuxterr.txt with a text editor and do the following:

(1) Replace the Izu with the Cux and replace the Izu with the Cux.

(2) Change the oracle_support_diagnostic_tools to ABCD_CUSTOM_APPL

8. Copy the following three files to the $appl_top/admin directory.

Cuxprod.txt

Cuxterr.txt

Newprods.txt

9, switch to the $appl_top/admin directory, execute the following command

    $ adsplice     Copyright  (c)  2002, 2012  Oracle Corporation                         Redwood Shores, California,  usa                                    ad  Splicer                                  version  12.2.0NOTE: You may not use this utility for custom  development      unless you have written permission  From oracle corporation. your default directory is  '/home/oraebs/apps/prod/fs1/ebsapps/appl '. Is this the correct appl_top [yes] ? ad splicer records your  AD Splicer session in a text fileyou specify.  Enter  Your ad splicer log file name or press [return]to accept the  default file name shown in brackets. your default directory is  '/u01/app/oracle/fs1/ebsapps/appl '. is this the correct appl_top [yes] ? filename[adsplice.log] : adsplice_xxont.logyou areabout to install or  Upgrade oracle e-business suite product tablesin your oracle database   ' D599 ' using oracle executables in  '/u01/app/oracle/fs1/ebsapps/10.1.2 '. Is this the correct database [yes] ? enterthe password for your  ' SYSTEM '  ORACLE schema:Enterthe ORACLE  password of application object library [apps] :P leaseenter the  Directory where your ad splicer control file is located. the default directory is [/u01/app/oracle/fs1/ebsapps/appl/admin] :P Lease enter  the name of your AD Splicer control file [newprods.txt] :D o  youwish to regenerate your environment file [yes] ? Checkingif autoconfig is enabled .... RUNNINGAUTOCONFIG ON : ALL PRODUCTS&NBSP, .....

11. Check the results of Adsplice and AutoConfig execution with the following SQL statement.

SELECT * from fnd_application where application_short_name = ' Cux ', select * from Fnd_product_installations where Applica tion_id = 50303;select * from dba_users where username = ' Cux ';

Log on to the user node and check the system environment.

$ env|grep xxontxxont_top=/u01/app/oracle/fs1/ebsapps/appl/xxont/12.0.0$ ls $XXONT _topadmin log mesg out SQL

If you are using shared appl_top, you need to perform all of these procedures on one of the nodes, and then run AutoConfig on the other nodes. You don't have to rerun Adsplice. If Appl_top is not shared, repeat steps 8,9,10 and 11.

This article from "Struggle More than" blog, reproduced please contact the author!

Oracle EBS12.2 Registration Custom Application