Soban.dba

Hi, During running long report in EBS R12.2 usually give below error and here the solution, I used multiple times and it works. Error: java.lang.OutOfMemoryError: Java heap space at oracle.jdbc.driver.T4CCallableStatement.allocateTmpByteArray(T4CCallableStatement.java:259) at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:204) at oracle.jdbc.driver.T4CCallableStatement.executeForRows(T4CCallableStatement.java:1111) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1488) at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3769) at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3954) at oracle.jdbc.driver.OracleCallableStatement.execute(OracleCallableStatement.java:9353) at oracle.jdbc.driver.OraclePreparedStatementWrapper.execute(OraclePreparedStatementWrapper.java:1539) at oracle.apps.fnd.cp.opp.OPPAQMonitor.waitForMessage(OPPA

 Need to find all the availble options in ADOP, here is the command. adop -examples [oracle@preprod appsTier]$ adop -examples Applications DBA Online Patching Tool (adop) See Oracle E-Business Suite Maintenance Guide for a full description of adop features, operation, and usage. Standard Online Patching Cycle:     In Oracle E-Business Suite Release 12.2, patches are normally applied     using an online patching cycle.  The online patching cycle consists of     five phases which are executed in order.     Example - Typical online patching cycle:         source <ebs_root>/EBSapps.env run         adop phase=prepare         adop phase=apply patches=123456         adop phase=finalize         adop phase=cutover         source <ebs_root>/EBSapps.env run         adop phase=cleanup     Note that after cutover the command line environment should be re-loaded     as the run edition file system has changed.     In a multi-node deployment, adop commands are only executed from the   

Adop in EBS R12.2 is a messy thing, we will be welcome every time with new type of error, to analyze the error is also a big job, for that purpose oracle has very good tools and techniques. Hope this will be helpful if you ever encountered in some unknown issue with adop. To debug Online Patching issues which utilize the adop (AD Online Patching) tool we need to collect adop log files located in the <INSTALL BASE>/fs_ne/EBSapps/log/adop directory   e.g. /u01/PROD/fs_ne/EBSapps/log/adop Each cycle of adop creates a subdirectory corresponding to the patch session ID, e.g. /u01/PROD/fs_ne/EBSapps/log/adop/1 /u01/PROD/fs_ne/EBSapps/log/adop/2 etc..etc When running adop the on-screen terminal output will mention which adop session ID  is in use. e.g. /u01/PROD/fs_ne/EBSapps/log/adop/ 9 /apply_20121011_024437 Online Patching Log Analyzer Utility (this new feature is delivered by AD and TXK C Delta 4 patches) This utility analyzes adop log directories for errors and war