Friday, August 22, 2025
fnd concurrent request queues and logs update
Thursday, July 11, 2024
Execute Curl Utility to transfer tar file to Object Storage
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.
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
Data Guard Concepts and Administration
Creating a Physical Standby using RMAN Duplicate (RAC or Non-RAC) (Doc ID 1617946.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
Oracle E-Business Suite on Exadata Database Machine (White Paper)
Oracle E-Business Suite Parallel Concurrent Manager:
How to Activate Parallel Concurrent Processing - Background Facts and Setup Steps (Doc ID 602899.1)
Managing Concurrent Manager Log and Out Directories (Doc ID 1616827.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)
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)
Secure Configuration Guide for Oracle E-Business Suite Release 12 (Doc ID 403537.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:
The adop Patch Utility in the E-Business Suite Maintenance Guide
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)
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:
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)
Wednesday, February 14, 2024
Creating an ACFS file system on OCI DB system
Creating an ACFS file system on OCI DB system
Tuesday, February 6, 2024
adcfgclone.pl Rapid clone Options E-Business suite 11, R12, R12.2
Thursday, November 17, 2022
What does f+++++++++ mean in rsync logs?
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:
- A
<means that a file is being transferred to the remote host (sent).- A
>means that a file is being transferred to the local host (received).- A
cmeans that a local change/creation is occurring for the item (such as the creation of a directory or the changing of a symlink, etc.).- A
hmeans that the item is a hard link to another item (requires --hard-links).- A
.means that the item is not being updated (though it might have attributes that are being modified).- A
*means that the rest of the itemized-output area contains a message (e.g. "deleting").The file-types that replace the X are:
ffor a file, adfor a directory, anLfor a symlink, aDfor a device, and aSfor 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:
- A
cmeans 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.- A
smeans the size of a regular file is different and will be updated by the file transfer.- A
tmeans 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.)- A
pmeans the permissions are different and are being updated to the sender’s value (requires --perms).- An
omeans the owner is different and is being updated to the sender’s value (requires --owner and super-user privileges).- A
gmeans the group is different and is being updated to the sender’s value (requires --group and the authority to set the group).- The
uslot is reserved for future use.- The
ameans that the ACL information changed.- The
xmeans 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...