- Solutions
- Resources
- News
- Support
- About
Verification of replication software products for business continuity is critical and requires independent methods to ensure consistency between databases even while they are actively running.
| Product | Supported File and Table Types | Repair Available |
|---|---|---|
| Compare for Enscribe | All Key-Sequenced, Relative, and Entry-Sequenced Enscribe Files | No |
| Compare for SQL/MP | All Key-Sequenced, Relative, and Entry-Sequenced SQL/MP Tables | Yes |
| Compare for SQL/MX | All Table Types Supported | Yes |
| Shadowbase Blistering Fast Compare | Entry Sequence/Non-Key Databases | Yes |
Homogeneous Validation
Discrepancies may occur, for example, if either a disaster corrupts one of the databases or a user misconfigures the application or replication environment. Shadowbase Compare generates a report of table differences for like-to-like replication, i.e., Enscribe-to-Enscribe, SQL/MP-to-SQL/MP, or SQL/MX to SQL/MX data.
Read the Solution BriefShadowbase Compare is particularly useful in business continuity data replication environments to validate that a target database matches its source.
Verify consistency between HPE Nonstop source files/tables with heterogeneous targets. Shadowbase Compare Plus is built on the Shadowbase Compare engine and has all of the same features, including Shadowbase Repair.
Discrepancies may occur, for example, if either a disaster corrupts one of the databases or a user misconfigures the application or replication environment.
Shadowbase Compare Plus generates a report of table differences for non-like-to-like replication, i.e., HPE Nonstop to Linux or any other Shadowbase-supported non-Nonstop target.
| Requirement | Compare (BE445AC) | Compare Plus (BE497AC, BE498AL) pre-requisite: BE445AC |
|---|---|---|
| Business Continuity/DR architectures? | Yes | Required if DR has heterogeneous formats, available in release 4 |
| Data streaming architectures? | No | Yes |
| Support HPE Nonstop (NS) and Other Servers (OS)? | NS Only | Yes |
| Support comparing data that was transformed? | No | Release 1: similar datatypes Release 2-4: moderate transformation supported |
| App can remain online? | Yes | Yes |
| Works with any replication product & architecture? | Yes | Yes |
| Audited vs. unaudited DBs/files? | Yes | Yes |
| Enscribe vs Enscribe comparisions? | Yes | Not Required |
| Enscribe file types? | All | Release 4: yes |
| Exclude specific Enscribe fields? | In-plan for a future release, not currently available | In-plan for a future release, not currently available |
| SQL/MP table types? | All | All |
| SQL/MX table types? | All | All |
| Exclude specific SQL/MP and SQL/MX columns? | Yes | Yes |
| Repair mismatches? | Yes (Enscribe is in-plan for future) | Yes (Enscribe is in-plan for future) |
| Wildcarding? | Yes | Yes |
| Expand? | Yes | N/A |
| TCP/IP? | Yes | Yes |
| Parallelism and high volume? | SQL/MP & SQL/MX: automatic Enscribe: manually via key ranges and parallelism | SQL/MP & SQL/MX: automatic Enscribe: In-plan for a future release, not currently available |
Mismatched data
This situation occurs when the tables being compared in the source and target databases have the same primary keys, but their data values differ. Shadowbase Repair can use the values in either the source or target table row to make the data in both tables consistent (match).
Extra or missing data
This situation occurs when a row of data is missing in either the source or the target table. To correct the issue, Shadowbase Repair can either insert or delete values from either table to make both tables consistent.
The user can automatically and quickly correct these discrepancies with just a few simple commands. The user has full control over selecting which table is considered to be correct (referred to as the source table) and which table is considered incorrect (referred to as the target table).
Read the Solution Brief
Copy link to clipboard
Email link
Print