This error is not an indication of a network problem unless it occurs on all connections in other words you have never been able to connect. If you can make connections up to a certain point but then fails it is an indication of a resource limitation at the os level this sounds like your scenario.
Note Others can be found by searching MOSC with "" as the keyword. You may be able to get an indication of which OS resource is the root of the problem by tracing the listener. The originating linux error can then be researched. All OS error codes can be found in:. Listener tracing: Add the lines below to the listener. Restart the listener to start tracing. Feel free to ask questions on our Oracle forum. Verify experience!
Anyone considering using the services of an Oracle support expert should independently investigate their credentials and experience, and not rely on advertisements and self-proclaimed expertise. Results 1 to 3 of 3. Yesterday while taking Online backup, I got the subject error. Detail of error from sqlnet. Tns error struct: nr err code: 0 ns main err code: TNS TNS:internal limit restriction exceeded ns secondary err code: nt main err code: TNS Internal limit restriction exceeded nt secondary err code: 8 nt OS err code: 0 init.
Regards Vijay. U got problem with of open file descriptors per 1 application process. Probably this is internal OS NT problem with size of the table of file descriptors. I know, how i can solve this situation in unix, but not in NT. Join Date Aug Posts The error implies that you have hit a limit of some form. This is usually an OS limit that has been reached. The error might be: TNS TNS:internal limit restriction exceeded The alert log has an entry that looks like: skgpspawn failed category The skgpspawn failed message refers to a failure to spawn a new session.
Solution Description Performance monitor shows that the instance that that has the TNS error occurring is using right around 2gb of memory. The SGA for the instance is about 1.
0コメント