cancel
Showing results for 
Search instead for 
Did you mean: 

"Asked to AND bitmaps of different length" error occurring since at least 2007

sladebe
Active Participant
0 Kudos

I've been getting errors like this since at least 2006 (version 12.6?). They happen sporadically after doing a "create subscription" command. This error occurred on 15.7.1 SP300:

E. 2018/07/12 12:35:16. <br>ERROR #25021 DIST(170 LogicalConnection.MyDb) - /generic/useful/bm.c(553)
Asked to AND bitmaps of different length<br>I. 2018/07/12 12:35:16. DIST for 'MyASEServer.MyDb' is waiting for SQM(s) to flush to outbound queue(s).<br>I. 2018/07/12 12:35:16. <br>The distributor for 'LogicalConnection.MyDb' is shutting down

This is a sporadic error, but occurs relatively frequently (occurs after maybe 1 out of 20 create subscription commands?).

I can't find any documentation pages or Knowledge Base entries for this.

I did find a archived community discussion about this with a summary explanation by Mark Parsons:

https://archive.sap.com/discussions/thread/3873000

There was a relevant Sybase Solved case 11113916 which said to reboot after, but is no longer available

I've opened an "incident" with SAP about this.

Does anybody else still get this sort of error? Any ways to prevent it?

Thanks in advance
Ben

Accepted Solutions (1)

Accepted Solutions (1)

sladebe
Active Participant
0 Kudos

Knowledge Base Answer (KBA) 2651802 was created for this.

2651802 - ERROR #25021 Asked to AND bitmaps of different length - SRSVersion 1 from 03.08.2018 in English

Symptom:

ERROR #25021 DIST(3075 PDS.PDB) - seful/bm.c(553) Asked to AND bitmaps of different length DIST for 'PDS.PDB' is waiting for SQM(s) to flush to outbound queue(s) The distributor for 'PDS.PDB' is shutting down

Environment:

SAP Replication Server (SRS) All versions

Cause:

The bitmap is used for internal code checking. Repserver keeps all the RDBs as bitmaps and caches them in memory. Error 25021 can be caused by inadequate cache an or inconsistency (orphaned row(s) in rs_rules) in the RSSD.

Check for orphaned rows. A result set of 1 or more rows is indicative of an orphan: select * from rs_rules where dbid not in (select distinct dbid from rs_subscriptions)

Resolution:

Workaround:
There are multiple approaches to remedy the error. Choose one of the following:
resume distributor PDS.PDS
Cycle the repserver
Increase dist_sqt_max_cache_size or sqt_max_cache_size
delete orphaned row(s) in rs_rules (back up RSSD before performing this option)

Answers (0)