PQ56586: ATTEMPT TO REMOVE A SERVERGROUP FAILED. ADMINSERVER WILL NOT START AFTER THE SERVERGROUP COULD NOT BE REMOVED FROM REPOSITORY | |||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||
APAR status Closed as unreproducible. Error description The following things were done successfully: 1. Created an application server and an enterprise app using xml-import. 2. Modified the appserver name in (1) to AppServerCloneName using wscp. 3. Created a ServerGroup from the AppServerCloneNameusing wscp. 4. Created a Clone of (3) and called it AppServerClone_2 5. Removed AppServerClone_2 using wscp. 6. Remove AppServerCloneName (servergroup)failed. A wscp list command fails to get the server group name. Further attempt to start the adminserver generates the following exception: java.sql.SQLException: ORA-08177: can't serialize access for this transaction. at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:1 at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:543) at oracle.jdbc.ttc7.TTC7Protocol.executeFetch(TTC7Protocol.javaLocal fix Problem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server 4.01 Advanced * * Edition users utilizing wscp * **************************************************************** * PROBLEM DESCRIPTION: Attempting to remove a server group * * or running clone via wscp results in * * DB corruption * **************************************************************** * RECOMMENDATION: * **************************************************************** When attempting to remove a running clone from a server group the relationship between the clone and the server group was removed first. Then, the remove was attempted and failed. However, the relationship between the clone and server group was already deleted and not re-established upon the remove failure. A check was added to the wscp code to verify that the clone was not running it prior to deleting the relationship or performing the remove. This eliminated that problem of getting the DB in an inconsistent state. The fix was dropped into PTF 4.02.Problem conclusion Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ56586
IBM Group: Software Group
Modified date: Feb 12, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.