| 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 |
Here is a list of the logfile errors with the problem that we are
facing I don't think that it is necessary to upgrade. This error
occured today. It is connected to note 214 the original note
Maybe something can be detected from here concerning our
problem.
regards
%SET-W-NOTSET, error modifying HSC000$DUA5:
-CLI-E-IVDEVTYPE, invalid device type - specify a mailbox device
$ SET NOVERIFY
Wait ...
***********************************************************************
--- BAPS ---
Batch : BAPS transfer to ERF020 job Started At 27-MAY-1996 02:04:02.61 On ATH651
***********************************************************************
%BAPS-I-TRANS, Initiate the transfer VDD from BAPS to ERF020
%RDO-F-DDALERR, DEC Data Distributor fatal error
-DDAL-E-TNSF_NAME_USED, transfer name already exists
Job BAPS_TO_ERF020_TRANSFER (queue SYS$BATCH, entry 840) holding until 28-MAY-1996 02:04
*********************************************************************
Batch : BAPS transfer to ERF020 job Ended At 27-MAY-1996 02:04:16.77 On ATH651
End Status: SUCCESS
*********************************************************************
BAPS_GR job terminated at 27-MAY-1996 02:04:16.94
Accounting information:
Buffered I/O count: 230 Peak working set size: 3431
Direct I/O count: 348 Peak page file size: 14700
Page faults: 4342 Mounted volumes: 0
Charged CPU time: 0 00:00:03.42 Elapsed time: 0 00:00:16.92
**********************************************************************************
%SET-W-NOTSET, error modifying MBA3573:
-CLI-E-IVDEVTYPE, invalid device type - specify a mailbox device
$ SET NOVERIFY
Wait ...
$ SHOW = "SHOW"
$ RUN = "RUN"
$ LOGOUT = "LOGOUT"
$ SHOW PROCESS
27-MAY-1996 02:04:18.44 User: BAPS_GR Process ID: 20415A5E
Node: ATH651 Process name: "DDAL_COPY_01 "
Terminal: MBA3573:
User Identifier: [BAPS_GR]
Base priority: 4
Default file spec: APPLIC_2:[BAPS_GR]
$ DEFINE DDAL$CP_CONTINUE "SUCCESS"
$ DEFINE/TRANS=TERMINAL DDAL$TRANSFER_NAME BAPS_GR_TO_ERF_GR00
$ DDAL$CP_ACTION :== E
$ DDAL$CP_RETRY_ITERATION == 00
$ RUN DDAL$COPY_PROCESS
Product version: VAX Data Distributor V2.4-0
----- 27-MAY-1996 02:04:20.03 ----- Process -------------------------
Process name: DDAL_COPY_01 Priority: 5
Username: BAPS_GR UIC: [BAPS_GR]
Nodename: ATH651 PID: 20415A5E
Privileges currently enabled:
TMPMBX, NETMBX
Image privileges:
SYSPRV, BYPASS, SYSLCK, SECURITY
Image name:
$2$DUA3:[SYS1.SYSCOMMON.][SYSEXE]DDAL$COPY_PROCESS.EXE
Transfer database = SYS$COMMON:[SYSEXE]DDAL$TR_DB
Transfer name = BAPS_GR_TO_ERF_GR00
Transfer option = E (Extraction transfer)
02:04:20 %DDAL-I-READTRDEF, reading the transfer definition from the transfer database
02:04:26 %DDAL-I-ATTACHSDB, attaching to source database BAPS$GR_ROOT:[DATABASE]BAPS_DB.RDB
02:04:30 %DDAL-I-CRETARGDB, creating target database ATH853"ERF_XFR_GR00"::ERF$TRANSFER:XFR_DB.RDB
----- 27-MAY-1996 02:04:31.93 ----- Error -------------------------
%RDB-F-IO_ERROR, input or output error
-SYSTEM-F-INVLOGIN, login information invalid at remote node
$ @DDAL$EPILOGUE ATH853"ERF_XFR_GR00"::ERF$COMMAND:ERF_PRO_UPD_1.COM
$ GOTO Skip_Comments
$ Skip_Comments:
$
$! Save the return status from the DDAL$COPY_PROCESS image in DDAL$SAVE_STATUS.
$
$ DDAL$SAVE_STATUS :== %X0126839B
$ ON SEVERE_ERROR THEN GOTO Cleanup
$
$! DEFINE DDAL$CP_CONTINUE based on the status value received from the
$! DDAL$COPY_PROCESS image.
$!
$! SUCCESS = DDAL$COPY_PROCESS succeeded
$! RETRY = DDAL$COPY_PROCESS failed but should be retried
$! PRO_RETRY = The prologue failed. The transfer should be retried.
$! PRO_FAIL = The prologue failed. The transfer should not be retried.
$! FAIL = Anything else should be a copy process failure that should not
$! be retried.
$
$ IF DDAL$SAVE_STATUS .EQ. %X012683AB
$ ELSE
$ IF DDAL$SAVE_STATUS .EQ. %X012683A3
$ ELSE
$ IF DDAL$SAVE_STATUS .EQ. %X0126C44B
$ ELSE
$ IF DDAL$SAVE_STATUS .EQ. %X0126C453
$ ELSE
$ DEFINE DDAL$CP_CONTINUE "FAIL"
%DCL-I-SUPERSEDE, previous value of DDAL$CP_CONTINUE has been superseded
$ ENDIF
$ ENDIF
$ ENDIF
$ ENDIF
$
$! Now execute the user's epilogue procedure named in the transfer definition.
$
$ @ATH853"ERF_XFR_GR00"::ERF$COMMAND:ERF_PRO_UPD_1.COM
%DCL-E-OPENIN, error opening ATH853"ERF_XFR_GR00"::ERF$COMMAND:ERF_PRO_UPD_1.COM; as input
-RMS-E-ACC, ACP file access failed
-SYSTEM-F-INVLOGIN, login information invalid at remote node
$
$! Reconstruct the exit status so that the transfer monitor will understand
$! what happened.
$
$ RESULT :== FAIL
$
$ IF RESULT .EQS. "SUCCESS" THEN $EXIT %X012683AB
$ IF RESULT .EQS. "FAIL" THEN $EXIT %X0126839B
$ LOGOUT
BAPS_GR job terminated at 27-MAY-1996 02:04:33.77
Accounting information:
Buffered I/O count: 218 Peak working set size: 2796
Direct I/O count: 335 Peak page file size: 12123
Page faults: 3803 Mounted volumes: 0
Charged CPU time: 0 00:00:03.19 Elapsed time: 0 00:00:18.94
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 215.1 | BROKE::PROTEAU | Jean-Claude Proteau | Mon May 27 1996 11:11 | 63 | |
Olympia,
It is difficult for me to know what versions of the various pieces of software
you decided to use. Note 214 talks about problems using DDD 6.0 and Rdb 6.0.
Here you seem to imply that you might have reverted to using the older ver-
sions of the software, but you did not actually say so. I can see from one
of the logs in note 215 that you are using VDD 2.4.
The errors in these log files are:
1. Invalid device type
%SET-W-NOTSET, error modifying HSC000$DUA5:
-CLI-E-IVDEVTYPE, invalid device type - specify a mailbox device
This has nothing to do with Rdb or DDD, and I assume it is an error you know
about and that can safely be ignored.
2. Transfer name already exists
Using BAPS (some sort of batch processing system) you run into a transfer that
fails:
%BAPS-I-TRANS, Initiate the transfer VDD from BAPS to ERF020
%RDO-F-DDALERR, DEC Data Distributor fatal error
-DDAL-E-TNSF_NAME_USED, transfer name already exists
...
End Status: SUCCESS
The log doesn't show all the commands executed. From the error message, you
must have tried to DEFINE TRANSFER using RDO. The error message indicates
you tried to create a transfer with a name already assigned to some other
transfer. Duplicate transfer names are not permitted.
3. Error executing extraction transfer BAPS_GR_TO_ERF_GR00
The transfer failed because the proxy account, ERF_XFR_GR00, does not exist on
node ATH853, or else does not permit access from your account. This error
appears in the copy process log file associated with the extraction transfer
BAPS_GR_TO_ERF_GR00:
Product version: VAX Data Distributor V2.4-0
...
02:04:30 %DDAL-I-CRETARGDB, creating target database ATH853"ERF_XFR_GR00"::
ERF$TRANSFER:XFR_DB.RDB
----- 27-MAY-1996 02:04:31.93 ----- Error ----------------------
%RDB-F-IO_ERROR, input or output error
-SYSTEM-F-INVLOGIN, login information invalid at remote node
...
$ @ATH853"ERF_XFR_GR00"::ERF$COMMAND:ERF_PRO_UPD_1.COM
%DCL-E-OPENIN, error opening ATH853"ERF_XFR_GR00"::ERF$COMMAND:ERF_PRO_UPD_
1.COM; as input
-RMS-E-ACC, ACP file access failed
-SYSTEM-F-INVLOGIN, login information invalid at remote node
If this worked in the past and has just recently stopped working, check with
your system manager to see how the RDBSERVER and FAL network objects are
defined in the DECnet database. I've seen problems where incoming and outgoing
ALIAS was not set up properly. If you are running on clusters that have
cluster ALIASes, both systems have to agree on whether or not the cluster alias
name is or is not to be used when identifying a user account on a remote system.
-Claude
| |||||