R12.1.

3 media setup on OEL4:

Installation of R12.1.1:
Server : Proliant BL460c OS: OEL 4 RAM: 16GB HDD: 820GB+234

Pre-requites check for installing R12.1.1 on OEL4:

1. After installing OEL4 on the server we need checkRPM's checked list: * binutils-2.15.92.0.2-21.x86_64.rpm * compat-db-4.1.25-9.i386.rpm (32-bit) * compat-db-4.1.25-9.x86_64.rpm * control-center-2.8.0-12.rhel4.5.x86_64.rpm * gcc-3.4.6-3.x86_64.rpm * gcc-c++-3.4.6-3.x86_64.rpm * glibc-2.3.4-2.25.x86_64.rpm * glibc-devel-2.3.4-2.25.x86_64.rpm * glibc-common-2.3.4-2.25.x86_64.rpm * gnome-libs-1.4.1.2.90-44.1.x86_64.rpm * libstdc++-3.4.6-3.x86_64.rpm * libstdc++-devel-3.4.6-3.x86_64.rpm * libgcc-3.4.6-3.x86_64.rpm * make-3.80-6.EL4.x86_64.rpm * pdksh-5.2.14-30.3.x86_64.rpm * setarch-1.6-1.x86_64.rpm * sysstat-5.0.5-11.rhel4.x86_64.rpm * xscreensaver-4.18-5.rhel4.11.x86_64.rpm * libaio-0.3.105-2.x86_64.rpm * libaio-devel-0.3.105-2.x86_64.rpm We can check these using rpm qa | grep <RPM> For installing the rpm, use rpm ivh <rpm>

 For upgarading the rpm, use rpm uvh <rpm> 2. Kernal Parameters checked list : For checking these parameters we need to use the following cmd. Ex. Cat /etc/sysctl.conf | grep Kernel*
kernel.semmsl kernel.semmns kernel.semopm kernel.semmni kernel.shmall kernel.shmmax 256 1 32000 1 100 1 142 2097152 Half the size of the physical memory (in bytes), and at least 2 2147483648 4096 8192 65535 2878 131072 3 10000 65000 262144 4194304 262144 262144
1

kernel.shmmni kernel.msgmax kernel.msgmnb kernel.msgmni fs.file-max net.ipv4.ip_local_port_range net.core.rmem_default net.core.rmem_max net.core.wmem_default net.core.wmem_max

If we edit any values, then we need to run sysctl p for getting chages . 3. Kernal requirement for OEL4: Oracle Linux Patch levels: 2.6.9-42.0.0.0.EL The command for checking is uname r 4. Check the available space in the server using df h command. 5. The space requirement for installing R12.1.1 is VISION- 208GB(db)+35GB(apps)=243GB PROD-55GB(db)+35GB(apps)=90GB 6. Create 2 users for accessing database and apps. EX. 1.Useradd g dba d /home/doramgr oramgr -s /bin/bash 2. Useradd g dba d /home/dapplmgr applmgr -s /bin/bash Where doramgr is the database user and dapplmgr is the application user. 7. Create two folders for db & apps and give permissions of two folders Ex. mkdir madevdb madevapps chown R dramgr: dba /u01/madevvdb chown R dapplmgr:dba /u01/madevapps

Where madevdb is the base directory for db & madevapps is the base directory for apps. 8. Need to check the software requirements using the command which -ar,gcc,g++,ksh,ld,linux32,make,X Display Server Ex. which ar which gcc 9. Verify the entries in etc/hosts. The entry should be in the following format. 127.0.0.1 localhost.localdomain localhost

[ip_adress] [node_name].[domain_name] [ node_name] Ex: 192.168.1.10 mavric.doyensys.com maverick 10. Modifying the Number of Open File Descriptors:
Open the /etc/security/limits.conf file and change the existing values for "hard" and "soft" parameters as follows. Restart the system after making changes

* hard nofile 65535 * soft nofile 4096 * hard nproc 16384 * soft nproc 2047

11. Run the rapidwiz from the staging.

./rapidwiz

Up gradation from R12.1.1 to R12.1.3:

For upgrading R12.1.1 to R12.1.3 we need to apply the following patches. 9239089 9239090 9817770 9966055 9239095

Before applying the patches, we need to set the below parameter in pfile. _disable_fast_validate=TRUE

Post update steps:

Application Tier: 1. Run the environment on apps tier (Apps<CONTEXT_NAME>.env) 2. Run autoconfig on APPL_TOP 3. Run the admkappsutil.pl utility to create the file appsutil.zip in the <INST_TOP>/admin/out directory 4. Perl <AD_TOP>/bin/admkappsutil.pl DatabaseTier: 1. Run the environment on db tier(<CONTEXT_NAME>.env) 2. Copy the appsutil.zip file from <INST_TOP>/admin/out to <RDBMS ORACLE_HOME> 3. Now go to that $ORACLE_HOME and unzip the appsutil.zip file Unzip o appsutil.zip 4. Run autoconfig on dbtier

Run adpreclone.pl on both Database tier & Application tier:

1. Run adpreclene.pl on database tier perl adpreclone.pl dbTier 2. Run adpreclone.pl on apps tier. perl adpreclone.pl appsTier

------------------------------R12.1.3 installation completed-------------------------------

Faced issues in maverick:

1. While opening Approvals Management Administrator & Approval Management Business Analyst the following error occurs.

Troubleshooting:
1. Remove the responsibilities of Approvals Management Administrator & Approvals Management Business Analyst if already added to a particular user. 2. Do not assign these new responsibilities :
Approvals Management Business Analyst Approvals Management Administrator directly to a user, this will not work. 3. For the responsibilities to work, AME Roles need to be assigned to the user and data grant has to be given. 4. Follow the steps below to grant AME Access to a User : AME has implemented Role Based Access Model (RBAC) AME.B onwards. The following information would help you in setting up AME in R12.

a) AME has 5 seeded roles Approvals Management Administrator Approvals Management Analyst Approvals Management System Viewer Approvals Management System Administrator Approvals Management Process Owner The description of each of the roles can be found in AME.B implementation guide(ame.uk.oracle.com) b) AME can be accessed if sufficient functional grants are available. Each of the above 5 roles has specific set of functional grants. By assigning the roles to user, the functional grants will be available to user and hence he can access those functions/pages. c) Role can be assigned to user as follows: Login as Administrator Select the responsibility "User Management" Select "Users" screen Search for the user to whom you wish to grant AME roles. In the results table, click on update icon. In the update user page, user details can be seen along with a list of roles available to user Click on "Assign Roles" Select roles from the resulting LOV and click on Apply. d) Each of the 5 seeded AME roles, when assigned to a user, result in "Indirect" assignment of AME responsibilities to the user. e) Now the functional access to user has been successfully setup. f) AME restricts access to "AME Transaction Types" using Data Security. To access AME and use it, user needs to select a transaction type. But the transaction types that the user can select in the AME Dashboard is restricted by data security. g) Access to AME transaction types to a user can be setup as follows: Login as Administrator Select Functional Administrator responsibility Select Grants Tab

 Click on Create Grant Select "Specific User" as grantee type Select the User as grantee key Select "AME Transaction Types" as object In the next page there will be 3 options for instance type: 1. All rows: This grants access to all AME Transaction Types to the User 2. Instance: This grants access to the AME Transaction Type(1) specified by the following parameters: FND_APPLICATION_ID => Application ID of the application to which the transaction type belongs TRANSACTION_TYPE_ID => Unique identifier of the AME Transaction type within application 3. Instance set: This grants access to AME Transaction Types(>=1) specified by the following parameters: * Use the seeded instance set "AME Transaction Type Instance Set" * In the next page select FND_APPLICATION_ID as Parameter1 and a wild card search string for TRANSACTION_TYPE_ID as Parameter2. In the next page, select "AME Calling Applications" as the permission set Review and Finish. 5. Finally ensure that, the property : jbo.jdbc_bytes_conversion = jbo should be removed or commented in $COMMON_TOP/java/oracle/jbo/server/jboserver.properties. Clear cache, bounce apache server. Retest the issue.

Screen not opened when we click the responsibility:

1. It is a plug-in problem. Just remove the plug-in and reinstall it on the PC. 2. Allow the pop-ups.