FMW 11.1.2.3.1.0 Applying Patch 21118593: OAM WEBGATE BUNDLE PATCH 11.1.2.3.1
Pre-requisites
- Download Patch 21118593 (p21118593_111230_Linux-x86-64.zip)
- Set environment variable like ORACLE_HOME, PATH, etc
export ORACLE_HOME= export ORACLE_HOME=$MW_HOME/oamwebgate11
Please note Access Manager 11g Release 1 (11.1.2.0.0) WebGates are the required base for WebGate Bundle Patch 11.1.2.3.1
It is recommended that you apply the WebGate bundle patch to all installed WebGates for which a bundle patch is provided.
Apply patch 21118593
- Unzip the patch
unzip -d PATCH_TOP p21118593_111200_platform.zip
- Turn off the web server
- cd $MW_HOME/PATCH_TOP/21118593
- Run opatch apply
$ORACLE_HOME/OPatch/opatch apply -invPtrLoc $ORACLE_HOME/oraInst.loc
- Verify the patch
$ORACLE_HOME/OPatch/opatch lsinventory -invPtrLoc $ORACLE_HOME/oraInst.loc
- Restart the Web server.
If you have multiple instances, you must repeat these steps for each WebGate.
Patch De-installation
If any issues after applying the patch and rollback is needed, follow below steps:
- Stop the WebGate Web server
- cd $MW_HOME/PATCH_TOP/21118593
- Run opatch rollback
$ opatch rollback -id 21118593
- Restart the WebGate Web server
If you have multiple instances, you must repeat these steps for each WebGate.
Related Posts:
FMW 11.1.1.7.0 - Apply Oracle Virtual Directory Patch 17391582: OVD FOR IAM1112 BUNDLE PATCH 11.1.1.7.1
Showing posts with label OAM. Show all posts
Showing posts with label OAM. Show all posts
Sunday, 17 January 2016
FMW 11.1.2.3.1.0 Applying Patch 21118593: OAM WEBGATE BUNDLE PATCH 11.1.2.3.1
Labels:
11.1.2.0.0,
21118593,
FMW,
FMW 11.1.2.3.1.0,
http,
OAM,
OAM 11.1.2.3.1,
OAM WEBGATE BUNDLE PATCH,
oamwebgate11,
Oracle Access Manager,
p21118593_111230_Linux-x86-64.zip,
Web Server,
Webgate
Wednesday, 13 January 2016
Error oracle.xdo.servlet.CreateException:Report definition not found: /Oracle_Fusion_Middleware_Audit/Common_Reports/User_Activities/Event_Details/Event_Details.xdo [username=weblogicbi] when using 11g BI with OAM report in 10g format
Error oracle.xdo.servlet.CreateException:Report definition not found: /Oracle_Fusion_Middleware_Audit/Common_Reports/User_Activities/Event_Details/Event_Details.xdo [username=weblogicbi] when using 11g BI with OAM report in 10g format
Error
The report cannot be rendered because of an error, please contact the administrator.
Error Detail
Using Business Intelligence publisher to view Oracle Access Manager reports. The Event_Details.xdo report looks fine,
but when clicking on details link under "Event Details" column, the following exception occurs:
oracle.xdo.servlet.CreateException:Report definition not found: /Oracle_Fusion_Middleware_Audit/Common_Reports/User_Activities/Event_Details/Event_Details.xdo [username=weblogicbi]
To resolve this issue, upgrade OAM11g Reports using BIP tool following below steps:
Backup repository directory
$MW_HOME/config/domains/bi_domain/config/bipublisher/repository
Copy AuditReportTemplates.jar
From: $MW_HOME/fmw/112/oracle_common/modules/oracle.iau_11.1.1/reports/AuditReportTemplates.jar
To: $MW_HOME/config/domains/bi_domain/config/bipublisher/repository/Reports
Extract AuditReportTemplates.jar
cd $MW_HOME/config/domains/bi_domain/config/bipublisher/repository/Reports
jar xf AuditReportTemplates.jar
Upgrading Oracle Business Intelligence (BI) Publisher Repository from 10g to 11g
Follow the steps in this post Upgrading Oracle Business Intelligence (BI) Publisher Repository from 10g to 11g
Copy Reports Folder
Copy $MW_HOME/newrep/Reports to $MW_HOME/config/domains/bi_domain/config/bipublisher/repository. Copy only Reports folder
- Start the services.
- Access the reports in Shared Folder > Oracle Fusion Middleware > Common _reports
You may remove OAM folders from below path and use use Common Reports under Oracle_Fusion_Middleware_Audit.There is no need to unzip oam_audit_reports_11_1_2_0_0.zip
/repository/Reports/
/repository/Reports/Oracle_Fusion_Middleware_Audit/Component_Specific
To have OAM specific folder below Oracle_Fusion_Middleware_Audit/Component_Specific, then one needs to unzip oam_audit_reports_11_1_2_0_0.zip f both places.
/repository/Reports/
/repository/Reports/Oracle_Fusion_Middleware_Audit/Component_Specific
Related Posts:
OBIEE Patch 18277370 conflicts with Patch 17611288 installed during OBIA 11.1.1.8.1 installation
Oracle Business Intelligence Enterprise Edition Plus Client 11.1.1.7.0 Installation - Oracle BI Client Installer (64-bit) biee_client_install_x64.exe
Applying OBIA 11g: PATCH OBIEE 11.1.1.7.150120 for for Oracle Business Intelligence Enterprise Edition and Exalytics
[OracleBIServerComponent] [ERROR:1] [] [] [ecid: ] [tid: 1464] [nQSError: 93001] Can not load library, oracore11.dll, due to, The specified module could not be found error in OBIEE 11g NQSAdminTool.log file
OBI 11.1.1.8.1 - nQSError : 62022 Javahost has not been configured correctly. Please check your configuration in NQSConfig.ini
Error
The report cannot be rendered because of an error, please contact the administrator.
Error Detail
Using Business Intelligence publisher to view Oracle Access Manager reports. The Event_Details.xdo report looks fine,
but when clicking on details link under "Event Details" column, the following exception occurs:
oracle.xdo.servlet.CreateException:Report definition not found: /Oracle_Fusion_Middleware_Audit/Common_Reports/User_Activities/Event_Details/Event_Details.xdo [username=weblogicbi]
To resolve this issue, upgrade OAM11g Reports using BIP tool following below steps:
Backup repository directory
$MW_HOME/config/domains/bi_domain/config/bipublisher/repository
Copy AuditReportTemplates.jar
From: $MW_HOME/fmw/112/oracle_common/modules/oracle.iau_11.1.1/reports/AuditReportTemplates.jar
To: $MW_HOME/config/domains/bi_domain/config/bipublisher/repository/Reports
Extract AuditReportTemplates.jar
cd $MW_HOME/config/domains/bi_domain/config/bipublisher/repository/Reports
jar xf AuditReportTemplates.jar
Upgrading Oracle Business Intelligence (BI) Publisher Repository from 10g to 11g
Follow the steps in this post Upgrading Oracle Business Intelligence (BI) Publisher Repository from 10g to 11g
Copy Reports Folder
Copy $MW_HOME/newrep/Reports to $MW_HOME/config/domains/bi_domain/config/bipublisher/repository. Copy only Reports folder
- Start the services.
- Access the reports in Shared Folder > Oracle Fusion Middleware > Common _reports
You may remove OAM folders from below path and use use Common Reports under Oracle_Fusion_Middleware_Audit.There is no need to unzip oam_audit_reports_11_1_2_0_0.zip
/repository/Reports/
/repository/Reports/Oracle_Fusion_Middleware_Audit/Component_Specific
To have OAM specific folder below Oracle_Fusion_Middleware_Audit/Component_Specific, then one needs to unzip oam_audit_reports_11_1_2_0_0.zip f both places.
/repository/Reports/
/repository/Reports/Oracle_Fusion_Middleware_Audit/Component_Specific
Related Posts:
OBIEE Patch 18277370 conflicts with Patch 17611288 installed during OBIA 11.1.1.8.1 installation
Oracle Business Intelligence Enterprise Edition Plus Client 11.1.1.7.0 Installation - Oracle BI Client Installer (64-bit) biee_client_install_x64.exe
Applying OBIA 11g: PATCH OBIEE 11.1.1.7.150120 for for Oracle Business Intelligence Enterprise Edition and Exalytics
[OracleBIServerComponent] [ERROR:1] [] [] [ecid: ] [tid: 1464] [nQSError: 93001] Can not load library, oracore11.dll, due to, The specified module could not be found error in OBIEE 11g NQSAdminTool.log file
OBI 11.1.1.8.1 - nQSError : 62022 Javahost has not been configured correctly. Please check your configuration in NQSConfig.ini
Friday, 8 January 2016
OAAM 11.1.2.1.3 - Redeploying the OAAM Shared Library in Oracle WebLogic after applying Patch 19162894
OAAM 11.1.2.1.3 - Redeploying the OAAM Shared Library in Oracle WebLogic after applying Patch 19162894
Redeploying the OAAM Shared Library in Oracle WebLogic is one of the post patching steps after applying Patch 19162894. Refer to this post for more details.
If you have a native integration, redeploy the OAAM shared library by following these steps:
http://hostname:port/console
or
https://hostname:port/console
On the Welcome screen, log in using the user name and password
Redeploying the OAAM Shared Library in Oracle WebLogic is one of the post patching steps after applying Patch 19162894. Refer to this post for more details.
If you have a native integration, redeploy the OAAM shared library by following these steps:
- Start the managed server.
http://hostname:port/console
or
https://hostname:port/console
On the Welcome screen, log in using the user name and password
- In the Domain Structure section of the console, click Deployments. The Summary of Deployments page is displayed.
- In the Summary of Deployments page, select oracle.oaam.libs in the Deployments table and then click Delete.
- In Change Center, click Activate Changes for the changes to take effect.
- Click the Install button.
- In the path field, specify the path to the oaam_native_lib.war file, including the file name.
- Select oaam_native_lib.war and Next.
- On the next screen, select the Install this deployment as a library option and click Next.
- In the Select Deployments targets page, select the managed server from the list of servers to deploy the shared library, oracle.oaam.libs, and click Next and Click Finish.
- In the Change Center, click Activate Changes for the changes to take effect.
Related Posts:
Applying OAAM 11.1.2.1.3 - Patch 19162894 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
Applying OAAM 11.1.2.1.3 - Patch 19162894 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
FMW 11.1.1.6.0 - Oracle Platform Security for Java - Applying Patch 15894053: TRACKING BUG FOR OPATCH DELIVERY OF ENTSEC_11.1.1.6.0-IDM11.1.2.1.0_GENERIC
FMW 11.1.1.6.2 JPS for IAM 11.1.2 - Oracle Virtual Directory Patch 14603262: IDS USER/GROUP NAME ATTR NOT MAPPED CORRECTLY TO CONFIGURED VALUES IN OPCONFIG
Applying OPSS 11.1.1.6.3 Patch 18629534 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
Applying OES 11.1.2.1.1 - Patch 18629535 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
Applying OAM 11.1.2.1.4 - Patch 19162892 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
OAAM 11.1.2.1.3 - Redeploying OAAM applications in Oracle WebLogic Server after applying Patch 19162894
FMW 11.1.1.6.2 JPS for IAM 11.1.2 - Oracle Virtual Directory Patch 14603262: IDS USER/GROUP NAME ATTR NOT MAPPED CORRECTLY TO CONFIGURED VALUES IN OPCONFIG
Applying OPSS 11.1.1.6.3 Patch 18629534 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
Applying OES 11.1.2.1.1 - Patch 18629535 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
Applying OAM 11.1.2.1.4 - Patch 19162892 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
OAAM 11.1.2.1.3 - Redeploying OAAM applications in Oracle WebLogic Server after applying Patch 19162894
Labels:
19157616,
19162892,
19162894,
6880880,
IDM,
IDM 11.1.2.1.5,
OAAM,
OAAM 11.1.2.1.3,
OAM,
OAM 11.1.2.1.4,
oam-admin-was.ear,
oam-server.ear,
OES 11.1.2.1.1,
opatch,
OPSS 11.1.1.6.3,
redeploy shared library
OAAM 11.1.2.1.3 - Redeploying OAAM applications in Oracle WebLogic Server after applying Patch 19162894
OAAM 11.1.2.1.3 - Redeploying OAAM applications in Oracle WebLogic Server after applying Patch 19162894
Redeploying the OAAM applications is one of the post patching steps after applying Patch 19162894. Refer to this post for more details.
To redeploy the OAAM applications, follow these steps:
MW_HOME/user_projects/domains/domain_home/servers/oaam_admin_server1/tmp
MW_HOME/user_projects/domains/domain_home/servers/oaam_server_server1/tmp
MW_HOME/user_projects/domains/domain_home/servers/oaam_offline_server1/tmp
Start all servers.
or
https://hostname:port/console
1) In the Domain Structure section of the console, click Deployments. The Summary of Deployments page is displayed.
2) Select oaam_admin in the Deployments table and click Update.
3) In the Domain Structure section of the console, click Deployments.
4) In the Summary of Deployments page, select oaam_admin in the Deployments table.
5) Use the Stop drop-down list to select Force Stop Now.
Again select oaam_admin and then click Delete.
6) On the right, under Deployments, click Install.
When locating the deployment to install, provide the location of the oaam_admin.ear file in the Path field. You must include the file name, oaam_admin.ear, when specifying the path.
On the next screen, choose Install this deployment as an application as the targeting style and click Next.
On the next screen, select the OAAM Admin Server as the target for oaam_admin. For example, select the target oaam_admin_server1.
On the next screen for optional settings, make sure you select 'I will make the deployment accessible from the following location' and point to the location where the oaam_admin.ear file will be accessible:
Oracle_IDM/oaam/oaam_admin/ear/oaam_admin.ear
Click Finish to complete the deployment of oaam_admin.
7) Log in to the OAAM Admin Console.
In the Navigation tree, double-click Properties under Environment.
In the Properties page, search for the oaam.taskflow.enum.sessionaddtogroup property.
Select the oaam.taskflow.enum.sessionaddtogroup.name property and click Save.
Saving the property will change it from a file load type property to a database type property. The property is now available in the database.
If the oaam.taskflow.enum.sessionaddtogroup.name property does not exist, create it.
Click the New Property button or Create new Property icon.
In the New Property dialog, type in oaam.taskflow.enum.sessionaddtogroup.name as the property name and SessionAddToGroup as the property value.
Click Save to save the property.
8) Restart the OAAM Admin server.
9) Update and activate changes for OAAM Server.
In the Domain Structure section of the console, click Deployments.
In the Summary of Deployments page, select oaam_server in the deployment table and click Update.
In the Change Center, click Activate Changes for the changes to take effect.
10) Update and activate changes for OAAM Offline.
In the Domain Structure section of the console, click Deployments.
Select the oaam_offline application in the deployment table and click Update.
In the Change Center, click Activate Changes for the changes to take effect.
If you find that oaam_admin, oaam_server, and oaam_offline are not in the Active state, then select the appropriate server and click Start.
When you have applied the OAAM 11.1.2.1.3 patch (19162894), version information is shown when you click the About link on the right side bottom corner. The version information should appear as Version 11.1.2.1.0 (11.1.2.1.0.OAAM_11.1.2.1.0BP_GENERIC_140828.0325).
Redeploying the OAAM applications is one of the post patching steps after applying Patch 19162894. Refer to this post for more details.
To redeploy the OAAM applications, follow these steps:
- Delete the content from the OAAM Admin server (oaam_admin_server1), OAAM Server server (oaam_server_server1), OAAM Offline server (oaam_offline_server1) temp directories:
MW_HOME/user_projects/domains/domain_home/servers/oaam_admin_server1/tmp
MW_HOME/user_projects/domains/domain_home/servers/oaam_server_server1/tmp
MW_HOME/user_projects/domains/domain_home/servers/oaam_offline_server1/tmp
Start all servers.
- Log in to the WebLogic Administration Console. Open a web browser and enter the URL:
or
https://hostname:port/console
- Redeploy the oaam_admin application by performing these steps:
1) In the Domain Structure section of the console, click Deployments. The Summary of Deployments page is displayed.
2) Select oaam_admin in the Deployments table and click Update.
3) In the Domain Structure section of the console, click Deployments.
4) In the Summary of Deployments page, select oaam_admin in the Deployments table.
5) Use the Stop drop-down list to select Force Stop Now.
Again select oaam_admin and then click Delete.
6) On the right, under Deployments, click Install.
When locating the deployment to install, provide the location of the oaam_admin.ear file in the Path field. You must include the file name, oaam_admin.ear, when specifying the path.
On the next screen, choose Install this deployment as an application as the targeting style and click Next.
On the next screen, select the OAAM Admin Server as the target for oaam_admin. For example, select the target oaam_admin_server1.
On the next screen for optional settings, make sure you select 'I will make the deployment accessible from the following location' and point to the location where the oaam_admin.ear file will be accessible:
Oracle_IDM/oaam/oaam_admin/ear/oaam_admin.ear
Click Finish to complete the deployment of oaam_admin.
7) Log in to the OAAM Admin Console.
In the Navigation tree, double-click Properties under Environment.
In the Properties page, search for the oaam.taskflow.enum.sessionaddtogroup property.
Select the oaam.taskflow.enum.sessionaddtogroup.name property and click Save.
Saving the property will change it from a file load type property to a database type property. The property is now available in the database.
If the oaam.taskflow.enum.sessionaddtogroup.name property does not exist, create it.
Click the New Property button or Create new Property icon.
In the New Property dialog, type in oaam.taskflow.enum.sessionaddtogroup.name as the property name and SessionAddToGroup as the property value.
Click Save to save the property.
8) Restart the OAAM Admin server.
9) Update and activate changes for OAAM Server.
In the Domain Structure section of the console, click Deployments.
In the Summary of Deployments page, select oaam_server in the deployment table and click Update.
In the Change Center, click Activate Changes for the changes to take effect.
10) Update and activate changes for OAAM Offline.
In the Domain Structure section of the console, click Deployments.
Select the oaam_offline application in the deployment table and click Update.
In the Change Center, click Activate Changes for the changes to take effect.
If you find that oaam_admin, oaam_server, and oaam_offline are not in the Active state, then select the appropriate server and click Start.
When you have applied the OAAM 11.1.2.1.3 patch (19162894), version information is shown when you click the About link on the right side bottom corner. The version information should appear as Version 11.1.2.1.0 (11.1.2.1.0.OAAM_11.1.2.1.0BP_GENERIC_140828.0325).
Related Posts:
Applying OAAM 11.1.2.1.3 - Patch 19162894 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
Applying OAAM 11.1.2.1.3 - Patch 19162894 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
FMW 11.1.1.6.0 - Oracle Platform Security for Java - Applying Patch 15894053: TRACKING BUG FOR OPATCH DELIVERY OF ENTSEC_11.1.1.6.0-IDM11.1.2.1.0_GENERIC
FMW 11.1.1.6.2 JPS for IAM 11.1.2 - Oracle Virtual Directory Patch 14603262: IDS USER/GROUP NAME ATTR NOT MAPPED CORRECTLY TO CONFIGURED VALUES IN OPCONFIG
Applying OPSS 11.1.1.6.3 Patch 18629534 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
Applying OES 11.1.2.1.1 - Patch 18629535 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
Applying OAM 11.1.2.1.4 - Patch 19162892 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
OAAM 11.1.2.1.3 - Redeploying the OAAM Shared Library in Oracle WebLogic after applying Patch 19162894
FMW 11.1.1.6.2 JPS for IAM 11.1.2 - Oracle Virtual Directory Patch 14603262: IDS USER/GROUP NAME ATTR NOT MAPPED CORRECTLY TO CONFIGURED VALUES IN OPCONFIG
Applying OPSS 11.1.1.6.3 Patch 18629534 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
Applying OES 11.1.2.1.1 - Patch 18629535 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
Applying OAM 11.1.2.1.4 - Patch 19162892 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
OAAM 11.1.2.1.3 - Redeploying the OAAM Shared Library in Oracle WebLogic after applying Patch 19162894
Labels:
19157616,
19162892,
19162894,
6880880,
IDM,
IDM 11.1.2.1.5,
OAAM,
OAAM 11.1.2.1.3,
OAM,
OAM 11.1.2.1.4,
oam-admin-was.ear,
oam-server.ear,
OES 11.1.2.1.1,
opatch,
OPSS 11.1.1.6.3,
Oracle Access Manager,
redeploy OAAM
Thursday, 5 November 2015
Applying OAAM 11.1.2.1.3 - Patch 19162894 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
Applying OAAM 11.1.2.1.3 - Patch 19162894 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
- Download Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5 (p19157616_111210_Generic.zip)
- Patch 19157616 (p19157616_111210_Generic.zip) includes patches for components:
- OES 11.1.2.1.1
- OPSS 11.1.1.6.3
- OAM 11.1.2.1.4
- OAAM 11.1.2.1.3
- Copy and unzip p19157616_111210_Generic.zip onto the server staging area say PATCH_TOP with appropriate permissions.
- Download the latest version of OPatch (11.1.0.9.0 or higher) via Patch 6880880 (p6880880_111000_PLATFORM.zip)
Pre-requisites
- Stop all servers to which you will apply this bundle patch, and any application that uses this component.
- Backup ORACLE_HOME
- On OAAM Admin and OAAM Server, copy all customized properties, .xml and keystore files to create a backup.
- Set the ORACLE_HOME directory. For example:
$ export ORACLE_HOME=$MW_HOME/Oracle_IDM1
Apply Patch 19162894
- Stop all servers in which you have applied the bundle patch, and any application that uses the component.
- cd /PATCH_TOP/19157616/OAAM/19162894
- Run opatch apply
$ opatch apply
Post Patch Instructions:
i) Redeploying OAAM Applications in Oracle WebLogic
ii) Redeploying the Shared Library in Oracle WebLogic
Rollback Patch 19162894
- Stop all servers in which you have applied the bundle patch, and any application that uses the component.
- cd /PATCH_TOP/19157616/OAAM/19162894
- Run opatch apply
$ opatch rollback -id 19162894
- Start all servers after rolling back the patch
- Download Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5 (p19157616_111210_Generic.zip)
- Patch 19157616 (p19157616_111210_Generic.zip) includes patches for components:
- OES 11.1.2.1.1
- OPSS 11.1.1.6.3
- OAM 11.1.2.1.4
- OAAM 11.1.2.1.3
- Copy and unzip p19157616_111210_Generic.zip onto the server staging area say PATCH_TOP with appropriate permissions.
- Download the latest version of OPatch (11.1.0.9.0 or higher) via Patch 6880880 (p6880880_111000_PLATFORM.zip)
Pre-requisites
- Stop all servers to which you will apply this bundle patch, and any application that uses this component.
- Backup ORACLE_HOME
- On OAAM Admin and OAAM Server, copy all customized properties, .xml and keystore files to create a backup.
- Set the ORACLE_HOME directory. For example:
$ export ORACLE_HOME=$MW_HOME/Oracle_IDM1
Apply Patch 19162894
- Stop all servers in which you have applied the bundle patch, and any application that uses the component.
- cd /PATCH_TOP/19157616/OAAM/19162894
- Run opatch apply
$ opatch apply
Post Patch Instructions:
i) Redeploying OAAM Applications in Oracle WebLogic
ii) Redeploying the Shared Library in Oracle WebLogic
Rollback Patch 19162894
- Stop all servers in which you have applied the bundle patch, and any application that uses the component.
- cd /PATCH_TOP/19157616/OAAM/19162894
- Run opatch apply
$ opatch rollback -id 19162894
- Start all servers after rolling back the patch
Related Posts:
FMW 11.1.1.6.0 - Oracle Platform Security for Java - Applying Patch 15894053: TRACKING BUG FOR OPATCH DELIVERY OF ENTSEC_11.1.1.6.0-IDM11.1.2.1.0_GENERIC
FMW 11.1.1.6.2 JPS for IAM 11.1.2 - Oracle Virtual Directory Patch 14603262: IDS USER/GROUP NAME ATTR NOT MAPPED CORRECTLY TO CONFIGURED VALUES IN OPCONFIG
Applying OPSS 11.1.1.6.3 Patch 18629534 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
Applying OES 11.1.2.1.1 - Patch 18629535 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
Applying OAM 11.1.2.1.4 - Patch 19162892 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
OAAM 11.1.2.1.3 - Redeploying OAAM applications in Oracle WebLogic Server after applying Patch 19162894
OAAM 11.1.2.1.3 - Redeploying the OAAM Shared Library in Oracle WebLogic after applying Patch 19162894
FMW 11.1.1.6.2 JPS for IAM 11.1.2 - Oracle Virtual Directory Patch 14603262: IDS USER/GROUP NAME ATTR NOT MAPPED CORRECTLY TO CONFIGURED VALUES IN OPCONFIG
Applying OPSS 11.1.1.6.3 Patch 18629534 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
Applying OES 11.1.2.1.1 - Patch 18629535 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
Applying OAM 11.1.2.1.4 - Patch 19162892 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
OAAM 11.1.2.1.3 - Redeploying OAAM applications in Oracle WebLogic Server after applying Patch 19162894
OAAM 11.1.2.1.3 - Redeploying the OAAM Shared Library in Oracle WebLogic after applying Patch 19162894
Labels:
19157616,
19162892,
19162894,
6880880,
IBM Websphere,
IDM,
IDM 11.1.2.1.5,
OAAM,
OAAM 11.1.2.1.3,
OAM,
OAM 11.1.2.1.4,
oam-admin-was.ear,
oam-server.ear,
OES 11.1.2.1.1,
opatch,
OPSS 11.1.1.6.3,
Oracle Access Manager
Friday, 30 October 2015
Applying OES 11.1.2.1.1 - Patch 18629535 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
Applying OES 11.1.2.1.1 - Patch 18629535 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
Pre-requisite patches:
Apply OPSS Bundle Patch 11.1.1.6.3 and the Identity Governance Framework (IGF) Patch 14603262 prior to installing this bundle patch. The OPSS Bundle Patch is a prerequisite for the IGF Patch.
- Download Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5 (p19157616_111210_Generic.zip)
- Patch 19157616 (p19157616_111210_Generic.zip) includes patches for components:
- OES 11.1.2.1.1
- OPSS 11.1.1.6.3
- OAM 11.1.2.1.4
- OAAM 11.1.2.1.3
- Copy and unzip p19157616_111210_Generic.zip onto the server staging area say PATCH_TOP with appropriate permissions.
- Download the latest version of OPatch (11.1.0.9.0 or higher) via Patch 6880880 (p6880880_111000_PLATFORM.zip)
- Unzip the patch file into the PATCH_TOP directory.
$ unzip -d $PATCH_TOP p19157616_111210_Generic.zip
- Change to the directory where the patch is located.
$ cd /PATCH_TOP/19157616/OES/18629535
Apply patch 18629535
- Stop all servers including the Admin Server and all Managed server(s).
Run OPatch to apply the patch.
Proceed as below:
Set the ORACLE_HOME environment variable to the MW_HOME/Oracle_oesclient directory. (OES Client (Security Module) Home)
Run the following command:
- opatch apply
Set the ORACLE_HOME environment variable to the MW_HOME/Oracle_IDM1 directory. (OES or IDM Home)
Run the following command:
- opatch apply
(For 64-bit, opatch apply -jre Path_to_ORACLE_HOME/jdk/jre)
Post Installation Instructions:
- If any Security Module instances have been created, manually replace the following instance files:
oesclient/oes_sm_instances/instances/bin/oesPassword.* (sh/bat) by copying oesclient/oessm/enroll/bin/oesPassword.* (sh/bat)
oesclient/oes_sm_instances/instances/bin/setOesEnv.bat (Windows platform only) by copying oesclient/oessm/enroll/bin/setOesEnv.bat and replacing the @instance.home@ and @OES_CLIENT_HOME@ tokens.
- There have been domain level template changes. If adapting the new template changes, backup the existing domain and create a new domain using the updated template. This is not mandatory for existing functional domains.
- Start all servers including the Admin Server and all Managed server(s).
Patch Rollback instructions
- cd PATCH_TOP/18663203/OES/18629535
- Run OPatch to uninstall the patch.
i) Set the ORACLE_HOME environment variable to the Oracle_oesclient directory.
- opatch rollback -id 18629535 (For 64-bit, opatch rollback -id Patch_ID -jre Path_to_ORACLE_HOME/jdk/jre )
ii) Set the ORACLE_HOME environment variable to the Oracle_IDM1 directory.
Run the following command:
- opatch rollback -id 18629535 (For 64-bit, opatch rollback -id Patch_ID -jre Path_to_ORACLE_HOME/jdk/jre )
- Start all servers including the Admin Server and all Managed server(s).
FMW 11.1.1.6.0 - Oracle Platform Security for Java - Applying Patch 15894053: TRACKING BUG FOR OPATCH DELIVERY OF ENTSEC_11.1.1.6.0-IDM11.1.2.1.0_GENERIC
FMW 11.1.1.6.2 JPS for IAM 11.1.2 - Oracle Virtual Directory Patch 14603262: IDS USER/GROUP NAME ATTR NOT MAPPED CORRECTLY TO CONFIGURED VALUES IN OPCONFIG
Applying OPSS 11.1.1.6.3 Patch 18629534 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
Applying OAM 11.1.2.1.4 - Patch 19162892 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
Applying OAAM 11.1.2.1.3 - Patch 19162894 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
OAAM 11.1.2.1.3 - Redeploying OAAM applications in Oracle WebLogic Server after applying Patch 19162894
OAAM 11.1.2.1.3 - Redeploying the OAAM Shared Library in Oracle WebLogic after applying Patch 19162894
Pre-requisite patches:
Apply OPSS Bundle Patch 11.1.1.6.3 and the Identity Governance Framework (IGF) Patch 14603262 prior to installing this bundle patch. The OPSS Bundle Patch is a prerequisite for the IGF Patch.
- Download Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5 (p19157616_111210_Generic.zip)
- Patch 19157616 (p19157616_111210_Generic.zip) includes patches for components:
- OES 11.1.2.1.1
- OPSS 11.1.1.6.3
- OAM 11.1.2.1.4
- OAAM 11.1.2.1.3
- Copy and unzip p19157616_111210_Generic.zip onto the server staging area say PATCH_TOP with appropriate permissions.
- Download the latest version of OPatch (11.1.0.9.0 or higher) via Patch 6880880 (p6880880_111000_PLATFORM.zip)
- Unzip the patch file into the PATCH_TOP directory.
$ unzip -d $PATCH_TOP p19157616_111210_Generic.zip
- Change to the directory where the patch is located.
$ cd /PATCH_TOP/19157616/OES/18629535
Apply patch 18629535
- Stop all servers including the Admin Server and all Managed server(s).
Run OPatch to apply the patch.
Proceed as below:
Set the ORACLE_HOME environment variable to the MW_HOME/Oracle_oesclient directory. (OES Client (Security Module) Home)
Run the following command:
- opatch apply
Set the ORACLE_HOME environment variable to the MW_HOME/Oracle_IDM1 directory. (OES or IDM Home)
Run the following command:
- opatch apply
(For 64-bit, opatch apply -jre Path_to_ORACLE_HOME/jdk/jre)
Post Installation Instructions:
- If any Security Module instances have been created, manually replace the following instance files:
oesclient/oes_sm_instances/instances/bin/oesPassword.* (sh/bat) by copying oesclient/oessm/enroll/bin/oesPassword.* (sh/bat)
oesclient/oes_sm_instances/instances/bin/setOesEnv.bat (Windows platform only) by copying oesclient/oessm/enroll/bin/setOesEnv.bat and replacing the @instance.home@ and @OES_CLIENT_HOME@ tokens.
- There have been domain level template changes. If adapting the new template changes, backup the existing domain and create a new domain using the updated template. This is not mandatory for existing functional domains.
- Start all servers including the Admin Server and all Managed server(s).
Patch Rollback instructions
- cd PATCH_TOP/18663203/OES/18629535
- Run OPatch to uninstall the patch.
i) Set the ORACLE_HOME environment variable to the Oracle_oesclient directory.
- opatch rollback -id 18629535 (For 64-bit, opatch rollback -id Patch_ID -jre Path_to_ORACLE_HOME/jdk/jre )
ii) Set the ORACLE_HOME environment variable to the Oracle_IDM1 directory.
Run the following command:
- opatch rollback -id 18629535 (For 64-bit, opatch rollback -id Patch_ID -jre Path_to_ORACLE_HOME/jdk/jre )
- Start all servers including the Admin Server and all Managed server(s).
FMW 11.1.1.6.0 - Oracle Platform Security for Java - Applying Patch 15894053: TRACKING BUG FOR OPATCH DELIVERY OF ENTSEC_11.1.1.6.0-IDM11.1.2.1.0_GENERIC
FMW 11.1.1.6.2 JPS for IAM 11.1.2 - Oracle Virtual Directory Patch 14603262: IDS USER/GROUP NAME ATTR NOT MAPPED CORRECTLY TO CONFIGURED VALUES IN OPCONFIG
Applying OPSS 11.1.1.6.3 Patch 18629534 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
Applying OAM 11.1.2.1.4 - Patch 19162892 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
Applying OAAM 11.1.2.1.3 - Patch 19162894 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
OAAM 11.1.2.1.3 - Redeploying OAAM applications in Oracle WebLogic Server after applying Patch 19162894
OAAM 11.1.2.1.3 - Redeploying the OAAM Shared Library in Oracle WebLogic after applying Patch 19162894
Labels:
14603262,
18629535,
19157616,
Identity Governance Framework,
IDM,
IDM 11.1.2.1.5,
IGF,
OAAM,
OAAM 11.1.2.1.3,
OAM,
OAM 11.1.2.1.4,
OES,
OES 11.1.2.1.1,
OESCLIENT,
OPSS,
OPSS 11.1.1.6.3,
Oracle Entitlement Server
Applying OAM 11.1.2.1.4 - Patch 19162892 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
Applying OAM 11.1.2.1.4 - Patch 19162892 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
- Download Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5 (p19157616_111210_Generic.zip)
- Patch 19157616 (p19157616_111210_Generic.zip) includes patches for components:
- OES 11.1.2.1.1
- OPSS 11.1.1.6.3
- OAM 11.1.2.1.4
- OAAM 11.1.2.1.3
- Copy p19157616_111210_Generic.zip onto the server staging area say PATCH_TOP with appropriate permissions.
- Download the latest version of OPatch (11.1.0.9.0 or higher) via Patch 6880880 (p6880880_111000_PLATFORM.zip)
Apply OAM 11.1.2.1.4 - Patch 19162892
- Stop the Admin server and Managed servers (where OAM console and servers have been deployed)
- Unzip the patch zip file into the PATCH_TOP.
$ unzip -d PATCH_TOP p19162892_111210_Generic.zip
- cd /PATCH_TOP/19157616/OAM/19162892
- Run OPatch to apply the patch.
$ opatch apply
- Restart all servers (Admin Server and all Managed Server(s))
Post-Installation Steps for IBM WebSphere (WAS) (Only applicable for OAM installed on the IBM WebSphere Application Server)
-----------------------------------------------
After applying this bundle patch on an instance of OAM installed on the IBM WebSphere Application Server (WAS), you must redeploy the OAM application in WAS for successful patch application. Follow
steps in Patch README.HTML to manually redeploy the OAM administration application (oam-admin-was.ear) and the OAM server application (oam-server.ear). They should be individually redeployed.
1. "Redeploying oam-admin-was.ear"
2. "Redeploying oam-server.ear"
Patch 19162892 Rollback Instructions:
Post patching, if any issues encountered and rollback is required, follow below steps:
- Stop the Admin server and Managed servers (where OAM console and servers have been deployed)
- Change to the directory where the patch was unzipped.
$ cd PATCH_TOP/19162892
- Run OPatch to deinstall the patch.
$ opatch rollback -id 19162892
- Restart all servers (Admin Server and all Managed Server(s))
- Download Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5 (p19157616_111210_Generic.zip)
- Patch 19157616 (p19157616_111210_Generic.zip) includes patches for components:
- OES 11.1.2.1.1
- OPSS 11.1.1.6.3
- OAM 11.1.2.1.4
- OAAM 11.1.2.1.3
- Copy p19157616_111210_Generic.zip onto the server staging area say PATCH_TOP with appropriate permissions.
- Download the latest version of OPatch (11.1.0.9.0 or higher) via Patch 6880880 (p6880880_111000_PLATFORM.zip)
Apply OAM 11.1.2.1.4 - Patch 19162892
- Stop the Admin server and Managed servers (where OAM console and servers have been deployed)
- Unzip the patch zip file into the PATCH_TOP.
$ unzip -d PATCH_TOP p19162892_111210_Generic.zip
- cd /PATCH_TOP/19157616/OAM/19162892
- Run OPatch to apply the patch.
$ opatch apply
- Restart all servers (Admin Server and all Managed Server(s))
Post-Installation Steps for IBM WebSphere (WAS) (Only applicable for OAM installed on the IBM WebSphere Application Server)
-----------------------------------------------
After applying this bundle patch on an instance of OAM installed on the IBM WebSphere Application Server (WAS), you must redeploy the OAM application in WAS for successful patch application. Follow
steps in Patch README.HTML to manually redeploy the OAM administration application (oam-admin-was.ear) and the OAM server application (oam-server.ear). They should be individually redeployed.
1. "Redeploying oam-admin-was.ear"
2. "Redeploying oam-server.ear"
Patch 19162892 Rollback Instructions:
Post patching, if any issues encountered and rollback is required, follow below steps:
- Stop the Admin server and Managed servers (where OAM console and servers have been deployed)
- Change to the directory where the patch was unzipped.
$ cd PATCH_TOP/19162892
- Run OPatch to deinstall the patch.
$ opatch rollback -id 19162892
- Restart all servers (Admin Server and all Managed Server(s))
Related Posts:
FMW 11.1.1.6.0 - Oracle Platform Security for Java - Applying Patch 15894053: TRACKING BUG FOR OPATCH DELIVERY OF ENTSEC_11.1.1.6.0-IDM11.1.2.1.0_GENERIC
FMW 11.1.1.6.2 JPS for IAM 11.1.2 - Oracle Virtual Directory Patch 14603262: IDS USER/GROUP NAME ATTR NOT MAPPED CORRECTLY TO CONFIGURED VALUES IN OPCONFIG
Applying OPSS 11.1.1.6.3 Patch 18629534 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
Applying OES 11.1.2.1.1 - Patch 18629535 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
Applying OAAM 11.1.2.1.3 - Patch 19162894 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
OAAM 11.1.2.1.3 - Redeploying OAAM applications in Oracle WebLogic Server after applying Patch 19162894
OAAM 11.1.2.1.3 - Redeploying the OAAM Shared Library in Oracle WebLogic after applying Patch 19162894
FMW 11.1.1.6.2 JPS for IAM 11.1.2 - Oracle Virtual Directory Patch 14603262: IDS USER/GROUP NAME ATTR NOT MAPPED CORRECTLY TO CONFIGURED VALUES IN OPCONFIG
Applying OPSS 11.1.1.6.3 Patch 18629534 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
Applying OES 11.1.2.1.1 - Patch 18629535 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
Applying OAAM 11.1.2.1.3 - Patch 19162894 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
OAAM 11.1.2.1.3 - Redeploying OAAM applications in Oracle WebLogic Server after applying Patch 19162894
OAAM 11.1.2.1.3 - Redeploying the OAAM Shared Library in Oracle WebLogic after applying Patch 19162894
Labels:
19157616,
19162892,
6880880,
IBM Websphere,
IDM,
IDM 11.1.2.1.5,
OAAM,
OAAM 11.1.2.1.3,
OAM,
OAM 11.1.2.1.4,
oam-admin-was.ear,
oam-server.ear,
OES 11.1.2.1.1,
opatch,
OPSS 11.1.1.6.3,
Oracle Access Manager,
WAS
Applying OPSS 11.1.1.6.3 Patch 18629534 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
Applying OPSS 11.1.1.6.3 Patch 18629534 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
- Download Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5 (p19157616_111210_Generic.zip)
- Patch 19157616 (p19157616_111210_Generic.zip) includes patches for components:
- OES 11.1.2.1.1
- OPSS 11.1.1.6.3
- OAM 11.1.2.1.4
- OAAM 11.1.2.1.3
- Copy p19157616_111210_Generic.zip onto the server staging area say PATCH_TOP with appropriate permissions.
- Download the latest version of OPatch (11.1.0.9.0 or higher) via Patch 6880880 (p6880880_111000_PLATFORM.zip)
- Unzip the patch file into the PATCH_TOP directory.
unzip -d $PATCH_TOP p19157616_111210_Generic.zip
- cd /PATCH_TOP/19157616/OPSS/18629534
Apply OPSS 11.1.1.6.3 Patch 18629534:
- Stop all servers including the Admin Server and all Managed server(s).
i)Set the ORACLE_HOME environment variable to MW_HOME/oracle_common directory. (JRF Home)
- Run opatch apply:
$ opatch apply (For 64-bit, opatch apply -jre Path_to_ORACLE_HOME/jdk/jre)
ii) Set the ORACLE_HOME environment variable to MW_HOME/Oracle_oesclient directory. (OES Client (Security Module) Home)
Run opatch apply:
$ opatch apply (For 64-bit, opatch apply -jre Path_to_ORACLE_HOME/jdk/jre)
- Start all servers including the Admin Server and all Managed server(s).
Rollback OPSS 11.1.1.6.3 Patch 18629534:
If any issues encountered after applying the patch and rollback is required, follow below steps:
- Stop all servers including the Admin Server and all Managed server(s).
- Change to the directory in which the bundle patch was unzipped.
$ cd PATCH_TOP/19157616/OPSS/18629534
Run opatch rollback as below:
i) Set the ORACLE_HOME environment variable to the oracle_common directory.
Run the following command:
- opatch rollback -id 18629534
(For 64-bit, opatch rollback -id Patch_ID -jre Path_to_ORACLE_HOME/jdk/jre )
ii) Set the ORACLE_HOME environment variable to the oracle_oesclient directory.
Run opatch rollback as below:
- opatch rollback -id 18629534
(For 64-bit, opatch rollback -id Patch_ID -jre Path_to_ORACLE_HOME/jdk/jre )
- Start all servers including the Admin Server and all Managed server(s).
- Download Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5 (p19157616_111210_Generic.zip)
- Patch 19157616 (p19157616_111210_Generic.zip) includes patches for components:
- OES 11.1.2.1.1
- OPSS 11.1.1.6.3
- OAM 11.1.2.1.4
- OAAM 11.1.2.1.3
- Copy p19157616_111210_Generic.zip onto the server staging area say PATCH_TOP with appropriate permissions.
- Download the latest version of OPatch (11.1.0.9.0 or higher) via Patch 6880880 (p6880880_111000_PLATFORM.zip)
- Unzip the patch file into the PATCH_TOP directory.
unzip -d $PATCH_TOP p19157616_111210_Generic.zip
- cd /PATCH_TOP/19157616/OPSS/18629534
Apply OPSS 11.1.1.6.3 Patch 18629534:
- Stop all servers including the Admin Server and all Managed server(s).
i)Set the ORACLE_HOME environment variable to MW_HOME/oracle_common directory. (JRF Home)
- Run opatch apply:
$ opatch apply (For 64-bit, opatch apply -jre Path_to_ORACLE_HOME/jdk/jre)
ii) Set the ORACLE_HOME environment variable to MW_HOME/Oracle_oesclient directory. (OES Client (Security Module) Home)
Run opatch apply:
$ opatch apply (For 64-bit, opatch apply -jre Path_to_ORACLE_HOME/jdk/jre)
- Start all servers including the Admin Server and all Managed server(s).
Rollback OPSS 11.1.1.6.3 Patch 18629534:
If any issues encountered after applying the patch and rollback is required, follow below steps:
- Stop all servers including the Admin Server and all Managed server(s).
- Change to the directory in which the bundle patch was unzipped.
$ cd PATCH_TOP/19157616/OPSS/18629534
Run opatch rollback as below:
i) Set the ORACLE_HOME environment variable to the oracle_common directory.
Run the following command:
- opatch rollback -id 18629534
(For 64-bit, opatch rollback -id Patch_ID -jre Path_to_ORACLE_HOME/jdk/jre )
ii) Set the ORACLE_HOME environment variable to the oracle_oesclient directory.
Run opatch rollback as below:
- opatch rollback -id 18629534
(For 64-bit, opatch rollback -id Patch_ID -jre Path_to_ORACLE_HOME/jdk/jre )
- Start all servers including the Admin Server and all Managed server(s).
Related Posts:
FMW 11.1.1.6.0 - Oracle Platform Security for Java - Applying Patch 15894053: TRACKING BUG FOR OPATCH DELIVERY OF ENTSEC_11.1.1.6.0-IDM11.1.2.1.0_GENERIC
FMW 11.1.1.6.2 JPS for IAM 11.1.2 - Oracle Virtual Directory Patch 14603262: IDS USER/GROUP NAME ATTR NOT MAPPED CORRECTLY TO CONFIGURED VALUES IN OPCONFIG
Applying OAM 11.1.2.1.4 - Patch 19162892 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
Applying OES 11.1.2.1.1 - Patch 18629535 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
Applying OAAM 11.1.2.1.3 - Patch 19162894 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
OAAM 11.1.2.1.3 - Redeploying OAAM applications in Oracle WebLogic Server after applying Patch 19162894
OAAM 11.1.2.1.3 - Redeploying the OAAM Shared Library in Oracle WebLogic after applying Patch 19162894
FMW 11.1.1.6.2 JPS for IAM 11.1.2 - Oracle Virtual Directory Patch 14603262: IDS USER/GROUP NAME ATTR NOT MAPPED CORRECTLY TO CONFIGURED VALUES IN OPCONFIG
Applying OAM 11.1.2.1.4 - Patch 19162892 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
Applying OES 11.1.2.1.1 - Patch 18629535 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
Applying OAAM 11.1.2.1.3 - Patch 19162894 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
OAAM 11.1.2.1.3 - Redeploying OAAM applications in Oracle WebLogic Server after applying Patch 19162894
OAAM 11.1.2.1.3 - Redeploying the OAAM Shared Library in Oracle WebLogic after applying Patch 19162894
Labels:
11.1.1.6.3,
11.1.2.1.5,
18629534,
19157616,
IDM,
JDK,
JRE,
JRF,
OAAM,
OAAM 11.1.2.1.3,
OAM,
OAM 11.1.2.1.4,
OES 11.1.2.1.1,
OESCLIENT,
OPSS 11.1.1.6.3,
Oracle Identity Management Suite,
p19157616_111210_Generic.zip
Saturday, 5 October 2013
/scratch/alnguyen/Oblix/10143hf/palantir/webgate2/src/apache2entry_web_gate.cpp:434 "The AccessGate is unable to contact any Access Servers."
/scratch/alnguyen/Oblix/10143hf/palantir/webgate2/src/apache2entry_web_gate.cpp:434 "The AccessGate is unable to contact any Access Servers."
Are you seeing errors like "The AccessGate is unable to contact any Access Servers" ?
1) Check the status of Access Server and verify if its up and running. If it not running, restart Access Server.
2) If Access server is up & running, check the time of both OAM Access Server and WebGate machines. Ensure both servers are in sync with time.
Please note that Access Server clocks can be ahead of WebGates by no more than 60 seconds.
Webgate clocks should never be ahead of Access Server clocks.
More on time synchronization in OAM here
Message from syslogd@ at Thu Oct 3 11:50:02 2013 ...
hostname Oblix: 2013/10/03@10:50:02.086321 5382 5391 ACCESS_GATE FATAL 0x00001520 /scratch/alnguyen/Oblix/10143hf/palantir/webgate2/src/apache2entry_web_gate.cpp:433 "Exception thrown during WebGate initialization"
Message from syslogd@ at Thu Oct 3 11:50:02 2013 ...
hostname Oblix: 2013/10/03@10:50:02.086321 5382 5391 ACCESS_GATE FATAL 0x00001520 /scratch/alnguyen/Oblix/10143hf/palantir/webgate2/src/apache2entry_web_gate.cpp:433 "Exception thrown during WebGate initialization"
Message from syslogd@ at Thu Oct 3 11:50:02 2013 ...
hostname Oblix: 2013/10/03@10:50:02.091357 5382 5391 ACCESS_GATE FATAL 0x0000182C /scratch/alnguyen/Oblix/10143hf/palantir/webgate2/src/apache2entry_web_gate.cpp:434 "The AccessGate is unable to contact any Access Servers." raw_code^301
Message from syslogd@ at Thu Oct 3 11:50:02 2013 ...
hostname Oblix: 2013/10/03@10:50:02.091357 5382 5391 ACCESS_GATE FATAL 0x0000182C /scratch/alnguyen/Oblix/10143hf/palantir/webgate2/src/apache2entry_web_gate.cpp:434 "The AccessGate is unable to contact any Access Servers." raw_code^301
Message from syslogd@ at Thu Oct 3 11:50:22 2013 ...
hostname Oblix: 2013/10/03@10:50:22.019074 5382 5395 ACCESS_GATE FATAL 0x00001520 /scratch/alnguyen/Oblix/10143hf/palantir/webgate2/src/apache2entry_web_gate.cpp:433 "Exception thrown during WebGate initialization"
Message from syslogd@ at Thu Oct 3 11:50:22 2013 ...
hostname Oblix: 2013/10/03@10:50:22.019074 5382 5395 ACCESS_GATE FATAL 0x00001520 /scratch/alnguyen/Oblix/10143hf/palantir/webgate2/src/apache2entry_web_gate.cpp:433 "Exception thrown during WebGate initialization"
Message from syslogd@ at Thu Oct 3 11:50:22 2013 ...
hostname Oblix: 2013/10/03@10:50:22.026224 5382 5395 ACCESS_GATE FATAL 0x0000182C /scratch/alnguyen/Oblix/10143hf/palantir/webgate2/src/apache2entry_web_gate.cpp:434 "The AccessGate is unable to contact any Access Servers." raw_code^301
Message from syslogd@ at Thu Oct 3 11:50:22 2013 ...
hostname Oblix: 2013/10/03@10:50:22.026224 5382 5395 ACCESS_GATE FATAL 0x0000182C /scratch/alnguyen/Oblix/10143hf/palantir/webgate2/src/apache2entry_web_gate.cpp:434 "The AccessGate is unable to contact any Access Servers." raw_code^301
Are you seeing errors like "The AccessGate is unable to contact any Access Servers" ?
1) Check the status of Access Server and verify if its up and running. If it not running, restart Access Server.
2) If Access server is up & running, check the time of both OAM Access Server and WebGate machines. Ensure both servers are in sync with time.
Please note that Access Server clocks can be ahead of WebGates by no more than 60 seconds.
Webgate clocks should never be ahead of Access Server clocks.
More on time synchronization in OAM here
Message from syslogd@ at Thu Oct 3 11:50:02 2013 ...
hostname Oblix: 2013/10/03@10:50:02.086321 5382 5391 ACCESS_GATE FATAL 0x00001520 /scratch/alnguyen/Oblix/10143hf/palantir/webgate2/src/apache2entry_web_gate.cpp:433 "Exception thrown during WebGate initialization"
Message from syslogd@ at Thu Oct 3 11:50:02 2013 ...
hostname Oblix: 2013/10/03@10:50:02.086321 5382 5391 ACCESS_GATE FATAL 0x00001520 /scratch/alnguyen/Oblix/10143hf/palantir/webgate2/src/apache2entry_web_gate.cpp:433 "Exception thrown during WebGate initialization"
Message from syslogd@ at Thu Oct 3 11:50:02 2013 ...
hostname Oblix: 2013/10/03@10:50:02.091357 5382 5391 ACCESS_GATE FATAL 0x0000182C /scratch/alnguyen/Oblix/10143hf/palantir/webgate2/src/apache2entry_web_gate.cpp:434 "The AccessGate is unable to contact any Access Servers." raw_code^301
Message from syslogd@ at Thu Oct 3 11:50:02 2013 ...
hostname Oblix: 2013/10/03@10:50:02.091357 5382 5391 ACCESS_GATE FATAL 0x0000182C /scratch/alnguyen/Oblix/10143hf/palantir/webgate2/src/apache2entry_web_gate.cpp:434 "The AccessGate is unable to contact any Access Servers." raw_code^301
Message from syslogd@ at Thu Oct 3 11:50:22 2013 ...
hostname Oblix: 2013/10/03@10:50:22.019074 5382 5395 ACCESS_GATE FATAL 0x00001520 /scratch/alnguyen/Oblix/10143hf/palantir/webgate2/src/apache2entry_web_gate.cpp:433 "Exception thrown during WebGate initialization"
Message from syslogd@ at Thu Oct 3 11:50:22 2013 ...
hostname Oblix: 2013/10/03@10:50:22.019074 5382 5395 ACCESS_GATE FATAL 0x00001520 /scratch/alnguyen/Oblix/10143hf/palantir/webgate2/src/apache2entry_web_gate.cpp:433 "Exception thrown during WebGate initialization"
Message from syslogd@ at Thu Oct 3 11:50:22 2013 ...
hostname Oblix: 2013/10/03@10:50:22.026224 5382 5395 ACCESS_GATE FATAL 0x0000182C /scratch/alnguyen/Oblix/10143hf/palantir/webgate2/src/apache2entry_web_gate.cpp:434 "The AccessGate is unable to contact any Access Servers." raw_code^301
Message from syslogd@ at Thu Oct 3 11:50:22 2013 ...
hostname Oblix: 2013/10/03@10:50:22.026224 5382 5395 ACCESS_GATE FATAL 0x0000182C /scratch/alnguyen/Oblix/10143hf/palantir/webgate2/src/apache2entry_web_gate.cpp:434 "The AccessGate is unable to contact any Access Servers." raw_code^301
Subscribe to:
Posts (Atom)