Oracle rdbms 打psu从11.2.0.3.0升级到11.2.0.3.11 参考patch :18522512停应用,停监听与DB,将db的oracle_home下的OPatch目录加到环境变化PATH路径下,因为接下来要用opatch工具。报错,说这个opatch工具太旧,要下载新的。The OPatch version being used (
Oracle rdbms 打psu从11.2.0.3.0升级到11.2.0.3.11 参考patch :18522512 停应用,停监听与DB,将db的oracle_home下的OPatch目录加到环境变化PATH路径下,因为接下来要用opatch工具。 报错,说这个opatch工具太旧,要下载新的。 The OPatch version being used (11.2.0.1.7) doesn't meet the minimum version required by the patch(es). Please download latest OPatch from My Oracle Support. 下载了11.2.0.3.6的opatch工具,将内容覆盖Oracle_home的OPatch里面的内容,(做好备份) 一,首次尝试发现冲突 ora@erpt1:erpt1 > opatch applyoracle Interim Patch Installer version 11.2.0.3.6
copyright (c) 2013, Oracle Corporation. All rights reserved.
oracle Home : /u01/erpt1/db/tech_st/11.2.0
central Inventory : /u01/oraInventory
from : /u01/erpt1/db/tech_st/11.2.0/oraInst.loc
oPatch version : 11.2.0.3.6
oUI version : 11.2.0.3.0
log file location : /u01/erpt1/db/tech_st/11.2.0/cfgtoollogs/opatch/opatch2014-07-29_14-58-27PM_1.log
verifying environment and performing prerequisite checks...
composite Patch 18522512 is a bug superset of 13001379,9858539 in OH.
composite Patch 18522512 conflicts with installed patch(es) 12942119, 13004894
conflict Description:
here are the specific sub-patches of composite patch 18522512 that conflict with 12942119, 13004894
sub-Patch 16619892 conflicts with 13004894
sub-Patch 16902043 conflicts with 12942119
conflict Remedy:
refer to My Oracle Support Note 1299688.1 for instructions on resolving patch conflicts.
utilSession failed: Composite conflicts with existing oneoffs.
log file location: /u01/erpt1/db/tech_st/11.2.0/cfgtoollogs/opatch/opatch2014-07-29_14-58-27PM_1.log
oPatch failed with error code 73 大意是说,我的patch与一些有已打的patch有冲突,也是一些已经打的patch的超集。 利用自述文档里面的方法,再检查一下,大意跟上面的差不多。 ora@erpt1:erpt1 > opatch prereq CheckConflictAgainstOHWithDetail -ph ./
Oracle Interim Patch Installer version 11.2.0.3.6
Copyright (c) 2013, Oracle Corporation. All rights reserved.
PREREQ session
Oracle Home : /u01/erpt1/db/tech_st/11.2.0
Central Inventory : /u01/oraInventory
from : /u01/erpt1/db/tech_st/11.2.0/oraInst.loc
OPatch version : 11.2.0.3.6
OUI version : 11.2.0.3.0
Log file location : /u01/erpt1/db/tech_st/11.2.0/cfgtoollogs/opatch/opatch2014-07-29_15-02-46PM_1.log
Invoking prereq "checkconflictagainstohwithdetail"
ZOP-47: The patch(es) has supersets with other patches installed in the Oracle Home (or) among themselves.
ZOP-40: The patch(es) has conflicts with other patches installed in the Oracle Home (or) among themselves.
Prereq "checkConflictAgainstOHWithDetail" failed.
Summary of Conflict Analysis:
There are no patches that can be applied now.
Following patches have conflicts. Please contact Oracle Support and get the merged patch of the patches :
13004894, 18522512, 12942119
Following patches are not required, as they are subset of the patches in Oracle Home or subset of the patches in the given list :
13001379, 9858539
Following patches will be rolled back from Oracle Home on application of the patches in the given list :
13004894, 13001379, 12942119, 9858539
Conflicts/Supersets for each patch are:
Patch : 18522512
Conflict with 13004894
Conflict details:
/u01/erpt1/db/tech_st/11.2.0/lib/libserver11.a:/qke.o
/u01/erpt1/db/tech_st/11.2.0/lib/libserver11.a:/qke.o
/u01/erpt1/db/tech_st/11.2.0/lib/libserver11.a:/qke.o
Bug Superset of 13001379
Super set bugs are:
13001379
Conflict with 12942119
Conflict details:
/u01/erpt1/db/tech_st/11.2.0/lib/libserver11.a:/qksbg.o
Bug Superset of 9858539
Super set bugs are:
9858539
OPatch succeeded.
二、SR回复
此时我给MOS提了个SR,说了下情况。 Oracle工程师这么回复: PSU patch 11.2.0.3.11 has conflicts Here are the specific sub-patches of composite patch 18522512 that conflict with 12942119, 13004894 Sub-Patch 16619892 conflicts with 13004894 Sub-Patch 16902043 conflicts with 12942119
大意是,我们的patch 18522512是复合patch ,里面有一些子Patch,这些子patch与我已打的patch12942119, 13004894有冲突。(一般patch号就是bug号)。什么是冲突呢?如果我打了个Patch修改了一个二进制文件,然后再打另外一个Patch又修改这个二进制文件,但是会把第一个patch的效果消除,那就是冲突。
Patch conflict occurs when patches try to modify same binaries. To resolve conflicts and get fixes of both conflicting patches, we need to apply merge patch.
In case patch is conflicting PSU, then we say overlay patch instead of merge patch.
In composite patch model, we need to look at which PSU conflicts with existing installed patch.
In our case patch 13004894 patch conflicts with 11.2.0.3.7 PSU patch. So we develop overlay patch for 11.2.0.3.7 version,
If you check patch 13004894, it would have released for other version as well, it means the patch conflicts with those PSU as well. 一般来说,为了解决这种冲突,我们就要下载merge patch。merge patch能同时包含了两个冲突的patch的叠加效果。如果我们下载的是有冲突的PSU Patch,那么我们就用overlay patch的叫法来代替merge patch。意思是overlay patch也是叠加了冲突各方效果的psu patch包。对于psu patch这种复合的Patch包,我们需要知道这个包里面那个子patch与已经安装的patch产生冲突。在这个案例中,已经安装的patch 13004894与PSU PSU 11.2.0.3.7 与11.2.0.3.8有冲突。此时有同学要问了,我们要装的不是patch 11.2.0.3.11吗?怎么变成11.2.0.3.7了?
Dear Oracle team, Thanks for your update. 11.2.0.3.11 is PSU version, not DB version. The last digit denotes at what PSU level the environment is. Also PSU will not change the banner or binary version. You can confirm this by querying select * from v$version; Reference: Do Patchset Updates (PSU's) Change the Oracle Release Version/Fifth Digit? ( Doc ID 861152.1 ) PSU patches are composite. Suppose I have installed 11.2.0.3.4 PSU and applying 11.2.0.3.7 PSU, it will append fixes from 11.2.0.3.5 to 11.2.0.3.7 Old PSU will not be rolled back. In 10.2 and 11.1 old PSU will be rolled back while applying new PSU. In 11.2 it has been improved. Time to rollback old PSU is saved. More details at : Composite Patches for Oracle Products [Video] ( Doc ID 1376691.1 ) In our case the existing patches have conflict with Sub patches of PSU 11.2.0.3.11 while applying. Those conflicting sub patches are 11.2.0.3.7 and 11.2.0.3.8. Existing patch has conflict with fixes of sub patches. Hence we are applying overlay patches of those version. In case the above update is not clear or if you have any doubts, kindly let me know.
根据Oracle工程师的描述,11.2.0.3.11是一个PSU版本,而不是数据库版本。版本最后一位是代表该数据库PSU的版本。而我们的数据库是11.2.0.3,PSU不会改变它。参考(Doc ID 861152.1) PSU patches是复合的,比如我要从11.2.0.3.4打到11.2.0.3.7,这个PSU会先从11.2.0.3.4打到11.2.0.3.5,再从11.2.0.3.5打到11.2.0.3.7。 在10.2与11.1中,打新的PSU时,老的PSU会回滚。但在11.2中就不会。参考(Doc ID 1376691.1).
Dear Oracle team, Thanks for raising your queries. Query: As I know,18522512 was 11.2.0.3.11.After I apply it after (3),Why I should down psu11.2.0.3.7 at(4)?Did the psu 11.2.0.3.11 not contain 11.2.0.3.7? Ans: Yes, PSU 11.2.0.3.11 includes 11.2.0.3.7 PSU also. In 4th step we are downloading patch 13004894 of 11.2.0.3.7 version. While applying 11.2.0.3.11 PSU, it applies PSU patch 11.2.0.3.7 also which is not installed earlier. Existing Patch 13004894 has conflict with 11.2.0.3.7 PSU, hence we are applying 13004894 of 11.2.0.3.7 version Query: Apply PSU patch 18522512 Do you meadn I just put in "cd 18522512 opatch apply"?Should I "startup" and "@catbundle.sql psu apply"? We are applying patch only at binary level in 3rd step, i.e. opatch apply Database start up and catbundle execution is covered in step 7 We can do this step along with opatch apply, but for applying overlay patch (step 4) again we have to shutdown the database. To avoid that we apply all patches at binary first, then start the database to execute catbundle.sql
11.2.0.3.11的PSU是包含11.2.0.3.7的PSU的。Apply 11.2.0.3.11的PSU,是会先APPLY 11.2.0.3.7版本的。但是,已经存在的patch 13004894跟这个11.2.0.3.7 PSU有冲突,因此我们需要安装13004894的11.2.0.3.7版本,这个PSU,是会包含11.2.0.3.7的PSU与13004894这个patch的协调版本。
三,实际操作 Thanks for contacting oracle support.
PSU patch has conflict with existing installed patches.
Merge patch is available for this conflict. You can follow below steps to apply patch
1) Shutdown oracle services and then take backup of Oracle database, oracle home and central inventory
2) Rollback conflicting patches 13004894,12942119
opatch rollback -id
3) Apply PSU patch 18522512
4) Download following overlay patches from Oracle support,
https://updates.oracle.com/download/13004894.html
choose platform as 'Linux X86' and version as 11.2.0.3.7
p13004894_112037_LINUX.zip
https://updates.oracle.com/download/12942119.html
choose platform as 'Linux X86' and version as 11.2.0.3.8
p12942119_112038_LINUX.zip
5) Unzip the downloaded patches and apply. It will not have conflicts
6) Start the database
7) Perform PSU patch post Installation Instructions as specified in Patch Read me file
Please let me know if you require more details/assistance on any steps
We would like inform you about new MOS feature.
A new Patch Conflict Checker feature is available in the latest release of MOS. This is accessible from the Patch Search results screen ("Analyze with OPatch" button) and allows you to analyze candidate patches for conflicts and request merge fixes a lot more easily and quickly at the time of patch download itself. This feature allows you to:
1. Analyze patches for conflicts right at the time of patch download - All you need is your Opatch inventory.
2. Locate already available replacement patches – So, you can download resolution patches immediately.
3. Request a merge patch right there, if no replacement patches exist - You will not have to spend time logging a SR.
For more information and a demonstration video, please see Note 1091294.1 - How to use the My Oracle Support Conflict Checker Tool. Should you need assistance get started, I am glad to set up a call/web conference to walk you through the steps.
(1)停应用、监听、数据库; (2)rollback两个已经存在的patch ora@erpt1:erpt1 > opatch rollback -id 13004894
Oracle Interim Patch Installer version 11.2.0.3.6
Copyright (c) 2013, Oracle Corporation. All rights reserved.
Oracle Home : /u01/erpt1/db/tech_st/11.2.0
Central Inventory : /u01/oraInventory
from : /u01/erpt1/db/tech_st/11.2.0/oraInst.loc
OPatch version : 11.2.0.3.6
OUI version : 11.2.0.3.0
Log file location : /u01/erpt1/db/tech_st/11.2.0/cfgtoollogs/opatch/13004894_Jul_30_2014_11_45_32/rollback2014-07-30_11-45-31AM_1.log
RollbackSession rolling back interim patch '13004894' from OH '/u01/erpt1/db/tech_st/11.2.0'
Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.
(Oracle Home = '/u01/erpt1/db/tech_st/11.2.0')
Is the local system ready for patching? [y|n]
y
User Responded with: Y
Patching component oracle.rdbms, 11.2.0.3.0...
RollbackSession removing interim patch '13004894' from inventory
Log file location: /u01/erpt1/db/tech_st/11.2.0/cfgtoollogs/opatch/13004894_Jul_30_2014_11_45_32/rollback2014-07-30_11-45-31AM_1.log
OPatch succeeded.
ora@erpt1:erpt1 > opatch rollback -id 12942119
Oracle Interim Patch Installer version 11.2.0.3.6
Copyright (c) 2013, Oracle Corporation. All rights reserved.
Oracle Home : /u01/erpt1/db/tech_st/11.2.0
Central Inventory : /u01/oraInventory
from : /u01/erpt1/db/tech_st/11.2.0/oraInst.loc
OPatch version : 11.2.0.3.6
OUI version : 11.2.0.3.0
Log file location : /u01/erpt1/db/tech_st/11.2.0/cfgtoollogs/opatch/12942119_Jul_30_2014_11_47_21/rollback2014-07-30_11-47-21AM_1.log
RollbackSession rolling back interim patch '12942119' from OH '/u01/erpt1/db/tech_st/11.2.0'
Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.
(Oracle Home = '/u01/erpt1/db/tech_st/11.2.0')
Is the local system ready for patching? [y|n]
y
User Responded with: Y
Patching component oracle.rdbms, 11.2.0.3.0...
RollbackSession removing interim patch '12942119' from inventory
Log file location: /u01/erpt1/db/tech_st/11.2.0/cfgtoollogs/opatch/12942119_Jul_30_2014_11_47_21/rollback2014-07-30_11-47-21AM_1.log
OPatch succeeded.
ora@erpt1:erpt1 > (3)先apply PSU 18522512 ,就是cd 18522512 ,opatch apply.
ora@erpt1:erpt1 > cd 18522512
ora@erpt1:erpt1 > ls
13343438 13696216 13923374 14275605 14727310 16056266 16619892 16902043 17540582 18031683 18522512 patchmd.xml README.html README.txt ora@erpt1:erpt1 > opatch apply
Oracle Interim Patch Installer version 11.2.0.3.6
Copyright (c) 2013, Oracle Corporation. All rights reserved.
Oracle Home : /u01/erpt1/db/tech_st/11.2.0
Central Inventory : /u01/oraInventory
from : /u01/erpt1/db/tech_st/11.2.0/oraInst.loc
OPatch version : 11.2.0.3.6
OUI version : 11.2.0.3.0
Log file location : /u01/erpt1/db/tech_st/11.2.0/cfgtoollogs/opatch/opatch2014-07-30_11-49-30AM_1.log
Verifying environment and performing prerequisite checks...
Composite Patch 18522512 is a bug superset of 13001379,9858539 in OH.
Patches [ 13001379 9858539 ] will be rolled back.
Do you want to proceed? [y|n]
y
User Responded with: Y
OPatch continues with these patches: 13343438 13696216 13923374 14275605 14727310 16056266 16619892 16902043 17540582 18031683 18522512
Do you want to proceed? [y|n]
y
User Responded with: Y
All checks passed.
Provide your email address to be informed of security issues, install and
initiate Oracle Configuration Manager. Easier for you if you use your My
Oracle Support Email address/User Name.
Visit http://www.oracle.com/support/policies.html for details.
Email address/User Name:
You have not provided an email address for notification of security issues.
Do you wish to remain uninformed of security issues ([Y]es, [N]o) [N]: Y
Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.
(Oracle Home = '/u01/erpt1/db/tech_st/11.2.0')
Is the local system ready for patching? [y|n]
y
User Responded with: Y
Backing up files...
Applying sub-patch '13343438' to OH '/u01/erpt1/db/tech_st/11.2.0'
Rolling back interim patch '13001379' from OH '/u01/erpt1/db/tech_st/11.2.0'
Patching component oracle.rdbms, 11.2.0.3.0...
RollbackSession removing interim patch '13001379' from inventory
Rolling back interim patch '9858539' from OH '/u01/erpt1/db/tech_st/11.2.0'
Patching component oracle.rdbms, 11.2.0.3.0...
RollbackSession removing interim patch '9858539' from inventory
OPatch back to application of the patch '13343438' after auto-rollback.
Patching component oracle.rdbms.rsf, 11.2.0.3.0...
Patching component oracle.rdbms, 11.2.0.3.0...
Patching component oracle.rdbms.dbscripts, 11.2.0.3.0...
Verifying the update...
Applying sub-patch '13696216' to OH '/u01/erpt1/db/tech_st/11.2.0'
Patching component oracle.rdbms.rsf, 11.2.0.3.0...
Patching component oracle.rdbms, 11.2.0.3.0...
Patching component oracle.sdo.locator, 11.2.0.3.0...
Patching component oracle.sysman.console.db, 11.2.0.3.0...
Patching component oracle.sysman.oms.core, 10.2.0.4.4...
Verifying the update...
Applying sub-patch '13923374' to OH '/u01/erpt1/db/tech_st/11.2.0'
ApplySession: Optional component(s) [ oracle.network.cman, 11.2.0.3.0 ] not present in the Oracle Home or a higher version is found.
Patching component oracle.rdbms.rsf, 11.2.0.3.0...
Patching component oracle.rdbms, 11.2.0.3.0...
Patching component oracle.rdbms.dbscripts, 11.2.0.3.0...
Patching component oracle.network.rsf, 11.2.0.3.0...
Patching component oracle.network.listener, 11.2.0.3.0...
Patching component oracle.sysman.console.db, 11.2.0.3.0...
Verifying the update...
Applying sub-patch '14275605' to OH '/u01/erpt1/db/tech_st/11.2.0'
ApplySession: Optional component(s) [ oracle.precomp.lang, 11.2.0.3.0 ] not present in the Oracle Home or a higher version is found.
Patching component oracle.network.client, 11.2.0.3.0...
Patching component oracle.network.rsf, 11.2.0.3.0...
Patching component oracle.precomp.common, 11.2.0.3.0...
Patching component oracle.rdbms, 11.2.0.3.0...
Patching component oracle.rdbms.dbscripts, 11.2.0.3.0...
Patching component oracle.rdbms.rman, 11.2.0.3.0...
Patching component oracle.rdbms.rsf, 11.2.0.3.0...
Patching component oracle.rdbms.util, 11.2.0.3.0...
Verifying the update...
Applying sub-patch '14727310' to OH '/u01/erpt1/db/tech_st/11.2.0'
Patching component oracle.rdbms, 11.2.0.3.0...
Patching component oracle.rdbms.dbscripts, 11.2.0.3.0...
Patching component oracle.rdbms.rsf, 11.2.0.3.0...
Patching component oracle.sdo.locator, 11.2.0.3.0...
Patching component oracle.sysman.console.db, 11.2.0.3.0...
Patching component oracle.sysman.oms.core, 10.2.0.4.4...
Verifying the update...
Applying sub-patch '16056266' to OH '/u01/erpt1/db/tech_st/11.2.0'
ApplySession: Optional component(s) [ oracle.network.cman, 11.2.0.3.0 ] not present in the Oracle Home or a higher version is found.
Patching component oracle.network.listener, 11.2.0.3.0...
Patching component oracle.network.rsf, 11.2.0.3.0...
Patching component oracle.ovm, 11.2.0.3.0...
Patching component oracle.rdbms, 11.2.0.3.0...
Patching component oracle.rdbms.rman, 11.2.0.3.0...
Patching component oracle.rdbms.rsf, 11.2.0.3.0...
Patching component oracle.sdo.locator, 11.2.0.3.0...
Patching component oracle.rdbms.deconfig, 11.2.0.3.0...
Verifying the update...
Applying sub-patch '16619892' to OH '/u01/erpt1/db/tech_st/11.2.0'
ApplySession: Optional component(s) [ oracle.precomp.lang, 11.2.0.3.0 ] not present in the Oracle Home or a higher version is found.
Patching component oracle.marvel, 11.2.0.3.0...
Patching component oracle.precomp.common, 11.2.0.3.0...
Patching component oracle.rdbms, 11.2.0.3.0...
Patching component oracle.rdbms.rman, 11.2.0.3.0...
Patching component oracle.rdbms.rsf, 11.2.0.3.0...
Patching component oracle.sysman.agent, 10.2.0.4.3...
Patching component oracle.sysman.console.db, 11.2.0.3.0...
Patching component oracle.sysman.repository.core, 10.2.0.4.4...
Patching component oracle.xdk, 11.2.0.3.0...
Patching component oracle.xdk.parser.java, 11.2.0.3.0...
Patching component oracle.xdk.rsf, 11.2.0.3.0...
Verifying the update...
Applying sub-patch '16902043' to OH '/u01/erpt1/db/tech_st/11.2.0'
ApplySession: Optional component(s) [ oracle.idm.oid, 11.2.0.3.0 ] not present in the Oracle Home or a higher version is found.
Patching component oracle.ldap.rsf, 11.2.0.3.0...
Patching component oracle.ldap.rsf.ic, 11.2.0.3.0...
Patching component oracle.owb.rsf, 11.2.0.3.0...
Patching component oracle.rdbms, 11.2.0.3.0...
Patching component oracle.rdbms.rsf, 11.2.0.3.0...
Patching component oracle.sysman.console.db, 11.2.0.3.0...
Verifying the update...
Applying sub-patch '17540582' to OH '/u01/erpt1/db/tech_st/11.2.0'
ApplySession: Optional component(s) [ oracle.precomp.lang, 11.2.0.3.0 ] not present in the Oracle Home or a higher version is found.
Patching component oracle.rdbms, 11.2.0.3.0...
Patching component oracle.rdbms.rsf, 11.2.0.3.0...
Patching component oracle.sdo, 11.2.0.3.0...
Patching component oracle.ldap.rsf, 11.2.0.3.0...
Patching component oracle.precomp.common, 11.2.0.3.0...
Patching component oracle.ordim.client, 11.2.0.3.0...
Patching component oracle.rdbms.util, 11.2.0.3.0...
Patching component oracle.rdbms.dbscripts, 11.2.0.3.0...
Patching component oracle.sdo.locator, 11.2.0.3.0...
Patching component oracle.rdbms.rman, 11.2.0.3.0...
Patching component oracle.ordim.jai, 11.2.0.3.0...
Verifying the update...
Applying sub-patch '18031683' to OH '/u01/erpt1/db/tech_st/11.2.0'
ApplySession: Optional component(s) [ oracle.precomp.lang, 11.2.0.3.0 ] not present in the Oracle Home or a higher version is found.
Patching component oracle.rdbms.rsf, 11.2.0.3.0...
Patching component oracle.rdbms, 11.2.0.3.0...
Patching component oracle.ldap.rsf, 11.2.0.3.0...
Patching component oracle.precomp.common, 11.2.0.3.0...
Patching component oracle.rdbms.rman, 11.2.0.3.0...
Patching component oracle.rdbms.util, 11.2.0.3.0...
Patching component oracle.rdbms.dbscripts, 11.2.0.3.0...
Verifying the update...
Applying sub-patch '18522512' to OH '/u01/erpt1/db/tech_st/11.2.0'
Patching component oracle.rdbms.rsf, 11.2.0.3.0...
Patching component oracle.rdbms, 11.2.0.3.0...
Patching component oracle.network.rsf, 11.2.0.3.0...
Patching component oracle.precomp.common, 11.2.0.3.0...
Patching component oracle.rdbms.rman, 11.2.0.3.0...
Patching component oracle.rdbms.dbscripts, 11.2.0.3.0...
Verifying the update...
OPatch found the word "warning" in the stderr of the make command.
Please look at this stderr. You can re-run this make command.
Stderr output:
ins_precomp.mk:19: warning: overriding commands for target `pcscfg.cfg'
/u01/erpt1/db/tech_st/11.2.0/precomp/lib/env_precomp.mk:2160: warning: ignoring old commands for target `pcscfg.cfg'
/u01/erpt1/db/tech_st/11.2.0/precomp/lib/ins_precomp.mk:19: warning: overriding commands for target `pcscfg.cfg'
/u01/erpt1/db/tech_st/11.2.0/precomp/lib/env_precomp.mk:2160: warning: ignoring old commands for target `pcscfg.cfg'
OPatch found the word "warning" in the stderr of the make command.
Please look at this stderr. You can re-run this make command.
Stderr output:
ins_emagent.mk:113: warning: overriding commands for target `nmosudo'
ins_emagent.mk:52: warning: ignoring old commands for target `nmosudo'
/u01/erpt1/db/tech_st/11.2.0/sysman/lib/ins_emagent.mk:113: warning: overriding commands for target `nmosudo'
/u01/erpt1/db/tech_st/11.2.0/sysman/lib/ins_emagent.mk:52: warning: ignoring old commands for target `nmosudo'
Composite patch 18522512 successfully applied.
OPatch Session completed with warnings.
Log file location: /u01/erpt1/db/tech_st/11.2.0/cfgtoollogs/opatch/opatch2014-07-30_11-49-30AM_1.log
OPatch completed with warnings.
ora@erpt1:erpt1 >
(4)然后我们再下载13004894 这个与11.2.0.3.7 PSU能相融合的patch。再下载12942119这个能与11.2.0.3.8 PSU相融合的overlay Patch,并分别apply上。 (5)然后按照18522512 PSU的read me file里面的post Installation Instructions,进行catbundle。 sqlplus '/as sysdba' startup @catbundle.sql psu apply
我们必须先做(3),再做(4),(5),也就是说先PSU18522512 后,再打overlay patch,而不能是先做overlay patch。 否则会报这样的错。 [ora3@erpt1 13004894]$ opatch apply
Oracle Interim Patch Installer version 11.2.0.3.6
Copyright (c) 2013, Oracle Corporation. All rights reserved.
Oracle Home : /u03/erpt3/db/tech_st/11.2.0
Central Inventory : /u01/oraInventory
from : /u03/erpt3/db/tech_st/11.2.0/oraInst.loc
OPatch version : 11.2.0.3.6
OUI version : 11.2.0.3.0
Log file location : /u03/erpt3/db/tech_st/11.2.0/cfgtoollogs/opatch/13004894_Jul_31_2014_17_59_23/apply2014-07-31_17-59-22PM_1.log
Applying interim patch '13004894' to OH '/u03/erpt3/db/tech_st/11.2.0'
Verifying environment and performing prerequisite checks...
Prerequisite check "CheckPatchApplyDependents" failed.
The details are:
Interim patch 13004894 requires prerequisite patch(es) [ 16619892 ] which are not present in the Oracle Home.
Apply prerequisite patch(es) [ 16619892 ] before applying interim patch 13004894 .
Log file location: /u03/erpt3/db/tech_st/11.2.0/cfgtoollogs/opatch/13004894_Jul_31_2014_17_59_23/apply2014-07-31_17-59-22PM_1.log
Recommended actions: This patch requires some other patches to be installed in the Oracle Home. OPatch cannot find those required patches in the Oracle Home.
OPatch failed with error code 42 而这个16619892,正是产生冲突的那个sub patch。 完成。

MySQL과 Sqlite의 주요 차이점은 설계 개념 및 사용 시나리오입니다. 1. MySQL은 대규모 응용 프로그램 및 엔터프라이즈 수준의 솔루션에 적합하며 고성능 및 동시성을 지원합니다. 2. SQLITE는 모바일 애플리케이션 및 데스크탑 소프트웨어에 적합하며 가볍고 내부질이 쉽습니다.

MySQL의 인덱스는 데이터 검색 속도를 높이는 데 사용되는 데이터베이스 테이블에서 하나 이상의 열의 주문 구조입니다. 1) 인덱스는 스캔 한 데이터의 양을 줄임으로써 쿼리 속도를 향상시킵니다. 2) B-Tree Index는 균형 잡힌 트리 구조를 사용하여 범위 쿼리 및 정렬에 적합합니다. 3) CreateIndex 문을 사용하여 CreateIndexIdx_customer_idonorders (customer_id)와 같은 인덱스를 작성하십시오. 4) Composite Indexes는 CreateIndexIdx_customer_orderOders (Customer_id, Order_Date)와 같은 다중 열 쿼리를 최적화 할 수 있습니다. 5) 설명을 사용하여 쿼리 계획을 분석하고 피하십시오

MySQL에서 트랜잭션을 사용하면 데이터 일관성이 보장됩니다. 1) STARTTRANSACTION을 통해 트랜잭션을 시작한 다음 SQL 작업을 실행하고 커밋 또는 롤백으로 제출하십시오. 2) SavePoint를 사용하여 부분 롤백을 허용하는 저장 지점을 설정하십시오. 3) 성능 최적화 제안에는 트랜잭션 시간 단축, 대규모 쿼리 방지 및 격리 수준을 합리적으로 사용하는 것이 포함됩니다.

MySQL 대신 PostgreSQL을 선택한 시나리오에는 다음이 포함됩니다. 1) 복잡한 쿼리 및 고급 SQL 기능, 2) 엄격한 데이터 무결성 및 산 준수, 3) 고급 공간 기능이 필요하며 4) 큰 데이터 세트를 처리 할 때 고성능이 필요합니다. PostgreSQL은 이러한 측면에서 잘 수행되며 복잡한 데이터 처리 및 높은 데이터 무결성이 필요한 프로젝트에 적합합니다.

MySQL 데이터베이스의 보안은 다음 조치를 통해 달성 할 수 있습니다. 1. 사용자 권한 관리 : CreateUser 및 Grant 명령을 통한 액세스 권한을 엄격히 제어합니다. 2. 암호화 된 전송 : 데이터 전송 보안을 보장하기 위해 SSL/TLS를 구성합니다. 3. 데이터베이스 백업 및 복구 : MySQLDump 또는 MySQLPump를 사용하여 정기적으로 백업 데이터를 사용하십시오. 4. 고급 보안 정책 : 방화벽을 사용하여 액세스를 제한하고 감사 로깅 작업을 가능하게합니다. 5. 성능 최적화 및 모범 사례 : 인덱싱 및 쿼리 최적화 및 정기 유지 보수를 통한 안전 및 성능을 모두 고려하십시오.

MySQL 성능을 효과적으로 모니터링하는 방법은 무엇입니까? Mysqladmin, Showglobalstatus, Perconamonitoring and Management (PMM) 및 MySQL Enterprisemonitor와 같은 도구를 사용하십시오. 1. MySQLADMIN을 사용하여 연결 수를보십시오. 2. showglobalstatus를 사용하여 쿼리 번호를보십시오. 3.pmm은 자세한 성능 데이터 및 그래픽 인터페이스를 제공합니다. 4. MySQLENTERPRISOMITOR는 풍부한 모니터링 기능 및 경보 메커니즘을 제공합니다.

MySQL과 SqlServer의 차이점은 1) MySQL은 오픈 소스이며 웹 및 임베디드 시스템에 적합합니다. 2) SQLServer는 Microsoft의 상용 제품이며 엔터프라이즈 수준 애플리케이션에 적합합니다. 스토리지 엔진의 두 가지, 성능 최적화 및 응용 시나리오에는 상당한 차이가 있습니다. 선택할 때는 프로젝트 규모와 향후 확장 성을 고려해야합니다.

고 가용성, 고급 보안 및 우수한 통합이 필요한 엔터프라이즈 수준의 응용 프로그램 시나리오에서는 MySQL 대신 SQLServer를 선택해야합니다. 1) SQLServer는 고 가용성 및 고급 보안과 같은 엔터프라이즈 수준의 기능을 제공합니다. 2) VisualStudio 및 Powerbi와 같은 Microsoft Ecosystems와 밀접하게 통합되어 있습니다. 3) SQLSERVER는 성능 최적화에서 우수한 성능을 발휘하며 메모리 최적화 된 테이블 및 열 스토리지 인덱스를 지원합니다.


핫 AI 도구

Undresser.AI Undress
사실적인 누드 사진을 만들기 위한 AI 기반 앱

AI Clothes Remover
사진에서 옷을 제거하는 온라인 AI 도구입니다.

Undress AI Tool
무료로 이미지를 벗다

Clothoff.io
AI 옷 제거제

Video Face Swap
완전히 무료인 AI 얼굴 교환 도구를 사용하여 모든 비디오의 얼굴을 쉽게 바꾸세요!

인기 기사

뜨거운 도구

SecList
SecLists는 최고의 보안 테스터의 동반자입니다. 보안 평가 시 자주 사용되는 다양한 유형의 목록을 한 곳에 모아 놓은 것입니다. SecLists는 보안 테스터에게 필요할 수 있는 모든 목록을 편리하게 제공하여 보안 테스트를 더욱 효율적이고 생산적으로 만드는 데 도움이 됩니다. 목록 유형에는 사용자 이름, 비밀번호, URL, 퍼징 페이로드, 민감한 데이터 패턴, 웹 셸 등이 포함됩니다. 테스터는 이 저장소를 새로운 테스트 시스템으로 간단히 가져올 수 있으며 필요한 모든 유형의 목록에 액세스할 수 있습니다.

드림위버 CS6
시각적 웹 개발 도구

DVWA
DVWA(Damn Vulnerable Web App)는 매우 취약한 PHP/MySQL 웹 애플리케이션입니다. 주요 목표는 보안 전문가가 법적 환경에서 자신의 기술과 도구를 테스트하고, 웹 개발자가 웹 응용 프로그램 보안 프로세스를 더 잘 이해할 수 있도록 돕고, 교사/학생이 교실 환경 웹 응용 프로그램에서 가르치고 배울 수 있도록 돕는 것입니다. 보안. DVWA의 목표는 다양한 난이도의 간단하고 간단한 인터페이스를 통해 가장 일반적인 웹 취약점 중 일부를 연습하는 것입니다. 이 소프트웨어는

SublimeText3 영어 버전
권장 사항: Win 버전, 코드 프롬프트 지원!

에디트플러스 중국어 크랙 버전
작은 크기, 구문 강조, 코드 프롬프트 기능을 지원하지 않음
