在新版Oracle MOS 上面申请过时或受密码保护补丁指南 - 重庆思庄Oracle、KingBase、PostgreSQL、Redhat认证学习论坛

710516a2a578647632.png (246.67 KB, 下载次数: 0)

6 天前上传

第二步：填写请求

1. 在“Select a product or service”一栏中选择 “Oracle Database - Enterprise Edition”

929856a2a578db7ade.png (112.05 KB, 下载次数: 0)

6 天前上传

2.在详细信息里面填写需求，模板如下：

Subject: Request Download Permission for Obsolete/Password-Protected Patch <补丁号>
Description: Hello Team,
We urgently need to download the following historical patch which is currently not directly downloadable or password-protected on My Oracle Support:
• Patch Number: <补丁号>
• Patch Description: <补丁全名>
• Platform: [请在此处填写你的操作系统平台，例如：Linux x86-64 / IBM AIX on POWER Systems (64-bit)]
Business Justification: We are currently performing an environment alignment and testing procedure. Our existing production environment has already applied this specific <补丁信息>. To ensure strict environment consistency and eliminate any potential compatibility risks during our validation/migration testing, we must use the exact same patch version in our test environment rather than a newer release.
Could you please grant the download permission or provide the password for this patch?
Thank you for your support.

比如我想要一个OJVM补丁：OJVM PATCH SET UPDATE 11.2.0.4.181016，平台Linux x86-64，该补丁号为28440700

Subject: Request Download Permission for Obsolete/Password-Protected Patch 28440700
Description: Hello Team,
We urgently need to download the following historical patch which is currently not directly downloadable or password-protected on My Oracle Support:
• Patch Number: 28440700
• Patch Description: OJVM PATCH SET UPDATE 11.2.0.4.181016
• Platform: Linux x86-64
Business Justification: We are currently performing an environment alignment and testing procedure. Our existing production environment has already applied this specific OJVM patch version (11.2.0.4.181016). To ensure strict environment consistency and eliminate any potential compatibility risks during our validation/migration testing, we must use the exact same patch version in our test environment rather than a newer release.
Could you please grant the download permission or provide the password for this patch?
Thank you for your support.

填写完成后提交即可

284756a2a579805a79.png (267.76 KB, 下载次数: 0)

下载附件

6 天前上传

在弹出的提示框选择“Start AI Support Assistant”

389756a2a579d23415.png (22.63 KB, 下载次数: 0)

下载附件

6 天前上传

在弹出的AI会话中选择创建SR服务

395856a2a57a2dd8ce.png (132.76 KB, 下载次数: 0)

下载附件

6 天前上传

第三步：填写SR服务申请资料

创建SR后，系统会自动识别请求信息和类别，如下所示，保持默认即可，若有问题可手动修改

例如总结可以改成：
Unable to download historical patch 28440700 for OJVM PATCH SET UPDATE 11.2.0.4.181016 on Linux.

554986a2a57fc0ddda.png (261.84 KB, 下载次数: 0)

下载附件

6 天前上传

继续填写

489446a2a58043202f.png (176.22 KB, 下载次数: 0)

下载附件

6 天前上传

填写产品版本，运行环境，系统生命周期以及问题分类，如下所示

609676a2a580da700d.png (254.48 KB, 下载次数: 0)

下载附件

6 天前上传

填写平台类型、版本

红色字：提示 19.29 或 19.30 版本有个 RAC 滚动升级的 Bug 会导致数据损坏，我这里申请的是 11g 补丁，直接无视

蓝色框：Oracle 官方提示：“我们最近发了高优先级安全公告，为了安全和稳定，强烈建议你用最新的 Release Updates (RUs)，别用老补丁了。” 不用理它，直接往下走

Select the Best Option (再次细化分类)
当前状态：选择“Request Password protected patches for Quarterly Patch Releases”
以及“ Password Request for any Other DB Version”（其他任意数据库版本的密码请求）

因为 11g 已经属于非常老的“Other DB Version”了，系统这个自动归类非常精准，保持这个选项不要动。

760196a2a58179564b.png (300.15 KB, 下载次数: 0)

下载附件

6 天前上传

填写补丁号以及业务理由，可以用下面的语句：

We are currently performing an environment alignment and testing procedure. Our existing production environment has already applied this specific OJVM patch version (11.2.0.4.181016). To ensure strict environment consistency and eliminate any potential compatibility risks during our validation and migration testing, we must use the exact same patch version in our test environment rather than a newer release.

这段话的意思是：“我们目前正在进行环境对齐和测试。我们现有的生产环境已经应用了这个特定的 OJVM 补丁版本（11.2.0.4.181016）。为了确保严格的环境一致性，并消除验证和迁移测试期间任何潜在的兼容性风险，我们必须在测试环境中使用完全相同的补丁版本，而不是更新的版本。”