Knowledge, Architecture
& FAQs
Explore architectural references, security compliance briefs, and answers to common technical questions regarding QwikARC deployment and EBS data conversion.
QwikARC Product Overview Datasheet
Comprehensive summary of Oracle EBS historical data preservation, screen preservation, subledger drill-downs, and commercial adoption model.
Client AWS Deployment Architecture
In-depth specification for deploying MySQL on EC2, configuring AWS Secrets Manager, least-privilege IAM policies, and VPC network segmentation.
Qwik PI Certification Checklist
The mathematical reconciliation gates: 100% row count audits, schema validation, relationship integrity checks, and financial control totals.
Frequently Asked
Questions
Does QwikARC alter our current production Oracle EBS database?
No. During both the rapid POC and standard production deployment, QwikARC connects strictly via read-only SELECT database privileges. Zero schema alterations, zero database packages, and zero application triggers are placed in your EBS database.
What happens to our historical data if we end our subscription?
You retain permanent ownership of the entire MySQL relational archive, all AWS EC2 and EBS storage infrastructure, access credentials, and backups. QwikARC enforces zero vendor lock-in; your historical data remains in an open, industry-standard relational database that you own forever.
Can we run QwikARC on-premise instead of AWS?
Yes. While the standard architecture runs inside your client-controlled AWS account, QwikARC supports on-premise Linux virtual machine deployments (e.g., VMware vSphere or Nutanix) for organizations with strict data residency policies.
How does Qwik PI certify data completeness?
Qwik PI serves as an automated pre-migration validation gate. It executes automated 1:1 row count reconciliation across all archived tables, verifies foreign key referential integrity, and calculates financial debit/credit control totals against your trial balance to certify 100% accuracy.