Oracle Analytics Server 2025 – Solved: remoteConnection=false Fix for JDBC‑HANA Deployment

techlover

Product Environment

• Oracle Analytics Server (OAS) 2025, on‑premise
• Semantic Model built via Model Administration Tool using JDBC HAA connection.

Issue Encountered
When attempting to deploy a fully defined Semantic Model (with variables) to the catalog, I received:

Invalid connections detected in Connection pool:connectionPool:HANADB.SAPHANADB : Remote Connection property does not match the Remote Data Connectivity connection.

The physical-level preview worked fine, but deployment failed repeatedly.

Root Cause Diagnosis
OAS 2025 does not support Remote Data Connectivity for JDBC‑based HANA connections. Enabling the Remote Connection checkbox (or "remoteConnection": true in the SMML JSON) caused the modeler to look for a matching RDG connection, which doesn’t exist in this deployment model. As documented:

“If the database uses remote data connectivity and this field [Remote Connection] isn’t selected then you'll receive an error when you run consistency check” (Oracle Docs)

And per the SMML schema definition, the default for "remoteConnection" is false, and the deployment engine enforces this in consistency validation (Oracle Docs).

Solution Implemented

1. In the Semantic Model JSON (.smml), locate each ConnectionPool section.
2. "remoteConnection": false(instead of true or leaving it unset).
3. Save and re-upload the model. Deployment passed successfully afterward.

Why This Works

• Preview and variable init blocks use the Connection property only—not Remote Connection—so they still function.
• Consistency check during deployment enforces the remoteConnection flag when no RDG is defined, leading to failure unless the flag matches reality. Setting it to false bypasses the RDG logic.

✅ Best-Practice Recommendations & Caveat

Keep in mind…	Why this matters
Only use this approach in OAS 2025 on‑prem	Future versions or Oracle Analytics Cloud support RDG/HANA; "remoteConnection": true will be required
Version control your SMML	Re-syncing from Git or clients may revert the flag unintentionally
Document this fix	Post as comment or answer your own question, so that others benefit and you gain reputation in the Oracle Community forum (community.oracle.com)
Don’t share sensitive data	In the post, avoid IPs, hostnames, credentials, or internal usernames

📝 Final Note

This resolution aligns with the guidance that selecting the Remote Connection property without a corresponding RDG backend causes model validation to fail. Since JDBC‑HANA in OAS 2025 does not rely on Remote Data Connectivity, explicitly clearing that flag makes deployment work as intended.

If Oracle releases an update to enable RDG‑based HANA support in OAS later, you’ll need to revisit this and switch the flag back to true, provided the RDG connection name matches exactly.

Glad to share this workaround—feel free to ping me if anyone needs more detail!