| It looks like you had the Exporter background process running at some point
in the past, because it has created the queue. It also appears that you
executed some EXPORT commands, including the one you mentioned, without
starting the background process first. Each "future time" EXPORT command
will cause at least one entry to be inserted into the background processing
queue. The background process removes the queue entries. If the
background process is not started, entries will pile up in the queue and
the queue will eventually become full.
If you start the Exporter background process, it will clear the queue and
start all currently enabled "exportings". You'll have to check the last
command you entered to find out if is enabled (SHOW EXPORT command).
> what do I do to reset or increase it [the queue]?
The queue size is fixed at 100 entries and is not "user-settable". This
size queue should be adequate. The background process has to be running to
process "future time" EXPORT commands, so the queue has to be just large
enough to prevent a "queue full" error while the background process is
executing. If you do have the background process running and you're
getting this error, then we'll have to look at increasing the queue size.
Roy
(p.s. You don't need the "IN DOMAIN" qualifier when you specify a "future
time" EXPORT command, although it does no harm to have it there (as you've
probably noticed). However, a "past time" EXPORT command does require the
"IN DOMAIN" qualifier.)
|
| It appears that the exporter background parameter of the file name
must include a device as well as file name. I got 'file protection'
errors in the bacgrounds log file if I submit the file name without
the device specifier. I specified MCC_EXPORT.RBD which failed and
resubmitted the file as SYS$LOGIN:MCC_EXPORT.RDB which succeeded.
My default device at the time was SYS$LOGIN. Why did it fail? Is
the fileopen doing something funky with device names? Also, it would
be really nice to know the name of the file which it failed to open,
because the background process opens several files.
It also looks like the exported increases the size of the RDB file
by about 50 block for each poll of circuit counters. Are there more
metrics available for sizing the extent of disk consumption by
EXPORT and Historian (if appears to be 5-6 blocks per poll). Also
would be nice to know how many requests I can have outstanding
per director. Same for Alarms, etc.
/Claudia
|