Showing posts with label PATCH. Show all posts
Showing posts with label PATCH. Show all posts

Error While Upgrading Weblogic Domain Version 12.1.1 To 12.1.2 with error UPGWLS-03503

The reconfigure script to upgrade a WebLogic Server domain from version 12.1.1 to version 12.1.2 exits with an error. The issue seems to be with a custom Identity Asserter, in this case "Oracle Access Manager Identity Asserter." The error message is:
2014-02-11 09:12:44,752 INFO [AWT-EventQueue-0] com.oracle.cie.wizard.help.DefaultHelpProvider - Initializing help implementation....
2014-02-11 09:12:45,605 INFO [AWT-EventQueue-0] com.oracle.cie.domain.DomainRegistryWrapper - need to initialize domainRegistrydocument object
2014-02-11 09:13:35,547 WARNING [44] weblogic.upgrade.Upgrade - /web/oracle/Middleware/oracle_common/common/lib/:10:7: error: failed to load java type corresponding to t=oam-identity-asserterType@http://www.bea.com/ns/weblogic/90/security/extension
2014-02-11 09:13:35,550 SEVERE [Thread-4] com.oracle.cie.domain.WLSCoreReconfigurator - Reconfiguration failed
java.lang.reflect.InvocationTargetException
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
  at java.lang.reflect.Method.invoke(Method.java:601)
  at com.oracle.cie.common.ReflectionHelper.process(ReflectionHelper.java:48)
  at com.oracle.cie.domain.WLSCoreReconfigurator.run(WLSCoreReconfigurator.java:150)
  at java.lang.Thread.run(Thread.java:722)
Caused by: weblogic.upgrade.UpgradeException: UPGWLS-03503: The domain configuration file {0} is not valid.
  at weblogic.upgrade.Upgrade.parseConfig(Upgrade.java:172)
  at weblogic.upgrade.Upgrade.upgradeDomain(Upgrade.java:118)
  ... 7 more
2014-02-11 09:13:35,551 SEVERE [Thread-4] com.oracle.cie.domain.WLSCoreReconfigurator - Reconfiguration Failed!

 

How to Migrate a WebLogic Domain from a 32 to a 64 bit JVM/Architecture?

Currently on 32 bit OS which presents a physical constraint when trying to allocate memory.

By limit, a 32 bit OS, will not be able to allocate more than 3 GB on a Linux environment, or 2 GB for Windows environment (not considering Physical Address Extension (PAE) implementation, which can increase the maximum allocatable memory).

When this limit is reached, a migration to a 64 bit architecture is recommended.

Below are the steps on how to install a 64 WebLogic Server version, along with a 64 Bit JVM and then how to migrate the domain to this new environment.

Solution

The versions that were used on this test case are the following:

Weblogic Server Version: WebLogic Server Version: 10.3.4.0
OS: Linux dalquint-cl.cl.oracle.com 2.6.18-194.el5 #1 SMP Mon Mar 29 22:10:29 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
JVM:java version "1.6.0_22"
Java(TM) SE Runtime Environment (build 1.6.0_22-b04)
Oracle JRockit(R) (build R28.1.1-13-139783-1.6.0_22-20101206-0136-linux-x86_64, compiled mode)


Upgrading WebLogic 10.3.x (for PeopleTools 8.51-8.53) to a Newer Maintenance Pack (MP), Patch Level, and/or a Newer Java/JRockit Patch Level

This document answers frequently asked questions regarding:
  1) Steps to Upgrading WebLogic to a newer maintenance pack and patch level
  2) Questions about Upgrading Java patch level for your WebLogic Install.
  3) Details on how to locate/download/install newer WebLogic Maintenance Packs, Patches and Java Patches

This document is specifically for PeopleTools 8.51, 8.52 and 8.53 environments which are using WebLogic 10.3.x.

Give me an overview of the steps to get updated to the latest WebLogic version and patch level. And explain the difference between Maintenance Packs and Patches
If you are planning on upgrading WebLogic in your PeopleSoft environment, you need to keep in mind that there are actually three separate parts to the upgrade:
    Part #1: Upgrade the WebLogic Maintenance Pack (aka MP).
    Part #2: Upgrade the WebLogic Patch Level
    Part #3: Upgrade the Java (or JRockit) Patch Level

Note that you do not have to complete each of the above parts. However, we do recommend that you complete each part, as this will get you fully up-to-date on all bug fixes and patches for security vulnerabilities.

Below are additional details regarding WebLogic Maintenance Packs, WebLogic Patches and Java Patches, that are referenced in Part#1, 2 and 3 above.

WLST Script to Get WebLogic Server Patch Levels

Configuring


Make sure the user provided in the script can be authenticated in the domain where the script is run.

Instructions


  1. Save the script given as patchingLevel.py.
  2. Modify the parameters for the user and the connection string to the Admin Server.
  3. Set the domain environment using the script <domain_home>/bin/setDomainEnv.sh.
  4. Run the script as follows:
    $ java weblogic.WLST patchingLevel.py

Caution


This sample code is provided for educational purposes only, and is not supported by Oracle Support. It has been tested internally, however, we do not guarantee that it will work for you. Ensure that you run it in your test environment before using.

Script

username = 'admin-username'
password = 'admin-password'
connect(username,password, 'wls-hostname:wls-port')
print version
print "\n"
disconnect()
exit()

How to Upgrade the JDK Used by Oracle WebLogic Server UNIX installations to a Different Version


There are two different approaches that can be used to achieve the required goal. Both will be described briefly:
A) Installing a new JDK home, and using symbolic link to "rename" the existing and new JDK directories.
Following this approach, the JDK location originally used during the installation will not change and hence it has the minimal drawback that it might keep a versioned name as for example "$INSTALL_HOME/jdk_".
In any of the cases, this approach is simpler and less error prone than Approach B)

B) Installing a new JDK home directory and replacing the JAVA_HOME environmental variable in *** all *** the scripts referring to it.

This is the preferred approach if you want to do a partial upgrade (affecting to specific domains only, or not affecting to nodemanager), but its difficulty is around on how to know which files do refer to a JDK location.

The initial list of files to change will be :
* $INSTALL_HOME/wlserver_10.3/common/bin/commEnv.sh
* $INSTALL_HOME/user_projects/domains/<mydomain>/bin/setDomainEnv.sh
* $INSTALL_HOME/wlserver_10.3/common/nodemanager/nodemanager.properties
* $INSTALL_HOME/utils/bsu/bsu.sh
* $INSTALL_HOME/utils/quickstart/quickstart.sh
* $INSTALL_HOME/utils/uninstall/uninstall.sh
even that a more exhaustive way to determine them, will be to run the following command:
find . -type f -name "*.sh" -exec grep -il JAVA_HOME {} \;

Can I Install or Restore a Patch Now Appearing As Invalidated In Smart Update?

I'm installing a set of new patches. One of them is supposed to replace an older patch which is now marked in Smart Update as "invalidated."

In the event there is a problem with the application after the new patches are installed, I would like to restore the original combination of patches. Is it possible to restore the original patch even though it is now invalidated?


Cause


I'm installing a set of new patches. One of them is supposed to replace an older patch which is now marked in Smart Update as "invalidated."

In the event there is a problem with the application after the new patches are installed, I would like to restore the original combination of patches. Is it possible to restore the original patch even though it is now invalidated?

Solution

If a patch is invalid, that means that there is a problem with it, and we're specifically preventing you from using it. You don't want to install that patch because you'd be introducing errors into your system.

Attempting to install or restore an invalidated patch is thus strongly discouraged, for your own safety.

You should be sure to test the new patches thoroughly in your test environment before putting them into production. Work out any problems with the new patches there. Then when you're ready to put the new patches into production, you can do so with confidence that you won't need to revert to an older, problematic version.

Smart Update Fails to Apply Patch: java.io.IOException: Unable to backup file


When attempting to install a patch using Smart Update (BSU), the following error occurs:
java.io.IOException: Unable to backup file <path>/weblogic_patch.jar to <path>/weblogic_patch.jar.bak
Verbose logging gives some more details:
java.util.concurrent.ExecutionException: com;bea.plateng.patch.PatchInstallationException: java.io.IOException: Unable to backup file <path>/weblogic_patch.jar

Cause

This is a common problem customers experience when they try to apply patches while the WLS domain is running. Because the domain is running, the jar which Smart Update needs to write to is locked, and this error occurs.

Solution

Please stop the WLS domain, and make sure there are no processes or services running which would be holding a lock on that jar file. If Node Manager is running, you should also stop that.
Once all those processes and/or services are stopped, please run Smart Update and apply the patch. It should work.

WebLogic Server: Smart Update Throwing OutOfMemoryError


An issue has been reported of the Smart Update utility throwing an OutOfMemoryError when using bsu.cmd or bsu.sh script inside WL_HOME/utils/bsu directory. Below is the exception trace in bsu.log at the time of the issue.

JVMDUMP013I Processed Dump Event "systhrow", detail "java/lang/OutOfMemoryError".
Exception in thread "main" java.lang.OutOfMemoryError
at org.apache.xmlbeans.impl.store.Cur.createElementXobj(Cur.java:257)
at org.apache.xmlbeans.impl.store.Cur$CurLoadContext.startElement(Cur.java:2992)
at org.apache.xmlbeans.impl.store.Locale$SaxHandler.startElement(Locale.java:3194)
at org.apache.xmlbeans.impl.piccolo.xml.Piccolo.reportStartTag(Piccolo.java:1082)
at org.apache.xmlbeans.impl.piccolo.xml.PiccoloLexer.parseOpenTagNS(PiccoloLexer.java:1473)
at org.apache.xmlbeans.impl.piccolo.xml.PiccoloLexer.parseTagNS(PiccoloLexer.java:1362)
at org.apache.xmlbeans.impl.piccolo.xml.PiccoloLexer.parseXMLNS(PiccoloLexer.java:1293)
at org.apache.xmlbeans.impl.piccolo.xml.PiccoloLexer.parseXML(PiccoloLexer.java:1261)
at org.apache.xmlbeans.impl.piccolo.xml.PiccoloLexer.yylex(PiccoloLexer.java:4808)
at org.apache.xmlbeans.impl.piccolo.xml.Piccolo.yylex(Piccolo.java:1290)
at org.apache.xmlbeans.impl.piccolo.xml.Piccolo.yyparse(Piccolo.java:1400)
at org.apache.xmlbeans.impl.piccolo.xml.Piccolo.parse(Piccolo.java:714)
at org.apache.xmlbeans.impl.store.Locale$SaxLoader.load(Locale.java:3435)
at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:1270)
at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:1257)
at org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:345)
at com.bea.cie.common.dao.xbean.XBeanDataHandlerSpiImpl.create(XBeanDataHandlerSpiImpl.java:130)
at com.bea.cie.common.dao.xbean.XBeanDataHandlerSpiImpl.create(XBeanDataHandlerSpiImpl.java:111)
at com.bea.plateng.patch.dao.cat.PatchCatalogFactory.create(PatchCatalogFactory.java:163)
at com.bea.plateng.patch.dao.cat.PatchCatalogFactory.create(PatchCatalogFactory.java:85)
at com.bea.plateng.patch.dao.cat.PatchCatalogFactory.create(PatchCatalogFactory.java:71)
at com.bea.plateng.patch.dao.cat.PatchCatalogHelper.getPatchCatalog(PatchCatalogHelper.java:57)
at com.bea.plateng.patch.PatchSystem.updatePatchCatalog(PatchSystem.java:363)
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)

Exception When Using SmartUpdate In Offline Mode

The following exception is seen when installing patch in offline mode using the Oracle Smart Update command line option:

$ ./bsu.sh -prod_dir=WEBLOGIC_HOME -patchlist= -verbose -install
Unable to locate valid patch target with BEA Home "BEA_HOME" and Product Directory "WEBLOGIC_HOME

Cause


When installing patches in offline mode for servers which do not have access to the Internet, the required patch is usually downloaded by logging into the Oracle SmartUpdate server from a machine which has access to the Internet and retrieving the patch on this machine. Once we download the patch jar files, we copy the .jar, prod-info.xml and patch-catalog.xml files from BEA_HOME\utils\bsu\cache_dir on the machine where we downloaded to the same directory on the machine where we want to use SmartUpdate to install the patch in offline mode.
The issue described above happens when you download the patch using SmartUpdate and copy the <patchid>.jar, prod-info.xml and patch-catalog.xml files to a machine which has an older version of SmartUpdate, and then try to install the patch in offline mode.

Note on Troubleshooting Smart Update Issues.

What is Smart Update?

Smart Update is the Oracle-recommended tool for applying patches to WebLogic Server. It is located under your BEA_HOME or MW_HOME directory under the directory utils/bsu and is named bsu.cmd (Windows) or bsu.sh (UNIX). Smart Update is always recommended to apply patches because it takes care of all the details for you, and more important, it provides a check to make sure that the patch you are applying does not conflict with any patches already on your system.

Using Smart Update


Detailed step-by-step instructions on how to apply patches to your system using Smart Update  click here.

Other Smart Update Issues


How to Apply WebLogic Server (WLS) Patches Using Smart Update

There are two ways to apply patches to a system:

1. Using Smart Update

You can apply the patch using Smart Update with the following steps:


  1. Extract the contents from the zip file: you will have a jar file and patch-catalog_xxx.xml. A readme file may also be included.
  2. Copy the files (for example, E5W8.jar and WGQJ.jar) and the patch-catalog_xxx.xml from the zip file to the target machine. You do not need the readme file. Copy the files to the appropriate cache_dir directory for the target system: for example, on Windows, %MIDDLEWARE_HOME%\utils\bsu\cache_dir, or on UNIX, $MIDDLEWARE_HOME/utils/bsu/cache_dir. The directory MW_HOME\utils\bsu\cache_diris created as the default patch download directory when you install Smart Update 3.3.0.
  3. Run Smart Update and apply the patches and/or patch sets to the target system. This can be done using the Smart Update GUI or the command-line interface

a. Smart Update in graphical (GUI) mode


  1. Run the <MIDDLEWARE_HOME>/utils/bsu/bsu script (bsu.sh for UNIX, bsu.cmd for Windows). This will start the Smart Update GUI.
  2. Look for the patches you copied in the "Downloaded Patches" section at the bottom.
  3. Select the "Apply" button for each pat
  4. Download the patch from My Oracle Support (MOS).
  5. ch you want to apply. This will validate the patch and apply it to the whole installation.