Oracle EBS adding Arabic Language

 

Adding and Maintaining NLS Languages:

Perform the following steps:

1. From Oracle Applications Manager, go to License Manager and activate or change your base language to a new one.

2. From AD Administration, run Maintain Multi-lingual Tables (AD Administration Main Menu > Maintain Applications Database Entities Menu).

3. From AD Administration, run Maintain Snapshot Information

4. Run the Translation Synchronization Patch utility (adgennls.pl). .
    If you have already run the Translation Synchronization Patch utility by following the Oracle E-Business Suite NLS Release Notes as mentioned in Step 3, 
    you can omit this step and step 5.
    Requesting Translation Synchronization Patches note 252422.1

5. When you are notified that it is available, apply your Translation Synchronization Patch (TSP) for all languages you requested.

6. Install the Release 12 NLS Help, if available (optional).

Find files larger than specific size in Linux

 find . -type f -size +10M -exec ls -lh {} \; | awk '{ print $9 "|| Size : " $5 }'

Manual masking script for EBS employees information

 /* Formatted on 07/03/2022 11:47:58 PM (QP5 v5.336) */

UPDATE per_all_people_f a

   SET national_identifier = '784123412345671',

       EMAIL_ADDRESS = 'test@testmail.com',

       a.FIRST_NAME = 'First',

       a.LAST_NAME = 'Last',

       a.PER_INFORMATION1 = 'Second',

       a.PER_INFORMATION2 = 'Third',

       a.PER_INFORMATION4 = 'Arabic First',

       a.PER_INFORMATION5 = 'Arabic Second',

       a.PER_INFORMATION6 = 'Arabic Third',

       a.PER_INFORMATION7 = 'Arabic  Last',

       a.DATE_OF_BIRTH = SYSDATE - 10000

 WHERE     a.EMPLOYEE_NUMBER IN ('184',

                                 '205',

                                 '414',

                                 '404',

                                 '187')

       AND a.BUSINESS_GROUP_ID = 81;

UPDATE pay_external_accounts

   SET segment1 = 'AJM', segment4 = '12345678', segment5 = 'AE1234567891234567890'

 WHERE external_account_id IN

           (SELECT b.external_account_id

              FROM pay_personal_payment_methods_f a, pay_external_accounts b

             WHERE     a.external_account_id = b.external_account_id

                   AND a.BUSINESS_GROUP_ID = 81

                   AND a.assignment_id IN

                           (SELECT x.assignment_id

                              FROM per_assignments_x x

                             WHERE     x.business_group_id = 81

                                   AND x.assignment_number IN ('184',

                                                               '205',

                                                               '414',

                                                               '404',

                                                               '187')));

update per_phones

set phone_number = '050123456'

where parent_table = 'PER_ALL_PEOPLE_F'

and parent_id in

(

select person_id from per_people_x where business_group_id = 81 and employee_number in 

('184',

                                                               '205',

                                                               '414',

                                                               '404',

                                                               '187')

)

Changing HOSTNAME in oracle EBS VM Appliance steps R12.2

 

Changing HOSTNAME in oracle EBS VM Appliance steps Release 12.2.7 (Doc ID 2328923.1)

Changing the logical host name of the virtual machine is not mandatory for accessing Oracle E-Business Suite applications. Our recommendation is to continue using the logical or virtual name as set when you install and front end the virtual machine with the virtual machine's public host name or any other device, such as a reverse proxy or a load-balancer, for access from external clients. Administrators can use the configwebentry.sh script shipped in the /u01/install/scripts directory for this purpose.

Please note that the instructions described in this section have been validated on the single node Vision instance virtual machine.

Perform the following steps to change the host name of the virtual machine:

1. Start the virtual machine.
2. Log in as the oracle user.
3. Source the runtime environment:
[oracle@apps ~]$ . /u01/install/APPS/EBSapps.env run
4. Execute the following command to start the Admin server:
[oracle@apps ~]$ $INST_TOP/admin/scripts/adadminsrvctl.sh start
5. Execute the following command:
[oracle@apps ~]$ $INST_TOP/admin/scripts/adpreclone.pl appsTier
6. Source the patch environment in the patch edition file system:
[oracle@apps ~]$ . /u01/install/APPS/EBSapps.env patch
7. Execute the following command:
[oracle@apps ~]$ $INST_TOP/admin/scripts/adadminsrvctl.sh start forcepatchfs
8. Execute the following command:
[oracle@apps ~]$ $INST_TOP/admin/scripts/adpreclone.pl appsTier
9. Execute the following command to shut down the Oracle E-Business Suite application tier services:
[oracle@apps ~]$ /u01/install/APPS/scripts/stopapps.sh
10. Execute the following command to shut down the Oracle E-Business Suite database tier services:
[oracle@apps ~]$ /u01/install/APPS/scripts/stopdb.sh
11. Execute the following command as the root user and provide the same IP configuration details and the new host name:
[root@apps ~]# /u01/install/scripts/configstatic.sh
12. Use the following two chkconfig commands to ensure that the boot scripts will not automatically start the database and application tiers upon boot. Use init 6 to reboot the VM.
[root@apps ~]# chkconfig apps off
[root@apps ~]# chkconfig ebsdb off
[root@apps ~]# init 6
It is important that the database and application tier processes do not start when the VM boots.

13. Once the virtual machine has rebooted, log in as the root user and ensure echo $HOSTNAME returns the new host name.
14. Execute the following command as the root user:
    
    Note: Change the SID of the Database (Conditional)
    If you want to change the SID of the database at this stage, perform the following task before running dbconfig.sh:
    

    • Edit the db_pairs.txt file in the /u01/install/APPS/scripts/ directory using the following commands:

    [root@apps ~]# cd /u01/install/APPS/scripts/
[root@apps ~]# sed -i "s/^s_dbSid=.*$/s_dbSid=VIS1227/" db_pairs.txt 

    In this example, consider "VIS1227" the new SID.

[root@apps ~]# /u01/install/APPS/scripts/dbconfig.sh
When the dbconfig.sh script completes, the database is left running with its new SID, such as "VIS1227", in this example.

15. Execute the following command as the root user:
[root@apps ~]# /u01/install/APPS/scripts/appsconfig.sh
If the script returns an error while creating the patch file system, perform the following steps to re-create the patch file system:

1. Stop any processes that is running from the patch file system.
2. Log in as the oracle user and source the run file system.
[oracle@apps ~]$ . /u01/install/APPS/EBSapps.env run
3. Execute the following command to create the patch file system:
[oracle@apps ~]$ adop phase=fs_clone force=yes
4. Perform the following steps to ensure that you can run online patching cycles without any errors on the reconfigured environment:
   
   1. Bring up processes from the run file system if they are down.
   2. Execute two adop empty cycles using the following commands:
   [oracle@apps ~]$ adop phase=prepare
[oracle@apps ~]$ adop phase=cutover
[oracle@apps ~]$ adop phase=prepare
[oracle@apps ~]$ adop phase=cutover
16. Attach inventory post appsconfig by executing the following command as the oracle user:
[oracle@apps ~]$ /u01/install/APPS/12.1.0/oui/bin/attachHome.sh