• State Suggested Answer
  • +2 person also asked this people also asked this
  • Locked Locked
  • Replies 11 replies
  • Answers 3 answers
  • Subscribers 97 subscribers
  • Views 14151 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Enable constraints 2, stuck DBQueue operation

Dario.Mariani
over 7 years ago

Hi all,

I'm using v 7.1

Eveytime I try to extend che 1IM schema with a new view or table, there is this operation "Enable constraints 2" in the DBQueue who needs to be executed before I can proceed, but this operation is stucked and won't be executed. I solved this "killing" the operation with Management Studio deleting it from the QBMDBQueueCurrent table, but I think there is a reason why it is there. What "Enable constraints 2" does and how can I prevent to blocking my system?

This happen only in the develop environment. If I remove the operation from the queue, extend the schema and transport with a change label the changes to test and production, the "Enable constraints 2" operation is ran with success and in few moments.

Parents
  • 0 over 7 years ago

    Hi Markus,

    There are indeed errors in the journal, but not sure what to make of them

     

     

    (execute slot single)50000           0              re-throw in Procedure QBM_ZConstraintEnable, Line 950000   0              re-throw in Procedure QBM_PConstraintEnable, Line 1350000       0              re-throw in Procedure QBM_PConstraintChange, Line 1450000             0              re-throw in Procedure QBM_PExecuteSQL, Line 9547  0                detected in Procedure QBM_PConstraintChange, Line 1

    The ALTER TABLE statement conflicted with the FOREIGN KEY constraint "QER_RFRL1201". The conflict occurred in database "<DBNAME>", table "dbo.BaseTree", column 'UID_Org'.

    Code starting with:

    alter table "BaseTreeCollectionF" with check check constraint QER_RFRL1201

Reply
  • 0 over 7 years ago

    Hi Markus,

    There are indeed errors in the journal, but not sure what to make of them

     

     

    (execute slot single)50000           0              re-throw in Procedure QBM_ZConstraintEnable, Line 950000   0              re-throw in Procedure QBM_PConstraintEnable, Line 1350000       0              re-throw in Procedure QBM_PConstraintChange, Line 1450000             0              re-throw in Procedure QBM_PExecuteSQL, Line 9547  0                detected in Procedure QBM_PConstraintChange, Line 1

    The ALTER TABLE statement conflicted with the FOREIGN KEY constraint "QER_RFRL1201". The conflict occurred in database "<DBNAME>", table "dbo.BaseTree", column 'UID_Org'.

    Code starting with:

    alter table "BaseTreeCollectionF" with check check constraint QER_RFRL1201

Children
No Data