Skip to main content
Solved

Geodatabase writer - Renamed user attribute - Invalid Characters

  • November 28, 2023
  • 9 replies
  • 353 views
rudy_v
Contributor
Forum|alt.badge.img+6

Hi

I am receiving this warning below - It worked fine in 2022.2.5. Since we have migrated - to 2023.1.x - this started to appear

It happens using GeoDatabase writer / and or FeatureWriter - using GeoDatabase : DB Version 10.9.1 on SQL Server

GEODATABASE_SDE Writer: Renamed user attribute '_Update{0}.action' to '_Update_0__action' based on format constraints for invalid characters, length, and case
GEODATABASE_SDE Writer: Renamed user attribute '_Update{0}.attributeName' to '_Update_0__attributeName' based on format constraints for invalid characters, length, and case
GEODATABASE_SDE Writer: Renamed user attribute '_Update{0}.originalValue' to '_Update_0__originalValue' based on format constraints for invalid characters, length, and case
GEODATABASE_SDE Writer: Renamed user attribute '_Update{0}.revisedValue' to '_Update_0__revisedValue' based on format constraints for invalid characters, length, and case

 

 

 

 

Best answer by danminneyatsaf

@david_r​ @hkingsbury​ @federico​ @rudy_v​ 

We're currently aware of a bug that is affecting all Esri formats writers (and PostGIS/PostgreSQL writers when "use lowercase attribute names" is enabled).

The issue results in excessive log warnings related to the renaming of attributes. This includes attributes that are not getting written to the target file/table, such as format attributes (ex. fme_feature_type, fme_data_type). In some cases, FME will log one error message per attribute per row, which not only causes huge bloat in the log file but also can cause performance slowdowns.

We've tagged the issue as critical and will update everyone here once we've released a fix.

The ticket number for this issue is FMEENGINE-81406.

 

At the moment to workaround the issue you can either disable Log Warnings via FME Options, or you can try using an AttributeExposer + AttributeRemove to remove the attributes before they reach the writer that is logging the warnings.

View original
Did this help you find an answer to your question?

9 replies

david_r
Evangelist
  • david_rEvangelist
  • November 28, 2023

I'm suspecting that dots and brackets are not allowed in column names of an Esri Geodatabase, see https://support.esri.com/en-us/knowledge-base/faq-what-characters-should-not-be-used-in-arcgis-for-fi-000005588

You can e.g. use an AttributeManager to rename the attribute names yourself before passing them on to the Writer.

hkingsbury
Celebrity
Forum|alt.badge.img+51
  • hkingsburyCelebrity
  • Celebrity
  • November 28, 2023
david_r wrote:

I'm suspecting that dots and brackets are not allowed in column names of an Esri Geodatabase, see https://support.esri.com/en-us/knowledge-base/faq-what-characters-should-not-be-used-in-arcgis-for-fi-000005588

You can e.g. use an AttributeManager to rename the attribute names yourself before passing them on to the Writer.

Yea, it's exactly that :)

rudy_v
Contributor
Forum|alt.badge.img+6
  • rudy_vContributor
  • Author
  • Contributor
  • December 6, 2023
david_r wrote:

I'm suspecting that dots and brackets are not allowed in column names of an Esri Geodatabase, see https://support.esri.com/en-us/knowledge-base/faq-what-characters-should-not-be-used-in-arcgis-for-fi-000005588

You can e.g. use an AttributeManager to rename the attribute names yourself before passing them on to the Writer.

Hi @david_r​ 

 

Thanks for the update - but it worked fine in 2022.2.5, without any warning - it only appeared, when we migrated to 2023.1. Similar other warning appeared in 2023.1 for GeoDatabase, but not in 2022.2.5

 

The above actually has written correctly into GeoDatabase

 

Regards

Rudy

federico
Participant
  • federicoParticipant
  • Participant
  • January 15, 2024

Hello, i got the same problem, When i executing the workbench with server version 2022.2.4 there was no problem. With server version 2023.1 i got the same warnings as the topic starter,. The log file contained at the end 16978 pages with these warnings. (the log file on the 2022.2.4 version was only 1 page and no warnings. anyone any ideas?

 

here are the last lines, to give an idea:

 

16976652024-1-15 13:17:53 | GEODATABASE_SDE Writer: Renamed user attribute 'attribute{5}.fme_data_type' to 'attribute_5__fme_data_type00' based on format constraints for invalid characters, length, and case16976662024-1-15 13:17:53 | GEODATABASE_SDE Writer: Renamed user attribute 'attribute{5}.name' to 'attribute_5__name00' based on format constraints for invalid characters, length, and case16976672024-1-15 13:17:53 | GEODATABASE_SDE Writer: Renamed user attribute 'attribute{5}.native_data_type' to 'attribute_5__native_data_type00' based on format constraints for invalid characters, length, and case16976682024-1-15 13:17:53 | GEODATABASE_SDE Writer: Renamed user attribute 'attribute{6}.fme_data_type' to 'attribute_6__fme_data_type00' based on format constraints for invalid characters, length, and case16976692024-1-15 13:17:53 | GEODATABASE_SDE Writer: Renamed user attribute 'attribute{6}.name' to 'attribute_6__name00' based on format constraints for invalid characters, length, and case16976702024-1-15 13:17:53 | GEODATABASE_SDE Writer: Renamed user attribute 'attribute{6}.native_data_type' to 'attribute_6__native_data_type00' based on format constraints for invalid characters, length, and case16976712024-1-15 13:17:53 | GEODATABASE_SDE Writer: Renamed user attribute 'attribute{7}.fme_data_type' to 'attribute_7__fme_data_type00' based on format constraints for invalid characters, length, and case16976722024-1-15 13:17:53 | GEODATABASE_SDE Writer: Renamed user attribute 'attribute{7}.name' to 'attribute_7__name00' based on format constraints for invalid characters, length, and case16976732024-1-15 13:17:53 | GEODATABASE_SDE Writer: Renamed user attribute 'attribute{7}.native_data_type' to 'attribute_7__native_data_type00' based on format constraints for invalid characters, length, and case16976742024-1-15 13:17:53 | GEODATABASE_SDE Writer: Renamed user attribute 'attribute{8}.fme_data_type' to 'attribute_8__fme_data_type00' based on format constraints for invalid characters, length, and case16976752024-1-15 13:17:53 | GEODATABASE_SDE Writer: Renamed user attribute 'attribute{8}.name' to 'attribute_8__name00' based on format constraints for invalid characters, length, and case16976762024-1-15 13:17:53 | GEODATABASE_SDE Writer: Renamed user attribute 'attribute{8}.native_data_type' to 'attribute_8__native_data_type00' based on format constraints for invalid characters, length, and case16976772024-1-15 13:17:53 | GEODATABASE_SDE Writer: Renamed user attribute 'attribute{9}.fme_data_type' to 'attribute_9__fme_data_type00' based on format constraints for invalid characters, length, and case16976782024-1-15 13:17:53 | GEODATABASE_SDE Writer: Renamed user attribute 'attribute{9}.name' to 'attribute_9__name00' based on format constraints for invalid characters, length, and case16976792024-1-15 13:17:53 | GEODATABASE_SDE Writer: Renamed user attribute 'attribute{9}.native_data_type' to 'attribute_9__native_data_type00' based on format constraints for invalid characters, length, and case16976802024-1-15 13:17:53 | MULTI_WRITER writer: 15430 of 15430 features written16976812024-1-15 13:17:53 | FeatureMerger (ReferenceFactory): Total Results: 15430 Complete Feature(s), 0 Incomplete Feature(s), 0 Referenced Feature(s), 0 Unreferenced Feature(s), 0 Referencer Feature(s) (NO REFERENCES), 0 Referencee Feature(s) (NO Referencee fields defined), and 0 Duplicate Referencee Feature(s)16976822024-1-15 13:17:53 | AttributeRemover (TeeFactory): Cloned 15430 input feature(s) into 15430 output feature(s)16976832024-1-15 13:17:53 | GeodatabaseRelationshipFeaturesPipeline::GeodatabaseRelationshipFeatures (SortFactory): Finished sorting a total of 0 features.16976842024-1-15 13:17:53 | Transaction #2 (final transaction) was successfully committed16976852024-1-15 13:17:54 | Closing the Esri Geodatabase writer16976862024-1-15 13:17:54 | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-16976872024-1-15 13:17:54 | Feature output statistics for `GEODATABASE_SDE' writer using keyword `FeatureWriter_0':16976882024-1-15 13:17:54 | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-16976892024-1-15 13:17:54 | Features Written16976902024-1-15 13:17:54 | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-16976912024-1-15 13:17:54 | test_SPOORBAANDEEL_LIJN 1542916976922024-1-15 13:17:54 | ==============================================================================16976932024-1-15 13:17:54 | Total Features Written 1542916976942024-1-15 13:17:54 | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

danminneyatsaf
Safer
Forum|alt.badge.img+12

@david_r​ @hkingsbury​ @federico​ @rudy_v​ 

We're currently aware of a bug that is affecting all Esri formats writers (and PostGIS/PostgreSQL writers when "use lowercase attribute names" is enabled).

The issue results in excessive log warnings related to the renaming of attributes. This includes attributes that are not getting written to the target file/table, such as format attributes (ex. fme_feature_type, fme_data_type). In some cases, FME will log one error message per attribute per row, which not only causes huge bloat in the log file but also can cause performance slowdowns.

We've tagged the issue as critical and will update everyone here once we've released a fix.

The ticket number for this issue is FMEENGINE-81406.

 

At the moment to workaround the issue you can either disable Log Warnings via FME Options, or you can try using an AttributeExposer + AttributeRemove to remove the attributes before they reach the writer that is logging the warnings.

marias
becchr
asablomberg
4 people upvoted this
  • marias
    marias
  • becchr
    becchr
  • asablomberg
    asablomberg
  • liamfez
    liamfez
tyson_moulder
Participant
Forum|alt.badge.img

@danminneyatsaf Do you have any updates on this excessive logging issue? We encountered it on the environment that we upgraded recently.  We disabled the warnings for the specific workspace that is encountering the issue.  I am concerned that we might miss a different issue with the warnings disabled.  We are seeing some logs taking between 20-50 GB of space on the server and it is causing storage alerts on our environment.

federico
david_r
becchr
3 people upvoted this
  • federico
    federico
  • david_r
    david_r
  • becchr
    becchr
david_r
Evangelist
  • david_rEvangelist
  • April 17, 2024
tyson_moulder wrote:

@danminneyatsaf Do you have any updates on this excessive logging issue? We encountered it on the environment that we upgraded recently.  We disabled the warnings for the specific workspace that is encountering the issue.  I am concerned that we might miss a different issue with the warnings disabled.  We are seeing some logs taking between 20-50 GB of space on the server and it is causing storage alerts on our environment.

@danminneyatsaf @mark2atsafe  I’d also like an update on this issue which is negatively impacting one of our clients.

Hopefully this has been resolved in the latest 2023.x?

kate-safe
Safer
Forum|alt.badge.img+6
  • kate-safeSafer
  • Safer
  • April 17, 2024

Just to update everyone - the issue with excessive logging was resolved under a related ticket (FMEENGINE-80292) and has available in build 23781 and newer!

 

If you have any questions or problems please don’t hesitate to reach out to our team!

 

 

Kate B (Technical Support Specialist)
francis
becchr
2 people upvoted this
  • francis
    francis
  • becchr
    becchr
marias
Contributor
Forum|alt.badge.img+8
  • mariasContributor
  • Contributor
  • May 10, 2024
kate-safe wrote:

Just to update everyone - the issue with excessive logging was resolved under a related ticket (FMEENGINE-80292) and has available in build 23781 and newer!

 

If you have any questions or problems please don’t hesitate to reach out to our team!

 

 

I still have similar warnings in 2024.0 version:

POSTGIS Writer: Renamed user attribute 'kml_schema_data{11}.name' to 'kml_schema_data{11}_name' based on format constraints for invalid characters, length, and case
I guess it is related to the same issue. But another reader type. Is there ticket for this as well? 

Reply


Helpful Members This Week

Community Stats

30,938
Posts
117,250
Replies
38,740
Members

Latest FME

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.