STATUS: E1000
MESSAGE: ORA-12500: TNS : listener failed to start a dedicated server
process
DB ERROR: -12500
We get this message everytime we do something with the repository,
connecting, retrieving or sending reports, refreshing, etc. Every second
time it works ok.
the Repository is in a 7.3.2.3 Oracle dbase on WinNT server 4. We use BO
4.1.3.
I’m not sure exactly what the error message was, but I have encountered
problems like this before. You may want to rebuild your BOMain.key and make
sure the connection is set to “Disconnect after each transaction”. This has
solved most problems I have come across.
STATUS: E1000
MESSAGE: ORA-12500: TNS : listener failed to start a dedicated server
process
DB ERROR: -12500
Are all of your domains on the same Oracle instance / same version of
Oracle ? We had the same problem. We had the Development domains on Oracle
7.23, and Test domains on Oracle 8.3, both on the same Oracle instance, and
we had the security domain and the Production domains on Oracle 8.3 on a
separate Oracle instance. We were using SQL*NET 2.3 as the middleware.
To solve our problem, we had to upgrade all of our clients to Net 8, and
change the domain connect strings (inside of the Supervisor Module) to Net
8. Hope this helps point you in the right direction.
That’s funny. With “asynchronous mode” turned on, I have the best luck with
the “Keep active during whole session” option. (Oracle 7.3.3 database, BO
4.1.3.)
Be careful of using this setting. I can cause you to exceed your license
for SQL if you are licensed by concurrent users. The recommendation is to
use the ‘Keep the connection active for 1 minute’ which allows the
appropriate connect and disconnect processes to complete. This also does
not typically endanger your licenses.
MESSAGE: ORA-12500: TNS : listener failed to start a dedicated server
process DB ERROR: -12500
To solve our problem, we had to upgrade all of our clients to Net 8, and
change the domain connect strings (inside of the Supervisor Module) to Net
Hope this helps point you in the right direction.
We think this will help for us too. We found out that this server uses
an older SQLnet server than the other BO servers. We will try to upgrade
to the same level and expect that our problem will be solved.
I wanted to update this thread with a resolution. Recently, one of our DB’s was moved from one server to another and many users suddenly started getting this error; however, our DBA and a some others had no problems connecting. After researching the issue we discovered many of us were using a slightly different version of the sqlnet.ora file. Those who could not connect had a parameter embeded in their sqlnet.ora file(s) called USE_DEDICATED_SERVER = ON and apparently this was the cause of the problem. Once this parameter was removed from the appropriate file the issue was resolved.
(BOB member since 2002-06-20)