The patch directory doesn't match the patch id | Oracle Forms

Issues: While applying the patch 17459191, we were getting the below mentioned error:

The patch directory 17459191 doesn't match the patch id. 
ERROR: OPatch failed during pre-reqs check. 
OPatch returns with error code = 150 

Solution:
One of the prerequisite mentioned in the patch was missing and has not been taken care 
i.e. Upgrade to the latest OUI 10.1 by downloading and installing the same from bug 6640838

One important note while upgrading the OUI is go for the custom install and then Expand All and select the "Installer SDK Component 10.1.0.6.0"

Once I upgraded the OUI the error was resolved while applying the patch

BEA-149205 Failed to initialize the application 'em' due to error java.lang.ClassNotFoundException: javax.faces.application.ProjectStage

Issue: After the upgrade of ADF from 11.1.1.6 to 11.1.2.2(by applying Patch 13656372 & 13656274), when we tried to access the weblogic EM page it was not coming up and throwing some error. In the logfile the below mentioned logs were present:

<Error> <Deployer> <BEA-149205> <Failed to initialize the application 'em' due to error java.lang.ClassNotFoundException: javax.faces.application.ProjectStage.
java.lang.ClassNotFoundException: javax.faces.application.ProjectStage
        at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
        at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
        at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:64)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:306)

Web Page:

Solution: After applying the patches we need to Upgrade the ADF component of the domain which was missed.

Follow the below steps to Upgrade the ADF component in domain.

1. Go to location  MW_HOME/oracle_common/common/bin
2. Invoke wlst.sh
3. Execute the command
upgradeADF('/u01/app/oracle/product/Middleware/user_projects/domains/<your_domain_name>') 

ORA-39127: unexpected error from call to "EXFSYS"."DBMS_EXPFIL_DEPASEXP" | while using expdp or exp

Issue: During a full database export using the utilities exp or expdp we see the below error.

ORA-39127: unexpected error from call to "EXFSYS"."DBMS_EXPFIL_DEPASEXP" 

Datapump Export log(expdp)

ORA-39127: unexpected error from call to "EXFSYS"."DBMS_EXPFIL_DEPASEXP"."SYSTEM_INFO_EXP"
ORA-44002: invalid object name
ORA-06512: at "SYS.DBMS_ASSERT", line 316
ORA-06512: at "SYS.DBMS_METADATA", line 9263
Processing object type DATABASE_EXPORT/SYSTEM_PROCOBJACT/PRE_SYSTEM_ACTIONS/PROCACT_SYSTEM
Processing object type DATABASE_EXPORT/SYSTEM_PROCOBJACT/PROCOBJ
ORA-39127: unexpected error from call to "EXFSYS"."DBMS_EXPFIL_DEPASEXP"."SYSTEM_INFO_EXP"
ORA-44002: invalid object name
ORA-06512: at "SYS.DBMS_ASSERT", line 316

Conventional Export log(exp)

EXP-00008: ORACLE error 6550 encountered
ORA-06550: line 1, column 14:
PLS-00201: identifier 'EXFSYS.DBMS_EXPFIL_DEPASEXP' must be declared
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
EXP-00083: The previous problem occurred when calling EXFSYS.DBMS_EXPFIL_DEPASEXP.schema_info_exp

Solution:

The account used internally to access the EXFSYS schema, which is associated with the Rules Manager and Expression Filter feature. This feature enables the building of complex PL/SQL rules and expressions. The EXFSYS schema contains the Rules Manager and Expression Filter DDL, DML, and associated metadata. EXFSYS schema is missing in the database. To install the EXFSYS schema execute the script "catexf.sql" as SYS user.

connect as sysdba and execute the below script

@?/rdbms/admin/catexf.sql

ORA-00119: invalid specification for system parameter LOCAL_LISTENER

Issue: ORA-00119: invalid specification for system parameter LOCAL_LISTENER
ORA-00132: syntax error or unresolved network name 'LISTENER_ORCL'

Solution: There are two methods by which this error can be removed.

Method 1:

Step 1: Make a entry in the tnsnames.ora as mentioned below
LISTENER_ORCL =
  (ADDRESS = (PROTOCOL = TCP)(HOST = linux01.com)(PORT = 1521))

Where LISTENER_ORCL is the parameter value for LOCAL_LISTENER which is mentioned in pfile/spfile
PORT is the listener port you are using.
Also there is no need to modify the pfile/spfile.


Step 2: start the database

Method 2:

Step 1: If you are using a spfile for starting up your database, create a pfile from it.

Step 2: Edit the pfile and remove the parameter LOCAL_LISTENER

Step 3: Create spfile from the pfile and start the database