u6678700.drv: VERY SLOW XDOLOADER(XDOLoader.class) TASK

Issue:

Performance issue for XDOLoader.class jobs


Cause:

The XDOLoader uses JDBC which uses the /dev/random
renaming /dev/random and creating a link to /dev/urandom called /dev/random Fixes the issue


Solution:

Rename /dev/random to /dev/random_org
Create a link to /dev/urandom called /dev/random

mv /dev/random /dev/random.bk
ln -s /dev/urandom /dev/random


Reference:

-12.1.1 UPGRADE FROM 11.5.10.2 VERY SLOW XDOLOADER TASK HANGS (Doc ID 1065393.1)

u6678700.drv : FAILED: file PO_VENDORS_OBS_F1.xdf

Action plan to avoid PO_VENDORS_OBS_F1.xdf job issue:

To implement the solution, please execute the following steps:

1) Drop index PO_VENDORS_F1

You can use command similar as:
SQL> drop index PO.PO_VENDORS_F1;

Restart the failed Worker using the adctrl utility in a second Shell session and continue.

Script otamlsw.odf Fails during Application of Patch 6678700

Action plan to avoid otamlsw.odf  job issue

Issue:

DROP INDEX OTA.OTA_CATEGORY_USAGES_TL_PK
AD Worker error:
The following ORACLE error:

ORA-02429: cannot drop index used for enforcement of unique/primary key

occurred while executing the SQL statement:

DROP INDEX OTA.OTA_CATEGORY_USAGES_TL_PK

AD Worker error:
Unable to compare or correct tables or indexes or keys
        because of the error above

Solution:

Disable the constraint OTA_EVENT_ASSOCIATIONS_UK2 as follows:

SQL> select * from dba_constraints
     where constraint_name = 'OTA_EVENT_ASSOCIATIONS_UK2'

SQL> alter table OTA_EVENT_ASSOCIATIONS disable constraint OTA_EVENT_ASSOCIATIONS_UK2;

Reference:

-Oracle SR 3-6974638882
-Doc ID 1312500.1: Under What Conditions Can Adding A Primary Key Constraint Not Create An Index?
-Doc ID 370633.1: ALTER TABLE DROP PRIMARY KEY CONSTRAINT DOES NOT DROP

Script Czhist.Sql Fails during Application of Patch 6678700

Execute below procedure to avoid issue (Script Czhist.Sql Fails during Application of Patch 6678700)

SQL> execute DBMS_STATS.UPGRADE_STAT_TABLE('APPLSYS','FND_STATTAB');

How to Unlock the stats for given tables

Identify the tables whose stats are locked by using below query:

Unlock the stats for given tables:

select owner, table_name, stattype_locked
from dba_tab_statistics
where stattype_locked is not null
and owner = 'APPLSYS' -- Schema Name

Unlock stats using below script:

SQL> exec dbms_stats.unlock_table_stats('owner', 'table_name');

For Example:

SQL> sho user
USER is "SYS"
SQL>
SQL> exec dbms_stats.unlock_table_stats('APPLSYS','AQ$_WF_CONTROL_P');

PL/SQL procedure successfully completed.

Unable to find an Output Post Processor service to post-process request in PCP environment

Problem Description:

Concurrent requests getting completed in warning status which are running on CM Admin node 2 in PCP environment.

Error in Log File:

POST-PROCESSING ---------+ Unable to find an Output Post Processor service to post-process request 13343094. Check that the Output Post Processor service is running.

Cause:

OPP manager does not exist on secondary admin node.

Solution:

In a Parallel Concurrent Processing (PCP) environment an need to create additional Output Post Processing (OPP) concurrent managers in nodes other than the primary node.

Reference:

How to Create a Second OPP Concurrent Manager in a Node Different Than The Primary Node (Doc ID 729883.1)

Intermittent Login issue R12.1 - 500 Internal Server Error

Problem Description:

Users are unable to get application login page.

Users are frequently getting below error while accessing the EBS application URL.

Cause:

This issue occurred due to low oacore heap size.

Solution:

Increase the oacore heap size and restart application services.

Change the parameters in $ORA_CONFIG_HOME/10.1.3/opmn/conf/opmn.xml

of both form nodes as shown below:

From:

-Xmx512M -Xms128M -XX:MaxPermSize=160M

To:

-Xmx1536M -Xms128M -XX:MaxPermSize=160M

Reference:

JVM: Guidelines to setup the Java Virtual Machine in Apps E-Business Suite 11i and R12 (Doc ID 362851.1)