Workato · Oracle connector
Something went wrong when loading Oracle metadata
Short answer
"Something went wrong" while Workato loads Oracle metadata, with ORA-12516 in the logs, means the Oracle database is not accepting new connections. Ask your DBA to raise the processes and sessions limits and check the listener.
VerifiedLast verified
01Error text
Something went wrong
oracle.net.ns.NetException: Listener refused the connection with the following error:
ORA-12516, TNS:listener could not find available handler with matching protocol stack02Likely causes
- The Oracle database is not accepting new connections when Workato loads metadata.
03How to fix it
- Ask the DBA to increase the
processesandsessionslimits. - Review
listener.orafor the handler configuration. - Restart the Oracle listener service.
- Reduce simultaneous connections or optimize connection reuse.
04Official documentation
→Related errors
- java.lang.OutOfMemoryError: Java heap space (on-prem agent)This error in the on-prem agent log means the agent does not have enough memory for a large job or payload. Raise the Java heap with the -Xmx option and restart the agent.
- UndefinedColumn - Column does not existUndefinedColumn - Column does not exist means the database cannot find a column named in the step's SQL. It often happens after a column in the underlying table was renamed, so check the names and refresh the recipe's schema.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for Workato work:Open Workato jobsWorkato rates and salariesHire a senior Workato developer