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

Conference orarep::nomahs::rdb_60

Title:	Oracle Rdb - Still a strategic database for DEC on Alpha AXP!
Notice:	RDB_60 is archived, please use RDB_70..
Moderator:	NOVA::SMITHISON

Created:	Fri Mar 18 1994
Last Modified:	Fri May 30 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	5118
Total number of notes:	28246

4980.0. "the root thinks it's name has changed!" by ORAREP::JRFVAX::HODGES () Wed Jan 29 1997 13:45

    I think this problem has to do with how logicals are being used, but
    I'm not exactly sure how to analyze it!  
    
    There are 10 databases on a node (Alpha Rdb V6.1-0, now upgraded to
    6.1-1) all running the same lab software (LIMS) from a third party.
    When I do an RMU/SHO SYS, set SQL$DATABASE to the name that
    shows up as the opened database and do a SHO TAB in interactive SQL, 
    8 of the 10 give me the following errors!
    
    %SQL-F-ERRATTDEF, could not use database file specified by SQL$DATABASE
    -RDB-F-DB_CORRUPT, database filename is corrupt
    -RDMS-F-BADROOTMATCH, root file "file-spec-as-displayed-by-RMU" no
    longer has its original name "SMP$PLTDAT:[DBASE]VGSM_RDB.RDB;1"
    
    The other 2 show me tables.  If I now use the process to define my
    process logicals, I can access the database just fine.
    
    What concerns me is that all 10 directory structures look the same and
    were supposedly created with the same software process.  So how come 8
    of the 10 think they've changed names?  
    
    A "former DBA" here thinks I need to use RMU ALTER and deposit root to
    "fix" this, but I don't want to start altering production databases
    until I understand the problem if there really is one.
    
    BTW, I found this while investigating 2 corrupt databases caused by the
    checksum off by 1 and failed recoveries.  We initially thought these
    logicals *might* have been the reason for the failed recoveries. 
    However with 8 of 10 showing the same behavior, I wonder if we wouldn't
    have had more than 2 go corrupt over a period of at least 2 months if
    the logicals were part of that problem.
    
    Thanks for any words of wisdom here.
    
    Mary Ann

T.R	Title	User	Personal Name	Date	Lines
4980.1		svrav1.au.oracle.com::MBRADLEY	I was dropped on my head as a baby. What's your excuse?	`Thu Jan 30 1997 20:02`	7
	Liz, What do you get from "SHOW LOG SMP$PLTDAT/FULL"? G'day, Mark.
4980.2		M5::LWILCOX	Chocolate in January!!	`Fri Jan 31 1997 08:28`	11
	<<< Note 4980.1 by svrav1.au.oracle.com::MBRADLEY "I was dropped on my head as a baby. What's your excuse?" >>> >>Liz, >>What do you get from "SHOW LOG SMP$PLTDAT/FULL"? >>G'day, Uhm, I know that Mary Ann and I really look quite a lot alike... :-).
4980.3	What have they been puting in my coffee?	svrav1.au.oracle.com::MBRADLEY	I was dropped on my head as a baby. What's your excuse?	`Sun Feb 02 1997 21:52`	7
	>Uhm, I know that Mary Ann and I really look quite a lot alike... My appologies to you both ... Friday brain fade no doubt. G'day, Mark.
4980.4	is "concealed" a bad word?	ORAREP::JRFVAX::HODGES		`Tue Feb 04 1997 10:51`	14
	I wish I knew as much as she does!!! Getting back to my technical issue - B-) "SMP$PLTDAT" [super]="LIMS_DISK1:[VGSM.VGSMDATA.EPO.]" [concealed] (LNM$PROCESS_TABLE) LIMS is the "name" of the 3rd party application; VGSM is the filename given to their .RDB files as well as much of their directory structure and EPO is one of the many instances of the LIMS databases on this system. Thanks for any and all help!!! Mary Ann
4980.5	Problems with this are not surprising	svrav1.au.oracle.com::MBRADLEY	I was dropped on my head as a baby. What's your excuse?	`Tue Feb 04 1997 20:18`	13
	Mary Ann, > "SMP$PLTDAT" [super]="LIMS_DISK1:[VGSM.VGSMDATA.EPO.]" [concealed] > (LNM$PROCESS_TABLE) This is bad!!! Rdb does not support the use of concealed logical names that do not translate to a device, or that are not in LNM$SYSTEM. So the above is bad. If it worked for them at all it was by accident. G'day, Mark.
4980.6	How to fix it???	ORAREP::JRFVAX::HODGES		`Wed Feb 05 1997 10:10`	6
	OK, so we're "all" in agreement that "something" needs to be fixed. But what is it and how do I fix it? There are 10 databases and 8 of them seem to have the same characteristics. Thanks, Mary Ann
4980.7	define the logical this way	UKVMS3::SHISCOCK	stand and deliver	`Wed Feb 05 1997 10:59`	9
	Either rmu/alter the root or $define/system/exec/trans=(concealed,term) SMP$PLTDAT - "$dua1:[vgsm.vgsmdata.epo.]" - whatever your device name is. cheers, Steve
4980.8	And get rid of them	svrav1.au.oracle.com::MBRADLEY	I was dropped on my head as a baby. What's your excuse?	`Wed Feb 05 1997 18:32`	10
	> Either rmu/alter the root or > $define/system/exec/trans=(concealed,term) SMP$PLTDAT - > "$dua1:[vgsm.vgsmdata.epo.]" And then use RMU/MOVE to move the DB so that it doesn't use these logical names at all. G'day, Mark.