We had a set of long-time Oracle 12c Database installations (multiple instances on separate VMs) on Windows Server. Over the past year we transitioned to Oracle 19c on Windows Server 2019. We found that database links that worked in the 12c environment did not work in the 19c environment; a query referencing such a link would fail with the error ORA-12631: Username retrieval failed. SQLNET traces showed

naun5validate: SPP is NEGOTIATE 

naun5validate: SSPI: 0x8009030c error in AcceptSecurityContext

Because we run multiple instances of the same application on the dev-servers, I'm trying to add the sqlnet.client_registration-parameter to the sqlnet.ora-files used by each instance. This, I hope, would help us distinguish clients by the instance-name instead of (or in addition to) hostname:

sqlnet.client_registration=MeowMeow

However, I do not see the configured strings anywhere in the V$SESSION -- is there some other place to look for the "MeowMeow" from the above example?

We ran into a problem, and so we're trying to understand all about the password versions. Here is what happened: We upgraded from 11g to 12c. Our sqlnet.ora had this parameter: SQLNET.ALLOWED_LOGON_VERSION = 8. Users were able to log in, using both upper & lower case passwords. So all was good. However, since SQLNET.ALLOWED_LOGON_VERSION = 8 was deprecated, thousands of error messages were going into the alert log. So, we commented out that parameter, and added SQLNET.ALLOWED_LOGON_VERSION_SERVER = 8, but then started receiving ORA-01017. So, we basically reset the password using "alter user......". Once that was done, any client that had an upper case password could no longer connect. We noticed that the 10G was missing from the password_versions string. So, to fix this, we put the SSQLNET.ALLOWED_LOGON_VERSION_SERVER = 11, then reset the password again, and then reset it back to SQLNET.ALLOWED_LOGON_VERSION_SERVER = 8. The password_version string now contained 10G again, but still could not log in with an upper case password. So to finally fix this, we disabled password case sensitivity. So we are curious on a couple things. First, why does the SQLNET.ALLOWED_LOGON_VERSION matter when it comes to the password_version? And, why after getting the 10G back into the password_version string, did it still not behave as it did before? Many thanks.

currently I can access a database on a remote server using Oracle's instant client "sqlplus" The connection is dependent on a couple of configuration files in: $ORACLE_HOME/network/admin which are called sqlnet.ora and ldap.ora The ldap.ora file has contents of: DEFAULT_ADMIN_CONTEXT="" DIRECTORY_SERVERS=(:,:) DIRECTORY_SERVER_TYPE=OID the sqlnet.ora file has entries of: NAMES.DEFAULT_DOMAIN= NAMES.DIRECTORY_PATH=(LDAP, TNSNAMES) I would like to be able to connect with mariadb client instead of Oracle's client, but I don't know how to configure this. Could someone help me please?

I have a mixed environment running both 11g and 12c databases on the same server. One of our databases was recently upgraded to 12c, and the older Oracle clients have started throwing ORA-28040 errors on connection attempts due to the use of older authentication protocols. On the database server, each instance is installed in a separate Oracle Home with it's own Oracle software. The sqlnet.ora files in each ORACLE_HOME/network/admin directory have been created as a symbolic link to a central sqlnet.ora file on a shared NFS disk. I would like to use the SQLNET.ALLOWED_LOGON_VERSION_SERVER parameter in the central sqlnet.ora file to allow connections from the older clients until they can be upgraded. The concern I have is this: If the parameter is only supported by 12c, I need to be sure that including it won't cause problems for connections to the 11g databases. Is it safe to include this parameter in the sqlnet.ora file of an 11g database? Will it simply be ignored?

I installed oracle 12c pn windows following the defaults settings... I end up with ORCL and ORCLPDB... I can connect to ORCLPDB using EZCONNECT via CONN system/password@//localhost:1521/ORCLPDB . Then I added a service name in my tnsnames.ora like this : ORCLPDB = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 127.0.0.1)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = orclpdb) ) ) But when I try connect system/password@ORCLPDB I get the following error : >ORA-12154: TNS:could not resolve the connect identifier specified This is strange because lsnrctl services has the following entry : >Service "orclpdb" has 1 instance(s). Instance "orcl", status READY, has 1 handler(s) for this service... Handler(s): "DEDICATED" established:0 refused:0 state:ready LOCAL SERVER What should I do ?

I have set sql.expire_time parameter to 10 which recommends me to keep in my two node RAC database. At times, my application gets the error ORA-3135, therefore I suspect that this parameter could have some role to play here.. What exactly does this parameter do? Does it have anything to do with the error im facing? I do not have any firewalls between my database and app server.

I wanted to extract some information from the server trace file that is generated after I send a connect statement to the database. I wanted to know the naming convention for the server trace file. I could figure out that the name is in the below format: _ORA_.trc I wanted to know what is the 4_digit_id that is appended at the end of the trace. As per my research it seems to the process id of the oracle server. I queried the v$process for the pid column, however it seems to be returning multiple values and that too are not in 4 digit. It would be really appreciated if an expert can comment on this. Is there a way to identify the spid of a failed login attempt? For instance I would like to know the spid for the process when I issue the below command: sqlplus non_existent_user/random_password BTW, the server trace is enabled through sqlnet.ora where trace_level_server=16 is set.

What is the significance of having ".WORLD" on the end of an Oracle connection name? I've found things to still connect without that suffix. I've also noticed that both the client tnsnames.ora file and the server tnsnames.ora file must both have this suffix (or none at all) in order to communicate.