Conference orarep::nomahs::rdb_60

5055.0. "-RDMS-F-ERROPENOUT, sys$login:'disk'.tmp" by chsr38.ch.oracle.com::ROHR (The Packers did it!) Thu Feb 20 1997 12:05

    I can't find anything similar. VAx 6.1 Rdb 6.0-15.
     
    A
    
    $ rmu/unload/virtual/rms=file=unload_dir1:cptyhist.rrd -                 
             /fields=( ABOUT 40 FIELDS LISTED HERE ) -                            
             convert_db cptyhist_upd unload_dir1:cptyhist.unl                     
          
    gives:
    
     %RDB-F-SYS_REQUEST, error from system services request                   
         -COSI-E-OPENERR, cannot open file                                        
         -RDMS-F-ERROPENOUT, error opening
    M0230_DISK:[MGR_M0230]NOL288$DK.TMP;   as output                                                                
         -SYSTEM-W-NOSUCHFILE, no such file                                       
         %RMU-I-DATRECUNL, 0 data records unloaded  
    
    The system has all disks that are called NOL288$DKAxxx. So the disk
    name is truncated to 9 in the tmp file name. If that's a problem, I
    don't know.
    
    NOL288_WQE> sh log m0230_disk /full                                      
            "M0230_DISK" [exec] = "NOL288$DKA100:[M0230_DISK.]"                   
         [concealed,terminal] (LNM$SYSTEM_TABLE)  
    
    Sortwork1 and sortwork1 are  
    
                                                                               
           "SORTWORK0" = "NOL288$DKA100:[SORTWORK]"                               
           "SORTWORK1" = "NOL288$DKA400:[SORTWORK]"                               
    . 
    
>>>>When do we create tmp files whose names are taken from a disk? 
    
    I found a Stars article (well a reference to it in an old list) that 
    talked about such a tmp filename (with system disk in it) but I can't 
    locate the article anymore.
    
    I also thought I read about a problem with multiversion and setver in
    syslogin causing problems with sys$scratch, but as say define the
    sortwork logicals that doesn't fit either.
    
    Anyone seen this?
    Thanks,
    Regina
    
    
     
    
     

interesting.  The two places that come to mind
where .TMP files are created would be for temp
work files and sort work files.  RDMS$BIND_WORK_FILE
would be the logical that would impact the creation
of the temp files.

I'd suggest trying to reproduce this after ensuring
that RDMS$BIND_WORK_FILE and the sort work files
logicals are deassigned.  Then start defining the
logicals to determine what one causes the problem.

It looks to me as though there is a problem in
creating the correct file name.  You might try to
make sure that you can do something like:

	$create SORTWORK0:x.x
	$create SORTWORK1:x.x

    After I finally got hold of the customer (the call was logged via
    mail), it turned out that the directory where the sortwork file was
    supposed to go did not exist on the disk.
    
    I would have expected an error message like DNF directory not found.
    
    /Regina                        
    

This sounds like a problem.  Please describe the problem and submit a BUG
report.  I would think we could give a better message.  This is not the first
time I have seen this.

Ian