Oracle Connection

Oracle Connection Skill

On Entry

Tell the user:

Setting up Oracle connection — I'll configure and test a connection to your source Oracle database. This requires a driver download on first use.

Prerequisites

• Network access to the Oracle database instance
• Oracle credentials (username/password)
• The scai CLI installed and available
• The Oracle .NET driver NuGet package (Oracle.ManagedDataAccess.Core.nupkg) — not the JDBC driver — see Step 1

Required Connection Details

Workflow

Step 1: Provision the Oracle Driver

The required driver is the Oracle.ManagedDataAccess.Core NuGet package. Resolve it by following the canonical bootstrap flow:

Driver bootstrap: see ../references/driver-bootstrap.md with parameters <dialect>=oracle, <package>=Oracle.ManagedDataAccess.Core, <driver_file>=Oracle.ManagedDataAccess.Core.nupkg, <cache_dir>=~/.snowflake/scai/drivers/oracle/, <nuget_url>=https://www.nuget.org/api/v2/package/Oracle.ManagedDataAccess.Core.

That doc walks through cache check → ask-on-miss → user-provided path or download → first SCAI invocation with --driver-path if needed. Follow it silently — don't narrate "the bootstrap flow" or step labels to the user.

Naming guard: the driver is a .NET NuGet package, not a JDBC driver. Refer to it only as "the Oracle driver" or "the Oracle NuGet package" when talking to the user.

For this skill specifically, the first SCAI invocation called out by the bootstrap is the configure tool call in Step 4 below — pass driver_path=<PATH> there if the driver wasn't already cached. The MCP server invokes scai connection test --driver-path <PATH> internally, which seeds the driver cache.

Step 2: Ask How to Provide Credentials

Ask the user:

"I need the following to connect to Oracle:

• Host (hostname or IP)
• Service name
• Username and Password

How would you like to provide these?"

Options:

1. Enter manually - Provide values interactively

Step 3: Add the Connection (Manual Entry)

Interactive mode (recommended):

scai connection add-oracle

Inline mode:

scai connection add-oracle \
  -c <CONNECTION_NAME> \
  --auth standard \
  --host <HOST> \
  --port 1521 \
  --service-name <SERVICE_NAME> \
  --user <USERNAME>

Password will be prompted securely.

Step 4: Save and Test Source Connection

This is the "first SCAI invocation" called out as 1e in the bootstrap reference. Use the path resolved in Step 1.

Call the configure tool with source_connection set to <CONNECTION_NAME>. The MCP server runs scai connection test internally and only persists the connection if the test passes.

• First use (driver not yet cached): also pass driver_path=<PATH_TO_NUPKG>. The first call copies the driver into ~/.snowflake/scai/drivers/oracle/, so every subsequent configure call (in this project or any other) can omit driver_path.

  configure(source_connection=<CONNECTION_NAME>, driver_path=<PATH_TO_NUPKG>)
  

• Driver already cached: omit driver_path.

  configure(source_connection=<CONNECTION_NAME>)
  

• On success: the response includes connection_test: ok.

• On failure: the tool returns an error containing the scai message. Surface it to the user, help them fix the issue, then re-run configure(...). See ./references/REFERENCE.md for detailed troubleshooting.

Common errors:

CHECKPOINT

Confirm with user:

• Oracle driver resolved via one of:
  • Already cached in ~/.snowflake/scai/drivers/oracle/ (Step 1a)
  • User-provided local path supplied via driver_path (Step 1c)
  • Downloaded by the agent and supplied via driver_path (Step 1d)
• configure returned connection_test: ok
• Connection appears in scai connection list -l oracle --json
• Source connection saved to session config

On Completion

After the CHECKPOINT passes, tell the user:

Connection configured — Successfully connected to Oracle using connection <connection_name>.

Then return to the calling skill.

Security Rules

• NEVER log or display passwords in plain text
• NEVER include passwords in command-line arguments that might be logged
• Use interactive mode to avoid password exposure

Quick Reference