Powerful solutions for difficult IBM Notes database problems

From being locked out of templates thanks to a previous developer hiding it, to dealing with mysteriously resurrected documents, there are a plenty of ways that problems can arise in your IBM Domino environment. What's important is how you deal with them. But, unfortunately, there are problems that the native toolkit just doesn't provide the tools to fix, at least in any practical way.

scanEZ offers unmatched ease in dealing with a range of database problems that normally grind workflow to a halt thanks to built-in tools and superior data handling.

Find and fix a wide range of database issues—from the simple to the serious—without any need to code.

Unlock the hidden design flag

Unlock the hidden design flag

Toggle the hidden design flag on/off, quickly and easily.

Bust "ghost" documents fast

Bust "ghost" documents fast

Find "ghost" (resurrected) documents within any given database in only a couple of clicks.

Simulate replication to proactively solve problems

Simulate replication to proactively solve problems

Run an accurately modeled replication simulation to uncover and solve problems before they hinder your environment

Hide/Unhide Hidden Designs

Unlock the hidden design flag

If your environment is like most, a lot has gone into application development. These investments are meant to last, but have you ever had to work on designs in a database whose template wasn’t available thanks to a previous developer's hiding it?

Maybe you yourself have wanted to prevent other users from opening a database in the Designer client, without going through the trouble of encrypting formulas and removing LotusScript source code. Hiding the design of a database can be helpful in the latter case, but a very big problem in the former.

scanEZ gives you a unique power over this situation, by letting you toggle the hidden design flag on/off. 

Manage the Hidden Design flag easily through powerful options unavailable in LotusScript.

Manage the hidden design flag

Regain control over your company's database designs.

Hide designs quickly and easily

Put your designs in a "read-only" mode in only a couple clicks.

Finally get a handle on hidden designs, and without having to write a single line of code.

scanEZ's Design Collection screen, with the option to work with the hidden design flag
Use #57

Unhide the design of any Notes database in only two clicks.

Like many adminstrators and developers, there may come a time where you need to unhide a database's design. scanEZ has helped numerous people make quick work of this. Why? Because in scanEZ it's only a question of two clicks to hide or unhide a design.

Busting Ghost Documents



Bust "ghost" documents fast

We've all experienced the startling mystery of previously deleted documents returning to your databases. [Not sure? Look at this blogpost explaining the symptoms and mechanics of document resurrection.] These resurrected documents often cause a great amount of confusion: you can clearly see they're back, but how do you identify them all? What's more, how can you know who brought them back?

With the number of documents that can be involved sometimes, where do you begin?

Detect troublesome and pesky resurrected documents through tailor-made tools.

When documents get resurrected finding out which ones to act upon acting upon them is a troublesome prospect in the native toolkit. With scanEZ’s Post-Replication Auditor, you’ll never have to look back to the old process.

Uncover "ghost" documents

Find all possible "ghost" documents withing a given database in only a couple clicks.

Easily organize your analysis results

Organize your analysis results by criteria such as resurrection status, sequence number, 'Created (Initially)' date, etc. all in a one feature-rich interface.

Effortlessly bust pesky "ghost" documents, and find the culprit who brought them back.

scanEZ's Post-Replication Auditor tool showing possible Ghost documents and the ability to copy UNIDs to clipboard
Use #38

Quickly identify and track resurrected "ghost" documents along their journey across servers.

The issue of resurrected documents has been an issue for as long as Notes has existed. The good news is that scanEZ has a built-in tool that specializes in identifying these annoying instances: the Post-Replication Auditor. But wouldn't it be great if you could not only find them, but also find out who created them? Using the combo of replicationEZ and scanEZ together with a little know how, this is easy to do. Here's how.

Replication Divergence Detection

Simulate replication to proactively solve problems

Figuring out what really makes two databases different is extremely challenging. And understanding what is causing those differences is even more difficult.

If you ever need to do this, we’ve got you covered.

scanEZ lets you see beyond a mere replication history for a completely unique and detailed view point thanks to a dedicated too based on an accurate model of the IBM Notes and Domino replication engine.

Fully expose the relations between a given database and one of its replicas—without needing to tamper with and clear the replication history.

Simulate replication to uncover and analyze the truth behind the relationship between two replicas.

Reveal complex replication scenarios and details:

Combine all this with the ability to report your results quickly through two-click, pre-formatted export options, and you have an insight into replication that just isn’t possible in the native IBM Notes toolkit or even in other third-party tools.

See the replication winner

If a document or design exists in both databases, but needs to be updated in one of them—instantly see which version will “win out.”

ID replica discrepancies

If a document or design should be created in another replica—see towards which database they need to be created and easily ID the documents or designs that don’t exist in the other replica.

See if you need to delete documents or designs in one of the replicas.

See if conflicts will be created or documents/designs that have been edited in both replicas since the last replication.

Prevent document deletion in other replicas by removing deletion stubs directly from within the Replication Auditor.

Compare replicas to prevent conflicts, or remove unwanted conflict documents.

Uncover replication problems before they happen.

scanEZ's Replication Auditor tool, comparing a document across two replicas to see what will happen if replication occurs
Use #14

Resolve conflicts before they even happen.

The built-in Replication Auditor gives you a glimpse at what will happen when replication occurs. But where does that leave conflicts? With the Replication Auditor, you get a clear vision of what conflict documents will be created. This lets you deal with them before they happen. Compare them to decide if you need to delete, for a clean replication all around.

Share |