File Extensions in Oracle Applications..

.pl extension:

Script written in Perl that is compiled and run using a Perl interpreter; contains lines of Perl program code with variables, operations, functions, and comments; may be difficult to read due to the brief and compact nature of the Perl language syntax.

PL scripts are commonly used to create programs that parse text using regular expressions, but they also are used for a wide variety of other applications, including server scripting and Web server CGI scripts.

PL files typically start with the line #!/usr/local/bin/perl, which tells the computer to run the script using the installed Perl interpreter.

.sh extension:

Files that contain the .sh file extension are self-extracting archive files. The SH file archive contains selected files and a shell script along with instructions on how to extract the contents of the SH file archive.

The SH file format is commonly used for Unix shell files and are created by the Unix shar utility program. These files are typically used for scripts that are meant to be run on the Unix command prompt. SH files can typically only be used on computers that are run on the Unix operating system, although systems similar to Unix may also use this file format.

.sql extension:

File written in SQL (Structured Query Language); contains SQL code used to modify the contents of a relational database; may contain statements for creating or modifying database structures, or may contain insertions, updates, deletions, and other SQL operations.

SQL files can be read by any SQL-compatible database program, including FileMaker, Microsoft Access, and MySQL. They can be edited using any text editor.

.log extensions:

Text file that keeps a log of certain events; may be created by the operating system to keep track of system events; also may be created by software installation programs, which list the name and location of installed files.

Most Web servers also generate log files for each hosted website to keep track of visitors and to monitor bandwidth usage; Web stats programs use log files to generate charts and graphs that present website traffic data in a graphical format.

.xml extension:

XML (Extensible Markup Language) data file that uses tags to define objects and object attributes; formatted much like an .HTML document, but uses custom tags to define objects and the data within each object; can be thought of as a text-based database.

XML files have become a standard way of storing and transferring data between programs and over the Internet. Because they are formatted as text documents, they can be edited by a basic text editor.

.conf extension:

Configuration or "config" file used on Unix and Linux based systems; stores settings for system processes and applications; similar to a .CFG file found on Windows and Macintosh systems.

Some examples of configuration files include rc.conf for the system startup, syslog.conf for system logging, smb.conf for the Samba server, and httpd.conf for the Apache Web server.

.cfg extension:

The .cfg file extension is assigned to a computer's configuration files. Configuration files are used by a wide range of programs and applications. The information within some CFG files contains a program's initial configuration and settings.

Some files with the .cfg file extension are also created when you change the settings of a particular program or computer application. For example, if you change the interface settings of a particular application the application will create a new CFG file to accommodate those settings.

Files that have the .cfg file extension are usually written in ASCII code, although the files may be stored in a different format depending on the application that it was created with.

.ini extension:

An .INI file is a type of file that contains configuration information in a simple, predefined format. It is used by Windows OSs and Windows-based applications to store information about the user's preferences and operating environment. These files are plain text files with a basic structure comprised of properties and sections. It is pronounced as “dot in-ee" or simply "in-ee” file, where .ini signifies “initialization".

.ora extension:

Text file used by Oracle Database, an enterprise-level relational database management system (RDBMS); contains database configuration parameters; used for storing system-wide defaults and for fine-tuning database performance.

All parameters in ORA files are optional since the Oracle database already contains default values for the required parameters. Parameters can be specified in any order.

Common ORA filenames include init.ora (initialization parameters) and tnsnames.ora (SQL*Net connection configuration file).

.a  - Library files for C language code

.c  - C lang source code

.ctl - DataMerge control file (Sql loader)

.dat - DataMerge import/export (Data file)

.Drv  - Driver (patch related files)

.env - Unix environment

.exp - DataMerge export

.fmb - Binary forms

.fmx - Execuatble forms

.h - C lang header file

.jar - java archive

.lc - C lang source to be archived

.lct - Data loader control

.ldt - Data loader datafile

.log - Concurrent request log

.lpc - PRO*C source to be archived

.msb - Binary message

.msg - Readable message

.o - C lang object module

.odf - Object description

.out - Concurrent request output

.plb - PL/SQL package body

.pll - PL/SQL shared library (reports)

.pls - PL/SQL package specs

.rdf - Oracle D2k Reports

.req - Oracle reports Executable

.sso – It is a ChessDB search options file that belongs to Database Files. .sso file store data in a structured format, organized into tables and fields.

.p12  extension:

In cryptography, PKCS #12 defines an archive file format for storing many cryptography objects as a single file. It is commonly used to bundle a private key with its X.509 certificate or to bundle all the members of a chain of trust.

A PKCS #12 file may be encrypted and signed. The internal storage containers, called "SafeBag"s, may also be encrypted and signed. A few Safe Bags are predefined to store certificates, private keys and CRLs. Another Safe Bag is provided to store any other data at individual implementer's choice.

PKCS #12 is one of the family of standards called Public-Key Cryptography Standards (PKCS) published by RSA Laboratories. The filename extension for PKCS #12 files is ".p12" or ".pfx".

These files can be created, parsed and read out with the OpenSSL pkcs12 command.

<Request ID>.req

This is the Concurrent Request log file. When any concurrent request is submitted, request log file is created in this directory with file name as l<Request ID>.req

Events####.log

adstrtal.sh script writes the log information in to this file, when ever there is any problem with starting of any 

Application Service.

Error####.log

This file contains the Java Exception Errors.

#####.log

This file keeps the information of starting of Apache Listener.

 f60webmx_dump_<PID>

This file is created when ever any Client Forms Session ends abruptly. When user forms session got crash or terminated abruptly that diagnostics information is written into this dump file.  If you want to get rid out of this dump files. Please execute the following steps Set the FORMS60_CATCHTERM = 0 in Registry (NT) or Environment Variable (Unix/Linux) and bounce the Forms Services

em_<PID>.rti

This file contains Client run time process information. These files are used by Oracle Application Manager and Enterprise Manager for Forms Monitoring Services and are generated by Forms runtime processes. For each f60webmx session, there is one .rti file is created. These files are written to the directory set by parameter $FORMS60_RTI_DIR.  By default these are written into $APPLCSF/$APPLLOG directory. RTI files should be automatically cleaned up when user logs out of the forms session, in case user logs out of the forms sessions abruptly. Then these files are not cleaned up properly. So then you may need to clear these files manually. We can delete the files, but we should not delete these files when users are active

em –> enterprise manager

<PID> –> Process ID of Client

rti –< Run time information In some cases,

we need to delete the FNDCPPUR program log files and output files manually to free up the disk space. Here I am giving UNIX commands to find out and deleting the old files. If your FNDCPPUR program is scheduled to run daily and given AGE Mode value as 7, purge Program has to delete the files which are older than 7 days. But if program did not delete the files, use this command to find out those files.

 Find the Concurrent Request Log and Output files which are not deleted

 find $APPLCSF/$APPLLOG -mtime +7 -name “*.req”

 find $APPLCSF/$APPLOUT -mtime +7 -name “*.out

Delete the Concurrent Request log and output files which are older than 7 Days

 find $APPLCSF/$APPLLOG -mtime +7 -name “*.req” -exec rm “{}” “;”

 find $APPLCSF/$APPLOUT -mtime +7 -name “*.out” -exec rm “{}” “;”

Delete other files in $APPLCSF/$APPLLOG directory

find $APPLCSF/$APPLLOG -mtime +7 -name “*.log” -exec rm “{}” “;”

find $APPLCSF/$APPLLOG -mtime +7 -name “*.mgr” -exec rm “{}” “;”

find $APPLCSF/$APPLLOG -mtime +7 -name “f60webmx*” -exec rm “{}” “;”

find $APPLCSF/$APPLLOG -mtime +7 -name “*.rti” -exec rm “{}” “;”