PQ93691: RUNNING IN 'PEER RESTART RECOVERY' MODE, MESSAGE BBOO0249E MAY BE SEEN DURING SERVER STARTUP, IF SYSTEMS ARE DIFFERENT LEVELS | |||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description When WebSphere z/OS is running in 'Peer Restart Recovery' mode, and all of the WebSphere Servers involved in the 'Peer Restart Recovery' mode are NOT at the same Service Level, WebSphere servers may fail with message: BBOO0249E INSTALLATION ROOT AND CONFIGURED ROOT ARE NOT RUNNING AT THE SAME SERVICE LEVEL. USE SMP/E TO RETURN TO LEVEL <service level> AND THEN USE BACKOUTPTF.SH TO RETURN TO LEVEL <service level> BEFORE SMP/E RESTORING OFF. .Local fix If running in 'peer restart recovery' mode, ensure all websphere servers involved are at the same service level.Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V5.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: The post installer prevents the * * WebSphere Application Server from * * starting during Peer Restart and * * Recovery mode if the systems are * * running at mixed service levels. * **************************************************************** * RECOMMENDATION: * **************************************************************** The post installer can prevent the WebSphere Application Server from starting during Peer Restart and Recovery mode if the systems are running at mixed service levels. This occurs if the configured root (WAS_HOME) has been brought up to a certain service level by the post installer and then this WAS_HOME is brought during Peer Restart and Recovery mode on another system that is running at a lower service level. Also, if said WAS_HOME is brought up by Peer Restart Recovery on another system that is running at a higher service level, then the post installer will run against that WAS_HOME to bring it up to the current service level of the recovering system. When Peer Restart and Recovery mode has completed and that WAS_HOME is restarted on its home system, the post installer component can fail to start the WebSphere Application Server because the WAS_HOME is now at a higher service level than its home system because it was brought up to a higher service level during Peer Restart and Recovery mode. This defect only applies to systems running Peer Restart and Recovery. This message will appear on the console BBOO0249E INSTALLATION ROOT AND CONFIGURED ROOT ARE NOT RUNNING AT THE SAME SERVICE LEVEL. USE SMP/E TO RETURN TO LEVEL <service level> AND THEN USE BACKOUTPTF.SH TO RETURN TO LEVEL <service level> BEFORE SMP/E RESTORING OFF.Problem conclusion The post install process was changed not to run when in Peer Restart and Recovery mode. In addition, when a service level mismatch is detected, message BBOO0287A will be issued and the operator will be able to choose whether the server should continue starting by replying 'CONTINUE' or 'CANCEL'. Changes will be made to the V5.0x and V5.1x WebSphere Application Server for z/OS Information Centers. To access the latest online documentation, go to the product library page at: www.ibm.com/software/webservers/appserv/zos_os390/library/ The list, contained in the article "Setting up peer restart and recovery," that describes the things a customer should do before using Peer Restart and Recovery will be updated to includ the following item: Check the service level of the application servers you are using for peer restart and recovery. Even though it is possible to perform peer restart and recovery across different service levels, minor differences in configuration data can prevent an application server from starting if the service level of the pee system is different than the service level of the failed system. When the post installer detects a service level difference, it sends a message to the operator asking if recovery should continue. You can set up your automation to provide a positive response to this message and allow recovery to continue under these conditions. However, if startup is attempted and fails, the transactions needing to be recovered are now associated with the peer system, and RRS must be stopped on that system before these transactions can be moved back to the failed system. Therefore it is recommended that you modify your ARM policy to turn off peer restart and recovery while you are adding WebSphere Application Server service on your sysplex to ensure that the systems performing peer restart and recovery are at the same service level as the failed system. (See Using RRS panels to resolve indoubt units of recovery for more information about peer restart and recovery messages.) The following description of Message BB000287A will be added to the article "Using RRS panels to resolve indoubt units of recovery:" If you receive the console message: BBOO0287A SERVER IS STARTING OUT OF PLACE AT MIXED PTF LEVELS. REPLY CONTINUE OR CANCEL * Respond CANCEL to abort peer restart and recovery processing before the server is restarted on a system that is running at a different service level than the failed system. * Respond CONTINUE to allow the server to restart. Note: If startup is attempted and fails, the transactions needing to be recovered are now associated with the peer syst and RRS must be stopped on that system before these transacti can be moved back to the failed system. The following publication was revised as a result of APAR PQ93691: ________________________________________________________________ WebSphere Application Server V5 for z/OS Messages and Codes GA22-7915-01 _______________________________________________________________ This APAR requires changes to documentation. NOTE: Periodically, we refresh the documentation on our Web site, so the changes might have been made before you read this text. To access the latest on-line documentation, go to the product library page at: www.ibm.com/software/webservers/appserv/zos_os390/library.html ________________________________________________________________ Chapter 1, pg. 45 New message Message identifier - BBOO0287A Explanation: The server has been restarted on a system other than the one on which it was configured to run. The PTF level on this system and the configured system are different. The server may not be able to start on this system. User Response: Reply CONTINUE to the WTOR if you are willing to accept the risk associated with starting the server on this system, or CANCEL if you would like the server to terminate. Refer to the documentation on Peer Restart and Recovery in the WebSphere Application Server Infocenter for more information on the risks associated with starting the server out of place at mixed PTF levels. ________________________________________________________________ APAR PQ93691 is associated with SERVICE LEVEL W502017 of WebSphere Application Server V5.0 for z/OS.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: PQ93694 Modules/Macros
Publications Referenced
|
Document Information |
Current web document: swg1PQ93691.html
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PQ93691
IBM Group: Software Group
Modified date: Dec 2, 2004
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.