Troubleshooting
Start from what you see. Each problem below gives the usual cause and the fix, with a link to the page that explains it. Got an error message? Look it up in Error messages, or paste it into the search (press /).
I cannot connect
| Problem | Cause | Fix |
|---|
(driver not found) next to a type, or JDBC driver class ... was not found | The database's driver JAR is not installed | Copy it into drivers, restart, check with SHOW DRIVERS;: Connect to your database |
| The connection test fails | Wrong URL, host, port, user or password | EDIT CONNECTION <id>; and test again with PING <id>; |
CONNECT ... refused: ... opens the BroadSQL configuration database | The connection points to the CDF | Delete it: The configuration database |
ENV PROD fails | No Database Group, or no PROD connection in it | SHOW GROUP;: CONNECT versus ENV |
My SQL is refused
| Problem | Cause | Fix |
|---|
No active database connection. | BroadSQL starts at BroadSQL>, without a connection | CONNECT <id>;: Starting, connecting and logging out |
| Nothing happens after Enter | The statement has no closing ; yet | Type ;, or Esc to abandon it: Entering commands |
| The commands after a failed one did not run | On one typed line, a failure stops the rest | Run them again, one per line if needed |
Authentication required: enter the master password first. | The session was locked with LOGOUT | Type the master password |
A change to production was refused
| Problem | Cause | Fix |
|---|
Production change refused ...: the change was not confirmed | The answer to Execute? [yes/no] was not yes | Run it again and answer yes: Production confirmation |
... no interactive confirmation is available | No terminal to ask (input redirected, unattended run) | Run the change interactively: Without a terminal |
| BroadSQL asks before a statement that only reads | The statement is one it cannot classify (a procedure call, a block) | Answer the question, or see What asks and what does not |
A Script does not do what I expect
| Problem | Cause | Fix |
|---|
requires argument ... | A required parameter was not passed | Pass name=value, or LET it first: Arguments |
Variable ... is not defined. | A ${name} has no value | SHOW SCRIPT VARIABLES;, then declare or set it: Variables |
| The Script went on after an error | ON ERROR CONTINUE is the default | Add ON ERROR STOP;: Error handling |
| Earlier changes vanished after an error | A failed statement rolls back the pending transaction | Continuing is not keeping the transaction |
is written for Oracle; the current connection's type is H2 | The Script's -- @dialect names another type | A warning: check the connection |
| A Script is not found | A plain name always starts at the library root; nothing is searched | Give the path under scripts/: Running Scripts |
An export or a load fails
| Problem | Cause | Fix |
|---|
APPEND refused: ... | The result's columns differ from the destination's | Select and alias the same columns: Local H2 datasets |
MERGE refused: ... | A NULL or duplicate key | Filter the rows or choose another key: MODE MERGE KEY |
DUMP LIB ... not exported: ... | The Script did not end with SUCCESS | Fix its errors: Exporting Script results |
| An export refused because the result was cut | DUMP / exports what was displayed, which stopped at MaxRowsOnScreen | Use DUMP (<query>), which runs the query and exports every row |
LOAD refuses a header | A CSV header names no column of the table | Rename the header: Importing data |
LOAD writes nothing in a Script | Plain LOAD asks for a confirmation, which a Script cannot give | Use LOAD ... EXECUTE: Using LOAD in scripts |
The console behaves oddly
| Problem | Cause | Fix |
|---|
| Ctrl+C does not stop a query at once | The database driver decides when the statement stops | Wait, or press Ctrl+C again: Ctrl+C during a command |
| No colors | Colors are off when the terminal does not report them | The color setting: Colors and themes |
<@clipboard> fails on Linux | No graphical environment in the session | Put the values in a file and use <@file> |
| No activity log | The log folder does not exist | LogFolderName=logs: Command activity log |
The limits listed on each guide
Each guide ends with the problems of its own subject: Arguments and parameters, The configuration database, Connections, API Client.
Still stuck? Tell us what you typed and what BroadSQL printed.
Found something wrong or unclear on this page? Tell us, with the page address.