opatch apply fails with “Error in checking for identical patches for composite patch” error

ERROR:

Attempting to install a composite patch fails with the following message

[Nov 22, 2014 11:36:08 AM]   OUI-67073:UtilSession failed: Error in checking for identical patches for composite patch. This means a constituent to be applied has an earlier creation date than a constituent installed in the Oracle Home. This patch is improperly packaged and will not be applied.
[Nov 22, 2014 11:36:08 AM]   Finishing UtilSession at Sat Nov 22 11:36:08 EST 2014
[Nov 22, 2014 11:36:08 AM]   Log file location: /apps/opt/oracle/product/11.2.0/db_1/cfgtoollogs/opatch/opatch2014-11-22_11-35-53AM_1.log
[Nov 22, 2014 11:36:08 AM] 
[Nov 22, 2014 11:36:08 AM]   StackTrace: oracle.opatch.opatchutil.NApply.process(NApply.java:725)
[Nov 22, 2014 11:36:08 AM]   StackTrace: oracle.opatch.opatchutil.OUSession.napply(OUSession.java:1136)
[Nov 22, 2014 11:36:08 AM]   StackTrace: sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[Nov 22, 2014 11:36:08 AM]   StackTrace: sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[Nov 22, 2014 11:36:08 AM]   StackTrace: sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[Nov 22, 2014 11:36:08 AM]   StackTrace: java.lang.reflect.Method.invoke(Method.java:592)
[Nov 22, 2014 11:36:08 AM]   StackTrace: oracle.opatch.UtilSession.process(UtilSession.java:322)
[Nov 22, 2014 11:36:08 AM]   StackTrace: oracle.opatch.OPatchSession.main(OPatchSession.java:2346)
[Nov 22, 2014 11:36:08 AM]   StackTrace: oracle.opatch.OPatch.main(OPatch.java:613)

CAUSE:

The failure is because the downloaded patch is not for the platform on which it is being installed. For example, if the OS platform is Linux x86-64 and the downloaded patch is for Solaris SPARC, patching fails with the reported error rather than suggesting that the OS platform and the platform of the patch do not match.

SOLUTION:

Download the patch for the correct platform and install it by executing the following command

opatch apply

RMAN-05001: auxiliary filename /xxx/xxx/xx.dbf conflicts with a file used by the target database tips

Question:  I am trying to clone a database using RMAN and I get the following RMAN-05001 error:  
RMAN-05001: auxiliary filename /xxx/xxx/xx.dbf conflicts with a file used by the target tips.


Solution :

                 set dbfile convert  and logfile concert parameter in init.ora and startup database in nomount and execute the rman script.

How to check dba users | failed login attempts

You can now view failed login attempts in dba_audit_trail:

select
   os_username,
   username,
   terminal,
   to_char(timestamp,'MM-DD-YYYY HH24:MI:SS')
from
   dba_audit_trail;

OS_USERNAME     USERNAME        TERMINAL        TO_CHAR(TIMESTAMP,'
--------------- --------------- --------------- -------------------
fred         SCOTT              app93           05-16-2009 16:21:13

ERROR While starting OACORE services in R12

In E-business Suite R12, some of Application services is not stopped correctly. so when we start oacore services it will fail with error code Error: <connector name="OracleASjms" path="OracleASjms.rar" .

Usually other services wont any issue while coming up.....

Error :

Following Error can be written in $INST_TOP/ora/10.1.3/opmn/oacore_default_group_1/oacorestd.err

=================================

14/09/30 13:56:18 Error: <connector name="OracleASjms" path="OracleASjms.rar" /> will not be bootstrapped since corresponding module declaration was not found in application.xml.
14/09/30 14:54:55 Error: <connector name="OracleASjms" path="OracleASjms.rar" /> will not be bootstrapped since corresponding module declaration was not found in application.xml.
14/09/30 17:15:45 Error: <connector name="OracleASjms" path="OracleASjms.rar" /> will not be bootstrapped since corresponding module declaration was not found in application.xml.
14/10/01 12:18:06 Error: <connector name="OracleASjms" path="OracleASjms.rar" /> will not be bootstrapped since corresponding module declaration was not found in application.xml.
14/10/01 12:59:31 Error: <connector name="OracleASjms" path="OracleASjms.rar" /> will not be bootstrapped since corresponding module declaration was not found in application.xml.
14/10/01 15:30:46 Error: <connector name="OracleASjms" path="OracleASjms.rar" /> will not be bootstrapped since corresponding module declaration was not found in application.xml.
14/10/01 16:14:48 Error: <connector name="OracleASjms" path="OracleASjms.rar" /> will not be bootstrapped since corresponding module declaration was not found in application.xml.
01/01/20 06:52:37 Error: <connector name="OracleASjms" path="OracleASjms.rar" /> will not be bootstrapped since corresponding module declaration was not found in application.xml.
01/01/20 06:58:31 Error: <connector name="OracleASjms" path="OracleASjms.rar" /> will not be bootstrapped since corresponding module declaration was not found in application.xml.
14/10/13 18:06:36 Error: <connector name="OracleASjms" path="OracleASjms.rar" /> will not be bootstrapped since corresponding module declaration was not found in application.xml.

========================


When services start , it creates lock files for the process and this lock will persist till the time services are up.

Solutions:

To resolve this issue, remove these lock files and restart services again. Lock file location is as below.

1. OACORE service lock file will be located at

    cd $INST_TOP/ora/10.1.3/j2ee/oacore/persistence/oacore_default_group_1
    remove all files under this location and restart oacore services.


2.  if forms are not opening, its giving same error, then remove forms lock files

     Form service lock file will be located at

    cd $INST_TOP/ora/10.1.3/j2ee/forms/persistence/forms_default_group_1
    remove all files under this location and restart forms services.


Hope this helps.