IBM Support

IV12309: PROMOTING BETWEEN TWO SERVERS IN THE SAME CELL CAN CAUSE THE COD E TO CREATE THE MOVETEMPDB IN THE SAME PLACE CAUSING A CONFLICT.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When promoting between two servers in the same cell the
custom setting are ignored when creating the MoveDataDB and
a conflict is created.

Exceptions such as the following may be seen in the
SystemOut.log:

com.ibm.sr.api.impl.MoveDataDBFactoryImpl createDB GSR5000I:
Captured exception [205]: java.sql.SQLException: Failed to start
database
'<WAS_PROFILE>/installedApps/<CELL_NAME>/ServiceRegistry.ear/Mov
eDataTempDB' with class loader
com.ibm.ws.bootstrap.ExtClassLoader@2e3e2e3e, see the next
exception for details.

Caused by: java.sql.SQLException: Another instance of Derby may
have already booted the database
<WAS_PROFILE>/installedApps/<CELL_NAME>/ServiceRegistry.ear/Move
DataTempDB

Caused by: ERROR XSDB6: Another instance of Derby may have
already booted the database
<WAS_PROFILE>/installedApps/<CELL_NAME>/ServiceRegistry.ear/Move
DataTempDB.

com.ibm.sr.api.impl.MoveDataDBFactory getMoveDataDBFactoryImpl
com.ibm.serviceregistry.exception.movedata.MoveDataSQLException:
GSR0424E: A Problem occurred with the temporary database used to
capture and load into WSRR

Local fix

  • NA

Problem summary

  • The WSRR prefix was not read when the temporary promotion
database was created. Therefore for a WSRR with a prefix the
default location was used, which in this case was already open
by the WSRR without a prefix.

Problem conclusion

  • WSRR was changed to read the prefix and use it when
determining the temporary database location.

This fix is targeted for inclusion in fix pack 3 for WSRR v7.5.

Temporary fix

  • 



Comments


    

  • 



APAR Information




    

  • APAR number
    IV12309
    • 

  • Reported component name
    SERVICE REGISTR
    • 

  • Reported component ID
    5724N7200
    • 

  • Reported release
    750
    • 

  • Status
    CLOSED  PER
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt
    • 

  • Submitted date
    2011-12-14
    • 

  • Closed date
    2012-03-02
    • 

  • Last modified date
    2012-08-28
    • 





    

  • APAR is sysrouted FROM one or more of the following:
    

    • 

  • APAR is sysrouted TO one or more of the following:
    

    • 



Fix information


    

  • Fixed component name
    SERVICE REGISTR
    • 

  • Fixed component ID
    5724N7200
    • 



Applicable component levels


    

  • R750  PSY
       UP
    • 








      
              
                            

              

              [{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSWLGF","label":"WebSphere Service Registry and Repository"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
              

                          

          
 
        

      

    

      

        

          

            
Document Information


            

            


                        

            Modified date:
            

            28 August 2012
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback