Oracle AI Database supports AI workloads where you query data by meaning (semantics), not just keywords. It combines semantic search over unstructured content with relational filtering over business data in a single system, so you can build retrieval workflows (like RAG) without introducing a separate vector database and fragmenting data across multiple platforms. This guide demonstrates how to useDocumentation Index
Fetch the complete documentation index at: https://langchain-5e9cc07a-preview-mdrxyo-1777658790-7be347c.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
OracleVS (the LangChain vector store integration for Oracle AI Vector Search) to:
- Ingest documents and embeddings into Oracle
- Run similarity search
- Create HNSW and IVF indexes
- Apply metadata filters for advanced retrieval
- Enable hybrid search (keyword + semantic) in Oracle AI Database 26ai
- Run full-text search using Oracle Text
Overview
Integration details
| Class | Package | Hybrid search | PY support |
|---|---|---|---|
OracleVS | @oracle/langchain-oracledb | ✅ | ✅ |
Setup
Install Oracle client bindings and the LangChain Oracle helpers:Create a vector store
The example below assumes that you already created a table with vector and metadata columns and generated embeddings usingOracleEmbeddings.
OracleVS. The store acquires and releases connections as needed.
Filter search results
You can pass rich metadata filters as the third argument tosimilaritySearch, similaritySearchWithScore, or similaritySearchVectorWithScore. Filters operate on the JSON metadata column that Oracle VS maintains for each document.
Supported comparison operators include $eq (default), $ne, $lt, $lte, $gt, $gte, $in, $nin, $between, and $exists. Combine clauses with $and and $or to build more expressive predicates.
Accelerate search with vector indexes
Oracle Database can speed up similarity queries by creating vector indexes on theembedding column. The @oracle/langchain-oracledb helpers expose a createIndex utility that provisions either HNSW (default) or IVF indexes.
HNSW index (default)
Use HNSW when you want a graph-based index that balances recall and latency. OmitidxType to use the default configuration or override parameters such as neighbors, efConstruction, and accuracy.
IVF index
Switch to IVF by passingidxType: "IVF" along with the number of neighbor partitions to create. IVF partitions vectors into clusters and is useful when you want coarse quantization with predictable memory usage.
createIndex once after loading data (or after initialize) and reuse the index for subsequent searches. To rebuild or swap strategies, drop the existing index through standard SQL (DROP INDEX ...) and rerun createIndex with new parameters.
Next steps
- Load content with
OracleDocLoader - Generate embeddings with
OracleEmbeddings - Summarize documents using
OracleSummary
Connect these docs to Claude, VSCode, and more via MCP for real-time answers.

