odf

10
What is the ODF Comparison Utility and how do I use it? Answer -------- Each Oracle Applications product is made up of one or more building blocks. For example, Journal Entry is one building block of Oracle General Ledger. Each building block has an ODF (Object Description File) that describes its tables, indexes, views and sequences. Several phases of Autoinstall use the ODF Comparison Utility (adodfcmp) to create the needed objects. Usage: adodfcmp keyword=value [,keyword=value,...] Valid Keywords -------------- odffile - Filename of ODF file that adodfcmp should read userid - ORACLE username/password to be compared with ODF file changedb - Change database to eliminate the differences? (Default No) logfile - File name of log file (Default adodfcmp.log) sizingfactor - Sizing factor (Default 100) tspace - Tablespace to store tables indextspace - Tablespace to store indexes mode - What do you want to compare? (Default objects) touser - Userid to grant to (Default NOBODY) parfile - Filename of a parameter file (if any) (Default NONE) listextra - Report extra objects? (Default No)

Upload: api-3736000

Post on 10-Apr-2015

403 views

Category:

Documents


1 download

TRANSCRIPT

Page 1: Odf

What is the ODF Comparison Utility and how do I use it?

Answer--------Each Oracle Applications product is made up of one or more building blocks. For example, Journal Entry is one building block of Oracle General Ledger. Each building block has an ODF (Object Description File) that describes its tables, indexes, views and sequences. Several phases of Autoinstall use the ODF Comparison Utility (adodfcmp) to create the needed objects.

Usage: adodfcmp keyword=value [,keyword=value,...] Valid Keywords -------------- odffile - Filename of ODF file that adodfcmp should read userid - ORACLE username/password to be compared with ODF file changedb - Change database to eliminate the differences? (Default No) logfile - File name of log file (Default adodfcmp.log) sizingfactor - Sizing factor (Default 100) tspace - Tablespace to store tables indextspace - Tablespace to store indexes mode - What do you want to compare? (Default objects) touser - Userid to grant to (Default NOBODY) parfile - Filename of a parameter file (if any) (Default NONE) listextra - Report extra objects? (Default No) listmatch - Report matching objects? (Default Yes) listmissing - Report missing objects? (Default Yes) batchsize - How many rows to update at a time (Default 1000) oldviews - Rename, drop or replace existing views (Default rename) You can specify command-line parameters either by position or by keywords. To run the command, first change your current directory to the locationof the .odf file. This is located in the install/odf directory under the product top directories.

Example ------- cd $FND_TOP/install/odf

Page 2: Odf

$ adodfcmp odffile=afform.odf userid=applsys/fnd changedb=yes

References

THE ODF COMPARISON UTILITY

Changes in ODFCMP for Release 10.

o Introduction

The ODF Comparison utility or ODFCMP as it was known in release 9, is used to compare objects in a database against an Object Description File (.odf). The ODF Comparison Utility reports:

o Objects missing from the account (ORACLE username).

o Extra objects in the account (not listed in the ODF file).

o Detailed differences between an object in the account and an object of the same name in the file.

The ODF Comparison Utility also reports and optionally executes the SQL statements to fix these differences. You can review the SQL statements before actually executing them.

The AutoInstall program uses ODF Comparison to install and upgrade Applications.

 XDF: "XDF is a common scientific data format based on XML and general mathematical principles that can be used throughout the scientific disciplines. It includes these key features: hierarchical data structures, any dimensional arrays merged with coordinate information, high dimensional tables merged with field information, variable resolution, easy wrapping of existing data, user specified coordinate systems, searchable ASCII meta-data, and extensibility to new features/data formats. [As of 2003-06] the XDF project supported two versions of XDF: a 'stable' and 'development' version..." "An XDF document contains N-dimensional arrays of data with associated spatial information. It is designed to be both an interchange format for scientific data and to be of archival quality. Multidimensional tables and scalar or vector fields are represented in a consistent way and become thoroughly self describing. Axial information is well described so that the space in which each part of the data structure resides is fully described. This means that XDF provides a consistent way to hold spectra with their wavelength scales, images with coordinate axes, vector fields with unitDirection, data

Page 3: Odf

cubes in complicated spaces, tables with column headers, and series of tables with each table having a unique name."

What is the .odf file, what its work?    Odf stands for Object Description Files.   These files are used to create tables & other database objects.   You can find these odf files under each Product_top/patch/115/odf.   You can run this odf file using the command line utility: adodfcmp.

   CONCEPTS OF FNDLOADER:  The FNDLOAD utility also know as the Generic loader in Oracle Applications is a concurrent program that can move data across applications instances using database and text file representations.The FNDLOAD downloads the data from the database using a oracle predefined configuration file (.lct) and stores the data in a converted data file (.ldt).Similarly while using FNDLOAD to upload data, the loader uploads the data from the data file created by the previous download based on the configuration file.The FNDLOAD does the download and upload based on the instructions given the configuration files (.lct), these are predefined by oracle and can be located at $FND_TOP/patch/115/import.  Oracle currently supports the migration of the following types of data using FNDLOADPrinters / Print queues / Executables Printers / Print queues / Executables. Roles / Responsibilities / Forms Roles / Responsibilities / Forms. Menus / Users / Request Sets Menus / Users / Request Sets. Request Groups / Request Queues Request Groups / Request Queues. Work shifts / Programs / Libraries Work shifts / Programs / Libraries. Attachments / Help Files Attachments / Help Files. Mime Types Mime Types. Security Information.

ADSPLICE: 

Adsplice is the one of the adutility, By using this we can register the offcycle products that are released after basereleses.( for example if we are working in 11.5.9 then if any new product is interduced in 11.5.10 by that time we can register the new product from 11.5.9 to 11.5.10)

Adsplice logfile is located under APPL_TOP/admin/SID

 When you run adsplice, accept the defaults and you will see lines like the following:

Page 4: Odf

  Please enter the directory where your AD Splicer control file is located.  The default directory is [/lv04/apps/oracle/apps/vis10g/appl_mgr/admin] : /lv04/ apps/oracle/apps/vis10g/appl_mgr/admin  Please enter the name of your AD Splicer control file [newprods.txt] : newprods. txt   Processing file /lv04/apps/oracle/apps/vis10g/appl_mgr/admin/newprods.txt... Loading information for product 'izu'...  Warning: Because the database is in new tablespace mode, AD Splicer is ignoring  the tablespace settings in your control file!  Successfully read file /lv04/apps/oracle/apps/vis10g/appl_mgr/admin/newprods.txt .  Verifying localizations...  Validating inter-product dependency information...  Re-organizing product information lists...   Adding new languages into FND_LANGUAGES...  ...  Saving module actions...done.  Saving product actions...done.  Making product top directory for product "izu"... Directory will be /lv04/apps/oracle/apps/vis10g/appl_mgr/izu/11.5.0  Making directory "log" for product "izu"... Making directory "out" for product "izu"... Making directory "mesg" for product "izu"... Making directory "sql" for product "izu"... Creating stub file "sql/IZUNLINS.sql" for product "izu"... Making directory "admin/sql" for product "izu"... Creating stub file "admin/sql/IZUNLADD.sql" for product "izu"... Making directory "admin/driver" for product "izu"...

Page 5: Odf

 Creating stub file "admin/driver/izucon.drv" for product "izu"... Creating stub file "admin/driver/izuseq.drv" for product "izu"... Creating stub file "admin/driver/izutab.drv" for product "izu"... Creating stub file "admin/driver/izutbm.drv" for product "izu"... Creating stub file "admin/driver/izuos.drv" for product "izu"... Creating stub file "admin/driver/izupls.drv" for product "izu"... Creating stub file "admin/driver/izuvw.drv" for product "izu"... Creating stub file "admin/driver/izuplb.drv" for product "izu"... Creating stub file "admin/driver/izupdt.drv" for product "izu"... Creating stub file "admin/driver/izudat.drv" for product "izu"... Creating stub file "admin/driver/izuupg.drv" for product "izu"... Creating stub file "admin/driver/izudfr.drv" for product "izu"... Creating stub file "admin/driver/izuen.drv" for product "izu"... Creating stub file "admin/driver/izudep.drv" for product "izu"...   Do you wish to regenerate your environment file [Yes] ? Yes  Checking if AutoConfig is enabled.... 

 Running AutoConfig on: All products ...     

 ADSPLICE USE ---------------------   You are now ready to run the ADSPLICE utility from the command line. Make sure you have changed directory to the $APPL_TOP/admin directory where your newprods.txt file was created.   On UNIX, log on as the applmgr user and make sure your applsys.env or  other applications environment file is sourced. Change directory to your $APPL_TOP/admin and run adsplice from the command line:    %> adsplice   On NT, open an MS-DOS window, change directory to the %APPL_TOP%\admin  directory, source your adovars.env or your applications environment file and run adsplice from the DOS command line:    d:\> adsplice     You will be asked a series of questions to verify your environment. When you

Page 6: Odf

 are asked for the name of the configuration file, give it the name of the  file you created above.    ADSPLICE will then run a set of scripts to add the new schema to the database and the $APPL_TOP. Scripts are also run to give the new user privileges on the database and to give the APPS and APPLSYS users privileges on the new product's  schema.   After the database and file system are updated to create the new product schema  and product top, you will be asked some additional questions about the  configuration of your system like server names, port numbers, etc.    You will be asked to regenerate your environment file. By doing this, the $APPLFULL environment variable is updated to indicate that you have a new product installed. Also, a new environment variable is created for the product.   When ADSPLICE finishes, this Oracle Applications product will be an integrated  piece of Oracle Applications and other AD Utilities can be used to apply patches, generate forms, and maintain the files.   You will need to run ADSPLICE on every APPL_TOP for this Oracle Applications  system. Run ADSPLICE on the admin server first.

FNDLOAD:

FNDLOAD is a concurrent program that can move oracleapplication data between database and textfile representation.

The fndload download the data from database using an oracle predefined configuration file (.lct) and stores the data in converted datafile (.ldt).

This fndload executable is located under FND_TOP/bin

Syntax:FNDLOAD [username/password] O Y [mode] [configuration file] [target datafile] [object type] [object identifier]

PLL files are the binary library modules. This file is portable across systems (but be aware of the inclusion or exclusion of path information that may make the module unportable - see a discussion of this later in the chapter). The file is created when you save the library in the Designer. It contains both the source code from the design session and the compiled executable code needed at runtime. This is the file you attach to a form module.

Page 7: Odf

CPU:Critical Patch Updates deliver critical security-related fixes for all of your Oracle technology stack components, including patches for E-Business Suite Release 11i and 12. Apps sysadmins need to apply all of the released CPUs to their E-Business Suite environment to get all of the latest security-related fixes.