cancel
Showing results for 
Search instead for 
Did you mean: 

Error during project deployment

Former Member
0 Kudos

Hi,

When I'm trying to deploy the prject that I'm working on, I get an error.

When I look at the server log, I see this exception:

"com.sybase.jdbc3.jdbc.SybSQLException: SQL Anywhere Error -193: Primary key for table 'SYNC_DATA' is not unique: Primary key value ('1,412')"

All help appreciated.

Accepted Solutions (0)

Answers (4)

Answers (4)

Jitendra_Kansal
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi,

Is this issue resovled?

Rgrds,

Jitendra

Jitendra_Kansal
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi,

has this issue been resolved?

Rgrds,

Jitendra

Former Member
0 Kudos

Hi Jitendra,

No, it hasn't been resolved yet. A colleague told me there was a problem with the SUP server.

They are trying to solve it now.

Regards,

Adam

Former Member
0 Kudos

HI Jitendra,

We reinstalled the server and it didn't work, it still gives the same error.

Is there a way to directly acces the sync_data" table and delete the entry?

Regards

Adam

Jitendra_Kansal
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi,

Please check this,

there is one table sync_data in cluster DB that you are looking for,

Rgrds,

Jitendra

Jitendra_Kansal
Product and Topic Expert
Product and Topic Expert
0 Kudos

SQL Anywhere Error -193 says

You attempted to add a new row to a table, but the new row has the same primary key as an existing row. The database has not added the incorrect row to the database. For example, you might have added a student with student number 86004 and there is already a row for a student with that number

Follow the steps while redeploying the mbo

http://scn.sap.com/community/developer-center/mobility-platform/blog/2013/05/11/steps-redeploy-mbo-p...

Rgrds,

Jitendra

former_member228049
Participant
0 Kudos

Are you talking about SM 2.x version ? if yes, has  the project you were working deployed before, if yes, delete first and then try to deploy again.  if no, try to delete the error message in the server log and re-deploy to see if the error message did come from deployment , if yes, try to check db to see in the table already have the data with that primary key