DOCUMENTATION BASIS
Product knowledge, reorganized for enterprise evaluation.
This website uses the complete Halo 1.0.16 user-manual Markdown set as its primary product source, then reorganizes that knowledge around customer questions rather than reproducing the manual chapter by chapter.
What belongs where
| On this website | In technical documentation |
|---|---|
| Product positioning and capability | Exact commands and syntax |
| Architecture and topology concepts | Installation and CLI procedures |
| Compatibility scope and boundaries | SQL, DDL, DML, and language examples |
| Migration and operational value | Configuration files and parameter values |
| Evidence limits and evaluation questions | Terminal output, logs, and troubleshooting steps |
The source families behind the site
Product and architectureChapters 1–2
Product origin and release history, instance/cluster architecture, transactions, storage, indexes, partitioning, and database objects.
Deployment and tuningChapters 3–6
Documented processor and operating-system families, installer workflow, initialization, character sets, and configuration surfaces.
CompatibilityChapters 7–10
E5, multiple operating modes, and Oracle, MySQL, and native PostgreSQL behavior and boundaries.
Backup and availabilityChapters 11–15
Protection models, RMAN2, physical/logical/grouped replication, and Halo Shield.
Distributed capabilitiesChapters 16–19
DLB, TWR, HSM, and HDS architecture and operational boundaries.
Operations and toolingChapters 20–22
Resource controls, HWR, Statement Sharing, and DBeaver.
Reference inventoriesAppendices A–G
SQL object families, RMAN2 scope, system catalogs/views, 45 extensions, structured errors, compatibility additions, and Shield cluster operations. Syntax and commands are excluded from the site body while the capabilities they prove are retained.
Frozen source snapshot used for this refactor
- 80Markdown files
- 40,934source lines
- 14,502nonblank non-code lines
- 80/80hash matches
- Every file matched the source map at the implementation freeze.
Before relying on a documented capability
- Confirm the exact Halo version and build
- Confirm the operating mode and optional modules
- Separate capability description from configuration example
- Preserve stated limitations and prerequisites
- Validate the requirement with the intended application and topology