RMAN-05531: a mounted database cannot be duplicated while datafiles are fuzzy

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 12/30/2012 10:52:56
RMAN-05531: a mounted database cannot be duplicated while datafiles are fuzzy

Bug 11715084 - Active duplicate should work when connected to Standby as source DB [ID 11715084.8]

RMAN active duplicate does not currently allow a standby in MRP to be cloned. Backup-based duplicate was altered in 11.1 so that a standby could be used as the source DB, but active duplicate does not work.

This is going to be fixed in RDBMS 12.1(future release) or 11.2.0.4(future patchset).(As on 30-Dec-2012)

The workaround is to Open the DataGuard in Read/Write Mode and Start the Active Duplicate. As it is 11.2.0.3, I opened the DataGuard in Read Only and Stopped the MRP. In 11gR2, you can have the Standby in Read Only, while the MRP Continues.

FORMS Customization - changes required in adovars.env and formservlet.ini

Customization Entry in $APPL_TOP/admin/adovars.env

# Begin customizations
export APPLLCSP=ON
export XXCSTAP_TOP="/pa01/oracle/mkkdevappl/xxcstap/11.5.0"
export XXCSTAR_TOP="/pa01/oracle/mkkdevappl/xxcstar/11.5.0"
export XXCSTGL_TOP="/pa01/oracle/mkkdevappl/xxcstgl/11.5.0"
export XXCSTPO_TOP="/pa01/oracle/mkkdevappl/xxcstpo/11.5.0"
# End customizations

Customization Entry in $IAS_ORACLE_HOME/Apache/Jserv/etc/formservlet.ini

# Begin customizations
XXCSTAP_TOP=/pa01/oracle/mkkdevappl/xxcstap/11.5.0
XXCSTAR_TOP=/pa01/oracle/mkkdevappl/xxcstar/11.5.0
XXCSTGL_TOP=/pa01/oracle/mkkdevappl/xxcstgl/11.5.0
XXCSTPO_TOP=/pa01/oracle/mkkdevappl/xxcstpo/11.5.0
# End customizations

In R12 Custom forms will not open after upgrade, because file formservlet.ini used in 11i has been replaced by default.env in R12. Put entry for the custom top in $ORA_CONFIG_HOME/10.1.2/forms/server/default.env file.
Note: If you have the custom top entries in $ORA_TOP/iAS/Apache/Jserv/etc/formservlet.ini in correct format, then autoconfig will preserve the customization.

SQL_Query - Find the Schedule Concurrent Requests and Request Sets

SELECT fcr.request_id,
DECODE(fcpt.user_concurrent_program_name,
'Report Set',
'Report Set:' || fcr.description,
fcpt.user_concurrent_program_name) CONC_PROG_NAME,
argument_text PARAMETERS,
NVL2(fcr.resubmit_interval,
'PERIODICALLY',
NVL2(fcr.release_class_id, 'ON SPECIFIC DAYS', 'ONCE')) PROG_SCHEDULE_TYPE,
DECODE(NVL2(fcr.resubmit_interval,
'PERIODICALLY',
NVL2(fcr.release_class_id, 'ON SPECIFIC DAYS', 'ONCE')),
'PERIODICALLY',
'EVERY ' || fcr.resubmit_interval || ' ' ||
fcr.resubmit_interval_unit_code || ' FROM ' ||
fcr.resubmit_interval_type_code || ' OF PREV RUN',
'ONCE',
'AT :' ||
TO_CHAR(fcr.requested_start_date, 'DD-MON-RR HH24:MI'),
'EVERY: ' || fcrc.class_info) PROG_SCHEDULE,
fu.user_name USER_NAME,
requested_start_date START_DATE
FROM apps.fnd_concurrent_programs_tl fcpt,
apps.fnd_concurrent_requests fcr,
apps.fnd_user fu,
apps.fnd_conc_release_classes fcrc
WHERE fcpt.application_id = fcr.program_application_id
AND fcpt.concurrent_program_id = fcr.concurrent_program_id
AND fcr.requested_by = fu.user_id
AND fcr.phase_code = 'P'
AND fcr.requested_start_date > SYSDATE
AND fcpt.LANGUAGE = 'US'
AND fcrc.release_class_id(+) = fcr.release_class_id
AND fcrc.application_id(+) = fcr.release_class_app_id
and DECODE(fcpt.user_concurrent_program_name,
'Report Set',
'Report Set:' || fcr.description,
fcpt.user_concurrent_program_name) like '%'
ORDER BY CONC_PROG_NAME;

Workflow Related Scheduled Concurrent Program for DBAs

Purge Obsolete Workflow Runtime Data

Oracle Workflow accesses several tables that can grow quite large with obsolete workflow information that is stored for all completed workflow processes. The size of these tables and indexes can adversely affect performance. You should purge these tables on a regular basis using FNDWFPR.
This program calls database package WF_Purge.Total.  This program deletes old Workflow runtime data for completed Workflows. It is recommended that this program or package is run regularly as required.

From Workflow Administrator's Guide PDF Document:
The Oracle Applications Manager console helps you easily maintain the Oracle Workflow and Oracle XML Gateway database tables. Oracle Workflow and Oracle XML Gateway access several tables that can grow quite large with obsolete workflow information that is stored for all completed workflow processes, as well as obsolete information for XML transactions. The size of these tables and indexes can adversely affect performance. These tables should be purged on a regular basis, using the Purge Obsolete Workflow Runtime Data concurrent program.

Parameter Explanation:
Item Type: The item type to purge. Leaving this field blank defaults to purging the runtime data for all item types.
Item Key: The item key to purge. Leaving is field blank defaults to purging the runtime data for all item keys.
Age: Minimum age of data to purge, in days.
Persistence Type: The persistence type to be purged, either for Temporary or for Permanent. The default is temp.
Core Workflow Only: Enter 'Y' to purge only obsolete runtime data associated with work items, or 'N' to purge all obsolete runtime data as well obsolete design data. The default is 'N'.
Commit Frequency: Enter the number of records to purge before the program commits data. To reduce rollback size and improve performance, set this parameter to commit data after a smaller number of records. The default is 500 records.
Signed Notifications: Enter 'N' to preserve signature evidence, including notifications that required electronic signatures and their associated signature information. Enter 'Y' to purge signature-related information. The default is 'N'.
Note: After performing a commit, the program resumes purging work items with the next subsequent begin date. In some cases, if additional items have the same begin date as the last item that was purged before a commit, the program may not purge all eligible items. To purge these remaining work items, simply rerun the program.

Workflow Control Queue Cleanup

Parameters: NONE
Schedule:
Frequency:    Run every 12 Hours
Responsibility:  System Administrator
Please tick the checkbox “From the start of the prior run”

Workflow Background Process

This program needs to be submitted in various permutation and combination.

Type-1: which Runs Every 3 Mins for Parameters:
Process Deferred: Yes
Process Timeout:  No
Process Stuck:  No

Type-2: which Runs Every 30 Mins for Parameters:
Process Deferred:  No
Process Timeout:  Yes
Process Stuck:  No

Type-3: which Runs Every 1 Hours for Parameters:
Process Deferred:  No
"Process Timeout:  No
Process Stuck:  Yes"

Type-4: which Runs Every 2 Hours for Parameters:
Process Deferred:  Yes
"Process Timeout:  Yes
Process Stuck:  Yes"

How to Submit a Workflow Background Process Engine [ID 182936.1], Follow the Note mentioned at the End of this Metalink Note

Workflow Mailer Statistics Concurrent Program

Parameters: NONE
Schedule:
Frequency:    Run every 1 Day
Responsibility:  System Administrator
Please tick the checkbox “Increment Date Parameters Each Run”
Please tick the checkbox “From the Completion of the Prior Run”

Workflow Work Items Statistics Concurrent Program

Parameters: NONE
Schedule:
Frequency:    Run every 1 Day
Responsibility:  System Administrator
Please tick the checkbox “Increment Date Parameters Each Run”
Please tick the checkbox “From the Completion of the Prior Run”

Workflow Agent Activity Statistics Concurrent Program

Parameters: NONE
Schedule:
Frequency:    Run every 1 Day
Responsibility:  System Administrator
Please tick the checkbox “Increment Date Parameters Each Run”
Please tick the checkbox “From the Completion of the Prior Run”

Gather Schema Statistics Schedule:

Make sure Gather Shema Stats is running on periodical basis, for XXXXX we have scheduled to run every 15 Days.
Following points needs to be noted for the Gather Schema Statistics:
●● Do not gather statistics excessively on entire schemas or the entire database such as nightly or weekly.
●● Do not gather statistics on permanent objects during peak intervals.
●● Gathering statistics invalidates cursors .Unless you use the ‘No Invalidate’ option.
●● Gathering statistics requires dictionary and object level locks.
●● The option 'GATHER_AUTO' can be used, to gather statistics only on objects that have changes above the specified 'Modification Threshold' (percentage of DML compared to the number of rows of the table).
●● Plans are not likely to change if the data distribution has not changed.
●● Use only FND_STATS or the Gather Schema and Gather Table Statistics Concurrent Programs.
●● Do NOT USE the analyze or dbms_stats command directly. It is not supported, and results in sub-optimal plans.

Following CONCSUB Command can be used to schedule the Gather Schema Statistics concurrent Program:
"CONCSUB apps/${xx_appspassword} SYSADMIN 'System Administrator' SYSADMIN CONCURRENT FND FNDGSCST START='""01-MAR-2012 02:00:00""'
REPEAT_DAYS=10 'ALL','10','18','NOBACKUP','','LASTRUN','GATHER','','Y'"

To Submit the Program Manually from SQLPlus following commands can be used:
For One Schema:
SQL> exec fnd_stats.gather_schema_statistics('MRP');
For All Schema:
SQL> exec fnd_stats.gather_schema_statistics('ALL');
For One Table:
SQL> exec fnd_stats.gather_table_stats('MRP','MRP_FORECAST_DATES');

To Submit the Gather Schema Statistics from EBS Front End:
●● Make sure you are logged in as SYSADMIN User
●● Use the System Administrator Responsibility to Submit the Concurrent Program.

DROP function was hanging for ever, even if you try to recompile the objects it throws ORA-04021

ORA-04021 timeout occurred while waiting to lock object... Same is applicable if the package status is getting invalidated.

drop function AGCST.AG_ASG_CHG_MAIL_PROG;

The background behind it was, this function is used in workflow and the initiated workflow was still accesing the objects.

Get the SID Information which are accessing this object and kill the same:
select * from v$access where owner='AGCST';

select 'ALTER SYSTEM KILL SESSION '''||SID||','||SERIAL#||''';' from gv$session where INST_ID=2 and SID IN(select SID from gv$access
where object like '%AR%CASH%REC%' and type='TABLE'
and INST_ID=1);

Once you complete killing all the SIDs, it will allow you to drop the object.

Removing OAF personalization document in the database using JDR_UTILS package

This method only requires access to the database and must be used with great care to ensure the correct document is deleted. For this method you need to know the document name of the OAF page with the personalization

Run the following commands to show the available personalization documents:

set serverout on;
exec jdr_utils.listcustomizations('/oracle/apps/<product>/<subcategories>/<pagename>');
exec jdr_utils.listcustomizations('/oracle/apps/fnd/framework/navigate/webui/HomePG');
exec jdr_utils.listcustomizations('/oracle/apps/eam/workorder/webui/CreateUpdateWOPG');

This will print the details:
exec jdr_utils.printdocument('/oracle/apps/eam/workorder/lov/server/customizations/site/0/MaterialsVO');
This returns the documentnames of the personalization document for this OAF page.

For example for SITE level on Homepage
/oracle/apps/fnd/framework/navigate/webui/customizations/site/0/HomePG
SQL> exec jdr_utils.listcustomizations('/oracle/apps/eam/workorder/webui/CreateUpdateWOPG');
/oracle/apps/eam/workorder/webui/customizations/site/0/CreateUpdateWOPG
PL/SQL procedure successfully completed.

Backup the personalization document by exporting it to a file

adjava -mx128m -nojit oracle.jrad.tools.xml.exporter.XMLExporter /oracle/apps/<product>/<subcategories>/customizations/<personalizationlevel>/<personalizationid>/ /<pagename> \
-username apps -password <appspwd> -dbconnection "(description=(address_list=(ADDRESS=(PROTOCOL=TCP)(HOST=<myHost>)(PORT=<port>)))(CONNECT_DATA=(SID=<SID>)))" \
-rootdir /tmp
This create an XML document in the /tmp directory, like
/tmp/oracle/apps/<product>/<subcategories>/<personalizationlevel>/<personalizationid>/<pagename>.xml

Delete the personalization document

SQL> exec jdr_utils.deletedocument('/oracle/apps/<product>/<subcategories>/customizations/<personalizationlevel>/<personalizationid>/<pagename>');
For the home page example this is:
SQL> exec jdr_utils.deletedocument('/oracle/apps/fnd/framework/navigate/webui/customizations/site/0/HomePG');
Restart Apache to ensure that Java caching is cleared
To restore the personalization document deleted, use the command (optional)
-adjava -mx128m -nojit oracle.jrad.tools.xml.importer.XMLImporter \
/tmp/oracle/apps/<product>/<subcategories>/<personalizationlevel>/<personalizationid>/<pagename>.xml \
-username apps -password apps -dbconnection "(description=(address_list=(ADDRESS=(PROTOCOL=TCP)(HOST=<myHost>)(PORT=<port>)))(CONNECT_DATA=(SID=<SID>)))" -rootdir /tmp

OAF Personalizations Issue - Temporary disable all Personalizations

In case it's not possible to determine the exact document name of the OAF page failing the following method can be used. The caveat of this method however is that during the change of profile option mentioned this makes *all* personalizations will be disabled so will also affect other pages. So only to be used on TEST environment or during maintenance window for PROD environment.

Update the Profile Option: "Disable Self-Service Personal" = YES
This can be set at SITE and APPLICATION level

Navigate to the OAF page personalized(may be done using another user). It should now open since personalizations are not taken into account. Depending on the situation you have following options:

Cause of the failure is known (e.g. last change made)
Revert the personalization step causing the problem
Apply the changes

Cause of the failure is unknown
Click pencil "Manage Personalizations"
Now Deactivate or Delete the personalization document

The difference between Deactivate and Delete is that in the case of Deactivating the personalization document in the MDS repository is not removed, while this is the case for Delete. Especially when there are multiple personalization documents, but it's not clear which causes the problem the 'Deactivate' allows these to be tested individually without the need to reload or recreate the personalization documents. 

After fixing the problem:  "Disable Self-Service Personal" = NO (for the level it was set to YES)

OAF Page Migration - adjava XMLImporter

1. SCP the Directory Structure from Source(DEV) to Target(CRP2).

As an example we are migrating cwsa OAF Pages, then SCP the ${JAVA_TOP}/xxcto/oracle/apps/eam/cwsa directory from DEV to CRP2.
Use the following command using CRP2 applmgr user:
$ scp -r appldev@mkkapplserver1:${xx_srcjavatopxx}/xxcto/oracle/apps/eam/cwsa/* ${JAVA_TOP}/xxcto/oracle/apps/eam/cwsa/

2. Execute XMLImporter Command

cd ${JAVA_TOP}/xxcto/oracle/apps/eam/cwsa/
find . -name "*.xml" -print | grep webui | wc -l

This would give you the name of all the XMLs required to be imported, likes LOVs..... DO NOT miss any LOVs......

Go to the Directory where .xml file is copied inside the webui directory.
adjava oracle.jrad.tools.xml.importer.XMLImporter XXCTOCreatePropVehiclePG.xml -username apps -password ${xx_appspassword} -rootdir ${JAVA_TOP} -dbconnection "(DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (COMMUNITY = tcp.world)(PROTOCOL = TCP) (Host = mkkapplserver1.mkkdomain.local)(Port = 1525)))(CONNECT_DATA = (SID = CRP2)))"
Make sure ADJAVA Import completed Successfully. This would load the OAF Pages to the MDS Repository.

3. Restart OACORE Services

. ${HOME}/db_apps_env.sh
. ${xx_scripts_top}/db_apps_env.sh
${ADMIN_SCRIPTS_HOME}/adoacorectl.sh stop
${ADMIN_SCRIPTS_HOME}/adoacorectl.sh start

WFLOAD - Workflow Migration

WFLOAD Download Command

$ WFLOAD apps/${xx_appspassword} 0 Y DOWNLOAD AGWOCOMP.wft <Type Internal Name>
$ WFLOAD apps/***** 0 Y DOWNLOAD $AGCST_TOP/workflow/AGWOCOMP.wft AGWOCOMP

WFLOAD Upload Command

$ WFLOAD apps/${xx_appspassword} 0 Y UPGRADE $ROI_TOP/admin/NAME_ACC.wft

WFLOAD <apps/pwd> 0 Y {UPLOAD | DOWNLOAD | UPGRADE | FORCE} [@<appl-shortname>:]<filepath> [<item type>]

******************************************************

WFLOAD Upload Issue due to NLS_LANG Characterset:

  wferr:
  - 1300: Could not load.
  - 1223: Parse error in line 1141ׂÍA“Á’è‚̃wƒbƒ_[‚É‘®‚µ'.
  - 1203: Warning: line 1141: unescaped quote.
  - 1217: No equal siׂÍA“Á’è‚̃wƒbƒ_[‚É‘®‚µ' truncated to within 30 bytes.
Reason: The NLS_LANG environment variable was not appropriately set for the environment.
Solution: Once NLS_LANG was set to japanese_Japan.JA16SJIS, the .wft file loaded without error. for the file wrongly Arabic Language was set

*********************************************************

WFLOAD Issue ORA-01480 trailing null missing from STR bind value

$ WFLOAD apps/${xx_appspassword} 0 Y DOWNLOAD SERVEREQ.wft SERVEREQ
>>> Item type SERVEREQ
wferr:
  - 1114: Could not load from database.
  - 1115: Could not load all definitions referenced by 'SERVEREQ' item type.
  - 1115: Could not load contents of 'SERVEREQ' item type.
  - 1101: Could not load item types from database. FILTER=SERVEREQ
  - 210: Oracle Error: ORA-01480: trailing null missing from STR bind value.  SQL text: SELECT protect_level, custom_level, name, display_name, description, wf_selector, read_role, write_role, execute_role,        persistence_type, to_char(persistence_days) FROM   wf_item_types_vl WHERE  name like :itemtype ORDER BY name

There are possible three solutions for this issue, verify and implement, whichever is applicable to you:


Check#1: Workflow Internal Name is More than 7 Character Long?

Is it happening for longer than 7 Characters Long or All(Workflow Internal Name), try to down POAPPRV(PO Approval Workflow and Verify the same.
If Check#1 fails, check the Patch#11838073. This is applicable for 12.1.1, 12.1.2 and 12.1.3.
For release 12.0.x oneoff   12361895 - 1OFF:9440402:12.0.4:12.0.4:ORA-01480 WHEN TRYING TO DOWNLOAD 8-CHARACTER LONG
Apply Patch 12361895:R12.OWF.A and it's pre-reqs in a test environment.

Check#2: Protection Level of Workflow Definition are Different?

Is it happening for some workflows and some are going successful, Protection Level of Workflow Definition are Different?
If this is the case then the probable reason is mismatch in the protection level of the workflow definition

Successful:
WFLOAD apps/${xx_appspassword} 0 Y DOWNLOAD POAPPRV.wft POAPPRV
Failure:
WFLOAD apps/${xx_appspassword} 0 Y DOWNLOAD PAWFPPWP.wft PAWFPPWP

Verify the Protection Level of Workflow Definition using following command:
SELECT protect_level, custom_level, name, display_name, description, wf_selector, read_role, write_role, execute_role, persistence_type, to_char(persistence_days) FROM wf_item_types_vl WHERE name like 'PAWFPPWP' ORDER BY name;

Relinking the WFLOAD Executable would resolve the issue:
$ cd $AD_TOP/bin
$ adrelink force=y "fnd WFLOAD"

Check#3: Is it happening for OKSKPRCS ITEM_TYPE Only?

Check if the file versions are lesser than these:
wfdes.lc 120.3.12000000.2
wfldr.lc 120.3.12000000.2
If yes, Apply Patch 12361895:R12.OWF.A and it's pre-reqs in a test environment.

Database Listener Issue | TNS-12555: TNS permission denied

[oracrp2@mkkdbserver1 ~]$ lsnrctl start LISTENER
LSNRCTL for Linux: Version 10.1.0.5.0 - Production on 13-MAR-2011 23:45:33
Copyright (c) 1991, 2004, Oracle.  All rights reserved.
Starting /hypprod/oracrp2/OraHome_1/bin/tnslsnr: please wait...
TNSLSNR for Linux: Version 10.1.0.5.0 - Production
System parameter file is /hypprod/oracrp2/OraHome_1/network/admin/listener.ora
Log messages written to /hypprod/oracrp2/OraHome_1/network/log/listener.log
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=mkkdbserver1.mkkdomain.local)(PORT=1521)))
Error listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1521)))
TNS-12555: TNS:permission denied
 TNS-12560: TNS:protocol adapter error
  TNS-00525: Insufficient privilege for operation
   Linux Error: 1: Operation not permitted


Solution: 1
****************

[root@mkkdbserver1 ~]# rm -rf /var/tmp/.oracle
Please be aware that this step should ONLY be taken as a last resort and ONLY when there are no  Net connections to the database(s).  This procedure could cause active sessions to be terminated.  It is NOT recommended to take this action in a RAC environment.  see Note 391790.1 for details.
Clear the /var/tmp/.oracle directory and start from fresh:
1. Stop all listeners
2. Remove the /var/tmp/.oracle directory, e.g. run the following from the root account:
rm -rf /var/tmp/.oracle
3. Check the listener(s) configuration contains unique keys specified for each IPC endpoint and each listener
4. Start the listener(s) from the normal Oracle OS user.
Clearing the /var/tmp/.oracle directory will force the listeners to recreate the socket files from fresh, each with its own correct ownership.
You need to make sure that you always start the listener(s) from the same OS user(s) and that you do not reuse IPC key endpoints between listeners running under different users, otherwise the problem will resurface.

Solution: 2
**************

1. Ensure that /tmp/.oracle or /var/tmp/.oracle directory exists.
2. Confirm that the user who is trying to start the listener has adequate read and write permissions on the directory specified above. The permissions should be 777.
3. If the /tmp directory has reached full capacity, this would cause the listener to fail to write the socket files.
To implement the solution, please use the following example:
1. cd /var/tmp
2. Check the whether the .oracle directory exists:
cd .oracle
3. If the directory does not exist, request the System Administrator create the directory and set the ownership as root:root with the permissions set to 01777
mkdir /var/tmp/.oracle
chmod 01777 /var/tmp/.oracle
chown root /var/tmp/.oracle
chgrp root /var/tmp/.oracle
4. Next try starting the TNS Listener using the ‘lsnrctl start <listener_name>’ command.

 

After Cloning Managers are not coming up

Method#1:

● Clean the FND_NODE Info:
EXEC FND_CONC_CLONE.SETUP_CLEAN;
COMMIT;
EXIT;
●● Run Autoconfig on DB node and then Apps Node
●●● Run $FND_TOP/patch/115/sql/afdcm037.sql script
●●●● Start Services (adstrtal.sh)


Method#2:

● Ensure Concurrent :GSM Enabled profile is set to ‘Y’
●● Run $FND_TOP/patch/115/sql/afdcm037.sql

●●● Do Relinking of FND Conc Libraries:
cd $FND_TOP/bin
adrelink.sh force=y "fnd FNDLIBR"
adrelink.sh force=y "fnd FNDSM"
adrelink.sh force=y "fnd FNDFS"
adrelink.sh force=y "fnd FNDCRM"

Before bringing the managers up, execute CMCLEAN….. In most of the cases it helped….

FNDLOAD Utility - Some Ready Reference

CUSTOM_MODE=FORCE in Upload

FNDLOAD apps/${xx_appspassword} O Y UPLOAD $FND_TOP/patch/115/import/afcpprog.lct AG_HR_EMP_RETIRE_PROG.ldt CUSTOM_MODE=FORCE


MENU

FNDLOAD apps/${xx_appspassword} O Y DOWNLOAD $FND_TOP/patch/115/import/afsload.lct <Menu_Name>.ldt MENU MENU_NAME="<Menu_Name>"
FNDLOAD apps/${xx_appspassword} O Y UPLOAD $FND_TOP/patch/115/import/afsload.lct <Menu_Name>.ldt


CONCURRENT PROGRAM

FNDLOAD apps/${xx_appspassword} O Y DOWNLOAD $FND_TOP/patch/115/import/afcpprog.lct <ccm_shrt_nm>.ldt PROGRAM APPLICATION_SHORT_NAME="ROI" CONCURRENT_PROGRAM_NAME="<ccm_shrt_nm>"
FNDLOAD apps/${xx_appspassword}  O Y UPLOAD $FND_TOP/patch/115/import/afcpprog.lct <ccm_shrt_nm>.ldt


REQUEST_SET

FNDLOAD apps/${xx_appspassword}  O Y DOWNLOAD $FND_TOP/patch/115/import/afcprset.lct <req_set>.ldt REQ_SET_LINKS REQUEST_SET_NAME="<req_set>"
FNDLOAD apps/${xx_appspassword}  0 Y UPLOAD @FND:patch/115/import/afcprset.lct <req_set>.ldt REQ_SET_LINKS



RESPONSIBILITIES

FNDLOAD apps/${xx_appspassword} O Y DOWNLOAD $FND_TOP/patch/115/import/afscursp.lct <Resp_Key>.ldt FND_RESPONSIBILITY RESP_KEY="<Resp_Key>"
FNDLOAD apps/${xx_appspassword} O Y UPLOAD $FND_TOP/patch/115/import/afscursp.lct <Resp_Key>.ldt FND_RESPONSIBILITY




VALUE_SET

FNDLOAD apps/${xx_appspassword} 0 Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct <val_set>.ldt VALUE_SET FLEX_VALUE_SET_NAME=<val_set>
FNDLOAD apps/${xx_appspassword} O Y UPLOAD $FND_TOP/patch/115/import/afffload.lct <val_set>.ldt




REQUEST GROUP

FNDLOAD apps/${xx_appspassword} O Y DOWNLOAD $FND_TOP/patch/115/import/afcpreqg.lct <req_grp>.ldt REQUEST_GROUP REQUEST_GROUP_NAME="<req_grp>" APPLICATION_SHORT_NAME="ROI"
FNDLOAD apps/${xx_appspassword} O Y UPLOAD $FND_TOP/patch/115/import/afcpreqg.lct <req_grp>.ldt




PRINTER STYLES

FNDLOAD apps/${xx_appspassword} O Y DOWNLOAD $FND_TOP/patch/115/import/afcppstl.lct <prntr_styl>.ldt STYLE PRINTER_STYLE_NAME="<prntr_styl>"
FNDLOAD apps/${xx_appspassword} O Y UPLOAD $FND_TOP/patch/115/import/afcppstl.lct <prntr_styl>.ldt




ALERT

FNDLOAD apps/${xx_appspassword} O Y DOWNLOAD $ALR_TOP/patch/115/import/alr.lct <alert>.ldt ALR_ALERTS APPLICATION_SHORT_NAME="FND" ALERT_NAME="<alert>"
FNDLOAD apps/${xx_appspassword} O Y UPLOAD $ALR_TOP/patch/115/import/alr.lct <alert>.ldt




USER

FNDLOAD apps/${xx_appspassword} 0 Y DOWNLOAD $FND_TOP/patch/115/import/afscursp.lct <user_name>.ldt FND_USER USER_NAME='<user_name>'
FNDLOAD apps/${xx_appspassword} 0 Y UPLOAD $FND_TOP/patch/115/import/afscursp.lct <user_name>.ldt

Notes for using FNDLOAD against FND_USER:-
1. After uploading using FNDLOAD, user will be promoted to change their password again during their next signon attempt.
2. All the responsibilities will be extracted by FNDLOAD alongwith User Definition in FND_USER 
3. In the Target Environment , make sure that you have done FNDLOAD for new responsibilities prior to running FNDLOAD on users. 




LOOKUP

FNDLOAD apps/${xx_appspassword} 0 Y DOWNLOAD $FND_TOP/patch/115/import/aflvmlu.lct <lookup_type>.ldt FND_LOOKUP_TYPE APPLICATION_SHORT_NAME ='XXCTO' LOOKUP_TYPE="<lookup_type"
FNDLOAD apps/${xx_appspassword} 0 Y UPLOAD $FND_TOP/patch/115/import/aflvmlu.lct <lookup_type>.ldt



FUNCTION

FNDLOAD apps/${xx_appspassword} 0 Y DOWNLOAD $FND_TOP/patch/115/import/afsload.lct XXCTO_VEH.ldt FUNCTION FUNCTION_NAME="XXCTO_VEH%"
FNDLOAD apps/${xx_appspassword} 0 Y UPLOAD $FND_TOP/patch/115/import/afsload.lct XXCTO_VEH.ldt