[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

1463.0. "Historian/Exporter problems" by WARDLE::REX (Life's not what I thought it was!) Fri Sep 06 1991 13:58

    
    I am having fun & games with the Exporter & Historian....
    
    Historian.....
    What I want to do is record data from a DECrouter 2000 (node4 olort1)
    and then export it to use the reports package.
    
    First I started recording on decrouter that worked fine until the
    system was rebooted. Then the recording of the "Initial attributes"
    partttion failed 11 times with an ETP error and suspended. I tried
    
    MCC> show node4 olort1 all ident 
    
    and it seemed fine so I restarted recording
    
    
    Exporter.....
    I fired off the background process and then started the exporting from
    the window interface. the MCC_EXPORT.RDB file was created, but the
    background process bombed out with 
    
    
    $       BTS == "$SYS$SYSTEM:MCC_EXPORTER_FM_BG.EXE"
    $       BTS "$_DISK1:[REX]MCC_EXPORT.RDB"
    %MCC-E-ALERT_TERMREQ, thread termination requested
    
    I now can not re-start the export process. Having checked the exporting
    for the decrouter it states there have been 0 polls. I am sure the
    exporter background job was running for a while before it crashed
    
    
    Can anyone assist as to what is happening ?
    
    :*(
    
    Rex
    
     
    %MCC-E-ALERT_TERMREQ, thread termination requested
T.RTitleUserPersonal
Name		DateLines
1463.1alert means ^CGOSTE::CALLANDERSat Sep 07 1991 10:335
    I will send your stuff along to Sam to look at, but as to alert
    term request...it is just what it sounds like. The thread that was
    running the request received the equivalent of a control C. That
    is strange.
1463.2TOOK::SHMUYLOVICHTue Sep 10 1991 10:2440
    
	From .0:

>    $       BTS == "$SYS$SYSTEM:MCC_EXPORTER_FM_BG.EXE"
>    $       BTS "$_DISK1:[REX]MCC_EXPORT.RDB"
>    %MCC-E-ALERT_TERMREQ, thread termination requested
    
	From .1:
>                                                   ... but as to alert
>    term request...it is just what it sounds like. The thread that was
>    running the request received the equivalent of a control C. That
>    is strange.

	The Exporter background process has a child subprocess which is
   responsible for writing in the RDB file. A special "control" thread
   in the background process is checking periodically if a child process
   is running. If a child process is dead this thread forces to terminate
   the background process with the above message.

>    I now can not re-start the export process.

	Why? Does it terminate? What message it gives?


     More questions:

      1. Is this your first attempt to use Exporter?
      2. Did you have at least one successfully running exporting
         request ( may be for another entity)?
      3. Is file MCC_EXPORT.RDB empty?
	 To check this you can use, for example, SQL:

		SQL> declare schema filename mcc_export.rdb;
		SQL> select * from mcc_node4;

     This additional information will help to define what is wrong 
     with your background process.

	Sam
1463.3Hmmmmm !WARDLE::REXLife's not what I thought it was!Tue Sep 10 1991 13:2925
    
    re .2
    
    Whenever the EXPORTER background process is initiated it fails with the
    thread termination error.
    
    1. Yes, this is my first attempt
    
    2. No exporting taking place anywhere else
    
    3. I get the following message using SQL
    
    SQL> declare schema filename mcc_export.rdb;
    %SQL-F-ERRATTDEC, Error attaching to declared schema mcc_export.rdb
    -RDB-E-BAD_DB_FORMAT, filename does not reference a database known to Rdb/VMS
    -RDMS-F-INV_ROOT, database file has illegal format
    
	any ideas ?
    
    
    ?:*(
    
    Rex
1463.4check SQL version numberTOOK::SHMUYLOVICHWed Sep 11 1991 18:1310
    
    What version of SQL is installed on your system?
    
    It must be not earlier that V3.1B.
    
    You can use analyze/image sys$library:sql*.exe command to look at 
    the SQl version installed on your system.
    
    Sam
1463.5SQL - V4WARDLE::REXLife's not what I thought it was!Wed Sep 18 1991 06:464
    
    The version is V4 for the SQL images