Lyall Barbour
2018-09-11 12:25:55 UTC
<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>Hi,</div>
<div> I've been testing upgrades from 11g and 12.1 to Oracle 12.2 database recently. Have bashed up against the new feature of finally defaulting case sensitivity in passwords in oracle 12.2</div>
<div> I've read up on all the different options with moving forward, but have somehow missed what i'd really like to do. Some of our systems are old and have old applications where we do not want to change the password. We would be ok with resetting the password to the same thing. We'd love to move to the "default" Oracle settings for our systems, so they'll be fine moving forward. This would be best case senario after upgrade</div>
<div> </div>
<div>1) all applications can log in with the same password they've always used.</div>
<div>2) sqlnet.ora does not change, stays default. SQLNET.ALLOWED_LOGON_VERSION_SERVER is default (not even set)</div>
<div>3) sec_case_sensitive_logon stays default (not set).</div>
<div>4) database accounts with only 10g on the password_versions column in dba_users, can log in after 12.2 upgrade.</div>
<div> </div>
<div>I thought i could do this by resetting the accounts with IDENTIFIED BY VALUES, but that hasn't worked in my tests, prior to upgrade. Do i have to reset these accounts after the upgrade? with that spare4 column in user$?</div>
<div> </div>
<div>I've looked through Google and the Community and have read answers that revolve around the sqlnet.ora file. Mark Powell, i'm looking at you.</div>
<div> </div>
<div>Can i get my optimal scenario or do i have to start setting the SQLNET.ora file parameter on these old systems?</div>
<div> </div>
<div>Thanks,</div>
<div>Lyall Barbour</div></div></body></html>
--
http://www.freelists.org/webpage/oracle-l
<div> I've been testing upgrades from 11g and 12.1 to Oracle 12.2 database recently. Have bashed up against the new feature of finally defaulting case sensitivity in passwords in oracle 12.2</div>
<div> I've read up on all the different options with moving forward, but have somehow missed what i'd really like to do. Some of our systems are old and have old applications where we do not want to change the password. We would be ok with resetting the password to the same thing. We'd love to move to the "default" Oracle settings for our systems, so they'll be fine moving forward. This would be best case senario after upgrade</div>
<div> </div>
<div>1) all applications can log in with the same password they've always used.</div>
<div>2) sqlnet.ora does not change, stays default. SQLNET.ALLOWED_LOGON_VERSION_SERVER is default (not even set)</div>
<div>3) sec_case_sensitive_logon stays default (not set).</div>
<div>4) database accounts with only 10g on the password_versions column in dba_users, can log in after 12.2 upgrade.</div>
<div> </div>
<div>I thought i could do this by resetting the accounts with IDENTIFIED BY VALUES, but that hasn't worked in my tests, prior to upgrade. Do i have to reset these accounts after the upgrade? with that spare4 column in user$?</div>
<div> </div>
<div>I've looked through Google and the Community and have read answers that revolve around the sqlnet.ora file. Mark Powell, i'm looking at you.</div>
<div> </div>
<div>Can i get my optimal scenario or do i have to start setting the SQLNET.ora file parameter on these old systems?</div>
<div> </div>
<div>Thanks,</div>
<div>Lyall Barbour</div></div></body></html>
--
http://www.freelists.org/webpage/oracle-l