| Title: | DECtrace V2.0 and All-in-1 Perf Rpts conf. |
| Notice: | Kits+Doc, 2 | Patches, 3 |
| Moderator: | OMYGOD::LAVASH |
| Created: | Mon Apr 26 1993 |
| Last Modified: | Mon Jun 02 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 467 |
| Total number of notes: | 2058 |
Customer has a collection that he is trying to cancel, but when he
cancels it, he gets a message saying that it doesn't exist, however
when he tries to schedule the collection, it says he can't because
there is already one that exists....
History...
Collection was started several days(300+) with a /duration=300, or so
days, and somewhere inbetween then and now, they moved the disk that
the collection was putting its output.
Customer has defined a new collection that is working, but how can
he get rid of this collection? SQL? If so, what items should be
cleaned up?
Thank You
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 439.1 | A few things to check | OOTOOL::CRAIG | Wed Feb 12 1997 11:30 | 54 | |
Hi,
There are two things that come to mind that
you might check to determine the cause of the problem:
1) EPC$ADMIN_DB AND EPC$HISTORY_DB logicals not pointing
to the right place.
SHOW COLLECTION/ FORMAT = FULL
If you don't see both, then the admin database on
your node is not pointing to the correct place.
You will need to change the translation for
EPC$ROOT on your node.
Another way to check for this problem is to check the
logicals on both nodes to see if they have the same
translation.
SHOW LOGICAL EPC$ROOT
If they don't, take down the Registrar and
edit the file on the node.
2) Check the cluster where the old collection was running
before it was moved.
Attach to EPC$ADMIN_DB
select * from EPC$test_active;
You'll probably see the collection as active on some other node
in your cluster.
The EPC$REGISTRAR process on that node has probably crashed or been
brought down since the collection was activated.
Re-start the registrar by @sys$startup:epc$startup.com on those
nodes that show up in the epc$test_active table.
The registrars at startup will perform the cleanup. And delete the
collection record from epc$test_main. (in your case if the 300 days
aren't up you can cancel the old collection and remove it if necessary).
If none of these ideas help let me know. If the customer is running an
old version of Trace, they may be running into a bug, so let me know what
version they are running.
Thanks,
Sheri
| |||||
| 439.2 | still active on some node in the cluster | OOTOOL::LAVASH | Same as it ever was... | Tue Feb 18 1997 08:42 | 16 |
> You'll probably see the collection as active on some other node > in your cluster. > The EPC$REGISTRAR process on that node has probably crashed or been > brought down since the collection was activated. > Re-start the registrar by @sys$startup:epc$startup.com on those > nodes that show up in the epc$test_active table. > The registrars at startup will perform the cleanup. And delete the > collection record from epc$test_main. (in your case if the 300 days > aren't up you can cancel the old collection and remove it if necessary). This is the answer. George | |||||