TRACING IN SQL*NET V2
제품 : SQL*NET
작성날짜 : 1997-10-10
Introduction
~~~~~~~~~~~~
For most problems you need to identify the relevant parts of a
connection to trace. To do this consider which scenario you are
having problems with and where tracing needs to be enabled.
Note that tracing produces a lot of output , especially at higher
trace levels.
There are 3 main areas of SQL*Net that can produce trace output:
1 = the SQL*Net 'client'
2 = the 'listener' process
3 = the SQL*Net 'server'.
a) Establishing a connection:
Client ----> Listener ----> Server
1 2 3
b) An established connection:
Client --------> Server
1 3
c) Opening a database link:
Client ----> Server ----> Listener -----> Server2
1 3 1 2 3
Note here that the Oracle server process is also a SQL*Net
client when it makes an outgoing call to a listener to
open a database link. Database links are OPENED when first
used. They should then remain open until closed.
d) An established database link:
Client ----> Server -----> Server2
1 3 1 3
In each case here there are several potential sampling points. You
should be able to identify quickly which of these scenarios matches
your setup. As these scenarios are likely to involve connections
between different machines you should remember that tracing for any
process is controlled by the configuration details that the process
reads WHEN IT IS STARTED. This is especially important when looking
at MTS connections as the SQL*Net server is the 'dispatcher' process.
Some dispatchers are started when the database instance is started
and others may start at a later time (on demand). Each dispatcher will
read their SQL*Net configuration WHEN THEY START.
7.2 Client Tracing
~~~~~~~~~~~~~~
For client TOOLS edit or create the file $HOME/.sqlnet.ora and add
the lines:
trace_level_client=16
trace_file_client=cli
trace_directory_client=/tmp # Or a known directory
trace_unique_client=true # Add '_pid' to trace filename
This will turn on FULL tracing for your user account only producing
output in a file called /tmp/cli_<PID>.trc .
(For some SQL*Net versions the file will be just /tmp/cli.trc)
For client 'ORACLE' process (as in the case of database links) put this
same information into $TNS_ADMIN/sqlnet.ora file.
On versions up to and including Oracle 7.0.16 client trace may not
add a process ID to the name of the trace file. This means two
processes may end up writing to the same trace file unless you
take care to control which processes write trace output to each file.
7.3 Listener Tracing
~~~~~~~~~~~~~~~~
Listener tracing can ONLY be configured in the listener.ora file.
Add the lines below to the listener.ora file:
trace_level_listener=16
trace_file_listener=listener
trace_directory_listener=/tmp # Or a known directory
This will define FULL listener tracing to the file /tmp/listener.trc.
You can enable this tracing by either:
lsnrctl reload
OR
lsnrctl stop;
lsnrctl start;
TCP/IP
~~~~~~
It is often useful to confirm that a listener is listening on a
specified address. Most Unix machines include a command called
'netstat' (Often in /etc or in /usr/etc). The command netstat -a
should list all TCP/IP end points on which a listener is listening.
Eg:
For a listener listening on HOST=... PORT=1580 there should be a
netstat entry of the form:
RecvQ SendQ Local Address Foreign Address TCP state
0 0 *.1580 *.* LISTEN
Note: Some versions of netstat will only list established connections
and not listen end points. See the man page on your machine.
7.4 Server Tracing
~~~~~~~~~~~~~~
Server side trace is not required as often as the other two traces
mainly because most problems are related to establishing a connection.
Once a connection has been established the client and server processes
are communicating. It is sometimes useful to see exactly what SQL
commands have been received by the server, and what data it has sent
back out.
The file $TNS_ADMIN/sqlnet.ora controls the server side tracing. Add
the lines below to this file:
trace_level_server=16
trace_file_server=server
trace_directory_server=/tmp # Or a known directory
Output should be sent to the file /tmp/server_<PID>.trc
Note: Server side tracing acts on the SQL*Net server side.
For dedicated connections this is the Oracle process on the
server machine.
For MTS connections this is the DISPATCHER and NOT the shared
server. Data is passed between the dispatcher and the shared
servers via the SGA and this does NOT involve SQL*Net.
It is also important to note that as a dispatcher handles
several client processes the dispatcher trace output can be a
mix of trace from many client processes making it VERY difficult
to follow. The general advice for such problems is:
a) See if the problem reproduces WITHOUT using MTS - if
so the trace is much cleaner
b) If a problem ONLY reproduces under MTS ensure the machine
is in a controlled environment so you can be sure that only
YOUR process is using the dispatcher.
7.5 Trace Summary
~~~~~~~~~~~~~
1) Identify where you need to trace.
2) Identify which files on which machines control tracing at these
points. Tracing is controlled in the following files:
Client Server Listener
~~~~~~ ~~~~~~ ~~~~~~~~
Files: $HOME/.sqlnet.ora sqlnet.ora listener.ora
sqlnet.ora
3) Add in the relevant trace parameters (See Below)
4) Restart any processes that need to read the new trace values.
Reload the listener as required.
5) Reproduce your problem
6) Save all your trace output immediately
7) Disable the tracing
7.6 Main Trace Parameters
~~~~~~~~~~~~~~~~~~~~~
trace_level_listener = off
trace_file_listener = Filename *1
trace_directory_listener = Directory *2
*1 Unquoted (") filenames will be translated into lower case.
*2 You CANNOT use environment variables in the Filename or Directory
name.
7.7 Diagnosing Trace output
~~~~~~~~~~~~~~~~~~~~~~~
Trace output can be very difficult to follow. Before looking at a
trace file make sure:
a) You are familiar with the sequence of events in setting up
a connection. SQL*Net connections follow a sequence of
events - you will need to determin where in the sequence
the problem occurs.
b) Do not be misled by error reports in the trace files. You
must follow the context of the errors - an error may be
quite valid at that point in a sequence. Eg: For client
connections a list of addresses to call is built - if the
first address yeilds no response the next address is tried.
This next address may yeild a response and the 'true' error
occurs at this point in the sequence.
c) Do not be misled by unusual 'Bequeath' connections in the
trace. If an error is received over SQL*Net the client
may use a "Bequeath" operation to spawn an oracle process
which it then uses to get the TEXT of the error. A very short
exchange of packets occurs and the bequethed process exits.
The 'TRUE' problem is likely to be before this bequeath
operation.
Useful trace 'tags':
The following are useful items to follow in trace files - these
are not guaranteed to be valid across all SQL*Net releases and
are for guidance only. Entries are assumed to be taken at trace
level 16 to allow data packets to be seen. This will produce a
LOT of trace output.
-<ERROR>-
Error information follows. Remember the error may be acceptable
osntns: Calling address
Shows address list constructed for a call OUT to a listener
nricall: Making call with following address information: ...
Shows the ACTUAL address being called from the above list
nsopen: entry
We are about to try and open a connection.
nsopen: transport is open
nsopen: error exit
A connection to the called address has been made / failed.
nsclose: ...
An established connection is being closed - check nearby
for errors.
nscall: redirected
The client has been redirected to a differenct address.
The next step should be to call the new address. The address
should appear in an earlier data packet.
nspsend / nsprecv
Outgoung / Incoming data
This forum is for Oracle Migration Workbench issues, i.e. migration using the workbench from a non Oracle database to an Oracle database.
Here are some pointers that may be useful, but you may need to get more information elsewhere, for example Oracle Customer Support.
a Oracle 7.1 client (including your example) will connect to an Oracle 8.1.5 server.
Is the server correctly configured (can a client connect from another machine)?
Tracing can be turned on in the client, server and/or listener to get further information.
Turloch
Similar Messages
-
CLIENT SIDE TRACING IN SQL*NET V2
제품 : SQL*NET
작성날짜 : 1997-10-10
Client Tracing
~~~~~~~~~~~~~~
1) Set the environment variable TNS_ADMIN to the directory where the
tnsnames.ora and listener.ora files exist.
The default location is $ORACLE_HOME/network/admin. Set $TNS_ADMIN
to this if it is not set. This ENSURES you know which files you are
using.
2) Start the listener: lsnrctl
> set password <password>
> start
Note any errors. If you do not have a password set then ignore the
set password command.
3) If the listener started, start the database.
4) Create a file in $HOME called .sqlnet.ora and add the lines:
trace_level_client= 16
trace_file_client=client
trace_directory_client= /tmp (or similar)
trace_unique_client=true
5) Try to connect from SQL*Plus thus:
sqlplus username/password@alias
or
sqlplus username/password
substituting a suitable alias.
6) If you get an error we may need to see the client trace file
/tmp/client_<PID>.trc where <PID> is the process ID of the
client process (*1).
This will be quite large so it is best to FAX or EMAIL it.
*1 Note: On earlier versions of SQL*Net the filename may NOT have
the process ID appended to it.
Listener Tracing:
~~~~~~~~~~~~~~~~~
1) Edit your $TNS_ADMIN/listener.ora file and add the lines:
TRACE_LEVEL_LISTENER = 16
TRACE_DIRECTORY_LISTENER = /tmp
TRACE_FILE_LISTENER = "listener"
2) Stop and restart the listener:
lsnrctl stop
lsnrctl start
Output should go to /tmp/listener.trcBy default in 11g traces will go to the ADR which is a new feature.
To disable that feature add the following line to your sqlnet.ora
diag_adr_enabled =OFF
[oops] saw that this is over a month old this post - sorry about that!
hope that helps
John
Edited by: Johnsung on Sep 27, 2012 3:59 PM -
VMS : SQL*NET V2.0 ARCHITECTURE
제품 : SQL*NET
작성날짜 : 2001-05-28
VMS : SQL*NET V2.0 ARCHITECTURE
===============================
1. SQL*Net V2.0 Architecture
* Master File 위치 : Logical name TNS_ADMIN
= ORA_ROOT:[NETWORK.ADMIN]
* Main File 종류 : SQLNET.ORA
LISTENER.ORA
TNSNAMES.ORA
2. SQLNET.ORA
* SQL*Net에 대한 몇가지 parameter setting을 가지고 있다.
* Comments는 # 후에 기록한다.
* Client와 Server 측면에서의 trace와 log level을 setting할 수 있다.
* TRACE_FILE_xxxxx parameter는 trace file의 이름을 지정한다.
.TRC file name의 끝부분을 자동으로 생성한다.
* IPC(Inter-Process Communication)를 제어하는 parameter를 설정할 수
있는데 default는 ON이다. 이것은 자동으로 OpenVMS Mailboxe와
Unix pipes 중에서 platform에 맞게 고르는 것이다.
# FILENAME: sqlnet.ora
# NETWORK.: UK_VAX_NET
# SERVICE.: NA
TRACE_LEVEL_CLIENT = OFF
TRACE_DIRECTORY_CLIENT = ORACLE$DISK:[ORACLE7.PROD.NETWORK.TRACE]
TRACE_FILE_CLIENT = CLIENT
LOG_DIRECTORY_CLIENT = ORACLE$DISK:[ORACLE7.PROD.NETWORK.LOG]
LOG_FILE_CLIENT = CLIENT
TRACE_LEVEL_SERVER = OFF
TRACE_DIRECTORY_SERVER = ORACLE$DISK:[ORACLE7.PROD.NETWORK.TRACE]
TRACE_FILE_SERVER = SERVER
LOG_DIRECTORY_SERVER = ORACLE$DISK:[ORACLE7.PROD.NETWORK.LOG]
LOG_FILE_SERVER = SERVER
AUTOMATIC_IPC = ON
SQLNET.EXPIRE_TIME = 10
3. LISTENER.ORA
* LISTENER의 default name은 LISTENER이다.
* LISTENER의 name과 capability를 setting한다.
<lsnr-name> = (ADDRESS_LIST =
(ADDRESS =
(PROTOCOL = IPC)
(KEY = sid)
(ADDRESS =
(PROTOCOL = DECNET)
(NODE = node-name)
(OBJECT = object-name)
(ADDRESS =
(PROTOCOL = TCP)
(HOST = node-name)
(PORT = 1521)
* ORACLE8 이후로는 DECnet protocol은 지원하지 않는다.
* LISTENER START & STOP COMMAND : LISTENER 이름이 LISTENER일 경우
$ LSNRCTL START
$ LSNRCTL STOP
$ LSNRCTL STATUS
4. TNSNAMES.ORA
* Client level에서 필요한 file로 service를 define한다.
* Service Define
For DECnet...
<service-name> =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS =
(PROTOCOL = DECNET)
(NODE = <node-name>)
(OBJECT = <lsnr-object>)
(CONNECT_DATA =
(SID = <sid>)
For TCP/IP...
<service-name> =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS =
(PROTOCOL = TCP)
(HOST = <node-name>)
(PORT = 1521)
(CONNECT_DATA =
(SID = <sid>)
5. Logging and Tracing
* Listener logging은 default로 자동으로 하게 되어있다.
LOG_DIRECTORY : Log File이 생성될 Directory setting
LOG_FILE_<lis> : Log File name
* Tracing Level
TRACE_LEVEL_<listener-name> = OFF|USER|ADMIN
OFF tracing을 disable시킨다.
USER 제한적으로 tracing 한다.
ADMIN 상세하게 tracing 한다.
* server process에 대한 tracing은 default로 disable되어 있다.
6. Tips
* 실제로 동작하기 위해서 server process를 기동시켜주는 command
procedure인 ORASRV_NETV2.COM 이 있어야 하는데 TNS_ADMIN 에
sample이 있으므로 수정해서 사용하도록 한다.
이때 반드시 ORA_DB directory가 정의되어 있어야 한다.
* SYLOGIN.COM이나 LOGIN.COM에 다음의 조건문을 넣어서 Network
Access를 처리할 수 있다.
$ IF F$MODE() .EQS. "NETWORK" .OR. F$MODE() .EQS. "OTHER" -
THEN EXIT
* 만약 listener나 server process가 아무런 tracing information을
남기지 않고 계속 죽는다면 VMS Accounting Utility를 이용하여
process termination status를 점검해본다.
$ ACCOUNTING/FULL/IDENT=<pid>Depending on how large is your database you can use either exp/imp utility to migrate the data after installing the Oracle8i on your O/S or Inplace db upgrade. Otherwise backup your current Oracle7.x release and install the Oracle8i Software only without the database. Open old database using the Oracle8i svrlmgrl utility. Upgrade using the upgrade scripts available in $ORACLE_HOME/rdbms directory. Also read the documentation for any additional information on issues on the upgrades.
I am not sure about the SQL Net versions, but SQL Net Version 2 should work against net8 listener. You could try v1 too.
Hope this helps
null -
Sql*net V2 vs. Net 8
I need to connect Forms 4.5 with Oracle 8.
Since Forms 4.5 uses sql*net v2 and Oracle 8 supports Net 8 as TNS, how do i go about accomplishing this ?
Need help ASAP.
Thanks !This forum is for Oracle Migration Workbench issues, i.e. migration using the workbench from a non Oracle database to an Oracle database.
Here are some pointers that may be useful, but you may need to get more information elsewhere, for example Oracle Customer Support.
a Oracle 7.1 client (including your example) will connect to an Oracle 8.1.5 server.
Is the server correctly configured (can a client connect from another machine)?
Tracing can be turned on in the client, server and/or listener to get further information.
Turloch -
SQL*NET V2 SETUP (MTS)
제품 : SQL*NET
작성날짜 : 1997-06-23
SQL*NET V2 SETUP (MTS)
======================
UNIX에서 SQL*NET V2를 사용하려면 ORACLE 인스톨 후에 다음과 같이 SETUP을 한
다음 사용하면 된다. 여기서
ORACLE_HOME DIRECTORY는 /usr/oracle7
ORACLE_SID는 ORA7
이라고 가정한다.
1. (단, MTS로 setting하지 않고 dedicated로 접속할 때에는 이 과정은 생략하도록
한다.)
Multi-threaded server 프로세스들을 먼저 기동을 하여야 한다.
$ORACLE_HOME/dbs/initSID.ora 화일에 다음과 같은 내용을 추가하고
DB 를 다시 startup 을 한다
# Filename : /usr/oracle7/dbs/initSID.ora
# Protocol : tcp
mts_dispatchers="tcp, 3"
mts_max_dispatchers=10
mts_servers=5
mts_max_servers=10
mts_service=ORA7
mts_listener_address="(ADDRESS=(PROTOCOL=tcp)(port=1521)
(host=hostname))"
2. tnsnames.ora 및 listener.ora 를 작성한다. 이 화일들은
/usr/oracle7/network/admin 디렉토리에 만들어야 하며 유닉스 환경변수를
TNS_ADMIN=$ORACLE_HOME/network/admin
과 같이 지정하고 사용하는 것이 좋다.
<EXAMPLE>
# File name : /usr/oracle7/network/admin/listener.ora
# This configuration supports tcp
LISTENER =
(ADDRESS_LIST =
(ADDRESS =
(PROTOCOL = tcp)
(HOST = hostname)
(PORT = 1521)
STARTUP_WAIT_TIME_LISTENER = 0
CONNECT_TIMEOUT_LISTENER = 0
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = ORA7)
(ORACLE_HOME=/usr/oracle7)
# Filename : /usr/oracle7/network/admin/tnsnames.ora
TORA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS =
(PROTOCOL = tcp)
(HOST = hostname)
(PORT=1521)
(CONNECT_DATA =
(SID = ORA7)
3. Listener process를 start한다.
$lsnrctl start
4. SQL*NET v2 를 사용하여 MTS 에 접속한다.(LOOPBACK TEST)
$ sqlplus scott/tiger@TORA
5. CLIENT에서 접속하는 경우라면 위에서 만든 tnsnames.ora 화일을 CLIENT의
$ORACLE_HOME/network/admin 디렉토리에 COPY 하기만 하면 된다.
6. 예를 들어 CLIENT가 WIN95라면 C:\ORAWIN95\NETWORK\ADMIN 디렉토리에
tnsnames.ora 화일을 COPY하면 된다. 만약 ORA-12154 에러가 발생하면
C:\ORAWIN95\NETWORK\ADMIN 디렉토리에 sqlnet.ora가 있는지 확인하고
이것을 sqlnet.old 같이 다른 이름으로 rename 한 후에 접속테스트를 해
보도록 한다. sql*plus(plus33.exe or plus33w.exe)로 접속하는 경우
다음과 같이 접속하면 된다.
USERNAME scott
PASSWORD tiger
HOST STRING TORA
* SERVER가 WINDOWS NT인 경우에는 다른 부분은 UNIX와 동일하게 setup하면
되고 단지 Listener를 띄우는 방법만 다르다.
제어판 -> SERVICES 에서 ORACLE 관련 SERVICE들을 모두 START 시켜주면 된다.This forum is for Oracle Migration Workbench issues, i.e. migration using the workbench from a non Oracle database to an Oracle database.
Here are some pointers that may be useful, but you may need to get more information elsewhere, for example Oracle Customer Support.
a Oracle 7.1 client (including your example) will connect to an Oracle 8.1.5 server.
Is the server correctly configured (can a client connect from another machine)?
Tracing can be turned on in the client, server and/or listener to get further information.
Turloch -
제품 : SQL*NET
작성날짜 : 2001-04-25
SQL*NET V2 최적화하기
====================
1) PING
TCP/IP 네트워크상에서 ping을 사용해서
client와 server간에 걸리는 시간을 check할 수 있다.
만일 이 시간이 오래 걸리면 SQL*Net 보다 이 문제를 먼저 해결해야 한다.
사용 방법 :
ping 호스트이름
(NT의 경우에는 dos command상태에서)
2) TNSPING
이 tool은 기본적으로 설치가 되어 있으며
이 tool을 가지고 user가 client에 setting한 TNS alias(tnsnames.ora
파일안에 설정)
가 정상적으로 동작하는지를 테스트해 볼 수 있습니다.
TNSPING은 접속하고자하는 database가 있는 machine의 listener에 접속을하고
걸리는 시간을 miliseconds로 표시해 줍니다.
(실제 db와 connection을 맺는 것은 아닙니다.)
사용 방법 :
tnsping TNSalias이름
(NT의 경우에는 dos command상태에서)
3) 모든 logging 과 tracing 막기
Tracing은 client와 server에 모두 가능하게 할 수 있습니다.
다음 parameter를 SQLNET.ORA파일과 LISTENER.ORA파일
( $ORACLE_HOME/network(또는 net80)/admin에 위치합니다 )
에 setting하고 listener를 restart
(lsnrctl stop, lsnrctl start)
하면 SQL*Net의 모든 tracing을 막을 수 있습니다.
SQLNET.ORA:
TRACE_LEVEL_CLIENT =OFF
TRACE_LEVEL_SERVER =OFF
TNSPING.TRACE_LEVEL=OFF
'OFF'대신에 '0'을 사용해도 됩니다.
LISTENER.ORA:
TRACE_LEVEL_LISTENER=OFF
LOGGING_LISTENER=OFF
4) Listener log 파일들 지우기
만일 listener의 logging이 설정되어 있는 상태라면 LISTENER.LOG 파일이
이 생깁니다. listener는 connection이 맺어질대 마다 이 파일에
lock을 걸고 write하기 때문에 size가 계속 증가하게 되어 문제가 생길 수
있습니다. 만일 LISTENER.LOG 파일의 size가 너무 크게 되면 rename을 하시기
바랍니다. 그리고 listener를 restart하면 새로운 log file이 만들어 집니다.
5) SQLNET.ORA에 AUTOMATIC_IPC를 OFF로 설정
AUTOMATIC_IPC = { ON | OFF }
위 parameter는 "SQLNET.ORA"파일에 설정할 수 있으며 ON으로 되어 있는경우
SQL*Net이 같은 alias정보를 가진 local database가 있는지 check하게
됩니다.
만일 local database가 있다면 connection은 network layer를 건너뛰고 local
'Inter Process Communication'(IPC) connection을 맺게 됩니다.
따라서 이 setting은 database server쪽에 사용할 수 있는 것이지
client machine SQL*Net에는 아무 쓸모 없습니다.
database server쪽에 사용하더라도 local database에 SQL*Net connection이
반드시 필요한 경우가 아니라면 사용하시 않는 것(OFF로 설정)이 좋습니다.
6) SQLNET.ORA에 NAMES.DIRECTORY_PATH 설정
NAMES.DIRECTORY_PATH = (ONAMES,TNSNAMES)
이 parameter는 TNS aliases를 찾는 경로를 지정할때 사용합니다.
Oracle*Names가 설정이 안되어 있는 경우 ONAMES을 지우시는 것이 좋습니다.
7) SDU와 TDU
SDU('Session Data Unit')는 네트워크를 통해 보내는 packet의 size입니다.
이 size는 MTU(Maximum Transmission Unit)를 넘어서는 안됩니다.
MTU는 네트워크상에 고정된 값입니다.
TDU('Transport Data Unit')는 SQL*Net이 data를 함께 묶는 기본 packet size
이며 SDU의 배수여야 합니다.
다음에서 예를 들어 보겠습니다.
* SDU=1024, TDU=1536:
SQL*Net은 buffer에 1536 byptes까지 저장했다가 네트워크로 보냅니다.
낮은 network layer에서 이것을 다시 두개의 physical packets(1024,512
bytes)로
나누어 보냅니다.
* SDU=1514, TDU=1000:
SQL*Net은 buffer에 1000 byptes까지 저장했다가 네트워크로 보냅니다.
SDU는 request당 514 bytes를 더 담을 수 있는데도 불구하고 보내지기 때문에
network resource의 낭비를 초래합니다.
표준 Ethernet network에서 MTU의 default size는 1514 bytes입니다.
표준 token ring network에서 MTU의 default size는 4202 bytes입니다.
SDU와 TDU를 설정하려면 TNSNAMES.ORA 과 LISTENER.ORA 를 다음과 같이
바꾸어야 합니다.
TNSNAMES.ORA:
ORCL.WORLD =
(DESCRIPTION =
(SDU=1514)
(TDU=1514)
(ADDRESS =
(PROTOCOL = TCP)
(HOST = fu.bar)
(PORT = 1521)
(CONNECT_DATA = (SID = ORCL))
LISTENER.ORA:
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SDU = 1514)
(TDU = 1514)
(SID_NAME = ORCL)
(GLOBAL_DBNAME = ORCL.WORLD)
SDU와 TDU는 modem을 사용하는 환경에서는 줄여주는 것이 좋고
fiber나 T3 line을 사용하는 환경에서는 늘려주는 것이 좋습니다.
SDU와 TDU의 default값은 2048이고 maximum값은 32768입니다.
8) PROTOCOL.ORA의 tcp.no_delay 설정
기본적으로 SQL*Net은 SDU buffer가 찰때가지 request를 전송하지 않고
기다립니다. 다시 말해 request가 도착지점으로 바로 전송되지 않는 다는것을
의미 합니다. 그런데 'no_delay'를 설정함으로써 data buffering을 하지 않게
할 수 있습니다. 따라서 'no_delay'를 설정하게 되면 작은 size의 patckets의
전송이 늘게되어 network traffic이 증가하게 됩니다.
따라서 이 parameter는 TCP timeout이 발생했을 경우에만 사용하셔야 합니다.
9) LISTENER.ORA의 QUEUESIZE 설정
QUEUESIZE는 listener가 저장할 수 있는 request의 수를 의미 합니다.
만일 들어오는 reqeusts의 수가 buffer의 size를 넘게 되면,
접속을 시도한 client는 접속을 실패하게 됩니다.
이 buffer의 size는 예상되는 동시 접속 수를 설정해 주는 것이 좋습니다.
LISTENER =
(ADDRESS_LIST =
(ADDRESS =
(PROTOCOL = TCP)
(HOST = fu.bar)
(PORT = 1521)
(QUEUESIZE = 32)
이 parameter는 TCP/IP나 DECNET protocol이 사용될때만 사용됩니다.
10) SQLNET.ORA의 BREAK_POLL_SKIP 설정
이 parameter는 user break을 check하는 사이의 packet수를 지정합니다.
다시 말해 만일 이 parameter의 값이 높으면 CTRL-C checking은 덜 자주
일어나게되며 CPU overhead는 줄게 됩니다.
만일 이 parameter의 값이 낮으면 CTRL-C checking이 자주 발생되어
CPU overhead가 늘게 됩니다.
기본값은 4이며 client SQL*NET에만 사용됩니다.
11) SQLNET.ORA의 DISABLE_OOB 설정
Out of band break check를 enable시키거나 disable시킬때 사용하는
parameter입니다.
기본값은 off입니다.
여기서 잠간만 !
Out of Band Breaks란 무엇인가 ?
네트워크 통신상에서 받아들여지는 interrupt signals은 일반적으로
다른 data(예를 들어 select 문장)과 같이 도착하게 됩니다.
이것을 In-band Breaks라고 합니다.
그런데 이 interrupt signals을 connection과는 다른 channel을 통해
전달할 수 있습니다 이것을 Out of Band Breaks라고 하며 이 방식은
interrupt signal을 훨씬 빠르게 그리고 효과적으로 전달 할 수 있습니다.
(예를 들어 deadlock을 break하기위해 control-C를 사용하는 것)
12) PROCESS.DAT와 REGID.DAT
7.3.2 버전에서 Oracle Server Tracing은 기본적으로 enabled되어 있습니다.
따라서 모든 connection과 request가 PROCESS.DAT와 REGID.DAT에
기록이됩니다.
database의 사용기간이 길어지면 이 파일들은 접속속도를 현저히 떨어뜨리게
됩니다.
이러한 trace 파일들을 사용하지 않기위해 listener.ora파일에
'EPC_DISBLED=TRUE'를 설정해야 합니다.This forum is for Oracle Migration Workbench issues, i.e. migration using the workbench from a non Oracle database to an Oracle database.
Here are some pointers that may be useful, but you may need to get more information elsewhere, for example Oracle Customer Support.
a Oracle 7.1 client (including your example) will connect to an Oracle 8.1.5 server.
Is the server correctly configured (can a client connect from another machine)?
Tracing can be turned on in the client, server and/or listener to get further information.
Turloch -
Hello,
i'm looking for the SQL*NET proxy because i want to integrate into out firewall software. I'm looking for a contact too. Nobody knows anything about this product.
With best regards
Claus Rosenbergerdespite that I do not know the type of the Firewall , I was able to adjust Oracle with Microsoft ISA server as follows :
go to oracle server on Windows 2000
open system variables
insert the following variable : USE_SHARED_SOCKET
make its value : TRUE
restart server
this variable will make you able to share ports on windows platform ,, this is essential because Oracle servers replies back on any port randomly when trying to connect to it ,, you can track this by enabling tracing for listener.
on firewall you will need to redirect connection received by the firewall on specific port on the firewall and NAT it to Oracle server IP/port .
this is proven work
on UNIX you do not need this beacsue Unix natively share ports. -
Looking for SQL*Net for Windows 95
I have Brio client installed on my laptop running Windows 98. I am looking for SQL *Net for Windows 95, to connect to an Oracle database running on Solaris. Where can I find it.
How do I connect? I tried MS ODBC and it did not work.
Please help
My email address is [email protected]
Thanks in advancedespite that I do not know the type of the Firewall , I was able to adjust Oracle with Microsoft ISA server as follows :
go to oracle server on Windows 2000
open system variables
insert the following variable : USE_SHARED_SOCKET
make its value : TRUE
restart server
this variable will make you able to share ports on windows platform ,, this is essential because Oracle servers replies back on any port randomly when trying to connect to it ,, you can track this by enabling tracing for listener.
on firewall you will need to redirect connection received by the firewall on specific port on the firewall and NAT it to Oracle server IP/port .
this is proven work
on UNIX you do not need this beacsue Unix natively share ports. -
Can't connect to sql*net, ORA-12638: Credential retrieval failed
after installed oracle9i, I can use sqlplus, but when I try to use sql navigator, I can't connect to sql*net.
I found out the following error message in logfile:
Fatal NI connect error 12638, connecting to:
(DESCRIPTION=
(ADDRESS=
(PROTOCOL=BEQ)
(PROGRAM=oracle)
(ARGV0=oracleoms)
(ARGS='(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))'))
(CONNECT_DATA=(SID=oms)(CID=(PROGRAM=c:\oracle\ora92\bin\ORACLE.EXE)(HOST=JZQGG31)(USER=OraUser))))
VERSION INFORMATION:
TNS for 32-bit Windows: Version 9.2.0.1.0 - Production
Oracle Bequeath NT Protocol Adapter for 32-bit Windows: Version 9.2.0.1.0 - Production
Time: 11-MAR-2004 17:04:17
Tracing not turned on.
Tns error struct:
nr err code: 0
ns main err code: 12638
TNS-12638: Credential retrieval failed
ns secondary err code: 0
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
=============================================
Hope somebody can help me! Thanks!change in sqlnet.ora file
find under oracle home\network\admin\sqlnet
and
SQLNET.AUTHENTICATION_SERVICES = (NTS)
CHANGE TO
SQLNET.AUTHENTICATION_SERVICES = (NONE)
hope it will solve u r problem
kuljeet pal singh -
SQL*Net and Datapump export disconnects with ORA-03113 error
Hi,
I have some trouble with an Oracle 11.2.0.1.0 server installation on a Windows 2008 R2 server.
If I am connected with SQL*Plus on the database server to an instance it randomly disconnects me, but no longer than after 30-60 seconds even though I am active running simple select queries.
I can connect again without any error and soon it disconnects me again.
If I am running an expdp, datapump export it starts but displays error UDE-03113 and then ORA-03113. The datapump export continues in the background and finish successfully though.
When having a look at the Alert.log for the database instance I see this error everytime it happens:
Fatal NI connect error 12547, connecting to:
(LOCAL=NO)
VERSION INFORMATION:
TNS for 64-bit Windows: Version 11.2.0.1.0 - Production
Oracle Bequeath NT Protocol Adapter for 64-bit Windows: Version 11.2.0.1.0 - Production
Windows NT TCP/IP NT Protocol Adapter for 64-bit Windows: Version 11.2.0.1.0 - Production
Time: 22-JUL-2012 21:10:40
Tracing not turned on.
Tns error struct:
ns main err code: 12547
TNS-12547: TNS:lost contact
ns secondary err code: 12560
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
opiodr aborting process unknown ospid (19800) as a result of ORA-609
Mon Jul 23 02:00:00 2012
I don't believe it is an network problem as each command I am running is on the server console. No other errors in the OS event log so I need some help where to start...
Thanks in advance!
Best Regards
Martin GabrielssonThanks, no windows firewall turned on, I turned on SQL*Net tracing and this is the last part of the trc file after doing a simple select query on a table with 3 rows. After the select query has been runned I am disconnected... Any idea, help is really appreciated!
+2012-07-30 18:15:28.658650 : nsbasic_brc:packet dump+
+2012-07-30 18:15:28.658660 : nsbasic_brc:01 74 00 00 06 00 00 00 |.t......|+
+2012-07-30 18:15:28.658668 : nsbasic_brc:00 00 06 01 1A 00 26 00 |......&.|+
+2012-07-30 18:15:28.658676 : nsbasic_brc:00 00 00 00 0F 00 00 00 |........|+
+2012-07-30 18:15:28.658684 : nsbasic_brc:00 00 00 00 00 00 00 00 |........|+
+2012-07-30 18:15:28.658693 : nsbasic_brc:00 00 00 00 00 00 00 00 |........|+
+2012-07-30 18:15:28.658701 : nsbasic_brc:00 00 00 00 00 00 00 00 |........|+
+2012-07-30 18:15:28.658708 : nsbasic_brc:00 00 00 00 00 00 00 00 |........|+
+2012-07-30 18:15:28.658717 : nsbasic_brc:00 00 00 00 07 96 2C 00 |......,.|+
+2012-07-30 18:15:28.658725 : nsbasic_brc:25 06 4D 52 20 20 20 20 |%.MR....|+
+2012-07-30 18:15:28.658734 : nsbasic_brc:03 C2 1A 5F 04 C3 02 10 |..._....|+
+2012-07-30 18:15:28.658742 : nsbasic_brc:43 06 43 4C 4F 53 45 44 |C.CLOSED|+
+2012-07-30 18:15:28.658750 : nsbasic_brc:FF FF FF FF FF FF FF FF |........|+
+2012-07-30 18:15:28.658758 : nsbasic_brc:FF FF 06 4C 50 49 4D 20 |...LPIM.|+
+2012-07-30 18:15:28.658767 : nsbasic_brc:20 FF FF FF FF FF FF FF |........|+
+2012-07-30 18:15:28.658775 : nsbasic_brc:FF FF FF FF FF 0A 4D 41 |......MA|+
+2012-07-30 18:15:28.658783 : nsbasic_brc:52 47 41 42 20 20 20 20 |RGAB....|+
+2012-07-30 18:15:28.658791 : nsbasic_brc:FF 3C 77 68 65 65 6C 20 |.<wheel.|+
+2012-07-30 18:15:28.658799 : nsbasic_brc:73 68 6F 70 20 20 20 20 |shop....|+
+2012-07-30 18:15:28.658807 : nsbasic_brc:20 20 20 20 20 20 20 20 |........|+
+2012-07-30 18:15:28.658815 : nsbasic_brc:20 20 20 20 20 20 20 20 |........|+
+2012-07-30 18:15:28.658824 : nsbasic_brc:20 20 20 20 20 20 20 20 |........|+
+2012-07-30 18:15:28.658832 : nsbasic_brc:20 20 20 20 20 20 20 20 |........|+
+2012-07-30 18:15:28.658840 : nsbasic_brc:20 20 20 20 20 20 20 20 |........|+
+2012-07-30 18:15:28.658848 : nsbasic_brc:20 20 20 20 20 20 02 C1 |........|+
+2012-07-30 18:15:28.658856 : nsbasic_brc:05 07 78 66 05 03 10 09 |..xf....|+
+2012-07-30 18:15:28.658864 : nsbasic_brc:38 02 C1 02 FF 03 C2 08 |8.......|+
+2012-07-30 18:15:28.658872 : nsbasic_brc:42 FF 01 58 04 01 00 00 |B..X....|+
+2012-07-30 18:15:28.658880 : nsbasic_brc:00 14 00 01 02 00 00 00 |........|+
+2012-07-30 18:15:28.658888 : nsbasic_brc:7B 05 00 00 00 00 02 00 |{.......|+
+2012-07-30 18:15:28.658897 : nsbasic_brc:00 00 03 00 20 00 00 00 |........|+
+2012-07-30 18:15:28.658905 : nsbasic_brc:00 00 00 00 00 00 00 00 |........|+
+2012-07-30 18:15:28.658912 : nsbasic_brc:00 00 00 00 00 00 00 00 |........|+
+2012-07-30 18:15:28.658921 : nsbasic_brc:00 00 00 00 00 16 00 00 |........|+
+2012-07-30 18:15:28.658929 : nsbasic_brc:01 00 00 00 36 01 00 00 |....6...|+
+2012-07-30 18:15:28.658937 : nsbasic_brc:00 00 00 00 00 00 00 00 |........|+
+2012-07-30 18:15:28.658945 : nsbasic_brc:00 00 00 00 E0 53 D1 22 |.....S."|+
+2012-07-30 18:15:28.658953 : nsbasic_brc:00 00 00 00 00 00 00 00 |........|+
+2012-07-30 18:15:28.658961 : nsbasic_brc:00 00 00 00 00 00 00 00 |........|+
+2012-07-30 18:15:28.658969 : nsbasic_brc:00 00 00 00 00 00 00 00 |........|+
+2012-07-30 18:15:28.658977 : nsbasic_brc:00 00 00 00 00 00 00 00 |........|+
+2012-07-30 18:15:28.658987 : nsbasic_brc:00 00 00 00 00 00 00 00 |........|+
+2012-07-30 18:15:28.658996 : nsbasic_brc:00 00 00 00 00 00 00 00 |........|+
+2012-07-30 18:15:28.659004 : nsbasic_brc:00 00 00 00 00 00 00 00 |........|+
+2012-07-30 18:15:28.659012 : nsbasic_brc:00 00 00 00 17 4F 52 41 |.....ORA|+
+2012-07-30 18:15:28.659021 : nsbasic_brc:2D 30 31 34 30 33 3A 20 |-01403:.|+
+2012-07-30 18:15:28.659029 : nsbasic_brc:64 61 74 61 20 73 61 6B |data.sak|+
+2012-07-30 18:15:28.659038 : nsbasic_brc:6E 61 73 0A |nas. |+
+2012-07-30 18:15:28.659046 : nsbasic_brc:exit: oln=0, dln=362, tot=372, rc=0+
+2012-07-30 18:15:28.659054 : nioqrc:exit+
+2012-07-30 18:16:09.583993 : nioqsn:entry+
+2012-07-30 18:16:09.584062 : nioqsn:exit+
+2012-07-30 18:16:09.584086 : nioqrc:entry+
+2012-07-30 18:16:09.584097 : nsbasic_bsd:entry+
+2012-07-30 18:16:09.584107 : nsbasic_bsd:tot=0, plen=318.+
+2012-07-30 18:16:09.584116 : nttfpwr:entry+
+2012-07-30 18:16:09.584146 : ntt2err:entry+
+2012-07-30 18:16:09.584162 : ntt2err:soc 564 error - operation=6, ntresnt[0]=530, ntresnt[1]=54, ntresnt[2]=0+
+2012-07-30 18:16:09.584171 : ntt2err:exit+
+2012-07-30 18:16:09.584178 : nttfpwr:exit+
+2012-07-30 18:16:09.584192 : nserror:entry+
+2012-07-30 18:16:09.584203 : nserror:nsres: id=0, op=67, ns=12571, ns2=12560; nt[0]=530, nt[1]=54, nt[2]=0; ora[0]=0, ora[1]=0, ora[2]=0+
+2012-07-30 18:16:09.584213 : nsbasic_bsd:exit (-1)+
+2012-07-30 18:16:09.584224 : nioqrc:send failed: bl = 1, nicbl = 1+
+2012-07-30 18:16:09.584234 : nioqper: error from nioqrc+
+2012-07-30 18:16:09.584242 : nioqper: ns main err code: 12571+
+2012-07-30 18:16:09.584250 : nioqper: ns (2) err code: 12560+
+2012-07-30 18:16:09.584258 : nioqper: nt main err code: 530+
+2012-07-30 18:16:09.584266 : nioqper: nt (2) err code: 54+
+2012-07-30 18:16:09.584275 : nioqper: nt OS err code: 0+
+2012-07-30 18:16:09.584285 : nioqer:entry+
+2012-07-30 18:16:09.584293 : nioqer: incoming err = 12150+
+2012-07-30 18:16:09.584301 : niomapnserror:entry+
+2012-07-30 18:16:09.584311 : niqme:entry+
+2012-07-30 18:16:09.584321 : niqme:reporting NS-12571 error as ORA-12571+
+2012-07-30 18:16:09.584330 : niqme:exit+
+2012-07-30 18:16:09.584337 : niomapnserror:exit+
+2012-07-30 18:16:09.584344 : nioqce:entry+
+2012-07-30 18:16:09.584352 : nioqce:exit+
+2012-07-30 18:16:09.584359 : nioqer: returning err = 12571+
+2012-07-30 18:16:09.584366 : nioqer:exit+
+2012-07-30 18:16:09.584374 : nioqrc: returning error: 12571+
+2012-07-30 18:16:09.584381 : nioqrc:exit+
+2012-07-30 18:16:09.584396 : nioqrs:entry+
+2012-07-30 18:16:09.584412 : nioqrs: state = interrupted (1)+
+2012-07-30 18:16:09.584425 : nscontrol:entry+
+2012-07-30 18:16:09.584435 : nscontrol:cmd=45, lcl=0x0+
+2012-07-30 18:16:09.584442 : nscontrol:normal exit+
+2012-07-30 18:16:09.584450 : nscontrol:entry+
+2012-07-30 18:16:09.584457 : nscontrol:cmd=1, lcl=0x0+
+2012-07-30 18:16:09.584464 : nscontrol:normal exit+
+2012-07-30 18:16:09.584476 : nioqsm:entry+
+2012-07-30 18:16:09.584485 : nioqsm: Sending break packet (1)...+
+2012-07-30 18:16:09.584493 : nscontrol:entry+
+2012-07-30 18:16:09.584500 : nscontrol:cmd=45, lcl=0x0+
+2012-07-30 18:16:09.584508 : nscontrol:normal exit+
+2012-07-30 18:16:09.584516 : nsdo:entry+
+2012-07-30 18:16:09.584525 : nsdo:cid=0, opcode=67, *bl=1, *what=17, uflgs=0x100, cflgs=0x3+
+2012-07-30 18:16:09.584534 : nsdo:rank=64, nsctxrnk=0+
+2012-07-30 18:16:09.584543 : nsdo:nsctx: state=8, flg=0x400d, mvd=0+
+2012-07-30 18:16:09.584552 : nsdo:gtn=32, gtc=32, ptn=10, ptc=8191+
+2012-07-30 18:16:09.584560 : nsdofls:entry+
+2012-07-30 18:16:09.584569 : nsdofls:DATA flags: 0x0+
+2012-07-30 18:16:09.584577 : nsdofls:normal exit+
+2012-07-30 18:16:09.584587 : nsdo:sending NSPTMK packet+
+2012-07-30 18:16:09.584596 : nspsend:entry+
+2012-07-30 18:16:09.584605 : nspsend:plen=11, type=12+
+2012-07-30 18:16:09.584614 : nttwr:entry+
+2012-07-30 18:16:09.584628 : ntt2err:entry+
+2012-07-30 18:16:09.584638 : ntt2err:soc 564 error - operation=6, ntresnt[0]=530, ntresnt[1]=54, ntresnt[2]=0+
+2012-07-30 18:16:09.584646 : ntt2err:exit+
+2012-07-30 18:16:09.584657 : nttwr:exit+
+2012-07-30 18:16:09.584668 : nspsend:0 bytes to transport+
+2012-07-30 18:16:09.584677 : nspsend:transport write error+
+2012-07-30 18:16:09.584684 : nspsend:error exit+
+2012-07-30 18:16:09.584692 : nsdo:error sending NSPTMK packet+
+2012-07-30 18:16:09.584700 : nserror:entry+
+2012-07-30 18:16:09.584709 : nserror:nsres: id=0, op=67, ns=12571, ns2=12560; nt[0]=530, nt[1]=54, nt[2]=0; ora[0]=0, ora[1]=0, ora[2]=0+
+2012-07-30 18:16:09.584719 : nsdo:nsctxrnk=0+
+2012-07-30 18:16:09.584726 : nsdo:error exit+
+2012-07-30 18:16:09.584737 : nioqsm:send-break: failed to send break...+
+2012-07-30 18:16:09.584746 : nioqper: error from send-marker+
+2012-07-30 18:16:09.584753 : nioqper: ns main err code: 12571+
+2012-07-30 18:16:09.584761 : nioqper: ns (2) err code: 12560+
+2012-07-30 18:16:09.584769 : nioqper: nt main err code: 530+
+2012-07-30 18:16:09.584776 : nioqper: nt (2) err code: 54+
+2012-07-30 18:16:09.584784 : nioqper: nt OS err code: 0+
+2012-07-30 18:16:09.584792 : nioqsm:exit+
+2012-07-30 18:16:09.584799 : nioqer:entry+
+2012-07-30 18:16:09.584808 : nioqer: incoming err = 12152+
+2012-07-30 18:16:09.584817 : niomapnserror:entry+
+2012-07-30 18:16:09.584824 : niqme:entry+
+2012-07-30 18:16:09.584833 : niqme:reporting NS-12571 error as ORA-12571+
+2012-07-30 18:16:09.584840 : niqme:exit+
+2012-07-30 18:16:09.584847 : niomapnserror:exit+
+2012-07-30 18:16:09.584854 : nioqce:entry+
+2012-07-30 18:16:09.584861 : nioqce:exit+
+2012-07-30 18:16:09.584868 : nioqer: returning err = 12571+
+2012-07-30 18:16:09.584876 : nioqer:exit+
+2012-07-30 18:16:09.584884 : nioqrs:nioqrs: Couldn't send break. returning 12571+
+2012-07-30 18:16:09.584894 : nioqrs:exit+
+2012-07-30 18:16:09.584912 : nioqds:entry+
+2012-07-30 18:16:09.584921 : nioqds: disconnecting...+
+2012-07-30 18:16:09.584933 : nsclose:entry+
+2012-07-30 18:16:09.584945 : nsvntx_dei:entry+
+2012-07-30 18:16:09.584953 : nsvntx_dei:exit+
+2012-07-30 18:16:09.584964 : nstimarmed:entry+
+2012-07-30 18:16:09.584973 : nstimarmed:no timer allocated+
+2012-07-30 18:16:09.584980 : nstimarmed:normal exit+
+2012-07-30 18:16:09.584994 : nttctl:entry+
+2012-07-30 18:16:09.585009 : nttctl:entry+
+2012-07-30 18:16:09.585021 : nsfull_cls:entry+
+2012-07-30 18:16:09.585031 : nsfull_cls:cid=0, opcode=65, *bl=0, *what=0, uflgs=0x0, cflgs=0x0+
+2012-07-30 18:16:09.585040 : nsfull_cls:nsctx: state=8, flg=0x4009, mvd=0+
+2012-07-30 18:16:09.585048 : nsdo:entry+
+2012-07-30 18:16:09.585056 : nsdo:cid=0, opcode=67, *bl=0, *what=1, uflgs=0x0, cflgs=0x1+
+2012-07-30 18:16:09.585065 : nsdo:nsctx: state=8, flg=0x4009, mvd=0+
+2012-07-30 18:16:09.585074 : nsdo:gtn=32, gtc=32, ptn=10, ptc=8191+
+2012-07-30 18:16:09.585082 : nsdo:normal exit+
+2012-07-30 18:16:09.585089 : nsdofls:entry+
+2012-07-30 18:16:09.585097 : nsdofls:DATA flags: 0x40+
+2012-07-30 18:16:09.585105 : nsdofls:sending NSPTDA packet+
+2012-07-30 18:16:09.585113 : nspsend:entry+
+2012-07-30 18:16:09.585120 : nspsend:plen=10, type=6+
+2012-07-30 18:16:09.585128 : nttwr:entry+
+2012-07-30 18:16:09.585140 : ntt2err:entry+
+2012-07-30 18:16:09.585150 : ntt2err:soc 564 error - operation=6, ntresnt[0]=530, ntresnt[1]=54, ntresnt[2]=0+
+2012-07-30 18:16:09.585158 : ntt2err:exit+
+2012-07-30 18:16:09.585165 : nttwr:exit+
+2012-07-30 18:16:09.585173 : nspsend:0 bytes to transport+
+2012-07-30 18:16:09.585181 : nspsend:transport write error+
+2012-07-30 18:16:09.585188 : nspsend:error exit+
+2012-07-30 18:16:09.585196 : nserror:entry+
+2012-07-30 18:16:09.585205 : nserror:nsres: id=0, op=67, ns=12571, ns2=12560; nt[0]=530, nt[1]=54, nt[2]=0; ora[0]=0, ora[1]=0, ora[2]=0+
+2012-07-30 18:16:09.585215 : nsdofls:exit (-1)+
+2012-07-30 18:16:09.585223 : nsbfr:entry+
+2012-07-30 18:16:09.585230 : nsbaddfl:entry+
+2012-07-30 18:16:09.585239 : nsbaddfl:normal exit+
+2012-07-30 18:16:09.585247 : nsbfr:normal exit+
+2012-07-30 18:16:09.585254 : nsbfr:entry+
+2012-07-30 18:16:09.585261 : nsbaddfl:entry+
+2012-07-30 18:16:09.585268 : nsbaddfl:normal exit+
+2012-07-30 18:16:09.585276 : nsbfr:normal exit+
+2012-07-30 18:16:09.585283 : nsfull_cls:normal exit+
+2012-07-30 18:16:09.585291 : nsiocancel:entry+
+2012-07-30 18:16:09.585303 : nsiofrrg:entry+
+2012-07-30 18:16:09.585313 : nsiofrrg:cur = 5e5f3f8+
+2012-07-30 18:16:09.585321 : nsbfr:entry+
+2012-07-30 18:16:09.585328 : nsbaddfl:entry+
+2012-07-30 18:16:09.585335 : nsbaddfl:normal exit+
+2012-07-30 18:16:09.585342 : nsbfr:normal exit+
+2012-07-30 18:16:09.585350 : nsiofrrg:exit+
+2012-07-30 18:16:09.585358 : nsiocancel:exit+
+2012-07-30 18:16:09.585365 : nsclose:closing transport+
+2012-07-30 18:16:09.585375 : nttdisc:entry+
+2012-07-30 18:16:09.585438 : nttdisc:Closed socket 564+
+2012-07-30 18:16:09.585453 : nttdisc:exit+
+2012-07-30 18:16:09.585463 : nsclose:global context check-out (from slot 0) complete+
+2012-07-30 18:16:09.585471 : nsnadisc:entry+
+2012-07-30 18:16:09.585484 : nadisc:entry+
+2012-07-30 18:16:09.585496 : nacomtm:entry+
+2012-07-30 18:16:09.585506 : nacompd:entry+
+2012-07-30 18:16:09.585513 : nacompd:exit+
+2012-07-30 18:16:09.585521 : nacompd:entry+
+2012-07-30 18:16:09.585527 : nacompd:exit+
+2012-07-30 18:16:09.585535 : nacomtm:exit+
+2012-07-30 18:16:09.585545 : nas_dis:entry+
+2012-07-30 18:16:09.585553 : nas_dis:exit+
+2012-07-30 18:16:09.585562 : nau_dis:entry+
+2012-07-30 18:16:09.585577 : nau_dis:exit+
+2012-07-30 18:16:09.585587 : naeetrm:entry+
+2012-07-30 18:16:09.585596 : naeetrm:exit+
+2012-07-30 18:16:09.585604 : naectrm:entry+
+2012-07-30 18:16:09.585613 : naectrm:exit+
+2012-07-30 18:16:09.585623 : nagbltrm:entry+
+2012-07-30 18:16:09.585632 : nau_gtm:entry+
+2012-07-30 18:16:09.585640 : nau_gtm:exit+
+2012-07-30 18:16:09.585648 : nagbltrm:exit+
+2012-07-30 18:16:09.585657 : nadisc:exit+
+2012-07-30 18:16:09.585665 : nsnadisc:normal exit+
+2012-07-30 18:16:09.585675 : nsvntx_dei:entry+
+2012-07-30 18:16:09.585682 : nsvntx_dei:exit+
+2012-07-30 18:16:09.585694 : nsopenfree_nsntx:nlhthdel from mplx_ht_nsgbu, ctx=5e5e0e0 nsntx=5e5e6c0+
+2012-07-30 18:16:09.585703 : nsiocancel:entry+
+2012-07-30 18:16:09.585710 : nsiofrrg:entry+
+2012-07-30 18:16:09.585718 : nsiofrrg:exit+
+2012-07-30 18:16:09.585725 : nsiocancel:exit+
+2012-07-30 18:16:09.585732 : nsmfr:entry+
+2012-07-30 18:16:09.585741 : nsmfr:2944 bytes at 0x5e5e6c0+
+2012-07-30 18:16:09.585748 : nsmfr:normal exit+
+2012-07-30 18:16:09.585755 : nsmfr:entry+
+2012-07-30 18:16:09.585763 : nsmfr:240 bytes at 0x5f2a610+
+2012-07-30 18:16:09.585771 : nsmfr:normal exit+
+2012-07-30 18:16:09.585778 : nsmfr:entry+
+2012-07-30 18:16:09.585785 : nsmfr:280 bytes at 0x63c010+
+2012-07-30 18:16:09.585792 : nsmfr:normal exit+
+2012-07-30 18:16:09.585803 : nladtrm:entry+
+2012-07-30 18:16:09.585820 : nladtrm:exit+
+2012-07-30 18:16:09.585828 : nsmfr:entry+
+2012-07-30 18:16:09.585836 : nsmfr:1496 bytes at 0x5e5e0e0+
+2012-07-30 18:16:09.585844 : nsmfr:normal exit+
+2012-07-30 18:16:09.585851 : nsclose:normal exit+
+2012-07-30 18:16:09.585859 : nioqds:exit+
+2012-07-30 18:16:09.585868 : nsbfree:entry+
+2012-07-30 18:16:09.585876 : nsbgetfl:entry+
+2012-07-30 18:16:09.585884 : nsbgetfl:normal exit+
+2012-07-30 18:16:09.585894 : nsbaddfl:entry+
+2012-07-30 18:16:09.585901 : nsbaddfl:normal exit+
+2012-07-30 18:16:09.585909 : nsbfree:normal exit+
+2012-07-30 18:16:09.585916 : nsbfree:entry+
+2012-07-30 18:16:09.585923 : nsbgetfl:entry+
+2012-07-30 18:16:09.585930 : nsbgetfl:normal exit+
+2012-07-30 18:16:09.585938 : nsbaddfl:entry+
+2012-07-30 18:16:09.585945 : nsbaddfl:normal exit+
+2012-07-30 18:16:09.585952 : nsbfree:normal exit+
+2012-07-30 18:16:09.585961 : nigtrm:Count in the NI global area is now 2+
+2012-07-30 18:16:09.585974 : nsbfrfl:entry+
+2012-07-30 18:16:09.585982 : nsbrfr:entry+
+2012-07-30 18:16:09.585991 : nsbrfr:nsbfs at 0x5f26470, data at 0x5f26520.+
+2012-07-30 18:16:09.585999 : nsbrfr:normal exit+
+2012-07-30 18:16:09.586006 : nsbrfr:entry+
+2012-07-30 18:16:09.586015 : nsbrfr:nsbfs at 0x5f28540, data at 0x5f285f0.+
+2012-07-30 18:16:09.586025 : nsbrfr:normal exit+
+2012-07-30 18:16:09.586033 : nsbrfr:entry+
+2012-07-30 18:16:09.586040 : nsbrfr:nsbfs at 0x5e5f480, data at 0x5e5f530.+
+2012-07-30 18:16:09.586048 : nsbrfr:normal exit+
+2012-07-30 18:16:09.586055 : nsbrfr:entry+
+2012-07-30 18:16:09.586063 : nsbrfr:nsbfs at 0x5f2a610, data at 0x5f2a9f0.+
+2012-07-30 18:16:09.586073 : nsbrfr:normal exit+
+2012-07-30 18:16:09.586082 : nsbrfr:entry+
+2012-07-30 18:16:09.586090 : nsbrfr:nsbfs at 0x62c7d0, data at 0x5f2ca10.+
+2012-07-30 18:16:09.586098 : nsbrfr:normal exit+
+2012-07-30 18:16:09.586106 : nsbfrfl:normal exit+
+2012-07-30 18:16:09.586153 : nigtrm:Count in the NL global area is now 3+ -
How to decipher SQL*Net protocols/packets?
hi,
we have a customer that sells compliance solutions that basically track and audit information at the packet level. in order to expand their customer base they would like to offer their solutions to customer that have business systems built on Oracle Forms 6.x and Pro*C. to do this they need to understand how our network communication works. is this something that is generally available? here are some details for what the partner wants from us ...
Their product intercepts the communication between a typical Db client and Db server at packet level, performs analysis on the packets and extracts the information required for SOX compliance. It's been successfully installed and working for various versions of Oracle servers and Clients, however it does not handle Oracle Forms and pro*C clients.
It also wrks for pro*c client except for bind variables and arrays.
We need information on packet formats during communication between Oracle database and Forms and pro*c clients. This will help our product to work for SOX compliance for the customers who have FORMS and pro*c clients without replacing them
I know that form Forms to DB its SQL*Net, not sure what the protocol is for PRO*C to DB communication but do we have documentation on both?Assuming you are on Windows, you can download the client installable from
http://download.oracle.com/otn/nt/oracle10g/10201/10201_client_win32.zip -- for Oracle 10g client
http://download.oracle.com/otn/nt/oracle11g/win32_11gR1_client.zip -- for Oracle 11g client
If you are looking for any other version, please mention the same. -
How to find out the size of files transferred over the SQL * Net?
I am trying to test the Advanced Compress (AC) for 11g Data Guard. When the AC is turned on, the archived log files are supposed to be compressed on the primary database server and sent over SQL*Net, then decompressed on the standby db server. We will see the file sizes are the same on both primary and standby servers. I want to verify that the AC works by monitoring how much data are sent over SQL*Net. Per Oracle, AC uses 35% less of the bandwith. That means the size of the files transferred should be at least 65% of the original size.
Is there a way to find out the size through Oracle utilities? If not, how to find out by OS utilities? OS is Solaris 5.10.
Thanks.I'm not sure this can be done via SQL*Net, but a network packet sniffer between the two servers should be able to help - you might want to contact your network team.
HTH
Srini -
Process wait SQL*Net message from dblink /SQL*Net message from client
Hi There,
We have an ETL process that we kindly need your help with. The process been running since Sun, where it transfers the data from one server (via remote query). The process was running ok till last night where it appeared
to have stopped working and/or the session is just idling doing nothing.
Here are some tests that we did to figure out what's going on:
1. when looking at the session IO, we noticed that it's not changing:
etl_user@datap> select sess_io.sid,
2 sess_io.block_gets,
3 sess_io.consistent_gets,
4 sess_io.physical_reads,
5 sess_io.block_changes,
6 sess_io.consistent_changes
7 from v$sess_io sess_io, v$session sesion
8 where sesion.sid = sess_io.sid
9 and sesion.username is not null
10 and sess_io.sid=301
11 order by 1;
logical physical
SID BLOCK_GETS reads reads BLOCK_CHANGES CONSISTENT_CHANGES
301 388131317 97721268 26687579 223052804 161334
Elapsed: 00:00:00.012. Check there is nothing blocking the session
etl_user@datap> select * from v$lock where sid=301;
ADDR KADDR SID TY ID1 ID2 LMODE REQUEST CTIME BLOCK
684703F0 6847041C 301 DX 35 0 1 0 45237 0
684714C4 684714F0 301 AE 199675 0 4 0 260148 0
619651EC 6196521C 301 TM 52733 0 3 0 45241 0
67F86ACC 67F86B0C 301 TX 458763 52730 6 0 45241 03. Check if the session is still valid:
etl_user@datap> select status from v$session where sid=301;
STATUS
ACTIVE4. Check if there is anything in long ops that has not completed:
etl_user@datap> SELECT SID, SERIAL#, opname, SOFAR, TOTALWORK,
2 ROUND(SOFAR/TOTALWORK*100,2) COMPLETE, TIME_REMAINING/60
3 FROM V$SESSION_LONGOPS
4 WHERE
5 TOTALWORK != 0
6 AND SOFAR != TOTALWORK
7 order by 1;
no rows selected
Elapsed: 00:00:00.005. Check if there is anything in long ops for the session:
etl_user@datap> r
1* select SID,SOFAR,TOTALWORK,START_TIME,LAST_UPDATE_TIME,TIME_REMAINING,MESSAGE from V$SESSION_LONGOPS where sid=301
SID SOFAR TOTALWORK START_TIM LAST_UPDA TIME_REMAINING MESSAGE
301 0 0 22-JUL-12 22-JUL-12 Gather Table's Index Statistics: Table address_etl : 0 out of 0 Indexes done
Elapsed: 00:00:00.00This is a bit odd!! This particular step have actually completed successfully on the 22nd of July, and we don't know why it's still showing in long opps!? any ideas?
6. Looking at the sql and what's it actually doing:
etl_user@datap> select a.sid, a.value session_cpu, c.physical_reads,
2 c.consistent_gets,d.event,
3 d.seconds_in_wait
4 from v$sesstat a,v$statname b, v$sess_io c, v$session_wait d
5 where a.sid= &p_sid_number
6 and b.name = 'CPU used by this session'
7 and a.statistic# = b.statistic#
8 and a.sid=c.sid
9 and a.sid=d.sid;
Enter value for p_sid_number: 301
old 5: where a.sid= &p_sid_number
new 5: where a.sid= 301
CPU physical logical seconds
SID used reads reads EVENT waiting
301 1966595 26687579 97721268 SQL*Net message from dblink 45792
Elapsed: 00:00:00.037. We looked at the remote DB where the data resides on, and we noticed that the remote session was also waiting on the db link:
SYS@destp> select a.sid, a.value session_cpu, c.physical_reads,
2 c.consistent_gets,d.event,
3 d.seconds_in_wait
4 from v$sesstat a,v$statname b, v$sess_io c, v$session_wait d
5 where a.sid= &p_sid_number
6 and b.name = 'CPU used by this session'
7 and a.statistic# = b.statistic#
8 and a.sid=c.sid
9 and a.sid=d.sid;
Enter value for p_sid_number: 388
old 5: where a.sid= &p_sid_number
new 5: where a.sid= 390
SID SESSION_CPU PHYSICAL_READS CONSISTENT_GETS EVENT SECONDS_IN_WAIT
390 136 0 7605 SQL*Net message from client 46101
SYS@destp>We have had an issue in the past where the connection was being dropped by the network when the process runs for few days, hence we have added the following to the sqlnet.ora and listener.ora files:
sqlnet.ora:
SQLNET.EXPIRE_TIME = 1
SQLNET.INBOUND_CONNECT_TIMEOUT = 6000
listener.ora:
INBOUND_CONNECT_TIMEOUT_LISTENER = 6000What else can we do and/or further investigate to work out the root cause of the problem, and may be help resolve this. We don't want to just stop and start the process again as it took few days already. We have
had a chat to the infrastructure team and they've assured us that there have been no network outages.
Also, the alert logs for both instances (local and remote) shows no errors what so ever!
Your input is highly appreciated.
Thanks
Edited by: rsar001 on Jul 25, 2012 10:22 AMRan the query on both local/remote db, and no rows returned:
etl_user@datap> SELECT DECODE(request,0,'Holder: ','Waiter: ')||vl.sid sess, status,
2 id1, id2, lmode, request, vl.type
3 FROM V$LOCK vl, v$session vs
4 WHERE (id1, id2, vl.type) IN
5 (SELECT id1, id2, type FROM V$LOCK WHERE request>0)
6 and vl.sid = vs.sid
7 ORDER BY id1, request
8 /
no rows selected
Elapsed: 00:00:00.21 -
Oracle12c SQL*NET blocked by Windows 2008 firewall - what is the correct solution?
Hello,
I have a question with regards to the SQL*NET traffic being blocked by the Windows 2008 firewall. This document shows that disabling the firewall can resolve the problem:
https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=166773506396122&id=1472931.1&displayIndex=13&_afrWindowMode=0&_adf.ctrl-state=o4dq0hlih_112
Is this really the solution?
From what I understand from other documents is that just enabling port 1521 will not resolve any issues, as SQL*NET can use redirection to other random ports. That is probably the reason why the Oracle installation does not alter any firewall settings.
What other methods do people use to connect a client to a DB server?
This document shows what other methods to use, but who uses them?
https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=166043735580557&id=68652.1&_afrWindowMode=0&_adf.ctrl-state=o4dq0hlih_78
Does anyone use the Oracle Connection Manager for example?
Thanks
RichardI configure firewall to allow DB Server to start new network connections
-
Sql*net patch version 2.3.2.1.12 down load
While I am migrating 7.3 database to 8i, system is asking for install sql net patch version 2.3.2.1.12. How can I get this patch. Is it possible to download.
Thanks/Rgds
BijuI know that I should first download and apply the AD related patches separetly. But, what is the best practice for downloading the rest of them? How does an experienced Applications DBA handle this kind of situation? I was trying to use the Patching Wizard on OAM, but the request errored out stating that "****No codeline specified". Where do I specify this when I download a list of patches? I just pasted a comma separated list of 249 patches into the PatchList field on Download Patches page.Please see these docs.
'Analyze specific Patch' via Patchwizard is failing with java.lang.NullPointerException [ID 1066985.1]
Patch Wizard Utility [ID 976188.1]
Patch Wizard FAQ [ID 976688.1]
Patch Wizard : Overview [ID 1077813.1]
Thanks,
Hussein
Maybe you are looking for
-
Title Incorrect functionality of embed tag in html loader for adobe air development Description Problem Description: If we had loaded youtube.com video url in a view stack and navigate to other index of stack or away from we UI screen within the same
-
Usage of Efxclipse Controls like FilterableTreeTable - Best practice?
Hello all, what is best practice of using efxclipse controls? currently i have linked the needed jars from the eclipse plugins folder (i.e. efxclipse controls jar) to my project to use features like the FilterableTreeTable. But.. this can not be the
-
Multiple currencies under one company code for contracts
Gooday! We have a new schenario ( In RE-FX) where we have a couple of contracts which were negotiated with the landlord that needs to be settled in Rand, whilst the company code are setup for another currency, which is dollar (caters for the bulk of
-
Anyone managed to play a slideshow with icloud Keynote? I tried in different browsers and different computers and with native keynore presentation or icloud-built. All that I get is a black screen. I am desperate!!! I need any solution for my lectur
-
PROBLEM SAVING LARGE FILES ON ACROBAT READER XI
I download a largish document (70 - 100 MB) from the on-line storage folder of a friend. But am unable to save it on my PC. I have the recent version of Acrobat Reader 11.0.5 on a PC using Windows 8 and this opens this or any other pdf file without p