Conference rocks::dec_edi

    The equivalent is RESET | REPROCESS in the Cockpit, the document
    returns to available status. You shouldn't use SQL to fix this!
    
    Pete.

Hi Pete,

    I'm sorry but a RESET | REPROCESS doesn't return the document's status to
    Available. The customer already did this before he phoned me.....

    Any more ideas ?

Martin

    Martin,
    
    Hi, I tried this and it worked for me. Note that you may need to do an
    update after resetting as sometimes the display doesn't get updated.
    Can you get more info from the customer, e.g.:
    
     - What actually happened. Did the Cockpit say it had been reset
       correctly or did it give an error.
    
     - Is there anything in the server error log?
    
     - Was only one document being reset or many at one time?
    
     - Can other documents be successfully reset?
    
    		Chris

Hi Chris,

>>    Hi, I tried this and it worked for me. Note that you may need to do an
>>    update after resetting as sometimes the display doesn't get updated.
>>    Can you get more info from the customer, e.g.:

Refresh done but no change
    
>>     - What actually happened. Did the Cockpit say it had been reset
>>       correctly or did it give an error.

Trade fetch failed. Reset reprocess result in an GUI error.... please refer...
    
>>     - Is there anything in the server error log?
NO
    
>>     - Was only one document being reset or many at one time?

Just two documents
    
>>     - Can other documents be successfully reset?
Yes, I thinks so, otherwise the customer would told me.

Martin,

we have tested this recently and it is supposed to work.

We are working on a problem whereby the documents appear to be reset
to avalable in the cockpit but you can't fetch them until a restart
is done. Is this what your customer is seeing?

cheers

Mark

Hi Mark,

Do you mean a restart of the cockpit or DEC/EDI ?

Martin

Of DEC/EDI.

We're working on a patch.

Note - you have this problem if they *lookK as though you can fetch them
but you can't.

Mark

Hi Mark,

I think this is a different problem.

There's nothing to fetch a this moment because the document still have the 
status "Processing".

Reset -> Reprocess -> results in an error 
Stop/Start DEC/EDI doesn't fix the problem either.

So I think we've to delete the document from within Oracle .....

Martin

    Martin,
    
    If the documents are still at PROCESSING after DEC/EDI has been
    shutdown and restarted, then something is definitly strange about those
    documents as the recovery procedure on startup should reset them to
    AVAILABLE.
    
    If there's nothing in the error log file after startup or when the
    Cockpit fails to reset them, then I'm not sure what to suggest.
    
    If the customer can definitely reset other PROCESSING documents then it
    points to these particular ones.
    
    Could anything else be locking up these documents in the database? You
    could try shutting down DEC/EDI full and then the Oracle database (I
    assume you can shut it down) and then restart them both, this may free
    up anything that could be locking them.
    
    One other thought, ObjectBroker is called when a document is reset.
    Make sure all Objectbroker GUI servers are shutdown, and shutdown and
    restart the ObjectBroker Agent as well to make sure.
    
    If you don't mind Cancelling the document you could see if that works.
    
    	Chris

Hi Chris,

I'll ask the customer to do this, but I'm almost sure that last friday even the
whole system was rebooted.

But anyway I'll keep you informed.

Regards,

Martin

Hi Chris,

The customer just phoned me. He tried everything you and others suggested but 
the document still has the status PROCESSING.

What is the SQL statement to give it a more final status ?

Martin