I would like to see if you set ora_session_mode to SYSDBA and don't supply a username or password that it defaults to SYS and some non-null password. That's my opinion.
Thanks, Sam Gold -----Original Message----- From: Tim Bunce [mailto:[EMAIL PROTECTED] Sent: Friday, June 06, 2003 9:16 AM To: Gold, Samuel (Contractor) Cc: 'Alan Burlison'; Andy Hassall; Christian Merz; [EMAIL PROTECTED] Subject: Re: Oracle connect internal/OS authentification So do you all think that setting ora_session_mode to ORA_SYSDBA should force the password to be non-null? Tim. On Fri, Jun 06, 2003 at 07:26:12AM -0400, Gold, Samuel (Contractor) wrote: > Very interesting..... > > -----Original Message----- > From: Alan Burlison [mailto:[EMAIL PROTECTED] > Sent: Thursday, June 05, 2003 8:16 PM > To: Andy Hassall > Cc: Christian Merz; [EMAIL PROTECTED] > Subject: Re: Oracle connect internal/OS authentification > > > Hmm, this seems to work for me as well (on Solaris). The trick seems to be > to set the ora_session_mode to ORA_SYSDBA, provide a username of 'SYS' and a > > *non-null* password - anything will do, even a single space. I've checked > this from my primary oracle login account, and by adding/removing a normal > user from/to the dba group: > > # User not in dba group > t$ /tmp/dba > ORA-01031: insufficient privileges (DBD ERROR: OCISessionBegin) > > # User added to dba group > $ /tmp/dba > BASALT > SYS > > -- > Alan Burlison > -- > > >
