fnd_conc_clone.setup_clean vs cmclean.sql

fnd_conc_clone.setup_clean
====================
fnd_conc_clone  ===> is package
setup_clean ====> it is procedure name
When we run fnd_conc_clone.setup_clean it deletes the information from the below tables.
Delete from fnd_concurrent_queue_size
Delete from fnd_concurrent_queues_tl
Delete from fnd_concurrent_queuesDelete from fnd_nodes;

We use fnd_conc_clone.setup_clean to cleanup fnd_nodes table in the target to clear source node information as part of cloning.

below syntax to execute:
SQL> sho user
USER is "APPS"
SQL> exec fnd_conc_clone.setup_clean;
PL/SQL procedure successfully completed.
SQL> commit;
Commit complete.
First run the autoconfig on DB tier and middle tier this will regiser the nodes in fnd_nodes tables.

cmclean.sql
=========
If we stop conc manager using abort options then concurrent requests will be in running state ,Next when we start concurrent manager the processes will not start properly.
To cleanup running and pending requests we use cmclean.sql this script will update the below tables.
UPDATE fnd_concurrent_processes
UPDATE fnd_concurrent_queues
UPDATE fnd_concurrent_requests
UPDATE fnd_conflicts_domain
UPDATE fnd_concurrent_conflict_sets
Download cmclean.sql: 
=================
Concurrent Processing - cmclean.sql - Non Destructive Script to Clean Concurrent Manager Tables [ID 134007.1]
Note: cmclean.sql and fnd_conc_clone.setup_clean touch different set of concurrent request tables.
Its better idea to run both during the clone. 

NOFILENAMECHECK Parameter Causes ?

When NOFILENAMECHECK is used with the DUPLICATE command, RMAN does not validate the filenames during restoration.

If the primary database and the standby database are on the same host, The DUPLICATE NOFILENAMECHECK option should not be used.

What really happens when you enable maintenance mode before applying patches

Maintenance mode provides a clear separation between normal runtime operation of Oracle Applications and system downtime for maintenance. Enabling the maintenance mode feature shuts down the Workflow Business Events System and sets up function security so that no Oracle Applications functions are available to users. Used only during AutoPatch sessions, maintenance mode ensures optimal performance and reduces downtime when applying a patch. For more information, refer to Preparing your System for Patching in Oracle Applications Maintenance Utilities.

You may also refer to Article ID 291901.1, which has more information about Maintenance Mode.

Workflow Notifications - "Override Email address" Functionality

Background :

      Very often on a Oracle Apps Test or Development environment, you would like all the Workflow Email notifications to be sent to one temporary email address instead of the original users to avoid confusion and to avoid filling the users mail box with Test data. Some companies will setup a temporary mail box and give access to the consultants.

Please  find the steps required to assign a temporary email address. This is much needed when testing Oracle Workflows based applications and especially time out reminder notifications.

These steps have been tried and tested on R12 environment.

Note: Please do not try these steps on Production Environment. Hopefully DBA only will have access to it :)

Steps:

Step 1 : Login to  Workflow Administrator > Oracle Applications Manager > Workflow Manager

Step 2 : Ensure that Notification Mailer is running, and then click on icon as below 

            

 Step 3 : Click on the Notification Mailer > View Details

      Step 4 : Click on "Set Override Address

Step 5 : You can enter an email ID to which you want to send all workflow Notifications and submit. (Note: you can also change it any time.)

You will receive a verification code, just enter it here and click on apply.

 You can verify the same Override Address using the below SQL:

select fscpv.parameter_value test_address

from   fnd_svc_comp_params_tl fscpt

,      fnd_svc_comp_param_vals fscpv

,      fnd_svc_components fsc

where  fscpt.parameter_id = fscpv.parameter_id

and    fscpv.component_id = fsc.component_id

and    fscpt.display_name = 'Test Address'

and    fsc.component_name = 'Workflow Notification Mailer';

TEST_ADDRESS

--------------------------------------------------------------------------------

shrikant.aughad@tieto.com

Workflow Notification Mailer Outbound SMTP Server

We can get the Outbound SMTP Server Name using the below SQL:

select fscpv.parameter_value smtp_server_name

from   fnd_svc_comp_params_tl fscpt

,      fnd_svc_comp_param_vals fscpv

,      fnd_svc_components fsc

where  fscpt.parameter_id = fscpv.parameter_id

and    fscpv.component_id = fsc.component_id

and    fscpt.display_name = 'Outbound Server Name'

and    fsc.component_name = 'Workflow Notification Mailer';

oracle application table spaces

Tablespace Type	Tablespace Name	Contents
Transaction Tables	APPS_TS_TX_DATA	Tables that contain transactional data.
Transaction Indexes	APPS_TS_TX_IDX	Indexes on transaction tables.
Reference	APPS_TS_SEED	Reference and setup data and indexes.
Interface	APPS_TS_INTERFACE	Interface and temporary data and indexes.
Summary	APPS_TS_SUMMARY	Summary management objects, such as materialized views, and other objects that record summary information.
Nologging	APPS_TS_NOLOGGING	Materialized views not used for summary management and temporary objects.
Advanced Queuing/AQ	APPS_TS_QUEUES	Advanced Queuing and dependent tables and indexes.
Media	APPS_TS_MEDIA	Multimedia objects, such as text, video, sound, graphics, and spatial data.
Archive	APPS_TS_ARCHIVE	Archive-purge-related objects.
Undo	UNDO	Automatic Undo Management (AUM) tablespace. UNDO segments are identical to ROLLBACK segments when AUM is enabled.
Temp	TEMP	Temporary tablespace for global temporary table, sorts, and hash joins.
System	SYSTEM	System tablespace used by the Oracle Database.

How to set environment file in Linux for database

[grid@racpub151 u01]$ vi grid.env

export GRID_HOME=/u01/app/12.1.0/grid

export PATH=$PATH:$GRID_HOME/bin

:wq!