Setting up OracleDB
1. Add integration
Select OracleDB from the integrations page.2. Configure settings
Connect using either a form or a connection string.- Form
- Connection string
Fill out the form with the following settings:
| Setting | Required | Description |
|---|---|---|
| Name | ✓ | Name that will be displayed to users when selecting this integration in Superblocks |
| Host | ✓ | Hostname or IP address of the Oracle database server |
| Port | ✓ | Port to use when connecting to Oracle (default: 1521) |
| Service Name | ✓ | Oracle service name to connect to |
| Database Username | ✓ | Username to use to connect |
| Database Password | ✓ | Password for database username |
| Enable SSL | ✗ | Connect using SSL/TLS encryption |
| Use a self-signed SSL certificate | ✗ | Provide Server CA, Client Key, and Client Cert |
3. Test and save
Click Test Connection to check that Superblocks can connect to the data source. After connecting successfully, click Create to save the integration.4. Set data tags
Optionally, configure different data tags for separate development environments.Using OracleDB in APIs
Once your OracleDB integration is created, you can start using it by writing SQL in Superblocks APIs. Use standard Oracle SQL syntax for all your queries, including support for PL/SQL blocks.Troubleshooting
If you run into issues, first see our guide on Troubleshooting Database Integrations. There are also several common errors you may see when using OracleDB:| Error message | Why it’s happening & Resolution |
|---|---|
ORA-12154: TNS:could not resolve the connect identifier specified | Reason The service name or connect identifier cannot be found. Resolution Verify the service name is correct and that the Oracle listener is configured properly. |
ORA-12541: TNS:no listener | Reason The Oracle listener is not running on the specified host and port. Resolution Verify the host and port are correct, and ensure the Oracle listener service is running on the database server. |
ORA-01017: invalid username/password; logon denied | Reason The username or password provided is incorrect. Resolution Verify your credentials are correct. Note that Oracle passwords are case-sensitive. |
ORA-28000: the account is locked | Reason The database user account has been locked due to too many failed login attempts or administrative action. Resolution Contact your database administrator to unlock the account. |