Fixing Unread Marks in Notes/Domino Open Mic...When to Use: 1-time Synch of unread marks between 2...

© 2014 IBM CorporationPowered by IBM SmartCloud Meetings

Fixing Unread Marks in Notes/DominoOpen MicJune 4, 2014

Amy Knox | Staff Software Engineer

IBM Collaboration Solutions

| © 2014 IBM Corporation2

Agenda

■ Review of Key Terms and Concepts■ Recent SPRs – The state of Unread Marks today■ Troubleshooting Tools■ Common issues■ Must Gather Information for All Cases■ 8 Techniques for Resolving Unread Mark issues in the

─Notes client ─iNotes─Traveler and BES-enabled environments

■ Resources■ Q&A


Key Terms and Concepts

■ “Unread ID Table”: The ID table, stored in the nsf, stores a list of unread documents for each user

─ All unread = all docs in the table; Read a doc = remove a doc from the table─ One table per username, per database. Each replica maintains its own Unread Table─ Stored by NoteID; thus, unique to each database

■ “Unread Journal”: Stored in the local Notes client, tracks and stores up to 20,000 consecutive operations by unid, for the purpose of synchronizing unread marks across multiple replicas of the same db

─ Tracks UNIDs of docs marked read/unread while accessing a db. ─ Does not track external API operations─ Not available outside the Notes client



■ “Unread Activity log”: Per-user, per-database log, Stored in the nsf, contains time stamped information used to determine the latest unread status for a document.

─ When a user marks a note read or unread, a new entry is added to the end of the activity log─ Data organized and then Replicated in chunks, only the new entries since last replication─ Client-initiated replication only processes that user's activity logs─ Configured in Advanced db property → Unread Mark Options → “Replicate Unread Marks”

■ “Unread Log Playback”: Occurs when a user opens a database or clicks F9; Synchs the Unread Activity log with the Unread ID Table

■ “Modified Note ID Table”: tracks a list of modified documents in a database; Relevant to unread marks with respect to the db option in Design tab → “Do not mark modified documents as read”



Single Client – Multiple Replica■ User reads documents in replica on Server A■ Unread Journal tracks operations on the Notes client (cache.ndk)■ User opens replica of the database on Server B■ Journal operations applied to the Unread

table of replica B


Recent SPRs – The state of Unread Marks today

SPR #RMAS8HN2KV:

■ SYMPTOMS: in the middle of a view, a whole block of docs turns unread OR all docs could change back to unread unexpectedly; could happen in 1 db or multiple, or intermittently to different dbs

■ FOUND IN: 8.5.2FP2■ FIXED IN: 8.5.2FP4 and above; 9.x■ SOLUTION: Upgrade to 8.5.2FP4 or above■ WORKAROUND:

1) Go to "ALL Documents" view: View → Show –Unread Only2) Ctrl+A to select all unread documents3) Edit → Unread Marks → "Mark Selected Read"

*After this, all selected documents are marked read in all folders and subfolders*The issue does not seem to resurface in the same db after it is repaired


Recent SPRs – The state of Unread Marks today

SPR # DANG7UCHMJ

■ Background: REPL_SYNC_ALL_UNREAD=1 not working as expected; In larger Notes & Domino deployments, sometimes unread mark counts were losing synchronization across multiple replicas. The parameter did not resolve discrepancies as expected

■ Symptom: all documents marked unread■ Found in: 8.x■ Fixed in: 8.5.3FP1, 9.x■ Solution: Upgrade to 8.5.3FP1 or above■ Workaround: No known workaround while using the notes.ini parameter. Use

other methods to sync unread marks across replicas


Recent SPRs - The state of Unread Marks today

■ SPR # JPAI8ELRFN: Internal SPR related to new MMR feature and huge activity logs

■ Steps to reproduce: Large database with large unread log; Create “Managed Mail Replica” (MMR) for user; mark all read/unread several times in large db

■ Symptom: Replication issues; replication performance degradation ■ Found in: 8.5.2.x■ Fixed in: 8.5.3■ More info: Provides a new internal mechanism to purge the database unread log of

extremely large databases. The intent was to allow hugely bloated unread logs to be made a more manageable size by forcing a purge


Recent SPRs - The state of Unread Marks today

■ SPR # RMAS96PR2M: Fixed an edge case for DbGetModifiedNoteTable that resulted in too many documents being returned

■ Symptom: Random cases where small chunks of docs (10-200) would be appear unread again

■ Found in: 8.5.x■ Fixed in: 8.5.3FP5, 9.0.1■ Solution: Upgrade to Domino server 853FP5/9.0.1 or above ■ Workaround: Manually fix the documents in question


Troubleshooting Tools for Unread Marks1.) sh stat database.nsf.replicate.unreadmarks.*2.) new replica, other replicas, OR restored databases3.) (single db) DEBUG_UNREAD_DB=<full database path>4.) (for multiple dbs) DEBUG_UNREAD=

─ (Bit) Options include:

─ To debug multiple options, add the bit values together: EX: Debug_Unread=31─ Unused (1) + View Refresh Dump (2) + Repl (4) + Playback (8) + Unread Log mgmt (16)

5.) Notes client:─ “Exchange Unread Marks” tool─ DEBUG_LIMIT_UNREAD_JOURNAL=1

6.) REPL_SYNC_ALL_UNREAD=1 (client or server)7.) ADMINP_EXCHANGE_ALL_UNREAD_MARKS=1 (“source” server)8.) iNotes/Traveler: Tell commands for Domino http and traveler servers

9.) IBM Internal tools: dumpNSF and dumpUnread tools

1 = Unused 32 = Extreme logging

2 = Dump log on view refresh 64 = Log admin activity

4 = Log replication 128 = Purge logging

8 = Log playback 256 = OpBlock logging

16 = Unread log mgmt 512 = Debug for messages marked Read/Unread


Common Issues

■ All docs Marked as Read/Unread suddenly (today) for no apparent reason and without user interaction

■ Blocks or chunks of docs marked unread/read, without user interaction■ Recently received docs are marked as Read without user interaction■ Unread Marks not synchronized between multiple replicas of a database■ Unread Marks not synchronized between a Notes mail file and mobile device■ Unread Folder count is different between replicas or “off” for a single database■ Unread ID table or Unread Log corruption■ Extremely large database has trouble keeping up with Unread Marks Activity


Resolving Unread Mark issues:Information to gather in all Cases

1. What is the Exact version of the Domino server?─ Eliminate the obvious SPRs and known issues

2. Type of Client used: Notes client? iNotes? Mobile device? All 3?─ From multiple clients, does a different one exhibit expected behavior?

3. When did the issue first start?4. How widespread is the issue: some docs or all? One user vs multiple?5. Are multiple db replicas involved?

a.) Get specifics on which replica(s) has the issue, unread state of each;b.) Get connection doc settings, is this a clustered environment? PIRC-enabled?,

6. Any notes.ini parameters set in the client/server related to unread marks?7. Is the behavior reproducible at will? In a brand new database? In a new replica?8. Was the user recently renamed? LDAP authentication in use?9. If you switch id/log in as the user, from a different client, do you see same issue?10. What is the goal: Quick fix now or determine root cause?


Resolving Unread Mark Issues:Steps for all Situations

For all Notes/Domino Unread Marks issues, execute the following steps:1) Upgrade Domino server to 8.5.3FP5/9.0.1; all major unread issues resolved

● Eliminate the known issues that have been identified and fixed

2) Check/Set these Application properties in the database(s):a.) Advanced Tab: “Replicate Unread Marks” option – 'Never' or 'All servers' checkedb.) Design Tab: "Do not mark modified documents as unread" should be checked, if you want the read documents to stay read, after they are modified

3) Check time/date on clients and Domino servers, for accuracy/similarity4) Compare Username value of the Person doc against the authenticated user

(user.id, traveler, ldap, or http authenticated name) to ensure a match ● If they are different, there will be 2 different UnreadID tables – one for each username

5) (If multiple replicas): Verify Replication options and Disable the Unread Journal: a.) Basics tab: "Send documents to server" and "Receive documents from server" checked b.) Other tab: make sure the 'Temporarily disable replication' option not checked c.) Check db replication history to see if db has been replicating regularly/as scheduled d.) Disable the (client) unread Journal; use only of db unread activity log:

DEBUG_LIMIT_UNREAD_JOURNAL=1


Resolving Unread Issues: Single Database, Single UserTechnique #1: Toggle all docs Read/Unread Status

When to Use: single database; when a new replica not convenient; quick 1-time fixWhat this does: Removes all docs from unread ID table first, puts them backSteps: 1. Create two folders, Group1 (read) and Group2 (unread) 2. Go to the All Documents view 3. From the menu, select: Edit → Select All 4. If using a mail based design, click the Action Bar -> Folder -> Move to Folder -> select Group1 → Add

*For other dbs, drag the document collection to the Group1 folder in the left pane

5. Switch into the Group1 folder 6. From the menu, select View → Show → Unread Only

*Only the unread documents should appear

7. From the menu, select Edit → Select All 8. If using a mail-based design, click the Action Bar: Folder → Move to Folder, select Group2 → Move

*For other dbs, drag the document collection to the Group2 folder in the left pane.


Resolving Unread Issues: Single Database, Single User Technique #1: Toggle all docs Read/Unread Status (cont'd)

9. From the menu, select View → Show → Unread Only10. From the menu, select Edit → Select All11. From the menu, select Edit → Unread Marks → Selected Unread12. From the menu, select Edit → Select All13. From the menu, select Edit → Unread Marks → Selected Read14. From the menu, select Actions → Folder Options → Remove folder15. Switch to the Group2 folder16. From the menu, select Edit → Select All17. From the menu, select Edit → Unread Marks → Selected Read18. From the menu, select Edit → Select All19. From the menu, select Edit → Unread Marks → Selected Unread20. From the menu, select Actions → Folder Options → Remove folder


Resolving Unread Issues: Single Database, Single UserTechnique #1 : Toggle Some docs' Read/Unread Status

Variation 1: Toggle all currently unread docs to “Read” status1. Go to the All Docs view2. View → Show → Unread Only3. Edit → Select all, to highlight all docs4. Edit → Unread Marks → Mark All Read

Variation 2: Toggle all currently Read docs to Unread1. Go to the All Docs view2. View → Show → Read Only3. Edit → Select all, to highlight all docs4. Edit → Unread Marks → Mark All Unread

■ When to use variations: When a chunk of docs have incorrect status, single db.


Resolving Unread Issues: Single User, Multiple Replicas Technique #2: Notes client “Exchange Unread Marks” toolWhen to Use: 1-time Synch of unread marks between 2 replicas, and 1 replica has correct unread list; the user's Notes client is availableSteps: (Executed form the Notes client, user's machine in question) 1. From the Notes client workspace, unstack the replica icons 2. Select the “Source” (“good”) replica icon so it becomes highlighted 3. Hold the Shift key and select the “Target” replica. Both icons should be highlighted now 4. Edit → Unread Marks → Exchange Unread Marks

*It is advisable to create a backup of the “good” replica first*“Source” db = correct unread list. “Target” db = the one being fixed “fixing”. The order of selection is crucial.*Can be done with client and/or server replicas.*This only exchanges the unread marks for the user.id in question; thus, must be done from the user's workstation in question. Admin may do this for the user, if the admin has the user.id file. *Similarly, a SmartIcon may be created with the formula @Command([ExchangeUnreadMarks]), but you will still need to select the 2 icons


Resolving Unread Issues: Single/Multiple users, multiple replicas Technique #3: REPL_SYNC_ALL_UNREAD=1

When to use: Apply to Notes client or server (8.5.3FP1 or above), for 1-time synch of unread ID Tables for one or multiple databasesApplied to: “Source” server or client = the one with the accurate unread marks OR the server whose replication code should initiate the synching of unread marksNotes: resource intensive operation; triggers a full replication of all unread tables (not just latest updates); should be used sparingly; should never be constantly enabled on the Domino serverPossible Application/Steps:1) Enable the parameter dynamically: (Set config REPL_SYNC_ALL_UNREAD=1)2) Restart all Domino replicator tasks (restart task replica)3) Force replication of the db between source and target servers (or client-server)4) Wait for replication to complete5) Disable the parameter dynamically: (Set config REPL_SYNC_ALL_UNREAD=0)6) Restart replicator task

*Another option: Create different program documents to toggle this option on/off occasionally


Resolving Unread Issues: Single User, Multiple ReplicasTechnique #4: Replicate Manually First

When to use: multiple replicas; When 1 replica has correct unread marksSteps:1. In the source server, check/set Application properties → Advanced → Replicate unread marks → 'all servers' 2. Check the replication history of both replicas for inconsistencies or issues3. Clear replication history of both replicas, then re-replicate. Push from “source” (good) database to “target” (incorrect) db, and monitor4. If not resolved, add 'set config REPL_SYNC_ALL_UNREAD=1' to the “source” server, restart all replicator tasks, and initiate a push of the db again. Monitor both replicas. Issue resolved?5. If not, create a new replica:

a.) manuallyb.) via adminp with notes.ini parameter 'ADMINP_EXCHANGE_ALL_UNREAD_MARKS=1'

6. set config REPL_SYNC_ALL_UNREAD=0; restart replicator task *NOTE: REPL_SYNC_ALL_UNREAD=1 is valid on server or client; always disable after use


Resolving Unread Issues: Single user, Single/Multiple Replicas Technique #5: Other Notes Client Solutions

When to use: Notes client; Unread Folder count is off or Different between replicas

Steps (may use one, multiple, or all):1. Purge Deletion Stubs, close and reopen the database2. Empty the Trash Folder (mail databases) and force replication3. Run Full maintenance (fixup -f, compact -c, updall -R)4. On the workspace: Unstack icons, Remove “bad” icons from the workspace, then Compact the workspace. Reopen db replicas to re-add icons again.5. Delete cache.ndk file and restart Notes client; Remove desktop.ndk file from data, re-test6. Create a new Replica of the “incorrect” database, from the “correct” database7. Disable Unread Journal (client), restart Notes client, and collect client console.log:

DEBUG_LIMIT_UNREAD_JOURNAL=1 *this disables the journal for logged dbsconsole_log_enabled=1

8. Enable REPLICATOR_SYNC_UNREAD=h on the client (*h = number of hours) NOTE: client param, synchs unread IDTable, can negatively impact client replication

9. Open a new PMR and have IBM Support run the DumpUnread tool on the db


Resolving Unread Issues: Single/Multiple Users or Replicas Technique #6: Fixing iNotes Unread issues

When to Use: iNotes-only issuesNotes: iNotes uses Unread ID table, no journal; Unread Activity log for multiple replicas Steps:1. tell http show users2. Review the user's person doc, username field 3. Open the user's mail file in the Admin client or via browser. Make sure that the authenticated user name in step 1 matches the username and owner

─ If names are different, then the user has different unread lists for each authenticated name4. Is the user currently working off a secondary server replica (vs. primary)?

a.) Have the user open the primary db via the browser. Are unread marks the same?– If not, then we may be facing issue with replication of unread marks.

b.) Use Technique #1, 2, 3, 4, or 8 to resolve discrepancies between 2 replicas5. (8.x and 8.5.x) test in lite mode, if available Is the issue present in other modes? 6. If issue is not resolved, open PMR with IBM support, to run DumpUnread tool against affected database


Resolving Unread Issues: Single/Multiple Users or Replicas Technique #6: Fixing iNotes Unread issues


Resolving Unread Issues: Single/Multiple users or Replicas Technique #7: Fixing Issues with Mobile DevicesWhen To use: When a mobile device is in useNotes:

─ The majority of reported issues are caused by variations in authenticated usernames, or multiple usernames in the person document

─ Traveler: Unread replication is enabled for each user automatically by the IBM® Notes® Traveler server so that unread marks sync correctly with the device Uses the Domino APIs for determining Unread Status.

─ BES/RIM uses its own internal mechanism for maintaining unread marks. In the past, it pulled info from the Domino UnreadID Table and used it. NoteIDs only relevant in the current database, so this was not good for clustered environments. In recent releases, RIM has switched to using the UNID, since the UNID is uniform across all replicas

─ There are currently some limitations with Apple devices:a.) When a mail message has synched with the Apple device, it cannot be modified again. Any modifications on the server except for read/unread status changes do not sync with the mail on the deviceb.) Read/unread changes periodically do not synch from device to server with iOS versions prior to iOS5. If the change cannot be synched immediately, the device often "forgets" about the change and not synch it later


Resolving Unread Issues: Single/Multiple users or Replicas Technique #7: Fixing Issues with Mobile DevicesSteps:1. Upgrade to the latest Fixpack or Interim fix available for Traveler

853 UP2: Unread marks sometimes not synched to from Android to Server (LOLO71503)901 IF1: 'Traveler Access Rights' error if unread mark synching not enabled in mail file (LO77846)901 IF3 / 9001 IF4: Read Status for Calendar invitation not synched from Mobile device to Notes Client (LO77998)

2. Check database properties - replication of unread marks. Synching Unread Marks: http://www-10.lotus.com/ldd/dominowiki.nsf/xpDocViewer.xsp?lookupName=Administering+IBM+Notes+Traveler+9.0.1#action=openDocument&res_title=Enabling_syncing_of_read_or_unread_changes_A901&content=pdcontent

3. Is the user using an Apple device? If so, there are known limitations:http://www-10.lotus.com/ldd/dominowiki.nsf/xpDocViewer.xsp?lookupName=Using+IBM+Notes+Traveler+9.0.1#action=openDocument&res_title=Apple_limitations_and_restrictions_U901&content=pdcontent

4. Enhancement Request RSSN-8B7JTP: For Instant unread synch between client and device: http://www-01.ibm.com/support/docview.wss?uid=swg21666362

*By default, Traveler does not push unread-only updates to the device

http://www-01.ibm.com/support/docview.wss?uid=swg21666362


Resolving Unread Issues: Single/Multiple users, Multiple replicasTechnique #8: New ReplicaWhen to use: When it is convenient to create a new replica; newly created replicas does not have correct unread marks

Steps: Create a new replica for affected dbs: 1. In the source server, set:

all dbs' properties - advanced tab (via admin client) to replicate unread marks, 'all servers' Set config ADMINP_EXCHANGE_ALL_UNREAD_MARKS=1

2. Delete the "bad" replica on the destination server(s)3. Re-create the replica via adminp. Does this resolve the issue? 4. If not, Add 'set config REPL_SYNC_ALL_UNREAD=1' to the source server console, restart replicator task, then initiate a push for the 1 database, from source to target server5. set config REPL_SYNC_ALL_UNREAD=0


Resources

■ The Architecture of Unread Marks in Lotus Notes

■ The enhanced unread functionality in Notes/Domino

■ Open Mic Replay and Q&A: Understanding and Troubleshooting Unread Marks in Notes/Domino - 10 January 2012

■ Open Mic - Troubleshooting & Best Practices for Read/Unread Marks





http://www-01.ibm.com/support/docview.wss?uid=swg21588524&aid=1


Questions

Press *1 on your telephone to ask a question.

Visit our Support Technical Exchange page or our Facebook page for details on future events.

To help shape the future of IBM software, take this quality survey and share your opinion of IBM software used within your organization: https://ibm.biz/BdxqB2

IBM Collaboration Solutions Support page http://www.facebook.com/IBMLotusSupport

IBM Collaboration Solutions Supporthttp://twitter.com/IBM_ICSSupport

http://www.ibm.com/support/entry/portal/scheduled_tech_exchanges/software/lotus/lotus_brand_support_(general)

http://www.ibm.com/support/entry/portal/scheduled_tech_exchanges/software/lotus/lotus_brand_support_(general)

http://www.facebook.com/IBMLotusSupport


https://ibm.biz/BdxqB2


http://twitter.com/IBM_ICSSupport

Fixing Unread Marks in Notes/Domino Open Mic...When to Use: 1-time Synch of unread marks between 2...

Documents

Transcript of Fixing Unread Marks in Notes/Domino Open Mic...When to Use: 1-time Synch of unread marks between 2...