ERROR: OPatch failed during prerequisite check. Interim Patch yyyyyyy is holding the lock from this patch xxxxxxx for R12

PROBLEM:

I have problem when try to apply patch:9044638

ERROR:

bash-4.2$ opatch apply

Oracle Interim Patch Installer version 1.0.0.0.64
Copyright (c) 2011 Oracle Corporation. All Rights Reserved..

Oracle recommends you to use the latest OPatch version
and read the OPatch documentation available in the OPatch/docs
directory for usage. For information about the latest OPatch and
other support-related issues, refer to document ID 293369.1
available on My Oracle Support (https://myoraclesupport.oracle.com)

Oracle Home : /appdata/data_appl/apps/tech_st/10.1.2
Oracle Home Inventory : /appdata/data_appl/apps/tech_st/10.1.2/inventory
Central Inventory : /appdata/cloneap2/inst/apps/burklon_testburlaapp/admin/oraInventory
from : /etc/oraInst.loc
OUI location : /appdata/data_appl/apps/tech_st/10.1.2/oui
OUI shared library : /appdata/data_appl/apps/tech_st/10.1.2/oui/lib/ibm_aix/liboraInstaller.so
Java location : /appdata/data_appl/apps/tech_st/10.1.2/jre/1.4.2/bin/java
Log file location : /appdata/data_appl/apps/tech_st/10.1.2/.patch_storage/<patch ID>/*.log

Problems with the lock file
Lock file exists, details are:
Interim Patch 9593176 is holding the lock from this patch 9044638,
probably due to previous unsuccessful operation

ERROR: OPatch failed during prerequisite check.

SOLUTION:

1. Remove patch_locked file.
 

mv $ORACLE_HOME\.patch_storage\patch_locked 
     $ORACLE_HOME\.patch_storage\patch_locked_backup
 

 2. Apply patch again

Routine AFPPRD has encountered a fatal error. ORA-03114: not connected to ORACLE|| 'Shutting down Concurrent Manager' ||ORACLE error 3114 in AFPRSR-Resubmit_Time

Error:

+--------- 1) POST-PROCESSING  ---------+

Beginning post-processing of request 34508980 on node ACOD1RKA001 at 18-OCT-2017 11:04:50.

-- Publishing output

APP-FND-01564: ORACLE error 3113 in publish

Cause: publish failed due to ORA-03113: end-of-file on communication channel.

The SQL statement being executed at the time of the error was: &SQLSTMT and was executed from the file &ERRFILE.

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

Finished executing request completion options.

APP-FND-01564: ORACLE error 3114 in afpprq

Cause: afpprq failed due to ORA-03114: not connected to ORACLE.

The SQL statement being executed at the time of the error was: &SQLSTMT and was executed from the file &ERRFILE.

Shutting down Concurrent Manager : 18-OCT-2017 11:09:55

ORA-03114: not connected to ORACLE

ORACLE error 3114 in AFPRSR-Resubmit_Time

Cause: AFPRSR-Resubmit_Time failed due to ORA-03114: not connected to ORACLE

The SQL statement being executed at the time of the error was: select To_Char(To_Date(Decode(Resubmit_Time,null ,'00:

List of errors encountered:

.............................................................................

_ 1 _

Routine AFPCMT encountered an ORACLE error. ORA-03114: not connected

to ORACLE

Review your error messages for the cause of the error. (=<POINTER>)

_ 2 _

Routine AFPPRD has encountered a fatal error. ORA-03114: not connected

to ORACLE

Contact your system administrator or support representative.

_ 3 _

Routine AFPPRD has encountered a fatal error. ORA-03114: not connected

to ORACLE

Contact your system administrator or support representative.

.............................................................................

Solutions:

There are multiple scenarios that cause this error. Check the following list of solutions:

Lets devide it into two scenarios where we get this error.

1.DB Connection issue :-

                           

2. Verify there is no firewall or router setting which terminates connections which are active for longer than x minutes.

3. Verify there is no firewall or router setting which terminates connections which are idle for longer than x minutes.

3. Verify the Oracle configuration. Let the database send a packet every x minutes, so that the firewall, router, etc does not close the connection due to being 'idle'.

                                    The Oracle documentation lists the following details for the  sqlnet.ora parameter:   SQLNET.EXPIRE_TIME 

How to increase oacore processes in R12

How to increase oacore processes in R12

In EBS projects --depending on the workload , sometimes you need to increase the oacore process counts. There is a detailed calculation to determine the needed oacore process for an instance, but in general; it’s based on the user count.. Basically user count / 100 will give you the needed oacore process count.

Note that, the memory size that you will assign to these processes is also important for determining the right process counts.

Below are the steps to increase oacore process from 1 to 3

1)Take a backup of below files /test/inst/apps/TEST_test02/ora/10.1.3/opmn/conf/opmn.xml and $CONTEXT_FILE

2)Modify $CONTEXT_FILE as follows

From

<oacore_nprocs oa_var="s_oacore_nprocs">1</oacore_nprocs>

To

<oacore_nprocs oa_var="s_oacore_nprocs">3</oacore_nprocs>

3) Modify /test/inst/apps/TEST_test02/ora/10.1.3/opmn/conf/opmn.xml file as follows

under oacore section modify as follows

(<process-type id="oacore" module-id="OC4J" status="enabled"

working-dir="$ORACLE_HOME/j2ee/home">)

From

<process-set id="default_group" numprocs="1"/>

To

<process-set id="default_group" numprocs="3"/>

4) Bounce Apache services

In pre

$ adapcctl.sh status

You are running adapcctl.sh version 120.7.12010000.2

Checking status of OPMN managed Oracle HTTP Server (OHS) instance ...

Processes in Instance: TEST_test02.test02.hyd.com

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

ias-component                    | process-type       |     pid | status

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

OC4JGroup:default_group          | OC4J:oafm          |    2023 | Alive 

OC4JGroup:default_group          | OC4J:oacore        |    1899 | Alive 

HTTP_Server                      | HTTP_Server        |    1814 | Alive 

In post

$ adapcctl.sh status

You are running adapcctl.sh version 120.7.12010000.2

Checking status of OPMN managed Oracle HTTP Server (OHS) instance ...

Processes in Instance: TEST_test02.test02.hyd.com

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

ias-component                    | process-type       |     pid | status

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

OC4JGroup:default_group          | OC4J:oafm          |   17348 | Alive 

OC4JGroup:default_group          | OC4J:oacore        |   17347 | Alive 

OC4JGroup:default_group          | OC4J:oacore        |   17345 | Alive 

OC4JGroup:default_group          | OC4J:oacore        |   17346 | Alive 

HTTP_Server                      | HTTP_Server        |   17339 | Alive 

adapcctl.sh: exiting with status 0

adapcctl.sh: check the logfile /test/inst/apps/TEST_test02/logs/appl/admin/log/adapcctl.txt for more information ...

$

TNS-01153: Failed To Process String Error When Running Adalnctl.sh: Exiting With Status 1

Error :

On : 12.1.3 version, Database for Application Technology

Getting error when starting up EBS Apps listener, when issuing command,

adalnctl.sh start <listener Name>

lsnrctl start APPS_DEV

LSNRCTL for Linux: Version 10.1.0.5.0 - Production on 08-APR-2016 00:44:10

Copyright (c) 1991, 2004, Oracle. All rights reserved.

Starting /apps01/DEV/apps/tech_st/10.1.2/bin/tnslsnr: please wait...

TNSLSNR for Linux: Version 10.1.0.5.0 - Production
System parameter file is /path/DEV/inst/apps/DEV_HOST/ora/10.1.2/network/admin/listener.ora
Log messages written to /path/DEV/inst/apps/DEV_HOST/logs/ora/10.1.2/network/apps_dev.log
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=host.domain.com)(PORT=1111)))

Connecting to (ADDRESS=(PROTOCOL=TCP)(Host=host)(Port=1111))
TNS-01153: Failed to process string: ▒t▒


The issue can be reproduced at will with the following steps:
1. adalnctl.sh start <Apps listener Name>

Cause :

libnlsnr10.a was corrupted. Issue is addressed in the Bug 23080041 TNS-01153: FAILED TO PROCESS STRING

Solution :

1. Restore $ORACLE_HOME/network/lib/libnlsnr10.a file from a working instance.

cp $ORACLE_HOME/network/lib/libnlsnr10.a to target instance

2. Relink executable.

cd $ORACLE_HOME/network/lib/
make -f ins_net_server.mk itnslsnr

3. Retest the issue.

adalnctl.sh start <Apps listener Name>

Automating Database Startup and Shutdown on Windows server

To automate database startup and shutdown by using Oracle Administration Assistant for Windows:

1. From the Start menu, select All Programs, then select Oracle - HOMENAME,then select Configuration
    and Migration Tools, and then select Administration Assistant for Windows.
   
                        

2.    Right-click the SID.

3.    Select Startup/Shutdown Options.

                       

4.    Select the Oracle Instance tab.

5.    Select start up instance when service is started.

                  

                     
6.    Select the Oracle NT Service tab.

7.    Select Automatic in Oracle NT Service Startup Type.

                  

8.    Click Apply.

9.    Click OK.

Done. All set now, Oracle database will start automatically when system reboots on windows machine