Skip to main content
raymondk8700
raymondk8700
May 31, 2024
Question

Unique Constraint During Synchronization

  • May 31, 2024
  • 4 replies
  • 0 views

Using v21.3.

I'm fairly new to Appian.

While tailing the tomcat log, I see when the ObjectSynchronizer runs, I get the following:

... WARN com.appiancorp.common.ObjectSynchronizer - 1 services were missing users.
... ERROR org.hibernate.util.JDBCExceptionReporter - ORA-00001: unique constraint ([constraint name]) violated

I am attempting to see the actual sql causing the issue.

I modified appian_log4j.properties as follows:
from "log4j.logger.com.appiancorp.common.ObjectSynchronizer=INFO"
to "log4j.logger.com.appiancorp.common.ObjectSynchronizer=DEBUG"

However, the tomcat log file does not produce any additional entries.

Is a restart required?

Would the debug entries be written to a different file?

Is there another logger that needs to be modified?

Any help would be appreciated.

    4 replies

    stefanhelzle0001
    stefanhelzle0001
    May 31, 2024

    21.3 ?

    I think the best you can do is to upgrade to a supported version.

    raymondk8700
    raymondk8700Author
    May 31, 2024

    Is upgrading going to answer any of my questions???

    stefanhelzle0001
    stefanhelzle0001
    May 31, 2024

    Not really, but you will probably not get much help from Appian for an unsupported version.

    And yes, I know this is probably not the answer you were hoping for.

    Is this a self-hosted environment? If yes, you could try to check the DB logs for this error. If this is in cloud, get it updated.

    peter.lewis
    peter.lewis
    Employee
    May 31, 2024

    Are you seeing an error / issue elsewhere in Appian outside of the tomcat log? And if so can you give some more information about where you're encountering the error? I mention this because the tomcat log is very noisy - it's a good place to go if you already know there is a problem, but it's not a great place to determine if there is a problem or not.

    Terms & ConditionsAccessibility statement