|
Hi Timo,
I'll answer your questions from the bottom to the top ( from the easiest one
to the most difficult).
>(PS. MCC V1.1 RDB 3.1-1, anything else?)
As it's stated in the release notes Exporter FM requires RDB not earlier that
VAX RDB/VMS V3.1B.
>7. A 'show export' through the iconic map, gives a lot of info, like:
> state active, , last successful poll=NONE etc.
>
In export command you did not specify the "export period" argument.
Its default value is 1 hour. So the first poll will be in an hour.
> through the command line interface,
>
> MCC>show export node4 rtwo
>
> gives: Repositories do not exist.
You forgot to specify "export target" argument:
MCC>show export node4 rtwo export target = sys$login:rtwo_1.rdb
The default value for this argument is MCC_EXPORT.RDB. You have never
started exporter request for this target and therefore there aren't repositories
corresponding to the MCC_EXPORT.RDB file.
> Than , the system comes back with:
>
> mcc routine error : %export-f-invdbctx, invalid DB context
> enitity existence info: entity existence cannot be determined.
This is most difficult question. The only thing I can assume is
that Exporter's files are corrupted. Did you abort exporting directive
during its execution?
Would you ,please, before fixing this situation send me mail
(TOOK::SHMUYLOVICH) or post here the result of the following operation:
DIR MCC_COMMON:*.MCC_EXP*/DAT/SIZ
How to fix this:
1. If you do not have exporting requests you want to save (for all
export targets) please do the following:
a. stop background process in the queue( all of them if
you have several);
b. do DELETE MCC_COMMON:*.MCC_EXP*;*
c. start background process in the queue;
d. invoke MCC and set up exporting.
2. If you want to save exporting requests:
a. stop background process in the queue( all of them if
you have several);
b. do DELETE MCC_COMMON:*.MCC_EXP*Q;*
c. start background process in the queue;
d. invoke MCC and set up exporting.
The first method is preferred.
Sam Shmuylovich
|
|
> As it's stated in the release notes Exporter FM requires RDB not earlier that
> VAX RDB/VMS V3.1B.
Checked again, and I am running V3.1B-0. So this should be ok.
> This is most difficult question. The only thing I can assume is
> that Exporter's files are corrupted. Did you abort exporting directive
> during its execution?
No.
> Would you ,please, before fixing this situation send me mail
> (TOOK::SHMUYLOVICH) or post here the result of the following operation:
> DIR MCC_COMMON:*.MCC_EXP*/DAT/SIZ
$ DIR MCC_COMMON:*.MCC_EXP*/DAT/SIZ
Directory SYS$COMMON:[MCC]
MCC_00.MCC_EXP_ATTR011_PMS;1
81 24-APR-1991 15:17:41.08
MCC_00.MCC_EXP_INST011_PMS;1
66 24-APR-1991 15:17:39.53
MCC_F87C000400AA000001CA58504AA78140.MCC_EXPO_Q11_Q;1
5 12-AUG-1991 06:28:43.93
MCC_F87C000400AA000001CA58504AA78140.MCC_EXP_ATTR011_P;1
81 12-AUG-1991 06:29:04.00
MCC_F87C000400AA000001CA58504AA78140.MCC_EXP_ATTR011_PH;1
81 12-AUG-1991 06:29:11.10
MCC_F87C000400AA000001CA58504AA78140.MCC_EXP_INST011_P;1
66 12-AUG-1991 06:29:01.89
MCC_F87C000400AA000001CA58504AA78140.MCC_EXP_INST011_PH;1
66 12-AUG-1991 06:29:05.92
MCC_F87C000400AA000001CA5856A6D3A380.MCC_EXPO_Q11_Q;1
5 12-AUG-1991 07:14:17.58
MCC_F87C000400AA000001CA5856A6D3A380.MCC_EXP_ATTR011_P;1
81 12-AUG-1991 07:14:37.00
MCC_F87C000400AA000001CA5856A6D3A380.MCC_EXP_ATTR011_PH;1
81 12-AUG-1991 07:14:44.34
MCC_F87C000400AA000001CA5856A6D3A380.MCC_EXP_INST011_P;1
66 12-AUG-1991 07:14:34.33
MCC_F87C000400AA000001CA5856A6D3A380.MCC_EXP_INST011_PH;1
66 12-AUG-1991 07:14:38.58
MCC_F87C000400AA000001CA5970CF268DA0.MCC_EXPO_Q11_Q;1
5 13-AUG-1991 17:02:29.11
MCC_F87C000400AA000001CA5970CF268DA0.MCC_EXP_ATTR011_P;1
81 13-AUG-1991 16:54:21.92
MCC_F87C000400AA000001CA5970CF268DA0.MCC_EXP_ATTR011_PH;1
81 13-AUG-1991 16:54:26.28
MCC_F87C000400AA000001CA5970CF268DA0.MCC_EXP_INST011_P;1
66 13-AUG-1991 16:54:19.52
MCC_F87C000400AA000001CA5970CF268DA0.MCC_EXP_INST011_PH;1
66 13-AUG-1991 16:54:23.42
MCC_F87C000400AA000001CA5979B558EFE0.MCC_EXP_ATTR011_P;1
81 13-AUG-1991 17:58:04.01
MCC_F87C000400AA000001CA5979B558EFE0.MCC_EXP_ATTR011_PH;1
81 13-AUG-1991 17:58:08.44
MCC_F87C000400AA000001CA5979B558EFE0.MCC_EXP_INST011_P;1
66 13-AUG-1991 17:58:01.72
MCC_F87C000400AA000001CA5979B558EFE0.MCC_EXP_INST011_PH;1
66 13-AUG-1991 17:58:05.82
MCC_F87C000400AA000001CA597A2FFBE540.MCC_EXPO_Q11_Q;1
5 13-AUG-1991 18:01:15.87
MCC_F87C000400AA000001CA597A2FFBE540.MCC_EXP_ATTR011_P;1
81 13-AUG-1991 18:01:29.13
MCC_F87C000400AA000001CA597A2FFBE540.MCC_EXP_ATTR011_PH;1
81 13-AUG-1991 18:01:33.80
MCC_F87C000400AA000001CA597A2FFBE540.MCC_EXP_INST011_P;1
66 13-AUG-1991 18:01:26.72
MCC_F87C000400AA000001CA597A2FFBE540.MCC_EXP_INST011_PH;1
66 13-AUG-1991 18:01:31.29
Total of 26 files, 1637 blocks.
$
> How to fix this:
> 1. If you do not have exporting requests you want to save (for all
> export targets) please do the following:
> a. stop background process in the queue( all of them if
> you have several);
$ sh que mcc_export
Batch queue MCC_EXPORT, on SSPVBI::
Jobname Username Entry Status
------- -------- ----- ------
MCC_EXPORTER_BACKGROUND
SYSTEM 57 Executing
$ del/entry=57 mcc_export
$ sh que mcc_export
Batch queue MCC_EXPORT, on SSPVBI::
> b. do DELETE MCC_COMMON:*.MCC_EXP*;*
$ DELETE MCC_COMMON:*.MCC_EXP*;*
c. start background process in the queue;
$ subm/que=mcc_export/restart/param=sys$login:rtwo_5.rdb -
_$ sys$manager:mcc_exporter_background.com
Job MCC_EXPORTER_BACKGROUND (queue MCC_EXPORT, entry 59) started on MCC_EXPORT
d. invoke MCC and set up exporting.
Through iconic map.
-open domain, select node4 icon, select EXport, fill in window with:
begin time : now
end time : 16-aug-1991 9:00:00
export target: sys$login:rtwo_5.rdb
sequence name :rtwo_5
sequence nr :5
Start operation.
Same result: after about 2 minutes, window comes back with :
mcc routine error : %export-f-invdbctx, invalid DB context
Entity existence info : Entity Existence Cannot be determined.
$ DIR MCC_COMMON:*.MCC_EXP*/DAT/SIZ
Directory SYS$COMMON:[MCC]
MCC_00.MCC_EXP_INST011_PMS;1
66 14-AUG-1991 18:00:07.09
MCC_F87C000400AA000001CA5A4355C28300.MCC_EXPO_Q11_Q;1
5 14-AUG-1991 18:00:59.02
MCC_F87C000400AA000001CA5A4355C28300.MCC_EXP_ATTR011_P;1
81 14-AUG-1991 18:01:23.57
MCC_F87C000400AA000001CA5A4355C28300.MCC_EXP_ATTR011_PH;1
81 14-AUG-1991 18:01:27.52
MCC_F87C000400AA000001CA5A4355C28300.MCC_EXP_INST011_P;1
66 14-AUG-1991 18:01:20.90
MCC_F87C000400AA000001CA5A4355C28300.MCC_EXP_INST011_PH;1
66 14-AUG-1991 18:01:25.20
Any other ideas?
Thanks
Timo
|
|
I've tried some more things and the following seems to be the problem:
When I setup the exporting through the iconic map interface and I specify
a specific begin and end time (for example 20-aug-1991 9:00 and
22-aug-1991 9:00) I get the message 'export started' and everything seems
to work fine. Also when I repeat the same through FCL. However, when I
change the BEGIN TIME in NOW, the iconic map interface accepts it as valid
input but comes back with the message described in .0 (INVALID DB context).
When I try to repeat the same through the FCL I get an 'invalid qualifier'
message, when defining 'BEGIN TIME = NOW'.
Here is some more log output:
$ DIR MCC_COMMON:*.MCC_EXP*/DAT/OWNER/PROT
Directory SYS$COMMON:[MCC]
MCC_00.MCC_EXP_INST011_PMS;1
14-AUG-1991 18:00:07.09 [SYSTEM] (RWED,RWED,RE,)
MCC_F87C000400AA000001CA5A4355C28300.MCC_EXPO_Q11_Q;1
14-AUG-1991 18:00:59.02 [SYSTEM] (RWED,RWED,RWED,)
MCC_F87C000400AA000001CA5A4355C28300.MCC_EXP_ATTR011_P;1
14-AUG-1991 18:01:23.57 [SYSTEM] (RWED,RWED,RE,)
MCC_F87C000400AA000001CA5A4355C28300.MCC_EXP_ATTR011_PH;1
14-AUG-1991 18:01:27.52 [SYSTEM] (RWED,RWED,RE,)
MCC_F87C000400AA000001CA5A4355C28300.MCC_EXP_INST011_P;1
14-AUG-1991 18:01:20.90 [SYSTEM] (RWED,RWED,RE,)
MCC_F87C000400AA000001CA5A4355C28300.MCC_EXP_INST011_PH;1
14-AUG-1991 18:01:25.20 [SYSTEM] (RWED,RWED,RE,)
Total of 6 files.
$ sh que mcc_export
Batch queue MCC_EXPORT, on SSPVBI::
$ pu sys$manager:*.log
$ DELETE MCC_COMMON:*.MCC_EXP*;*
%DELETE-W-FILNOTDEL, error deleting SYS$COMMON:[MCC]MCC_00.MCC_EXP_INST011_PMS;1
-RMS-E-FLK, file currently locked by another user
%DELETE-W-FILNOTDEL, error deleting SYS$COMMON:[MCC]MCC_F87C000400AA000001CA5A4355C28300.MCC_EXP_ATTR011_P;1
-RMS-E-FLK, file currently locked by another user
%DELETE-W-FILNOTDEL, error deleting SYS$COMMON:[MCC]MCC_F87C000400AA000001CA5A4355C28300.MCC_EXP_ATTR011_PH;1
-RMS-E-FLK, file currently locked by another user
%DELETE-W-FILNOTDEL, error deleting SYS$COMMON:[MCC]MCC_F87C000400AA000001CA5A4355C28300.MCC_EXP_INST011_P;1
-RMS-E-FLK, file currently locked by another user
%DELETE-W-FILNOTDEL, error deleting SYS$COMMON:[MCC]MCC_F87C000400AA000001CA5A4355C28300.MCC_EXP_INST011_PH;1
-RMS-E-FLK, file currently locked by another user
***********Who is locking these files?
$ sh que mcc_export/ful
Batch queue MCC_EXPORT, on SSPVBI::
/BASE_PRIORITY=4 /JOB_LIMIT=100 /OWNER=[SYSTEM] /PROTECTION=(S:RWED,O:D,
G:RW,W)
$ sh qu mcc_history
%DCL-W-ABKEYW, ambiguous qualifier or keyword - supply more characters
\QU\
$
[K
$ sh que mcc_history
Batch queue MCC_HISTORY, on SSPVBI::
Jobname Username Entry Status
------- -------- ----- ------
MCC_HISTORIAN_BACKGROUND
SYSTEM 49 Executing
$ del/entry=49 mcc_history
$
[K
$ del/entry=49 mcc_history
[K
$ sh que mcc_history
Batch queue MCC_HISTORY, on SSPVBI::
Jobname Username Entry Status
------- -------- ----- ------
MCC_HISTORIAN_BACKGROUND
SYSTEM 49 Aborting
$
[K
$ sh que mcc_history
Batch queue MCC_HISTORY, on SSPVBI::
$
$ DELETE MCC_COMMON:*.MCC_EXP*;*
%DELETE-W-FILNOTDEL, error deleting SYS$COMMON:[MCC]MCC_00.MCC_EXP_INST011_PMS;1
-RMS-E-FLK, file currently locked by another user
%DELETE-W-FILNOTDEL, error deleting SYS$COMMON:[MCC]MCC_F87C000400AA000001CA5A4355C28300.MCC_EXP_ATTR011_P;1
-RMS-E-FLK, file currently locked by another user
%DELETE-W-FILNOTDEL, error deleting SYS$COMMON:[MCC]MCC_F87C000400AA000001CA5A4355C28300.MCC_EXP_ATTR011_PH;1
-RMS-E-FLK, file currently locked by another user
%DELETE-W-FILNOTDEL, error deleting SYS$COMMON:[MCC]MCC_F87C000400AA000001CA5A4355C28300.MCC_EXP_INST011_P;1
-RMS-E-FLK, file currently locked by another user
%DELETE-W-FILNOTDEL, error deleting SYS$COMMON:[MCC]MCC_F87C000400AA000001CA5A4355C28300.MCC_EXP_INST011_PH;1
-RMS-E-FLK, file currently locked by another user
********who is locking these? No jobs in MCC_EXPORT or MCC_HISTORY
$ subm/que=mcc_export/restart/param=sys$login:rtwo_10.rdb -
_$ sys$manager:mcc_exporter_background
Job MCC_EXPORTER_BACKGROUND (queue MCC_EXPORT, entry 112) started on MCC_EXPORT
$ sh que mcc_export
Batch queue MCC_EXPORT, on SSPVBI::
Jobname Username Entry Status
------- -------- ----- ------
MCC_EXPORTER_BACKGROUND
SYSTEM 112 Executing
$ manag/enter
DECmcc (V1.1.0)
)0[4l
=
>
)0[4l
=
>
MCC> EXPORT NODE4 RTWO BEGIN TIME = NOW, END TIME = TOMORROW,-
_MCC> EXPORT PERIOD= 30:00, EXPORT TARGET = SYS$LOGIN:RTWO_10.RDB
%MCC-E-BIN_REL_TIM_ERR, error in Binary Relative Time value
_MCC> EXPORT NODE4 RTWO BEGIN TIME = NOW, END TIME = TOMORROW,-
_MCC> EXPORT TARGET = SYS$LOGIN:RTWO_10.RDB
%MCC-E-INV_IN_Q, invalid qualifier
$ SH TIME
20-AUG-1991 14:28:54
$ MANAG/ENTER
DECmcc (V1.1.0)
MCC> EXPORT NODE4 RTWO END TIME = 23:00, EXPORT PERIOD = 00:00:05, -
_MCC> EXPORT TARGET = SYS$LOGIN:RTWO_10.RDB
Node4 51.333
AT 20-AUG-1991 14:29:43
Exporting started
MCC> DELETE EXPORTING NODE4 RTWO EXPORT TARGET = SYS$LOGIN:RTWO_10.RDB
Node4 RTWO
AT 20-AUG-1991 14:36:44
Exporting stopped and deleted
MCC> EXI
>
>
$ SH QUE MCC_EXPORT
Batch queue MCC_EXPORT, on SSPVBI::
Jobname Username Entry Status
------- -------- ----- ------
MCC_EXPORTER_BACKGROUND
SYSTEM 112 Executing
$ MANAG/ENTER
DECmcc (V1.1.0)
MCC> EXPORT NODE4 RTWO BEGIN TIME = NOW , END TIME = 21-AUG-1991 9:00,-
_MCC> EXPORT PERIOD = 00:30:00, EXPORT TARGET = SYS$LOGIN:RTWO_10.RDB
%MCC-E-INV_IN_Q, invalid qualifier
MCC> EXI
>
>
$ LO
SYSTEM logged out at 20-AUG-1991 14:46:10.10
When I repeat the last command through the iconic interface I get the
INVDBCNTXT error.
Does this give a clue?
Timo
|
|
Hi Timo,
>I've tried some more things and the following seems to be the problem:
>
>When I setup the exporting through the iconic map interface and I specify
>a specific begin and end time (for example 20-aug-1991 9:00 and
>22-aug-1991 9:00) I get the message 'export started' and everything seems
>to work fine. Also when I repeat the same through FCL. However, when I
>change the BEGIN TIME in NOW, the iconic map interface accepts it as valid
>input but comes back with the message described in .0 (INVALID DB context).
It's exactly where the problem is! Sorry it took long time to find it.
The "begin time" and "end time" arguments in the export directive
have BIN_ABS_TIME data type. When you specify "now" as a value for
begin time FCL and Iconic Map write a value of the current time in
this argument. Later Exporter FM determines if this exporting request
is for past or future data. Because the value of the "begin time"
argument is a current time of the request Exporter initiates a Past
time export request with is broken due to the bug in the Exporter FM
( note 1182.*) and as a result you have useless error "invalid data
base context". Until past time Export is fixed, please, do not use
"now" as an argument to the "begin time" argument. The default value
for "begin time" argument provides exporting request starting immediately,
e.g. "now".
>***********Who is locking these files?
Files *.MCC_EXP* are locked by past time child subprocess which
hangs due to the bug in the Exporter FM when past time request is
specified.
>
MCC> EXPORT NODE4 RTWO BEGIN TIME = NOW, END TIME = TOMORROW,-
>
_MCC> EXPORT PERIOD= 30:00, EXPORT TARGET = SYS$LOGIN:RTWO_10.RDB
>
%MCC-E-BIN_REL_TIM_ERR, error in Binary Relative Time value
This error is returned by FCL due to the specified value of the
"export period" argument. The valid format for the 30 hours is
1-06:00:00.
>
_MCC> EXPORT NODE4 RTWO BEGIN TIME = NOW, END TIME = TOMORROW,-
>
_MCC> EXPORT TARGET = SYS$LOGIN:RTWO_10.RDB
>
%MCC-E-INV_IN_Q, invalid qualifier
As it was described in the beginning Export FM tries to create
a past time exporting request which requires IN DOMAIN qualifier.
In V1.2 it will return exception "required qualifier is missing"
Sam
|