Wednesday 20 August 2014

Arabic forms are not opening in R12.1.3

Soution:



Refered Note: 292942.1

1.A) Create the "9i behavior" file set:
you have 2 way's to do this:
1* OR Automatically (If you have perl installed)

run the $ORACLE_HOME/nls/data/old/cr9idata.pl script to create the $ORACLE_HOME/nls/data/9idata directory.
$ORACLE_HOME/perl/bin/perl $ORACLE_HOME/nls/data/old/cr9idata.pl
sample output:
Creating directory /grdbms/64bit/patchdb/app/oracle/product/p12101a/nls/data/9idata ...
Copying files to /grdbms/64bit/patchdb/app/oracle/product/p12101a/nls/data/9idata...
Copy finished.
Please reset environment variable ORA_NLS10 to /grdbms/64bit/patchdb/app/oracle/product/p12101a/nls/data/9idata!
After creating the fileset check that $ORACLE_HOME/nls/data/9idata contains more than 500 files
ls -l $ORACLE_HOME/nls/data/9idata | wc -l
note: if $ORACLE_HOME/nls/data/9idata already exist and you want to redo the file generation "to make sure" then it might be a good idea to shutdown all oracle processes using this ORACLE_HOME
2* OR Manually
note: if $ORACLE_HOME/nls/data/9idata already exist and you want to redo the file generation "to make sure" then it might be a good idea to shutdown all oracle processes using this ORACLE_HOME

a) make a new subdirectory under $ORACLE_HOME/nls/data called "9idata"

b) COPY all files in $ORACLE_HOME/nls/data/ to $ORACLE_HOME/nls/data/9idata

c) COPY all files from $ORACLE_HOME/nls/data/old to $ORACLE_HOME/nls/data/9idata
you will need to overwrite some files - this is normal.

on Unix this means:
* make sure the $ORACLE_HOME is set correctly
rm -r $ORACLE_HOME/nls/data/9idata
mkdir $ORACLE_HOME/nls/data/9idata
cp $ORACLE_HOME/nls/data/*.* $ORACLE_HOME/nls/data/9idata
cp $ORACLE_HOME/nls/data/old/*.* $ORACLE_HOME/nls/data/9idata
The ORDER is important, FIRST do point B) then do point C), do NOT inverse this.
d)After creating the 9i fileset check that $ORACLE_HOME/nls/data/9idata contains more than 500 files
* The $ORACLE_HOME/nls/data/old directory only contains the changed files, so you need to overwrite copy the more than 500 files of $ORACLE_HOME/nls/data/ to $ORACLE_HOME/nls/data/9idata and then overwrite some files in $ORACLE_HOME/nls/data/9idata with the ones found in $ORACLE_HOME/nls/data/old .
* You cannot use Oracle9i (or earlier) NLB files in Oracle10g and up.
* You cannot use the new Oracle10g definitions in Oracle9i and lower.
4.B) Enable the Oracle9i behavior:
After creating the "9i behavior" file set you need to point ORA_NLS10 to $ORACLE_HOME/nls/data/9idata instead of the default $ORACLE_HOME/nls/data/ directory and start the database *and* listener on the server using the new setting.

NOTE:  The creation of the "Oracle9i behavior" files and setting ORA_NLS10 to $ORACLE_HOME/nls/data/9idata should be done on the database server AND on all 10g/11g clients which connect to this system (!).
On Unix you need to set the ORA_NLS10 variable for the Oracle user or any other Unix user that stops and starts the listener/database. Make sure to not forget any startup scripts when the server starts up.
When using RAC you need ALSO set the ORA_NLS10 variable using srvctl
$ srvctl setenv database -d <dbname> -t ORA_NLS10=$ORACLE_HOME/nls/data/9idata
-- set it for all RAC managed listeners
$ srvctl setenv listener -t ORA_NLS10=$ORACLE_HOME/nls/data/9idata
-- set it for one specific listener
$ srvctl setenv listener -l <listener_name> -t ORA_NLS10=$ORACLE_HOME/nls/data/9idata


$ srvctl stop database -d <dbname>
$ srvctl stop listener
$ srvctl start listener
$ srvctl start database -d <dbname>

After the restart of the database and listener check the result using sqlplus from the database $ORACLE_HOME 
export ORA_NLS10=$ORACLE_HOME/nls/data/9idata
sqlplus / as sysdba
select to_char(to_date( '18/04/2009', 'DD/MM/YYYY'),'DD-MON-YYYY', 'NLS_DATE_LANGUAGE=FRENCH') from dual;
-- this should give 18-AVR-2009
if this is correct then the *database* side is fine.


    

Tuesday 5 August 2014

Patch is hanging while applying HRMS RUP6 patch

Issue Details:

 Patch is running XDOLoader.class file

 By seeing worker log file getting below error I found below error

SQLState: null
Message: Io exception: There is no process to read data written to a pipe.
Vendor: 17002
java.sql.SQLException: Io exception: There is no process to read data written to a pipe.
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:334)
at oracle.jdbc.ttc7.TTC7Proto .handleIOException(TTC7Protocol.java:3664)
at oracle.jdbc.ttc7.TTC7Protocol.logon(TTC7Protocol.java:353)
at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:371)
at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:551)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:351)
at java.sql.DriverManager.getConnection(DriverManager.java:559)
at java.sql.DriverManager.getConnection(DriverManager.java:211)
at oraConn.main(oraConn.java:9)

Soution:

 Kill the current patch session and restart the patch session with low workers.

See Metalink note :1459733.1

Sunday 3 August 2014

Concurrent request is failed with REP-0124,REP-0002 Errors in R12

Symptoms:

Enter Password:
REP-0081: Error during file I/O operation.
REP-0124: Unable to write to the temporary file.
scafa 3
REP-0002: Unable to retrieve a string from the Report Builder message file.
REP--1870639101:
REP-0069: Internal error
REP-57054: In-process job terminated:Terminated with error:
REP--1870639101: Error during file I/O operation.
REP-0124: Unable to write to the temporary file.
scafa 3
REP-0002: Unable to retrieve a string from the Report Builder message file.
REP--1870639101:

Solution:
1. Check the utl_file_dir path wich is creating temp files
2. Delete some temp files from /tmp (utl_file_dir) location
3.If you still facing the issue, check the size of report which is user trying to generate using concurrent request and ask the user to reduce the report size using parameters.
4. Still you are facing issue log SR.

Monday 28 July 2014

POST CLONE STEPS in 11i/R12:
++++++++++++++++++++++++++++++++++++++++++
1.select distinct OUTFILE_NODE_NAME from FND_CONCURRENT_REQUESTS ;

2.select distinct LOGFILE_NODE_NAME from FND_CONCURRENT_REQUESTS ;
3.select node_name , status from fnd_nodes


   CHECK ALL THE NODE NAMES IF YOU FOUND ANY SOURCE NODE NAMES THEN FOLLOW THE STEPS BELOW.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++==
1. Make a backup copy of the FND_RUN_REQUESTS, FND_CONCURRENT_REQUESTS, and
FND_CONCURRENT_PROCESSES tables

2. Run the following statements to remove the rows that refer to the node that
is no longer available.. (ERP is an example value)

delete FND_RUN_REQUESTS WHERE parent_request_id
in (select request_id from FND_CONCURRENT_REQUESTS where
upper(LOGFILE_NODE_NAME) = 'ERP'
or upper(OUTFILE_NODE_NAME) = 'ERP');

delete FND_CONCURRENT_REQUESTS where upper(LOGFILE_NODE_NAME) = 'ERP' or
upper(OUTFILE_NODE_NAME) = 'ERP';

delete FND_CONCURRENT_PROCESSES where upper(NODE_NAME) = 'ERP';


commit;




PATCH IS HANGING BY ALLOCATING MORE NUMBER OF USERS

1459733.1
ORA-00020 Error in Alert log file:

How to increase PROCESSES initialization parameter:

1.    Login as sysdba
    sqlplus / as sysdba
   
2. Check Current Setting of Parameters
    sql> show parameter sessions
    sql> show parameter processes
    sql> show parameter transactions

3.    If you are planning to increase "PROCESSES" parameter you should also plan to increase "sessions and "transactions" parameters
    A basic formula for determining  these parameter values is as follows:
   
        processes=x
        sessions=x*1.1+5
        transactions=sessions*1.1
       
4.    These paramters can't be modified in memory. You have to modify the spfile only (scope=spfile) and bounce the instance.
    sql> alter system set processes=500 scope=spfile;
    sql> alter system set sessions=555 scope=spfile;
    sql> alter system set transactions=610 scope=spfile;
    sql> shutdown abort
    sql> startup
oracle.apps.fnd.framework.OAException: Illegal method call because there is no database connection.

Please review the document Login Fails Intermittently With: Application: Fnd, Message Name: FND_NO_DATABASE_CONNECTION (Doc ID 1298103.1)

12.1.2 and 12.1.1 Customers
Apply and test patch 9908921
Be sure to stop and start application tier services after the patch is applied

12.1.3 Customers
Apply and test patch 11832737


Internal Error --- 500

1. Shutdown the http server, oc4j and opmn services using following scripts at $INST_TOP/admin/scripts

adapcctl.sh stop
adoacorectl.sh stop
adformsctl.sh stop
adoafmctl.sh stop
adopmnctl.sh stop

Note: If its during Production Down Time or a UAT/TEST Instance then all the middle tier services can be shutdown.

2. Backup/Delete existing log files in:

$LOG_HOME/ora/10.1.3/Apache
$LOG_HOME/ora/10.1.3/j2ee
$LOG_HOME/ora/10.1.3/opmn

Note: If the issue is easily reproducible it is safe to delete the log files (unless otherwise required)

3. Enable HTTP/OC4J/OPMN debug logging

a) Enable http ODL logging, Edit httpd.conf file, add the following to the end of file $ORA_CONFIG_HOME/10.1.3/Apache/Apache/conf/httpd.conf

OraLogMode oracle
OraLogSeverity TRACE:32
OraLogDir $LOG_HOME/ora/10.1.3/Apache/oracle

Note: Please use the full path to $LOG_HOME e.g. OraLogDir /u01/inst/apps/JCB_atg/logs/ora/10.1.3/Apache/oracle

b) Make the following directory which will be holding the created Apache ODL log files

> mkdir $LOG_HOME/ora/10.1.3/Apache/oracle


4. Increase OC4J logging for oacore

a) edit j2ee-logging.xml adjust the following in file: $ORA_CONFIG_HOME/10.1.3/j2ee/oacore/config/j2ee-logging.xml

<logger name='oracle' level='TRACE:32' useParentHandlers='false'>


b) Increase OC4J logging for forms:
edit j2ee-logging.xml adjust the following in file:
$ORA_CONFIG_HOME/10.1.3/j2ee/forms/config/j2ee-logging.xml
<logger name='oracle' level='TRACE:32' useParentHandlers='false'>

c) edit orion-web.xml adjust the following in file:
$ORA_CONFIG_HOME/10.1.3/j2ee/oacore/application-deployments/oacore/html/orion-web.xml

param-name>debug_mode</param-name>

<param-value>true</param-value>


5. Increase OPMN Logging

a) edit opmn.xml adjust the following in file:
$ORA_CONFIG_HOME/10.1.3/opmn/conf/opmn.xml

<debug path="/u01/inst/apps/JB_atg/logs/ora/10.1.3/opmn/opmn.dbg" comp=" internal;ons;pm" rotation-size="1500000" rotation-hour="0" />


6. Use the ojspcompile.pl perl script to perform a manual pre-compilation of the JSP pages. The following command will compile all the JSP pages and build up the JSP cache again.

Unix: # $FND_TOP/patch/115/bin/perl ojspCompile.pl --compile --flush -p 2

Windows: C:> <FND_TOP>\patch\115\bin\perl -x ojspCompile.pl --compile --flush

This utility is also used by the AD utilities to perform this action, for example after patches are applied which replaced 1 or more JSP pages. Since this a manual action which also requires understanding of parameters to be passed to have the right (set of) JSP compiled this option may be error-prone.




7. Startup the http server, oc4j and opmn (reverse the startup sequence above)

8. Reproduce the issue

- Access the following urls and inform support if the url was successful or unsuccessful (with the resulting error):

http://<server>.<domain>:<PORT>/OA_HTML/ServletPing
http://<server>.<domain>:<PORT>/OA_HTML/OA.jsp?OAFunc=OAHOMEPAGE
http://<server>.<domain>:<PORT>
http://<server>.<domain>:<PORT>/OA_HTML/OAInfo.jsp
http://<server>.<domain>:<PORT>/OA_HTML/jsp/fnd/aoljtest.jsp
http://<server>.<domain>:<PORT>/OA_MEDIA/FNDLOGOL.gif
http://<server>.<domain>:<PORT>/forms/frmservlet
http://<hostname.domainname>:<port>/OA_HTML/fndvald.jsp?username=sysadmin&password=<sysadmin_password>


9. Upload the FRESH log files at:

$LOG_HOME/ora/10.1.3/Apache
$LOG_HOME/ora/10.1.3/j2ee
$LOG_HOME/ora/10.1.3/opmn
https://support.oracle.com/epmos/adf/images/t.gif




Action plan-2
1.Choose another value for $CONTEXT_FILE variable: s_java_object_cache_port

2.Make sure its the same on all apps tiers

3.Run AutoConfig and retest


NOTE:issue is resolved

Gather Schema concurrent request is failed

+---------------------------------------------------------------------------+
Application Object Library: Version : 12.0.0

Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.

FNDGSCST module: Gather Schema Statistics
+---------------------------------------------------------------------------+

Current system time is 26-JUN-2013 08:16:48

+---------------------------------------------------------------------------+

**Starts**26-JUN-2013 08:16:49
**Ends**26-JUN-2013 08:49:42
ORA-0000: normal, successful completion
+---------------------------------------------------------------------------+
Start of log messages from FND_FILE
+---------------------------------------------------------------------------+
In GATHER_SCHEMA_STATS , schema_name= ALL percent= 10 degree = 8 internal_flag= NOBACKUP
stats on table AQ$_WF_CONTROL_P is locked
stats on table FND_CP_GSM_IPC_AQTBL is locked
stats on table FND_SOA_JMS_IN is locked
stats on table FND_SOA_JMS_OUT is locked
stats on table GAT_REQ_QTBL is locked
Error #1: ERROR: While GATHER_TABLE_STATS:
object_name=GL.JE_BE_LINE_TYPE_MAP***ORA-20001: invalid column name or duplicate columns/column groups/expressions in method_opt***
Error #2: ERROR: While GATHER_TABLE_STATS:
object_name=GL.JE_BE_LOGS***ORA-20001: invalid column name or duplicate columns/column groups/expressions in method_opt***
Error #3: ERROR: While GATHER_TABLE_STATS:
object_name=GL.JE_BE_VAT_REP_RULES***ORA-20001: invalid column name or duplicate columns/column groups/expressions in method_opt***
+---------------------------------------------------------------------------+
End of log messages from FND_FILE
+---------------------------------------------------------------------------+


+---------------------------------------------------------------------------+
Executing request completion options...

Output file size:
0


Finished executing request completion options.

+---------------------------------------------------------------------------+
Concurrent request completed
Current system time is 26-JUN-2013 08:49:42




SOLUTION:

1.       Please also review "ORA-20005 WHEN GATHERING STATISTICS FOR EBS APPS 11i or R12 IN Database 10G or 11G [ID 375351.1]" for the messages
2.       Please review "Gather Schema Statistics fails with Ora-20001 errors after 11G database upgrade [ID 781813.1]" which appears to match your issue.
Cause
There are two reasons for that error message:
1 ) There are duplicate rows on FND_HISTOGRAM_COLS table for JE_BE_LINE_TYPE_MAP table.
Because of this problem, FND_STATS tries to gather histogram information using wrong command and
it fails with ora-20001 errors.

Following SQL should have returned one row , not two.
SQL>select column_name, nvl(hsize,254) hsize
from FND_HISTOGRAM_COLS
 
where table_name = 'JE_BE_LINE_TYPE_MAP'
order by column_name;

COLUMN_NAME HSIZE
------------------------------ ----------
SOURCE 254
SOURCE 254

Since there are two rows in histograms table, FND_STATS creates following command to gather statistics on table 'JE_BE_LINE_TYPE_MAP' :
 dbms_Stats.gather_table_stats(OWNNAME => 'GL', TABNAME 
=>'JE_BE_LINE_TYPE_MAP',METHOD_OPT=>'FOR ALL COLUMNS SIZE 1 FOR COLUMNS SOURCE SIZE 254 FOR
 
COLUMNS SOURCE SIZE 254');
 Above command will work on 9i and 10G databases but it will fail with ora-20001 errors on 11G.

2) Column does not exist on the table but still listed in FND_HISTOGRAMS_COL table.
You can use following SQL to identify. SQL will prompt for table name, use table name from the errors. In above examples you can use FII_FIN_ITEM_HIERARCHIES.
select hc.table_name, hc.column_name
from FND_HISTOGRAM_COLS hc , dba_tab_columns tc
where hc.table_name ='&TABLE_NAME'
and hc.table_name= tc.table_name (+)
and hc.column_name = tc.column_name (+)
and tc.column_name is null;
Solution

Find out all duplicates and/or obsolete rows in FND_HISTOGRAM_COLS and delete one of them.
Remember to take backup of the FND_HISTOGRAM_COLS table before deleting any data.
-- identify duplicate rows

select table_name, column_name, count(*)
from FND_HISTOGRAM_COLS
group by table_name, column_name
having count(*) > 1;
-- Use above results on the following SQL to delete duplicates

delete from FND_HISTOGRAM_COLS
where table_name = '&TABLE_NAME'
and  column_name = '&COLUMN_NAME'
and rownum=1;
-- Use following SQL to delete obsoleted rows

delete from FND_HISTOGRAM_COLS
where (table_name, column_name) in
 
  (
   select hc.table_name, hc.column_name
   from FND_HISTOGRAM_COLS hc , dba_tab_columns tc
   where hc.table_name  ='&TABLE_NAME'
   and hc.table_name= tc.table_name (+)
   and hc.column_name = tc.column_name (+)
   and tc.column_name is null
  );
1-----à
Cause
This can happen with Advance Queue tables. In 10g, if a queue is created or recreated during the upgrade, automatic statistics gather is locked (disabled) on these queue.
The following statement can be used to check the tables which have statistics locked:
    select owner, table_name, stattype_locked
    from dba_tab_statistics
    where stattype_locked is not null; 
Solution
Unlock statistics gathering on those queues running the commands below. To unlock all the tables in a schema at once:
exec dbms_stats.unlock_schema_stats('schema_owner'); 
OR
To unlock individual tables (need to run for all tables individually):
exec dbms_stats.unlock_table_stats('table_owner','table_name');
Examples:
SQL> exec dbms_stats.unlock_schema_stats ('AR'); 
SQL> exec dbms_stats.unlock_table_stats('AR', 'AR_REV_REC_QT'); 





1. If CPU is maxing out (100%), then you may have no other choice than to kill off the sessions/processes that are consuming the high CPU.
This is normally due to spinning of the frmweb process due to returning rows from LOVs by end users that don't attempt to filter (perform blind query) in core forms.

When an end user login to forms and start working with LOV within core forms sometimes and according to the search criteria that the user will provide to filter the results in LOV, it may fetch huge numbers of records in which causes the frmweb process to grow very large, and in extreme cases this can even lock up the current process or even the whole machine.

So when executing a LOV query, every row is fetched into memory on the middle tier, the frmweb process can get extremely large, and the larger it gets the more likely it is to start paging.
Eventually it starts consuming excessive CPU just paging the process in and out of memory, which is probably what you can see here in this case as the amount of memory consumed when the LOV records are fetched into memory obviously depends on the amount of data in each record.

This has been mentioned in the following bug:
Bug 6519700 - ESC: CSE: R12SIP: 6513826 FRMWEB RUNAWAY PROCESS CONSUMING 100% CPU-MIDDLE TIER


Therefore, if the FRMWEB process is consuming near 100% CPU and sustaining this consumption, you may have to kill off the process to resume normal operation.


2. You may check the directory: $FORMS_TRACE_DIR on forms node. The FRMWEB process may create a coredump file here which may lead to clues of what caused the issue. The file is normally named: frmweb_dump_<PID>

Where PID is the process ID of the user running the form session.

Adrelink is exiting with status 1: for MSC Product
Issue:

adrelink is exiting with status 1: In 11i/R12  & RHEL 5.4 while patching

Fix:

STEP1:  cd $AD_TOP/bin

STEP2:  Take backup of the existing adrelinknew.sh

cp -rp  adrelinknew.sh  adrelinknew.sh_orig

STEP3: Edit the adrelinknew.sh

 vi adrelinknew.sh

Change CPP_LDFLAGS  as below

From:

CPP_LDFLAGS=' -L$(ORACLE_HOME)/lib -L$(ORACLE_HOME)/lib/stubs -lclntsh'

 To:

#CPP_LDFLAGS=' -L$(ORACLE_HOME)/lib -L$(ORACLE_HOME)/lib/stubs -lclntsh'
CPP_LDFLAGS=' -L$(ORACLE_HOME)/lib -L$(ORACLE_HOME)/lib/stubs -lclntsh -Wl,--noinhibit-exec'

:wq! --> save & exit
Symptoms:

Users unable to open the out files.

Concurrent requests failed with “Post-processing of request failed error message”

One or more post-processing actions failed. Consult the OPP service log for details.

No further attempts will be made to post-process this request.

Cause:

The concurrent manager process was able to successfully invoke the Output Post-Processor (OPP) but encountered a timeout as the OPP takes longer than the value assigned to complete the job.

 Solution:

Increase the value of profile Concurrent: OPP Response Timeout . Bounce Apache and retest.

If the issue still exists, perform the following steps.

Increase the number of Output Post Processors as follows:

Increase the number of processes for Output Post Processor.

Additionally, ensure there is a setting of  oracle.apps.fnd.cp.opp.OPPServiceThread:2:0:max_threads=5 under Parameters.
CONCURRENT REQUEST IS FAILED WITH ERROR 127:

/oracle/appltest/apps/tech_st/10.1.2/bin/rwrun: error while loading shared libraries: librw.so: cannot open shared object file: No such file or directory
++++++++++++++++++++++++++++++++++++++++++++++++++++++++
1) unlink /usr/lib/libXtst.so.6
ln -s /usr/X11R6/lib/libXtst.so.6.1 /usr/lib/libXtst.so.6

2) cd 10.1.2 $ORACLE_HOME/reports/lib
make -f ins_reports.mk install

3) Relink application executables from the adadmin utility.

4) Bounce the services.

5) Retry failing concurrent requests.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++

Note: 551795.1 - How to change the default branding on the homepage which shown as "E-Business Suite" ?
Note: 395445.1 - Oracle Application Framework Profile Options Release 12
Note: 421636.1 - How to replace the default Oracle Logo with a Customized Logo?
Note: 459350.1 - R12 - Image Size Problem On Login Page

ISSUE IS APPLICATIONS ARE RUNNING SLOW
______________________________________

--> To find out the cause, acion plan as follows

    *Take awr,ash and addm reports
    *Find out the cause by using reports, if it is query take a sqlid
    *Then take a SQLT(SQLTXPLAIN) tool report for that query (Doc ID 215187.1)
 
--> SOLUTION:

A) From AWR report, seems you have high waits on "Latch: cache buffer chain":

Latch: cache buffer chain may occur due to high buffer get queries/hot blocks/high concurrent requests for similar data.

The more rows are in one block the higher the risk for cache buffer chain contentions when many sessions accessing the same block concurrently.
Reducing the number of rows per block may help to overcome cache buffer chain contention as sessions may not request to access the same block so frequently.

Well we need to find the hot block for latch: cache buffers chains.
See : How To Identify a Hot Block Within The Database Buffer Cache. (Doc ID 163424.1)

In order to reduce contention for this object the following mechanisms can be put in place:

1) Examine the application to see if the execution of certain DML and SELECT statements can be reorganized to eliminate contention on the object. See:
Note:1342917.1 Troubleshooting 'latch: cache buffers chains' Wait Contention
2) Decrease the buffer cache -although this may only help in a small amount of cases.
3) DBWR throughput may have a factor in this as well. If using multiple DBWR's then increase the number of DBWR's. See:
Note:62172.1 - Understanding and Tuning Buffer Cache and DBWR
4) Increase the PCTFREE for the table storage parameters via ALTER TABLE or rebuild. This will result in less rows per block.
5) Consider implementing reverse key indexes (if range scans aren't commonly used against the segment)

B) About the top sql consumer with sqlid =a49xsqhv0h31b (Eg sqlid)

Optimizer statistics for table "APPLSYS"."FND_CONC_REQUEST_ARGUMENTS" are stale.
The optimizer requires up-to-date statistics for the table and its indices in order to select a good execution plan.

- Consider collecting optimizer statistics for this table and its indices.

execute dbms_stats.gather_table_stats(ownname => 'APPLSYS', tabname =>
'FND_CONC_REQUEST_ARGUMENTS', estimate_percent =>
DBMS_STATS.AUTO_SAMPLE_SIZE, method_opt => 'FOR ALL COLUMNS SIZE
AUTO', cascade => TRUE);
WHEN PALTFORM MIGRATION IS DONE IN MY SCENARIO REDHAT LINUX 5.8 TO REDHAT LINUX 6.3 DO THE FOLLOWING ACTIONS

Has the following related to installing patch 12415211 been done as per Note 761566.1 : "Oracle E-Business Suite Installation and Upgrade Notes Release 12 (12.1.1) for Linux x86-64" :

$ cd <12.1_INSTALL_DIR>/apps/tech_st/10.1.2/lib
$ cp -p -R stubs stubsORIG
$ cd stubs
$ cp <PATCH_INSTALL_DIR>/12415211/files/lib/stubs/libgcc_s-2.3.2-stub.so .
$ ln -s libgcc_s-2.3.2-stub.so libgcc_s.so.1
$ ln -s libgcc_s.so.1 libgcc_s.so

Adrelink is exiting with status 1: for MSC Product
Issue:

adrelink is exiting with status 1: In 11i/R12  & RHEL 5.4 while patching

Fix:

STEP1:  cd $AD_TOP/bin

STEP2:  Take backup of the existing adrelinknew.sh

cp -rp  adrelinknew.sh  adrelinknew.sh_orig

STEP3: Edit the adrelinknew.sh

 vi adrelinknew.sh

Change CPP_LDFLAGS  as below

From:

CPP_LDFLAGS=' -L$(ORACLE_HOME)/lib -L$(ORACLE_HOME)/lib/stubs -lclntsh'

 To:

#CPP_LDFLAGS=' -L$(ORACLE_HOME)/lib -L$(ORACLE_HOME)/lib/stubs -lclntsh'
CPP_LDFLAGS=' -L$(ORACLE_HOME)/lib -L$(ORACLE_HOME)/lib/stubs -lclntsh -Wl,--noinhibit-exec'

:wq! --> save & exit

Step to Find APPS PASSWORD :


STEP 1 :

sqlplus> sqlplus system/system_password

sqlplus / as sysdba

STEP 2 :  (Create Function for to decrypt the encrypted password)


SQL> create FUNCTION apps.decrypt_pin_func(in_chr_key IN VARCHAR2,in_chr_encrypted_pin IN VARCHAR2)
RETURN VARCHAR2
AS
LANGUAGE JAVA NAME 'oracle.apps.fnd.security.WebSessionManagerProc.decrypt(java.lang.String,java.lang.String) return java.lang.String';
2 3 4 5
6 /

Function created.
STEP 3 : (Query for password)


SQL> select ENCRYPTED_FOUNDATION_PASSWORD from apps.fnd_user where USER_NAME='GUEST';

ENCRYPTED_FOUNDATION_PASSWORD
--------------------------------------------------------------------------------
ZG379C5C883FF56235BE975D075A6FD2E7A749279B7BFCE331530B443E86F41A1966E3E4B1864519
DB88BC07D58666AD837B


STEP 4: 

SQL> SELECT apps.decrypt_pin_func('GUEST/ORACLE','ZG379C5C883FF56235BE975D075A6FD2E7A749279B7BFCE331530B443E86F41A1966E3E4B1864519DB88BC07D58666AD837B') from dual;

APPS.DECRYPT_PIN_FUNC('GUEST/ORACLE','ZG379C5C883FF56235BE975D075A6FD2E7A749279B
--------------------------------------------------------------------------------
APPS

STEP 5: (Test apps password)
SQL> conn apps/APPS;

Connected.