Troubleshooting
#"Cannot reach the backend at :5020"
Every panel reports this when the local service is not responding.
- Close DBCraft completely (check Task Manager for a lingering process) and restart it.
- Check that nothing else on the machine has taken port 5020.
- Check whether local security software is blocking loopback connections.
#Connection failures at login
| Error | Cause | Fix |
|---|---|---|
ORA-01017: invalid username/password | Wrong credentials. | Re-enter. Note that Oracle passwords may be case-sensitive. |
ORA-12541: TNS:no listener | Nothing is listening at that host and port. | Verify host, port and that the listener is running. |
ORA-12514: listener does not currently know of service | Wrong service name, or the database is not registered. | Check the service name; try SID instead. |
ORA-28000: the account is locked | Account locked. | Ask a DBA to unlock it. |
#"The password could not be saved securely"
The Windows credential vault was unavailable. Everything except the password is still remembered. This is not an error you can work around by design — the product will not write a password in the clear.
#A panel is empty, or a health check says "Unable to evaluate"
Your account lacks SELECT on the required dictionary or V$ view. DBCraft names the exact grant needed in the message. Ask a DBA for that grant, or connect with a privileged account.
#My inserted rows are not visible in a report / the terminal / the Data tab
You have not committed. The SQL editor runs in manual-commit mode; every other panel uses its own auto-committed connection. Press the ⎇ Commit button. See §16.6.
#Other users are blocked behind my session
Your editor session is holding uncommitted DML and therefore row locks. Commit or roll back. The status bar’s amber Uncommitted segment tells you when this is the case.
#The debugger does not stop at my breakpoints
- Recompile the program with debug information:
ALTER PROCEDURE my_proc COMPILE DEBUG; - Confirm your account has
DEBUG CONNECT SESSION. - Confirm the source shown is the source that is actually executing — after Step Into the highlight is suppressed if execution has moved into a different program (the status badge names it).
#The container switcher shows no PDBs
Oracle hides V$PDBS rows from common users by default. Use the Enable PDB visibility button in the dropdown, or ask a DBA to run ALTER USER <you> SET CONTAINER_DATA=ALL CONTAINER=CURRENT;.
#PDB open/close controls are missing
They appear only when connected as SYS, because Oracle requires a SYSDBA session for PDB lifecycle operations.
#The AI assistant returns an error
Open Settings → AI Configuration and press Test Connection — it reports exactly what failed (an invalid Base URL, a rejected key, an unreachable host) and refreshes the model list. The endpoint’s own error message is shown in the assistant’s reply.
#The ER diagram is missing tables
Generation is capped at the first 15 tables for performance. Use Specified Tables and Referenced Only in the display panel to focus the diagram, or model the remainder by hand.
#Excel export produced fewer rows than expected
Check Settings → System → Export row limit (DBA accounts only).
#Nothing happens when I press Save in the SQL editor
Save writes a .sql file to disk; it does not write to the database. If your browser-style download location is set to prompt, look for the dialog. Use Save As… to choose the location explicitly.