Adpatch Mode FAQ
1.如何从数据库查询当前系统是否处于Maintainance模式
SQL> SELECT FND_PROFILE.VALUE('APPS_MAINTENANCE_MODE') FROM DUAL;
If it is in Maintenance Mode the above query will show as follows:FND_PROFILE.VALUE('APPS_MAINTENANCE_MODE')
---------------------------------------------------------
MAINT
If it is not in Maintenance Mode the above query will show as follows:
FND_PROFILE.VALUE('APPS_MAINTENANCE_MODE')
---------------------------------------------------------
NORMAL
2.其他AD命令是否也要用到Maintainance Mode
Maintainance Mode只用于adpatch，其他AD命令不会涉及Maintainance Mode。
3.启用Maintainance Mode之后是否需要停止Apps Server再打patch
Oracle官方推荐停止Apps Server，再打patch，这样打patch的性能会好一些，尤其是文件比较多的情况。如果patch比较小，可以不用停止服务器。
4.hotpatch vs maintainance mode
Oracle官方推荐打patch的方式是maintainance mode，这样打patch性能会更好，出现问题的风险几率比较小。
不是所有的patch都可以使用hotpatch模式。
5.WHEN HOT PATCH CAN BE USED？
If the patch is small and only affects a limited number of objects such as an updated form or report or perhaps just a database
package or two, then you could *potentially* apply the patch to a live environment.
6.WHEN HOT PATCH CAN **NOT** BE USED
> Patches that make changes to executables,
> Makes numerous database changes,
> has new Java code,
> Adds/changes seed data,
> Large patches, etc. could not realistically be applied to a live environment.
Depending on what's being changed, then you could need to bounce the Concurrent Manager, forms server, web server, database, etc. for changes to take effect.
Some changes (like a database change) would take effect immediately though, and lead to possible corruption due to a
mismatch in code.
Your environment would not have the complete fix until it was bounced. Even with using the "hotpatch" flag, it still all depends on
what the patch itself is changing on whether you need to bounce or not. or anything more than a one-off patch in which I know exactly what's being changed, I would not apply patches to a live environment, especially production.
7.什么样的patch”必须“使用maintanance模式
Standalone/Oneoff patches
Mini Packs
Family Packs
Maintenance Packs
NLS Patchs
8.What internally happen when we enable the maintenance mode?
Maintenance mode provides a clear separation between normal runtime operation of Oracle Applications and system downtime for maintenance.
9.Is there any difference between enabling maintenance mode and shutting down middle-tier services?
Enabling the maintenance mode feature shuts down the Workflow Business Events System and sets up function security so that no Oracle Applications functions are available to users. Used only during AutoPatch sessions, maintenance mode ensures optimal performance and reduces downtime when applying a patch. For more information, refer to Preparing your System for Patching in Oracle Applications Maintenance Utilities.
参考：
Maintenance Mode - A New Feature in 11.5.10 (Doc ID 291901.1)
How To Apply Patch without Enabling Maintenance Mode (Doc ID 375130.1)
https://forums.oracle.com/forums/thread.jspa?messageID=9223409
转载请注明出处： http://blog.csdn.net/pan_tian/article/details/7872817
===EOF===
SQL> SELECT FND_PROFILE.VALUE('APPS_MAINTENANCE_MODE') FROM DUAL;
If it is in Maintenance Mode the above query will show as follows:FND_PROFILE.VALUE('APPS_MAINTENANCE_MODE')
---------------------------------------------------------
MAINT
If it is not in Maintenance Mode the above query will show as follows:
FND_PROFILE.VALUE('APPS_MAINTENANCE_MODE')
---------------------------------------------------------
NORMAL
2.其他AD命令是否也要用到Maintainance Mode
Maintainance Mode只用于adpatch，其他AD命令不会涉及Maintainance Mode。
3.启用Maintainance Mode之后是否需要停止Apps Server再打patch
Oracle官方推荐停止Apps Server，再打patch，这样打patch的性能会好一些，尤其是文件比较多的情况。如果patch比较小，可以不用停止服务器。
4.hotpatch vs maintainance mode
Oracle官方推荐打patch的方式是maintainance mode，这样打patch性能会更好，出现问题的风险几率比较小。
不是所有的patch都可以使用hotpatch模式。
5.WHEN HOT PATCH CAN BE USED？
If the patch is small and only affects a limited number of objects such as an updated form or report or perhaps just a database
package or two, then you could *potentially* apply the patch to a live environment.
6.WHEN HOT PATCH CAN **NOT** BE USED
> Patches that make changes to executables,
> Makes numerous database changes,
> has new Java code,
> Adds/changes seed data,
> Large patches, etc. could not realistically be applied to a live environment.
Depending on what's being changed, then you could need to bounce the Concurrent Manager, forms server, web server, database, etc. for changes to take effect.
Some changes (like a database change) would take effect immediately though, and lead to possible corruption due to a
mismatch in code.
Your environment would not have the complete fix until it was bounced. Even with using the "hotpatch" flag, it still all depends on
what the patch itself is changing on whether you need to bounce or not. or anything more than a one-off patch in which I know exactly what's being changed, I would not apply patches to a live environment, especially production.
7.什么样的patch”必须“使用maintanance模式
Standalone/Oneoff patches
Mini Packs
Family Packs
Maintenance Packs
NLS Patchs
8.What internally happen when we enable the maintenance mode?
Maintenance mode provides a clear separation between normal runtime operation of Oracle Applications and system downtime for maintenance.
9.Is there any difference between enabling maintenance mode and shutting down middle-tier services?
Enabling the maintenance mode feature shuts down the Workflow Business Events System and sets up function security so that no Oracle Applications functions are available to users. Used only during AutoPatch sessions, maintenance mode ensures optimal performance and reduces downtime when applying a patch. For more information, refer to Preparing your System for Patching in Oracle Applications Maintenance Utilities.
参考：
Maintenance Mode - A New Feature in 11.5.10 (Doc ID 291901.1)
How To Apply Patch without Enabling Maintenance Mode (Doc ID 375130.1)
https://forums.oracle.com/forums/thread.jspa?messageID=9223409
转载请注明出处： http://blog.csdn.net/pan_tian/article/details/7872817
===EOF===