SMP 2.2 Deployment of package (update) problem in SCC

Question

Hi everybody,
Hope you can help. I'm currently working on some updates of a mobile application. The changes on the frontend and backend work ok. The problem lies in the update of the Sybase part. We already have a complete environment up and running and that works ok. I recently changed one of the structures of the bapi's which lay behind a MBO. I've refreshed the MBO and I see the new attributes in the workspace.
The second step is to build the package. This works as well.
The third step is to make sure the structure changes are also present in the backend system (QAS). This works ok.
The fourth step is to deploy it in our QAS domain of the SUP server using SCC. I follow the normal steps to update the Package and than the trouble starts. It says it failed to update the current package and provides me with the following errors (I've reduced it to the essential ones):
2014-03-05 09:11:31.023 Subsystem=Error,Application ID=,Application Connection ID=,User=,Correlation ID=,Package=,Root Context ID=,Transaction ID=,MBO=,Operation=,Thread ID=679,Node ID=SUP01,Error=DataServices: deploys intersect, not allowed with mode UPDATE.
And the following related to the newly added attributes:
2014-03-05 09:11:31.014 Subsystem=Error,Application ID=,Application Connection ID=,User=,Correlation ID=,Package=,Root Context ID=,Transaction ID=,MBO=,Operation=,Thread ID=679,Node ID=SUP01,Error=Column "XYZ" :new attribute
And
2014-03-05 09:11:31.014 Subsystem=Error,Application ID=,Application Connection ID=,User=,Correlation ID=,Package=,Root Context ID=,Transaction ID=,MBO=,Operation=,Thread ID=679,Node ID=SUP01,Error=DataServices: MBO: "Inspections" Column "XYZ" :new attribute.
And
2014-03-05 09:11:31.013 Subsystem=Error,Application ID=,Application Connection ID=,User=,Correlation ID=,Package=,Root Context ID=,Transaction ID=,MBO=,Operation=,Thread ID=679,Node ID=SUP01,Error=Columns Conflict
The problem is that the programmer who did al this is not available. I have a guide which I was following to the letter but somehow this doesn't work anymore. Documentation of sybase does not provide information about these errors (as far as I could find).
Hope you can help!
Cheers!
Laurens

Answer 1

I found the following in the documentation. Do I interpret it correctly by saying that adding attributes would result in errors?
http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc01283.0213/doc/html/fre1321910988667.html
Supported Changes for Update Deployment
Understand package changes supported by an Update deployment.
Allowed package updates include:
Adding MBOs to a new synchronization group
Changing the Cache Policy
Adding or removing Result Set Filters
Adding or removing Result Checkers
Adding operation parameters with default values
Adding or removing a logical role
During deployment, multiple messages may be returned via the ProgressMonitor, which display in the Error Log view in Unwired WorkSpace. Verification does not halt if an error is detected, it continues to log all relevant error messages. When deploying a package in Update mode where an existing version of that package is deployed, deployment fails verification and returns an error if it "breaks" the existing application.
Detailed messages returned from Unwired Server for an Update deployment indicating what the update consists of includes:
MBO: {MBOName} Column {name} :new attribute
Columns Conflict in MBO {MBOName} different nodes
Schema validation messages returned from Unwired Server if an Update deployment fails include:
Deploys intersect, not allowed with mode UPDATE
Cannot Merge Documents. Name or version does not match