Andreas Sheriff. I have gone through the postings in the groups for this error, however I could not find a solution to fix my problem. My database was working fine till the time it started giving this error just making sure that its not a tnsnames.
my applicationcontext.xml hibernate config
Question and Answer
Join Stack Overflow to learn, share knowledge, and build your career. Connect and share knowledge within a single location that is structured and easy to search. This has little to do with Spring, Hibernate, this is a pure Oracle "problem". Here is what we can read about ORA Cause: The process of starting up a dedicated server process failed. The executable could not be found or the environment may be set up incorrectly. The Oracle Protocol Adapter that is being called may not be installed on the local hard drive.
Cause : The process of starting up a dedicated server process failed. The executable could not be found or the environment may be set up incorrectly. The Oracle Protocol Adapter that is being called may not be installed on the local hard drive. Please check that the correct Protocol Adapter are successfully linked. If error persists, contact Oracle Customer Support. The solutions are:. Common syntax issues in the listener.
This question is You Asked Can either or both of these error conditions be generated by sending the TNS listener too many queries, too fast? If so, how fast is too fast? A user's database objects must have distinct names. Action: Enter a unique name for the database object or modify or drop the existing object so it can be reused. If you overload the OS, it won't be able to spawn any new processes. How fast is too fast -- thats a function of your OS, the amount of ram, how many cpu's you have, how fast they are, what else is going on on the box, etc etc etc Rating 63 ratings Is this answer out of date?