The Patch Set Update (PSU) is a functionality that allows you to apply the patches to the main deployed application.
This allows you to perform a version of update of the application. You're able to determine the current version of the Oracle application by following the link, What version of Oracle Access Manager am I using?.
Before you begin
You need to ensure that the WLS Environments are set within your terminal window. To do this you can run the following command:
sh /home/oracle/Oracle/OAM/Middleware/wlserver_10.3/server/bin/setWLSEnv.sh
Note: you'll probably need to alter the path to the setWLSEnv.sh file. Once you've done that, you'll probably see the CLASSPATH and PATH show up in the window.
You also need to ensure that you're running the correct WLS version (10.3.6) for 11gR2+. Running the command below will also assure you that your JAVA parameter is set
java weblogic.version
Create a temporary directory then move the patch to the cache_dir directory
Now you're ready to begin. First, navigate to the bsu directory, which resides within the $MW_HOME/utils directory.
After that, move the downloaded patch to the cache_dir directory - Do not uncompress it.
mv ./p20780171_1036_Generic.zip ./cache_dir/
Once you've done that, you're ready to run the
./bsu.sh -install -patch_download_dir=$MW_HOME/utils/bsu/cache_dir -patchlist=EJUW -prod_dir=$WL_HOME
When you initiate the WLS domain again, you should also version: WebLogic Server 10.3.6.0.12 PSU Patch for BUG20780171 THU JUN 18 15:54:42 IST 2015'
When you've initiated the command and once it's complete, you can run the the c
java weblogic.version command to see the current version along with the PSU update. For example WebLogic Server 10.3.6.0.12 PSU Patch for BUG20780171 THU JUN 18 15:54:42 IST 2015
ISSUE: Encountered unrecognized patch ID: EJUW
Encountered unrecognized patch ID: EJUW
SOLUTION
(unzip the jar file) and check directory path and provide 777 permissions
ISSUE: GC overhead limit exceeded
[oracle@localhost bsu]$ ./bsu.sh -install -patch_download_dir=$MW_HOME/utils/bsu/cache_dir -patchlist=EJUW -prod_dir=$WL_HOME
Exception in thread "main" java.lang.OutOfMemoryError: GC overhead limit exceeded
at com.bea.plateng.patch.dao.cat.PatchCatalogHelper.getPatchDependencies(PatchCatalogHelper.java:448)
at com.bea.plateng.patch.dao.cat.PatchCatalogHelper.getPatchDependencies(PatchCatalogHelper.java:464)
at com.bea.plateng.patch.dao.cat.PatchCatalog.getPatchDependencies(PatchCatalog.java:56)
at com.bea.plateng.patch.dao.cat.PatchCatalogHelper.getInvalidatedPatchMap(PatchCatalogHelper.java:1621)
at com.bea.plateng.patch.PatchSystem.updatePatchCatalog(PatchSystem.java:436)
at com.bea.plateng.patch.PatchSystem.refresh(PatchSystem.java:130)
at com.bea.plateng.patch.PatchSystem.setCacheDir(PatchSystem.java:201)
at com.bea.plateng.patch.Patch.main(Patch.java:281)
[oracle@localhost bsu]$
SOLUTION
MEM_ARGS="-Xms256m -Xmx1024m -XX:-UseGCOverheadLimit" You may also need to increase the heap size to avoid 'java.lang.OutOfMemoryError: Java heap space' exception.
About the author
Daniel is a Technical Manager with over 10 years of consulting expertise in the Identity and Access Management space.Daniel has built from scratch this blog as well as technicalconfessions.com
Follow Daniel on twitter @nervouswiggles
Comments
Other Posts
AS I was migrating my environment into an S3 environment, I wanted to leverage off the SES services that AWS provide, more specifically, to leverage the off the SMTP functionality by sending an email via PHP
Read More...
The WeMos D1 is a ESP8266 WiFi based board is an extension to the current out-of-the-box library that comes with the Arduino installation. Because of this, you need to import in the libraries as well as acknowledging the specific board. This process is highly confusion with a number of different individuals talking about a number of different ways to integrate.
Read More...
NameID element must be present as part of the Subject in the Response message, please enable it in the IDP configuration.
Read More...
For what I see, there's not too many supportive documentations out there that will demonstrate how provision AD group membership with the ICF connector using OpenIDM. The use of the special ldapGroups attribute is not explained anywhere in the Integrators guides to to the date of this blog. This quick blog identifies the tasks required to provision AD group membership from OpenIDM to AD using the LDAP ICF connector. However this doesn't really explain what ldapGroups actually does and there's no real worked example of how to go from an Assignment to ldapGroups to an assigned group in AD. I wrote up a wiki article for my own reference: AD group memberships automatically to users This is just my view, others may disagree, but I think the implementation experience could be improved with some more documentation and a more detailed example here.
Read More...
In the past, the similar error occurred though for the Oracle Identity Management solution. invalidcredentialexception remote framework key is invalid Because they all share the ICF connector framework, the error/solution would be the same.
Read More...
org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...
ForgeRock IDM - org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...
When performing the attempt of a reconciliation from ForgeRock IDM to Active Directory, I would get the following error
Read More...
In the past, the similar error occurred though for the Oracle Identity Management solution. invalidcredentialexception remote framework key is invalid Because they all share the ICF connector framework, the error/solution would be the same.
Read More...
During the reconcilation from OpenIDM to the ICF google apps connector, the following error response would occur. ERROR Caused by com.google.api.client.auth.oauth2.TokenResponseException 400 Bad Request - invalid_grant
Read More...
Tags
Recent Posts
Monthly Activity
Group by date