[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference orarep::nomahs::dec_data_distributor

Title:The Replication Option for Rdb
Notice:Product renamed to Replication Option for Rdb
Moderator:BROKE::PROTEAU
Created:Wed Mar 02 1994
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:287
Total number of notes:1231

277.0. "ACCVIO on RDB$VINTAGE" by M5::PTAKEO () Wed Apr 09 1997 19:45

Hi,

	I have a customer who is getting an error (ACCVIO) during his 
transfer on  AlphaServer 1000 4/200, OpenVMS V6.2, Rdb V6.1-04, ROR V6.0-11
and Transparent Gateway for Rdb (with DB2).

	I've tried to find out the reason for that problem, but I  failed.
I've saw the note #260, but I'm not sure whether that error is similar.

	Someone has any idea or suggestion ?

	Thanks...Pedro


======== TRANSFER LOG =====================================
 
$ SET NOVER 
$ SHOW = "SHOW" 
$ RUN = "RUN" 
$ LOGOUT = "LOGOUT" 
$ SHOW PROCESS  
 
 7-APR-1997 11:55:33.44   User: SYSTEM           Process ID:   00000787 
                          Node: C22006           Process name: "DDAL_COPY_02 " 
 
Terminal:           MBA4466: 
User Identifier:    [SYSTEM] 
Base priority:      4 
Default file spec:  SYS$SYSROOT:[SYSMGR] 
$ DEFINE DDAL$CP_CONTINUE "SUCCESS" 
$ DEFINE/TRANS=TERMINAL DDAL$TRANSFER_NAME BDA_BDACOM 
$ DDAL$CP_ACTION :== E 
$ DDAL$CP_RETRY_ITERATION == 00 
$ @DISCO01:[RLAM.SNS30SIS.SNS30DCL]BDACOM_PROLOGO.COM  
$!***************************************************************************** 
$!              ATUALIZACAO DA TABELA ACOMP_ORCAMENTARIO 
$!***************************************************************************** 
$!  
$  SET VER 
$  SET NOON 
$! 
$  RUN/NODEB NS30$EXE:PNS30BA1 
$  MCR SQL$ 
attach 'file bdacom'; 
drop index acom_srt; 
%SQL-F-INDNOTDEF, Index ACOM_SRT is not defined in this database or schema 
drop index acom_srt2; 
%SQL-F-INDNOTDEF, Index ACOM_SRT2 is not defined in this database or schema 
drop index atlo_srt; 
%SQL-F-INDNOTDEF, Index ATLO_SRT is not defined in this database or schema 
drop index bpaa_srt; 
%SQL-F-INDNOTDEF, Index BPAA_SRT is not defined in this database or schema 
drop index cbi_srt; 
%SQL-F-INDNOTDEF, Index CBI_SRT is not defined in this database or schema 
drop index clor_cd_class_hsh; 
%SQL-F-INDNOTDEF, Index CLOR_CD_CLASS_HSH is not defined in this database or 
schema 
drop index ctco_srt; 
%SQL-F-INDNOTDEF, Index CTCO_SRT is not defined in this database or schema 
drop index deat_srt; 
%SQL-F-INDNOTDEF, Index DEAT_SRT is not defined in this database or schema 
drop index empd_empd_nr_empd_srt; 
%SQL-F-INDNOTDEF, Index EMPD_EMPD_NR_EMPD_SRT is not defined in this database 
or schema 
drop index etap_etap_nr_empd_srt; 
%SQL-F-INDNOTDEF, Index ETAP_ETAP_NR_EMPD_SRT is not defined in this database 
or schema 
drop index imob_srt; 
%SQL-F-INDNOTDEF, Index IMOB_SRT is not defined in this database or schema 
commit; 
exit 
$ EXIT 
$ RUN DDAL$COPY_PROCESS 
 
Product version:	DEC Data Distributor V6.0-11 
 
-----  7-APR-1997 12:10:59.17 ----- Process         ------------------------- 
Process name:  DDAL_COPY_02                  Priority:  5                      
  
Username:  SYSTEM                            UIC:  [SYSTEM]                    
  
Nodename:  C22006                            PID:  00000787                    
  
Privileges currently enabled: 
    CMKRNL, CMEXEC, SYSNAM, GRPNAM, ALLSPOOL, DETACH, DIAGNOSE, LOG_IO, GROUP,  
    ACNT, PRMCEB, PRMMBX, PSWAPM, ALTPRI, SETPRV, TMPMBX, WORLD, MOUNT, OPER,  
    EXQUOTA, NETMBX, VOLPRO, PHY_IO, BUGCHK, PRMGBL, SYSGBL, PFNMAP, SHMEM,  
    SYSPRV, BYPASS, SYSLCK, SHARE, UPGRADE, DOWNGRADE, GRPPRV, READALL,  
    SECURITY 
 
Image privileges: 
    SYSPRV, BYPASS, SYSLCK, SECURITY 
 
Image name: 
    C22006$DKA0:[SYS0.SYSCOMMON.][SYSEXE]DDAL$COPY_PROCESS.EXE 
 
Transfer database = DISCO01:[RLAM.DDD]DDAL$TR_DB 
Transfer name     = BDA_BDACOM                      
Transfer option   = E (Extraction transfer) 
 
12:10:59  %DDAL-I-READTRDEF, reading the transfer definition from the transfer 
database 
12:11:01  %DDAL-I-ATTACHSDB, attaching to source database BDA 
12:11:07  %DDAL-I-ATTACHTDB, attaching to target database BDACOM 
12:11:08  %DDAL-I-STADATTRM, starting data transfer/modification 
 
          %DDAL-I-DEFGBLFLD, defining global field RDBVMS$TRANSFER_OBJECT_NAME 
          %DDAL-I-DEFGBLFLD, defining global field RDBVMS$TRANSFER_OBJECT_TYPE 
          %DDAL-I-DEFGBLFLD, defining global field RDB$VINTAGE_TIMESTAMP 
          %DDAL-I-DEFGBLFLD, defining global field RDBVMS$VINTAGE_TSER 
          %DDAL-I-DEFGBLFLD, defining global field RDBVMS$VINTAGE_TRANSFER_ADDR 
          %DDAL-I-DEFGBLFLD, defining global field RDBVMS$VINTAGE_TRANSFER_NODE 
          %DDAL-I-DEFGBLFLD, defining global field RDBVMS$VINTAGE_TRANSFER_BUSY 
          %DDAL-I-DEFGBLFLD, defining global field RDBVMS$VINTAGE_TRANSFER_ID 
          %DDAL-I-DEFGBLFLD, defining global field RDBVMS$VINTAGE_TRANSFER_NAME 
12:11:08  %DDAL-I-DEFINEREL, defining relation RDB$VINTAGE 
12:11:09  %DDAL-I-DEFINEREL, defining relation RDBVMS$TRANSFER_OWNER 
          %DDAL-I-DEFINEIDX, defining index RDBVMS$VINTAGE_INDEX1 
12:11:10  %DDAL-I-LOARELDAT, loading data for relation RDB$VINTAGE 
 
          %DDAL-I-DEFGBLFLD, defining global field DEAT_CD_ATIVIDADE 
	.
	.
	.
	.
	.

12:15:19  %DDAL-I-RELATSTAT,                RELATION DETALHE_ATIVIDADE 
 
          %DDAL-I-RECFRMSRC,        552 records copied from BDA 
 
          %DDAL-I-RECTOTARG,        552 records copied into BDACOM 
 
12:15:19  %DDAL-I-LOARELDAT, loading data for relation IMOBILIZADO 
 
12:15:21  %DDAL-I-RELATSTAT,                RELATION IMOBILIZADO 
 
          %DDAL-I-RECFRMSRC,       1283 records copied from BDA 
 
          %DDAL-I-RECTOTARG,       1283 records copied into BDACOM 
 
12:15:21  %DDAL-I-LOARELDAT, loading data for relation RDB$VINTAGE 
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=00000040, 
PC=00147AF4, PS=0000001B 
 
  Improperly handled condition, image exit forced. 
    Signal arguments:   Number = 00000005 
                        Name   = 0000000C 
                                 00000000 
                                 00000040 
                                 00147AF4 
                                 0000001B 
 
    Register dump: 
    R0  = 0000000000000001  R1  = 0000000000000000  R2  = 0000000000010EC8 
    R3  = 00000000002198CC  R4  = 0000000000000000  R5  = 0000000000220650 
    R6  = 0000000000000000  R7  = 0000000000219ADC  R8  = 0000000000219AF1 
    R9  = 000000007FF9C400  R10 = 000000007FF9D228  R11 = 000000007FFBE3E0 
    R12 = 0000000000000000  R13 = 000000007EF06900  R14 = 0000000000000000 
    R15 = 000000007EF05DA0  R16 = 0000000000000000  R17 = 000000000015B0E8 
    R18 = 000000000000000E  R19 = 0000000000000000  R20 = 0000000000000150 
    R21 = 00000000003A9CF0  R22 = 0000000000000000  R23 = 00000000013884A3 
    R24 = 000000007EE67280  R25 = 0000000000000001  R26 = 0000000000147AF0 
    R27 = 0000000000159068  R28 = FFFFFFFFFFFFFFFF  R29 = 0000000000000000 
    SP  = 000000007EE68000  PC  = 0000000000147AF4  PS  = 000000000000001B 
  SYSTEM       job terminated at  7-APR-1997 12:15:22.71 
 
  Accounting information: 
  Buffered I/O count:          212826         Peak working set size:  21488 
  Direct I/O count:             28441         Peak page file size:    76576 
  Page faults:                   3007         Mounted volumes:            0 
  Charged CPU time:           0 00:01:54.35   Elapsed time:     0 00:19:50.02 

T.RTitleUserPersonal
Name
DateLines
277.1VMS 6.2 patches up to date?BROKE::PROTEAUJean-Claude ProteauFri Apr 11 1997 12:2920
Pedro,

Is the ACCVIO problem repeatable?

I doubt that the problem reported in note 260 has any relevance to this case.
The Rdb/Disptach engineer I think told me it was a problem introduced in Rdb
7.0.  You can always post a note in the appropriate Rdb notes conference and
ask if the problem might also exist in earlier versions.

I looked at the linker map for the copy process image to see if the PC at
which the error occurred was in our code or not.  It was not.  Either it is in
some system routine, or it is in Rdb/Dispatch.

Something worth checking on is whether or not your customer has all the neces-
sary patches to VMS 6.2.  I've heard that there have been a lot of problems
without these VMS fixes.  There is some information about this in the appro-
priate Rdb notes conference (someone mentioned note 9.?, but I can't be sure
that's the correct one)>

Claude
277.2I will checkM5::PTAKEOMon Apr 14 1997 21:036
Hi,  Claude

	Thanks for your help. I will ask my customer about vms patch, 
and see note 9.x in RDB conference.

Pedro