<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dba_profiles on Oracle Scripts</title><link>https://www.oraclescripts.com/tags/dba_profiles/</link><description>Recent content in Dba_profiles on Oracle Scripts</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>OracleScripts.com</copyright><lastBuildDate>Sun, 31 Dec 2023 00:00:00 +0000</lastBuildDate><atom:link href="https://www.oraclescripts.com/tags/dba_profiles/index.xml" rel="self" type="application/rss+xml"/><item><title>How to Block a User in Oracle Database (ACCOUNT LOCK)</title><link>https://www.oraclescripts.com/post/lock-or-unlock-oracle-user/</link><pubDate>Sun, 31 Dec 2023 00:00:00 +0000</pubDate><guid>https://www.oraclescripts.com/post/lock-or-unlock-oracle-user/</guid><description>
&lt;h2 id="lock-or-unlock-an-oracle-user-in-the-database"&gt;Lock or Unlock an Oracle User in the Database&lt;/h2&gt;
&lt;h2 id="purpose"&gt;Purpose&lt;/h2&gt;
&lt;p&gt;A contractor leaves on Friday. A service account password shows up in a chat log. A batch user fails to log in 40 times from an unknown host. In each case the first move is the same: shut the account without dropping it. &lt;code&gt;ALTER USER ... ACCOUNT LOCK&lt;/code&gt; does that. The user, its objects, its grants and its password stay in the database, but a login attempt is refused.&lt;/p&gt;</description></item></channel></rss>