FRM-40735: KEY-COMMIT trigger raised unhandled exception ORA-04062

Issue:

While saving quote, the following error occurs :

ORA-01403: no data found

FRM-40735: KEY-COMMIT trigger raised unhandled exception ORA-04062

FRM-40735: WHEN-TAB-PAGE-CHANGED trigger raised unhandled exception ORA-04062

Cause:

Invalid objects on the instance after recently applying a patch.

Solution:

To implement the solution, please execute the following steps :

Please run adadmin utility to:

1. Recompile APPS Schema. 

2. Recompile the forms and libraries for <issue product> products

Java Heap Space Issue in R12

SQL> select instance_name from v$instance;

INSTANCE_NAME
----------------
TEST

SQL> select DEVELOPER_PARAMETERS from apps.FND_CP_SERVICES where SERVICE_ID = (select MANAGER_TYPE from apps.FND_CONCURRENT_QUEUES where CONCURRENT_QUEUE_NAME = 'FNDCPOPP');

DEVELOPER_PARAMETERS
-----------------------------------------------------
J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx512m


SQL> update FND_CP_SERVICES
set DEVELOPER_PARAMETERS =

'J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx1024m'

where SERVICE_ID = (select MANAGER_TYPE from FND_CONCURRENT_QUEUES

where CONCURRENT_QUEUE_NAME = 'FNDCPOPP');

1 row updated.

SQL> commit;

Commit complete.

SQL> select DEVELOPER_PARAMETERS from apps.FND_CP_SERVICES where SERVICE_ID = (select MANAGER_TYPE from apps.FND_CONCURRENT_QUEUES where CONCURRENT_QUEUE_NAME = 'FNDCPOPP');

DEVELOPER_PARAMETERS
------------------------------------------------------
J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx1024m

FNDCPASS Error in password verification for APPS in R12

Issue:

[applmgr@dev ~]$ FNDCPASS apps/****** 0 Y system/******SYSTEM APPLSYS apps
Log filename : L5179008.log


Report filename : O5179008.out
[applmgr@dev ~]$ cat L5179008.log
+---------------------------------------------------------------------------+
Application Object Library: Version : 12.0.0

Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.

 module:
+---------------------------------------------------------------------------+

Current system time is 31-JAN-2020 15:00:00

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

Arguments

   FNDCPASS system/***** SYSTEM APPLSYS *****
+----------------------------------------------------------------------------+
Working...
Error in password verification for APPS.

+---------------------------------------------------------------------------+
Concurrent request completed
Current system time is 31-JAN-2020 15:00:00

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

Cause:

[oracle@dev ~]$ sqlplus '/as sysdba'

SQL> show parameter case

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
sec_case_sensitive_logon             boolean     TRUE

Solution:

[oracle@dev ~]$ sqlplus '/as sysdba'

SQL> alter system set sec_case_sensitive_logon=FALSE;

System altered.

SQL> show parameter case

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
sec_case_sensitive_logon             boolean     FALSE

[applmgr@dev ~]$ FNDCPASS apps/******0 Y system/***** SYSTEM APPLSYS apps
Log filename : L5179012.log


Report filename : O5179012.out

[applmgr@dev ~]$ cat L5179012.log
+---------------------------------------------------------------------------+
Application Object Library: Version : 12.0.0

Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.

 module:
+---------------------------------------------------------------------------+

Current system time is 31-JAN-2020 15:04:26

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

Arguments

   FNDCPASS system/***** SYSTEM APPLSYS *****
+----------------------------------------------------------------------------+
Working...

FNDCPASS completed successfully.

+---------------------------------------------------------------------------+
Concurrent request completed successfully
Current system time is 31-JAN-2020 15:04:28

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

WARNING: failed to start ASMB (connection failed) in Oracle 12c

Issue:

Starting background process ASMB
Tue Feb 04 05:25:00 2020
ASMB started with pid=37, OS id=19368
WARNING: failed to start ASMB (connection failed) state=0x1 sid=''

Cause:

RMAN CATALOG EXTREMELY SLOW WHEN MIGRATING DATABASE FROM ASM TO FILE SYSTEM
RMAN Restore/Duplicate from ASM to Non ASM in 12.1 take a longer time waiting for the ASMB process.  
Any RMAN command at the mount state which involves Non ASM location can take more time.

Solution:

Apply the patch 19503821, if not available for your version/OS then please log a SR with the support to get the patch for your version.

Ref:
WARNING: failed to start ASMB after RAC Database on ASM converted to Single Instance Non-ASM Database (Doc ID 2138520.1)

WARNING: Oracle executable binary mismatch detected.

Issue:
======
 Binary of new process does not match binary which started instance
issue alter system set "_disable_image_check" = true to disable these messages
Mon May 13 14:25:57 2019
WARNING: Oracle executable binary mismatch detected.
 Binary of new process does not match binary which started instance
issue alter system set "_disable_image_check" = true to disable these messages

Solution:
=========
Whenever the binary is linked or changed, you need to make sure that all instances are shutdown.
So in this case, the following action plan would fix this problem:

Shutdown the instance(Database and Applications)
Ensure that all related processes have been killed
Restart the instance (Database and Applications)

How to recreate Em DB console in Oracle 10gR2

Source environment and run below emca command

bash-5.0$ emca -config dbcontrol db -repos recreate

STARTED EMCA at Apr 22, 2019 11:13:17 AM
EM Configuration Assistant, Version 10.2.0.5.0 Production
Copyright (c) 2003, 2009, Oracle.  All rights reserved.

Enter the following information:
Database SID: <sid> Ex: orcl
Listener port number: <Port> Ex: 1521
Password for SYS user:
Password for DBSNMP user:
Password for SYSMAN user:
Email address for notifications (optional):
Outgoing Mail (SMTP) server for notifications (optional):
-----------------------------------------------------------------

You have specified the following settings

Database ORACLE_HOME ................ /u01/app/oracle/OraHome_1

Local hostname ................ <hostname>
Listener port number ................ 1521
Database SID ................ <sid>
Email address for notifications ...............
Outgoing Mail (SMTP) server for notifications ...............

-----------------------------------------------------------------

----------------------------------------------------------------------
WARNING : While repository is dropped the database will be put in quiesce mode.
----------------------------------------------------------------------
Do you wish to continue? [yes(Y)/no(N)]: Y
Apr 22, 2019 11:13:37 AM oracle.sysman.emcp.EMConfig perform
INFO: This operation is being logged at /u01/app/oracle/OraHome_1/cfgtoollogs/emca/<sid>/emca_2019-04-22_11-13-17-AM.log.
Apr 22, 2019 11:13:38 AM oracle.sysman.emcp.EMReposConfig invoke
INFO: Dropping the EM repository (this may take a while) ...
Apr 22, 2019 11:13:38 AM oracle.sysman.emcp.EMReposConfig dropRepository
INFO: Dropping the EM repository (this may take a while) ...
Apr 22, 2019 11:14:05 AM oracle.sysman.emcp.EMReposConfig invoke
INFO: Repository successfully dropped
Apr 22, 2019 11:14:05 AM oracle.sysman.emcp.EMReposConfig createRepository
INFO: Creating the EM repository (this may take a while) ...
Apr 22, 2019 11:15:29 AM oracle.sysman.emcp.EMReposConfig invoke
INFO: Repository successfully created
Apr 22, 2019 11:15:32 AM oracle.sysman.emcp.util.DBControlUtil secureDBConsole
INFO: Securing Database Control (this may take a while) ...
Apr 22, 2019 11:16:12 AM oracle.sysman.emcp.util.DBControlUtil secureDBConsole
INFO: Database Control secured successfully.
Apr 22, 2019 11:16:12 AM oracle.sysman.emcp.util.DBControlUtil startOMS
INFO: Starting Database Control (this may take a while) ...
Apr 22, 2019 11:17:51 AM oracle.sysman.emcp.EMDBPostConfig performConfiguration
INFO: Database Control started successfully
Apr 22, 2019 11:17:51 AM oracle.sysman.emcp.EMDBPostConfig performConfiguration
INFO: >>>>>>>>>>> The Database Control URL is https://<hostname>:5502/em <<<<<<<<<<<
Enterprise Manager configuration completed successfully
FINISHED EMCA at Apr 22, 2019 11:17:51 AM

EM 12c/EM 13c monitoring credentials for the database in Enterprise Manager password has expired/account locked

Issue:

ORA-28001: the password has expired The Connect Descriptor was (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = <hostname>)(PORT = 1521))(CONNECT_DATA = (SID = <sid>)))

The error message shown above indicates that the agent is unable to monitor this database because the agent cannot logon. 
To correct this, the Monitor Password needs to match the corresponding database password for dbsnmp. 
To change both the dbsnmp database password and the Monitor Password, click the Change dbsnmp Password button. 
This operation will also unlock the dbsnmp user.

Cause:

The dbsnmp password has expired" or "ORA-28000: the account is locked"

Solution:

Method 1 -

SQL> select username, account_status from dba_users where username=’DBSNMP’;

USERNAME   ACCOUNT_STATUS
__________________________

DBSNMP       EXPIRED

SQL> alter user dbsnmp identified by <password> account unlock;

User altered.

update dbsnmp password in OEM grid control.

Method 2 -

1. Login grid control with sysman
2. Click Setup -> Manage Cloud Control -> Agents
3. Click Server name
4. Goto Monitoring -> Click Database Instance name
5. Click configure and Provide sys password
6. Change password

7. Click test connection
8. Message displays “The connection test was successful”
9. Click next
10.Submit

Enterprise Manager Database Control Configuration/Certificate issue after upgrading 10.2.0.1 to 10.2.0.5

Issue:
bash-5.0$ emctl start dbconsole
Oracle Enterprise Manager 10g Database Control Release 10.2.0.5.0
Copyright (c) 1996, 2010 Oracle Corporation.  All rights reserved.
https:/hostname:1158/em/console/aboutApplication
ps: cmd is not a valid field name
Starting Oracle Enterprise Manager 10g Database Control ............................................................ failed.
------------------------------------------------------------------
Logs are generated in directory /u01/app/oracle/OraHome_1/<hostname_sid>/sysman/log
bash-5.0$ ./emctl status dbconsole
Oracle Enterprise Manager 10g Database Control Release 10.2.0.5.0
Copyright (c) 1996, 2010 Oracle Corporation.  All rights reserved.
https://hostname:1158/em/console/aboutApplication
Oracle Enterprise Manager 10g is not running.

Checking the ORACLE_HOME\<hostname>_<SID>\sysman\log\emagent.trc, below errors can see also:

2019-04-12 10:49:29 Thread-5 ERROR http: 16: Unable to initialize ssl connection with server, aborting connection attempt
2019-04-12 10:49:29 Thread-5 ERROR command: nmejcn: failed http connection to https://hostname:1158/em/upload/: retStatus=-1
2019-04-12 10:49:30 Thread-24 ERROR upload: Error in uploadXMLFiles.  Trying again in 103.00 seconds.
2019-04-12 10:49:34 Thread-25 ERROR upload: Error in uploadXMLFiles.  Trying again in 123.00 seconds.
2019-04-12 10:49:39 Thread-28 ERROR upload: Error in uploadXMLFiles.  Trying again in 147.00 seconds.
2019-04-12 10:49:45 Thread-5 ERROR ssl: Open wallet failed, ret = 28750
2019-04-12 10:49:45 Thread-5 ERROR ssl: nmehlenv_openWallet failed

(or)

2019-04-12 12:14:18 Thread-128 ERROR ssl: nzos_Handshake failed, ret=28862
2019-04-12 12:14:18 Thread-128 ERROR http: 15: Error initializing SSL connection for incoming request, aborting request. ret=-1


Cause:
In Enterprise Manager (EM) Database Control with Oracle Database 10.2.0.4 and 10.2.0.5, the root certificate used to secure communications via the Secure Socket Layer (SSL) protocol will expire on 31-Dec-2010 00:00:00. The certificate expiration will cause errors if you attempt to configure Database Control on or after 31-Dec-2010.Existing Database Control configurations are not impacted by this issue.

Solution:

1. Stop database,listener and em services.
2. Download and apply patch
bash-5.0$ /u01/app/oracle/OraHome_1/OPatch/opatch apply
Invoking OPatch 10.2.0.4.9

Oracle Interim Patch Installer version 10.2.0.4.9
Copyright (c) 2009, Oracle Corporation.  All rights reserved.


Oracle Home       : /u01/app/oracle/OraHome_1
Central Inventory : /u01/app/oracle/oraInventory
   from           : /var/opt/oracle/oraInst.loc
OPatch version    : 10.2.0.4.9
OUI version       : 10.2.0.5.0
OUI location      : /u01/app/oracle/OraHome_1/oui
Log file location : /u01/app/oracle/OraHome_1/cfgtoollogs/opatch/opatch2019-04-12_11-34-01AM.log

Patch history file: /u01/app/oracle/OraHome_1/cfgtoollogs/opatch/opatch_history.txt

ApplySession applying interim patch '8350262' to OH '/u01/app/oracle/OraHome_1'

Running prerequisite checks...

OPatch detected non-cluster Oracle Home from the inventory and will patch the local system only.

Backing up files and inventory (not for auto-rollback) for the Oracle Home
Backing up files affected by the patch '8350262' for restore. This might take a while...
Backing up files affected by the patch '8350262' for rollback. This might take a while...

Patching component oracle.sysman.agent.core, 10.2.0.5.0a...
Updating jar file "/u01/app/oracle/OraHome_1/sysman/jlib/emCORE.jar" with "/sysman/jlib/emCORE.jar/oracle/sysman/eml/sec/fsc/FSWalletUtil.class"
Updating jar file "/u01/app/oracle/OraHome_1/sysman/jlib/emCORE.jar" with "/sysman/jlib/emCORE.jar/oracle/sysman/eml/sec/rep/RepWalletUtil.class"
Updating jar file "/u01/app/oracle/OraHome_1/sysman/jlib/emCORE.jar" with "/sysman/jlib/emCORE.jar/oracle/sysman/eml/sec/util/RootCert.class"
Updating jar file "/u01/app/oracle/OraHome_1/sysman/jlib/emCORE.jar" with "/sysman/jlib/emCORE.jar/oracle/sysman/eml/sec/util/SecConstants.class"
Updating jar file "/u01/app/oracle/OraHome_1/sysman/jlib/emd_java.jar" with "/sysman/jlib/emd_java.jar/oracle/sysman/eml/sec/fsc/FSWalletUtil.class"
Updating jar file "/u01/app/oracle/OraHome_1/sysman/jlib/emd_java.jar" with "/sysman/jlib/emd_java.jar/oracle/sysman/eml/sec/rep/RepWalletUtil.class"
Updating jar file "/u01/app/oracle/OraHome_1/sysman/jlib/emd_java.jar" with "/sysman/jlib/emd_java.jar/oracle/sysman/eml/sec/util/RootCert.class"
Updating jar file "/u01/app/oracle/OraHome_1/sysman/jlib/emd_java.jar" with "/sysman/jlib/emd_java.jar/oracle/sysman/eml/sec/util/SecConstants.class"
ApplySession adding interim patch '8350262' to inventory

Verifying the update...
Inventory check OK: Patch ID 8350262 is registered in Oracle Home inventory with proper meta-data.
Files check OK: Files from Patch ID 8350262 are present in Oracle Home.

OPatch succeeded.
bash-5.0$ /u01/app/oracle/OraHome_1/OPatch/opatch lsinventory
Invoking OPatch 10.2.0.4.9

Oracle Interim Patch Installer version 10.2.0.4.9
Copyright (c) 2009, Oracle Corporation.  All rights reserved.


Oracle Home       : /u01/app/oracle/OraHome_1
Central Inventory : /u01/app/oracle/oraInventory
   from           : /var/opt/oracle/oraInst.loc
OPatch version    : 10.2.0.4.9
OUI version       : 10.2.0.5.0
OUI location      : /u01/app/oracle/OraHome_1/oui
Log file location : /u01/app/oracle/OraHome_1/cfgtoollogs/opatch/opatch2019-04-12_11-34-25AM.log

Patch history file: /u01/app/oracle/OraHome_1/cfgtoollogs/opatch/opatch_history.txt

Lsinventory Output file location : /u01/app/oracle/OraHome_1/cfgtoollogs/opatch/lsinv/lsinventory2019-04-12_11-34-25AM.txt

--------------------------------------------------------------------------------
Installed Top-level Products (2):

Oracle Database 10g                                                  10.2.0.1.0
Oracle Database 10g Release 2 Patch Set 4                            10.2.0.5.0
There are 2 products installed in this Oracle Home.


Interim patches (1) :

Patch  8350262      : applied on Fri Apr 12 11:34:11 IST 2019
Unique Patch ID:  13011832
   Created on 13 Sep 2010, 14:09:12 hrs GMT
   Bugs fixed:
     8350262

--------------------------------------------------------------------------------

OPatch succeeded.

3. Start database and listener services.
4. Re-secure Database Control with the following command:
   <ORACLE_HOME>/bin/emctl secure dbconsole -reset
You will be prompted twice to confirm that the Root key must be overwritten. In both cases, enter upper-case "Y" as the response. Any other response (including lower-case "y") will cause the command to terminate without completing. If this happens, the command can be re-invoked.

bash-5.0$ emctl secure dbconsole -reset
Oracle Enterprise Manager 10g Database Control Release 10.2.0.5.0
Copyright (c) 1996, 2010 Oracle Corporation.  All rights reserved.
http://hostname:1158/em/console/aboutApplication
Enter Enterprise Manager Root Password :
DBCONSOLE already stopped...   Done.
Agent is already stopped...   Done.
Securing dbconsole...   Started.
Checking Repository...   Done.
Checking Em Key...   Done.
Checking Repository for an existing Enterprise Manager Root Key...
WARNING! An Enterprise Manager Root Key already exists in
the Repository. This operation will replace your Enterprise
Manager Root Key.
All existing Agents that use HTTPS will need to be
reconfigured if you proceed. Do you wish to continue and
overwrite your Root Key
(Y/N) ?
Y
Are you sure ? Reset of the Enterprise Manager Root Key
will mean that you will need to reconfigure each Agent
that is associated with this OMS before they will be
able to upload any data to it. Monitoring of Targets
associated with these Agents will be unavailable until
after they are reconfigured.
(Y/N) ?
Y
Generating Enterprise Manager Root Key (this takes a minute)...   Done.
Fetching Root Certificate from the Repository...   Done.
Updating HTTPS port in emoms.properties file...   Done.
Generating Java Keystore...   Done.
Securing OMS ...   Done.
Generating Oracle Wallet Password for Agent....   Done.
Generating wallet for Agent ...    Done.
Copying the wallet for agent use...    Done.
Storing agent key in repository...   Done.
Storing agent key for agent ...   Done.
Configuring Agent...
Configuring Agent for HTTPS in DBCONSOLE mode...   Done.
EMD_URL set in /u01/app/oracle/OraHome_1/<hostname_sid>/sysman/config/emd.properties
   Done.
Configuring Key store..   Done.
Securing dbconsole...   Sucessful.

5. Re-start Database Control with the following command:

   <ORACLE_HOME>/bin/emctl start dbconsole
bash-5.0$ emctl start dbconsole
Oracle Enterprise Manager 10g Database Control Release 10.2.0.5.0
Copyright (c) 1996, 2010 Oracle Corporation.  All rights reserved.
https://hostname>:1158/em/console/aboutApplication
ps: cmd is not a valid field name
Starting Oracle Enterprise Manager 10g Database Control .................... started.
------------------------------------------------------------------
Logs are generated in directory /u01/app/oracle/OraHome_1/<hostname_sid>/sysman/log

6. Verify Database Control status with the following command:

bash-5.0$ emctl status dbconsole
Oracle Enterprise Manager 10g Database Control Release 10.2.0.5.0
Copyright (c) 1996, 2010 Oracle Corporation.  All rights reserved.
https://hostname:1158/em/console/aboutApplication
Oracle Enterprise Manager 10g is running.
------------------------------------------------------------------
Logs are generated in directory /u01/app/oracle/OraHome_1/<hostname_sid>/sysman/log

NL-08014: Failed to initialize Diagnosability framework, falling back to old network tracing/logging

Issue:

[oracle1@oracle ~]$ lsnrctl start

LSNRCTL for Linux: Version 12.2.0.1.0 - Production on 03-APR-2019 15:49:56

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

Starting /u01/Installations/Oracledb_12c/product/12.2.0/dbhome_1/bin/tnslsnr: please wait...

TNSLSNR for Linux: Version 12.2.0.1.0 - Production
System parameter file is /u01/Installations/Oracledb_12c/product/12.2.0/dbhome_1/network/admin/listener.ora
Log messages written to /u01/Installations/Oracledb_12c/product/12.2.0/dbhome_1/network/log/humint.log
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oracle)(PORT=1521)))
Error listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1521)))
TNS-12555: TNS:permission denied
 TNS-12560: TNS:protocol adapter error
  TNS-00525: Insufficient privilege for operation
   Linux Error: 1: Operation not permitted
    NL-08014: Failed to initialize Diagnosability framework, falling back to old network tracing/logging

     NL-08002: Diagnosability  context creation failed

Listener failed to start. See the error message(s) above...

Cause:

1.
OCI client running a script is unable to write a file to the ADR_BASE:

/u01/app/oracle:


oracle $ pwd
/u01/Installations/Oracledb_12c
oracle $ userid touch a.txt
user1 is executing touch a.txt as userid in /u01/Installations/Oracledb_12c
touch: cannot touch `a.txt': Permission denied <===User can not write to ADR_BASE destination directory

2. Also Problem with IPC PRotocal after changing ownership oracle to another.

Solution:

Give the correct owner permission to write to the directory specified in the parameter ADR_BASE in the sqlnet.ora file.
Alternatively, change the value for ADR_BASE to a directory where the same user has write permissions.
Change ownership to correct user.

How to resolve grid(12.1.0) root.sh issue in Linux6

Issue:

[root@oracle grid]# ./root.sh
Entries will be added to the /etc/oratab file as needed by
Database Configuration Assistant when a database is created
Finished running generic part of root script.
Now product-specific root actions will be performed.
Using configuration parameter file: /u01/grid/product/12.1.0/grid/crs/install/crsconfig_params
PROTL-4: Failed to retrieve data from the local registry
2017/04/20 14:05:56 CLSRSC-169: Failed to create or upgrade OLR

Died at /u01/grid/product/12.1.0/grid/crs/install/crsutils.pm line 7672.
The command '/u01/grid/product/12.1.0/grid/perl/bin/perl -I/u01/grid/product/12.1.0/grid/perl/lib -I/u01/grid/product/12.1.0/grid/crs/install /u01/grid/product/12.1.0/grid/crs/install/roothas.pl ' execution failed 

Solution:

Need to deconfig grid before fresh installtion.


[root@oracle etc]# /u01/grid/product/12.1.0/grid/crs/install/roothas.pl -deconfig -force -verbose
Using configuration parameter file: /u01/grid/product/12.1.0/grid/crs/install/crsconfig_params
2017/04/20 14:54:18 CLSRSC-332: CRS resources for listeners are still configured
[root@oracle grid]# ./root.sh
PRCR-1065 : Failed to stop resource ora.ASMDB.lsnr
CRS-5013: Agent "ORAAGENT" failed to start process "/u01/db/oracle/product/12.1.0/dbhome_1/bin/lsnrctl" for action "clean": details at "(:CLSN00008:)" in "/u01/grid/diag/crs/oracle/crs/trace/ohasd_oraagent_grid.trc"
CRS-5013: Agent "ORAAGENT" failed to start process "/u01/db/oracle/product/12.1.0/dbhome_1/bin/lsnrctl" for action "check": details at "(:CLSN00008:)" in "/u01/grid/diag/crs/oracle/crs/trace/ohasd_oraagent_grid.trc"
CRS-2680: Clean of 'ora.ASMDB.lsnr' on 'oracle' failed

2017/04/20 14:54:19 CLSRSC-424: Failed to stop database listener, but continuing to deconfigure with force option

PRKO-2573 : ONS daemon is already stopped.
CRS-4133: Oracle High Availability Services has been stopped.
2017/04/20 14:54:37 CLSRSC-337: Successfully deconfigured Oracle Restart stack


[root@oracle grid]# ./root.sh
Performing root user operation.

The following environment variables are set as:
    ORACLE_OWNER= grid
    ORACLE_HOME=  /u01/grid/product/12.1.0/grid

Enter the full pathname of the local bin directory: [/usr/local/bin]:
The contents of "dbhome" have not changed. No need to overwrite.
The contents of "oraenv" have not changed. No need to overwrite.
The contents of "coraenv" have not changed. No need to overwrite.

Entries will be added to the /etc/oratab file as needed by
Database Configuration Assistant when a database is created
Finished running generic part of root script.
Now product-specific root actions will be performed.
Using configuration parameter file: /u01/grid/product/12.1.0/grid/crs/install/crsconfig_params
LOCAL ADD MODE
Creating OCR keys for user 'grid', privgrp 'dba'..
Operation successful.
LOCAL ONLY MODE
Successfully accumulated necessary OCR keys.
Creating OCR keys for user 'root', privgrp 'root'..
Operation successful.
CRS-4664: Node oracle successfully pinned.
2017/04/20 14:57:05 CLSRSC-330: Adding Clusterware entries to file 'oracle-ohasd.conf'


oracle     2017/04/20 14:57:30     /u01/grid/product/12.1.0/grid/cdata/oracle/backup_20170420_145730.olr     0
CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on 'oracle'
CRS-2673: Attempting to stop 'ora.evmd' on 'oracle'
CRS-2677: Stop of 'ora.evmd' on 'oracle' succeeded
CRS-2793: Shutdown of Oracle High Availability Services-managed resources on 'oracle' has completed
CRS-4133: Oracle High Availability Services has been stopped.
CRS-4123: Oracle High Availability Services has been started.
2017/04/20 14:57:47 CLSRSC-327: Successfully configured Oracle Restart for a standalone server

Target node/queue unavailable in R12

Error:

Manager log file shows below error

establish_icm - Unable to insert ICM record
Call to establish_icm failed
The Internal Concurrent Manager has encountered an error.

Review concurrent manager log file for more detailed information. : 12-NOV-2016 22:35:45 -


Shutting down Internal Concurrent Manager : 12-NOV-2016 22:35:45

List of errors encountered:
.............................................................................

_ 1 _
Routine AFPCSQ encountered an ORACLE error. .

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


APP-FND-01564: ORACLE error 12899 in insert_icm_record

Cause: insert_icm_record failed due to ORA-12899: value too large for column "APPLSYS"."FND_CONCURRENT_PROCESSES"."NODE_NAME" (actual: 31, maximum: 30).

Solution:

Step 1:

Stop Concurrent managers

Check source node information in refreshed instance.

select CONCURRENT_QUEUE_NAME, CONTROL_CODE , TARGET_NODE, NODE_NAME   from FND_CONCURRENT_QUEUES where concurrent_queue_name like 'PROD%';

update FND_CONCURRENT_QUEUES set TARGET_NODE='TEST' where CONCURRENT_QUEUE_NAME='PROD';

Step 2:

Increase column value

SQL> create table APPLSYS.FND_CONCURRENT_PROCESSES_old as select * from APPLSYS.FND_CONCURRENT_PROCESSES;

Table created.

SQL> ALTER TABLE APPLSYS.FND_CONCURRENT_PROCESSES MODIFY NODE_NAME VARCHAR2(32);

Table altered.

Step 3:

Run cmclean.sql

Start Concurrent services now . It should work.

How To Clear Caches (Apache/iAS, Cabo, Modplsql, Browser, Jinitiator, Java, Portal, WebADI)

Apache / iAS 

For 11i and earlier versions:

- shutdown iAS server
- go to $OA_HTML (for 11.5.9) or $COMMON_TOP (for 11.5.10.x) directory
- backup the directory _pages and delete its contents by running for instance:

  rm -rf $COMMON_TOP/_pages/*

- for modplsql caches remove contents of  $IAS_ORACLE_HOME/Apache/modplsql/cache directory
- restart iAS server


To clear middle tier cache in release 12:

- go to "Functional Administrator" responsibility
- select Core Services => Caching Framework => Global Configuration => Clear cache

In case you have login issue after accidentally cleared the _pages instead of using the method above for r12. Run below command for regenerating jdsps.

perl $FND_TOP/patch/115/bin/ojspCompile.pl --compile --flush -p 2

Cabo

Images and style sheets can be corrupted or out of sync in the cabo caches,
you may need to clear the related directories after backup:

$OA_HTML/cabo/images/cache
$OA_HTML/cabo/styles/cache


Web Browser

for Internet Explorer:

- go to menu Tools => Internet Options,
- select 'General' tab,
- click on button 'Delete Files' in 'Temporary Internet files' area
  or
- click on button 'Delete...' then in 'Delete Browsing History' pop-up window click on 'Delete Files...'
- close all IE windows and restart new browser session.

for Mozilla Firefox:

- go to menu Tools
- select 'Clear Private Data...' or 'Clear Recent History...' then check 'Cache'
  or
- go to menu Edit or Tools
- select Preferences or Options.
- expand the 'Advance' options and choose 'Cache' or Privacy
- click the button called 'Clear Cache'.

for Safari:

- go to Safari menu
- select Empty Cache => Click 'Empty' in the dialogue box

for Netscape:

- go to menu Edit => Preferences,
- choose 'Cache' in 'Advanced' category,
- click on buttons 'Clear Memory Cache' and 'Clear Disk Cache'.
- close all Netscape windows and restart new browser session.

Jinitiator

Two possibilities depending of the Jinitiator version:

for 1.1.8.x versions:

- delete all files in directory:

C:\Program Files\Oracle\Jinitiator <version>\jcache\

for 1.3.1.x versions:

- go to Start => Parameters => Control Panel
- double-click on "Jinitiator <version>" icon
- in the new pop-up window, click on "Cache" tab
- click on "Clear Jar Cache " button. On prompt, click Yes.

(you can also delete directly all files under directory:
C:\Documents and Settings\<your user name>\Oracle Jar Cache)


Java

Java/JRE plug-in (Windows)

- go to Start => Parameters => Control Panel
- double-click on 'Java' icon
- in the new pop-up window, click on 'General' tab
- click on 'Setting...' button in 'Temporary Internet files' area then click on 'Delete Files...' button
  (you can select Applets, Applications or other files)

JVM

- go to responsibility "Functional Administrator" 
- click on "Core Services" tab then the "Caching Framework" sub-tab 
- click on "Global Configuration" link then click on "Clear all cache" button to clear all of the Java Cache's


Portal

- go to the url: http://<host.domain>:<port>/pls/admin_/gateway.htm or cache.htm
- click on "Cache Settings" option and note the "Cache Directory"
- go to this directory and delete all the cache files in the directory and sub directories


WebADI / BNE cache

For instance when enabling BNE log

To clear the cache in 11i:
- go to url: http://<host.domain>:<port>/oa_servlets/oracle.apps.bne.framework.BneAdminServlet
- click on the "clear-cache" link
- at the bottom of the page you should see 'Cache Cleared'

For R12 the URL to clear the cache is:
- go to url: http: //server:port/OA_HTML/BneAdminServlet
- click on the "clear-cache" link
- at the bottom of the page you should see 'Cache Cleared'

Reference: 742107.1