If you have created a broker that uses a Sybase database, and you expect to run message flows that include message aggregation, you are recommended to apply row-level locking to the aggregation table in the database. If you do not plan to use aggregation, you do not have to make this change.
If you do not apply row-level locking, and your use of message aggregation is too great, the broker will experience deadlock problems.
To apply row-level locking:
isql -Umqsiuid -Pmqsipw
If you have authorized another user ID and password for broker access to this database, substitute your values for mqsiuid and mqsipw in that command.
use WBRKBKDB
If you have created your broker database with a different name, substitute your name for WBRKBKDB in that command.
alter table mqsiuid.BAGGREGATE lock datarows
If the owner of this database instance is not mqsiuid, substitute the correct schema name in that command.
go
sp_help BAGGREGATE go
The locking scheme is displayed: lock scheme datarows.
If the change has not completed, it is displayed as: lock scheme allpages.
Related concepts
Message flow aggregation
Related tasks
Preparing Oracle or Sybase databases on UNIX platforms
Connecting to the databases
Authorizing access to the databases
Related reference
Supported databases
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ah14510_ |