Move the Concurrent Program ,data defination etc using FNDLOAD

1.Concurrent Program

FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afcpprog.lct XXAP_UTILITY_PAYABLE.ldt PROGRAM APPLICATION_SHORT_NAME=XXARG CONCURRENT_PROGRAM_NAME=XXAP_UTILITY_PAYABLE

FNDLOAD apps/apps 0 Y UPLOAD $FND_TOP/patch/115/import/afcpprog.lct XXAP_UTILITY_PAYABLE.ldt – CUSTOM_MODE=FORCE
==================================================================================
2.Template and data defination :

FNDLOAD apps/apps 0 Y DOWNLOAD $XDO_TOP/patch/115/import/xdotmpl.lct XXAP_UTILITY_PAYABLE_tmp.ldt XDO_DS_DEFINITIONS APPLICATION_SHORT_NAME=XXARG DATA_SOURCE_CODE=XXAP_UTILITY_PAYABLE


FNDLOAD apps/apps 0 Y UPLOAD $XDO_TOP/patch/115/import/xdotmpl.lct XXAP_UTILITY_PAYABLE_tmp.ldt
=================================

Can not login to Applications : oracle.apps.fnd.framework.OAException: Could not load application module 'oracle.apps.fnd.sso.login.server.MainLoginPageAM'.

No user able to connect: 

oracle.apps.fnd.framework.OAException: Could not load application module

'oracle.apps.fnd.sso.login.server.MainLoginPageAM'.

## Detail 0 ##

oracle.apps.fnd.framework.OAException: Application: FND, Message Name:

FND_NO_TRANSACTION_ID.

===========CAUSE =============

Due to tablespace one of the tablespace full 

=======SOLUTION =================

Increase the tablespace and retry ....

Ref: 737960.1
        

Purge Concurrent Request and/or Manager Data Running long after clone

cause
=======
When the purge program is run it will be executed from one of the concurrent processing nodes, it will try to delete the request log and output files. The complete paths to these files are stored in FND_CONCURRENT_REQUESTS table under columns LOGFILE_NAME and OUTFILE_NAME , the node where they are physically stored will be indicated in columns LOGFILE_NODE_NAME and OUTFILE_NODE_NAME.
The purge program will try to delete these log and output files from the node where it is running, it is mandatory that OS files can be accessed and deleted from the nodes where the concurrent managers are running.
The node retaining the out/log files doesn't exist anymore in the architecture, but the purge program uses this node name to delete the files from your system. If the program can not access these files it will have issues .


Need to check :

1.select count(*) from fnd_concurrent_requests

2.select LOGFILE_NODE_NAME, OUTFILE_NODE_NAME, count(*) from fnd_concurrent_requests
group by LOGFILE_NODE_NAME, OUTFILE_NODE_NAME

3.select node_name , SUPPORT_CP , SUPPORT_FORMS , SUPPORT_WEB,SUPPORT_ADMIN, STATUS
from fnd_nodes

4.select CONCURRENT_QUEUE_NAME , MAX_PROCESSES , RUNNING_PROCESSES ,
TARGET_NODE , NODE_NAME , NODE_NAME2 , ENABLED_FLAG , CONTROL_CODE
from FND_CONCURRENT_QUEUES
/

SELECT trigger_name , status FROM user_triggers WHERE table_name = 'FND_NODES' 

5- What is the result of the unix commands from the concurrent manager node :

uname -a
hostname
domainname

==============SOLUTION ================================

create table FND_RUN_REQUESTS_bk1 as select * from FND_RUN_REQUESTS  126
create table FND_CONCURRENT_REQUESTS_bk1 as select * from FND_CONCURRENT_REQUESTS   (rows =4964  )
create table FND_CONCURRENT_PROCESSES_bk1 as select * from FND_CONCURRENT_PROCESSES  (rows=1073 )


delete  FND_RUN_REQUESTS WHERE parent_request_id
in (select request_id from FND_CONCURRENT_REQUESTS where upper(LOGFILE_NODE_NAME) = 'OLDNODE' or upper(OUTFILE_NODE_NAME) = 'OLDNODE');


delete FND_CONCURRENT_REQUESTS where upper(LOGFILE_NODE_NAME) = 'OLDNODE' or
upper(OUTFILE_NODE_NAME) = 'OLDNODE';

In GATHER_SCHEMA_STATS , schema_name= ALL percent= 10 degree = 8 internal_flag= NOBACKUP

Gather Schema Statistics" program reported following errors:  R12.1.3
============================================================
Error #1: ERROR: While GATHER_TABLE_STATS: 
object_name=GL.JE_BE_LINE_TYPE_MAP***ORA-20001: invalid column name or duplicate columns/column groups/expressions in method_opt*** 
Error #2: ERROR: While GATHER_TABLE_STATS: 
object_name=GL.JE_BE_LOGS***ORA-20001: invalid column name or duplicate columns/column groups/expressions in method_opt*** 
Error #3: ERROR: While GATHER_TABLE_STATS: 
object_name=GL.JE_BE_VAT_REP_RULES***ORA-20001: invalid column name or duplicate columns/column groups/expressions in method_opt***

Error #4: ERROR: While GATHER_TABLE_STATS:  object_name=FII.FII_FIN_ITEM_HIERARCHIES***ORA-20001: invalid column name or duplicate columns/column groups/expressions in method_opt***
=============================================================





There are two reasons for that error message:

1 ) There are duplicate rows on FND_HISTOGRAM_COLS table for JE_BE_LINE_TYPE_MAP table.
Because of this problem, FND_STATS tries to gather histogram information using wrong command and
it fails with ora-20001 errors.

Following SQL should have returned one row , not two.

SQL> select a.column_name, nvl(a.hsize,254) hsize
from FND_HISTOGRAM_COLS a
where table_name = 'JE_BE_LINE_TYPE_MAP'
order by column_name;

COLUMN_NAME HSIZE
------------------------------ ----------
SOURCE 254
SOURCE 254

2) Column does not exist on the table but still listed in FND_HISTOGRAMS_COL table.

Solution:

1. Remember don't forget  to take backup of the FND_HISTOGRAM_COLS table before deleting any data. 

Find out all duplicates and/or obsolete rows in FND_HISTOGRAM_COLS and delete one of them.

-- identify duplicate rows
select table_name, column_name, count(*)
from FND_HISTOGRAM_COLS
group by table_name, column_name
having count(*) > 1;



-- Use above results on the following SQL to delete duplicates
delete from FND_HISTOGRAM_COLS
where table_name = '&TABLE_NAME'
and  column_name = '&COLUMN_NAME'
and rownum=1;