R12 d49656 gc10-apps dba 19
•Als PPT, PDF herunterladen•
0 gefällt mir•657 views
Oracle Applications, Oracle Database, D49656, Oracle Applications DBA
![Objectives ,[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Andere mochten auch
Andere mochten auch (10)
Ă„hnlich wie R12 d49656 gc10-apps dba 19
Ă„hnlich wie R12 d49656 gc10-apps dba 19 (20)
KĂĽrzlich hochgeladen
KĂĽrzlich hochgeladen (20)
R12 d49656 gc10-apps dba 19
- 1. Configuration Utilities AD Utilities Topics
- 8. Editing newprods.txt The schema for product data objects oracle_schema The sizing factor used when creating tables and indexes sizing_factor base_product_top product Status The product being spliced The base directory for product files Description
- 12. File Character Set Conversion (adncnv) Path and filename for the converted file <destination file> New character set for the converted file <dest char set> <source char set> <source file> Parameter Path and filename of the file to convert Current character set Description
Hinweis der Redaktion
- ILT Schedule: Timing Topic 15 minutes Lecture 30 minutes Practice 45 minutes Total
- <Course name> <Lesson number> -
- <Course name> <Lesson number> -
- <Course name> <Lesson number> - AD Splicer AD Splicer performs the same product registration function as License Manager. However, it registers off-cycle products — those that are released between maintenance packs — as active in your system. This process of &quot;splicing&quot; modifies the APPL_TOP and database so that AutoPatch and AD Administration recognize the off-cycle product as a valid product for a specific release. Patches that contain off-cycle products also contain the control files that AD Splicer needs to register the product. The patch also contains a readme file that describes how to install the new product(s).
- <Course name> <Lesson number> - AD Splicer Product tablespaces for the new off-cycle products must be created before running AD Splicer. AD Splicer automatically determines the correct tablespaces in the Oracle Applications Tablespace Model (OATM).
- <Course name> <Lesson number> - AD Splicer Control Files Off-cycle products are generally released as patches. All product files and control files necessary to splice in the product are included in the patch. There is one product configuration file, called newprods.txt. The product configuration file must be edited for your specific system before the off-cycle product can be properly spliced. Note: The product definition files must not be altered. There are two product definition files per off-cycle product. They are <prod>prod.txt: which contains language-independent information for product <prod> <prod>terr.txt: which contains language-dependent information for product <prod> <prod> represents the product abbreviation for an Applications product. For example GL for General Ledger and PO for Purchasing. The AD Splicer control files must copied from the patch to the APPL_TOP/admin directory.
- <Course name> <Lesson number> - Editing newprods.txt Each spliced product in newprods.txt has an entry as shown in the slide. Release 12 uses the OATM (Oracle Applications Tablespace Model),so you do not need to supply AD splicer with parameters for identifying tablespaces This example shows the ZSA product. This file needs to be edited for your specific environment. Parameters that may need editing are: base_product_top – the default value of *APPL_TOP* will place the product files under APPL_TOP. main_tspace – the default value of *Product_Name*D must be changed to the product’s tablespace name. For example, ZSAD for the ZSA product. index_tspace – the default value of *Product_Name*X must be changed to the product’s index tablespace name. For example, ZSAX for the ZSA product. temp_tspace – the default value of *Temporary_Tablespace* must be changed to the temporary tablespace name. For example, TEMP. default_tspace – the default value of *Product_Name*D must be changed to the product’s tablespace name. For example, ZSAD for the ZSA product. Instructor Note : AD Splicer connects to the database and identifies the registered tablespaces to determine whether the system uses OATM.
- <Course name> <Lesson number> - Editing newprods.txt This table defines each of the parameters in the newprods.txt file. The product entry is the product abbreviation of the product you are splicing in. The base_product_top is the base directory for product files. In most cases this is called APPL_TOP. oracle_schema is the schema name for the products database objects. Warning: Do not use APPS. sizing_factor is the sizing factor used when creating tables and indexes. Note: A sizing factor of 100 means that new data objects (tables or indexes) are created with the Oracle defined NEXT extent size. A sizing factor of 200 means that a new object’s NEXT extent size will be 200% of the Oracle-defined value. Release 12 uses the OATM (Oracle Applications Tablespace Model),so you do not need to supply AD splicer with parameters for identifying tablespaces.
- <Course name> <Lesson number> -
- <Course name> <Lesson number> - File Character Set Conversion Rapid Install, AutoPatch, and AD Administration convert Oracle files from one character set to another automatically. If necessary, you can use the File Character Set Converter to perform manual conversion of files from other vendors.
- File Character Set Conversion Warning: Do not character set convert a file multiple times as this may corrupt the file. Also non-text files (such as .fmx) should not be character set converted.
- <Course name> <Lesson number> - File Character Set Conversion This table describes each of the parameters required by the File Character Set Conversion utility.
- File Character Set Conversion The path and file name for the source and the destination files can be the same if the source file’s directory and the APPLTMP directory are on the same file system. In general, it is simpler and safer to use different source and destination file names. Suggestion: If you cannot convert to the same file name, convert to a different file name or change APPLTMP to a directory on the same file system as the source file directory.
- <Course name> <Lesson number> -
- <Course name> <Lesson number> -
- <Course name> <Lesson number> - Refer to Practice - Registering a Product with AD Splicer [ LAB420FY ]