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

Conference ulysse::rdb_vms_competition

Title:DEC Rdb against the World
Moderator:HERON::GODFRIND
Created:Fri Jun 12 1987
Last Modified:Thu Feb 23 1995
Last Successful Update:Fri Jun 06 1997
Number of topics:1348
Total number of notes:5438

255.0. "Oracle V5.1.22, VMS V5, VAX C V2.4" by WIBBIN::NOYCE (you're no Gordon Bell.) Wed Nov 23 1988 21:48

Can anyone help?
                 <<< TLE::DISK$NOTES_PACK:[NOTES$LIBRARY]VAXC.NOTE;1 >>>
                                -< VAX C Notes >-
================================================================================
Note 1762.0                  VAX C & ORACLE problems                  No replies
KAOFS::M_ROY                                         13 lines  23-NOV-1988 13:50
--------------------------------------------------------------------------------

A customer of our is having a problem..They are using VAX C V2.4
and ORACLE V5.1.22..They get their problems when they try to run
programs (that worked fine on VMS V4.7) on VMS V5.0 on a 6220..
The error they are getting is IMPROPERLY HANDLED CONDITION, BAD STACK
OR NO HANDLER SPECIFIED..This seems to happen after a ORACLE call
if (OPEN_ORACLE() == false)..I told him it was ORACLE related, but
they want to know why are they having problems, the only difference
is the VMS version..
	Does anybody know any problems with ORACLE V5.1.22 running 
on VMS V5.0 ?
It seems that the stack might handle the ORACLE call different in V5.0

Any help would be appreciated..
    
T.RTitleUserPersonal
Name
DateLines
255.1Check with OracleBROKE::BOOTHWhat am I?...An Oracle?Wed Nov 23 1988 22:1422
    Well, let's see. To load Oracle V5.1.22 on VMS V5.0, one must eliminate
    the possibility of the Oracle software finding the VMS version number.
    In other words, Oracle must be blind to the version, since it will
    only accomodate up to VMS 4.6 (or 4.7, I can't remember).
                                  
    So I would guess that the Oracle libraries are unaware of the version
    number as well. So, I don't know what happens under SMP. But I would
    guess that since Oracle can't see the operating system's SMP support,
    Oracle can't use it. That might not show up until the user had three
    processors instead of two.    
                                  
    The possibilities for chaos are endless. 
                                  
    In fairness, I have had reports that your version of Oracle works
    fine up to 6220. But I have had no reports on any configuration
    with more than two processors. So, who knows what happens then.
    
    You really should deal with Oracle on situations like this. There
    is little we can do to correct conditions created by their software.
    
    ---- Michael Booth