txkcreateACL.sh INSTE8_APPLY 1

 WARNING: [AutoConfig Error Report]

The following report lists errors AutoConfig encountered during each
phase of its execution.  Errors are grouped by directory and phase.
The report format is:
      <filename>  <phase>  <return code where appropriate>  [APPLY PHASE]
  AutoConfig could not successfully execute the following scripts:
    Directory: /u02/app/oracle/product/12.1.0.0/EBSGOLDN/appsutil/install/EBSTEST_exanprd01-xti6e1
      txkcreateACL.sh         INSTE8_APPLY       1AutoConfig is exiting with status 1AutoConfig execution completed on Thu Mar 30 07:16:46 2023Time taken for AutoConfig execution to complete : 0 mins  24 secs-------You are running txkcreateACL.sh version 120.1.12020000.2is_pdb=falseThe environment settings are as follows ...       ORACLE_HOME : /u02/app/oracle/product/12.1.0.0/EBSGOLDN
        ORACLE_SID : EBSTEST
              PATH : /u02/app/oracle/product/12.1.0.0/EBSGOLDN/perl/bin:/u02/app/oracle/product/12.1.0.0/EBSGOLDN/bin:/u02/app/oracle/product/12.1.0.0/EBSGOLDN/OPatch:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:.
Executable : /u02/app/oracle/product/12.1.0.0/EBSGOLDN/bin/sqlplusExecuting txkcreateACL.sql ...SQL*Plus: Release 12.1.0.2.0 Production on Thu Mar 30 07:16:45 2023Copyright (c) 1982, 2014, Oracle.  All rights reserved.Connected to an idle instance.
DECLARE
*
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 0
Session ID: 0 Serial number: 0ERROR:
ORA-01012: not logged on
Process ID: 0
Session ID: 0 Serial number: 0DisconnectedtxkcreateACL.sh: exiting with status 1FIX:Replace txkcreateACL.sh and txkcreateACL.sql from patch to $OH/appsutil/$CONTEXT_NAME
Patch 31246939: REMOVE INVOCATION OF THE ACL SCRIPTS VIA AUTOCONFIG (EBS 12.1)
Patch 31246939: REMOVE INVOCATION OF THE ACL SCRIPTS VIA AUTOCONFIG (EBS 12.2)

CPE Configuration | OCI | Networking

CPE Configuration

This topic is for network engineers. It explains how to configure the on-premises device (the customer-premises equipment, or CPE) at your end of Site-to-Site VPN so traffic can flow between your on-premises network and virtual cloud network (VCN). See these related topics:

• Networking: For general information about the parts of a VCN
• Site-to-Site VPN: For various topics about IPSec VPNs
• Verified CPE Devices: For a list of CPE devices Oracle has verified

The following figure shows the basic layout of Site-to-Site VPN's IPSec connection.

Requirements and Prerequisites

There are several requirements and prerequisites to be aware of before moving forward.

Routing Considerations

For important details about routing for your Site-to-Site VPN see Routing for Site-to-Site VPN.

Oracle uses asymmetric routing across the multiple tunnels that make up the IPSec connection. Even if you configure one tunnel as primary and another as backup, traffic from your VCN to your on-premises network can use any tunnel that is "up" on your device. Configure your firewalls accordingly. Otherwise, ping tests or application traffic across the connection will not reliably work.

If you use BGP dynamic routing with your Site-to-Site VPN, you can configure routing so that Oracle prefers one tunnel over the other.

Note that the Cisco ASA policy-based configuration uses a single tunnel.

Creation of Cloud Network Components

You or someone in your organization must have already used the Oracle Console to create a VCN and an IPSec connection, which consists of multiple IPSec tunnels for redundancy. You must gather the following information about those components:

• VCN OCID: The VCN OCID is a unique Oracle Cloud Infrastructure identifier that has a UUID at the end. You can use this UUID or any other string that helps you identify this VCN in the device configuration and doesn't conflict with other object-group or access-list names.
• VCN CIDR
• VCN CIDR subnet mask

• For each IPSec tunnel:

  • The IP address of the Oracle IPSec tunnel endpoint (the VPN headend)
  • The shared secret

Information About Your CPE Device

You also need some basic information about the inside and outside interfaces of your on-premises device (your CPE). For a list of the required information for your particular CPE, see the links in this list: Verified CPE Devices.

By default, NAT-T is enabled on all Site-to-Site VPN IPSec tunnels. Oracle recommends leaving NAT-T enabled when configuring Site-to-Site VPN to OCI.

If your CPE is behind a NAT device, you can provide Oracle with your CPE's IKE identifier. For more information, see Overview of Site-to-Site VPN Components.

Route-Based Versus Policy-Based IPSec

The Oracle VPN headends use route-based tunnels, but can work with policy-based tunnels with some caveats. See Encryption domains for policy-based tunnels for full details.

Site-to-Site VPN Best Practices

• Configure all tunnels for every IPSec connection: Oracle deploys multiple IPSec headends for all your connections to provide high availability for your mission-critical workloads. Configuring all the available tunnels is a key part of the "Design for Failure" philosophy. (Exception: Cisco ASA policy-based configuration, which uses a single tunnel.)
• Have redundant CPEs in your on-premises locations: Each of your sites that connects with IPSec to Oracle Cloud Infrastructure should have redundant CPE devices. You add each CPE to the Oracle Cloud Infrastructure Console and create a separate IPSec connection between your dynamic routing gateway (DRG)  and each CPE. For each IPSec connection, Oracle provisions two tunnels on geographically redundant IPSec headends. Oracle may use any tunnel that is "up" to send traffic back to your on-premises network. For more information, see Routing for Site-to-Site VPN.

• Consider backup aggregate routes: If you have multiple sites connected via IPSec VPNs to Oracle Cloud Infrastructure, and those sites are connected to your on-premises backbone routers, consider configuring your IPSec connection routes with both the local site aggregate route as well as a default route.

  Note that the DRG routes learned from the IPSec connections are only used by traffic you route from your VCN to your DRG. The default route will only be used by traffic sent to your DRG whose destination IP address does not match the more specific routes of any of your tunnels.

Confirming the Status of the Connection

After you configure the IPSec connection, you can test the connection by launching an instance into the VCN and then pinging it from your on-premises network. For information about launching an instance, see Launching an Instance. To ping the instance, the VCN's security rules must allow ping traffic.

You can get the status of the IPSec tunnels in the API or Console. For instructions, see To view the status and configuration information for the IPSec tunnels.

Device Configurations

For links to the specific configuration information for each verified CPE 

https://docs.oracle.com/en-us/iaas/Content/Network/Tasks/configuringCPE.htm

How to increase java heap size in EBS R12.2

Why we need to increase the Java heap size: Mainly we need to increase the EBS Performance. Default oacore JVM heap size is 512 MB it's supports 50 to 100 users When our R12.2 instance reach more than 200 users we need to be increase the oacore size for better performance. Oracle recommended to configure 2 GB JVM Heap Space for oacore. This can roughly support 150 to 200 users depending on usage. For higher user load additional oacore managed servers need to be created. Oracle recommend to have 1 managed server per 2 CPU. Following steps how increase the oacore size. Step1: Login weblogic console Step 2: Click à lock and edit Step3: Choice the Domain tab and click à serves menu Step4: Click àoacore_server1 Step 5: Click à server start Step 6: Go to Argument tab Then change the xms and xmx values default value is 512m Default values -XX:PermSize=128m -XX:MaxPermSize=384m -Xms512m -Xmx512m - I changed the values in -XX:PermSize=128m -XX:MaxPermSize=384m -Xms1024m -Xmx2048m – What is mean by XX,Xms and Xmx? XX is MaxPermSize Xms is the minimum heap size Xmx is the maximum heap size Step 7: Click save and release the configuration tab.

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:

• 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 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.).
• A h means 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: 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:

• A 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.
• A s means the size of a regular file is different and will be updated by the file transfer.
• A 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.)
• A 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).
• A 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 

Oracle E-Business Suite with Oracle Autonomous Database on Dedicated Exadata Infrastructure

Oracle E-Business Suite with Oracle Autonomous Database on Dedicated Exadata Infrastructure Oracle Autonomous Database on Dedicated Exadata Infrastructure is certified for use with Oracle E-Business Suite (EBS) Release 12.2. Customers who use Oracle Autonomous Database can expect to benefit from increased system availability as well as automation of tasks such as provisioning, patching, and tuning. This initial limited availability certification includes procedures for several key tasks, starting with migration of an existing EBS environment to Oracle Cloud Infrastructure (OCI) and Oracle Autonomous Database. Further procedures are provided for subsequent backup and restore, cloning, and patching of the migrated EBS environment. If you would like to learn more about the limited availability program for Oracle E-Business Suite with Oracle Autonomous Database, contact the EBS on Autonomous Database Program Office at ebs-adb-info_ww@oracle.com.

How to Change Profile Option Value Without Forms? (Doc ID 943710.1)

 

APPLIES TO:

Oracle Application Object Library - Version 11.5.10.0 to 12.2.10 [Release 11.5 to 12.2]
Information in this document applies to any platform.

GOAL

How to update a Profile Option using SQL (if Forms login is not possible)?

SOLUTION

Please use the API:  FND_PROFILE
The package FND_PROFILE  can be found in file AFPFPROS.pls

 

Note: FND_PROFILE is not public interface.  Use of this API is considered a customization and should be tested in a test environment.

FND_PROFILE.SAVE - sets the value of a profile option permanently to the database,
at any level. This routine can be used at runtime or during patching.
This routine will not actually commit the changes; the caller must commit.
The levels are: 'SITE', 'APPL', 'RESP', or 'USER'.

Examples of use:

FND_PROFILE.SAVE('P_NAME', 'P_VAL', 'SITE');
FND_PROFILE.SAVE('P_NAME', 'P_VAL', 'APPL', 321532);
FND_PROFILE.SAVE('P_NAME', 'P_VAL', 'RESP', 321532, 345234);
FND_PROFILE.SAVE('P_NAME', 'P_VAL', 'USER', 123321);

returns: TRUE if successful, FALSE if failure.


To update a Profile Option value at Site level, you need to run the SQL Script below:

Declare
value Boolean;
Begin
value := fnd_profile.save('APPS_DATABASE_ID','<new_value>','SITE');
End;

Example:

===========
Sample Code
===========
DECLARE
stat boolean;
BEGIN
dbms_output.disable;
dbms_output.enable(100000);
stat := FND_PROFILE.SAVE('GUEST_USER_PWD', 'GUEST/ORACLE', 'SITE');
IF stat THEN
    dbms_output.put_line( 'Stat = TRUE - profile updated' );
ELSE
    dbms_output.put_line( 'Stat = FALSE - profile NOT updated' );
END IF;
commit;
END;
===============
End of Sample Code
===============

Description of the FND_PROFILE.SAVE function parameters:

Function SAVE(
X_NAME in varchar2,             /* Profile name you are setting */
X_VALUE in varchar2,            /* Profile value you are setting */
X_LEVEL_NAME in varchar2,       /* Level that you're setting at:
                                   'SITE','APPL','RESP','USER', etc. */
X_LEVEL_VALUE in varchar2 default NULL,
                                /* Level value that you are setting at,
                                   e.g. user id for 'USER' level.
                                   X_LEVEL_VALUE is not used at site level. */
X_LEVEL_VALUE_APP_ID in varchar2 default NULL,
                                /* Used for 'RESP' and 'SERVRESP' level;
                                   Resp Application_Id. */
X_LEVEL_VALUE2 in varchar2 default NULL
                                /* 2nd Level value that you are setting at.
                                   This is for the 'SERVRESP' hierarchy. */
) return boolean;

 

 

Reference: https://docs.oracle.com/cd/E26401_01/doc.122/e20927.pdf

FND_CONCURRENT_QUEUE Control Code Meaning

 In the FND_CONCURRENT_QUEUE table we have a column named control_code.

To get the details of the code present in the column we can use below script.

SQL> select lookup_code,meaning from apps.fnd_lookups where lookup_type = 'CP_CONTROL_CODE' order by lookup_code;

LOOKUP_CODE    MEANING
----------                    ------------------------------
A                               Activating
B                               Activated
D                               Deactivating
E                               Deactivated
H                               System Hold, Fix Manager before resetting counters
N                               Target node/queue unavailable
O                               Suspending concurrent manager
P                                Suspended
Q                               Resuming concurrent manager
R                               Restarting
T                               Terminating
U                               Updating environment information
V                               Verifying
X                               Terminated