While upgrading your Oracle database server from 10g to 19c, you want to ensure that the users can still connect with their current passwords after the upgrade. What do you need to set explicitly…

Question

Options

• ASQLNET.ALLOWED_LOGON_VERSION_SERVER = 12a in the sqlnet.ora of the new database
• BClient net. allowed_lLOGON_VERSION_client must be set to a lower value than the server
• CSQLNET.ALLOWED_LOGON_VERSION_client = 8 in the sqlnec.ora file of the client application.
• DSQLNET.ALLOWED_LOGON_VERSION_sebveb = 8 In the aqlnec.ora of the new database

• A
  3% (2)
• B
  9% (5)
• C
  3% (2)
• D
  84% (49)

Explanation

Setting SQLNET.ALLOWED_LOGON_VERSION_SERVER = 8 in the sqlnet.ora on the new 19c server is correct because it tells the server to accept connections from clients using the older 10g-era authentication protocol (DES-based hashing). Without this, Oracle 19c defaults to requiring version 12+ authentication, which 10g-era password hashes cannot satisfy - locking out existing users.

Why the distractors fail:

• A is the opposite of helpful - setting the server to 12a raises the minimum authentication requirement, blocking 10g passwords rather than allowing them.
• B is a distractor about client-side configuration; ALLOWED_LOGON_VERSION_CLIENT controls what protocol versions the client will accept from a server, not whether the server accepts old passwords.
• C sets the client parameter to 8, which only affects what the client tolerates from the server's response - it does nothing to make the server accept old password hashes.

Memory tip: The word SERVER is the key - old passwords must be accepted by the server, so you configure the server-side parameter (ALLOWED_LOGON_VERSION_SERVER). Set it low (8) to allow legacy logins. "Low server = old passwords survive."

Note: Option D contains deliberate typos (sebveb, aqlnec.ora) in the exam - don't let that distract you; focus on the underlying concept, which is correct.

No community discussion yet for this question.