[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

1080.0. "Can't delete export!!!" by ZPOVC::RAMARAJ () Fri May 31 1991 13:00

I've setup exporting for a node4 entity.  

Doing a 
    
mcc> show export node4 mndv01 export target=mccreportsdir:mcc_export.rdb
    
displays all information abt the exporting.  It show the state as ACTIVE,
but the last successful poll was 5 hours ago, although the export period
is set to 15mins(00:15:00).  The node4 entity is still up and running.

So I tried to delete it and when I did  
    
mcc> delete export node4 mndv01 export target=mccreportsdir:mcc_export.rdb
    
it gives an error NOENTITY, no corresponding entity instance exists.

Doing anything other than a show, gives the same error.

Why does the show, says its there, but modify, delete, suspend cannot see
it?

How else can I delete the export for that entity?

Raj
SWS Singapore
T.RTitleUserPersonal
Name
DateLines
1080.1TOOK::SHMUYLOVICHFri May 31 1991 20:5331
re :.0

>Doing a 
>    
>mcc> show export node4 mndv01 export target=mccreportsdir:mcc_export.rdb
>    
>displays all information abt the exporting.  It show the state as ACTIVE,
>but the last successful poll was 5 hours ago, although the export period
>is set to 15mins(00:15:00).  The node4 entity is still up and running.

	What about the "last unsuccessful poll" ? If it's in the past it looks
to me like a background process for this target is dead. Could you, please, 
check this.
Also are there exportings for other entities? If yes, are they running? I mean
does the "last successful poll" or "last unsuccessful poll" match to the
export period? If not the background process for this target is definitely dead.

>Why does the show, says its there, but modify, delete, suspend cannot see
>it?

	Did you deregister and register again this node4 while exporting 
request was active?

	Try to use another identifier (address or full name) in the delete 
exporting directive.


 Sam Shmuylovich
 Historian/Exporter team
    
1080.2Export Background is running?ZPOVC::RAMARAJSat Jun 01 1991 00:4218
    The background process for the exporting is still running.
    
    The node4 was node not renamed or deregistered during the period.
    
    The only thing that happened was as stated in 1079.0, the background
    process exited suddenly, but I restarted it again, and it is running
    again.
    
    The background process is still running and I still cannot delete,
    modify, or suspend it.
    
    This is at a customer site, so I try the deleting with the address on
    Monday.
    
    Any other hints in the mean time?
    
    Raj
    SWS Singapore
1080.3try to reregisterTOOK::SHMUYLOVICHMon Jun 03 1991 21:225
    
    Please, try to deregister abd register again. I think that exporting
    will go away.
    
    Sam
1080.4Deregister/register works, butZPOVC::RAMARAJTue Jun 04 1991 12:2721
    I did a deregister and register of the node4.  I still cannot delete
    the export. but unlike previous times, I was able to do a 
    export node4 mndv01..... again.
    
    Before the deregister and register, the export node4 mndv01.....
    command would fail, saying that exporting is already present.
    
    Sometimes, the exporting stops after 1 poll.  The status shows it as
    still active, but it does not poll anymore.  There is no last failed
    poll time either.  
    
    I cannot delete, modify or suspend the export.  Had to deregister and
    register again.
    
    All this while, the export background process is still running.
    
    It is occurring too many times, on most systems I have tried so far,
    whether the export period is 1 min, 15 min or 1 hour.
    
    Raj
    SWS Singapore
1080.5one more expirementTOOK::SHMUYLOVICHWed Jun 05 1991 13:1147

	Raj,
	You entered several notes and some of them describe the same situation.
   Let's summarize what problems you have now with Exporter FM.

     1. > I cannot delete, modify or suspend the export.  Had to deregister and
        > register again.
    
     2. > Sometimes, the exporting stops after 1 poll.  The status shows it as
        > still active, but it does not poll anymore.  There is no last failed
        > poll time either.  

	
     1. I know two situations which give this problem:

	 a. The background process stops during execution of the Export command
	    in the foreground (MCC). Usually it happens when system quotas are
	    not enough. 

	 b. The bug you found in 1091 (thanks again). Modify Exporting with 
	    export target entered using lower case. Please see 1091.1 for a 
	    temporary work around.

     2. If exporting has "active" state and no polling activity can be 
        detected ( I mean "time of last successful poll" and "time of last
	unsuccessful poll") it means that background process is dead.

     Could you please do a "clean" experiment?

	1. Stop background process.
	2. Start background process with NEW database name.
	3. Start exporting into NEW database ( please do it for node4 and
	   export period > 3 min)
	4. When you see that there is no polling activity please do:

		- SHOW EXPORTING;
		- SHOW entity_being_exported ALL ATTRIBUTES;
		- SHOW entity_being_exported ALL STATISTICS,-
		  FOR DURATION = (export_period - 30 sec);
		- type log background log file;
		- please send all this information to me (TOOK::SHMUYLOVICH)
		  or put it in notes.

	Thanks, Sam

    
1080.6Maybe case sensitivity issue?NSSG::R_SPENCENets don't fail me now...Wed Jun 05 1991 13:376
    Also, keep in mind that much of the export stuff is CASE Sensitive
    so you must specify things in the exact same case each time you refer
    to them. So, to delete the export job, specify the entity in the same
    case as you did when you did the original EXPORT directive.
    
    s/rob
1080.7Export and case sensitivityTOOK::SHMUYLOVICHThu Jun 06 1991 12:3447
	RE: .6

>    Also, keep in mind that much of the export stuff is CASE Sensitive
>    so you must specify things in the exact same case each time you refer
>    to them. So, to delete the export job, specify the entity in the same
>    case as you did when you did the original EXPORT directive.
 

   Sorry Rob, but I disagree with you. The only case sensitive problem I know 
is Modify Exporting bug (see note #1091 ) with export target argument. All other
exporting commands accept this argument in both cases.

   How to specify the entity in the Export commands? It does NOT depend on how 
it was done in the original Export directive. It depends on what Directory
directive returns (in other words, it depends on how this entity has been 
registered).

   Here is example for node4:

MCC> dir node4 rudone

Node4 rudone
AT  6-JUN-1991 09:19:24

Directory successful.
                        Registered Name = MCC1_NS:.rudone
                                Address = 4.773
                                   Name = RUDONE

	export node4 rudone
	export node4 RUDONE
	export node4 4.773
	export node4 .rudone
	export node4 .RUDONE

 All these commands work. Now what happens after exporting request is created.
 I use as example Show Export command:

	show export node4 rudone  -------> works
	show export node4 RUDONE  -------> works
	show export node4 4.773   -------> works	
	show export node4 .rudone -------> works
	show export node4 .RUDONE-------> does NOT work (due to the case 
					  sensitivity in the MIR)

	Sam
    
1080.8NSSG::R_SPENCENets don't fail me now...Thu Jun 06 1991 13:013
    Oops, sorry Sam. I agree, it does matter relating to how it was
    registered, but that also affects the original EXPORT directive.
    s/rob