Unable to insert to source because the sequence [RECORD_NAME]_SQ is not valid, does not exist, or is not accessible.

Hello everyone,

I’m experiencing an issue after changing the structure of a record in our development environment. Since we don’t have direct access to the database where the records are stored, we had to send the scripts to the client’s database admin to execute and reflect the changes in test environment. Now, the fields are the same in both the DEV and TEST environments.

However, at first, the record in TEST failed to synchronize, showing an error related to the record. After manually re-syncing, the synchronization succeeded. The specific error message is in the execution of a process model, in the Write Records node:

Unable to insert to source because the sequence PARTICIPACIONES_SQ is not valid, does not exist, or is not accessible.

The Write Records node is actually trying to save the "Relacion Socio" record, which has a one-to-many relationship with "Participaciones" (the record that also underwent structural changes and is now synchronized).

The Write Records node is saving Relacion Socio in this format: RelacionSocio(data: 1, participaciones(dataitem:1, etc.))

The problem only occurs in TEST environment.

Has anyone encountered a similar issue, or do you have any suggestions on how to address this?

Thank you in advance for your help!

  Discussion posts and replies are publicly visible

Parents
  • 0
    Certified Associate Developer

    I had the same problem in the TEST environment. For me, the problem was exactly the DB sequence.

    I forgot to create the sequence related to the record table in the TEST DB.

    You should check if the sequence exists in your TEST DB, if it doesn't exist run the SQL command "create sequence [RECORD_NAME]_sq start with 1 increment by  1;" and then synchronise the record again.

    My processes returned to work as usual, without errors. I hope it works for you.

Reply
  • 0
    Certified Associate Developer

    I had the same problem in the TEST environment. For me, the problem was exactly the DB sequence.

    I forgot to create the sequence related to the record table in the TEST DB.

    You should check if the sequence exists in your TEST DB, if it doesn't exist run the SQL command "create sequence [RECORD_NAME]_sq start with 1 increment by  1;" and then synchronise the record again.

    My processes returned to work as usual, without errors. I hope it works for you.

Children
No Data