Response: not enabled: libopmnoc4j

Response: not enabled: libopmnoc4j

In 12.1.X instance while starting services after clone the following error occured.

Due to this error opmn managed services are not started.

ORA-12157: TNS:internal network communication error

ORA-12157: TNS:internal network communication error

This error can happen if the network files not generated properly.

relink them using the below commands to fix the issue.

Cannot allocate memory for the 'shmcb' session cache\n

Have faced the below error in R12 instance,While bouncing opmn, http server is not coming up.
The below error observed from error.log.
[error] mod_ossl: Cannot allocate memory for the 'shmcb' session cache\n
[error] mod_ossl: Cannot allocate memory for the 'shmcb' session cache\n
[warn] pid file /u01/inst/apps/TEST_vin01/pids/10.1.3/Apache/httpd.pid overwritten -- Unclean shutdown of previous Apache run?
[error] mod_ossl: Cannot allocate memory for the 'shmcb' session cache\n

To fix this issue follow the metalink note : 754838.1

cd $ORA_CONFIG_HOME/10.1.3/Apache
Edit ssl.conf
edit the following entry and make sure shmcb to local FS (eg: /var)
Eample entry :
SSLSessionCache shmcb:/var/opt/Apache/logs/ssl_scache(512000)
- Restart the adopmnctl.sh start , http started without issue.
The reason for this issues is in correct NFS options used for SSLSessionCache location.

Multi Node to Single Node Cloning - Oracle Apps 11i

Multi Node to Single Node Cloning – Oracle Apps 11i

With Oracle Applications 11.5.10 the ability to clone from a multi node to a single node system using rapid clone has now been certified.

Source System here refers to the multi node system to be cloned

Target System refers to the newly to be created single node system

Applications Version 11.5.10

The following Steps are required to be performed on the source system

1. Apply application tier patches using adpatch

Apply patch 4038964
Apply patch 4175764

Both the above patches are include in the consolidated update 2 or CU2 so in case you are on 11.5.10.2 or later you can ignore this step.

2. Maintain snapshot information

Log in as the applications user on each application tier node and run 'Maintain Snapshot Information' by using adadmin.

3. Merge existing APPL_TOPs

Log in to the primary node of your application tier as the application user user and run:

$ cd [COMMON_TOP]/admin/scripts/[CONTEXT_NAME]
$ perl adpreclone.pl appsTier merge

This will prompt you with option to merge secondary nodes

Now log in as the applications user to each of the secondary application tier nodes being merged and run:

$ cd [COMMON_TOP]/admin/scripts/[CONTEXT_NAME]
$ perl adpreclone.pl appltop merge

4. Prepare the source system database tier.

Log on to the database tier of the source system as the oracle user and run the following commands:

$ cd [RDBMS ORACLE_HOME]/appsutil/scripts/[CONTEXT_NAME]
$ perl adpreclone.pl dbTier

With this all the pre clone tasks on the source system have been completed.

The next set of tasks is required to be carried out on the target system that is the system on which you wish to place the merged single node instance.

5. Copy the following application tier directories

Copy the following application tier directories from the primary node of your source system to the target application tier node, retaining the original directory structure:

– [APPL_TOP]
– [OA_HTML]
– [OA_JAVA]
– [COMMON_TOP/util]
– [COMMON_TOP/clone>
– [806 ORACLE_HOME]
– [iAS ORACLE_HOME]

6. Copy the required files for merging

Log in as the applications user to each of the secondary source nodes and recursively copy:

directory [COMMON_TOP]/clone/appl
- to -
directory [COMMMON_TOP]/clone/appl on the target system node

Before proceeding with the next steps you must shutdown your oracle applications services and the database on the source system

  7. Copy the database tier file system

Log on to the source system as the database user

Copy the database (DBF) files from the source to the target system
Copy the source database ORACLE_HOME to the target system

After this you can now startup the database and applications services on your source system and release it for use.

8. Configure the target system database server

Log on to the target system as the database user and type the following commands to configure and start the database:

$ cd [RDBMS ORACLE_HOME]/appsutil/clone/bin
$ perl adcfgclone.pl dbTier

This will prompt for new ORACLE_SID,ORACLE_HOME,Port Pool,JAVA_TOP and DATA_TOP give the appropriate values matching your target system

Once successful this should start your database and listener

9. Configure the application tier server nodes

The database and its listener should remain up before executing the next set of commands.
Log in to the merged APPL_TOP node as the applications user and execute the following commands:

$ cd [COMMON_TOP]/clone/bin
$ perl adcfgclone.pl appsTier

This will prompt you new port pool for application tier services as well as new APPLTOP,COMMON_TOP,ORACLE_HOME and IAS_TOP

Successful completion of this task will bring up your application tier services on the target or the cloned node.

10. Post Clone Tasks

Log in to the target system application tier node as the APPLMGR user.

1.      Run the following tasks in adadmin for all products:o generate JAR files
o generate message files
o relink executables
o copy files to destination

2.      Change Apps,system,sysadmin passwords using FNDCPASS

3.      Update the following tables to clean up the source entries:

   - update wf_notification_attributes

- update wf_item_attribute_values

- update wf_systems

- update fnd_concurrent_requests log & our directories

- update fnd_concurrent_queues target_node names

4. update the profile options:  

   -Site Name & any custom profile options

FNDCPASS – Oracle Applications 11i & R12

What is FNDCPASS?

To change the password in Oracle Applications 11i & R12, The FND binary which will help us is doing these things is FNDCPASS. This is present in $FND_TOP/bin directory.

FNDCPASS is a utility change password in Oracle Applications 11i and R12.

Using FNDCPASS

Below is the usage for FNDCPASS

You can just type FNDCPASS and press enter , it will give you these details.

Gather Schema Statistics Using FND_STATS.

Gather Schema Statistics Using FND_STATS.

1. Gathers specified schema level statistics

2. Backs up existing statistics

3. Creates the histogram for the specified columns in the FND_HISTOGRAM_COLS tables
4. Populates default statistics for all the interface tables as defined in the FND_EXCLUDE_TABLE_STATS table.