[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

4986.0. "Dispatch unavailable after installing 6.1A" by ukvms3.uk.oracle.com::PJACKSON (Oracle UK Rdb Support) Fri Jan 31 1997 08:08

    A customer has installed V6.1A onto two Alpha's (VMS 6.2). On the
    second (more important) one the IVP failed with an RDB UNAVAILABLE
    message about Rdb Dispatch followed by a RDB TEXT message about BAD
    PARAMS.
    
    I've got him to check for images in sys$specific, old installed images,
    the versions of rdbshr and rdb$share, and for logical names. They all
    look OK. He can reproduce the error by trying to create a database from
    interactive SQL and RDO.
    
    Using SET WATCH FILES/CLASS=MAJOR we found a difference between his
    systems.
    
    The working one reports the image names SQL$, SQL$UTL_SHARE61, and
    RDB$SHARE, etc. On the one that fails the third image is RDB$COSIP. It
    continues til the SQL prompt appears, but fails immediately when he
    tries to create a database. RDB$SHARE is not installed.
    
    Any ideas?
    
    Peter

T.R	Title	User	Personal Name	Date	Lines
4986.1		M5::LWILCOX	Chocolate in January!!	`Fri Jan 31 1997 08:32`	8
	<<< Note 4986.0 by ukvms3.uk.oracle.com::PJACKSON "Oracle UK Rdb Support" >>> How about protections? I'd have him deinstall all Rdb-related images by hand, then run rmonstart, and ensure that the right images get installed, etc.. I hate this one more than just about any other. Liz
4986.2		ukvms3.uk.oracle.com::PJACKSON	Oracle UK Rdb Support	`Fri Jan 31 1997 08:58`	12
	>How about protections? He was using a privileged account, so I don't think that is likely to be the cause. I left him rebooting the system. Now I can't get back to him - his phone is either engaged or unavailable. Since he is in the US and this is a P1 call, I am going to have to send it your way. Sorry :-( Peter
4986.3		M5::LWILCOX	Chocolate in January!!	`Fri Jan 31 1997 09:18`	13
	<<< Note 4986.2 by ukvms3.uk.oracle.com::PJACKSON "Oracle UK Rdb Support" >>> >> I left him rebooting the system. Now I can't get back to him - his >> phone is either engaged or unavailable. Since he is in the US and this >> is a P1 call, I am going to have to send it your way. It figures...I got him. Turns out that RDB$COSIP.EXE was not installed. Once that was installed all was well. Am I good or what? :-).
4986.4		HOTRDB::LASTOVICA	Is it possible to be totally partial?	`Fri Jan 31 1997 09:20`	4
	>Turns out that RDB$COSIP.EXE was not installed. Once that was >installed all was well. what didn't rmonstart install it correctly?
4986.5		ukvms3.uk.oracle.com::PJACKSON	Oracle UK Rdb Support	`Fri Jan 31 1997 09:23`	8
	>Turns out that RDB$COSIP.EXE was not installed. Once that was installed >all was well. Am I good or what? You're good. I'll close my call. I suppose I owe you some chocolate :-) Peter
4986.6		M5::LWILCOX	Chocolate in January!!	`Fri Jan 31 1997 09:36`	6
	<<< Note 4986.4 by HOTRDB::LASTOVICA "Is it possible to be totally partial?" >>> >> what didn't rmonstart install it correctly? My guess is something is strange/different about his SQL$STARTUP.COM since that's where it gets installed. We'll work that out later.
4986.7		ukvms3.uk.oracle.com::PJACKSON	Oracle UK Rdb Support	`Fri Jan 31 1997 10:32`	8
	> what didn't rmonstart install it correctly? RMONSTART knows nothing about it. UKVMS3> search rmonstart61.com rdb$cosip %SEARCH-I-NOMATCHES, no strings matched Peter
4986.8		M5::LWILCOX	Chocolate in January!!	`Fri Jan 31 1997 15:37`	10
	<<< Note 4986.7 by ukvms3.uk.oracle.com::PJACKSON "Oracle UK Rdb Support" >>> >> RMONSTART knows nothing about it. >> UKVMS3> search rmonstart61.com rdb$cosip >> %SEARCH-I-NOMATCHES, no strings matched Right, but the sql startup which is called from monstart does (or is suppossed to) know about it. At least on our system.