KIMYONG : basic Export / Attachment issues 가이드

Question

Purpose
======
이 문서는 Support Analayst / DBA에게 Export /Attachments issues 발생시
조치할수 있는 기본적인 Troubleshooting Guide를 소개하고자 합니다.
Explanations
======
Export Analysis
Turn on export debug,
Go to Help -> Diagnostics -> Examine
Set Block = GLOBAL
Set Field = FND_EXPORT_DEBUG
Set Value = TRUE
Then export and observe the messages that are generated during the export process
Important Parameters.
set serveroutput on
declare
plsql_agent varchar2(200);
web_server varchar2(200);
dad varchar2(200);
gfm_agent varchar2(200);
protocol varchar2(200);
database_id varchar2(200);
jsp_agent varchar2(200);
check_enabled varchar2(200) ;
begin
plsql_agent := fnd_web_config.plsql_agent ;
dbms_output.put_line('PL SQL Agent ->'||plsql_agent);
web_server :=fnd_web_config.web_server ;
dbms_output.put_line('Web Server ->'||web_server);
dad := fnd_web_config.dad ;
dbms_output.put_line('DAD ->'||dad);
gfm_agent := fnd_web_config.gfm_agent ;
dbms_output.put_line('GFM Agent ->'||gfm_agent);
protocol := fnd_web_config.protocol ;
dbms_output.put_line('Protocol ->'||protocol);
database_id := fnd_web_config.database_id ;
dbms_output.put_line('Database Id ->'||database_id);
jsp_agent := fnd_web_config.jsp_agent ;
dbms_output.put_line('JSP Agent ->'||jsp_agent);
check_enabled := fnd_web_config.check_enabled('FND_GFM.GET') ;
dbms_output.put_line('FND_GFM.GET ->'||check_enabled);
end ;
Examining SQL Trace for the sequence of events that happen in the Export process
SQL >alter session set events '10046 trace name context forever, level 12';
Then run the following block of pl/sql code
set serveroutput on
declare
db_file number;
mime_type varchar2(255) :='text/plain' ;
out_string varchar2(32767) :='Just some plain text that is stored' ;
web_server_prefix varchar2(500);
url varchar2(500);
begin
db_file :=fnd_gfm.file_create(content_type =>mime_type,program_name=>'export');
fnd_gfm.file_write_line(db_file,out_string);
db_file :=fnd_gfm.file_close(db_file);
url:=fnd_gfm.construct_download_url(fnd_web_config.gfm_agent,db_file,TRUE);
dbms_output.put_line(url);
end;
Exit the sql plus session and study the sql trace file as being there in USER_DUMP_DEST
$ ls -lrt
Refer to Note # 282806.1 Performance Tuning Approach for Oracle(8.1.6 - 9.2.0.5) on
UNIX for more information on how to obtain sql tracing .
Example of download URL :-
http://finance.sriratu:8001/pls/SR/fndgfm/fnd_gfm.get/776537528/202595/fnd_gfm.tsv
http://aoltest2.idc.oracle.com:8000/pls/VIS/fndgfm/fnd_gfm.get/820067633/298941/Screen_shots.doc
Example of Upload Attachment URL:
http://aoltest2.idc.oracle.com:8000/pls/VIS/OracleSSWA.Execute?
E=%7B!2DAF44968EBBEC83211B5D5F27F58334FBFB2B90E38AD205&P=%7B!BEFD8114A932C86A1548EC73FFCF6EADB4F7826B217EDCE92719B62BDA9FF0AF193DC7BC64A2C60AFC5123B50C8C78F9E6807695ED9A7FE7AE87F8E49E80807223756706B3FC777F645FA5A07C7A467B
http://aoltest2.idc.oracle.com:8000/pls/VIS/OracleSSWA.Execute?
E=%7B!2DAF44968EBBEC83211B5D5F27F58334FBFB2B90E38AD205&P=%7B!BEFD8114A932C86A5525987DB9C8D9785657497306AAE1FD25D1CC352ADF38DFD69C21355096CBC38D285B083D24F261701F5F278E199044D603A5A8B1D588292099782AC4AF3D97E23B95936809D280
To check the row being created in the table FND_LOBS during Export or Attachment
SQL>create table fnd_lobs_bak as
select file_id,file_name from fnd_lobs ;
SQL>select * from fnd_lobs
where file_id not in
(select file_id from fnd_lobs_bak );
SQL>select * from fnd_lobs
where to_char(upload_date,'DD/MM/YYYY')=to_char(sysdate,'DD/MM/YYYY')
Analysis on an Attachment
Help -> Diagnostics -> Examine
Block : DOCUMENT_HEADER
Field : ATTACHED_DOCUMENT_ID
Note down <Value>
SQL>select document_id
from fnd_attached_documents
where attached_document_id=<Value>;
SQL>select media_id
from fnd_documents_tl
where document_id=<document_id>;
SQL>select *
from fnd_lobs
where file_id=<media_id>;
SQL>select *
from fnd_documents_short_text
where media_id=<media_id>;
from fnd_documents_long_text
where media_id=<media_id>;
SQL>select *
from fnd_documents_long_raw
where media_id=<media_id>;
FND_LOBS stores information about all LOBs managed by the Generic File Manager (GFM).
Each row includes the file identifier, name, content-type, and actual data. Each row also
includes the dates the file was uploaded and will expire, the associated program name and
tag, and the language and Oracle characterset.
The file data, which is a binary LOB, is stored exactly as it is uploaded from a client browser,
which means that no translation work is required during a download to make it HTTP compliant.
Therefore uploads from non-browser sources will have to prepare the contents
appropriately (for instance, separating lines with CRLF).
The program_name and program_tag may be used by clients of the GFM for any purpose,
such as striping, partitioning, or purging the table if the program is de-installed.
They are otherwise strictly informative.
These columns and the expiration date are properly set when the
procedure FND_GFM.CONFIRM_UPLOAD is called. If not called, the column
expiration_date remains set, and will eventually be purged by the procedure
FND_GFM.PURGE_EXPIRED.
FND_DOCUMENTS_LONG_RAW stores images and OLE
Objects, such as Word Documents and Excel
spreadsheets, in the database. If the user elects
to link an OLE Object to the document, this table
stores the information necessary for Oracle Forms
to activate the OLE server, and it saves a
bit-mapped image of the OLE server's contents.
If the user does not elect to link an OLE Object,
the entire document will be stored in this table.
FND_DOCUMENTS_LONG_TEXT stores information about
long text documents.
FND_DOCUMENTS_SHORT_TEXT stores information about
short text documents.
To know which Forms provide Attachment feature
SQL>select *
from fnd_attachment_functions
where function_name like '%FND_%';
Examining FND_LOBS tablespace
SQL>select tablespace_name
from dba_tables
where table_name='FND_LOBS';
SQL>select *
from fnd_profile_options_tl
where profile_option_name='FND_EXPORT_MIME_TYPE';
SQL>select a.tablespace_name TABLESPACE_NAME , a.bytes TOTAL_BYTES,
sum(b.bytes) FREE_BYTES , count(*) EXTENTS
from dba_data_files a, dba_free_space b
where a.file_id = b.file_id AND A.TABLESPACE_NAME=<TABLESPACE_NAME>
group by a.tablespace_name, a.bytes
order by a.tablespace_name ;
Examing Profile Option value
SQL>select *
from fnd_profile_options_tl
where profile_option_name='FND_EXPORT_MIME_TYPE' ;
SQL>select b.profile_option_name,level_id,profile_option_value
from fnd_profile_option_values a, fnd_profile_options b
where a.application_id=b.application_id
and a.profile_option_id=b.profile_option_id
and b.profile_option_name in ('FND_EXPORT_MIME_TYPE') ;
Procedure FND_GFM.GET ANALYSIS
http://aoltest2.idc.oracle.com:8000/pls/VIS/fndgfm/fnd_gfm.get/560074272/298951/fnd_gfm.doc
access
SQL>select substr('/560074272/298951/fnd_gfm.doc',instr('/560074272/298951/fnd_gfm.doc','/',1)+1,instr('/560074272/298951/fnd_gfm.doc','/',2)-2) access from dual ;
560074272
file_id
SQL>select substr('/560074272/298951/fnd_gfm.doc',instr('/560074272/298951/fnd_gfm.doc','/',2)+1,(instr('/560074272/298951/fnd_gfm.doc','/',-1)-instr('/560074272/298951/fnd_gfm.doc','/',2)-1)) from dual ;
298951
Profile Options being referenced in the package FND_GFM
FND_EXPORT_MIME_TYPE
FND_NATIVE_CLIENT_ENCODING
Lookup Type Being used in the package FND_GFM
SQL>select tag,lookup_code,meaning
from fnd_lookup_values_vl
where lookup_type='FND_ISO_CHARACTER_SET_MAP';
Reference
========
Note 338651.1

Answer 1