Doyensys Allappsdba Blog..

NOTE: The following Clone approach is applicable for the APPLICATION version from R12.2.1 To R12.2.4

ENVIRONMENT:-

Source:-

BASE_PATH=/s01/oracle/R122

RUN_FILE_SYSTEM=/s01/oracle/R122/fs1

PATCH_FILE_SYSTEM=/s01/oracle/R122/fs2

Non-Editioned File System=/s01/oracle/R122/fs_ne

Target:-

BASE_PATH=/t01/oracle/R122

RUN_FILE_SYSTEM=/t01/oracle/R122/fs1

PATCH_FILE_SYSTEM=/t01/oracle/R122/fs2

Non-Editioned File System=/t01/oracle/R122/fs_ne

STEP1: Prepare Source Node for cloning

Run adpreclone.pl from RUN File System

cd /s01/oracle/R122/fs1/inst/apps/SI_source_appl/admin/scripts

[applsource@source_appl scripts]$ perl adpreclone.pl appsTier

STEP2: Copy the Source to Target

Choose only EBSapps from RUN File System for copy

[applsource@source_appl fs1]$ scp -rf EBSapps appltarget@<target-ip-address>:<target-server-path>

Prepare Target Server

mkdir /t01/oracle/R122/fs1

mkdir /t01/oracle/R122/fs2

mkdir /t01/oracle/R122/fs_ne

STEP3: After finishing Copy Configure Target File System

Go to Clone directory

cd /t01/oracle/R122/fs1/EBSapps/clone/bin

[appltarget@target_appl bin$ perl adcfgclone.pl appsTier

STEP4:Start application and run adpreclone on TARGET RUN File System

Run the environment of Target RUN File System application tier

cd $ADMIN_SCRIPTS_HOME

sh adstrtal.sh apps/<apps-password>

[appltarget@target_appl scripts$ perl adpreclone.pl appsTier

STEP5:Shutdown application on TARGET RUN File System

cd $ADMIN_SCRIPTS_HOME

sh adstpall.sh apps/<apps-password>

STEP6:Copy Target RUN File System to Target Patch File System

cp -rf /t01/oracle/R122/fs1/* /t01/oracle/R122/fs2/

UNSET the application Enviroment.Previously we have executed env.

Before we run adcfgclone.pl dont run any env's, Directly go to /u01/oracle/R122/fs2/EBSapps/comn/clone/bin/ and execute adcfgclone.pl

STEP7:Once Finished copying START CONFIGURING TARGET PATCH FILESYSTEM

[appltarget@target_appl bin$ perl adcfgclone.pl appsTier

STEP8:Once we are done with everything. Start the application Tier using adstral.sh

This time set the env to RUN File System

. /t01/oracle/R122/EBSapps.env run

cd $ADMIN_SCRIPTS_HOME

adstral.sh apps/<apps-password>

Thanks & Regards

Venkatesh RK

We faced the error ORA-16057 while building a standby database.archives were not shipping to the DR site

Now in the production database,

Select dest_id,error from v$archive_dest;

DEST_ID ERROR
---------- --------------------------------------------------------------------------
1
2
3
4 ORA-16057: server not in Data Guard configuration
5
6
7
8
9
10
11

In our case ,this error is due to wrong configuration in "log_archive_config" parameter in the DR side .
Once we the fixed the parameter "log_archive_config"

sql > alter system set LOG_ARCHIVE_CONFIG='DG_CONFIG=(prod,standby)' scope=both;

Now defer and enable the "log_archive_dest_state_4" paramter in production DB.and the logs started shipping to DR without any issues

sql > alter system set log_archive_dest_state_4=DEFER;

sql > alter system set log_archive_dest_state_4=ENABLE;

Now checking again for the error,

Select dest_id,error from v$archive_dest;

DEST_ID ERROR
---------- -------------------------------------------------------------------------
1
2
3
4
5
6
7
8
9
10
11

Hope this helps..

Adpreclone Fails in EBS 12.2.3 : There is already an ACTIVE ADOP CYCLE with session id

Issue:

The below failure while executing :

Running perl /DB01/app/PROD/fs2/prodapps/appl/ad/12.0.0/patch/115/bin/adProvisionEBS.pl ebs-get-serverstatus -contextfile=/DB01/app/PROD/inst/fs2/inst/apps/PROD_DB01PRODapp01/appl/admin/PROD_DB01PRODapp01.xml -servername=AdminServer -promptmsg=hide

The Oracle WebLogic Administration Server is up.

There is already an ACTIVE ADOP CYCLE with session id : SP2-0640: Not connected

adpreclone cannot be run with pending ADOP session.

Details:

Looking at the error message, it seems like there is an open ADOP session. Basically in Oracle EBS R12.2, we need to have all ADOP sessions completed or aborted before any cloning can be executed. While An active ADOP session , If any clone is performed, both filesystems can be put into trouble: RUN and PATCH. Hence we need to clear all ADOP sessions before executing adpreclone.

However when checked the status using: adop -status -detail , there were no active sessions.

Solution:

Patch 22271970: ADPRECLONE.PL FAILS ON DELTA 7

adop phase=apply patches=22271970

Actualize the old database editions after online patching to avoid possible performance issues: EBS 12.2.3/12.2.4

During Online patching (ADOP) :

An additional column ZD_EDITION_NAME is populated in the seed tables.This happens during th prepare phase.
Online patching doesn't modify runtime seed data by the use of editioned data storage. Creating a (patch) copy of the seed data, which is stored in the same table happens, as seen below :

ZD_EDITION_NAME
----------------------------
ORA$BASE
V_20161912_2051

Every time we perform online patching , there will an old database edition entry and this will accumulate as and when we do more online patching's.
Oracle suggests that we perform actualize_all after this reaches a count of 25. However it would be time consuming to perform the cleanup after the count has increased.

If the number of these grows too large, system performance will start to be affected. When the number of old database editions reaches 25 or more, you should consider dropping all old database editions by running the adop actualize_all phase and then performing a full cleanup.

Perform this every-time when there is no immediate need for online patching:

Before starting, you should ensure that the system has the recommended database patches and latest AD-TXK code level installed.

To proceed, run the following commands in the order shown:

$ adop phase=prepare
$ adop phase=actualize_all
$ adop phase=finalize finalize_mode=full
$ adop phase=cutover
$ adop phase=cleanup cleanup_mode=full
You have now completed removal of the old database editions.

OR

Every-time online patching is performed:

adop phase=actualize_all can be performed just before phase=finalize/cutover

As a DBA, we should be able to provide the history of locks to the application team to check.

This is the query to get the information from v$active_session_history

This view is part of diagnosis pack, make sure that you have a license for Diagnostic Pack before running this query.

Lock History information - v$active_session_history:
====================================================
col SAMPLE_TIME for a30
col BLOCKING_PATH format a40
set lines 170
SELECT
level,
sample_time,
session_id blocked_sid,
CONNECT_BY_ROOT blocking_session ultimate_blocker_sid,
sys_connect_by_path(blocking_session,'/')|| '/' || session_id blocking_path
FROM
(-- Blocked Sessions
SELECT
s.session_id,
s.blocking_session,
s.sample_time
FROM v$active_session_history s
--s.dbid = 70854992
-- AND s.instance_number = 1
--AND s.snap_id BETWEEN 62234 and 62235
WHERE s.blocking_session IS NOT NULL
AND s.event IN
('enq: TX - row lock contention')
UNION
-- Blocking Sessions
SELECT s.session_id,
s.blocking_session,
s.sample_time
FROM v$active_session_history s
-- s.dbid = 70854992
--AND s.instance_number = 1
--AND s.snap_id BETWEEN 62234 and 62235
WHERE s.blocking_session IS NULL
AND s.event IN
('enq: TX - row lock contention'
,'enq: TM - contention'
,'enq: UL - contention'
,'enq: TX - allocate ITL entry')
AND EXISTS
(SELECT 'exists'
FROM v$active_session_history bs
--bs.dbid = 70854992
--AND bs.instance_number = 1
--AND bs.snap_id BETWEEN 62234 and 62235
WHERE bs.blocking_session = s.session_id
AND bs.sample_time = s.sample_time
AND bs.blocking_session IS NOT NULL
AND bs.event IN
('enq: TX - row lock contention')
)
)
CONNECT BY NOCYCLE PRIOR session_id = blocking_session
AND PRIOR sample_time = sample_time
ORDER BY sample_time;

What we can do, if the required information not found in v$active_session_history?

Don't worry, we can get it from dba_hist_active_sess_history view.

Lock History information - dba_hist_active_sess_history:
========================================================

SELECT
level,
sample_time,
session_id blocked_sid,
CONNECT_BY_ROOT blocking_session ultimate_blocker_sid,
sys_connect_by_path(blocking_session,'/')|| '/' || session_id blocking_path
FROM
(-- Blocked Sessions
SELECT
s.session_id,
s.blocking_session,
s.sample_time
FROM dba_active_sess_history s
-- WHERE s.dbid = 70854992
-- AND s.instance_number = 1
WHERE s.snap_id BETWEEN '&StSnap' and '&EdSnap'
AND s.blocking_session IS NOT NULL
AND s.event IN
('enq: TX - row lock contention'
,'enq: TM - contention'
,'enq: UL - contention'
,'enq: TX - allocate ITL entry')
UNION
-- Blocking Sessions
SELECT s.session_id,
s.blocking_session,
s.sample_time
FROM dba_active_sess_history s
-- s.dbid = 70854992
-- s.instance_number = 1
WHERE s.snap_id BETWEEN '&StSnap' and '&EdSnap'
AND s.blocking_session IS NULL
AND s.event IN
('enq: TX - row lock contention'
,'enq: TM - contention'
,'enq: UL - contention'
,'enq: TX - allocate ITL entry')
AND EXISTS
(SELECT 'exists'
FROM DBA_HIST_ACTIVE_SESS_HISTORY bs
-- bs.dbid = 70854992
-- bs.instance_number = 1
WHERE bs.snap_id BETWEEN '&StSnap' and '&EdSnap'
AND bs.blocking_session = s.session_id
AND bs.sample_time = s.sample_time
AND bs.blocking_session IS NOT NULL
AND bs.event IN
('enq: TX - row lock contention'
,'enq: TM - contention'
,'enq: UL - contention'
,'enq: TX - allocate ITL entry')
)
)
CONNECT BY NOCYCLE PRIOR session_id = blocking_session
AND PRIOR sample_time = sample_time

ORDER BY level DESC, blocked_sid, sample_time;

Log File Sync :

To Find out Storage is the problem?

-> Run AWR Report during the problematic time

-> Check "Wait Avg(ms)" for the wait event "log file sync", if it's less than 1s, we are good with storage,
if we more than that there is some issue with storage, i.e LGWR is slow to write to disk.

-> Check "Wait Avg(ms)" for the wait event "Log file parallel write", if it's less than 20s, we are good with storage,
if we more than 20s that there is some issue with storage subsystem, i.e LGWR is slow to write to disk.

-> Check LGWR Traces
You will notice a warning like below.

*** 2011-10-26 10:14:41.718
Warning: log write elapsed time 21130ms, size 1KB
(set event 10468 level 4 to disable this warning)

-> Check the number of log switches, if you notice the high number, consider increasing the log file size.

To find Issue from application side?

-> Excessive Application Commits
Excession commit can cause performance issue, since it flushes the redo from redo buffer to redo log. You can confirm by looking at the AWR report.

In the AWR or Statspack report,
if the average user calls per commit/rollback calculated as "user calls/(user commits+user rollbacks)" is less than 30, then commits are happening too frequently:

Adaptive Log File Sync

Adaptive Log File sync was introduced in 11.2. The parameter controlling this feature, _use_adaptive_log_file_sync, is set to false by default in 11.2.0.1 and 11.2.0.2.
In 11.2.0.3 the default is now true. When enabled, Oracle can switch between the 2 methods:

Post/wait, traditional method for posting completion of writes to redo log
Polling, a new method where the foreground process checks if the LGWR has completed the write.

Recommendations for storage

1. Work with the system administrator to examine the filesystems where the redologs are located with a view to improving the performance of IO.
2. Do not place redo logfiles on a RAID configuration which requires the calculation of parity, such as RAID-5 or RAID-6.
3. Do not put redo logs on Solid State Disk (SSD).
4. Look for other processes that may be writing to that same location and ensure that the disks have sufficient bandwidth to cope with the required capacity. If they don't then move the activity or the redo.

ORA-12012: error on auto execute of job “SYS”.”BSLN_MAINTAIN_STATS_JOB”

Error in Alert-Log :

ORA-12012: error on auto execute of job "SYS"."BSLN_MAINTAIN_STATS_JOB"

ORA-06502: PL/SQL: numeric or value error

ORA-06512: at "DBSNMP.BSLN_INTERNAL", line 2073

ORA-06512: at line 1

Solution :

SQL> select * from dba_tab_privs where table_name='DBMS_JOB';

GRANTEE OWNER TABLE_NAME GRANTOR PRIVILEGE GRA HIE

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

APEX_040200 SYS DBMS_JOB SYS EXECUTE NO NO

ODM SYS DBMS_JOB SYS EXECUTE NO NO

APPS SYS DBMS_JOB SYS EXECUTE NO NO

APPLSYS SYS DBMS_JOB SYS EXECUTE NO NO

SYSTEM SYS DBMS_JOB SYS EXECUTE YES NO

PUBLIC SYS DBMS_JOB SYS EXECUTE NO NO

SQL > GRANT EXECUTE ON sys.dbms_job to DBSNMP;

SQL> select * from dba_tab_privs where table_name='DBMS_JOB';

GRANTEE OWNER TABLE_NAME GRANTOR PRIVILEGE GRA HIE

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

APEX_040200 SYS DBMS_JOB SYS EXECUTE NO NO

ODM SYS DBMS_JOB SYS EXECUTE NO NO

APPS SYS DBMS_JOB SYS EXECUTE NO NO

APPLSYS SYS DBMS_JOB SYS EXECUTE NO NO

DBSNMP SYS DBMS_JOB SYS EXECUTE NO NO

SYSTEM SYS DBMS_JOB SYS EXECUTE YES NO

PUBLIC SYS DBMS_JOB SYS EXECUTE NO NO

SQL> select * from DBSNMP.BSLN_BASELINES;

DBID INSTANCE_NAME BASELINE_ID BSLN_GUID TI A STATUS LAST_COMP

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

1724681118 R1211BL 0 58605EC9134062C3CDE8DA5AA9CAE7B4 Y ACTIVE

704361310 PRODPACK 0 57A79678879E7D4A5EF045F734B4F638 Y ACTIVE

710768600 PRODPACK 0 04F1BA3A08B5399B9FF1783252D984F1 NX Y ACTIVE 05-APR-09

2987591379 GLDE 0 9521E07C475B7334089E22F0966942F4 XW Y ACTIVE 23-APR-12

193295451 PROD 0 0685D7B900D9C257EE3932966E60B586 ND Y ACTIVE 28-AUG-16

193295451 TEST 0 FBDCDE19CC84758789F4625BD7F5387A XW Y ACTIVE 04-SEP-16

SQL> DELETE FROM DBSNMP.BSLN_BASELINES WHERE INSTANCE_NAME ='R1211BL';

1 rows deleted.

SQL> DELETE FROM DBSNMP.BSLN_BASELINES WHERE INSTANCE_NAME ='PRODPACK';

2 rows deleted.

SQL> DELETE FROM DBSNMP.BSLN_BASELINES WHERE INSTANCE_NAME ='GLDE';

1 row deleted.

SQL> DELETE FROM DBSNMP.BSLN_BASELINES WHERE INSTANCE_NAME ='PROD';

1 row deleted.

SQL> commit;

Commit complete.

SQL> select * from DBSNMP.BSLN_BASELINES;

DBID INSTANCE_NAME BASELINE_ID BSLN_GUID TI A STATUS LAST_COMP

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

193295451 TEST 0 FBDCDE19CC84758789F4625BD7F5387A XW Y ACTIVE 04-SEP-16

SQL> EXEC DBMS_SCHEDULER.RUN_JOB('BSLN_MAINTAIN_STATS_JOB');

PL/SQL procedure successfully completed.

SQL>

select *

from (select owner, job_name, log_date, status, run_duration

from dba_scheduler_job_run_details a

where job_name = 'BSLN_MAINTAIN_STATS_JOB'

order by log_date)

where rownum < 10

OWNER JOB_NAME LOG_DATE STATUS RUN_DURATION

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

SYS BSLN_MAINTAIN_STATS_JOB 27-NOV-16 02.30.02.886624 AM -05:30 FAILED +000 00:00:02

SYS BSLN_MAINTAIN_STATS_JOB 04-DEC-16 02.30.03.314409 AM -05:30 FAILED +000 00:00:02

SYS BSLN_MAINTAIN_STATS_JOB 11-DEC-16 02.30.04.118379 AM -05:30 FAILED +000 00:00:04

SYS BSLN_MAINTAIN_STATS_JOB 18-DEC-16 02.30.04.237527 AM -05:30 FAILED +000 00:00:04

SYS BSLN_MAINTAIN_STATS_JOB 20-DEC-16 09.28.02.924042 AM -05:30 FAILED +000 00:00:04

SYS BSLN_MAINTAIN_STATS_JOB 20-DEC-16 09.31.17.559915 AM -05:30 SUCCEEDED +000 00:00:25

Ora-12560: TNS: protocol adapter error
************************************************

Make sure that you have set the correct ORACLE_SID:

C:\>sqlplus system/manager@orcl
SQL*Plus: Release 11.2.0.2.0 Production
ERROR:
ORA-12560: TNS:protocol adapter error
Enter user-name:
C:\>set ORACLE_SID=orcl
C:\>sqlplus system/manager@orcl
Connected to:
Oracle Database 11g Express Edition Release 11.2.0.2.0 - Production

SQL> startup
ORACLE instance started.
Total System Global Area 1071333376 bytes
Fixed Size 1388352 bytes
Variable Size 620757184 bytes
Database Buffers 444596224 bytes
Redo Buffers 4591616 bytes
Database mounted.
Database opened.

SQL>
If the above method doesn’t work, may be the OracleService for the database is not running. Check for the service, if it is not running then starts the service. If it is running then restart the service.

C:\>sqlplus
SQL*Plus: Release 11.2.0.2.0 Production on Sat Dec 17 22:34:24 2016
Copyright (c) 1982, 2010, Oracle. All rights reserved.
Enter user-name: / as sysdba
ERROR:
ORA-12560: TNS:protocol adapter error
Now restart the service using below method.

Start > Run > Type Services.msc

Start/Restart both Oracle service & listener service- OracleServiceORCL & OracleorclTNSListener

C:\>sqlplus
SQL*Plus: Release 11.2.0.2.0 Production on Sat Dec 17 22:41:30 2016
Copyright (c) 1982, 2010, Oracle. All rights reserved.
Enter user-name: / as sysdba
Connected to an idle instance.
SQL> startup
ORACLE instance started.
Total System Global Area 1071333376 bytes
Fixed Size 1388352 bytes
Variable Size 620757184 bytes
Database Buffers 444596224 bytes
Redo Buffers 4591616 bytes
Database mounted.
Database opened.

SQL>

ORA-12541: TNS:no listener
************************

Resolution:

Now you have to follow below mentioned steps to resolve the ORA-12541 issue.

STEP-1: First check your listener status.
*********************************

C:\>lsnrctl status

The above command will show the current status of your listener.

STEP-2: Start the listener, if listener is not running.
*****************************************

C:\>lsnrctl start

This command will start all your listener services.

STEP-3: Stop the listener, if listener is running.
***************************************

C:\>lsnrctl stop

This command will stop all your listener services.

STEP-4: Now restart the listener.
***************************

C:\>lsnrctl reload

This command will restart all your listener services.

Note: If you want to see all the available listener commands. Type lsnrtcl help on command prompt and you will get all available options.

C:\>lsnrctl help

LSNRCTL for 32-bit Windows: Version 11.2.0.2.0 – Production on 02-DEC-2016 20:25:14

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

The following operations are available
An asterisk (*) denotes a modifier or extended command:

start stop status
services version reload
save_config trace change_password
quit exit set*
show*

STEP-5: very important thing which you have to do.
*******************************************

Open sqlnet.ora file and make the changes as suggested.

ora-12541-error

Change NTS to NONE

SQLNET.AUTHENTICATION_SERVICES = (NONE)

Now restart the listener services and your listener problem ORA-12541 will be resolved.

While during impdp,I have seen the error ORA-39083 & ORA-02270 in impdp logfile.

ERROR:

ORA-02270: no matching unique or primary key for this column-list
Failing sql is:
ALTER TABLE "USER"."SMARTDB" ADD CONSTRAINT "PRLD_PRLM_FK" FOREIGN KEY ("PRLD_PRLM_FK") REFERENCES "PI OOL"."SMARTDB" ("PRLM_PK") DISABLE
ORA-39083: Object type REF_CONSTRAINT failed to create with error:

Workaround:

Compare the source and target environment tables,

Step 1: Check the tables which are having primary key disabled

SQL> select owner||''||constraint_name||''||constraint_type||''||status from dba_constraints where table_name='SMARTDB';

OWNER||''||CONSTRAINT_NAME||''||CONSTRAINT_TYPE||''||STATUS
------------------------------------------------------------------------
USER PRLM_PK P DISABLED
USER SYS_C0015976 C DISABLED
USER SYS_C0015975 C DISABLED
USER SYS_C0015974 C DISABLED
USER SYS_C0015973 C DISABLED
USER SYS_C0015972 C DISABLED

6 rows selected.

SQL> select owner||''||constraint_name||''||constraint_type||''||status from dba_constraints where table_name='SMARTDB';

OWNER||''||CONSTRAINT_NAME||''||CONSTRAINT_TYPE||''||STATUS
------------------------------------------------------------------------
USER PLM_PK P DISABLED
USER SYS_C0015986 C DISABLED
USER SYS_C0015985 C DISABLED
USER SYS_C0015984 C DISABLED
USER SYS_C0015983 C DISABLED
USER PLM_FK R DISABLED

6 rows selected.

Step 2:Enable the primary keys on SOURCE database

SQL> ALTER TABLE USER.SMARTDB enable CONSTRAINT PRLM_PK;

Table altered.

SQL> ALTER TABLE USER.SMARTDB enable CONSTRAINT PLM_PK;

Table altered.

SQL> select owner||''||constraint_name||''||constraint_type||''||status from dba_constraints where table_name='SMARTDB';

OWNER||''||CONSTRAINT_NAME||''||CONSTRAINT_TYPE||''||STATUS
------------------------------------------------------------------------
USER PRLM_PK P ENABLED
USER SYS_C0015976 C DISABLED
USER SYS_C0015975 C DISABLED
USER SYS_C0015974 C DISABLED
USER SYS_C0015973 C DISABLED
USER SYS_C0015972 C DISABLED

6 rows selected.

Step 3: Now do the expdp,copy the dump file and impdp in target database.
Remember to disable the primary keys at both Source and Target side.

In the final step,copy the new dump file and import into target database.

During startup,ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance.

SQL> startup

ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance
ORACLE instance started.

Total System Global Area 2147483648 bytes
Fixed Size 2926472 bytes
Variable Size 1392511096 bytes
Database Buffers 738197504 bytes
Redo Buffers 13848576 bytes
Database mounted.
Database opened.

SQL> SELECT name FROM v$parameter WHERE isdeprecated = 'TRUE';

NAME
--------------------------------------------------------------------------------
lock_name_space
instance_groups
resource_manager_cpu_allocation
active_instance_count
buffer_pool_keep
buffer_pool_recycle
log_archive_start
standby_archive_dest
parallel_server
parallel_server_instances
fast_start_io_target

NAME
--------------------------------------------------------------------------------
serial_reuse
rdbms_server_dn
max_enabled_roles
remote_os_authent
sec_case_sensitive_logon
global_context_pool_size
cursor_space_for_time
plsql_v2_compatibility
plsql_debug
background_dump_dest
user_dump_dest

NAME
--------------------------------------------------------------------------------
commit_write
sql_trace
parallel_automatic_tuning
parallel_io_cap_enabled

26 rows selected.

SQL> exit
Disconnected from Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

Cause: Obsolete or deprecated parameters for this instance type were specified in the SPFILE or the PFILE on the server side.

Action: See alert log for a list of parameters that are obsolete or deprecated. Remove them from the SPFILE or the server side PFILE.

Parameters that must have identical in RAC database:

In a RAC database there may contain several instances and the initialization parameters of all of the instances should not have identical setting. In fact the initialization parameters that are critical for database creation and affect certain database operations must have the same value for every instance in an Oracle RAC database.

Below is the list of initialization parameters that must have identical settings for all instances in a RAC database.

1)ACTIVE_INSTANCE_COUNT

2)ARCHIVE_LAG_TARGET

3)CLUSTER_DATABASE

4)CLUSTER_DATABASE_INSTANCES

5)COMPATIBLE

6)CONTROL_FILES

7)DB_BLOCK_SIZE

8)DB_DOMAIN

9)DB_FILES

10)DB_NAME

11)DB_RECOVERY_FILE_DEST

12)DB_RECOVERY_FILE_DEST_SIZE

13)DB_UNIQUE_NAME

14)DML_LOCKS (Only if set to zero).

15)INSTANCE_TYPE (RDBMS or ASM)

16)PARALLEL_MAX_SERVERS

17)REMOTE_LOGIN_PASSWORD_FILE

18)UNDO_MANAGEMENT

OIDMOS status stop and OID not starting up after crash

Our system has a system shutdown in which OID 11.1.1.9 was running and not starting up using opmnctl after server is brought up. A few things I went through to fix it up is posted below.

Check the status from the Oracle Instance home as below.

[apploid@oam01 bin]$ ./opmnctl status

Processes in Instance: asinst_1

———————————+——————–+———+———

ias-component | process-type | pid | status

———————————+——————–+———+———

ohs1 | OHS | 19283 | Alive

ovd1 | OVD | 19282 | Alive

oid1 | oidldapd | N/A | Down

oid1 | oidmon | 5562 | Stop

EMAGENT | EMAGENT | 19281 | Alive

You can see oidmon is stopped and oidldap is down. Normally opmnctl startall can bring up in almost all the cases, but I was getting time outs and stuck at below in the oidmon****.log file.

[2015-09-04T13:23:59.800201+10:00] [OID] [NOTIFICATION:16] [] [OIDMON] [host: oam01.saroj.com.au] [pid: 19273] [tid: 0] OIDMON_STOP: Thread started

[2015-09-04T13:23:59.807343+10:00] [OID] [NOTIFICATION:16] [] [OIDMON] [host: oam01.saroj.com.au] [pid: 19273] [tid: 0] OIDMON_STOP: Connecting to database, connect string is oiddb

I did check the database connectivity from the OID application server, checked the ODS schema status and almost everything including the status in ODS_PROCESS_STATUS (I will post about this table soon).

Since we had a abrupt shutdown, I guessed we have some uncleaned files in the directory below. Removed the files after taking the backup after shutting down everything, then try starting up.

$ORACLE_INSTANCE/bin/opmnctl stopall

cd $ORACLE_INSTANCE/config/OPMN/opmn/states

[apploid@oam01 states]$ ls

p1515733570

[apploid@oam01 states]$ cd ..

[apploid@oam01 opmn]$ mv states states_bak

[apploid@oam01 opmn]$ mkdir states

$ORACLE_INSTANCE/bin/opmnctl startall

Check the log file

[apploid@oam01 opmn]$ tail -f /u01/oid/Oracle/Middleware/asinst_1/diagnostics/logs/OID/oid1/oidmon-0000.log

[2015-09-04T13:33:43.438248+10:00] [OID] [NOTIFICATION:16] [] [OIDMON] [host: oam01.saroj.com.au] [pid: 19771] [tid: 0] Guardian: Starting OIDLDAPD cmdLine args = “instance=1 inst=1 “

[2015-09-04T13:33:43.446457+10:00] [OID] [NOTIFICATION:16] [] [OIDMON] [host: oam01.saroj.com.au] [pid: 19771] [tid: 0] Guardian: Starting OIDLDAP Server,PID=19818

[2015-09-04T13:33:43.449019+10:00] [OID] [NOTIFICATION:16] [] [OIDMON] [host: oam01.saroj.com.au] [pid: 19771] [tid: 0] Guardian: Updating Process Table…

[2015-09-04T13:33:43.452984+10:00] [OID] [NOTIFICATION:16] [] [OIDMON] [host: oam01.saroj.com.au] [pid: 19771] [tid: 0] Guardian: gsldda_DeleteEntry:gsldfgGetEntryID Error..1010

[2015-09-04T13:33:43.707887+10:00] [OID] [NOTIFICATION:16] [] [OIDMON] [host: oam01.saroj.com.au] [pid: 19771] [tid: 0] Guardian: CreateInstance: Successfuly created entry cn=asinst_1_oid1_1_oam01.saroj.com.au,cn=osdldapd,cn=subregistrysubentry

[2015-09-04T13:33:53.403166+10:00] [OID] [NOTIFICATION:16] [] [OIDMON] [host: oam01.saroj.com.au] [pid: 19771] [tid: 0] Guardian: gslmmonOpmnProcStatus: Sending OIDLDAPD PID=,19956 status to OPMN

[2015-09-04T13:33:55.405243+10:00] [OID] [NOTIFICATION:16] [] [OIDMON] [host: oam01.saroj.com.au] [pid: 19771] [tid: 0] Guardian: gslmmonOpmnProcStatus:Sending OID Host and ports info to OPMN

HOST=oam01.saroj.com.au LDAP NONSSL PORT = 3060 LDAP SSL PORT = 3131

[apploid@oam01 bin]$ ./opmnctl status

Processes in Instance: asinst_1

———————————+——————–+———+———

ias-component | process-type | pid | status

———————————+——————–+———+———

ohs1 | OHS | 19773 | Alive

ovd1 | OVD | 19772 | Alive

oid1 | oidldapd | 19956 | Alive

oid1 | oidldapd | 19818 | Alive

oid1 | oidmon | 19771 | Alive

EMAGENT | EMAGENT | 19770 | Alive

OID EMCTL Agent not starting due to Daylight Savings Timezone Issue

The issue was actually because of incorrect timezone daylight savings updates in the installed JDK and JRE

Simply update the timezone in your installed JDK and JRE. On the safe side I had updated the timezone for ALL the installed JDK and JRE in my entire Fusion Middleware stack.

Step 1. Rerun the reset timezone command, which will now complete successfully.

$ export TZ=Pacific/Newyork

$ ./emctl resetTZ agent

Oracle Enterprise Manager 10g Release 5 Grid Control 10.2.0.5.0.

Copyright (c) 1996, 2009 Oracle Corporation. All rights reserved.

Updating /app/oracle/config/instances/oid1/EMAGENT/EMAGENT/sysman/config/emd.properties...

Successfully updated /app/oracle/config/instances/oid1/EMAGENT/EMAGENT/sysman/config/emd.properties.

Login as the em repository user and run the script:

exec mgmt_target.set_agent_tzrgn('idm117.aclnz.com:5162','Pacific/Newyork')

and commit the changes

This can be done for example by logging into sqlplus and doing

SQL> exec mgmt_target.set_agent_tzrgn('idm117.aclnz.com:5162','Pacific/Newyork')

SQL> commit

Step 2. As a part of the above reset command, it will ask you to run a script at the SQL prompt. But when you run that scipt, you will receive the following error:

SQL> exec mgmt_target.set_agent_tzrgn('idm117.aclnz.com:5162','Pacific/Newyork');

BEGIN mgmt_target.set_agent_tzrgn('idm117.aclnz.com:5162','Pacific/Newyork'); END;

*

ERROR at line 1:

ORA-20233: Invalid agent name idm117.aclnz.com:5162

ORA-06512: at "SYSMAN.MGMT_TARGET", line 3811

ORA-06512: at line 1

Step 3. According to MOS DOC ID 388280.1, the error: ORA-20233: Invalid agent name agentmachine.domain:3872 will occur if the Agent has not successfully started even once and communicated its details to the OMS. You can confirm this by querying the MGMT_TARGETS table in the sysman schema:

SQL> select target_name, target_type from mgmt_targets where target_name like '%agentmachine.domain%';

To execute the mgmt_target.set_agent_tzrgn procedure, there should be a target of type 'oracle_emd' in this table.

And in our case we could never be able to start OID EMCTL agent before, so we followed Oracle solution for this issue. The solution was to simply ignore the error and start the emctl agent (that is "Skip the steps suggested by the mgmt_target.set_agent_tzrgn routine. These are needed only if the Agent was already communicating with the OMS and its TZ has changed.").

Step 4. Now simply start the OID emctl agent with the below command and we could start it successfully.

$ ./emctl start agent

Oracle Enterprise Manager 10g Release 5 Grid Control 10.2.0.5.0.

Copyright (c) 1996, 2009 Oracle Corporation. All rights reserved.

Starting agent ............................. started.
Adop is not to able to detect any valid application tier nodes
Adop is not to able to detect any valid application tier nodes

Issue:
Running ADOP on 12.2 is failing at initial Validation with error “adop is not able to detect any valid application tier nodes”
Enter the APPS password:
Enter the SYSTEM password:
Enter the WLSADMIN password:

Validating credentials...

Initializing...
Run Edition context : /u01/oracle/VIS/fs1/inst/apps/VIS_ora01/appl/admin/VIS_ora01.xml
Patch edition context: / u01/oracle/VIS/fs2/inst/apps/VIS_ora01/appl/admin/VIS_ora01.xml
*******FATAL ERROR*******
PROGRAM : (/u01/oracle/VIS /fs1/EBSapps/appl/ad/12.0.0/bin/adzdoptl.pl)
TIME : Wed Apr 22 04:40:38 2015
FUNCTION: ADOP::GlobalVars::_GetMandatoryArgs [ Level 1 ]
ERRORMSG: adop is not able to detect any valid application tier nodes in
ADOP_VALID_NODES table. Ensure autoconfig is run on all nodes.

[STATEMENT] Please run adopscanlog utility, using the command

"adopscanlog -latest=yes"

to get the list of the log files along with snippet of the error message corresponding to each log file.

adop exiting with status = 255 (Fail)

Cause
Upon investigation we found that Database listener is not listening ebs_patch service which is mandatory for 12.2 to work on any adop activities.
[oracle@ora01 ~]$ lsnrctl status $ORACLE_SID
LSNRCTL for Linux: Version 11.2.0.4.0 - Production on 23-APR-2015 12:20:02
Copyright (c) 1991, 2013, Oracle. All rights reserved.
Alias VIS
Listening Endpoints Summary...
.
.
Services Summary...
Service "VIS" has 2 instance(s).
Instance "VIS", status UNKNOWN, has 1 handler(s) for this service...
Instance "VIS", status READY, has 1 handler(s) for this service...
The command completed successfully
Solution
1) Make sure that Database init parameter has service name ebs_patch defined
2) Connect to Database as sysdba
sqlplus / as sysdba
SQL> show parameter service_name

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
service_names string VIS, ebs_patch
If this is there, set the parameter as below
SQL> alter system set service_names=’ebs_patch’,’VIS’ scope=spfile;

3) Verify init parameter LOCAL_LISTENER and set it to <DB_NAME>_LOCAL
SQL> alter system set local_listener=’VIS_LOCAL’ scope=spfile;

4) Bounce the application & database services

ERRORS During 12.2.4 Upgrade

Error 1:

If WF_DEFERRED_R Invalid then upgrade patch 12.2.4 failed with below Error :

R12: "ORA-04063: rule set "APPLSYS.WF_DEFERRED_R" has errors" Error When Attempting to Apply Patch 6435000

select object_name, object_type, status from dba_objects where object_name='WF_DEFERRED_R' ;

FIX: NoteID :553673.1

set serverout on

declare

lagent sys.aq$_agent;

subscriber_exist exception;

pragma EXCEPTION_INIT(subscriber_exist, -24034);

begin

lagent := sys.aq$_agent('WF_DEFERRED',null,0);

dbms_aqadm.add_subscriber(

queue_name =>'APPLSYS.WF_DEFERRED',

subscriber=>lagent,

rule=>'1=1');

exception

when subscriber_exist then

-- just add the rule if subscriber exists

dbms_aqadm.alter_subscriber(queue_name =>'APPLSYS.WF_DEFERRED',

subscriber=>lagent,

rule=>'1=1');

end;

ERROR 2:

adwork018.log:ORA-04043: object PO_ASL_API_ERROR_REC does not exist

adwork019.log:ORA-20001: Could not apply Crossedition Trigger

adwork019.log:"APPS"."PA_COST_DISTRIBUTION_LINES_F1": ORA-06502: PL/SQL: numeric or value

adwork019.log:ORA-06512: at "APPS.AD_ZD", line 29

adwork019.log:ORA-06512: at "APPS.AD_ZD_TABLE", line 21

adwork019.log:ORA-06512: at "APPS.AD_ZD_TABLE", line 1703

adwork019.log:ORA-06512: at line 1

adwork020.log:ORA-20001: Could not apply Crossedition Trigger

adwork020.log:"APPS"."PA_COST_DISTRIBUTION_LINES_F1": ORA-06502: PL/SQL: numeric or value

adwork020.log:ORA-06512: at "APPS.AD_ZD", line 29

adwork020.log:ORA-06512: at "APPS.AD_ZD_TABLE", line 21

adwork020.log:ORA-06512: at "APPS.AD_ZD_TABLE", line 1703

adwork020.log:ORA-06512: at line 1

FIX: Need to Run @bug14296972_apply.sql Available in the $ORACLE_HOME/admin/scripts

SQL> desc sys.DBMS_PARALLEL_EXECUTE_TASK$

Name Null? Type

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

TASK_OWNER# NOT NULL NUMBER

TASK_NAME NOT NULL VARCHAR2(128)

CHUNK_TYPE NOT NULL NUMBER

STATUS NOT NULL NUMBER

TABLE_OWNER VARCHAR2(30)

TABLE_NAME VARCHAR2(30)

NUMBER_COLUMN VARCHAR2(30)

CMT VARCHAR2(4000)

JOB_PREFIX VARCHAR2(30)

STOP_FLAG NUMBER

SQL_STMT CLOB

LANGUAGE_FLAG NUMBER

EDITION VARCHAR2(32) APPLY_CROSSEDITION_TRIGGER VARCHAR2(32)

FIRE_APPLY_TRIGGER VARCHAR2(10)

PARALLEL_LEVEL NUMBER

JOB_CLASS VARCHAR2(30)

Edition size should be varchar2 (32) length previously it was 30

ERROR 3: Prepare phase will fail with below error

adop is not able to detect any valid application tier nodes in

ADOP_VALID_NODES table.

Fix: Error due to invalid entry in the ADOP_VALID_NODES after AD/TXK patches

Node Status

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

node name multiple entries for PATCH context file found

ERROR:

Nodes with context files in the FND_OAM_CONTEXT_FILES table on both run and patch file systems: NONE

Nodes without context files in the FND_OAM_CONTEXT_FILES table on either/or run and patch file systems:

Corrective Action:

- If the run file system context file for a node is missing, run AutoConfig on the run file system of that node to sync with the value with the database.

- If the patch file system context file of a node is missing, run AutoConfig on the patch file system of that node with the -syncctx option as follows to sync with the

value with the database.

On UNIX:

sh <AD_TOP>/bin/adconfig.sh contextfile=<CONTEXT_FILE> -syncctx

1. Connect to SQL*PLUS as "APPLSYS" user.

2. Backup the FND_OAM_CONTEXT_FILES table.

SQL> CREATE TABLE fnd_oam_context_files_bak AS SELECT * FROM fnd_oam_context_files;

3. Truncate the FND_OAM_CONTEXT_FILES table.

SQL> TRUNCATE TABLE fnd_oam_context_files;

Take complete Application down.

cd $ADMIN_SCRIPTS_HOME

sh adstpall.sh apps/apps

4. Run Autoconfig on database and all nodes at RUN using:

Run Autoconfig on db tier.

sh $ORACLE_HOME/appsutil/scripts/.../adautocfg.sh

Run Autoconfig on apps tier.

cd $ADMIN_SCRIPTS_HOME

sh adautocfg.sh

5 - Executed on the RUN file system to upload the PATCH context file:

copy command line by line and run on appstier.

replace PATCH_CONTEXT_FILE with full path.

$ADJVAPRG oracle.apps.ad.autoconfig.oam.CtxSynchronizer \

action=upload \

contextfile=<PATCH_CONTEXT_FILE>\

logfile=/tmp/patchctxupload.log

6. Re run failed Prepare session

AutoConfig: Parallel Run Option on R12.1.1

The “Parallel Run” feature enables AutoConfig to be executed simultaneously across multiple nodes of an Oracle E-Business Suite instance. Certain AutoConfig configurations of one node depend on the configurations of other nodes. When running in parallel mode, AutoConfig uses dbms_locks so that the configuration of one node does not interfere with the configuration of other nodes. During the instantiation (INST) phase, locking is done at the script level. During the execution (EXEC) phase, locking is done at the product_top level.

AutoConfig can be run in parallel mode on the application tier with the following command:

perl $AD_TOP/bin/adconfig.pl contextfile=<CtxFile> [product=<product_top>] –parallel

Where <CtxFile> is the absolute path of the applicaton tier context file, and <product_top> is the short name of the product to be configured.

AutoConfig can be run in parallel mode on the database tier with the following command:

perl $ORACLE_HOME/appsutil/bin/adconfig.pl contextfile=<CtxFile> -parallel

Where <CtxFile> is the absolute path of the database tier context file.

In parallel mode, AutoConfig must be invoked with the “–parallel” option on all nodes of a multi-node environment.

Weblogic Server 12.1.2 Performance Issue Due To weblogic.socket.NIOSocketMuxer

Weblogic server 12.1.2 in a runnable state consuming high CPU resources.

Error:

"LDAPConnThread-579 ldaps://ldapserver.us.oracle.com:636" daemon prio=10 tid=0x00000000041f6800 nid=0x56d7 runnable [0x00007f9b6b9f8000]

java.lang.Thread.State: RUNNABLE

at sun.nio.ch.IOUtil.drain(Native Method)

at sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:90)

- locked <0x000000078a2f6e48> (a java.lang.Object)

at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:87)

- locked <0x000000078a2f6b48> (a sun.nio.ch.Util$2)

- locked <0x000000078a2f6b38> (a java.util.Collections$UnmodifiableSet)

- locked <0x000000078a2f6910> (a sun.nio.ch.EPollSelectorImpl)

at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:98)

at weblogic.socket.NIOSocketMuxer$NIOInputStream.readInternal(NIOSocketMuxer.java:815)

at weblogic.socket.NIOSocketMuxer$NIOInputStream.read(NIOSocketMuxer.java:759)

at weblogic.socket.NIOSocketMuxer$NIOInputStream.read(NIOSocketMuxer.java:742)

at weblogic.socket.JSSEFilterImpl.readFromNetwork(JSSEFilterImpl.java:462)

at weblogic.socket.JSSEFilterImpl.read(JSSEFilterImpl.java:424)

at weblogic.socket.JSSESocket$JSSEInputStream.read(JSSESocket.java:64)

at java.io.BufferedInputStream.fill(BufferedInputStream.java:235)

at java.io.BufferedInputStream.read(BufferedInputStream.java:254)

- locked <0x000000079c2dc630> (a java.io.BufferedInputStream)

at netscape.ldap.ber.stream.BERElement.getElement(Unknown Source)

at netscape.ldap.LDAPConnThread.run(Unknown Source)

at java.lang.Thread.run(Thread.java:745)

Fix:

In this case, as customer was using Linux x86-64, changing the MuxerClass from weblogic.socket.NIOSocketMuxer to weblogic.socket.PosixSocketMuxer worked.

In WLS Admin Console

Go to Environment > Servers > Server Name > Tuning, under Advanced, set the Muxer Class based on the OS and Reboot the server.

Solaris/HP-UX Native Muxer : weblogic.socket.DevPollSocketMuxer

POSIX Native Muxer : weblogic.socket.PosixSocketMuxer

Windows Native Muxer : weblogic.socket.NTSocketMuxer

Java Muxer : weblogic.socket.JavaSocketMuxer

You may also set the above in the Weblogic startup scripts via the JAVA_OPTIONS:

-Dweblogic.MuxerClass=weblogic.socket.PosixSocketMuxer

Cannot identify any valid application tier nodes in ADOP_VALID_NODES

Issue:

PROGRAM : (/u01/oracle/fs1/EBSapps/appl/ad/12.0.0/bin/adzdoptl.pl)

TIME :

FUNCTION: ADOP::GlobalVars::_GetMandatoryArgs [ Level 1 ]

ERRORMSG: Cannot identify any valid application tier nodes in

ADOP_VALID_NODES table. Ensure AutoConfig has been run on all nodes.

[STATEMENT] Please run adopscanlog utility, using the command

“adopscanlog -latest=yes”

Solution 1:

1. Run autoconfig on application node

2.Now run adop

Workflow mailer outbound and inbound setup for R12 Oracle Applications.

Assumption : It is assumed that the setup is being done for both outbound (send emails) and inbound (to process approvals).

Pre-requirements:

1. SYSADMIN user access or Oracle Applications access which has system administrator access.

2. SMTP server hostname and port detail

3. SMTP Server's port access from Oracle Applications server where concurrent is running

4. Oracle Applications Web's physical host and active Port

5. webmail workflow email id and password (access), once you have access, Create the PROCESSED AND DISCARD folders from the EMAIL application.
Please note : IMAP protocol is alone available.

Configuration Steps:

1. Login to Oracle applications --> System administrator --> oracle Applications manager --> workflow

2. Click over notification mailer.

3. Ensure that the Notification Mailer is stopped, Else select the stop from the Lov (right corner in the same row), and click Go
please wait for few minutes until it is stopped (you will see user deactivated)

4. click on Edit and Advanced.

5. Best practices is to have Startup mode as Automatic (which will bring up mailer services automatically when workflow containers are up).
it is up to you, if you would like to bring up manual, you may select startup mode as manual.

6. Click next, Ensure Inbound thread count and outbound thread count as 1

7. Click Next, in Inbound Email Account section, Select Inbound protocal => IMAP, Enter the Inbound Server Name, Webmail username & Password

8. In Outbound Email Account section, Enter Outbound Server name . if you have outbound authentication, then enter the userid and password.

9. Ensure that all points in pre-req 4 completed, click next.

10. Ensure 'From' has Correct entry, and map reply-to address (workflow@abczyx.com) as webmail email id, ensure HTML Agent has correct URL.

11. Related to Workflow mailer configuration, all above steps only related , you may click finish, or Click next till the end, review the details and click finish.

12. PLEASE NOTE, DONT START THE SERVICES yet

13. Navigate --> System administrator -->Profiles --> system

14. Query "WF: Workflow Mailer Framework Web Agent", click find, ensure "IT SHOULD HAVE PHYSICAL WEB SERVER ADDRESS AND ACTIVE WEB PORT ENTRY", if in case your web URL is virtual host.

15. Once saved, Start the workflow mailer services (Oracle applications --> System administrator --> oracle Applications manager --> workflow Notification Mailer --> start)

Additional info :

If you want to outbound (send emails) alone and not approvals , make inbound thread count as 0 and outbound thread count as 1,
and dont provide any details related to inbound.

Narasimha Rao

How to Exclude Failure Notice/Any Pattern Emails from Processing in Oracle Applications Workflow

When there is a out of office notification or Email got bounced it will be sent to workflow, This post is to provide the steps to configure how to exclude or (in other words, how to make oracle workflow to ignore those email and move it to Discard folder in workflow email account).

Assumption :

Workflow Mailer is configured for both inbound and outbound , and up & running.

Configuration Steps:

1. Login to Oracle applications --> System administrator --> oracle Applications manager --> workflow.

2. Click over notification mailer.

3. Ensure that the Notification Mailer is stopped, Else select the stop from the Lov (right corner in the same row), and click Go.

please wait for few minutes until it is stopped (you will see user deactivated)

4. click on Edit and Advanced.

5. “Click on Next till Tags”

6. Login to Workflow inbox and get the Pattern - Key word in subject – which has to be ignored from processing.

7. In the Workflow Mailer tag configuration, click on “Add Another Row” and Add the key word found in Step 5 as pattern and Action as “Ignore”.

8. Click on next and finish.

9. Start the Workflow Mailer.

10. Once the Workflow Mailer is up, please check the discard folder in workflow inbox , the emails with such patterns needs to be moved to Discard folder automatically.

-- Narasimha Rao

EBS R12.2 Cloning Steps

Solved " ORA-16057: server not in Data Guard configuration " , in oracle dataguard environment

Article 15

Adpreclone Fails in EBS 12.2.3 : There is already an ACTIVE ADOP CYCLE with session id

Article 14

Actualize the old database editions after online patching to avoid possible performance issues: EBS 12.2.3/12.2.4

History of enq: TX - row lock contention

WAIT Event : Log File Sync

Log File Sync :

To Find out Storage is the problem?

To find Issue from application side?

Adaptive Log File Sync

Recommendations for storage

Article 11

ORA-12012: error on auto execute of job “SYS”.”BSLN_MAINTAIN_STATS_JOB”

Ora-12560: TNS: protocol adapter error

ORA-12541: TNS:no listener

Errors during impdp ORA-39083 & ORA-02270

ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance

Identical parameters in RAC

Article 5

OIDMOS status stop and OID not starting up after crash

Article 4

OID EMCTL Agent not starting due to Daylight Savings Timezone Issue

Article 3

ERRORS During 12.2.4 Upgrade

Article 2

AutoConfig: Parallel Run Option on R12.1.1

Article 1

Weblogic Server 12.1.2 Performance Issue Due To weblogic.socket.NIOSocketMuxer

Article 0

Cannot identify any valid application tier nodes in ADOP_VALID_NODES

Issue:

Workflow mailer outbound and inbound setup

How to Exclude Failure Notice/Any Pattern Emails from Processing in Oracle Applications Workflow