Sql*net for Macintosh

Hello,
i have some clients on macintosh, and i'm looking for Sql*net
for macintosh. Can somebody tell me where i can find this
product ?
Thank's in advance

What did you end up doing?

Similar Messages

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 advance

despite 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.

SQL*NET for TCP/IP

Where can i download SQL*NET for tcp/ip?

When someone answers you, please forward the answer to my email. I am trying to connect to an Oracle db from Visual Basic, and need the component. I have downloaded software from this site, but it did not have the SQL Net.

SQL*Plus for Macintosh

I see this referenced in the oracle white papers on technet, but I can't find the software anywhere?
1) is it still available?
2) if not, can I buy an old version somewhere?
Thanks!

Hi,
The following products are orderable.
SQL*Plus V3.3.2.0.2 for Apple Macintosh PowerPC versions 7.5.3, 8.1.
Programmer/2000 has sql*plus for Apple Macintosh OS version 7.5.3.
Cheers,
Adithya
null

SQL*NET for Linux[redhat 6.2]?

if there is SQLNET for redhat6.2 , where can I find it? without the whole Oracle database

if there is SQLNET for redhat6.2 , where can I find it? without the whole Oracle database

SQL*NET V1 FOR APPC/LU6.2 TEST

제품 : SQL*NET
작성날짜 : 1995-06-05
Olivetti system에서 SQL*Net V1 for APPC/LU6.2 test 결과입니다.
customer : 한국컴퓨터
Test System : Olivetti UNIX System 2대
O / S version : SVR4 2.4
1. Server Install
1.1 Shared Memory Parameter
SHMMAX8388608
SHMSEG6
SHMMIN1
SHMMNI100
1.2 Kernel Parameter
SVMMLIM0x7FFFFFFF
HVMMLIM0x7FFFFFFF
SFSZLIM0x7FFFFFFF
HFSZLIM0x7FFFFFFF
파라메터가 이보다 적으면 oracle kernel을 만들면서 에러가 발생함.
1.3 Oracle Server Install 시 relink option 에서 Yes 선택.
LU6.2를 사용하기 위해서 반드시 해주어야 함.
1.4 Version이 2.3이하인 경우 kernel 생성시 에러 발생.
2. SQL*Net Install
2.1 Transaction Program 을 Generate.
$ $ORACLE_HOME/bin/gentpn ORACLE_SID Max_RU_size Min_RU_size
RU_size는 256 에서 1024 범위내에서 set 해야함.
ex) $ gentpn ORA7 512 512
generate 후 TPORA7 이라는 Transaction Program 이 generate
되었다는 message가 떨어짐
TP name은 ORACLE_SID 앞에 TP가 붙어서 생성.
generate후 $ORACLE_HOME/lu62/server directory 에 TPORA7
이라는 binary file이 생성.
2.2 TPORA7을 APPC Services에 등록.
sysadm tool을 이용하여 등록.
TP_Name : TPORA7
TP_Filespec : /home/oracle7/lu62/server/TPORA7
3. Connection.
3.1 Connect String
- @L:remote_LU_name::local_LU_name:mode_name:TP_name
remote_LU_name, local_LU_name, mode_name 의 value는 APPC
service에 등록이 되어있슴.
ex) $ sqlplus scott/tiger@L:BBBBBBBB::AAAAAAAA:CCCCCCCC:TPORA7
4. 특이사항.
-. gentpn시 Max_RU_size와 Min_RU_size 256으로 set:
sqlplus에서 접속시 SQL> prompt가 떨어지지 않고 waiting 상태.
반면 상대방 remote system에 session 은 연결됨.
-. gentpn시 Max_RU_size와 Min_RU_size 512으로 set:
sqlplus에서 접속은 됨.
그러나 512를 넘어서는 데이타일경우에는 ORA-6412 에러가 떨어지면서
disconnect 가 되어버림. (ORA-6412:bad read length)
remote에서 select 된 데이타는 local system 까지는 가져옴.
data size 는 548.
sqlplus 에서 array size를 '1'로 하면 정상적으로 작동.
ex) 1). select empno, ename from emp; ----> 정상
2). select * from emp; ----> disconnect
3). select empno, ename, hiredate, sal,
mgr, comm, deptno
from emp; ----> disconnect
4). set array 1
select * from emp; ----> 정상
-. gentpn시 Max_RU_size와 Min_RU_size 1024으로 set:
데이타 사이즈가 1024를 넘어설경우 동일한 현상발생.

great to hear some one talking of sql*net for dos
hi
you can't connect from v1 to net8
you can conn from v1 to v2
don't start net8
on the server
start sql*net 2.?? at the server
hope this helps
I need drivers for sql*net on dos
where can i down load these from
thnkx
Adrian Maier (guest) wrote:
: Here is my problem:
: I have some DOS applications written for Oracle 6 for DOS.
: I want that these connect to an Oracle Server using SQL*Net.
: For the start, I want to connect to the server with sqlplus,
: from DOS. For testing I have a small TCP/IP network with two
: computers:
: 1. the SERVER, running Linux(Debian 2.1) and Oracle 8.0.5
: 2. the CLIENT, running MSDOS, PSNFS as networking software
: and SQL*Net Client v1 for DOS.
: Question: Is this version of SQl*Net client compatible with
: Net8 which comes with Oracle8?
: From win95 I've bben able to connect to the server, so I
: believe the serevr is correctly configured. When I'm trying
: to connect from DOS with sqlplus, the ethernet card's leds
: blink two or three times, which means that some data is
: transmitted through network. After that, sqlplus waits for
: an indefinite period of time.
: If I stop the listener, sqlplus generates the error ORA-06136
: and asks for a new username. If I don't stop the listener,
: sqlplus remains blocked.
: In SQLNet documentation I've found:
: "ORA-06136: Error during connection handshake.
: Cause: The destination server was unable to obtain enough
: information to complete the connection.
: Action: Check that the configuration of the server is correct,
: blah, blah .... "
: I think that the server might not understand this version
: of client, but Net8 should be "backward compatible"!
: SQL*Net client v1 was the only DOS version I could find.
: Are there any other newer DOS SQl*Net clients available?
: If you have any idea about what could I do, please let me know.
: Best regards,
: Adrian Maier
: [email protected]
null

SQL*Net Client for Oracle 8i/9i ?

Hi..All,
Where do I download just the SQL*NET client for ORacle 8i/9i. ?
Regards

I have the same question: is there a stand-alone
installer for SQL*Net?No.
>
I need this for a Windows 2003 Server x64 platform.
The link provided just goes to the client, which is
far too large to transfer over my VPN connection to
a remote host.The alternative is the 'instant client'. You MIGHT be able to use that.

SQL*Net over IPC fails for normal users

When normal users try to use SQL*Net to log on to a local
database on a Linux box, they get the message "ORA-12546:
TNS:permission denied". An example of this would be the command:
sqlplus scott/tiger@MG8
The oracle unix account can execute the above without problems
and when a normal user sets ORACLE_SID and omits the SQL*Net
connect string it works fine.
Oddly, this is only a problem for connections using the IPC
protocol. If I omit the IPC section from my listener.ora
(leaving only the TCP section), non-privileged users can log on
to local databases through SQL*Net without problems.
I suppose it's not a big deal (there's not that much overhead
going through the TCP loopback port on Linux), but I'm wondering
what's wrong. SQL*Net over IPC certainly works on Solaris.
This is on a S.u.S.E 5.3 distribution of Linux.
null

Mark Gleaves (guest) wrote:
: When normal users try to use SQL*Net to log on to a local
: database on a Linux box, they get the message "ORA-12546:
: TNS:permission denied". An example of this would be the
: command
: sqlplus scott/tiger@MG8
: The oracle unix account can execute the above without problems
: and when a normal user sets ORACLE_SID and omits the SQL*Net
: connect string it works fine.
Check that your oracle executable is SUID oracle and SGID dba?
I'd have thought that would cause problems with bequeath
connections, so perhaps not.
Wierd error. You might try running an strace on the sqlplus to
see what system call fails.
-michael
null

Looking for SQL*NET Proxy

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 Rosenberger

despite 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.

How do I get SQL*Net Client for Win95?

Specifically, which software package comes with the SQL*Net Client for Windows 95?

Any of the products that requires a client side installation will include it. Things like the server will also normally include a client side instalation kit. The JDBC drivers do not come bundled with a client (not when downloaded from technet at any rate).

SQL*Net more data to dblink event for hours or days

Hello Everyone,
in our production database when we commit a transaction we call a remote procedure over dblink.
usually the call succeeds ,but every now and then a couple of sessions hang up,
when I use the session browser of Toad I notice that these sessions are waiting with the event SQL*Net more data to dblink
below are some queries and their results:
select sid,event,wait_class,wait_time,seconds_in_wait,state from gv$session_wait where sid=225
rslt:
225 SQL*Net more data to dblink Network -1 18279 WAITED SHORT TIME
select * from gv$session_wait_history where sid=225
rslt:
INST_ID     SID     SEQ#     EVENT#     EVENT     P1TEXT     P1     P2TEXT     P2     P3TEXT     P3     WAIT_TIME     WAIT_TIME_MICRO     TIME_SINCE_LAST_WAIT_MICRO
2     225     1     344     SQL*Net more data to dblink     driver id     1413697536     #bytes     8144          0     0     8     41
2     225     2     344     SQL*Net more data to dblink     driver id     1413697536     #bytes     8143          0     0     13     39
2     225     3     344     SQL*Net more data to dblink     driver id     1413697536     #bytes     8149          0     0     7     37
2     225     4     344     SQL*Net more data to dblink     driver id     1413697536     #bytes     8145          0     0     8     40
2     225     5     344     SQL*Net more data to dblink     driver id     1413697536     #bytes     8145          0     1     11394     37
2     225     6     344     SQL*Net more data to dblink     driver id     1413697536     #bytes     8143          0     0     7     37
2     225     7     344     SQL*Net more data to dblink     driver id     1413697536     #bytes     8145          0     0     7     36
2     225     8     344     SQL*Net more data to dblink     driver id     1413697536     #bytes     8138          0     0     8     37
2     225     9     344     SQL*Net more data to dblink     driver id     1413697536     #bytes     8149          0     0     8     38
2     225     10     344     SQL*Net more data to dblink     driver id     1413697536     #bytes     8149          0     1     11476     37I'm not sure but from the above results ,is it safe to conclude that I get stuck because I am caught in infinite loop trying to write to dblink?
additional notes:
<li>some times when I look at the current statement I find that the statement is a query or insert into a local table.
<li>there were some network outages.
<li>when viewing the database log files I found:Error 3135 trapped in 2PC on transaction 7.6.306086. Cleaning up.
Error stack returned to user:
ORA-03135: connection lost contact
ORA-02063: preceding line from MPF//where MPF is the name of dblinkeven though we use the DBLink to execute the procedure only without any changes on the remote DB, and we don't use 2PC.
<li> the local DB is a RAC
select * from dba_blockers
rslt:
no rows
select * from dba_waiters
rslt:
no rows
select * from gv$lock where sid=225
rslt:
INST_ID     ADDR     KADDR     SID     TYPE     ID1     ID2     LMODE     REQUEST     CTIME     BLOCK
2     0000000199D54F60     0000000199D54FB8     225     AE     100     0     4     0     20152     2
2     000000018EA18108     000000018EA18180     225     TX     1114138     251539     6     0     19654     2
select * from gv$session where sid=225
rslt:
INST_ID     SADDR     SID     SERIAL#     AUDSID     PADDR     USER#     USERNAME     COMMAND     OWNERID     TADDR     LOCKWAIT     STATUS     SERVER     SCHEMA#     SCHEMANAME     OSUSER     PROCESS     MACHINE     PORT     TERMINAL     PROGRAM     TYPE     SQL_ADDRESS     SQL_HASH_VALUE     SQL_ID     SQL_CHILD_NUMBER     SQL_EXEC_START     SQL_EXEC_ID     PREV_SQL_ADDR     PREV_HASH_VALUE     PREV_SQL_ID     PREV_CHILD_NUMBER     PREV_EXEC_START     PREV_EXEC_ID     PLSQL_ENTRY_OBJECT_ID     PLSQL_ENTRY_SUBPROGRAM_ID     PLSQL_OBJECT_ID     PLSQL_SUBPROGRAM_ID     MODULE     MODULE_HASH     ACTION     ACTION_HASH     CLIENT_INFO     FIXED_TABLE_SEQUENCE     ROW_WAIT_OBJ#     ROW_WAIT_FILE#     ROW_WAIT_BLOCK#     ROW_WAIT_ROW#     TOP_LEVEL_CALL#     LOGON_TIME     LAST_CALL_ET     PDML_ENABLED     FAILOVER_TYPE     FAILOVER_METHOD     FAILED_OVER     RESOURCE_CONSUMER_GROUP     PDML_STATUS     PDDL_STATUS     PQ_STATUS     CURRENT_QUEUE_DURATION     CLIENT_IDENTIFIER     BLOCKING_SESSION_STATUS     BLOCKING_INSTANCE     BLOCKING_SESSION     FINAL_BLOCKING_SESSION_STATUS     FINAL_BLOCKING_INSTANCE     FINAL_BLOCKING_SESSION     SEQ#     EVENT#     EVENT     P1TEXT     P1     P1RAW     P2TEXT     P2     P2RAW     P3TEXT     P3     P3RAW     WAIT_CLASS_ID     WAIT_CLASS#     WAIT_CLASS     WAIT_TIME     SECONDS_IN_WAIT     STATE     WAIT_TIME_MICRO     TIME_REMAINING_MICRO     TIME_SINCE_LAST_WAIT_MICRO     SERVICE_NAME     SQL_TRACE     SQL_TRACE_WAITS     SQL_TRACE_BINDS     SQL_TRACE_PLAN_STATS     SESSION_EDITION_ID     CREATOR_ADDR     CREATOR_SERIAL#     ECID
2     00000001993E4F58     225     445     1353611     0000000198E2FA10     198     <schema>     47     2147483644     000000018EA18108          ACTIVE     DEDICATED     198     <schema>     oracle     1234     <cluster name>     49993     unknown     JDBC Thin Client     USER     00000001968A1250     3198676106     72y8ztfzagv4a     2     02/04/2013 11:18:22 ص     33554852     00000001968A18E0     3992616824     03mm4u3qznzvs     0     02/04/2013 11:18:22 ص     33554730     158207     1     158207     1     JDBC Thin Client     2546894660          0          12206     122409     8     49354     0     94     02/04/2013 10:53:20 ص     19559     NO     NONE     NONE     NO          DISABLED     ENABLED     ENABLED     0          NOT IN WAIT               NOT IN WAIT               42844     344     SQL*Net more data to dblink     driver id     1413697536     0000000054435000     #bytes     8144     0000000000001FD0          0     00     2000153315     7     Network     -1     19553     WAITED SHORT TIME     8          19553325216     SYS$USERS     DISABLED     FALSE     FALSE     FIRST EXEC     100     0000000198E2FA10     2     004qLk^iPyp0bqw5wFDCiW0002fR000B^f

Hi ,
we managed to reproduce the case in test environment, below are the steps:
1)have 2 databases on different machines, will call the first one local, the other one remote.
2)in the local database create:
a - DBLink to remote database.
b - read data from remote database(we simply used select count(*) from dummy_table )
c - insert data into a table on the local database
d - terminate the connection between the 2 databases (disconnect either machine from the network)
e - commit on local database.
what we noticed was the following:
1)when the local database is disconnected from the network(the machine is not connected to any network at the moment): almost immediately throws an error, and issuing the following:
select * from dba_2pc_pending;we found some data .
2) when the remote database was disconnected(the local database is still connected to the network):
after 7-8 seconds an error is thrown, and issuing the following:
select * from dba_2pc_pending;did not return any data.
since this is pretty similar to our case ,we concluded that it's a network issue.
is this the correct behavior ?
as a temporary solution till the network issue is fixed ,we did the following:
1) changed the call of the remote procedure to calling a local procedure that calls the remote procedure.
2) added pragma autonomous_transaction to the local procedure.
3) at the end of the local procedure rollback the autonomous transaction.
it seems that since the global transaction does not use the DBLink database does not issue a 2PC commit.
this works in my cases since the DBLink is only issed to read data.

Looking for SQL*Net patch version 2.3.3.0.3

Hello friends:
In order to migrent a Oracle 7.3 database to a Oracle 8i DB I need a SQL*Net patch version 2.3.3.0.3. Would you please tell me where can I get it?
Thank a lot!
Zhang Weidong

Hello friends:
In order to migrent a Oracle 7.3 database to a Oracle 8i DB I need a SQL*Net patch version 2.3.3.0.3. Would you please tell me where can I get it?
Thank a lot!
Zhang Weidong

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

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

Sql*net for Macintosh

Similar Messages

Maybe you are looking for