ORA-12514 Error
9th June 2009 by jt No CommentsResolving “ORA-12514: TNS:listener does not currently know of service requested in connect descriptor”.
JT’s blog-o-stuff
Resolving “ORA-12514: TNS:listener does not currently know of service requested in connect descriptor”.
One of my goals for Log4Ora is to make it easy to use. Has the ability for you to set the module name for logging. This is handy in the logging so you can see where in the code the log message came from. Downside of the Log4PLSQL implementation is you have to set the [...]
Today, I’ve started my own little open source project called Log4Ora.
I’ve found logging in PL/SQL is a weak area. I have not found a solution for PL/SQL with the versitily of a mature logging product such as log4j.
What I see most often, are home grown solutions, where the author creates a simple API to write [...]
A coworker and I had a spirited debate about how to run scheduled jobs in Oracle. Being the Oracle nerd that he is, his tool of choice is the Oracle job scheduler. He actually told me that running bash scripts off cron was ‘too complicated’. What!?!
Now, before I digress… I am very familiar with the Oracle job scheduler. I know its capabilities and some of its quirks. It is a nice tool. We are currently only leveraging a small part of its capabilities. But I’ve found it to have some odd quirks. Jobs don’t run for no apparent reason. When things go wrong it can be difficult to troubleshoot. Cron on the other hand is simple, flexible, and rock solid.
I’m an old unix guy. I’m certainly no guru on unix, but I do love the simplicity of the environment. Running bash scripts via cron is a powerful combination. Going back to when Oracle 7 was the latest and greatest, shell scripts were the way to do things in Oracle. And they still are for many people. After all, real DBAs don’t use OEM! Their tool of choice is putty!
You’ll find religious wars on unix vs linux