Stat 7.0 - System Administration Guide

Table 19. Init.ora recommended parameters settings
Name	Recommended
session_cached_cursors	150
sort_area_size	1048576
optimizer_index_cost_adj	35
optimizer_index_caching	90
pga_aggregate_target	25165824
workarea_size_policy	AUTO
open_cursors	300

Run the following command on a weekly basis:

exec dbms_stats.gather_schema_stats(ownname=>'STAT', CASCADE => TRUE);

MSS SQL Server Database Tuning

MSS SQL Server is basically a self tuning system.

Be sure there is adequate space for Transaction logs based on your backup schedule

TempDB should be a minimum 50M for each database on the server, including the master, model, etc). e.g. if there are 6 databases, the tempdb should be, at minimum, 300M in size.

Run the following on a weekly basis:

Execute STAT_UPDATESTATS

Appendix: Oracle Applications File Type Directory

This appendix documents the directories Stat uses for retrieving an object list, archiving an object, and migrating an object for all the proprietary Oracle Applications file object types. Proprietary Oracle Applications file types require that the user select a product and language before Stat retrieves a list of objects. These attributes are used to determine the archive and migration locations.

Notation:

•

$prod is used to represent the selected product

•

$prodTop is used to represent the directory for the selected product

•

$lang is used to represent the selected language.

Oracle follows a precise file structure convention for locating files for specific types. Many sites do not adhere to the convention strictly for their custom object types. Stat provides flexibility where feasible and useful to accommodate common conventions used by many sites for storing custom files. For example, Oracle stores all FMB files in $AU_TOP/forms/<lang>. Many sites do not store custom FMB files in $AU_TOP, nor do they create a sub-directory for each language. Stat allows custom FMBs to be stored in $prodTop/forms directory.

An Oracle Applications environment can be partitioned across several physical servers. Logically, there are four servers: Web Server, Forms Server, Concurrent Manager, and Database. Objects for each object type are stored on one or more of these logical servers. The table also identifies the server type.

Table 20.
Object Type: Exe File (All Servers)
Object List	Include all files in: - $prodTop/bin/*
Object Archive	$prodTop/bin
Migration Destination	$prodTop/bin

Table 21.
Object Type: Menu File (Forms Server only)
Object List	Include all files in: $prodTop/resource/$lang/*.mmb
Object Archive	$prodTop/resource/$lang
Migration Destination	$prodTop/resource/$lang NOTE: The MMX file is always generated in $prodTop/resource/$lang (not $AU_TOP/resource).

Table 22.
Object Type: Form File (Forms Server only)
Object List	Consider possible forms in: - Registered Form - FMX files in $prodTop/forms/$lang Include if FMB file exists in $AU_TOP/forms/$lang If $prod is custom Include all FMBs in $prodTop/forms/$lang Include all FMBs in $prodTop/forms EndIf NOTE: Stat does not return any objects if selected product is AU*
Object Archive	If $prod is custom Consider following directories using first where file is found - $prodTop/forms/$lang - $propTop/forms - $AU_TOP/forms/$lang If file not found, throw exception. Else $prodTop/forms/$lang EndIf
Migration Destination	If $prod is custom Consider following directories using first where file is found - $prodTop/forms/$lang - $propTop/forms - $AU_TOP/forms/$lang If file not found, consider following directories using first that exists - $prodTop/forms/$lang - $propTop/forms If directory not found, throw exception. Else $prodTop/forms/$lang EndIf NOTE: The FMX file is always generated in $prodTop/forms/$lang

Table 23.
Object Type: Form Library File (Forms Server only)
Object List	Include all files in: - $prodTop/resource/*.pll NOTE: Since Oracle stores all PLLs in $AU_TOP/resource, no files will typically be returned with standard products except for AU. However, Stat searches the product top to allow custom PLLs to be stored with the custom product top.
Object Archive	$prodTop/resource
Migration Destination	$prodTop/resource NOTE: The PLX file is always generated in $prodTop/resource (not $AU_TOP/resource). This requires FORMS60_PATH to include $prodTop/resource if custom PLLs are not stored in $AU_TOP/resource.

Table 24.
Object Type: Oracle Workflow File (Database Server only)
Object List	If $prod is custom Include all files in: - $prodTop/admin/import/$lang/.wft - $prodTop/admin/import/.wft - $prodTop/admin/$lang/.wft - $prodTop/admin/.wft Else Include all files in: - $prodTop/patch/115/import/$lang/.wft - $prodTop/patch/115/import/.wft - $prodTop/admin/import/$lang/.wft - $prodTop/admin/import/.wft EndIf
Object Archive	If $prod is custom Consider following directories using first where file is found - $prodTop/admin/import/$lang - $prodTop/admin/import - $prodTop/admin/$lang - $prodTop/admin If file not found, throw exception. Else Consider following directories using first where file is found - $prodTop/patch/115/import/$lang - $prodTop/patch/115/import - $prodTop/admin/import/$lang - $prodTop/admin/import EndIf
Migration Destination	If $prod is custom Consider following directories using first where file is found - $prodTop/admin/import/$lang - $prodTop/admin/import - $prodTop/admin/$lang - $prodTop/admin If file not found, consider following directories using first that exists - $prodTop/admin/import/$lang - $prodTop/admin/import - $prodTop/admin/$lang - $prodTop/admin If directory not found, throw exception. Else Consider following directories using first where file is found - $prodTop/patch/115/import/$lang - $prodTop/patch/115/import - $prodTop/admin/import/$lang - $prodTop/admin/import If file not found, consider following directories using first that exists - $prodTop/patch/115/import/$lang - $prodTop/patch/115/import - $prodTop/admin/import/$lang - $prodTop/admin/import If directory not found, throw exception. EndIf NOTE: The WFT file is always loaded into the database using WFLOAD NOTE: For R12.2 environments, the WFT file is loaded into the Run Edition of the database when migrating to Run or Both Editions and is loaded into Patch Edition of the database when migrating to Patch Edition. Note that you need to have the ‘OraApp Migration to Run Edition’ right to migrate to Run Edition.

Table 25.
Object Type: PKB (PL/SQL Body) File (Database Server only)
Object List	Include all files in: - $prodTop/admin/sql/.pkb,.plb $prodTop/patch/115/sql/.pkb, .plb
Object Archive	Consider following directories using first where file is found - $prodTop/patch/115/sql - $prodTop/admin/sql
Migration Destination	If $prodTop/patch/115/sql directory exists - $prodTop/patch/115/sql Else - $prodTop/admin/sql EndIf NOTE: The file is always executed in the database using sqlplus NOTE: For R12.2 environments, the file is executed in the Run Edition of the database when migrating to Run or Both Editions and is executed in Patch Edition of the database when migrating to Patch Edition. Note that you need to have the ‘OraApp Migration to Run Edition’ right to migrate to Run Edition.

Table 26.
Object Type: PKH (PL/SQL Body) File (Database Server only) NOTE: This object type looks for files with both .pkh and .pks extensions.
Object List	Include all files in: - $prodTop/admin/sql/(.pkh, .pks) $prodTop/patch/115/sql/(.pkh, .pks)
Object Archive	Consider following directories using first where file is found - $prodTop/patch/115/sql - $prodTop/admin/sql
Migration Destination	If $prodTop/patch/115/sql directory exists - $prodTop/patch/115/sql Else - $prodTop/admin/sql EndIf NOTE: The file is always executed in the database using sqlplus. NOTE: For R12.2 environments, the file is executed in the Run Edition of the database when migrating to Run or Both Editions and is executed in Patch Edition of the database when migrating to Patch Edition. Note that you need to have the ‘OraApp Migration to Run Edition’ right to migrate to Run Edition.

Table 27.
Object Type: PL/SQL File (Database Server only)
Object List	Include all files in: - $prodTop/admin/sql/.pls if exists, otherwise $prodTop/sql/.pls - $prodTop/patch/115/sql/*.pls NOTE: All standard products include the $prodTop/admin/sql directory. Stat checks the $prodTop/sql directory to accommodate sites that store their custom PLS files in this directory
Object Archive	Consider following directories using first where file is found - $prodTop/patch/115/sql/ $prodTop/admin/sql if exists, otherwise $prodTop/sql
Migration Destination	If $prodTop/patch/115/sql directory exists - $prodTop/patch/115/sql Else if $prodTop/admin/sql directory exists - $prodTop/admin/sql Else - $prodTop/sql EndIf NOTE: The file is always executed in the database using sqlplus NOTE: For R12.2 environments, the file is executed in the Run Edition of the database when migrating to Run or Both Editions and is executed in Patch Edition of the database when migrating to Patch Edition

Table 28.
Object Type: Report File (Concurrent Manager Server only)
Object List	Include all files in: - $prodTop/reports/$lang/.rdf if exists, otherwise $prodTop/reports/.rdf NOTE: Stat uses the value of $APPLREP instead of “reports” for the subdirectory. This environment variable is always set to “reports
Object Archive	$prodTop/reports/$lang if exists, otherwise $prodTop/reports
Migration Destination	$prodTop/reports/$lang if exists, otherwise $prodTop/reports NOTE: The file is always compiled.

Table 29.
Object Type: SQL Report (Concurrent Manager Server only)
Object List	$prodTop/sql/*.sql
Object Archive	$prodTop/sql
Migration Destination	$prodTop/sql NOTE: The file is never executed in the database.

Table 30.
Object Type: SQL Script (Database Server only)
Object List	Include all files in: - $prodTop/admin/sql/.sql - $prodTop/patch/115/sql/.sql
Object Archive	Consider following directories using first where file is found - $prodTop/patch/115/sql - $prodTop/admin/sql
Migration Destination	If $prodTop/patch/115/sql directory exists - $prodTop/patch/115/sql Else - $prodTop/admin/sql EndIf NOTE: The file is always executed in the database using sqlplus. NOTE: For R12.2 environments, the file is executed in the Run Edition of the database when migrating to Run or Both Editions and is executed in Patch Edition of the database when migrating to Patch Edition. Note that you need to have the ‘OraApp Migration to Run Edition’ right to migrate to Run Edition.

Table 31.
Object Type: OAF - OA Component XML File (Database Server only)
Object List	Include all .xml files in: MDS Repository for a specific $prodTop
Object Archive	XMLExporter is used to extract the xml file from MDS Repository.
Migration Destination	XMLImporter is used to deploy the xml file to MDS Repository of target NOTE: For R12.2 environments, the xml file is loaded into the Run Edition of the database when migrating to Run or Both Editions and is loaded into Patch Edition of the database when migrating to Patch Edition. Note that you need to have the ‘OraApp Migration to Run Edition’ right to migrate to Run Edition.

Table 32.
Object Type: OAF - OA Component Class File (Web Server only)
Object List	Include all seeded files in: $JAVA_TOP/oracle/apps/$ProdTop/<component>/webui/.class And any custom files in: $JAVA_TOP/$mycompany/oracle/apps/$ProdTop/<component>/<layer type>/<layer value>/webui/.class
Object Archive	Consider following directories -$JAVA_TOP/oracle/apps/$ProdTop/<component>/webui -$JAVA_TOP/$mycompany/oracle/apps/$ProdTop/<component>/<layer type>/<layer value>/webui
Migration Destination	Seeded files are migrated to: -$JAVA_TOP/oracle/apps/$ProdTop/<component>/webui Custom files are migrated to: -$JAVA_TOP/$mycompany/oracle/apps/$ProdTop/<component>/<layer type>/<layer value>/webui NOTE: Custom files could be placed under a directory other than $JAVA_TOP, as long as that directory is on the classpath.

Table 33.
Object Type: OAF - OA Component Java File (Web Server only)
Object List	Include all seeded files in: $JAVA_TOP/oracle/apps/$ProdTop/<component>/webui/.java And any custom files in: $JAVA_TOP/$mycompany/oracle/apps/$ProdTop/<component>/<layer type>/<layer value>/webui/.java
Object Archive	Consider following directories -$JAVA_TOP/oracle/apps/$ProdTop/<component>/webui -$JAVA_TOP/$mycompany/oracle/apps/$ProdTop/<component>/<layer type>/<layer value>/webui
Migration Destination	Seeded files are migrated to: -$JAVA_TOP/oracle/apps/$ProdTop/<component>/webui Custom files are migrated to: -$JAVA_TOP/$mycompany/oracle/apps/$ProdTop/<component>/<layer type>/<layer value>/webui NOTE: Custom files could be placed under a directory other than $JAVA_TOP, as long as that directory is on the classpath.

Table 34.
Object Type: OAF - BC4J Component XML File (Web Server only)
Object List	Include all seeded files in: $JAVA_TOP/oracle/apps/$ProdTop/<component>/server/.xml And any custom files in: $JAVA_TOP/$mycompany/oracle/apps/$ProdTop/<component>/<layer type>/<layer value>/server/.xml
Object Archive	Consider following directories: -$JAVA_TOP/oracle/apps/$ProdTop/<component>/server -$JAVA_TOP/$mycompany/oracle/apps/$ProdTop/<component>/<layer type>/<layer value>/server
Migration Destination	Seeded files are migrated to: -$JAVA_TOP/oracle/apps/$ProdTop/<component>/server Custom files are migrated to: -$JAVA_TOP/$mycompany/oracle/apps/$ProdTop/<component>/<layer type>/<layer value>/server NOTE: Custom files could be placed under a directory other than $JAVA_TOP, as long as that directory is on the classpath.

Table 35.
Object Type: OAF - BC4J Component Class File (Web Server only)
Object List	Include all seeded files in: - $JAVA_TOP/oracle/apps/$ProdTop/<component>/server/.class - $JAVA_TOP/oracle/apps/$ProdTop/<component>/<all except webui>/.class And any custom files in: - $JAVA_TOP/$mycompany/oracle/apps/$ProdTop/<component>/<layer type>/<layer value>/server/.class - $JAVA_TOP/$mycompany/oracle/apps/$ProdTop/<component>/<layer type>/<layer value>/<all except webui>/.class
Object Archive	Consider following directories -$JAVA_TOP/oracle/apps/$ProdTop/<component>/server -$JAVA_TOP/$mycompany/oracle/apps/$ProdTop/<component>/<layer type>/<layer value>/server -$JAVA_TOP/oracle/apps/$ProdTop/<component>/<all except webui> -$JAVA_TOP/$mycompany/oracle/apps/$ProdTop/<component>/<layer type>/<layer value>/<all except webui>
Migration Destination	Seeded files are migrated to: -$JAVA_TOP/oracle/apps/$ProdTop/<component>/<all except webui> -$JAVA_TOP/oracle/apps/$ProdTop/<component>/<all except webui> Custom files are migrated to: -$JAVA_TOP/$mycompany/oracle/apps/$ProdTop/<component>/<layer type>/<layer value>/server NOTE: Custom files could be placed under a directory other than $JAVA_TOP, as long as that directory is on the classpath.

Table 36.
Object Type: OAF - BC4J Component Java File (Web Server only)
Object List	Include all seeded files in: - $JAVA_TOP/oracle/apps/$ProdTop/<component>/server/.java - $JAVA_TOP/oracle/apps/$ProdTop/<component>/<all except webui>/.java And any custom files in: - $JAVA_TOP/$mycompany/oracle/apps/$ProdTop/<component>/<layer type>/<layer value>/server/.java - $JAVA_TOP/$mycompany/oracle/apps/$ProdTop/<component>/<layer type>/<layer value>/<all except webui>/.java
Object Archive	Consider following directories -$JAVA_TOP/oracle/apps/$ProdTop/<component>/server -$JAVA_TOP/$mycompany/oracle/apps/$ProdTop/<component>/<layer type>/<layer value>/server -$JAVA_TOP/oracle/apps/$ProdTop/<component>/<all except webui> -$JAVA_TOP/$mycompany/oracle/apps/$ProdTop/<component>/<layer type>/<layer value>/<all except webui>
Migration Destination	Seeded files are migrated to: -$JAVA_TOP/oracle/apps/$ProdTop/<component>/<all except webui> -$JAVA_TOP/oracle/apps/$ProdTop/<component>/<all except webui> Custom files are migrated to: -$JAVA_TOP/$mycompany/oracle/apps/$ProdTop/<component>/<layer type>/<layer value>/server NOTE: Custom files could be placed under a directory other than $JAVA_TOP, as long as that directory is on the classpath.

Table 37.
Object Type: XDO XML Publisher Template Files (Database Server only)
Object List	Include all templates for a specific $prodTop from XDO_LOB table where LOB_TYPE is one of TEMPLATE, TEMPLATE_SOURCE, XML_SCHEMA, XML_SAMPLE and DATA_TEMPLATE
Object Archive	XDOLoader is used to extract the template from XDO_LOB table
Migration Destination	XDOLoader is used to deploy the template to XDO_LOB table of target NOTE: For R12.2 environments, the template file is loaded into the Run Edition of the database when migrating to Run or Both Editions and is loaded into Patch Edition of the database when migrating to Patch Edition. Note that you need to have the ‘OraApp Migration to Run Edition’ right to migrate to Run Edition.

Table 38.
Object Type: XDO XML Publisher Translations (Database Server only)
Object List	Include all translations for a specific $prodTop from XDO_LOB table where LOB_TYPE is XDO_TRSL
Object Archive	XLIFFLoader is used to extract the translation from XDO_LOB table
Migration Destination	XLIFFLoader is used to deploy the translation to XDO_LOB table of target environment NOTE: For R12.2 environments, the template file is loaded into the Run Edition of the database when migrating to Run or Both Editions and is loaded into Patch Edition of the database when migrating to Patch Edition. Note that you need to have the ‘OraApp Migration to Run Edition’ right to migrate to Run Edition.

Table 39.
Object Type: XDO XML Publisher DS by Template (Database Server only)
Object List	Include all active data sources from XDO_DS_DEFINITIONS
Object Archive	FNDLoad is used to extract the data source from XDO_DS_DEFINITIONS table
Migration Destination	FNDLoad is used to deploy the data source to XDO_DS_DEFINITIONS table of target environment

Table 40.

Object Type: XDF Editioning Views (R12.2 and Database Server only)

Object List

Include all Editioning Views from DBA_EDITIONING_VIEWS

Object Archive

xdfgen.pl is used to extract the xdf file from the Run Edition

Migration Destination

-xdf file is copied to

If $prodTop/patch/115/xdf directory exists

-$prodTop/patch/115/xdf

Else if $prodTop/admin directory exists

-$prodTop/admin

EndIf

-xdfcmp.pl is used to deploy the xdf file to

the target environment

NOTE: When migrating xdf files to Run or Both Editions of a target environment:

•

If there is an active Patch Cycle in effect, Stat deploys the xdf file to the file system and returns with a warning.

•

If there is no Patch Cycle in effect, Stat deploys the xdf file to the file system and loads it to the Run Edition of the environment.

When migrating xdf files to Patch Edition of a target environment:

•

If there is an active Patch Cycle in effect, Stat deploys the xdf file to the file system and loads it to the Patch Edition of the environment.

•

If there is no Patch Cycle in effect, Stat deploys the xdf file to the file system and returns with a warning.

Table 41.
Object Type: XDF Editioning View Files (R12.2 and Database Server only) NOTE: This object type is available to users in case the generated xdf file using the xdfgen.pl needs to be modified before deployment to a target environment.
Object List	Include all files in: - $prodTop/patch/115/xdf/*.xdf
Object Archive	$prodTop/patch/115/xdf
Migration Destination	If $prodTop/patch/115/xdf directory exists - $prodTop/patch/115/xdf and xdfcmp.pl is used to deploy the xdf file to the target environment

Seleziona il prodotto:

Per una maggiore efficacia, compilare l'Obiettivo della chat:

Soluzioni consigliate per il problema

Stat 7.0 - System Administration Guide

Appendix: Database Tuning

Oracle Database Instance Tuning

MSS SQL Server Database Tuning

Appendix: Oracle Applications File Type Directory