# Ignition Log message Skipping schema feature

**URL:** <https://forum.inductiveautomation.com/t/ignition-log-message-skipping-schema-feature/18186>\
**Category:** Ignition\
**Created:** [May 28, 2018, 10:21am UTC](https://forum.inductiveautomation.com/t/ignition-log-message-skipping-schema-feature/18186 "2018-05-28T10:21:14Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mau89](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mau89/32/20680_2.png) [@Mau89](https://forum.inductiveautomation.com/u/Mau89)\
**Post date:** [May 28, 2018, 10:21am UTC](https://forum.inductiveautomation.com/t/ignition-log-message-skipping-schema-feature/18186/1 "2018-05-28T10:21:14Z")

</div>

Hi everyone,  
I found this messagge in wrapper.log

> INFO | jvm 1 | 2018/05/26 13:46:42 | I [g.InternalDatabaseManager] [11:46:42]: Skipping schema feature 'INTERNAL\_SQL\_TAGS' for module 'UPDATE\_SC\_PROV\_ID' - Does not apply to this db type.  
> INFO | jvm 1 | 2018/05/26 13:46:42 | I [g.InternalDatabaseManager] [11:46:42]: Skipping schema feature 'INTERNAL\_SQL\_TAGS' for module 'INCREASE\_STR\_SIZE' - Does not apply to this db type.  
> INFO | jvm 1 | 2018/05/26 13:46:43 | W [T.P.DataTypes] [11:46:43]: Invalid folder structure for UDT member. Tag cannot be added to hierarchy. Parent details may not be loaded yet, will try again if the udt parent is updated

What these mean?

thanks

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [May 29, 2018, 3:18pm UTC](https://forum.inductiveautomation.com/t/ignition-log-message-skipping-schema-feature/18186/2 "2018-05-29T15:18:23Z")

</div>

Absolutely nothing. The first two are related to the process of upgrading a legacy internal database ([pre 7.7.7 or 7.8.2](https://support.inductiveautomation.com/index.php?/Knowledgebase/Article/View/101/0/important-information-concerning-upgrading-to-777-and-782)), and the other one is just informational - what it’s saying is that on the initial readthrough of your tags from the internal database, it read a child before its containing parent (or something similar to that) so it wasn’t able to construct the UDTs correctly. As the loading continues the UDT will load in fine.