Custom Top creation in Oracle EBS R12.2

I'm using Oracle EBS R12.2.7 and below are the steps I followed to create custom top. Here I used the name xxerp for my custom top,custom schema and the tablespace for this schema. 

1.Download Patch 3636980 "Support Diagnostics (IZU) patch for AD Splice" from My Oracle Support.

2.Manually copy the three .txt files from the 3636980\izu\admin directory to your own temporary directory.

3.Rename izuprod.txt to <CUSTOM MODULE>prod.txt. In this example, we will use "xxerpprod.txt".

4.Rename izterr.txt to <CUSTOM MODULE>terr.txt. In this example, we will use "xxerpterr.txt".

5.Open newprods.txt in a text editor.

a.Change all references of "izu" to <custom module> and all references of "IZU" to <CUSTOM MODULE> (i.e. keep the case sensitivity).

b.Modify other values as below.

6.Create a custom schema,tablespace for that schema and provide the required grants to that schema.

7.Edit newprods.txt file and change the default_tspace to APPS_TS_TX_DATA. 

8.Edit xxerpprod.txt file Change all references of "izu" to <custom module> and all references of "IZU" to <CUSTOM MODULE> (keeping the case sensitivity). 

      a.Change all references of prodid 278 to your own application ID. You can run the following SQL to find out if your selected custom application ID number is available or not. Here I've used the port 50005.

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 ) );

9.Open xxerpterr.txt in a text editor and Change all references of "izu" to <custom module> and all references of "IZU" to <CUSTOM MODULE> (keeping the case sensitivity).

     a.Change the text "Oracle_Support_Diagnostic_Tools" to "xxerp_custom_app".

10.Copy the following text files to the $APPL_TOP/admin directory.

11.Change directory to the admin directory under $APPL_TOP and run adsplice

12.When prompted for location, name of AD Splicer control file and to regenerate the environment file accept the default answers.

Once adsplice completed successfully, follow the below steps to confirm successful creation of custom top.

select * from fnd_application where application_short_name = 'XXERP';

select * from fnd_product_installations where APPLICATION_ID = 50005;

select * from dba_users where username = 'XXERP';

All these above queries should return only one row.

Logout and login to a new session and confirm the below to ensure that the environment file is regenerated properly with the entry of our custom top.

Have created the custom top successfully.

Ref : Creating a Custom Application in Oracle E-Business Suite Release 12.2 (Doc ID 1577707.1)

                      ****************************நன்றி****************************

Changing ASM Diskgroup Redundancy

Recently I've created a new ASM instance. In that I've created a diskgroup named DATA and created with Normal redundancy, but I supposed to create it with External redundacy. Now I need to change the redundancy to Normal of that diskgroup. I tried many steps, but at last I did change the redundancy and below are the steps I followed.

Trying to dismount the Diskgroup DATA in-order to change the redundancy, but in the attempt of dismounting the diskgroup I faced below issues.

So, I decided to take a bounce on the ASM Instance and dismount the diskgroup, it works. Now I tried to drop that diskgroup and recreate the same with External redundancy but no luck!

Facing the above issue, since the diskgroup is in mount state. Tried to dismount,disable the diskgroup but nothing worked.

Finally I decided to do the dismount and drop the diskgroup using force option. Since this is a new instance and the diskgroup doesn't contain any data I used 'including contents'.

Now I created the diskgroup with External redundancy as I intended. 

                                     ****************************நன்றி****************************

Adding ASM Disk to existing Diskgroup

We can add an ASM disk to existing diskgroup in two ways.

   1. GUI - Using asmca utility
   2. Command Line - Using SQL Command

GUI - Using asmca utility

Check Diskgroup and ASM disk details as follows.

Now switch to root user and create ASM disk(DATA07) as follows. Here DATA07 is the new LUN partition provisioned by storage team in the alias name as DATA07. Also I'm going to create the ASM disk in the same name(DATA07)

 Once ASM disk is created, switch to grid user and invoke asmca utility as follows.

Here enter your server IP and launch the putty session.

Command Line - Using SQL Command

Here in the below example I'm going to add a new ASM disk named DISK14 to diskgroup DATA. Let us see the steps involved.

In the below SS, we've disks upto 13.

Below are the SS shows the diskgroup details.

 

In below SS, you can see disk named DATA14. Our storage team had assigned a LUN partition in the alias name as 'DATA14'.

Now as root user, create ASM disk with the newly assigned LUN partition(DATA14) .

Now switch to grid user and assign the newly created disk(DATA14) and map the same to the diskgroup DATA.

                                     ****************************நன்றி****************************