Thursday, September 1, 2016

Basic queries often used for Oracle Administration

The below are the basic queries which can be used for DB administration:

To check space of tablespaces:

select tablespace_name, used_percent from dba_tablespace_usage_metrics where used_percent > 85;

To delete archivelogs :

delete noprompt archivelog until time 'SYSDATE-1';

DELETE noprompt archivelog until time "to_date('2014-07-14:01:00:00','YYYY-MM-DD:hh24:mi:ss')";

To check archivelog generation per hour :

alter session set NLS_DATE_FORMAT='DD-MON-YYYY HH24:MI:SS';

select trunc(COMPLETION_TIME,'HH') Hour,thread# , round(sum(BLOCKS*BLOCK_SIZE)/1048576) MB,count(*) Archives from v$archived_log group by trunc(COMPLETION_TIME,'HH'),thread# order by 1 ;

select JOB,WHAT,BROKEN,FAILURES,INTERVAL from dba_jobs where what like ‘%INFI%’;

select job,what,interval from dba_jobs where what like '%xxxx%';

select * from dba_mview_refresh_times where name like '%xxxx%';

To check whether rman backup completed :

set pages 2000 lines 200
COL in_sec FORMAT a10
COL out_sec FORMAT a10
COL TIME_TAKEN_DISPLAY FORMAT a10
col output_bytes_display for a10
select session_key,
       input_type,
       status,
       to_char(start_time,'yyyy-mm-dd hh24:mi') start_time,
       to_char(end_time,'yyyy-mm-dd hh24:mi')   end_time,
       output_bytes_display,
       time_taken_display
from v$rman_backup_job_details
order by session_key asc;

To know the version of oracle apps:

select release_name from apps.fnd_product_groups;

To check space of tablespaces:

select tablespace_name, used_percent from dba_tablespace_usage_metrics where used_percent > 85;

To know the version of oracle apps :

select release_name from apps.fnd_product_groups;

If password expire or locked:

alter user username identified by passwrd account unlock;
alter user username account unlock;


NOTE: As of 11g the DBA_USERS table no longer contains encrypted passwords. Use the SYS.USER$ table and the NAME, PASSWORD columns.

select name, password, ltime from user$ order by name, exptime;


To change password of sys: (This has to be executed on comand prompt at the path orapwd file location)
 $ orapwd file=filename  password=password entries=max_users

To create controlfile :
alter database backup controlfile to trace as 'location';

Create table in oracle:

CREATE TABLE table_name(
   column1 datatype,
   column2 datatype,
   column3 datatype,
   .....
   columnN datatype,
   PRIMARY KEY( one or more columns )
);

Insert into table:

INSERT INTO TABLE_NAME (column1, column2, column3,...columnN)]
VALUES (value1, value2, value3,...valueN);

Update table oracle:

UPDATE table_name
SET column1 = value1, column2 = value2...., columnN = valueN
WHERE [condition];


To create a service in windows:

sc [<ServerName>] create [<ServiceName>] [type= {own | share | kernel | filesys | rec | interact type= {own | share}}] [start= {boot | system | auto | demand | disabled}] [error= {normal | severe | critical | ignore}] [binpath= <BinaryPathName>] [group= <LoadOrderGroup>] [tag= {yes | no}] [depend= <dependencies>] [obj= {<AccountName> | <ObjectName>}] [displayname= <DisplayName>] [password= <Password>]

To delete service in windows:

sc "\\<servername>" delete <service-name>


To change passwrd encrypted:

set pagesize 0
set long 90000
set feedback off
set echo off
select dbms_metadata.get_ddl('USER', 'xyz') from dual;

To know the tablespaces:

To view all tablespaces:

SELECT TABLESPACE_NAME,SUM(BYTES)/1024/1024/1024 "FREE SPACE(GB)" FROM DBA_FREE_SPACE GROUP BY TABLESPACE_NAME;

-------------------------------

To view all tablespaces in % :

select tablespace_name, used_percent from dba_tablespace_usage_metrics where used_percent > 85;

-------------------------------

To view all tablespaces with free space :

column "Tablespace" format a13
column "Used MB"    format 99,999,999
column "Free MB"    format 99,999,999
column "Total MB"   format 99,999,999
select
   fs.tablespace_name                          "Tablespace",
   (df.totalspace - fs.freespace)              "Used MB",
   fs.freespace                                "Free MB",
   df.totalspace                               "Total MB",
   round(100 * (fs.freespace / df.totalspace)) "Pct. Free"
from
   (select
      tablespace_name,
      round(sum(bytes) / 1048576) TotalSpace
   from
      dba_data_files
   group by
      tablespace_name
   ) df,
   (select
      tablespace_name,
      round(sum(bytes) / 1048576) FreeSpace
   from
      dba_free_space
   group by
      tablespace_name
   ) fs
where
   df.tablespace_name = fs.tablespace_name;

**************
select distinct TEMPORARY_TABLESPACE from dba_users;
**************
create temporary tablespace TEMP_01 tempfile 'C:\app\oracle\oradata\devidw\xxx.DBF size 500M autoextend on maxsize 8024M;
**************
alter database default temporary tablespace TEMP_01;


To view the user which is connected:

select s.sid, s.serial#, s.status, p.spid
from v$session s, v$process p
where s.username = 'myuser'
and p.addr (+) = s.paddr;

-- alter system kill session '<sid>,<serial#>';

To know the privilege of user:

select privilege
from dba_sys_privs
where grantee='HYPHSS' order by 1;


To create user / schema:

create user <username> identified by <password>;

To grant privileges :

grant <privileges> to <username>;


To create a DB_Link:

create public database link DBlink connect to user identified by password using 'Dblink';

create public database link Link_name connect to user identified by password using 'dblink';

And to test the dblink:

select * from dual@urdblink;

To know the schema size : 

select
   sum(bytes)/1024/1024/1024 as size_in_gig,
   segment_type
from
   dba_segments
where
   owner='SCOTT'
group by
   segment_type;




Thursday, May 22, 2014

File System of Oracle Applications R12..


An Oracle E-Business Suite Release 12 system utilizes components from many Oracle products. These product files are stored below a number of key top-level directories on the database and application server machines.

Note: No Oracle E-Business Suite components are installed on desktop client machines, although JAR files and 
their supporting utilities are downloaded as required.

Depending on how you chose to install Oracle E-Business Suite, these product directories may be located on a single machine (the simplest case) or on multiple machines (the most common type of deployment). Operating system environment settings indicate the location of the various files in the file systems of the database and application tier machines. This chapter discusses the association between these environment settings and the 
corresponding files and directories.


the picture is described in the document text

  • The db/apps_st/data directory is located on the database node machine, and contains the system tablespaces, redo log files, data tablespaces, index tablespaces, and database files
  • The db/tech_st/11.1.0 directory is located on the database node machine, and contains the ORACLE_HOME for the Oracle 11g database
  • The apps/apps_st/appl (APPL_TOP) directory contains the product directories and files for Oracle E-Business Suite
  • The apps/apps_st/comn (COMMON_TOP) directory contains Java classes, HTML pages, and other files and directories used by multiple products
  • The apps/tech_st/10.1.2 directory contains the ORACLE_HOME used for the Oracle E-Business Suite technology stack tools components
  • The apps/tech_st/10.1.3 directory contains the ORACLE_HOME used for the Oracle E-Business Suite technology stack Java components

Oracle E-Business Suite Environment

Oracle E-Business Suite makes extensive use of environment settings to locate executable programs and other files essential to Oracle E-Business Suite operation. These environment settings are defined when you install Oracle E-Business Suite. Many of the settings are defined by information you provide when running Rapid Install, while others have the same values in all installations.

The environment settings and their associated values are stored in environment files, which have a .env suffix on UNIX (.cmd on Windows). Environment files and settings are discussed in more detail later in this chapter.

Instance Home ($INST_TOP)

Oracle E-Business Suite Release 12 introduces the concept of a top-level directory for an Oracle E-Business Suite instance. This directory is referred to as the Instance Homeand denoted by the environment variable $INST_TOP.

Using an Instance Home provides the ability to share application and technology stack code among multiple instances, for example a development instance and a test instance. Other benefits include support for read-only file systems and centralization of log files, both of which are discussed further below.

The basic structure of the instance home is: <APPS_BASE>/inst/apps/<context_name>, where APPS_BASE (which does not have or need a corresponding environment variable) is the top level of the Oracle E-Business Suite installation, and <context_name> is the highest level at which the applications context exists. For example, the setting of $INST_TOP might be <diskresource>/applmgr/inst/apps/testsys2, where testsys2 is the context name.

All configuration files created by AutoConfig are stored under the Instance Home. This facilitates use of a shared application tier file system, as described later in this chapter.


the picture is described in the document text


Read-Only File Systems

A key benefit of moving to the new Instance Home model is that as AutoConfig no longer writes to the APPL_TOP or ORACLE_HOME directories, both of these can be made into read-only file systems if required. In previous Oracle E-Business Suite releases, the adpatch utility wrote to $APPL_TOP/admin on an administration (patching) node. Under the new model, $APPL_CONFIG_HOME/admin is used instead. $APPL_CONFIG_HOME will equate to a value such as /u01/oracle/VIS/apps/apps_st/appl.

Note: In a shared file system environment, Oracle recommends that the INST_TOP should be located on a local disk and not on a shared resource such as NFS, because of possible issues storing log files on shared resources.

Log Files

Another advantage of employing the concept of an Instance Home is that log files can be stored centrally for an instance, and therefore managed more easily.

Important: This is particularly significant from a security perspective, as log files may contain sensitive data that should not be accessible to general users.

The following diagram shows the directory structure used for log files in Release 12, with some of the subdirectories used to categorize the log files:


the picture is described in the document text


The data Directory

The db/apps_st/data directory stores the different types of file used by the Oracle database. Rapid Install places the system, data, and index files in directories below several file system mount points on the database machine. You can specify these mount points during installation.

The db Directory

Oracle E-Business Suite supports employing an Oracle E-Business Suite database running out of one ORACLE_HOME, while running other Oracle E-Business Suite components out of additional ORACLE_HOMEs. This multiple ORACLE_HOMEs configuration allows Oracle E-Business Suite to utilize new features of the Oracle Database and associated technologies in the most flexible manner.

Release 12 utilizes an Oracle Database 11g ORACLE_HOME, (Oracle E-Business Suite database home) whose files are located under the db directory. These files are needed for running and maintaining the Oracle E-Business Suite database.

Note: Oracle E-Business Suite is always certified with database server patchsets (minor maintenance releases).

The comn Directory

The apps/apps_st/comn (COMMON_TOP) directory contains files used by many different Oracle E-Business Suite products, and which may also be used with third-party products.


the picture is described in the document text

The admin directory

The admin directory, under the COMMON_TOP directory, is the default location for the concurrent manager log and output directories. When the concurrent managers run Oracle E-Business Suite reports, they write the log files and temporary files to the log subdirectory of the admin directory, and the output files to the out subdirectory of the admin directory.

You can change the location the concurrent managers write these files to, so that, for example, the log and output files are written to directories in each <PROD>_TOP directory. This may be more desirable in terms of disk space management, or the need to avoid a possible performance bottleneck on a system that has a high concurrent processing throughput.

Note: For further details, see Concurrent Processing Server in Chapter 1 of this book, and Chapters 6, 7 and 8 of Oracle E-Business Suite System Administrator's Guide - Configuration.

The install subdirectory of the admin directory contains scripts and log files used by Rapid Install. 

The scripts subdirectory of admin contains scripts used to start and stop services such as listeners and concurrent managers.

The html directory

The OA_HTML environment setting points to the html directory. The Oracle E-Business Suite HTML-based sign-on screen and Oracle HTML-based Applications HTML files are installed here. The html directory also contains other files used by the HTML-based products, such as JavaServer Page (JSP) files, Java scripts, XML files, and style sheets. Typically, the path will look like: <diskresource>/applmgr/apps/apps_st/comn/webapps/oacore/html.

Note: The META-INF and WEB-INF subdirectories were introduced in Release 12 to meet J2EE specifications.

The java directory

Release 12 introduces some significant changes to the locations in which the various types of Java files are stored. Rapid Install installs all Oracle E-Business Suite class files in the COMMON_TOP/classes directory, pointed to by the $JAVA_TOP environment variable. Zip and jar files are installed in the $COMMON_TOP/java/lib directory, pointed to by the $AF_JLIB environment variable (introduced with Release 12). The top-level Java directory, $COMMON_TOP/java, is pointed to by the $JAVA_BASE environment variable.

The util directory

The util directory contains the third-party utilities licensed to ship with Oracle E-Business Suite. These include, for example, the Java Runtime Environment (JRE), Java Development Kit (JDK), and the Zip utility.

The appl Directory

Oracle E-Business Suite files are stored in the <dbname>APPL directory, which is generally known as the APPL_TOP directory.


the picture is described in the document text

The APPL_TOP directory contains:
  • The core technology files and directories.
  • The product files and directories (for all products).
  • The main Oracle E-Business Suite environment file, called <CONTEXT_NAME>.env on UNIX, and <CONTEXT_NAME>.cmdon Windows.
  • The consolidated environment file, called APPS<CONTEXT_NAME>.env on UNIX, and APPS<CONTEXT_NAME>.cmd on Windows.
Note: CONTEXT_NAME is the Oracle Applications contextdescribed further in Chapter 5. Its default value is <SID>_<hostname>.

Rapid Install creates a directory tree for every Oracle E-Business Suite product in this APPL_TOP directory, whether licensed or not.

Warning: Regardless of registration status, all Oracle E-Business Suite products are installed in the database and the file system. Do not attempt to remove files for any unregistered products.

Rapid Install installs a new APPL_TOP directory when you upgrade. Rapid Install does not delete any existing product files from earlier releases, but unloads new product files into a new apps/apps_st/appl directory tree.
Each APPL_TOP directory is associated with a single Oracle E-Business Suite database. If you install both a Vision Demo system and a test system, Rapid Install will lay down two file systems, one for each of these Oracle E-Business Suite systems.

Product Directories

Each product has its own subdirectory under APPL_TOP. The subdirectories are named in accordance with the product's standard abbreviation, such as gl for Oracle General Ledger. Within each product directory is a subdirectory that is named using the base Oracle E-Business Suite release number, such as 12.0.0 for the initial Release 12. This directory contains the various subdirectories for the product files.

<PROD>_TOP Directory

The <APPL_TOP>/<prod>/<version> path is known as the product top directory (<PROD>_TOP), and its value is stored in the <PROD>_TOP environment variable.
For example, if APPL_TOP=/d01/oracle/prodapps, then the value contained in the AD_TOP environment variable is /d01/oracle/prodapps/ad/12.0.0, and the AD_TOP environment variable points to the <APPL_TOP>/ad/12.0.0 directory.

For the same APPL_TOP, the value of AU_TOP is /d01/oracle/prodapps/au/12.0.0, and the AU_TOP environment variable points to the <APPL_TOP>/au/12.0.0 directory. The same principle applies to all directories, apart for the admin directory.

Product Files

Each <PROD>_TOP directory, such as <APPL_TOP>/gl/12.0.0, contains subdirectories for product files. Product files include forms files, reports files, and files used to upgrade the database. To display data entry forms for Oracle General Ledger, for example, Oracle E-Business Suite accesses files in the forms subdirectory under the 12.0.0 directory.


the picture is described in the document text

Within each <PROD>_TOP directory, the product's files are grouped into subdirectories according to file type and function. The next figure expands the inset to show the full directory structure for gl.
                                  
                            Detail of gl Directory Structure
the picture is described in the document text


The following table summarizes product subdirectories and the types of files each one may contain.


 Applications Product Sub-directories and File Types file types
Subdirectory NameDescription
adminThe <PROD>_TOP/admin directory contains product-specific files used to upgrade each product. This is in distinction to the <APPL_TOP>/admin directory, which contains upgrade-related files for all products.
driverContains driver files (.drv files) used in upgrading.
importContains DataMerge files used to upgrade seed data.
odfContains object description files (.odf files) used to create tables and other database objects.
sqlContains SQL*Plus scripts used to upgrade data, and .pkh, .pkb, and .pls scripts to create PL/SQL stored procedures.
binContains concurrent programs, other C language programs and shell scripts for each product.
formsContains Oracle Forms generated runtime (.fmx) files (Oracle Forms form files).
helpContains the online help source files. Within this directory are subdirectories for each language installed.
htmlContains HTML, JavaScript, and JavaServer Page (JSP) files, primarily for HTML-based Applications products.
includeContains C language header (.h) files that my be linked with files in the lib directory. Not all products require this directory.
javaContains JAR files (Java Archive files) and Java dependency files. Copies of JAR files are also located in the $AF_JLIB directory.
libContains files used to relink concurrent programs with the Oracle server libraries. These files include:
  • object files (.o on UNIX, .OBJ on Windows), with compiled code specific to one of the product's programs.
  • library files (.a on UNIX, various including .DLL on Windows), with compiled code common to the product's programs.
  • make files (.mk) that specify how to create executables from object files and library files.
log and outContains output files for concurrent programs:
  • .mgr (master log file for concurrent manager)
  • .req (log file for a concurrent process)

Note that log and out subdirectories under a product directory are not used if you choose to set up a common directory for log and output files (FND_TOP is the only exception to this).
mediaContains .gif files used in the display of text and graphics on the desktop client.
mesgConcurrent programs also print messages in the log and output files. This directory contains the .msb files (binary message files used at runtime), and language-specific message files (such as a US.msb file for American English and a D.msb file for German). The files contain the forms messages that are displayed at the bottom of the screen or in popup windows.
patchUpdates to the data or data model utilize this directory to store the patch files.
reportsContains Oracle Reports platform-specific rdf binary report files for each product. Reports for each language are stored in subdirectories of the reports directory.
resourceContains .pll files (PL/SQL library files for Oracle Forms), which, like the plsql directory files, are later copied to AU_TOP.
sqlContains .sql files (SQL*Plus scripts) for concurrent processing.


File System of Oracle Applications 11i..

11i file system




Note: <dbname> is the name of your system determined through Rapid Install at the time of installation. For example, PROD.

• The <dbname>DATA or DATA_TOP directory is located on the database server machine, and contains the system tablespaces, redo log files, data tablespaces, index tablespaces, and database files.
• The <dbname>DB directory is located on the database server machine, and contains the ORACLE_HOME for the Oracle9i database.
• The <dbname>APPL or APPL_TOP directory contains the product directories and files for Oracle Applications.
• The <dbname>ORA directory contains the ORACLE_HOMEs for the Applications technology stack components.
• The <dbname>COMN or COMN_TOP (or COMMON_TOP) directory contains directories and files used across products.

The DATA Directory

The <dbname>DATA file system contains the data (.dbf) files of the Oracle database. Rapid Install installs the system, data, and index files in directories below several mount points on the database server. You can specify the directory names of the mount points on the database server during installation.

DB and ORA Directories

Oracle Applications supports employing an Applications database of one version, while linking Applications programs using the tools from a second or third version of the database. This multiple ORACLE_HOMEs configuration allows new features of the database to be supported, while maintaining compatibility with earlier releases. 

Release 11i utilizes three ORACLE_HOMEs:

• The 9.2.0 ORACLE_HOME (Applications database home) is located in the <dbname>DB directory. It contains the files needed for running and maintaining the Oracle Applications database.

• The 8.0.6 directory contains the ORACLE_HOME for the Developer 6i products (Forms, Reports, and Graphics). The product libraries in the 8.0.6 ORACLE_HOME are used to relink Oracle Applications executables.

• The iAS directory, also under the <dbname>ORA, contains the ORACLE_HOME for Oracle9i Application Server.

The COMN Directory

The <dbname>COMN or COMMON_TOP directory contains files used by many different Oracle Applications products, and which may also be used with third-party products.


The admin directory

The admin directory, under the COMMON_TOP directory, is the default location for the concurrent manager log and output directories. When the concurrent managers run Oracle Applications reports, they write the log files and temporary files to the log subdirectory of the admin directory, and the output files to the out subdirectory of the admin directory.


The install subdirectory of the admin directory contains scripts and log files used by Rapid Install. The scripts subdirectory of admin contains scripts used to start and stop services such as listeners and concurrent managers.

The html directory

The OA_HTML environment setting points to the html directory. The Oracle Applications HTML-based sign-on screen and Oracle HTML-based Applications HTML files are installed here. The html directory also contains other files used by the HTML-based products, such as JavaServer Page (JSP) files, Java scripts, XML files, and style sheets. Rapid Install and the AD utilities copy the HTML-based product files from
each <PROD>_TOP directory to subdirectories in the html directory.

The java directory

The JAVA_TOP environment setting points to the java directory. Rapid Install installs all Oracle Applications JAR files in the Oracle namespace of this JAVA_TOP directory. The java directory also holds third-party Java files used by Oracle Applications, as well as other zip files.

The portal directory

The portal directory contains the Rapid Install Portal files. The Rapid Install Portal is a web page that provides access to post-install tasks that may be necessary for your installation, plus server administration scripts, installation documentation, and online help. Using a browser, you can view the Rapid Install Portal after you run Rapid Install.

The temp directory

The temp directory is used for caching by some products such as Oracle Reports.

The util directory

The util directory contains the third-party utilities licensed to ship with Oracle Applications. These include, for example, the Java Runtime Environment (JRE), Java Development Kit (JDK), and the Zip utility.

The scripts directory

The scripts directory contains application tier control scripts such as adstrtal.sh and adstpall.sh, which are located in the <CONTEXT_NAME> subdirectory.

The APPL Directory

Oracle Applications files are stored in the <dbname>APPL directory, which is known as the APPL_TOP directory.


The APPL_TOP directory contains:
1. The core technology files and directories.
2. The product files and directories (for all products).
3. The main applications environment file, called .env on UNIX, and .cmd on Windows.
4. The consolidated environment file, called APPS.env on UNIX, and APPS.cmd on Windows.

PROD_TOP Directory

Each product has its own subdirectory under APPL_TOP, and the Oracle Applications base release is typically reflected in the subdirectory name. For Release 11i, the base release is
11.5.0.

The directory path for a particular product is defined by the value of the environment variable PROD_TOP, where PROD is the product schema name. For example, If the directory path to APPL_TOP is /d01/prodappl, the paths to these product directories would be specified in the .env file as follows:

• APPL_TOP=/d01/prodappl
• AU_TOP= /d01/prodappl/au/11.5.0
• FND_TOP = /d01/prodappl/fnd/11.5.0
• INV_TOP= /d01/prodappl/inv/11.5.0

All Oracle Applications products, regardless of license status, are installed in the database and the file system. Files for unlicensed products should not be removed. Conversely, multiple releases and product versions must not be installed under a single APPL_TOP directory.

The same principle applies to all directories, apart for the admin directory.

Product Directories
Each Oracle Applications product directory contains numerous subdirectories, which are used to group the various types of file used by the product. Not all products have all the sub-directories shown on the slide. There may also be differences depending on installation choices.



Additional Language Subdirectories
Translated forms files, reports files, and installation scripts are all stored in their own language specific directories. These directories are identified by a language directory code.

For example, all forms files located under the US directory are in American English, while all forms files located under the AR directory are in Arabic.

Message files are not stored in language-specific directories. Instead, message files are named according to the language of the messages they contain. For example, AR.msb is a file containing messages translated to Arabic.



AU Directory
Applications Utilities (AU) are product files that are consolidated in a single location for optimal processing.

These files include:
• PL/SQL libraries used by Oracle Reports, in the PLSQL subdirectory.
• PL/SQL libraries used by Oracle Forms, in the resource subdirectory.
• Oracle Forms source files, in the forms subdirectory.
• A copy of all Java files used by JInitiator when regenerating the desktop client JAR files, in the java subdirectory.
• Certain reports needed by products such as Discoverer, in the reports subdirectory.



Common Components Directory - COMMON_TOP

The db_nameCOMN or COMMON_TOP directory contains files used by many different Oracle Applications products, and which may also be used with third-party products.

The COMMON_TOP/admin directory is the default location for the concurrent manager log and output directories. When the concurrent managers run Oracle Applications reports, they write the log files and temporary files to the log subdirectory of the admin directory (COMMON_TOP/admin/log) and the output files to the out subdirectory of the admin directory (COMMON_TOP/admin/out).

By default, the top-level directories for both Java (JAVA_TOP) and HTML (OAH_TOP) are both under COMMON_TOP.




Applications Technology Stack Directory - (db_Name)ORA
Oracle Applications supports employing an Applications database of one version, while linking Applications programs using the tools from a second or third version of the database.

This multiple ORACLE_HOMEs configuration allows new features of the database to be supported, while maintaining compatibility with earlier releases.

Release 11i utilizes two ORACLE_HOMEs under the (db_Home)ORA directory:
• The 8.0.6 directory contains the ORACLE_HOME for the Developer 6i products (Forms, Reports, and Graphics). The product libraries in the 8.0.6 ORACLE_HOME are used to relink Oracle Applications executables. This is the base Oracle home, which contains SQL*Plus and other database utilities used by Auto Patch.
• The iAS directory contains the ORACLE_HOME for Oracle9i Application Server, which includes the Oracle HTTP server.



Database Technology Stack Directory - (DB_NAME)DB

The database server is located in its own directory structure, with its own ORACLE_HOME.The 9.2.0 ORACLE_HOME (Applications database home) is located in the DB directory. It contains the files needed to run and maintain the Oracle Applications database.





Wednesday, May 21, 2014

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

.ssoIt 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 “{}” “;”