11.3 Multi-Threaded Server Problems

Team-Fly    

 
Oracle Net8 Configuration and Troubleshooting
By Jonathan Gennick, Hugo Toledo
Table of Contents
Chapter 11.  Solutions to Common Problems


This section provides possible solutions for some common problems related to the use of multi-threaded server.

11.3.1 Your Instance Won't Start

11.3.1.1 Symptom

You made some changes to the MTS parameters in your database initialization file, and now your instance won't start. The only error message you receive is this one:

 ORA-01078: failure in processing system parameters 
11.3.1.2 Possible solution

Unfortunately, setting an MTS-related initialization parameter incorrectly is often enough to prevent an instance from starting. Even more unfortunately , you aren't likely to get an error message that pinpoints the specific parameter that's incorrect. Your only real recourse is to carefully review each and every MTS parameter to ensure that it is correct.

One specific cause of this problem that we've noticed involves the MTS_SERVERS parameter. If no dispatchers are configured, a nonzero setting of MTS_SERVERS causes instance startup to fail. The reason is that with no dispatchers, the instance can't be configured with the specified minimum number of servers.

Check the MTS_DISPATCHERS parameter especially carefully. Of all the MTS parameters, MTS_DISPATCHERS is the one with the most complex syntax. Be sure that you have the correct number of parentheses and that they are nested properly.

All MTS_DISPATCHER parameters must be grouped together in your initialization parameter file. No other parameters can come between them.

If you don't find the problem through visual inspection, and you are still certain it is related to the MTS parameters, you need to do some experimentation. Comment out all MTS parameter settings, and see if your instance starts. If it does, then you know the problem is with one of those parameters. Uncomment them one by one, restarting the instance each time, until you reach the point where the instance fails to start. At that point, you know that the problem parameter is the one that you most recently uncommented.

11.3.2 You Get an ORA-00101 Error When Starting an Instance

11.3.2.1 Symptom

You try to start an instance, and you get the following error message:

 ORA-00101: invalid specification for system parameter MTS_DISPATCHERS 
11.3.2.2 Possible solution

In at least one case, this can be a somewhat misleading error message. The message tells you that there is a problem with one of your MTS_DISPATCHERS parameter settings. That message can be misleading if the problem lies with the LISTENER attribute. If the LISTENER attribute specifies a name (as opposed to a protocol address), then Oracle must resolve that name using tnsnames.ora or some other naming mechanism. If the name cannot be resolved, that will ultimately be reported back to you as an ORA-00101 error. Be sure that the name you supplied can be resolved. You can check that using the tnsping utility. If you can't resolve the problem with the name, you can sidestep the entire problem by supplying the listener's protocol address for the LISTENER attribute. See Chapter 5 for detailed information on the MTS_DISPATCHERS parameter.


Team-Fly    
Top


Oracle Net8 Configuration and Troubleshooting
Oracle Net8 Configuration and Troubleshooting
ISBN: 1565927532
EAN: 2147483647
Year: 2000
Pages: 120

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net