1.1- EBS R12.1.1 升级12.1.3 数据库升级 11.2.0.3
EBS R12.1.1安装手册 for Linux_x86
For RHEL5.0 x86
作者: 邮箱: 创建日期: 最后更新: 版本:
action825 action825@ 2011-1-17 2011-1-17 1.0
目录
1 安装前的系统准备...................................................................................................................2 1.1 安装说明.......................................................................................................................2 1.2 安装文档.......................................................................................................................2 1.3 操作系统版本...............................................................................................................2 1.4 磁盘空间要求...............................................................................................................2 1.5 内核要求.......................................................................................................................2 1.6 要求安装的包...............................................................................................................2 1.7 软件要求.......................................................................................................................3 1.8 内核设置.......................................................................................................................4 1.9 DNS 参数修改................................................................................................................4 1.10 验证主机名...............................................................................................................4 1.11 修改资源限制参数...................................................................................................5 1.12 安装补丁...................................................................................................................5 1.13 创建用户和组...........................................................................................................5 1.14 准备安装介质...........................................................................................................5
oracle ebs r12.1.1 for linux X64 数据库及应用启动说明
[root@paleonode1 ~]# mount /dev/sdc2 /u1 ‘/加载数据库挂在/u1下[root@paleonode1 ~]# mount /dev/sdb3 /u2 ‘/加载数据库挂在/u2下[root@paleonode1 ~]# su oravis ‘/切换用户oravis[oravis@paleonode1 root]$ pwd ‘/查看当前目录/root[oravis@paleonode1 root]$ cd ~ ‘/进入根[oravis@paleonode1 ~]$ ls ‘/查看内容db oradiag_oravis[oravis@paleonode1 ~]$ pwd ‘/查看当前目录路径/u1/VIS/visora[oravis@paleonode1 ~]$ cd db ‘/进入db目录[oravis@paleonode1 db]$ ls ‘/查看当前目录内容apps_st tech_st[oravis@paleonode1 db]$ cd tech_st ‘/进入tech_st目录[oravis@paleonode1 tech_st]$ cd 11.1.0 ‘/进入11.1.0目录[oravis@paleonode1 11.1.0]$ ls ‘/查看当前目录内容[oravis@paleonode1 11.1.0]$ . ./PROD_paleonode1.env ‘/运行环境变量[oravis@paleonode1 11.1.0]$ cd appsutil ‘/进入appsutil目录[oravis@paleonode1 appsutil]$ cd scripts ‘/进入脚本目录[oravis@paleonode1 scripts]$ cd PROD_paleonode1 ‘/进入PROD_paleonode1目录[oravis@paleonode1 PROD_paleonode1]$ ls ‘/查看当前目录内容adautocfg.sh addbctl.sh adexecsql.pl adpreclone.pl adstrtdb.sqladchknls.pl addlnctl.sh adlsnodes.sh adstopdb.sql[oravis@paleonode1 PROD_paleonode1]$ addbctl.sh start ‘/启动数据库You are running addbctl.sh version 120.1Starting the database PROD ...addbctl.sh: exiting with status 0 ‘/启动数据库结束后。
PDMS数据库的升级步骤(详细)
PDMS数据库升级教程如下：如果需要把PDMS11.5的项目数据升级到PDMS12.0项目,需要执行以下的步骤。
第一步：把PDMS11.5的项目数据升级到PDMS11.6项目，具体请参考以下的步骤：1.请您确保没有用户访问当前需要升级的项目2.清理驻留用户（Expunge - all user processes）3.对所有数据库执行DICE（Database Integrity Check）操作看是否报错，如果有报错请及时修复，然后才进行下一步。
Utilities> Integrity Check4.对需要升级的项目进行备份5.以FREE权限用户登录，进入monitor模块，打开命令行输入：$M D:\AVEVA\PDMS11.6.SP4\PDMSUI\dra\upgrade\upgradeMac(请注意：如果安装的PDMS版本和路径不同请自行修改。
)项目升级的方式，详细请查看随机安装的文档PDMS User Bulletin11.6的第2.5 Upgrading from PDMS 11章节。
第二步：把PDMS11.6的项目数据升级到PDMS12.0项目，具体请参考以下的步骤：6.请您确保没有用户访问当前需要升级的项目7.进入11.6的Admin模块，清理驻留用户（Expunge - all user processes）8.对所有数据库执行DICE（Database Integrity Check）操作看是否报错，如果有报错请及时修复，然后才进行下一步。
Utilities> Integrity Check9.对需要升级的项目进行备份10.将项目的环境变量添加至12.0的evars文件中，并以FREE权限用户登录12.0，进入monitor模块，打开命令行输入：$M D:\AVEVA\Plant\PDMS12.0.SP6\PDMSUI\dra\upgrade\upgradeMac(请注意：如果安装的PDMS版本和路径不同请自行修改。
案例客服数据库RAC升级11.2.0.1升级11.2.0.4
一．准备工作1. 所需补丁可以到ORACLE官网上下载11204 for Redhat Linux的补丁，补丁号为8202632，文件名为p1*******_112040_Linux-x86-64_1of7.zip、p1*******_112040_Linux-x86-64_2of7.zip和p1*******_112040_Linux-x86-64_3of7.zip （包含clusterware和software）。
3、备份备份两实例下的oracle_base ，以便出问题后恢复。
tar zcvf /oracle/ora11.tar.gz /oracle/ora11二、GRID升级1、grid安装预检查./runcluvfy.sh stage -pre crsinst -upgrade -n wzsxdb01,wzsxdb02 -rolling -src_crshome $ORACLE_HOME -dest_crshome /oracle/ora11/11.2.0/grid -dest_version 11.2.0.4.0 -fixup -fixupdir /tmp -verbose以下是检查明细：grid预检查.txt（1）检查: 用户"grid" 的等同用户节点名状态------------------------------------ ------------------------wzsxdb02 失败wzsxdb01 失败结果:PRVF-4007 : 用户"grid" 的等同用户检查失败ERROR:等同用户在所有指定的节点上都不可用验证无法继续解决方法：ssh wzsxdb02 date不成功,于是手工重新建立SSH用户等效性配置:node1:$ mkdir ~/.ssh$ chmod 700 ~/.ssh$ ssh-keygen -t rsa$ ssh-keygen -t dsanode2:$ mkdir ~/.ssh$ chmod 700 ~/.ssh$ ssh-keygen -t rsa$ ssh-keygen -t dsanode1:$ cat ~/.ssh/id_rsa.pub >> ~/.ssh/authorized_keys$ cat ~/.ssh/id_dsa.pub >> ~/.ssh/authorized_keys$ ssh wzsxdb02 cat ~/.ssh/id_rsa.pub >> ~/.ssh/authorized_keys$ ssh wzsxdb02 cat ~/.ssh/id_dsa.pub >> ~/.ssh/authorized_keys$ scp ~/.ssh/authorized_keys wzsxdb02:~/.ssh/authorized_keys（2）正在检查主目录"/oracle/ora11/11.2.0/grid" 中的Oracle 补丁程序"9413827 或9706490"。
oracle升级操作流程
数据库版本升级操作手册目录备份数据库 (3)升级Oracle软件 (3)修改ORACLE_HOME (13)升级实例 (14)手工使用脚本升级实例 (15)升级遇到问题的解决办法 (17)检查升级后的版本信息和无效对象 (17)附录 (19)本文用于指导oracle数据库由版本11.2.0.1.0升级到版本11.2.0.3.0升级步骤如下：➢备份数据库➢升级oracle 软件➢修改ORACLE_HOME➢升级实例➢检查升级后的版本信息和无效对象备份数据库由于oracle升级存在一定风险，所以在升级前一定要对已有数据进行备份。
1、停掉所有使用数据库的相关程序，以及数据库。
2、对数据库文件进行冷备份。
备份后的文件可转存到异机或在本地存放。
升级Oracle软件1、获取oracle升级软件p1*******_112030_Linux-x86-64_1of7.zip 及p1*******_112030_Linux-x86-64_2of7.zip。
2、将其上传到数据库服务器的/tmp/目录下并解压。
unzip p1*******_112030_Linux-x86-64_1of7.zipunzip p1*******_112030_Linux-x86-64_1of7.zip3、解压后，会在当前目录下生成一个database目录。
4、切换到oracle用户，执行oracle升级脚本。
5、s u - oracle/tmp/database/runInstaller6、不需要进行任何更改，直接点击下一步。
7、选择跳过软件更新，点击下一步。
8、选择升级现有数据库，点击下一步。
9、语言选择简体中文和英语，点击下一步。
10、选择企业版，并点击下一步。
11、Oracle基目录无需更改，软件位置需要更改为新的位置，这样可以减少宕机时间，是oracle所推荐的方法。
如下图我们将软件安装位置选择为/home/oracle/oracle11g3，修改后，点击下一步。
商务套件EBSEBusinessSuite研发战略和路线图
可行的组织结构图
增强的劳动力管理
HR 自助服务
员工全景视图有助于全面了解人才。 9 宫格矩阵和人才备注特性。 从单一页面启动相应的人才管理操作。主动识别潜能，采取行动以培养和留住人才。
第 II 阶段
In-Memory Cost Management
第 II 阶段 — 离散和流程制造客户
Inventory Management 手动桌面库存记录交易并跟踪余额
Mobile Supply Chain Applications仅射频/条形码提高现有事务的准确性，降低延迟
Oracle Warehouse Management仓库管理通过完整的任务管理实施真正的“执行系统”
2009 年 12 月
2010 年
8 月
2012 年 11 月
Oracle E-Business Suite 支持时间表
11.5.10 和 12.1 最新支持政策
11.5.10
12.0
12.1
2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018
标准
持续
标准
持续
2013 年 11 月
2012 年 1 月
2015 年 1 月
2014 年 5 月
2017 年 5 月
GA
GA
2010 年 11 月
扩展
12.2 GA 将从新的支持时间表开始
2007 年 1 月
2009 年 5 月
扩展
扩展
标准
有关发布的更多信息，请参见 MOS Doc ID 1495337.1
Oracle数据库12c升级指南说明书
Trouble-free Upgrade to Oracle Database 12c with Real Application TestingKurt EngeleiterPrincipal Product ManagerSafe Harbor StatementThe following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.Program Agenda▪Oracle Database Upgrades▪Validating Upgrades with Real Application Testing ▪Two Upgrade Use Cases:‒Consolidation into Multi-Tenant‒Database In-Memory▪Customer StoriesOracle Database UpgradesWhy Upgrade to Database 12c? •Database Consolidation to Multitenant–Ease management–Standardize on most recent version–Simplify future upgrades•Database In-Memory–Real time analytics•Migration to a new environment–Hardware / Software•Take advantage of other new database featuresValidating Upgradeswith Real Application TestingDatabase Upgrade Testing - Why•Every customer has a unique environment–Hardware configuration–Application use of the database•Upgrade testing in your environment provides validation ofperformance and correctness–Validates your unique hardware and software stack–Assures most important databases / applications perform to meet SLAsReal Application Testing provides real-workload testing solution that is comprehensive & easy-to-use for system change assessmentResponse Time TestingLoadTestingComprehensiveTestingSolutionSQL Performance Analyzer DatabaseReplayRealApplicationTestingReal Application Testing – Two Complementary SolutionsSQL Performance Analyzer •Helps users predict the impact of system changes on SQL workload response time•Low overhead capture of SQL workload to SQL Tuning Set (STS) on production system•Build different SQL trials (experiments) of SQL statements performance by test execution •Analyzes performance differences•Offers fine-grained performance analysis on individual SQL•Integrated with STS, SQL Plan Baselines, & SQL Tuning Advisor to form an end-to-end solutionAnalysis ReportCompareSQL PerformanceSQL plans + stats SQL plans + stats Pre-change Trial Post-change TrialSQL WorkloadSTSSPA Report1 2 345Database Replay •Database load and performance testing with real production workloads–Production workload characteristicssuch as timing, transactiondependency, think time, etc., fullymaintained•Identify and remediate application scalability and concurrency problems in multitenant and non-CDB databases •Allows scheduling, scaleup, subsetting, of multiple workloads•Concurrent database replay available for 11.2.0.2 and above, MOS Note: 1453789.1Database Upgrade Testing Best Practices•Always use SPA first–Unit test before load test•Capture and replay a manageable amount of time – e.g. 1 to 2 hours •Key metric for Database Replay is DB Time•Capture SQL Tuning Sets during capture and replay for additional validation•Use Enterprise Manager 12c with the latest DB Plugin–Implements best practices–Wizards guide you through the capture and replay process–Long term repository for storing and analyzing test results*Check MOS Note 560977.1 for recommended patch bundlesDB Time Definition•Total time in database calls by foreground sessions •Includes–CPU time –IO time–Active wait (non-idle wait) time•Basic unit for Oracle performance analysisCPUI/O WaitDB TimeDatabase Consolidation Into MultitenantDatabase Workload Compatibility: Challenges•Applications have different workload profiles –CPU–Memory –Storage –Network •Will my Multitenant database handle peak workloads and co-exist? •Is there enough headroom? •How do I minimize risk? •Use Real Application Testing to assess Multitenantworkload compatibility and conduct capacity planning ✓✗✓ ✓Using SPA in Multitenant EnvironmentCRM DW ERP HCMValidate SQL performance forconsolidated database:•Capture SQL workload foreach database in STS•Execute SPA for all workloadstogether in consolidatedenvironment•Identify errors & SQLregressions•Review response time•RemediateERP STSCRM STSHCM STSDWSTSSALESHRERPCRMMultitenant Load Testing: Use Consolidated DB Replay•Capture workload on different databases that needs to co-exists concurrently •Works for schema consolidation and Pluggable Databases•Use scaleup, subsetting, scheduling of multiple workloads•Use for schema and CDB consolidation •Identify and remediate inter-application scalability and concurrency problems •Available for 11.2.0.2 and above, MOS Note: 1453789.1TestCapture Process ReplayAnalysis & ReportingProductionReplay DriverClientsStorage StorageMultitenant Load Testing: Use Consolidated Database ReplayWindows DB 10.2 Capture 1Capture 2Capture 3Production SystemsCRM- DB1 HCM-DB2 DW-DB3DirectoriesAIXDB 9.2.0.8 HP-UX DB 11gMay: Month-end Close June15: Daily PeakJune 18: DW - ETL…CDB – DB12cReplay on CDBCapture 1Capture 2Capture 3Test SystemConsolidated Replay DirectoryDirectoriesHow to Test For Consolidation•If consolidating a few databases–Use SPA–Use Consolidated Replay•If consolidating a large number of databases–Identify databases with similar workload profiles–Categorize them into small, medium and large–Scale up each category with workload scheduling and Consolidated ReplayUse Case Example•Move to new platform and consolidate to multitenant databaseCapture SQL Tuning Sets on each databaseCapture Workload on each database with Database ReplayUpgrade Database to12cConfigure PDBsRun SPA TestRun Database ReplayTarget1 Node, 4 CPU, 16 GB MemoryProduction2 Nodes with 2 CPUs, 8 GB MemoryCapture Production WorkloadDatabase 1 Database 2•Capture SQL for each database into SQL Tuning Sets for SPA test •Capture workloads for Database ReplayOn Test System•Install Database 12c with Multitenant configuration•Restore production backups into individual PDBs and run upgrade scripts•Run SPA–Convert captured production STS into trial 1–Execute SPA trial 2 on each PDB–Evaluate results–Remediate any regressions before database replayConsolidated Database SPA - Execution Plans Unchanged•For consolidation into multitenant,most SQL should have unchangedexecution plan•For OLTP workload- ‘Buffer Gets’ isbest metric•Most SQL also have unchangedperformanceTest System – Consolidated Replay •Execute Consolidated Replay on test system–Remap captured TNS connections to individuals PDBs –Run Consolidated Replay–Evaluate resultsConsolidated Database Replay Result•Replay ‘user calls’ identical tocapture – same amount ofdatabase work was done•DB Time slightly reduced•Conclusion: Upgraded andconsolidated databaseperformance matches sourceStress Test with Workload Scheduling•Consolidated Database Replay also includes workload scheduling •Workload peaks can be aligned to maximize stress on replay systemUpgrading to Database In-MemoryOracle Database In-MemoryBoth row and column in-memory formatsSimultaneously active and transactionally consistentensuring access to freshest dataEliminates manual tuning and expensive analytic indexesUnique Dual-Format ArchitectureColumn FormatMemoryRow Format MemoryAnalyticsOLTPSales Sales Up-to-date analyticsOptimizing Transaction and Query Performance Row Format Databases versus Column Format DatabasesRow ▪Transactions run faster on row format –Insert or query a sales order–Fast processing few rows, many columnsColumn▪Analytics run faster on column format–Report on sales totals by state–Fast accessing few columns, many rows ORDERSALESSALESSTATEOracle 12c: Stores Data in Both Formats SimultaneouslySimple Implementation1.Upgrade to database 12.1.0.2 (or higher)2.Configure Memory Capacity‒inmemory_size = XXX GB3.Configure tables or partitions to be in memory ‒alter table | partition … inmemory;4.Drop analytic indexes to speed up OLTPUse Case Example•Upgrade to database 12.1.0.2 and Database In-MemoryRun In-MemoryAdvisorCapture SQLTuning SetCapture Workload withDatabase ReplayUpgrade Database to12cConfigureDatabase In-Memory UsingAdvisor OutputRun SPA TestRunDatabaseReplayProduction TestUpgrade and Testing Steps•Run Database In-Memory Advisor in existing database 11.2 environment•Capture SQL Tuning Set•Capture workload with Database Replay•In test environment–Upgrade database and implement Database In-Memory Advisor recommendations–Run SPA trial–Run Database Replay–Evaluate resultsRun Oracle Database In-Memory Advisor•New In-Memory Advisor •Analyzes existing DB workloadvia AWR & ASH repositories•Provides list of objects that would benefit most from being populated into IM column store•Works on database versions 11.2 and aboveObject TypeObjectEstimated In-Memory Size EstimatedAnalyticPerformance Improve mentTable SALES.ORDERS 2.19 GB 9.3X TableSALES.LINEITEM1.03 GB5.2XPartition SALES.PRODUCTS.201404 415 MB 4.3X Sub-partitionSALES.PRODUCTS.20140330200 MB2.7XCapture Production Workload•Capture SQL into a SQL Tuning Set •Capture workload for Database ReplayConfigure In-Memory on Test System•Restore production database•Upgrade to database 12.1.02 or higher•Set init.ora parameter inmemory_size to size In-Memory column store•Restart database•Execute SQL script from In-Memory Advisor to configure objects In-MemoryValidate In-Memory ConfigurationEnterprise Manger 12c In-Memory Central Object map – displaysrelative sizes of objectsIn-MemoryObject Table – Listsdetails of segmentsloaded In-MemorySPA – Look for Expected Plan Changes•Convert production STS to trial 1•Execute trial SPA trial 2•Produce comparison report•Best metric for analytic queryworkload is ‘Elapsed Time’•Analytic SQL have changedexecution plan with plan line‘Table Access In Memory Full’•SQL are benefitting from In-MemoryIdentify Plan Change Improvements Real Time SQL MonitoringExecute Database Replay•Validate concurrency and loadimprovement for consolidatedworkload•Database Replay trial results:•User calls identical – same workloadwas executed•DB Time substantially reduced•SuccessDatabase In-Memory DB Time ImprovementDatabase 11.2.0.4 Database 12.1.0.2 + In-MemoryCustomer Case StudiesSumitomo Heavy Industries,Ltd. Database Upgrade ProjectUsing RAT & GG VeridataCustomer ProfileCompany Name: Sumitomo Heavy Industries, Ltd.Head Office: ThinkPark Tower, 1-1 Osaki 2-chome, Shinagawa-ku, Tokyo 141-6025, JapanFounded: November 20, 1888Incorporated: November 1, 1934Capital: JPY 30,871,650,000 (as of March 31, 2014) Employees: Consolidated: 17,941 (as of March 31, 2014)Annual Revenue: Consolidated: JPY 615,270,000,000(for the 2013 Fiscal Year)Challenge & SolutionDatabase Upgrade 9i /10g -> 11gR2Solution•Perform application test with completely the same workload using Oracle Real Application Testing •Automate the Performance management using Diagnostics Pack & Tuning Pack•Guarantee data consistency after testing on new environment using Oracle GoldenGate Veridata •Use Oracle GoldenGate for minimizing downtime and fallback plan (under proposing)Challenge •Aim to reduce costs to around $2.5 M to 30-50% •Upgrading in parallel in a short period of time about 30DB •The data migration in a short period of time large-scale DB and Mission-Critical DB environment, to minimize business downtime •Standardizing method for migrating and upgrading multiple databases efficiently •Performing and automating application test by DBA for minimize costSolution ArchitectureArchitecture•1st step: Measure the SQL Elapsed timeCheck the workload consistency by using Veridata•2nd step: Check whether the new database has been created successfully by using Veridata•3rd step: Compare the whole throughput and workload between the production and the new production by using RATPerformanceTest Performance and Consistency TestProduction (9i) Test (9i)Test (11g)Veridata Server New Production(11g)1st Step3rd StepDatabaseConfiguration Test2nd StepVeridata ServerSumitomo Heavy Industries, Ltd.30DBs Upgrade, reduce the verification Cost to take advantage of support toolsCustomer ProfileName： Sumitomo Heavy Industires, Ltd.（http://www.shi.co.jp/english/）Location： Tokyo (Japan)Industry： manufacturing IndustryEmployees： 17,961Oracle Products•Oracle Real Application Testing (RAT)•Oracle Diagnostics Pack /Oracle Tuning Pack (Diag/Tuning) •Oracle GoldenGate Veridata(Veridata)•Oracle GoldenGate (GG) CUSTOMER PERSPECTIVE“I heard that Other Oracle Customer has efficiently implementedDB upgrade, to take advantage of tools(RAT, GG etc).Therefore ,We accept the Challenge!!”Engineer / Takayuki Okoshi INFORMATION SYSTEMS DEVELOPMENT DEPT.Sumitomo Heavy Industries Business Associates, Ltd.CHALLENGES/OPPORTUNITIES• Upgrading in parallel in a short period of time about 30DB •Aim to reduce costs to around $2.5 M to 30-50% •Establishing an upgrade method utilizing a tool for efficient operation while ensuring the quality• The data migration in a short period of time large-scale DB environment, to minimize business downtime• Adopt the DB performance improvement technique method RESULTS•RAT realized the accurate verification and efficient online processing performance•Diag/Tuning realized the performance improvement technique method•Veridata realized the data validation of the old and new environment accurate and efficiently to a large extent•To maintain business continuity, used GG to data migrate on the Critical DBs.。
oracle-RAC-11.2.0.3-升级至11.2.0.4
Linux-RAC升级11.2.0.3至11.2.0.4一、上传及解压相关文件 (2)二、创建GI和DB软件目录（新） (2)三、安装升级GI软件 (2)四、安装升级DB软件 (12)五、修改环境变量 (25)六、升级结果验证 (27)6.1验证环境变量是否生效 (27)6.2验证数据库所有组件是否成功升级 (27)七、关闭数据库关闭CRS重启服务器 (31)一、上传及解压相关文件将11204版的grid以及oracle软件上传至服务器。
并在合适的位置进行解压，得到database 以及grid文件夹。
二、创建GI和DB软件目录（新）mkdir -p /data/11.2.0.4/grid/basemkdir -p /data/11.2.0.4/grid/crsmkdir -p /data/11.2.0.4/oracle/appchown grid:oinstall /data/11.2.0.4/grid/basechown grid:oinstall /data/11.2.0.4/grid/crschown -R oracle:oinstall /data/11.2.0.4/oracle/appchmod -R 775 /data/11.2.0.4/chown -R grid:oinstall /oracle_new三、安装升级GI软件停止数据库实例节点一脚本执行情况：[root@linux1 ~]# sh /oracle/app/11.2.0/grid/rootupgrade.sh Performing root user operation for Oracle 11gThe following environment variables are set as:ORACLE_OWNER= gridORACLE_HOME= /oracle/app/11.2.0/gridEnter the full pathname of the local bin directory: [/usr/local/bin]: The contents of "dbhome" have not changed. No need to overwrite. The contents of "oraenv" have not changed. No need to overwrite. The contents of "coraenv" have not changed. No need to overwrite.Entries will be added to the /etc/oratab file as needed by Database Configuration Assistant when a database is created Finished running generic part of root script.Now product-specific root actions will be performed.Using configuration parameter file: /oracle/app/11.2.0/grid/crs/install/crsconfig_paramsCreating trace directoryUser ignored Prerequisites during installationInstalling Trace File AnalyzerCRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on 'linux1'CRS-2673: Attempting to stop 'ora.crf' on 'linux1'CRS-2673: Attempting to stop 'ora.mdnsd' on 'linux1'CRS-2677: Stop of 'ora.crf' on 'linux1' succeededCRS-2673: Attempting to stop 'ora.gipcd' on 'linux1'CRS-2677: Stop of 'ora.mdnsd' on 'linux1' succeededCRS-2677: Stop of 'ora.gipcd' on 'linux1' succeededCRS-2673: Attempting to stop 'ora.gpnpd' on 'linux1'CRS-2677: Stop of 'ora.gpnpd' on 'linux1' succeededCRS-2793: Shutdown of Oracle High Availability Services-managed resources on 'linux1' has completed CRS-4133: Oracle High Availability Services has been stopped.ASM 升级已在第一个节点上初始化。
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
EBS R12.1.1 升级12.1.3 数据库升级 11.2.0.3安装说明书编制：长安铃木信息系统课王川2012-11-21目录目录 (2)1 概述 (5)1.1升级内容 (5)1.2准备的补丁 (5)2 升级应用 (6)2.1停止应用。
(6)2.2ADADMIN进入维护模式 (7)2.3追加补丁 (9)2.4执行DB节点应用CODE LEVEL (9)2.5追加应用补丁 (10)3 升级数据库 (10)3.1升级数据库准备 (10)3.2创建NLS/DA TA/9IDATA目录 (13)3.3安装数据库补丁 (13)3.4P REPARE U PGRADE (14)3.5执行DBUA (14)3.6初始化参数文件和监听文件 (19)3.6.1 参数文件 (19)3.6.2 监听文件 (19)3.6.3 运行脚本 (20)4 初始化数据库节点 (20)4.1应用层生成生成新的APPSUTIL (20)4.2生成数据库上下文文件 (20)5 ADADMIN重建权限和同义词 (21)6 分别重启数据库和应用。
(22)7 校验升级结果。
(22)文档版本记录版本编号变更内容变更人日期EBS R12.1.1 Enterprise5.7 64bit安装说明书1概述1.1 升级内容1、应用从R12.1.1升级到R12.1.3。
2、数据库升级到11.2.0.3。
1.2 准备的补丁1、APP升级补丁p1*******_R12.BIV.B_R12_GENERIC.zipp1*******_R12.TXK.B_R12_GENERIC.zipp1*******_R12.TXK.B_R12_GENERIC.zipp8919489_R12.TXK.B_R12_GENERIC.zipp8919489_R12.TXK.B_R12_zhs.zipp9062910_12.1.0_R12_GENERIC.zipp9151516_R12.ECX.B_R12_GENERIC.zipp9239089_R12.AD.B_R12_LINUX.zipp9239090_R12_LINUX_1of6.zipp9239090_R12_LINUX_2of6.zipp9239090_R12_LINUX_3of6.zipp9239090_R12_LINUX_4of6.zipp9239090_R12_LINUX_5of6.zipp9239090_R12_LINUX_6of6.zipp9239090_R12_zhs.zipp9239095_R12_GENERIC.zipp9583541_R12.TXK.B_R12_GENERIC.zipp9738085_R12.TXK.B_R12_GENERIC.zipp9817770_R12.ATG_PF.B_R12_LINUX.zipp9852070_R12.TXK.B_R12_GENERIC.zipp9868229_R12.BOM.C_R12_GENERIC.zipp9966055_R12.FND.B_R12_GENERIC.zip2、数据库升级到11.2.0.3的安装包p1*******_112030_Linux-x86-64_1of7.zip…p1*******_112030_Linux-x86-64_7of7.zip3、数据库补丁p1*******_112030_Linux-x86-64.zipp1*******_112030_Linux-x86-64.zipp1*******_112030_Linux-x86-64.zipp1*******_112030_Generic.zipp1*******_112030_Linux-x86-64.zipp1*******_112030_Generic.zipp1*******_112030_Generic.zipp4247037_112030_Generic.zipp9858539_112030_Generic.zip2升级应用2.1 停止应用。
[root@test ~]# su - appdemo[appdemo@test ~]$ cd $INST_TOP/admin/scripts/[appdemo@test scripts]$ ./adstpall.sh apps/apps查看是否停止完成ps -ef | grep appdemo[appdemo@test scripts]$ ps -ef | grep appdemoroot 19111 19086 0 10:12 pts/1 00:00:00 su - appdemo appdemo 19112 19111 0 10:12 pts/1 00:00:00 -bashroot 19240 19204 0 10:13 pts/2 00:00:00 su - appdemo appdemo 19241 19240 0 10:13 pts/2 00:00:00 -bash appdemo 19886 19241 0 10:15 pts/2 00:00:00 ps -ef appdemo 19887 19241 0 10:15 pts/2 00:00:00 grep appdemo2.2 ADADMIN进入维护模式直接进入维护模式1、Patch 9239089以orademo用户创建目录$ORACLE_HOME/appsutil/admin[orademo@test ~]$ mkdir -p $ORACLE_HOME/appsutil/admin拷贝adgrants.sql到目录$ORACLE_HOME/appsutil/admin[orademo@test admin]$ cp /src/patch/to1213/9239089/admin/adgrants.sql $ORACLE_HOME/appsutil/admin在目录下执行SQLPLUS，后面写参数”APPS”[orademo@test admin]$ cd $ORACLE_HOME/appsutil/admin[orademo@test admin]$ lsadgrants.sql[orademo@test admin]$ lltotal 56-rwxr-xr-x 1 orademo dba 53060 Nov 21 10:26 adgrants.sql[orademo@test admin]$ sqlplus / as sysdbaSQL*Plus: Release 11.1.0.7.0 - Production on Wed Nov 21 10:27:19 2012Copyright (c) 1982, 2008, Oracle. All rights reserved.Connected to:Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit ProductionWith the Partitioning, OLAP, Data Mining and Real Application Testing optionsSQL> @adgrants.sql APPSAPPDEMO用户在9239089目录下执行adpatch，完成补丁。
Orademo用户执行SQLPLUS，修改参数，重启数据库。
alter system set "_disable_fast_validate"=TRUE2、Patch 9239090进入9239090备注：中间遇到报错，按以下方式排除：Relink Advanced Supply Chain Planning executables (for SLES 10, Oracle Linux/RHEL 5.4 or higher and Oracle Linux 6 only)During the relink phase of the installation of EBS Release 12 (12.1.1) on SLES 10, Oracle Linux/RHEL 5.4 (Update 4 or higher) or Oracle Linux 6 failures will result while relinking the Advanced Supply Chain Planning (ASCP) executables MSO, MSC, MSR and FEM. To fix this problem, users are required to replace the following line under the Linux section of the $AD_TOP/bin/adrelinknew.sh:CPP_LDFLAGS=' -L$(ORACLE_HOME)/lib -L$(ORACLE_HOME)/lib/stubs -lclntsh'CPP_LDFLAGS=' -L$(ORACLE_HOME)/lib -L$(ORACLE_HOME)/lib/stubs -lclntsh -Wl,--noinhibit-exec' 然后在adadmin中relink3、进入9239090_ZHS目录，运行adpatch。
2.3 追加补丁按以下顺序：9239095981777099660552.4 执行DB节点应用code levelStep1:应用用户appdemo运行autoconfig，生成appsutil.zip$cd /u01/demo/appdemo/inst/apps/demo_test/admin/scripts$./adautocfg.sh$perl $AD_TOP/bin/admkappsutil.plStep2:拷贝appsutil.zip到数据库节点cd /u01/demo/appdemo/inst/apps/demo_test/admin/out/拷贝appsutil.zip到DB节点Step3:数据库应用autoconfigorademo用户解压appsutil.zip$cd $ORACLE_HOME$unzip -o appsutil.zip运行autoconfig[orademo@test 11.1.0]$ cd appsutil[orademo@test appsutil]$ lsadmin clone demo_test.xml html java log out perl sql templatebin conf_demo.txt driver install jre media outbound scripts temp[orademo@test appsutil]$ cd scripts/[orademo@test scripts]$ lsdemo_test[orademo@test scripts]$ cd demo_test/[orademo@test demo_test]$ lsadautocfg.sh adchknls.pl addbctl.sh addlnctl.sh adexecsql.pl adlsnodes.sh adpreclone.pl adstopdb.sql adstrtdb.sql[orademo@test demo_test]$ ./adautocfg.shStep4:DB、APP层执行preclone操作DB层执行preclone操作：$cd /u01/demo/orademo/db/tech_st/11.1.0/appsutil/scripts/demo_test $perl adpreclone.pl dbTierAPP层执行preclone操作：$ cd /u01/demo/appdemo/inst/apps/demo_test/admin/scripts$perl adpreclone.pl appsTier2.5 追加应用补丁顺序执行：11g Release 2 interoperability patch for Release 12.1 (9062910)12.1 TXK Delta 3 patch (8919489)p8919489_R12.TXK.B_R12_zhs958354191515169868229101637531107156997380859852070126866103升级数据库3.1 升级数据库准备1、进入升级包目录，安装数据库代码。