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

Conference azur::mcc

Title:DECmcc user notes file. Does not replace IPMT.
Notice:Use IPMT for problems. Newsletter location in note 6187
Moderator:TAEC::BEROUD
Created:Mon Aug 21 1989
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6497
Total number of notes:27359

1761.0. "export error" by F18::ROBERT () Mon Nov 04 1991 16:55

    Can someone give be an idea as to what is going wrong with my export
    function. I have been running decmcc since 18 oct until 30 oct.
    I then shut all the exporting jobs and the queues, I then just now 
    tried to restart the export function to see how this particular
    function slows down the network.
    
    This is the error that I get.
    
    I select node in an entity called see003
    begin time 3:50
    end time 4-may-1992
    expt per 30 min
    expt target exp:usan.rdb
    seq name n_stl_se3
    
    I get the following
    The requested operation cannot be completed
    
    mcc routine error %export-f-invdbctx, invalid db context
    entity existence info  entity existence cannot be determined
    
    
    I deleted the old .rdb files and deleted the batch jobs, and restarted
    new ones with the correct name.
    
    Any ideas? I had it running from the 18-30 of oct 1991\
    
    Thanks Dave
    
T.RTitleUserPersonal
Name
DateLines
1761.1begin time in the future?CLARID::HOFSTEETake a RISC, buy a VAXTue Nov 05 1991 03:4211
In one of my previous notes, I described the same problem.(Don't remember
the number). After some time we figured out that in our case, the problem 
came from the fact that I specified the begin time as NOW. In general, the
begin time should be in the future. When you specify NOW, or the system
time when you type in the command, the moment that your job is started in
the queue, this time will be past and you get the message you described.

Hope this helps

Timo
1761.2F18::ROBERTTue Nov 05 1991 09:4712
    Timo,
    	I specified the time to start as the future. i.e. 5 minutes ahead
    of present wall clock time. I will give this a shot.
    
    I just tried it again and gave it a time plus a date - I gave it a time
    of 10 minutes ahead of wall clock time. It worked fine. So for some
    reason the export functions that I set up yesterday, I did not give it
    enough time to get going, I think?
    
    Thanks for the help.
    Dave
    
1761.3F18::ROBERTTue Nov 05 1991 12:2611
    The real reason why this happened, I was changing my mcc_export within
    datatrieve, this is what I typed in 
    DTR>define database mcc_export exp:usa.rdb ;
    
    I should have typed in define database mcc_export on exp:usa.rdb ;
    
    I did not have "on" in this line. This is the problem that this will
    cause by leaving out the "on"
    
    Dave