Skip to main content
Question

'ERROR: null value in column "objectid" violates not-null constraint - postgres/ArcSDE

  • March 27, 2020
  • 2 replies
  • 281 views

raaaju1990
Contributor
Forum|alt.badge.img+9

Hi,

I have an ArcSDE geodatabase on postgres. Im using a feature writer to insert records in an existing feature class.

While doing so, I get the below error 'ERROR: null value in column "objectid" violates not-null constraint'

When I drop the table and create new while writing, I get no errors.

Logically, the sde should autogenerate this objectid field whenever I insert a new record. Am I right or where am I going wrong?

Please suggest

Thanks

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

2 replies

oscard
Influencer
Forum|alt.badge.img+22
  • Influencer
  • March 27, 2020

That's weird.

 

 

FME ignores the OBJECTID value even if you pass it to the Writer.

Is the OBJECTID in the attribute list of your Writer? I would remove it just in case.


david_r
Celebrity
  • March 27, 2020

Are you using the POSTGRES or the GEODATABASE_SDE writer format in FME?

Only ESRI writers will automatically populate the OBJECTID values, with any other writer (e.g. POSTGRES) you will have to manually specify the value.

If you are using the GEODATABASE_SDE writer, it would be helpful if you could post the FME log here.