NextGenSoftware.OASIS.API.Providers.OracleDBOASIS 2.0.3

There is a newer version of this package available.
See the version list below for details.
dotnet add package NextGenSoftware.OASIS.API.Providers.OracleDBOASIS --version 2.0.3
                    
NuGet\Install-Package NextGenSoftware.OASIS.API.Providers.OracleDBOASIS -Version 2.0.3
                    
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="NextGenSoftware.OASIS.API.Providers.OracleDBOASIS" Version="2.0.3" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="NextGenSoftware.OASIS.API.Providers.OracleDBOASIS" Version="2.0.3" />
                    
Directory.Packages.props
<PackageReference Include="NextGenSoftware.OASIS.API.Providers.OracleDBOASIS" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add NextGenSoftware.OASIS.API.Providers.OracleDBOASIS --version 2.0.3
                    
#r "nuget: NextGenSoftware.OASIS.API.Providers.OracleDBOASIS, 2.0.3"
                    
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
#:package NextGenSoftware.OASIS.API.Providers.OracleDBOASIS@2.0.3
                    
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.
#addin nuget:?package=NextGenSoftware.OASIS.API.Providers.OracleDBOASIS&version=2.0.3
                    
Install as a Cake Addin
#tool nuget:?package=NextGenSoftware.OASIS.API.Providers.OracleDBOASIS&version=2.0.3
                    
Install as a Cake Tool

NextGen Software WEB4 OASIS API Oracle Database OASIS Provider

WEB4 OASIS API Oracle Database OASIS Provider is one of the many WEB2/WEB3 providers that plug in and integrate into the OASIS.

This provider uses the real Oracle.ManagedDataAccess.Core client with indexed lookup columns and canonical JSON records in CLOBs. It targets Oracle Database, including applicable OCI-hosted database services; it does not implement OCI Object Storage. Hosted service, wallet/IAM and full interface acceptance must be verified separately.

Configuration and verification

For provider-scoped public read catalogues, query-only host enrollment, supported HTTP shapes and remaining demo gates, see the Oracle CQL host guide.

Hosted query activation uses ICosmicReadOnlyQueryActivation.ActivateQuerySourceAsync. It opens the configured existing database and reuses canonical schema validation; it never provisions or repairs tables. Missing/incompatible schemas fail with CQL_QUERY_SOURCE_UNAVAILABLE, cancellation with CQL_QUERY_CANCELLED, and either failure clears activation state. Ordinary explicit storage activation retains its separate schema-setup contract. Query activation does not grant record access or enroll Oracle into a host's writable routes.

The retained local read-only probe is Scripts/TestHosts/Test-OracleQueryActivation.ps1: after producer/test builds, run through the provider build lease. It reuses the existing original Oracle container/secret/source and verifies unchanged schema and four source records before/after activation. It stops the runtime only if it started it. Hosted connectivity, authoritative access policy and public presets remain separate acceptance gates; local native success is not hosted readiness.

Record-history parsing reuses the existing shared canonical JSON parser, preserving date-shaped metadata strings and high-precision untyped JSON numbers at latest and historical versions. It does not reinterpret metadata as local dates or narrow numbers through binary floating point. This does not reconstruct values already altered by an older stored write.

Successful storage reads set IsLoaded=true. Point reads count one returned record; collection/export reads count returned roots, not recursively nested children. A successful empty collection has LoadedCount=0 and remains loaded. Search counts its returned avatar/holon roots. Missing-record and failed reads do not claim loaded records. These response annotations do not change the query, persisted data, logical history or encryption policy.

ExportAllDataForAvatarByUsername and ExportAllDataForAvatarByEmail resolve the current avatar identity; their version selects exported holon roots, not the avatar's independent history. Use the current username/email even when exporting an older holon version. Linked children retain independent versions. Explicit LoadAvatarByUsername/LoadAvatarByEmail with a version still select avatar history, including historical identity fields; that separate contract is unchanged. Export version 0 selects current roots, positive values select that stored root version, and -1 enumerates flat nondeleted stored versions without hydrating child navigation. Canonical stored JSON excludes navigation; stored relationship manifests are not a point-in-time graph snapshot. Owner filtering applies to each exported version. Values below -1 are rejected before identity storage reads. Ordinary non-export reads still reject negative versions.

Avatar-scoped exports require a nonempty avatar GUID. Current/positive-version outputs include only descendants owned by that avatar, not foreign public/private branches; unscoped ExportAll remains independent. SearchOnlyForCurrentAvatar likewise filters entire returned graphs. These detached output projections retain stored relationship observations so a filtered graph cannot silently replace hidden stored membership. They do not replace API authorization or native access controls.

Holon deletion sets IsDeleted=true and DeletedCount=1 only after an acknowledged commit. Repeating a soft delete on an existing inactive tombstone acknowledges that state with DeletedCount=0 and no new mutation. An uncertain commit does not claim deletion success or a count. The provider's boolean soft/hard-delete helpers preserve the native operation's result metadata through the existing result-copy helper. The IOASISStorageProvider.DeleteHolon GUID/provider-key, synchronous/asynchronous aliases perform hard deletion, matching HyperDrive's shared dispatch contract. HolonManager implements soft deletion through a tombstone Save; direct provider callers can explicitly select it with DeleteHolonWithSoftDelete*(..., true).

Known point-read or delete-target absence uses OASISResultErrorCodes.RecordNotFound with no payload or native exception. Direct reads retain an unloaded error result; absent deletes do not acknowledge mutation, increment deletion counts or commit. V2's existing manager layer can distinguish that state from an outage and honor explicit allowMissing behavior, including first-use settings/karma ledger creation. Malformed keys, invalid versions, corrupt records and native failures are not relabeled as absence. Empty collection reads retain their normal successful-empty semantics.

Identity column compatibility

USERNAME and EMAIL in OASIS_AVATARS and OASIS_AVATAR_DETAILS require explicit character length semantics with capacity of at least 256 characters. New tables use VARCHAR2(256 CHAR). Existing byte-semantic identity columns fail activation with a provisioning-review error; activation does not silently alter them or change the database character set.

Before upgrading an existing schema, have its DBA inspect data lengths, character representability, indexes and maintenance requirements. Do not blindly narrow wider columns. Oracle DDL commits independently, so a schema change is not an ordinary rollback-safe data transaction. The guarded local empty-test-schema procedure is not a general production migration. Unicode acceptance was tested on AL32UTF8; other database character sets and hosted configurations require their own verification.

Write outcomes

An original ORA-12899 returned by the canonical DML statement before its row acknowledgement is an explicit capacity rejection, retaining the original Oracle exception. A matching error number after DML acknowledgement is not treated as proof of rejection: commit/transport uncertainty still requires reconciliation before replay. Rejected work can consume database resources even when it commits no record.

Connection settings

Configure OASIS.StorageProviders.OracleDBOASIS.ConnectionString through the host's secure configuration. IsVersionControlEnabled defaults to false; enabling it creates version archives. Existing archives are preserved when creation is disabled. Historical profile reads do not authorize historical credentials: verification/reset/refresh token selectors require version zero.

Activation first checks the six required table names in the current owner's USER_TABLES, using the same schema definitions as validation. If all exist, activation validates their column and primary-key invariants without entering provisioning or issuing DDL. Secondary tuning indexes are not silently recreated or certified on this path; a DBA should review their suitability. This adds one catalog query per activation, not per record operation.

Additional user-declared columns, including invisible columns, must permit the provider's explicit INSERT column lists: nullable, defaulted, identity-generated or virtual columns are accepted; a required stored extra column without a default is rejected before activation succeeds. This is structural admission, not proof that arbitrary default expressions, triggers or extra constraints will succeed for every input. Activation never repairs the schema. System-generated hidden columns are excluded from this user-schema check.

Every required table must be permanent (TEMPORARY=N, DURATION null). Validation reads these flags in the existing column-metadata query; it does not issue another query, convert temporary tables or alter their data. Session/transaction-scoped tables are rejected because they do not provide persistent storage across provider connections. See Oracle's table metadata definitions.

If any table is absent, the existing initialization path still creates missing tables/indexes before validating. Use only a database/schema where that provisioning is explicitly authorized; Oracle DDL is not an ordinary rollback-safe data transaction. A validation-only activation is not proof that a particular least-privilege account can perform every storage operation. Real SQL tests reuse one retained local Oracle Free instance; they do not certify hosted Autonomous Database or every provider/HyperDrive interface. Current scoped evidence and remaining gates are tracked in the working verification report.

Separate schema provisioning from application access. A pre-provisioned schema can activate without CREATE TABLE: the local permission fixture verifies effective CREATE SESSION only, no roles, unchanged table identities, and avatar/detail/holon saves, indexed lookups and deletion. The schema owner has implicit access to its own tables. This is scoped local evidence, not a blanket privilege prescription for every operation or Autonomous/IAM configuration. The local fixture uses one passwordless schema-only identity through an administrator-authenticated proxy; that test setup is not a recommendation to give production applications administrator credentials. Have the DBA provision/review the intended application schema and cloud authentication separately.

Initial Release targeting OASIS API v2.0.0:
https://api.oasisweb4.one

Full documentation and source code can be found here:
https://github.com/NextGenSoftwareUK/Our-World-OASIS-API-HoloNET-HoloUnity-And-.NET-HDK

Make sure you check out the Overview and Benefits Of Building On The WEB 4 OASIS API sections above! 😃 Thank you!

Product Compatible and additional computed target framework versions.
.NET net10.0 is compatible.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (1)

Showing the top 1 NuGet packages that depend on NextGenSoftware.OASIS.API.Providers.OracleDBOASIS:

Package Downloads
NextGenSoftware.OASIS.OASISBootLoader

The OASIS BootLoader provides a single entry point to initialise the entire OASIS ecosystem in any .NET application. Reads OASISDNA configuration, registers and activates all configured providers, sets up Auto-FailOver/LoadBalancing, and returns a ready-to-use OASIS instance. Integrate 55+ decentralised networks into your app with just a few lines of code. Part of the OASIS Omniverse at https://oasisomniverse.one

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
2.0.4 152 11/14/2026
2.0.3 142 11/14/2026
2.0.2 106 10/13/2026
1.0.0 107 9/28/2026

NextGenSoftware.OASIS.API.Providers.OracleDBOASIS v2.0.3

Connects the OASIS to Oracle Database — the world's most widely used enterprise RDBMS. Stores OASIS holons and avatars using Oracle.ManagedDataAccess.Core with indexed lookup columns and full JSON serialisation via CLOB. Compatible with Oracle Database 12c+ and Oracle Autonomous Database. Part of the OASIS HOT-Swappable Provider Architecture. Ecosystem: https://oasisomniverse.one/

What's new since v2.0.2
- Add explicit public S3 metadata CQL source and recover Oracle query adapter (64c0d94)
- Align Oracle empty metadata filters and validate match modes before IO (d3b84d0)
- Bind Firestore acknowledgement counts and reconcile null Oracle writes (cc941f6)
- Bind Oracle CQL authorization and discovery to provider-scoped host catalogues (5c5f913)
- Converge Oracle compatibility reads on canonical version and graph owner (b9358af)
- Delete Oracle avatar and detail atomically with canonical tombstones (4d37260)
- docs(oracle): record published Core native compatibility verification (0dcf6ca)
- feat(oracle): export all validated record history versions (c7fd876)
- feat(oracle): serialize protected preparation claims with conditional receipts (eb16e24)
- fix: discover Oracle cloud storage and verify interface options (cec5cbe)
- fix: keep Oracle avatar exports within owned descendants (81e06b9)
- fix: preserve Oracle post-acknowledgement commit uncertainty (64ce268)
- fix: protect Oracle and shared scoped search descendants (a7b6d7a)
- fix: reject unwritable Oracle generated canonical columns (92a0ae9)
- fix: validate Oracle deletes and reuse retained provider lifecycles (54d982c)
- fix(oracle): acknowledge successful storage reads and root counts (47c167d)
- fix(oracle): capture metadata scope before database reads (15155f5)
- fix(oracle): classify absent records for durable V2 karma bootstrap (950ea2e)
- fix(oracle): count selected parent edge in graph depth (a0bfb37)
- fix(oracle): distinguish provider configuration from invalid delete payloads (8487b31)
- fix(oracle): distinguish statement rejection from commit uncertainty (b1422e7)
- fix(oracle): do not report tombstone observation as a save (e7d37dc)
- fix(oracle): honor shared hard-delete dispatch contract (ee1164a)
- fix(oracle): own canonical search request before SQL awaits (8d1f69b)
- fix(oracle): persist planned child roles under native write locks (576d53b)
- fix(oracle): preserve exact metadata scalars through record history (81f73ae)
- fix(oracle): preserve identity character capacity and guard local provisioning (af5e6d6)
- fix(oracle): preserve known delete absence and retire all karma test projections (83849a3)
- fix(oracle): preserve truthful deletion acknowledgements across aliases (348fb03)
- fix(oracle): reject missing native audit timestamp defaults (f05ea2c)
- fix(oracle): reject nonpersistent storage table schemas (43300c6)
- fix(oracle): reject unwritable extra columns during schema admission (87ae58e)
- fix(oracle): report acknowledged avatar deletion outcomes (5e52504)
- fix(oracle): retain known save acknowledgements across publication failures (16c9587)
- fix(oracle): select export identity independently of holon history (bacbde8)
- fix(oracle): select null-parent roots consistently across versions (a791eee)
- fix(oracle): validate avatar deletion and prove native identity contention (63bbba8)
- fix(oracle): validate complete schemas without provisioning DDL (e9e0a7b)
- fix(oracle): validate existing storage columns before activation (bbf71a2)
- fix(oracle): validate holon projections before history and deletion filters (953bac2)
- fix(oracle): validate native identity and conditional receipt primary keys (fe700bf)
- fix(oracle): validate point selectors before SDK connection access (c2fc8db)
- fix(oracle): validate required nullability and numeric and text capacities (5b1ea47)
- fix(providers): share validated conditional acknowledgement assembly (b88181d)
- fix(storage): scope historical embedded graph exports by owner (0422e00)
- Guard Oracle acknowledged publication against observed caller edits (f408102)
- Guard Oracle identity admission and preserve listener failure controls (9cace82)
- Guard Oracle named binding and pre-dispatch caller state (025d7ae)
- Implement and verify Oracle standalone avatar-detail lifecycle (7c8f085)
- Implement and verify read-only Oracle query source activation (9e3f7b2)

Full changelog
https://github.com/NextGenSoftwareUK/OASIS/commits/master/Providers/Storage/NextGenSoftware.OASIS.API.Providers.OracleDBOASIS