Links
Home
Oracle DBA Forum
Frequent Oracle Errors
TNS:could not resolve the connect identifier specified
Backtrace message unwound by exceptions
invalid identifier
PL/SQL compilation error
internal error
missing expression
table or view does not exist
end-of-file on communication channel
TNS:listener unknown in connect descriptor
insufficient privileges
PL/SQL: numeric or value error string
TNS:protocol adapter error
ORACLE not available
target host or object does not exist
invalid number
unable to allocate string bytes of shared memory
resource busy and acquire with NOWAIT specified
error occurred at recursive SQL level string
ORACLE initialization or shutdown in progress
archiver error. Connect internal only, until freed
snapshot too old
unable to extend temp segment by string in tablespace
Credential retrieval failed
missing or invalid option
invalid username/password; logon denied
unable to create INITIAL extent for segment
out of process memory when trying to allocate string bytes
shared memory realm does not exist
cannot insert NULL
TNS:unable to connect to destination
remote database not found'>ora-02019
exception encountered: core dump
inconsistent datatypes
no data found
TNS:operation timed out
PL/SQL: could not find program
existing state of packages has been discarded
maximum number of processes exceeded
error signaled in parallel query server
ORACLE instance terminated. Disconnection forced
TNS:packet writer failure
see ORA-12699
missing right parenthesis
name is already used by an existing object
cannot identify/lock data file
invalid file operation
quoted string not properly terminated
-none-

-none-

2004-08-06       - By -not available-

Reply:     <<     161     162     163     164     165     166     167     168     169     170     >>  

By setting the following values, you can require that the password used to
verify a connection always be encrypted:
Set the ORA_ENCRYPT_LOGIN environment variable to TRUE on the client
machine.
Set the DBLINK_ENCRYPT_LOGIN server initialization parameter to TRUE.
If enabled at both the client and server, passwords will not be sent
across the network "in the clear ", but will be encrypted using a modified
DES (Data Encryption Standard) algorithm.
The DBLINK_ENCRYPT_LOGIN initialization parameter is used for connections
between two Oracle servers (for example, when performing distributed
queries). If you are connecting from a client, Oracle checks the
ORA_ENCRYPT_LOGIN environment variable.
Whenever you attempt to connect to a server using a password, Oracle
encrypts the password before sending it to the server. If the connection
fails and auditing is enabled, the failure is noted in the audit log.
Oracle then checks the appropriate DBLINK_ENCRYPT_LOGIN or
ORA_ENCRYPT_LOGIN value. If it set to FALSE, Oracle attempts the
connection again using an unencrypted version of the password. If the
connection is successful, the connection replaces the previous failure in
the audit log, and the connection proceeds. To prevent malicious users
from forcing Oracle to re-attempt a connection with an unencrypted version
of the password, you must set the appropriate values to TRUE.



-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
To unsubscribe send email to: oracle-l-request@(protected)
put 'unsubscribe ' in the subject line.
--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- --