It would be extremely helpful if you provided more details. The above is like saying over the phone - "Doc, my arm hurts"........without explaining that it was because you go too close to the stove and burned it.
- e.g. what operations were you doing when problem occurred
- e.g. any stack traces in the log
There were changes in ASE 16.0 GA (long before sp02) in which many previous shared table locks were removed. It could be that some section of code was expecting them (and shouldn't be) or needs them now. It also could be for a variety of other reasons - e.g. a old style reorg that escalates to a tablelock when it hits a forwarded row but couldn't for some reason.