FAQ: Webcenter Sites 12.2.1.x Patching
(Doc ID 2735439.1)
Last updated on JULY 26, 2023
Applies to:
Oracle WebCenter Sites - Version 12.2.1.3.0 and laterInformation in this document applies to any platform.
Purpose
This article will answer some frequently asked questions about applying patch.
Questions and Answers
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Purpose |
Questions and Answers |
1. How to check if customer is using a certified version of JDK? |
2. How can customers check if they have latest Oracle Fusion Middleware Infrastructure (WebLogic Server for FMW) patch and corresponding Coherence patch too? |
4. Do customers need to stop the node managers at this step: “Stop all servers (AdminServer and all Managed server(s)).” |
5. If customer has a previously applied Sites Patch, does the opatch rolls back it automatically? |
6. What needs to be done for the below step, on a NIO based system: “Take the backup of your current <sites_shared>/elements folder.” |
7. “Remove the property value "12.2.1.x.xxxxx" from oracle.wcsites.bootstrap.patch.status property in config/wcs_properties_bootstrap.ini file”. Why is this not done when rolling back the patch? |
8. Where to get Catalog Mover for 12.2.1.x? |
9. How to run Catalog Mover if there is no GUI? |
10. If sitespatchsetup url fails to run, can the elements be imported manually? |
12. Are there any new behavior observed after applying Patch 31548912 (Sites 12.2.1.4.200714)? |
13. In the Pre-Installation Instructions why is the wcsites.app.port required to have Global checkbox enabled? |
14. What if valid.urls property has not been set prior to Sites 12.2.1.4.211019? |
15. Can you publish between different patch levels in 12.2.1.4.0? |
References |