A quick summary of what might go wrong when trying to connect to an Oracle database. Based on this excellent article. Read the whole thing, this is just a quick reference. Error Code Message Translation ORA-12154 TNS:could not resolve the connect identifier specified No entry with the requested name in tnsnames.ora ORA-12545 Connect failed because […]
Note to self: You should not use message priority as a proxy for message order; this will only work in a single consumer situation. E.g. – Assume high priority messages have to be processed before low – You have 10 consumers – 11 messages arrive, 10 high, 1 low priority – All consumers start processing […]
You probably updated a DB element and need to grant permission on it, e.g. “grant execute on my_proc to ;”
Request the “DEBUG ANY PROCEDURE” privilege from your DBAs. This allows full interactive debugging of stored procs and functions in SQL Developer (probably Toad as well). In Tools/Preferences/Debugger, set ‘Prompt for Debugger…’ (use own ip address when prompted) Open the body of a package to add a breakpoint Then compile for debug Right click somewhere […]
Problem: You are passing info to the db, but the proc doesn’t appear to receive it. The stored proc works fine when executed directly from Toad or SQL Developer. This might be due to a missing i18n library which should be on your runtime classpath.
This might be caused by running to_char on a timestamp like this: to_char(dp.calc_date, ‘dd/Mon/yyyy hh:mi:s’). Try just returning the date without trying to convert it first. More about this error here.
Problem Error with Oracle hanging on a stored procedure call or commit statement. Solution Does someone have an uncommitted session? SQL Developer will sometimes cause this (maybe a user doesn’t have autocommit on?). select s.seconds_in_wait, s.blocking_instance, s.blocking_session, s.event, t.start_time, s.sid, s.serial#, s.username, s.status, s.schemaname, s.osuser, s.process, s.machine, s.terminal, s.program, s.module, to_char(s.logon_time,’DD/MON/YY HH24:MI:SS’) logon_time from v$transaction […]