Re: Oracle 8.0.5 and database links

From: AleX <korrozia_at_my-deja.com>
Date: Thu, 29 Jul 1999 19:05:30 GMT
Message-ID: <7nq8lj$1e4$1@nnrp1.deja.com>

This is a long running bug which was tbf in 7.3.4

The problem is one of the shared libraries that has an empty table for the authentication adapters. 2 things can be done:

you can bug OSS to get them to supply you with the correct libabry
install at least one sqlnet authentication adapter.

In article <379fbc0f.5147435_at_newshost.gu.edu.au>, K.Grant_at_mailbox.gu.edu.au (Kevin Grant) wrote:
> On 28 Jul 1999 07:54:01 GMT, dbaoracle_at_aol.com (DBAOracle) wrote:
>
> >We have migrated two Oracle databases from 7.3 to 8.0.5.1.
Unfortunatly the
> >database links in the newly migrated databases no longer work (these
links
> >point back to other 7.3 databases). I can create links to other 805
databases
> >with no problem. I've also tested building the same link in 8.0.4.3
and it
> >appears to work fine. Oracle 8.1.5 gives the same failure.
> >
> >I've worked with Oracle support for two days, and I am certain this
is a bug,
> >has anyone found a work around they would like to share please? I
have also
> >tried to create a new 8.0.5 database and the links still don't work
(so this
> >isn't a migration issue).
> >
> >Robert
> >
>
> Robert,
>
> Although not, from your description, the same problem I was having,
> maybe the following information will be of help.
>
> There is a problem when connecting from an Oracle 8.0.5 instance to
> another 8.0.5 instance. For example:
>
> DB1 Oracle 7.3.4 instance
> DB2 Oracle 8.0.4 instance
> DB3 Oracle 8.0.5 instance
> DB4 Oracle 8.0.5 instance
>
> Scenario 1:
> - From within the DB1 enviornment run sqlplus. From within SQLPLUS
> 'Connect user_at_DB2': No problems.
> Scenario 2:
> - From within the DB1 enviornment run sqlplus. From within SQLPLUS
> 'Connect user_at_DB3': No problems.
> Scenario 3:
> - From within the DB3 enviornment run sqlplus. From within SQLPLUS
> 'Connect user_at_DB1': No problems.
> Scenario 4:
> - From within the DB3 enviornment run sqlplus. From within SQLPLUS
> 'Connect user_at_DB2': No problems.
> Scenario 5:
> - From within the DB3 enviornment run sqlplus. From within SQLPLUS
> 'Connect user_at_DB4': Error: Failed Authentication Services.
>
> There only seems to be a problem when connecting from an Oracle 8.0.5
> instance to another 8.0.5 instance.
>
> If the line 'SQLNET.AUTHENTICATION_SERVICES' is commented out of
> '/var/opt/oracle/sqlnet.ora' or if the value is changed to 'BEQ,NONE'
> then the error no longer occurs.
>
> Oracle were notified of this problem. The work around they suggest is
> the one described above.
>
> The Oracle documentation describes:
>
> SQLNET.AUTHENTICATION_SERVICES
> Purpose:
> Enables one or more authentication services. If
> authentication has been installed, it is recommended that this
> parameter be set to either NONE or to one of the authentication
> adapters.
> Available
> Values:
> NONE - the database will use the username and password to
> log in
>
> ALL - Enables all authentication adapters to be used.
>
> BEQ - always used in conjunction with one or more of the
> following items:
>
> KERBEROS5 - use the Kerberos adaptor
>
> SECURID - use SecurID
>
> CYBERSAFE - use Cybersafe
>
> IDENTIX - use Identix
>
> DCEGSSAPI - use DCE GSSAPI
> Example:
>
> sqlnet.authentication_services =(beq, kerberos5, cybersafe)
>

                 Alex Shterenberg

"I hate people. I think they should suffer as much as possible, and therefore I'm into those old communist

dictatorships." - Euronymous, Mayhem

Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't. Received on Thu Jul 29 1999 - 14:05:30 CDT