Oracle EBS Concurrent Mangers logs files

Concurrent Managers log files are located in the $APPLCSF/$APPLLOG location



cd $APPLCSF/$APPLLOG
For ICM Log                     –> ls -lrt *$TWO_TASK*
For Standard manager Log        –> ls -lrt w*.mgr
For Conflict Resolution manager Log –> ls -lrt c*.mgr

SQL Query to get ICM manager log file location

SELECT 'ICM_LOG_NAME=' || fcp.logfile_name

FROM fnd_concurrent_processes fcp, fnd_concurrent_queues fcq

WHERE fcp.concurrent_queue_id = fcq.concurrent_queue_id

AND fcp.queue_application_id = fcq.application_id

AND fcq.manager_type = '0'

AND fcp.process_status_code = 'A';

How to Create a Oracle EBS Custom Concurrent Manager

Reference:

How to Create a Custom Concurrent Manager [ID 170524.1]

A. Define Concurrent Manager

Manager : XXXX Custom Manager

Short Name : XXXX_CUSTOM_MANAGER

Application Name: XXXX Custom Application

Type : Concurrent Manager

Cache Size : 5

Name : FNDLIBR

B. Assign workshift

Work Shift : Standard

Processes : 1

C. Include concurrent program to newly created concurrent manager

D. Exclude concurrent program from the standard manager
E. Bounce concurrent manager to take effect

Oracle Database Managing the Redo Log

List the current redo file and size:

set linesize 160
col MEMBER for a50
select a.GROUP#, a.THREAD#, a.BYTES/1024/1024 BYTES_MB, b.MEMBER from  V$LOG a, v$logfile b where a.GROUP# = b.GROUP#;


Add Redo log group:

ALTER DATABASE ADD LOGFILE GROUP 3 ('/diso3i/oradata/data/log03a.dbf','/diso3i/oradata/data/log03b.dbf') size 1000M;

Migrating a MS SQL Server Database to Oracle Database 11g

Click here to see the steps for Migrating a Microsoft SQL Server Database to Oracle Database 11g

Oracle EBS Missing Responsibilities

Here are some of the MOS Notes which as further details about this issue.

How To Fix Missing Responsibilities For A User (Doc ID 429852.1 )
Missing Responsibilities after 12.1.3 Upgrade (Doc ID 1309852.1 )
Missing responsibilities in R12.1.3 (Doc ID 1423432.1 )
Missing Responsibilities of direct/indirect Responsibilities Assignment After Upgrade To 12.1.3 From 11i (Doc ID 1581955.1 )

Cleaning up the FND_NODES Table

Reference:

Note: 260887.1 – How to Clean Nonexistent Nodes or IP Addresses From FND_NODES

Why we need to clean FND_NODES table post cloning?

Because this table contains the IP Addresses of the source servers (apps and db) and when you clone your target servers have different IP Addresses, and this need to be populated in FND_NODES table.

Select the current value


set linesize 160
col NODE_NAME for a30
col SERVER_ADDRESS for a16
select SERVER_ADDRESS, node_name, node_mode, support_cp, support_web, support_admin,support_forms from FND_NODES;

From sqlplus execute the following command:


SQL> EXEC FND_CONC_CLONE.SETUP_CLEAN;
COMMIT;


This deletes data from a few FND tables such as FND_NODES but after AutoConfig has been executed they will contain the correct values.

Run AutoConfig on Database and Application Servers.

Force all Oracle EBS users to change their password

Reference: Note: 414976.1 – How To Force All Applications Users To Change Their Password? We might have the requirement to force all EBS users to change their passwords due to some requirement. run Sql Script like below or same you can achieve by submitting concurrent request.

sqlplus -s APPS/apps @AFCPEXPIRE.sql