SQL *NET Add-On

I want to install the Personnel Oracle 8 (Student Edition) with
SQL *NET Add-On Version 2.2.2.1.1 on Windows 95(win98), but the
system tell me that i have to install the SQL *NET Add-On
version 2.2.2.0.0 (patch) first.
Anybody can help me ?
Thanks
Best Regards
Carlos Barbosa
null

Carlos,
This discussion forum is specifically targeted to answer
questions on the Oracle Migration Workbench and Migration
issues. I am unfamiliar with this product and unfortunately
do not have any information that may help. Perhaps if you
called Oracle support or check out the database section
on OTN. There may be information there that will help.
Regards,
Marie
Carlos Barbosa (guest) wrote:
: I want to install the Personnel Oracle 8 (Student Edition) with
: SQL *NET Add-On Version 2.2.2.1.1 on Windows 95(win98), but the
: system tell me that i have to install the SQL *NET Add-On
: version 2.2.2.0.0 (patch) first.
: Anybody can help me ?
: Thanks
: Best Regards
: Carlos Barbosa
Oracle Technology Network
http://technet.oracle.com
null

Similar Messages

  • Unable to install SQL SSRS add-in for SharePoint

    I am unable to install MS SQL SSRS add-in for SharePoint 2010 in a two tier architecture. The following message is displayed while running the Add-in installation:
    "Please ensure Microsoft SharePoint Technologies is installed"
    The environment setup is as mentioned below:
    SharePoint Server
    Has SharePoint 2010 installed
    Hosts Central Administration.
    Has SQL 2008 Reporting Services installed.
    SQL Server:
    Has SQL 2008 R2 installed in SharePoint Integrated Mode
    Has SQL Reporting Services
    Has SharePoint Server installed, configured and joined to two tier farm.
    Could you please help resolve this issue?

    Hi Abhijit,
    According to your description, my understanding is that you got an error when you ran SQL Reporting service add-in for SharePoint 2010.
    Which version add-in did you use? Please you installed the right version.
    There are some reasons for this error:
    You are installing the wrong version of add-in. For example, installing 32bit add-in on x64 machine or vice versa.
    You haven’t install SharePoint on the report server machine
    Your SharePoint installation is not recognized by the add-in. Either cases, you need to reinstall SharePoint.
    Some similar articles for your reference:
    http://geekswithblogs.net/naijacoder/archive/2010/06/28/140653.aspx
    http://blogs.devhorizon.com/reza/2008/10/16/shifting-from-ssrs-2008-native-to-integrated-for-good/
    About installing reporting service add-in, please refer to the links:
    http://stevemannspath.blogspot.com/2012/10/reporting-services-2012-integrated-mode.html
    http://msdn.microsoft.com/en-us/library/aa905871.aspx
    Best Regards
    Wendy
    Forum Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Wendy Li
    TechNet Community Support

  • 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

  • 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.trc

    By 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

  • Error PL Developer - SQL*Net not properly installed PL Developer

    - ok i am getting this error after i have installed my oracle 10 client on a windows 7 OS.
    - trying to use PL DEVELOPER version 6 (which is free ).
    error :
    SQL*Net not properly installed PL Developer
    -any ideas?
    Thanks in advance

    Maybe PL/SQL Developer is trying to use some missing registry values, or a missing ORACLE_HOME environment variable
    Check the ORACLE_HOME is pointing to your 10g client path, and then try to add the following entries in the registry, making a .reg file with the following, replacing with your paths, and executing (from Windows PATH variable
    [HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE]
    "inst_loc"="C:
    Program Files\\Oracle
    Inventory"
    "API"="D:\\oracle\\product\\10.1.0
    db_1"
    [HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\ALL_HOMES]
    "HOME_COUNTER"="1"
    "DEFAULT_HOME"="HOME0"
    "LAST_HOME"="0"
    [HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\ALL_HOMES\ID0]
    "NAME"="Oracle - ORACLE_HOME"
    "PATH"="D:\oracle\product\10.1.0\db_1"
    "NLS_LANG"="NA"
    [HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOME0]
    "ID"="0"
    "ORACLE_GROUP_NAME"="Oracle - ORACLE_HOME"
    "ORACLE_HOME_NAME"="ORACLE_HOME"
    "ORACLE_HOME"="D:\\oracle\\product\\10.1.0\\db_1"
    I hope this help
    Regards,
    Alfonso Vicente

  • Oracle 10g: Initialization error SQL*Net not properly installed

    Hello, everyone.
    I have an app that uses Oracle 10g client to connect a remote Oracle 10g server.
    I encountered a pop-up error saying
    " Initialization error SQL*Net not properly installed. "
    OracleHomeKey: SOFTWARE\ORACLE
    OracleHomeDir:
    Please advise a fix.
    Thanks.

    Maybe PL/SQL Developer is trying to use some missing registry values, or a missing ORACLE_HOME environment variable
    Check the ORACLE_HOME is pointing to your 10g client path, and then try to add the following entries in the registry, making a .reg file with the following, replacing with your paths, and executing (from Windows PATH variable
    [HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE]
    "inst_loc"="C:
    Program Files\\Oracle
    Inventory"
    "API"="D:\\oracle\\product\\10.1.0
    db_1"
    [HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\ALL_HOMES]
    "HOME_COUNTER"="1"
    "DEFAULT_HOME"="HOME0"
    "LAST_HOME"="0"
    [HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\ALL_HOMES\ID0]
    "NAME"="Oracle - ORACLE_HOME"
    "PATH"="D:\oracle\product\10.1.0\db_1"
    "NLS_LANG"="NA"
    [HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOME0]
    "ID"="0"
    "ORACLE_GROUP_NAME"="Oracle - ORACLE_HOME"
    "ORACLE_HOME_NAME"="ORACLE_HOME"
    "ORACLE_HOME"="D:\\oracle\\product\\10.1.0\\db_1"
    I hope this help
    Regards,
    Alfonso Vicente

  • SQL net easy configuration

    I can't connect Developer 2000 at a client site with the Database on th Server:
    AFTER INSTALLING THE DEVELOPER 2000 R2.1 ON THE CLIENT MACHINE(WIN 98),
    I NEED TO CONNECT HIM TO THE ORACLE DATABASE(ORACLE 8 ENTERPRISE EDITION)
    ON THE SERVER(WINNT),
    I DEFINED THE FOLLOWING SERVICE (DB ALIAS) ON THE ORACLE SERVER(TNSNAMES.ORA):
    XXX.WORLD =
    (DESCRIPTION =
    (ADDRESS =
    (PROTOCOL = TCP)
    (HOST = 3.1.1.1)
    (PORT = 1521)
    (CONNECT_DATA = (SID = ORCL)
    WHAT I DID WAS THAT I WENT TO SQL NET EASY CONFIGURATION, AT CLIENT MACHINE
    AND SELECT TO ADD DATABASE ALIAS,
    THEN I ENTERED THE DB ALIAS NAME: KOKO (FOR EXAMPLE)
    THEN I ENTERED THE TCP\IP ADDRESS OF THE SERVER: 3.1.1.1,
    THEN I ENTERED THE DATA BASE INSTANCE : ORCL,
    THEN I CONFIRMED THE OPERATION AND EXIT THE SQL NET EASY CONFIGURATION.
    THEN I WENT TO THE TNSNAMES.ORA FILE, AND CHECK FOR THE DEFININTION, AND IT
    WAS OK. AND AS FOLLOWS:
    KOKO.WORLD =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS =
    (COMMUNITY = TCP.WORLD)
    (PROTOCOL = TCP)
    (HOST = 3.1.1.1)
    (PORT = 1521)
    (ADDRESS =
    (COMMUNITY = TCP.WORLD)
    (PROTOCOL = TCP)
    (HOST = 3.1.1.1)
    (PORT = 1526)
    (CONNECT_DATA = (SID = ORCL)
    THEN I TRYED TO CONNECT TO THE DATABASE USING SQLPLUS8 FROM THE USER MACHINE,
    BUT I GET THIS ERR MSG;
    ERROR:
    ORA-12154: TNS:COULD NOT RESOLVE SERVICE NAME
    I TRYED TO GO TO ORACLE REGISTRY FILE AND ADD A STRING LOCAL: XXX
    THIS XXX IS THE NAME OF THE DATABASE ALIAS ON THE SERVER.
    AFTER THAT I TRYED TO CONNECT TO THE DATABSE, AND I GOT THE SAME ERR MSG:
    ERROR MSG:
    ERROR:
    ORA-12154: TNS:COULD NOT RESOLVE SERVICE NAME
    IF YOU HAVE AN IDEA, I WILL APPRECIATE SHARING IT.
    null

    hi,
    If you are installing D2K on '98 please insure the following:
    1. does the cient machine have orawin95/98 folder?
    2. In orawin95/net80/admin you said you have TNSNAMES.ORA but do you also have SQLNET.ORA with a proper configuration pointing to TNSNAMES.ORA?
    Tushar

  • SQL*Net Secure Protocol?

    Anyone,
    My security auditors are breathing down my back... Is SQL*Net considered a secure communication protocol?
    Can someone with a Packet Sniffer siphen off my SQL*Net communications and obtain any data being transfered through it? Namely Passwords and DB connect paramateters, data is also a concern but less.
    This is via an Internal Network not over the internet..
    Thanks in advance,
    Milller

    yes.
    you an encrypt sql*net communications within the network.
    ASO provides different bult-in mechanisms.
    you just add the following entries with appropriate values
    and your sqlnet is encrypted.
    SQLNET.ENCRYPTION_SERVER = <ACCEPTED, REJECTED, REQUESTED or REQUIRED>
    SQLNET.ENCRYPTION_CLIENT = <ACCEPTED, REJECTED, REQUESTED or REQUIRED>
    SQLNET.CRYPTO_SEED = <STRING>
    only disadvantage is
    in 8i your internal account will be locked!
    so you cant use dbstart/dbshut scripts.
    workaoround is to script the following in your dbstart/dbshut
    1. move or rename sqlnet.ora to something.ora
    2. proceed with dbstart/dbshut.
    3. move or rename something.ora to sqlnet.ora

  • WINDOWS 용 SQL*NET 사용 시 TNS-12203

    제품 : SQL*NET
    작성날짜 : 2004-11-09
    WINDOWS 용 SQL*NET 사용 시 TNS-12203
    ====================================
    PURPOSE
    TNS-12203 "TNS:unable to connect to destination"은 여러가지 원인 때문에
    발생할 수 있습니다. 여기서는 가장 일반적인 몇 가지 원인을 설명합니다.
    1. WINDOWS 용 TCP/IP 어댑터를 설치하지 않은 상태에서 연결하려 하면 TNS-
    12203이 발생할 수 있습니다. SQL*NET TCP/IP V2는 SQL*NET V2와 V2 TCP/IP
    어댑터 등 두가지 제품으로 구성됩니다. 이들은 별도의 두 키트로 되어 있는데,
    반드시 두 키트를 모두 설치해야 합니다.
    2. TNS-12203 에러는 WINDOWS 용 ORACLE SQL*NET소프트웨어가 ORACLE HOME
    디렉토리를 찾을 수 없다는 의미일 수 있습니다. 이 문제를 해결하려면, 먼저
    WIN.INI 화일의 ORACLE 부분에 다음 항목이 있는지 확인하십시오.
    [ORACLE]
    ORA_CONFIG=C:\WINDOWS\ORACLE.INI
    WINDOWS디렉토리가 C:\WINDOWS가 아니면, 위 행의 C:\WINDOWS 부분을 그
    이름으로 바꾸십시오. 그런 다음, ORACLE 소프트웨어를 다시 설치하십시오.
    ORACLE.INI 화일이 있으면 그 ORACLE.INI 화일에 다음 행이 있는지
    확인하십시오.
    ORACLE_HOME=C:\ORAWIN
    ORACLE 홈 디렉토리가 C:\ORAWIN이 아니면 위 행의 C:\ORAWIN 부분을 그
    이름으로 바꾸십시오.
    3. TNSNAMES.ORA가 ORACLE 홈 디렉토리 아래의 NETWORK\ADMIN에 있는지
    확인하십시요. ORACLE 홈 디렉토리는 ORACLE.INI(또는 WIN.INI의
    ORA_CONFIG 매개변수가 지시하는 파일)의 ORACLE_HOME 에 의해 정의됩니다.
    4. 서버 쪽에서 실행 중인 SQL*NET V2 TCP/IP Listener가 없어도 TNS-12203이
    발생할 수 있습니다. 서버 쪽에서 실행 중인 SQL*NET V2가 있는지 확인하십시오.
    서버 쪽에서 Listener Control 유틸리티(LSNRCTL)를 사용하면 서버의 V2
    Listener가 실행 중인지 확인할 수 있습니다. 서버에서 "LSNRCTL STATUS"
    명령을 실행하십시오. Listener Control 유틸리티에 대해서는 SQL*NET
    Administrator's Guide를 참조하십시오.
    5. 연결할 SERVICES 이름에 대해 CONNECT DESCRIPTOR에 정확한 ADDRESS
    매개 변수를 지정했는지 확인하십시오. 정확한 ADDRESS 매개변수를 사용 중인지
    확인하는 방법은, WINDOWS 클라이언트에서 사용 할 것과 같은 ADDRESS 매개
    변수를 가진 TNSNAMES.ORA를 사용하여 서버에서 루프백을 해 보는 것입니다.
    루프백을 수행한다는 것은 데이타베이스와 같은 기계에서 SQL*DBA 등을
    호출하고 연결 스트링을 지정함으로써 SQL*NET V2를 통해 연결한다는 뜻입니다.
    6. JSB VSL 소켓이 초기화되지 않으면 TNS-12203이 발생할 수 있습니다. 이
    문제를 해결하려면 다음 사항을 점검하여 JSB VSL 레이어가 정확하게
    초기화되었는 지 확인하십시요.
    1) ORACLE.INI 파일(또는 WIN.INI의 ORA_CONFIG 매개변수가 지시하는 파일)의
    업체키 매개변수 TCP_VENDOR가 정확하게 설정되었는 지 확인하십시요
    2) ORACLE_HOME\BIN 디렉토리에 MSOCKLIB.DLL이 있는지 확인하십시요.
    3) ORACLE_HOME\BIN 디렉토리에 선택된 JSB 업체 특유의 DLL이 있는지, 또는
    그 JSB 업체 특유의 TSR 파일이 실행되는 지 확인하십시요.
    4) WINDOWS 홈 디렉토리에 VSL.INI 파일이 있는 지 확인하십시요.
    7. TNS-12203에 이어 실제 문제가 무엇인지 더 자세하게 나타내 주는
    또 다른 에러가 발생할 수 있습니다. 화면에서 다른 에러가 보이지 않으면
    ORACLE_HOME\NETWORK\LOG 디렉토리의 SQLNET.LOG 파일을 점검하십시오.

    change (Port = 1526) to 1521 and try to connect
    add the entry to tnsnames.ora file on both client and server
    ORCL =
      (DESCRIPTION =
        (ADDRESS = (PROTOCOL = TCP)(HOST =192.168.25.16 )(PORT = 1521))
        (CONNECT_DATA =
          (SERVER = DEDICATED)
          (SERVICE_NAME = orcl)
    EXTPROC_CONNECTION_DATA =
      (DESCRIPTION =
        (ADDRESS_LIST =
          (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
        (CONNECT_DATA =
          (SID = PLSExtProc)
          (PRESENTATION = RO)
      )Edited by: rajeysh on May 15, 2011 3:02 PM

  • Get sql*net to use perl module (DBI and DBD::Oracle)

    Hi,
    I'm doing a perl script which tests oracle database availability
    Now to install it on a Unix computer i need some Oracle files to use the DBI and DBD::Oracle module
    I saw in differents forums that i need to install SQL*NET to have those files but i know few things about Oracle products and then i don't know which package i have to download to have it.
    If someone have the answer please mail me !!([email protected])
    Thanks a lot
    Nicolas Minant

    Ok, so i got it working as below. putting the details steps for someone to refer (or may myself in future if i forget)
    - Install Perl DBI module
    - install below 3 rpm for oracle instant client from (http://www.oracle.com/technetwork/topics/linuxx86-64soft-092277.html)
    oracle-instantclient11.2-basic-11.2.0.3.0-1
    oracle-instantclient11.2-devel-11.2.0.3.0-1
    oracle-instantclient11.2-sqlplus-11.2.0.3.0-1
    I am using 64 bit linux box, so choose your RPM accordingly.
    - set below variables:
    LD_LIBRARY_PATH=/usr/lib/oracle/11.2/client64/lib
    ORACLE_HOME=/usr/lib/oracle/11.2/client64
    also add ORACLE_HOME to your PATH variable
    - download DBD::Oracle ver 1.44 from
    - untar the module and run below commands in given sequence:
    perl Makefile.PL
    make
    make install
    DONE !!!
    Issues I had faced were due to the wrong LD_LIBRARY_PATH. i had set it to "/usr/lib/oracle/11.2/client64" whereas the correct value is "/usr/lib/oracle/11.2/client64/lib"
    certainly, this was a great learning for a newbie like me. i have spent 8 years as Linux sysadmin and have done a lot of perlscripting bt never had to deal with oracle stuff ever. hence this was a learning for me.
    Thanks everyone for your responses. you guys pushed me to right direction. thanks for the Great HELP.

  • 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 AM

    Ran 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
    Richard

    I 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
    Biju

    I 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