Conference clusta::acms

4113.0. "version mis-match or ACMS problem ?" by TAVIS::MIRO () Thu Feb 27 1997 13:03

            <<< NOMAHS::DISK$NOMAHS1:[NOTES$LIBRARY]RDB_60.NOTE;1 >>>
       -< Oracle Rdb - Still a strategic database for DEC on Alpha AXP! >-
================================================================================
Note 5086.0                Version mis-match problem ?                No replies
ORAREP::TAVIS::MIRO                                  73 lines  27-FEB-1997 12:57
--------------------------------------------------------------------------------
    We have move an ACMS application from a node :
      AlphaVMS 6.2    rdb 6.1-04   Turbo 8400     ACMS 4.1-0
    
    To  AlphaVMS 6.2  RDB 6.1-1    Alphaserver 1000a        ACMS 4.1-0
    
    
    We have move the acms images and all required components.
    
    The acms server dies.
    From the RDB monitor log I can see that the server attached to the
    database.
    The acms server has a initialization routine that starts a transaction
    The process dies when trying to perform the initializtion routine.
    (SQLMOD)
    
    My question is : Does this have anything to do with the difference
    versions of RDB ?
    
    Please advise.
    -----------------------------------------------------------------------
    27-FEB-1997 19:52:21.60 - received user attach request from 2FE:1
      - process name ACMS00BSP002001, user TFH_ACMS_SUP
      - for database "_$1$DKA100:[000000.RDB.AP0000]AP_DB.RDB;3"
      - sending normal user attach reply to 2FE:1
    
    27-FEB-1997 19:52:21.60 - received user attach request from 2FD:1
      - process name ACMS00BSP001000, user TFH_ACMS_SUP
      - for database "_$1$DKA100:[000000.RDB.AP0000]AP_DB.RDB;3"
      - sending normal user attach reply to 2FD:1
    
    27-FEB-1997 19:52:22.04 - received user image termination from
    000002FE:1
      - abnormal user termination detected
      - database monitor created recovery process RDM_RB_1 (000002FF)
      - user termination suspended until recovery ready
    27-FEB-1997 19:52:22.48 - received recovery attach from 2FF:1
      - process name RDM_RB_1, user SYSTEM
      - sending normal recovery attach reply to 2FF:1
    
    27-FEB-1997 19:52:22.50 - received recovery ready from 2FF:1
      - process name RDM_RB_1, user SYSTEM
    
    -----------------------------------------------------------------------
    $ acms/start appl ap_appl_v0001
    %ACMSOPR-E-STRTAPLERR, Error while attempting to START APPLICATION
    AP_APPL_V0001
    -ACMSEXC-E-WP_TRM, Server Process for server AP_RW_SERVER defined in
    group AP_GR
    OUP_V0001 died unexpectedly
    -ACMSTWP-E-INIT_ERR, Error executing server initialization procedure
    %ACMSOPR-E-ERROR, Some operations may not have been performed
    
    -------------------------------------------------------------------
    
    Process UIC  : [001,004]
    Process name : ACMS01ACC001000
    Username     : SYSTEM
    Image file   : $1$DKA0:[SYS0.SYSCOMMON.][SYSEXE]ACMSACC.EXE;1
    
    %ACMSACC-I-EVENT, Event
    -ACMSACC-E-ERRSTARTA, Error occured starting application
    -ACMSEXC-E-WP_TRM, Server Process for server !AS defined in group !AS
    died unexp
    ectedly
    -----------------------------------------------------------------------
    Type   : ERROR     Time   : 27-FEB-1997 19:51:57.93
    Appl   : AP_APPL_V0001
    Text   : Error executing server initialization procedure
    -SYSTEM-F-ACCVIO, access violation, reason mask=04, virtual
    address=00884E18, PC
    =010E000D, PS=00020194
    -----------------------------------------------------------------------
    
    x-posted rdb

    
    	It's not an ACMS problem.  Try running the task debugger and set
    a breakpoint in the server initialization and step through the code.
    
    Bill
    

    Thanks.
    The same application works fine on the devlopment machine, however when
    we move the files to the "production" machine we get the mentioned
    error.
    Your help in pointing to "things that could go wrong" in moving from
    a devlopment to production will be of great help.
    As to versions the only difference is that RDB in development is 6.1-04
    and in production 6.1-1
    
    Thanks,
    Moshe
    

    
    If your production only has the Run-time version of ACMS, you'll
    need to copy the file SYS$SYSTEM:ACMSDBG.EXE from your development
    system.  This will give you access to the ACMS task debugger.
    
    Then you should be able to do an ACMS/DEBUG <tdb name> and start
    the server that is failing and walk through the init code.
    
    The times I've seen ACCVIO is the RDB code is when I moved code
    from a newer version of RDB to a system with an older version
    and didn't re-compile.  It's the INIT procedure that is
    failing.
    
    Bill
    

    Thanks bill. I will try it.
    
    Moshe