<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hello Andy,</p>
<p>the supported way is to remove the attribute from the data before
dropping it from the schema. You can use e.g. <a
moz-do-not-send="true"
href="https://wiki.evolveum.com/pages/viewpage.action?pageId=13991970">bulk
actions (a.k.a. scripting)</a> to do so.<br>
</p>
<p>Of course, we made midPoint resilient enough to avoid the worst
behavior if the administrator removes the attribute or the whole
schema without cleaning up the data first - at least we tried to.
The exact behavior can be version-dependent, but generally it is
such that:</p>
<ol>
<li>"Normal" operations on the affected objects are not possible -
e.g. such a user cannot be displayed via regular GUI. An error
is reported instead. Data in the repository are not changed,
i.e. wrong data are still there.<br>
</li>
<li>The affected object can be, however, opened via Repository
objects page, and fixed. At this moment the data are updated in
the repository.</li>
</ol>
<p>The midpoint.log file will contain warnings and errors in both
cases. So the administrator can learn where the problem is and fix
it.</p>
<p>---<br>
</p>
<p>An interesting situation could occur if some of system objects
are affected. Out of curiosity I have now checked the behavior on
master branch and found out that:</p>
<ol>
<li>When the administrator user is affected, it is still possible
to log in as this user; and then fix the data.</li>
<li>When the system configuration object is affected, the system
is usable as well.</li>
</ol>
(other objects like the Superuser role were not tested but I suppose
they should be OK as well)<br>
<p>---<br>
</p>
<p>Anyway, I would strongly recommend to follow the supported path
and remove the data first. :)<br>
</p>
<pre class="moz-signature" cols="72">Pavol Mederly
Software developer
evolveum.com
</pre>
<div class="moz-cite-prefix">On 21.07.2018 1:18, Andrew Morgan
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:alpine.DEB.2.11.1807201615560.17038@shell.onid.oregonstate.edu">I
have extended the midPoint schema by adding a file to the
${midpoint.home}/schema directory. What happens if I remove an
attribute from the schema file (maybe I don't need it anymore)?
What happens if I remove the schema file itself?
<br>
<br>
Will there be any errors when I restart midPoint? Will the
extension attribute values remain in the midPoint database?
<br>
<br>
Thanks,
<br>
<br>
Andy Morgan
<br>
Systems Administrator, Identity & Access Management
<br>
Information Services | Oregon State University
<br>
541-737-8877 | is.oregonstate.edu
<br>
_______________________________________________
<br>
midPoint mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:midPoint@lists.evolveum.com">midPoint@lists.evolveum.com</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.evolveum.com/mailman/listinfo/midpoint">http://lists.evolveum.com/mailman/listinfo/midpoint</a>
<br>
</blockquote>
<br>
</body>
</html>