ebs系统架构简介9——Patch

1、什么是codelines 和 codelevels?

在R12中,oracle Application 补丁以codelines分组,R12.0对应codeline A。Any future point releases introduce new codelines, each
identified by a new letter.  For example, Release 12.1 would introduce codeline B and Release 12.2 would introduce codeline C.  

Patches associated with codelines not only implement a set of product features for that point release, but also provide fixes to that set of features. We describe this unique set of product
features for a point release as a codelevel and assign it a unique number. Codelevels also identify patches for individual products. 

For example, codelevel R12.AD.A.1 is the first set of fixes to codelevel R12.AD.A, 

R12.AD.A.2 is the second set, and so on. 

Codelevels are cumulative(累加的) - each one contains the initial set of features plus all the fixes created to date for that product or product family.

All codelevels created after the initial point release are aggregated into cumulative release update packs (RUPs). RUP1 is equivalent to R12.0.1, RUP2 is equivalent to R12.0.2, and so on.  In addition, they may also provide feature enhancements, which provide
new functionality that has a limited impact on your system.

A new point release contains new features that will substantially impact your system and may change its operation.  It starts a new codeline (for example, codeline B).  At that point, you can choose to upgrade to the new codeline and adopt the new features,
or stay on your existing codeline, where bug fixes and enhancements will continue to be provided for your existing features.

2、patch 的驱动文件里有什么?

The driver actions are as follows:

  • Copy: Contains commands to change Oracle Applications files. The commands include directives to copy and update files, libraries, and/or Java, and commands for generating JAR files and/or C executables. In a multi-node system, the copy
    portion runs on all application tier APPL_TOPs.
  • Database: Contains commands to change Oracle Applications database objects,such as PL/SQL and table definitions, or to update or migrate data. In a multi-node system, the database portion runs only on
    the application tier APPL_TOP that implements the administration server.
  • Generate: Contains commands to generate forms, reports, messages, and/or graphics files. In a multi-node system, the generate portion runs on all application tier APPL_TOPs, unless the APPL_TOP only implements the administration server.

adpatch

adpatch补丁是打在ebs各个模块上的补丁,简单理解为把一些:forms、reports等拷贝到对应的模块目录下,还有sql对象拷贝到数据库内,执行。

在打补丁的过程中,会在补丁存放的目录(比如/home/apptest/1456321/)下,创建backup目录,把需要修改或者替换的文件拷贝到这个目录下。

打这个补丁,一直是关闭应用,enable维护模式后才进行的,数据库开启;

不过最近在网上及书上看到一些操作, 比如在版主zlc158的大作上看到安装简体中文语言包时, 操作步骤中没有关闭应用,只有修改

维护模式 , adpatch 之后直接disable 维护模式。

关于adpatch的例子,参考:http://download.csdn.net/detail/changyanmanman/7442163

admrgpch:

这个可以合并多个补丁,生成一个驱动文件,然后打一次就了。

Create
Source and
destination
directory
Copy all the patche to source directory
and run the below scripts
admrgpch -s /home/appltest/source -d /home/appltest/dest -merge_name mergedrv

例子:

[appl01@vs123 patch]$
admrgpch -s /u01/patch/merge -d /u01/patch/dest -merge_name mergedrv

Executing the merge of the patch drivers
 -- Processing patch: /u01/patch/merge/9062910
 -- Processing file: /u01/patch/merge/9062910/u9062910.drv
 -- Done processing file: /u01/patch/merge/9062910/u9062910.drv
 -- Done processing patch: /u01/patch/merge/9062910

 -- Processing patch: /u01/patch/merge/9868229
 -- Processing file: /u01/patch/merge/9868229/u9868229.drv
 -- Done processing file: /u01/patch/merge/9868229/u9868229.drv
 -- Done processing patch: /u01/patch/merge/9868229

 -- Processing patch: /u01/patch/merge/11071569
 -- Processing file: /u01/patch/merge/11071569/u11071569.drv
 -- Done processing file: /u01/patch/merge/11071569/u11071569.drv
 -- Done processing patch: /u01/patch/merge/11071569

Copying files...

100% complete. Copied 7 files of 7...

Character-set converting files...

  3 unified drivers merged.

Patch merge completed successfully

Please check the log file at ./admrgpch.log.

[appl01@vs123 patch]$ cat admrgpch.log 
************* Start of AD Merge Patch session *************
AD Merge Patch version: 12.0.0
AD Merge Patch started at: Tue Jun 03 2014 21:56:07

Options : "-s /u01/patch/merge -d /u01/patch/dest -merge_name mergedrv "
  NLS_LANG Character Set is: AL32UTF8

Executing the merge of the patch drivers

STRT_TASK: [Looping through patch driver files] [Tue Jun 03 2014 21:56:07]
 -- Processing patch: /u01/patch/merge/9062910
 -- Processing file: /u01/patch/merge/9062910/u9062910.drv
Reading driver file /u01/patch/merge/9062910/u9062910.drv ...
 Patch Character Set is: us7ascii
 -- Merging patch driver : /u01/patch/merge/9062910/u9062910.drv
 -- Done processing file: /u01/patch/merge/9062910/u9062910.drv
 -- Done merging patch: /u01/patch/merge/9062910
 -- Done processing patch: /u01/patch/merge/9062910

 -- Processing patch: /u01/patch/merge/9868229
 -- Processing file: /u01/patch/merge/9868229/u9868229.drv
Reading driver file /u01/patch/merge/9868229/u9868229.drv ...
 Patch Character Set is: us7ascii
 -- Merging patch driver : /u01/patch/merge/9868229/u9868229.drv
 -- Done processing file: /u01/patch/merge/9868229/u9868229.drv
 -- Done merging patch: /u01/patch/merge/9868229
 -- Done processing patch: /u01/patch/merge/9868229

 -- Processing patch: /u01/patch/merge/11071569
 -- Processing file: /u01/patch/merge/11071569/u11071569.drv
Reading driver file /u01/patch/merge/11071569/u11071569.drv ...
 Patch Character Set is: us7ascii
 -- Merging patch driver : /u01/patch/merge/11071569/u11071569.drv
 -- Done processing file: /u01/patch/merge/11071569/u11071569.drv
 -- Done merging patch: /u01/patch/merge/11071569
 -- Done processing patch: /u01/patch/merge/11071569

STOP_TASK: [Looping through patch driver files] [Tue Jun 03 2014 21:56:07]

STRT_TASK: [Copying Files] [Tue Jun 03 2014 21:56:07]

Copying files...

100% complete. Copied 7 files of 7...

STOP_TASK: [Copying Files] [Tue Jun 03 2014 21:56:07]

STRT_TASK: [Character-set converting files] [Tue Jun 03 2014 21:56:07]

Character-set converting files...

************* Start of AD Character-set Conversion session *************
AD Character-set Conversion version: 12.0.0
AD Character-set Conversion started at: Tue Jun 03 2014 21:56:07

Converting character set for file
  /u01/patch/merge/9062910/fem/patch/115/sql/fem_chk_dis_mbrs.plb
from 'US7ASCII'to 'AL32UTF8'... Done.
Source file:
  /u01/patch/merge/9062910/fem/patch/115/sql/fem_chk_dis_mbrs.plb
Destination file:
  /u01/patch/dest/fem/patch/115/sql/fem_chk_dis_mbrs.plb

Converting character set for file
  /u01/patch/merge/9062910/okl/patch/115/sql/OKLRKRPB.pls
from 'US7ASCII'to 'AL32UTF8'... Done.
Source file:
  /u01/patch/merge/9062910/okl/patch/115/sql/OKLRKRPB.pls
Destination file:
  /u01/patch/dest/okl/patch/115/sql/OKLRKRPB.pls

Converting character set for file
  /u01/patch/merge/9062910/per/patch/115/sql/pechktsk.sql
from 'US7ASCII'to 'AL32UTF8'... Done.
Source file:
  /u01/patch/merge/9062910/per/patch/115/sql/pechktsk.sql
Destination file:
  /u01/patch/dest/per/patch/115/sql/pechktsk.sql

Converting character set for file
  /u01/patch/merge/11071569/README.html
from 'US7ASCII'to 'AL32UTF8'... Done.
Source file:
  /u01/patch/merge/11071569/README.html
Destination file:
  /u01/patch/dest/11071569_README.html

Converting character set for file
  /u01/patch/merge/11071569/README.txt
from 'US7ASCII'to 'AL32UTF8'... Done.
Source file:
  /u01/patch/merge/11071569/README.txt
Destination file:
  /u01/patch/dest/11071569_README.txt

Converting character set for file
  /u01/patch/merge/11071569/b11071569.ldt
from 'US7ASCII'to 'AL32UTF8'... Done.
Source file:
  /u01/patch/merge/11071569/b11071569.ldt
Destination file:
  /u01/patch/dest/b11071569.ldt

Converting character set for file
  /u01/patch/merge/11071569/f11071569.ldt
from 'US7ASCII'to 'AL32UTF8'... Done.
Source file:
  /u01/patch/merge/11071569/f11071569.ldt
Destination file:
  /u01/patch/dest/f11071569.ldt

Converting character set for file
  /u01/patch/merge/9062910/README.html
from 'US7ASCII'to 'AL32UTF8'... Done.
Source file:
  /u01/patch/merge/9062910/README.html
Destination file:
  /u01/patch/dest/9062910_README.html

Converting character set for file
  /u01/patch/merge/9062910/README.txt
from 'US7ASCII'to 'AL32UTF8'... Done.
Source file:
  /u01/patch/merge/9062910/README.txt
Destination file:
  /u01/patch/dest/9062910_README.txt

Converting character set for file
  /u01/patch/merge/9062910/b9062910.ldt
from 'US7ASCII'to 'AL32UTF8'... Done.
Source file:
  /u01/patch/merge/9062910/b9062910.ldt
Destination file:
  /u01/patch/dest/b9062910.ldt

Converting character set for file
  /u01/patch/merge/9062910/f9062910.ldt
from 'US7ASCII'to 'AL32UTF8'... Done.
Source file:
  /u01/patch/merge/9062910/f9062910.ldt
Destination file:
  /u01/patch/dest/f9062910.ldt

Converting character set for file
  /u01/patch/merge/9868229/README.html
from 'US7ASCII'to 'AL32UTF8'... Done.
Source file:
  /u01/patch/merge/9868229/README.html
Destination file:
  /u01/patch/dest/9868229_README.html

Converting character set for file
  /u01/patch/merge/9868229/README.txt
from 'US7ASCII'to 'AL32UTF8'... Done.
Source file:
  /u01/patch/merge/9868229/README.txt
Destination file:
  /u01/patch/dest/9868229_README.txt

Converting character set for file
  /u01/patch/merge/9868229/b9868229.ldt
from 'US7ASCII'to 'AL32UTF8'... Done.
Source file:
  /u01/patch/merge/9868229/b9868229.ldt
Destination file:
  /u01/patch/dest/b9868229.ldt

Converting character set for file
  /u01/patch/merge/9868229/f9868229.ldt
from 'US7ASCII'to 'AL32UTF8'... Done.
Source file:
  /u01/patch/merge/9868229/f9868229.ldt
Destination file:
  /u01/patch/dest/f9868229.ldt

Adncnv completed successfully.

Please check the adncnv logfile at admrgpch.log.

STOP_TASK: [Character-set converting files] [Tue Jun 03 2014 21:56:07]

  3 unified drivers merged.

Patch merge completed successfully

Please check the log file at ./admrgpch.log.

然后再使用adpatch安装即可。

时间: 2024-09-21 22:48:25

ebs系统架构简介9——Patch的相关文章

ebs系统架构简介3

整理自:http://www.itpub.net/thread-1409361-1-1.html ==================================================================4: 基本系统管理知识 结合上面提到的系统架构的基本知识,这里总结R12系统的基本管理知识,就是如何做我们最关心的最基本的start/stop/status . 1. database 方面: 如上述,Database Tier 有关的 Server Process S

ebs系统架构简介6——应用管理工具总结

Oracle 开发了 Oracle Applications Technology Layer. Products in the Oracle E-Business Suite technology layer include(Oracle Applications Technology Layer 包含的功能有):1. Oracle Applications DBA (AD): 就是一些安装,维护用的工具, 包括:AD Administration (adadmin)AD Merge Patc

ebs系统架构简介1——三层结构上篇

转载自:http://www.itpub.net/thread-1409361-1-1.html <Oracle Applications DBA 基础>3- 4 系统架构及基本系统管理知识 1. 系统架构介绍 ============== Oracle 的applications 主要包括一个文件系统,一个数据库: 而文件系统包括:forms(用来交互和更新数据).reports(用来显示标准的输出数据).一致性程序(提供了大容量.非交互的数据更新操作).程序和sql脚本(管理这个系统).h

ebs系统架构简介2——三层结构和Environment file下篇

整理自:http://www.itpub.net/thread-1409361-1-1.html Database Tier:我们看R12的后台数据库. Oracle Applications 充分使用 Oracle 数据库提供的各种数据类型:select object_type, count(*) from dba_objects where owner not like '%SYS%' group by object_type order by 1; OBJECT_TYPE         

ebs系统架构简介4——Apps Schema

转自:http://blog.csdn.net/pan_tian/article/details/7708430 Apps schema:本身不拥有任何表,对于每一个独立Schema下的表数据,在Apps schema下要同样有一个synonym存在.apps的默认密码为"apps". 关于Apps Schema可以参见:http://blog.csdn.net/cymm_liu/article/details/10164877 Applsys Schema:包含所有系统管理(admi

ebs系统架构简介6——clone

1.介绍 clone有不同的用途: 1)可以做个生产系统的副本来做补丁测试. 2)创建一个stageing area(可理解为缓冲区准备区)来降低打补丁的停机时间 3)刷新测试系统(把最新的生产系统拷贝给测试系统) 4)把当前存在的系统拷贝到一个不同的机器或者平台上(一般常用的是我们给一个企业做好系统,clone一个做测试,一个开发) 2.Rapid Cline Operation 通过运行Rapid Clone tool,快速克隆不改变原来的系统,运行:adpreclone.pl脚本收集数据库

ebs系统架构简介5——Auto Config

AD 工具中有一个相当重要的,就是 AutoConfig.主要是简化和标准化配置管理任务.参考文档: Using AutoConfig to Manage System Configurations in Oracle E-Business Suite Release 12 (文档 ID 387859.1) R12 将所有的配置参数集中在 context file 中, app tier 一个context file:db tier 一个 context file. 例如,如果用户要修改Apac

ebs系统架构简介7.1——rac clone

今天在rac环境clone 的时候,查看日志: /testebs/uat/db/11.2.0/appsutil/log/TESTUAT1_hostname1/ApplyDatabase_12201204.log 发现这样一句话: Attempting to move clone specific files to temporary directory.. Src location: /backup/testsit/clone/data/stage Target location: /teste

《系统架构:复杂系统的产品设计与开发》——导读

目录 第一部分系统思维第1章 系统架构简介1.1 复杂系统的架构1.2 良好架构的优势 1.3 学习目标 1.4 本书结构1.5 参考资料 第2章 系统思维 2.1 简介 2.2 系统与涌现2.2.1 系统 2.2.2 涌现 2.3 任务一:确定系统及其形式与功能 2.3.1 形式与功能 2.3.2 工具-过程-操作数:这是人类的标准思维模式吗 2.4 任务二:确定系统中的实体及其形式与功能 2.4.1 具备形式与功能的实体 2.4.2 确定如何将系统初步分解为恰当的实体 2.4.3 用整体思维