Community
Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

Could not drop constraint. Problem when Table moved to QA server

Former Member

‎2010 Jul 02 12:39 PM

0 Likes
1,431

Dear Experts,

I modified a transparent 'Z' table by adding three fields to it. It was already having four fields as primary keys and it was working fine. I created Lock object for this table as well.

Now the problem is when I moved it to Quality server, It is accepting duplicated entries even though primary keys are already defined to it.

I checked Utilities --> Database Object --> Check in SE11, it showing - 'Unique index 0 does not exist' - means, Primary Key is not got created in Database level (MS SQL).

Then I tried to 'Activate and Adjust Database'' using SE14 (used BASIS userId), then its showing error - 'Constraint <Primay Key name> does not belong to table <Table name>. Could not drop constraint.

Its nothing but an SQL error. How to solve this issue ?

These issues are not showing in Dev. server.

Please help.

John.

Dear Experts,

I modified a transparent 'Z' table by adding three fields to it. It was already having four fields as primary keys and it was working fine. I created Lock object for this table as well.

Now the problem is when I moved it to Quality server, It is accepting duplicated entries even though primary keys are already defined to it.

I checked Utilities --> Database Object --> Check in SE11, it showing - 'Unique index 0 does not exist' - means, Primary Key is not got created in Database level (MS SQL).

Then I tried to 'Activate and Adjust Database'' using SE14 (used BASIS userId), then its showing error - 'Constraint <Primay Key name> does not belong to table <Table name>. Could not drop constraint.

Its nothing but an SQL error. How to solve this issue ?

These issues are not showing in Dev. server.

Please help.

John.

Reply
4 REPLIES 4
Read only

Former Member

‎2010 Jul 02 1:22 PM

0 Likes
857

Hi,

I think as you added new fields after taht some thing is not get transported in production.

make sure that each field,data element,domain...etc get transpoted correctly.

I am sure it is issue of TRANSPORT REQUEST.

Regards,

Pravin

Read only

Former Member
In response to Former Member

‎2010 Jul 02 2:08 PM

0 Likes
857

Thanks Pravin,

But that is not the case here.

Every depended elements have moved along with the table to QA. I checked again.

If it was a transport request problem, it would have given an error message in the 'Transport Log' saying - 'Depended dataelement/domain not generated/activated'. which is not the case here.

John

Read only

Former Member

‎2010 Jul 04 8:19 PM

0 Likes
857

Hi John,

Can you have a look at the Software Component versions of the Development and Quality Servers? Also, check what are the SP that's been applied on both the systems.

You can try regenerating all the associated objects in the Quality system once more. Else, make a small change in the development system( Like a desc change) and then regenerate all the objects in the dev and lock the same in a transport request. Then release the request and check whether your problem got resolved or not.

Hope this will help.

Thanks,

Samantak.

Read only

Former Member

‎2010 Jul 06 5:11 PM

0 Likes
857

Dear all,

Thanks for your resopnse.

The problem got solved. It was purly DBA issue. As the error was showing, the primary index was not regenerating/correpted in the Database server. BASIS people has the authority to regenerate the index directly in the DBA system. They hae done it and issue got resolved.

thanks,

John V.