<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Row with nulls in SDE.GDB_ITEMS in Geodatabase Questions</title>
    <link>https://community.esri.com/t5/geodatabase-questions/row-with-nulls-in-sde-gdb-items/m-p/1187615#M7730</link>
    <description>&lt;P&gt;&lt;EM&gt;Oracle 18c 10.7.1 GDB:&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;I noticed that our&amp;nbsp;SDE.GDB_ITEMS table has a row that is mostly null values. I discovered that row using this technique:&amp;nbsp;&lt;A href="https://gis.stackexchange.com/questions/434701/find-problem-rows-in-gdb-items-vw/434702#434702" target="_self"&gt;Find problem rows in GDB_ITEMS_VW&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Bud_0-1656463441096.png" style="width: 999px;"&gt;&lt;img src="https://community.esri.com/t5/image/serverpage/image-id/44726i3E978B5DBD4591FD/image-size/large?v=v2&amp;amp;px=999" role="button" title="Bud_0-1656463441096.png" alt="Bud_0-1656463441096.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;That null row causes problems when extracting data from the XML DEFINITION clob column in&amp;nbsp;GDB_ITEMS_VW. For example, these two queries would error-out if I selected ALL rows using CTRL+END in SQL Developer (originally, the queries didn't have WHERE clauses):&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;A href="https://gis.stackexchange.com/a/434761/62572" target="_self"&gt;Select domain codes/descriptions using XMLTABLE instead of EXTRACTVALUE&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;&lt;A href="https://gis.stackexchange.com/a/434583/62572" target="_self"&gt;Select subtype and a subtype field/domain names using SQL&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;PRE&gt;ORA-31011: XML parsing failed&lt;BR /&gt;ORA-19202: Error occurred in XML processing&lt;BR /&gt;LPX-00007: unexpected end-of-file encountered&lt;BR /&gt;ORA-06512: at "SYS.XMLTYPE", line 272&lt;BR /&gt;ORA-06512: at line 1&lt;BR /&gt;31011. 00000 - "XML parsing failed"&lt;BR /&gt;*Cause: XML parser returned an error while trying to parse the document.&lt;BR /&gt;*Action: Check if the document to be parsed is valid.&lt;/PRE&gt;&lt;P&gt;Now that I know what row is causing the problem, it's easy workaround the issue by adding a WHERE clause to the queries:&lt;/P&gt;&lt;PRE&gt;where &lt;BR /&gt;&amp;nbsp; &amp;nbsp; i.name is not null&lt;/PRE&gt;&lt;P&gt;With that said, I'm still curious how that junk row got created. I doubt anyone meddled with the system tables through the back-end using SQL. My best guess is that the row was somehow created via an ArcGIS bug. I looked at some old backups, and it would seem that row has been there for years — since the 10.3.1 GDB days. It wasn't created recently.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Questions:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Has anyone else had that issue?&lt;/STRONG&gt; Does the query below find any null rows in your Oracle GDB?&lt;/P&gt;&lt;PRE&gt;select&lt;BR /&gt;    *&lt;BR /&gt;from&lt;BR /&gt;    sde.gdb_items&lt;BR /&gt;where&lt;BR /&gt;    name is null&lt;BR /&gt;&lt;BR /&gt;OBJECTID  UUID          TYPE          NAME    PHYSICALNAME  PATH  URL     PROPERTIES  DEFAULTS  DATASETSUBTYPE1  DATASETSUBTYPE2  DATASETINFO1  DATASETINFO2  DEFINITION  DOCUMENTATION  ITEMINFO  SHAPE   CONTINGENTVALUES            
--------  ------------  ------------  ------  ------------  ----  ------  ----------  --------  ---------------  ---------------  ------------  ------------  ----------  -------------  --------  ------  ----------------
3367      {39F456FC...  {F3783E6F...  (null)  (null)        \     (null)  1           (null)    (null)           (null)           (null)        (null)        (null)      (null)         (null)    (null)  (null)&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 29 Jun 2022 05:32:50 GMT</pubDate>
    <dc:creator>Bud</dc:creator>
    <dc:date>2022-06-29T05:32:50Z</dc:date>
    <item>
      <title>Row with nulls in SDE.GDB_ITEMS</title>
      <link>https://community.esri.com/t5/geodatabase-questions/row-with-nulls-in-sde-gdb-items/m-p/1187615#M7730</link>
      <description>&lt;P&gt;&lt;EM&gt;Oracle 18c 10.7.1 GDB:&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;I noticed that our&amp;nbsp;SDE.GDB_ITEMS table has a row that is mostly null values. I discovered that row using this technique:&amp;nbsp;&lt;A href="https://gis.stackexchange.com/questions/434701/find-problem-rows-in-gdb-items-vw/434702#434702" target="_self"&gt;Find problem rows in GDB_ITEMS_VW&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Bud_0-1656463441096.png" style="width: 999px;"&gt;&lt;img src="https://community.esri.com/t5/image/serverpage/image-id/44726i3E978B5DBD4591FD/image-size/large?v=v2&amp;amp;px=999" role="button" title="Bud_0-1656463441096.png" alt="Bud_0-1656463441096.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;That null row causes problems when extracting data from the XML DEFINITION clob column in&amp;nbsp;GDB_ITEMS_VW. For example, these two queries would error-out if I selected ALL rows using CTRL+END in SQL Developer (originally, the queries didn't have WHERE clauses):&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;A href="https://gis.stackexchange.com/a/434761/62572" target="_self"&gt;Select domain codes/descriptions using XMLTABLE instead of EXTRACTVALUE&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;&lt;A href="https://gis.stackexchange.com/a/434583/62572" target="_self"&gt;Select subtype and a subtype field/domain names using SQL&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;PRE&gt;ORA-31011: XML parsing failed&lt;BR /&gt;ORA-19202: Error occurred in XML processing&lt;BR /&gt;LPX-00007: unexpected end-of-file encountered&lt;BR /&gt;ORA-06512: at "SYS.XMLTYPE", line 272&lt;BR /&gt;ORA-06512: at line 1&lt;BR /&gt;31011. 00000 - "XML parsing failed"&lt;BR /&gt;*Cause: XML parser returned an error while trying to parse the document.&lt;BR /&gt;*Action: Check if the document to be parsed is valid.&lt;/PRE&gt;&lt;P&gt;Now that I know what row is causing the problem, it's easy workaround the issue by adding a WHERE clause to the queries:&lt;/P&gt;&lt;PRE&gt;where &lt;BR /&gt;&amp;nbsp; &amp;nbsp; i.name is not null&lt;/PRE&gt;&lt;P&gt;With that said, I'm still curious how that junk row got created. I doubt anyone meddled with the system tables through the back-end using SQL. My best guess is that the row was somehow created via an ArcGIS bug. I looked at some old backups, and it would seem that row has been there for years — since the 10.3.1 GDB days. It wasn't created recently.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Questions:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Has anyone else had that issue?&lt;/STRONG&gt; Does the query below find any null rows in your Oracle GDB?&lt;/P&gt;&lt;PRE&gt;select&lt;BR /&gt;    *&lt;BR /&gt;from&lt;BR /&gt;    sde.gdb_items&lt;BR /&gt;where&lt;BR /&gt;    name is null&lt;BR /&gt;&lt;BR /&gt;OBJECTID  UUID          TYPE          NAME    PHYSICALNAME  PATH  URL     PROPERTIES  DEFAULTS  DATASETSUBTYPE1  DATASETSUBTYPE2  DATASETINFO1  DATASETINFO2  DEFINITION  DOCUMENTATION  ITEMINFO  SHAPE   CONTINGENTVALUES            
--------  ------------  ------------  ------  ------------  ----  ------  ----------  --------  ---------------  ---------------  ------------  ------------  ----------  -------------  --------  ------  ----------------
3367      {39F456FC...  {F3783E6F...  (null)  (null)        \     (null)  1           (null)    (null)           (null)           (null)        (null)        (null)      (null)         (null)    (null)  (null)&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 29 Jun 2022 05:32:50 GMT</pubDate>
      <guid>https://community.esri.com/t5/geodatabase-questions/row-with-nulls-in-sde-gdb-items/m-p/1187615#M7730</guid>
      <dc:creator>Bud</dc:creator>
      <dc:date>2022-06-29T05:32:50Z</dc:date>
    </item>
  </channel>
</rss>

