Showing posts with label Apps Related Issue. Show all posts
Showing posts with label Apps Related Issue. Show all posts

Saturday, April 2, 2011

Windows just disappears without any export

Problem: Data not generated in file means rows not to be exported when hitting “File -> Export”. The windows’ informing exporting data comes up and end without any error message or exporting.

Solution:

The above errors verify issues with index on FND_LOBS table. The cause is either lack of space in tablespace behind FND_LOBS indexes or corrupt index. This can be fixed by:

Step 1 Identify the tablespace behind this index to verify sufficient space to tablespace .

SQL> select INDEX_NAME, TABLESPACE_NAME from DBA_INDEXES where TABLE_NAME='FND_LOBS';

Step 2 if no sufficient space, just adds more files to the index tablespace.

Step 3 Rebuild the indexes by executing $FND_TOP/sql/aflobbld.sql (version should be 115.22 or higher) as APPS user.

This script takes two Argument:

1) The name of the APPLSYS schema (ie: APPLSYS)
2) The name of the APPS schema (ie: APPS)

Reference

Metalink Note: 272526.1: 'Export' Function Has Stopped Working In All Modules
Metalink Note: 338651.1: Troubleshooting Export and Attachment issues in Oracle
Metalink Note: 338651.1: Troubleshooting Export and Attachment issues in Oracle
Metalink Note: 71639.1: EOERR: ORA-29861 domain index is marked LOADING/FAILED/UNUSABLE





Friday, April 1, 2011

ERROR : ORA-20100: File o0013319.tmp creation for FND_FILE failed

When attempting to run a concurrent request, the following error occurs in the log file:
-------------------------------------------------------------------------------------------------------------
ERROR
ORA-20100: File o0013319.tmp creation for FND_FILE failed.
You will find more information on the cause of the error in request log.
Error: function fa_asset_trace_pkg.save_output returned failure
-------------------------------------------------------------------------------------------------------------
This error is caused by a concurrent manager setup and privilege related issue in the $APPLPTMP environment variable and UTL_FILE_DIR database parameter.

NOTE: Applications also produces temporary PL/SQL output files used in concurrent processing. These files are written to a location on the database server node specified by the APPLPTMP environment setting. The APPLPTMP directory must be the same directory as specified by the utl_file_dir parameter in your database initialization file.
-------------------------------------------------------------------------------------------------------------
Solution


Step 1 Make sure that APPLPTMP is set to a valid directory and that BOTH the applmgr user and the database user have read and write permissions on that directory (normally, it can be set to the same directory as APPLTMP).


Step 2 Make sure the directory pointed by APPLPTMP is the first entry on the utl_file_dir. Also, verify that all the entries on the utl_file_dir are valid and that the applmgr has read/write permissions.

Step 3 Check application user able to creat file in above directory if no then go to next step.

Step 4 Grant all users read/write permissions to that directory:

chmod 777 /usr/tmp

Step 5 Check DB user can write a file directly using FND_FILE, which is the package used by the Application. From sqlplus, connected as the apps user, run:


SQL> exec FND_FILE.PUT_LINE(FND_FILE.LOG, 'THIS IS A TEST');

This should dump a file on APPLPTMP.

Saturday, July 3, 2010

APP-SQLAP-10380 You Cannot Select this Payment Document

Step 1. Check that there are no locks on the payment batch

SELECT a.object_id, a.session_id, b.object_name FROM v$locked_object a, dba_objects b WHERE a.object_id = b.object_id

This select should return one row displaying AP_CHECK_STOCKS_ALL.

Step 2. Get the user's session ID and serial number.

SELECT sid, serial# from v$session WHERE sid = ;

Step 3. Once you have the 2 pieces of information from above, run the following:

ALTER system kill session 'sid, serial#'

------Completed---------------------