Friday, August 22, 2025

fnd concurrent request queues and logs update

 

create table apps.fnd_concurrent_queues_oci as select * from apps.fnd_concurrent_queues;
create table fnd_concurrent_requests_oci as select * from fnd_concurrent_requests;
create table xxau_fnd_concurrent_requests_oci as select * from xxau_fnd_concurrent_requests;
create table fnd_conc_req_outputs_oci as select * from apps.fnd_conc_req_outputs;

select CONCURRENT_QUEUE_NAME,NODE_NAME,NODE_NAME2,target_node from fnd_concurrent_queues_oci ;
select CONCURRENT_QUEUE_NAME,NODE_NAME,NODE_NAME2,target_node from fnd_concurrent_queues ;


select 'update fnd_concurrent_queues set node_name='''||NODE_NAME||''',NODE_NAME2='''||NODE_NAME2||''',TARGET_NODE='''||TARGET_NODE||''' where CONCURRENT_QUEUE_NAME ='''||CONCURRENT_QUEUE_NAME||''';' from fnd_concurrent_queues_oci;

 

col CONCURRENT_QUEUE_NAME for a20
set pages 500 lines 500
col 'Target_Node' for a20
col 'Node_Name' for a20
col 'Node_name2' for a20
select CONCURRENT_QUEUE_NAME,NODE_NAME,NODE_NAME2,target_node from fnd_concurrent_queues;
select CONCURRENT_QUEUE_NAME,TARGET_NODE,NODE_NAME,NODE_NAME2,RUNNING_PROCESSES,PCP_FLAG from fnd_concurrent_queues;
select CONCURRENT_QUEUE_NAME,TARGET_NODE,NODE_NAME,NODE_NAME2,RUNNING_PROCESSES,PCP_FLAG from fnd_concurrent_queues where target_node is not null;

update fnd_concurrent_queues set node_name='ASBAVEBSPRD17',NODE_NAME2='ASBAVEBSPRD18',TARGET_NODE='ASBAVEBSPRD17' where CONCURRENT_QUEUE_NAME in ( 'FNDICM','STANDARD','PASMGR','INVMGR','MRPMGR','WFALSNRSVC','WFMLRSVC','XDP_MANAGER','IEU_WL_CS','OKCCONCMGR','IEXCONMGR','OAMCOLMGR','WFWSSVC','FNDCPOPP','IEU_SH_CS','WFMGSMS','WFMGSMD','WMSTAMGR','CMICRM','FTE_TXN_MANAGER','AMSDMIN','FNDCRM','FNDSCH','PODAMGR','RCVOLTM','INVTMRPM','CRPINQMGR');

update fnd_concurrent_queues set node_name='ASBAVEBSPRD18',NODE_NAME2='ASBAVEBSPRD17',TARGET_NODE='ASBAVEBSPRD18' where CONCURRENT_QUEUE_NAME in ( 'XX_AU_MGR','XXSTD_ASC_DBMSPIPE');
Commit;


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


select CONCURRENT_QUEUE_NAME,TARGET_NODE,NODE_NAME,NODE_NAME2,RUNNING_PROCESSES,PCP_FLAG from fnd_concurrent_queues where target_node is not null;


select distinct(TARGET_NODE)from fnd_concurrent_queues where target_node is not null;
select distinct(NODE_NAME)from fnd_concurrent_queues where target_node is not null;
select distinct(NODE_NAME2)from fnd_concurrent_queues where target_node is not null;

update fnd_concurrent_queues set target_node='ASBAVEBSPRD17' where target_node='IRXVLP0628';
update fnd_concurrent_queues set node_name='ASBAVEBSPRD17' where node_name='IRXVLP0628';
update fnd_concurrent_queues set node_name2='ASBAVEBSPRD17' where node_name2='IRXVLP0628';
 
update fnd_concurrent_queues set target_node='ASBAVEBSPRD18' where target_node='IRXVLP0629';
update fnd_concurrent_queues set node_name='ASBAVEBSPRD18' where node_name='IRXVLP0629';
update fnd_concurrent_queues set node_name2='ASBAVEBSPRD18' where node_name2='IRXVLP0629';
 
select distinct(logfile_node_name) from fnd_concurrent_requests; 
LOGFILE_NODE_NAME
----------------------------------------------------------------------------------------------------
ASBAVEBSDEV04
ASBAVEBSDEV03
ASBAVEBSI1B04
ASBAVEBSI1B03
IRXVLP0628
IRXVLP0629


select distinct(outfile_node_name) from fnd_concurrent_requests;
select distinct(logfile_node_name) from fnd_concurrent_requests;
select distinct(NODE_NAME1) from fnd_concurrent_requests;
select distinct(NODE_NAME2) from fnd_concurrent_requests;

update fnd_concurrent_requests set logfile_node_name='ASBAVEBSPRD17' where logfile_node_name='IRXVLP0628';
update fnd_concurrent_requests set logfile_node_name='ASBAVEBSPRD18' where logfile_node_name='IRXVLP0629';
update fnd_concurrent_requests set outfile_node_name='ASBAVEBSPRD17' where outfile_node_name='IRXVLP0628';
update fnd_concurrent_requests set outfile_node_name='ASBAVEBSPRD18' where outfile_node_name='IRXVLP0629';
update fnd_concurrent_requests set NODE_NAME1='ASBAVEBSPRD17' where NODE_NAME1 in ('IRXVLP0628');
update fnd_concurrent_requests set NODE_NAME1='ASBAVEBSPRD18' where NODE_NAME1 in ('IRXVLP0629');

commit;




Thursday, July 11, 2024

Execute Curl Utility to transfer tar file to Object Storage

Command to Upload Backup to Object Storage For OEL 5.8 the wget&curl TSLV is disabled please use Java option curl -X PUT -T / -u ‘@miracle.com:’ https://swiftobjectstorage.us-.miracleecloud.com/v1/// -x omcs-proxy.miracleoutsourcing.com:80 or java -jar uploadcli.jar -url https://swiftobjectstorage.us-phoenix-1.oraclecloud.com/v1/ -user fist.lastname@miracle.com -container .tar.gz

Tuesday, March 19, 2024

Important 12.2 Documents

10 References

This section lists the reference material that can be read to gain further knowledge in the various areas relevant to establishing a Maximum Availability Architecture for Oracle E-Business Suite, including the materials referenced to develop the processes described in this paper.

Database MAA:

Oracle Database High Availability Overview and Best Practices

Automatic Storage Management Administrator's Guide

Database Backup and Recovery User's Guide

 “Oracle Flashback Technology” in Oracle Database Concepts

Flashback Database Best Practices & Performance (Doc ID 565535.1)

“Using Edition Based Redefinition” in the Database Development Guide

Database Oracle Data Guard:

Data Guard Concepts and Administration

Data Guard Broker

Creating a Physical Standby using RMAN Duplicate (RAC or Non-RAC) (Doc ID 1617946.1)

Using Active Data Guard Reporting with Oracle E-Business Suite Release 12.2 and Oracle Database 19c (Doc ID 2608030.1)

Oracle Patch Assurance - Data Guard Standby-First Patch Apply (Doc ID 1265700.1)

Oracle Real Application Clusters (RAC):

Real Application Clusters Administration and Deployment Guide

Clusterware Administration and Deployment Guide

Using Oracle 19c RAC Multitenant (Single PDB) with Oracle E-Business Suite Release 12.2 (Doc ID 2530665.1)

Oracle RAC Rolling Install Process for the “Oracle JavaVM Component Database PSU” (OJVM PSU) Patches (Doc ID 2217053.1)

Oracle E-Business Suite MAA:

Business Continuity for Oracle E-Business Suite Release 12.2 on Oracle Database 19c Using Logical Host Names (Doc ID 2617788.1)

Oracle E-Business Suite on Exadata Database Machine (White Paper)

Oracle Site Guard

Oracle E-Business Suite Parallel Concurrent Manager:

Configuring and Managing Oracle E-Business Suite Release 12.2.x Forms and Concurrent Processing for Oracle RAC (Doc ID 2029173.1)

How to Activate Parallel Concurrent Processing - Background Facts and Setup Steps (Doc ID 602899.1)

Concurrent Processing - Parallel Concurrent Processing Failover/Failback Expectations (Doc ID 271090.1)

Managing Concurrent Manager Log and Out Directories (Doc ID 1616827.1)

Concurrent Processing - Purge Concurrent Request and/or Manager Data Program (FNDCPPUR) (Doc ID 104282.1)

Concurrent Processing - Best Practices for Performance for Concurrent Managers in E-Business Suite (Doc ID 1057802.1)

Concurrent Processing - Product Information Center (PIC) (Doc ID 1304305.1)

Oracle E-Business Suite Configuration and Management:

Database Initialization Parameters for Oracle E-Business Suite Release 12 (Doc ID 396009.1)

Can The Primary Node Hosting the WLS Admin Server Failover To A 12.2 Slave Node, Migrating the Master WLS Admin Server To Another Machine (Doc ID 1986122.1)

Oracle Applications E-Business Suite 12.2 Fusion Middleware Log Files: Locate, View, and Control (Doc ID 1366187.1)

Managing Configuration of Oracle HTTP Server and Web Application Services in Oracle E-Business Suite Release 12.2 (Doc ID 1905593.1)

HTTP Server Is Either Slow Or Stops Responding When Installed On A NFS Mounted Drive [Doc ID 560853.1]

Using Load-Balancers with Oracle E-Business Suite Release 12.0 and 12.1 (Doc ID 380489.1)

E-Business Suite 12.2 Detailed Steps To Change The R12.2 Default Port To 80 (Doc ID 2072420.1)

How to Change Applications Passwords using Applications Schema Password Change Utility (FNDCPASS or AFPASSWD) (Doc ID 437260.1)

Secure Configuration Guide for Oracle E-Business Suite Release 12 (Doc ID 403537.1)

R12.2 : How To Create, Update or Rebuild The Central Inventory For Oracle Applications E-Business Suite ? (Doc ID 1588609.1)

How to Create a Clean oraInventory in Release 12.2 (Doc ID 1967205.1)

Best Practices for Gathering Statistics with Oracle E-Business Suite (Doc ID 1586374.1)

Fixed Objects Statistics Considerations [Doc ID 798257.1]

Sharing the Application Tier File System in Oracle E-Business Suite Release 12.2 (Doc ID 1375769.1)

Cloning Oracle E-Business Suite:

Cloning Oracle E-Business Suite Release 12.2 RAC Enabled Systems with Rapid Clone (Doc ID 1679270.1)

Cloning Oracle E-Business Suite Release 12.2 with Rapid Clone (Doc ID 1383621.1)

Oracle E-Business Suite Application Tier Patching:

Applying the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2 (Doc ID 1617461.1)

Oracle E-Business Suite Applications DBA and Technology Stack Release Notes for R12.AD.C.Delta.9 and R12.TXK.C.Delta.9 (Doc ID 2233485.1)

12.2 Online Patching Utility ADOP Fails During Cutover Due to Error "[UNEXPECTED] adop has detected a configured disaster recovery site" (Doc ID 2131833.1)

The adop Patch Utility in the E-Business Suite Maintenance Guide

Oracle E-Business Suite Applications DBA and Technology Stack Release Notes for R12.AD.C.Delta.7 and R12.TXK.C.Delta.7 (Doc ID 2033780.1)

OPMN Fails to Start and Says to Check Adopmnctl.txt (Doc ID 2174221.1)

Oracle Engineered Systems (Exadata, SuperCluster):

Exadata Database Machine and Exadata Storage Server Supported Versions (Doc ID 888828.1)

Oracle Exadata Database Machine exachk or HealthCheck (Doc ID 1070954.1)

Oracle Exadata Best Practices (Doc ID 757552.1)

Database Patches Required by Oracle E-Business Suite on Oracle Engineered Systems: Exadata Database Machines and SuperClusters (Doc ID 1392527.1)

Exadata Write-Back Flash Cache - FAQ (Doc ID 1500257.1)

Oracle Exadata Database Machine Performance Best Practices (Doc ID 1274475.1)

Configuring Exadata I/O Resource Manager for Common Scenarios (Doc ID 1363188.1)

Oracle Exadata Database Machine Setup/Configuration Best Practices (Doc ID 1274318.1)

Oracle SuperCluster Supported Software Versions – All Hardware Types (Doc ID 1567979.1)

OS Required Packages and HugePages:

Oracle E-Business Suite Installation and Upgrade Notes Release 12 (12.2) for Linux x86-64 (Doc ID 1330701.1)

HugePages on Oracle Linux 64-bit (Doc ID 361468.1)

HugePages and Oracle Database 11g Automatic Memory Management (AMM) on Linux (Doc ID 749851.1)

USE_LARGE_PAGES To Enable HugePages (Doc ID 1392497.1)

Wednesday, February 14, 2024

Creating an ACFS file system on OCI DB system

 

Creating an ACFS file system on OCI DB system


In an DB system on OCI if we want to add any file system then we can use the ACFS file system.

We can create an ACFS file system using below

1) Login to DB system with grid user

2)  Create a Volume by picking space from DATA disk group.

[grid@foa ~]$ asmcmd lsdg
State    Type    Rebal  Sector  Logical_Sector  Block       AU  Total_MB  Free_MB  Req_mir_free_MB  Usable_file_MB  Offline_disks  Voting_files  Name
MOUNTED  EXTERN  N         512             512   4096  4194304    262144     4372                0            4372              0             Y  DATA/
MOUNTED  EXTERN  N         512             512   4096  4194304    262144   257212                0          257212              0             N  RECO/


asmcmd volcreate -G data -s 20G oradata1

3) Validate the volume created

[grid@foa ~]$ asmcmd volinfo -G data oradata1
Diskgroup Name: DATA

 Volume Name: ORADATA1
 Volume Device: /dev/asm/oradata1-377
 State: ENABLED
 Size (MB): 20480
 Resize Unit (MB): 64
 Redundancy: UNPROT
 Stripe Columns: 8
 Stripe Width (K): 1024
 Usage: 
 Mountpath: 

4) We can check the volume physical details.

[grid@foa ~]$ fdisk -l /dev/asm/oradata1-377

Disk /dev/asm/oradata1-377: 21.5 GB, 21474836480 bytes, 41943040 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 1048576 bytes

5) Format the new volume as ACFS

[grid@foa ~]$ /sbin/mkfs -t acfs /dev/asm/oradata1-377
mkfs.acfs: version                   = 19.0.0.0.0
mkfs.acfs: on-disk version           = 46.0
mkfs.acfs: volume                    = /dev/asm/oradata1-377
mkfs.acfs: volume size               = 21474836480  (  20.00 GB )
mkfs.acfs: Format complete.

6) Register the mount

Exit from grid user and connect as root.

mkdir /backup

 /sbin/acfsutil registry -a /dev/asm/oradata1-377 /backup -u oracle

7)  Verify

df -h

/dev/asm/oradata1-377            20G  414M   20G   3% /backup

https://www.funoracleapps.com/2022/11/creating-acfs-file-system-on-oci-db.html

Tuesday, February 6, 2024

adcfgclone.pl Rapid clone Options E-Business suite 11, R12, R12.2

adcfgclone.pl Different Components There are different components with Rapid Clone that are used when cloning an Oracle Applications instance. These are: dbTechStack (RDBMS ORACLE_HOME) database (database only, including control file creation) dbconfig (database only, with no control file creation) dbTier (both dbTechStack and database) atTechStack (Tools and Web ORACLE_HOMEs) appltop (APPL_TOP only) appsTier (both atTechStack and appltop) Troubleshooting Rapid Clone issues with Oracle Applications R12.0 & R12.1 (Doc ID 603104.1)

Thursday, November 17, 2022

What does f+++++++++ mean in rsync logs?

230

Let's take a look at how rsync works and better understand the cryptic result lines:

1 - A huge advantage of rsync is that after an interruption the next time it continues smoothly.

The next rsync invocation will not transfer the files again, that it had already transferred, if they were not changed in the meantime. But it will start checking all the files again from the beginning to find out, as it is not aware that it had been interrupted.

2 - Each character is a code that can be translated if you read the section for -i, --itemize-changes in man rsync

Decoding your example log file from the question:

>f.st......

> - the item is received
f - it is a regular file
s - the file size is different
t - the time stamp is different

.d..t......

. - the item is not being updated (though it might have attributes 
    that are being modified)
d - it is a directory
t - the time stamp is different

>f+++++++++

> - the item is received
f - a regular file
+++++++++ - this is a newly created item

The relevant part of the rsync man page:

-i, --itemize-changes

Requests a simple itemized list of the changes that are being made to each file, including attribute changes. This is exactly the same as specifying --out-format='%i %n%L'. If you repeat the option, unchanged files will also be output, but only if the receiving rsync is at least version 2.6.7 (you can use -vv with older versions of rsync, but that also turns on the output of other verbose messages).

The "%i" escape has a cryptic output that is 11 letters long. The general format is like the string YXcstpoguax, where Y is replaced by the type of update being done, X is replaced by the file-type, and the other letters represent attributes that may be output if they are being modified.

The update types that replace the Y are as follows:

  • < means that a file is being transferred to the remote host (sent).
  • > means that a file is being transferred to the local host (received).
  • c means that a local change/creation is occurring for the item (such as the creation of a directory or the changing of a symlink, etc.).
  • h means that the item is a hard link to another item (requires --hard-links).
  • . means that the item is not being updated (though it might have attributes that are being modified).
  • * means that the rest of the itemized-output area contains a message (e.g. "deleting").

The file-types that replace the X are: f for a file, a d for a directory, an L for a symlink, a D for a device, and a S for a special file (e.g. named sockets and fifos).

The other letters in the string above are the actual letters that will be output if the associated attribute for the item is being updated or a "." for no change. Three exceptions to this are: (1) a newly created item replaces each letter with a "+", (2) an identical item replaces the dots with spaces, and (3) an unknown attribute replaces each letter with a "?" (this can happen when talking to an older rsync).

The attribute that is associated with each letter is as follows:

  • c means either that a regular file has a different checksum (requires --checksum) or that a symlink, device, or special file has a changed value. Note that if you are sending files to an rsync prior to 3.0.1, this change flag will be present only for checksum-differing regular files.
  • s means the size of a regular file is different and will be updated by the file transfer.
  • t means the modification time is different and is being updated to the sender’s value (requires --times). An alternate value of T means that the modification time will be set to the transfer time, which happens when a file/symlink/device is updated without --times and when a symlink is changed and the receiver can’t set its time. (Note: when using an rsync 3.0.0 client, you might see the s flag combined with t instead of the proper T flag for this time-setting failure.)
  • p means the permissions are different and are being updated to the sender’s value (requires --perms).
  • An o means the owner is different and is being updated to the sender’s value (requires --owner and super-user privileges).
  • g means the group is different and is being updated to the sender’s value (requires --group and the authority to set the group).
  • The u slot is reserved for future use.
  • The a means that the ACL information changed.
  • The x means that the extended attribute information changed.

One other output is possible: when deleting files, the "%i" will output the string "*deleting" for each item that is being removed (assuming that you are talking to a recent enough rsync that it logs deletions instead of outputting them as a verbose message).



https://stackoverflow.com/questions/4493525/what-does-f-mean-in-rsync-logs 

ewallet p12 vs cwallet sso

The  ewallet.p12  stores credentials and certificates protected by a user password, while  cwallet.sso  provides an obfuscated, random passw...