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

Similar Messages

  • OPS에서 SYSTEM FAIL로 인한 SQL*NET FAIL-OVER 에 대처할 수 있는 SETUP

    제품 : SQL*NET
    작성날짜 : 1997-11-20
    OPS에서 SYSTEM FAIL로 인한 SQL*NET FAIL-OVER 에 대처할 수 있는 SETUP
    ==================================================================
    OPS에서 여러 node를 사용 중 한 시스템이 fail이 생길 경우 사용자의
    application 수정없이 fail-over 시스템으로 접속하는 방법입니다.
    제약 조건 > SQL*NET V2.3.2.1.6 for windows 95
    SQL*NET V2.3.2.1.8 for windows
    상기의 Version 이상 이라야 하며 위의 경우 tnsnames.ora 화일의
    configuration에 대한 setup 내용입니다.
    Example tnsnames.ora for SQL*Net 2.3 fail-over.
    When a user requests to connect to <alias>, sqlnet will attempt to
    connect to the address in the first description in the
    description_list, if that fails, it will try to connect to the address
    in the next description in the description_list.
    You can have as many descriptions in the description_list as needed.
    The client will only receive an error if all the descriptions fail.
    <alias>=
    (description_list=
    (description=
    (address_list=
    (address=
    (protocol=tcp)
    (host=<server 1>)
    (port=1521)
    (connect_data=
    (sid=<sid1>)
    (description=
    (address_list=
    (address=
    (protocol=tcp)
    (host=<server 2>)
    (port=1521)
    (connect_data=
    (sid=<sid2>)
    )

  • 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

  • FUTURE TCP 와 SQL*NET V2 사용시 PERFORMANCE

    제품 : SQL*NET
    작성날짜 : 1995-05-04
    Subject: Re: Know How..[ 2. Future/tcp 사용시]
    두번째 항목의 경우 future/tcp 에서 Named Server를 잘못설정하면 Host의
    Named Server를 다 찾고서, 없으면 Client의 host file을 뒤져서 자기 host
    alias로 처리하는 경우가 있었습니다.(1-2초 걸리던 connection time이 12초
    까지 걸렸음)
    경남은행에도 SLIP으로 테스트를 하는데 SQL*Net을 통하면 엄청 늦다고 계속
    불평 해서 가서 보니까 SQL*Net의 문제가 아니라 future/tcp의 Client host
    file과 Named Server의 Host file의 불일치 때문으로 판명난 적이 있었습니다.
    이런경우,
    1. Client에서 future/tcp의 install program으로 Named Server를 없애든지
    2. Host와 Client의 Host file을 일치 시키면 되었습니다.
    sql*net v1 & v2 test 지원 중 발견된 사항입니다.
    1.
    아직도 많은 사용자가 sql*net v2 가 별 효과가 없다고 생각합니다. 이런
    user는 주로 MTS 환경으로 setting은 하였으되 shared server와 dispatcher를
    한개씩 뛰우고 사용하고 있었읍니다.
    근본적으로 oracle의 mts는 FIFO 방식으로 SQL을 처리하기 때문에 server가
    하나만 떠 가지고는 당연히 sql*net v1의 dedicated server 보다 느리게
    처리됩니다.
    따라서 mts 환경으로 setup 할 때에는 최소한 shared server와 dispatcher를
    2개 이상씩 (3개이상 권유) 뛰워서 사용할 수 있도록 하기 바랍니다.
    일부에서는 이런이유로 oracle mts 기능이 별볼일 없더라 라고 오해하며
    옆사람에게도 전달하고 있습니다.
    2.
    future tcp/ip 사용시에 tnsnames.ora에 host name 을 사용하면 sql*net v2 가
    v1보다 3배 정도 더 느리게 되는데 이때에는 ip address number를 직접사용하면
    됩니다.
    삼성전관 pdss test시 connection time : sql*net v1 --> 6-8초
    sql*net v2 host name --> 25초
    sql*net v2 ip number --> 2-3초

    Yes, it seems to be a kernel bug. Previously, my wife used Windows for years and nothing like this happened. Now, she tells a lot about Linux systems :-)
    An example of this very-ugly-workaround for somebody who'll find this topic struggling with the same problem:
    $ cat /etc/pm/sleep.d/99_fix_time_shift
    #!/bin/bash
    # fixing https://bbs.archlinux.org/viewtopic.php?id=173487
    case "$1" in
    suspend)
    date +%s > /tmp/suspend.log
    resume)
    was=`cat /tmp/suspend.log`
    now=`date +%s`
    # time shifts for 68 hours
    if [ $now -gt `expr $was + 244800` ]; then
    date -s "`date -R --date="-68 hours ago"`"
    ## sleep 30; ntpdate ntp.ubuntu.com
    fi
    esac
    Last edited by shurup (2014-03-26 16:25:55)

  • [Error] Microsoft SQL Server 2008 Setup. Error reading from file msdbdata.mdf

    Hi all
    I'm trying to install SQL 2008 Express on my Computer: Hp compact DX7300 Slim tower.
    and get this error:
    TITLE: Microsoft SQL Server 2008 Setup
    The following error has occurred:Error reading from file d:\8268cd7b247d294de359c9\x86\setup\sql_engine_core_inst_msi\PFiles\SqlServr\MSSQL.X\MSSQL\Binn\Template\msdbdata.mdf.  Verify that the file exists and that you can access it.
    Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup.
    For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.0.1823.0&EvtType=0xF45F6601%25401201%25401
    Log file
    Overall summary:
      Final result:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
      Exit code (Decimal):           -2068643839
      Exit facility code:            1203
      Exit error code:               1
      Exit message:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
      Start time:                    2014-12-09 23:22:03
      End time:                      2014-12-09 23:40:28
      Requested action:              Install
      Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141209_232121\sql_engine_core_inst_Cpu32_1.log
      Exception help link:           http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.0.1823.0
    Machine Properties:
      Machine name:                  VISTA-PC
      Machine processor count:       2
      OS version:                    Windows Vista
      OS service pack:               Service Pack 1
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x86
      Process architecture:          32 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                    Feature                
                     Language             Edition              Version         Clustered 
    Package properties:
      Description:                   SQL Server Database Services 2008
      SQLProductFamilyCode:          {628F8F38-600E-493D-9946-F4178F20A8A9}
      ProductName:                   SQL2008
      Type:                          RTM
      Version:                       10
      SPLevel:                       0
      Installation location:         d:\8268cd7b247d294de359c9\x86\setup\
      Installation edition:          EXPRESS
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      False
      AGTSVCACCOUNT:                 NT AUTHORITY\NETWORK SERVICE
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Disabled
      ASBACKUPDIR:                   Backup
      ASCOLLATION:                   Latin1_General_CI_AS
      ASCONFIGDIR:                   Config
      ASDATADIR:                     Data
      ASDOMAINGROUP:                 <empty>
      ASLOGDIR:                      Log
      ASPROVIDERMSOLAP:              1
      ASSVCACCOUNT:                  <empty>
      ASSVCPASSWORD:                 *****
      ASSVCSTARTUPTYPE:              Automatic
      ASSYSADMINACCOUNTS:            <empty>
      ASTEMPDIR:                     Temp
      BROWSERSVCSTARTUPTYPE:         Disabled
      CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141209_232121\ConfigurationFile.ini
      ENABLERANU:                    True
      ERRORREPORTING:                False
      FEATURES:                      SQLENGINE,REPLICATION
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  <empty>
      FTSVCPASSWORD:                 *****
      HELP:                          False
      INDICATEPROGRESS:              False
      INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
      INSTALLSHAREDWOWDIR:           C:\Program Files\Microsoft SQL Server\
      INSTALLSQLDATADIR:             <empty>
      INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
      INSTANCEID:                    SQLExpress
      INSTANCENAME:                  SQLEXPRESS
      ISSVCACCOUNT:                  NT AUTHORITY\NetworkService
      ISSVCPASSWORD:                 *****
      ISSVCSTARTUPTYPE:              Automatic
      MEDIASOURCE:                   d:\8268cd7b247d294de359c9\
      NPENABLED:                     0
      PID:                           *****
      QUIET:                         False
      QUIETSIMPLE:                   False
      RSINSTALLMODE:                 FilesOnlyMode
      RSSVCACCOUNT:                  <empty>
      RSSVCPASSWORD:                 *****
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         *****
      SECURITYMODE:                  <empty>
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLSVCACCOUNT:                 NT AUTHORITY\NETWORK SERVICE
      SQLSVCPASSWORD:                *****
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           VISTA-PC\VISTA
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  False
      TCPENABLED:                    0
      X86:                           False
      Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141209_232121\ConfigurationFile.ini
    Detailed results:
      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       SQL Server Replication
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141209_232121\SystemConfigurationCheck_Report.htm
    I will very appriciate if someone can help me solve it. I was trying to set Full control for my account in Properties/Security of root folder and try again but error is still.
    Many thanks

    Hi Foreverduy,
    Before you run SQL Server 2008 express setup, make sure that you have installed Windows installer 4.5 and.NET Framework 3.5 SP1 manually. For more information about the process, please refer to the article:
    http://msdn.microsoft.com/en-us/library/ms143506(v=sql.100).aspx. Moreover, please turn off all the third-party softwares which could prohibit the installation process.
    According to your error message, the issue could be due to that your account has no rights to install SQL Server, or the corruption on the media.
    Firstly, please ensure that your account has admin rights. Also make sure that you right-click the setup.exe and choose “Run as administrator” to complete the installation.
    Secondly, please check if "msdbdata.mdf" file exists at d:\8268cd7b247d294de359c9\x86\setup\sql_engine_core_inst_msi\PFiles\SqlServr\MSSQL.X\MSSQL\Binn\Template. If it exists, please make sure that your account has read permission to the extracted
    folder.
    However, if the file doesn't exist in the extraction, the media could be corrupt. Please download the
    media
    again and check if the issue still occurs.
    Regards,
    Michelle Li

  • SQL*NET V1, V2의 STATUS를 확인하는 방법

    제품 : SQL*NET
    작성날짜 : 1995-11-06
    * SQL*NET V 1의 적절한 사용 방법
    ORASRV의 Permission, Owner 및 Group은 다음과 같이 설정이 되어 있어야 하며
    파일의 Size는 Version에 따라 다를 수 있다.
    -rwsr-xr-x 1 oracle dba 7544832 Jul 21 20:35 oracle
    -rwsr-xr-x 1 root dba 303104 Jul 5 19:24 orasrv
    만일 위와 같지 않다면 Unix 명령 프롬프트에서 다음을 수행하여 모드를 바꾸어
    준다.
    #chmod 4755 oracle
    #chown root orasrv <= orasrv의 owner는 반드시 root로 되어야 합니다.
    #chmod 4755 orasrv
    1. SQL*NET V1을 사용하면서 가장 일반적으로 orasrv를 시작 및 정지 하는
    경우이다.
    #tcpctl start ( stop )
    2. orasrv의 현상태를 확인하는 방법
    #tcpctl status
    tcputl: Status summary follows
    Server is running :
    Started : 4-OCT-95 15:58:48
    Total connections : 0
    Total rejections : 0
    Active subprocesses : 0
    ORACLE SIDs : RC,ORA722
    Default SID : (null)
    Logging mode is ENABLED.
    DBA logins are DISABLED.
    OPS$ logins are ENABLED.
    OPS$ROOT logins are DISABLED.
    Orasrv is detached from the terminal.
    Break mode = OUT OF BAND.
    Debug level = 1
    Timeout (on orasrv handshaking) = 5 seconds.
    Length of listen queue = 10
    Orasrv logfile = /users2/oracle7/tcp/log/orasrv.log
    Orasrv mapfile = /etc/oratab
    * SQL*NET V2의 적절한 사용 방법
    SQL*NET V2를 사용하는데 있어서 갖추야 할 파라미터 파일이 있다.
    기본으로 listener.ora,tnsnames.ora,sqlnet.ora가 $ORACLE_HOME/network/admin
    directory내에 있어야 합니다.(상기 파일에 대한 configuration은 SQL*NET
    Administrator's Guide v 2.0을 참고하시기 바랍니다.)
    1. SQL*NET V2을 사용하면서 가장 일반적으로 listener를 시작 및 정지 하는
    경우이다.
    #lsnrctl start (stop)
    2. Oracle과 Listener의 Process를 확인하는 방법
    $ ps -ef |grep ORA7
    ora7 1343 1 7 Aug 22 ? 30:53 ora_dbwr_ORA7
    ora7 1342 1 7 Aug 22 ? 0:32 ora_pmon_ORA7
    ora7 1346 1 7 Aug 22 ? 0:00 ora_reco_ORA7
    ora7 1347 1 7 Aug 22 ? 0:00 ora_s000_ORA7
    ora7 1345 1 7 Aug 22 ? 12:25 ora_smon_ORA7
    ora7 1344 1 7 Aug 22 ? 58:57 ora_lgwr_ORA7
    ora7 1348 1 7 Aug 22 ? 0:00 ora_s001_ORA7
    ora7 8036 1 7 Aug 22 ? 0:00 /ora/ora7/bin/tnslsnr LISTENER -
    inherit
    ora7 24279 1342 7 09:40:16 ? 0:05 ora_d001_ORA7
    ora7 899 1342 7 14:54:36 ? 0:21 ora_d000_ORA7
    3. Listener의 현상태를 확인하는 방법
    $ lsnrctl service
    LSNRCTL for 88open UNIX: Version 2.0.14.0.0 - Production on 24-AUG-94
    09:19:37
    Copyright (c) Oracle Corporation 1993. All rights reserved.
    Connecting to (ADDRESS=(PROTOCOL=IPC)(KEY=ORA7))
    Services Summary...
    ORA7 has 3 service handlers
    DEDICATED SERVER established:0 refused:0
    DISPATCHER established:0 refused:0 current:0 max:60 state:ready
    D000 (machine: AViiON, pid: 899)
    (ADDRESS=(PROTOCOL=tcp)(DEV=6)(HOST=152.68.1.11)(PORT=2753))
    DISPATCHER established:0 refused:0 current:0 max:60 state:ready
    D002 (machine: AViiON, pid: 1357)
    (ADDRESS=(PROTOCOL=ipc)(DEV=5)(KEY=#1357.1))
    The command completed successfully
    4. SQL*NET V2를 MTS와 DEDICATE방식으로 사용코자 할때.
    MTS 방식 : ps -ef | grep s0 으로 시작하는 공유 process 를
    띄어두고, tnsnames.ora 에 MTS 와 같은 alias 를
    사용하여 접속한 session 들이 각각의 oracle process 를
    띄우지 않고, 공유 process 를 사용하는 방법
    dedicate 방식 :
    tnsnames.ora 에 MTS_DED 와 같은 alias 를 사용하거나, alias 없이
    server 에서 접속하는 유저들은 각각의 oracle process 를
    기동시켜고 공유하지 않는다
    $cd $ORACLE_HOME/network/admin/tnsnames.ora
    MTS =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS =
    (PROTOCOL = TCP)
    (HOST = Hostname)
    (PORT = 1521)
    (CONNECT_DATA =
    (SID = ORA7)
    MTS_DED =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS =
    (PROTOCOL = TCP)
    (HOST = Hostname)
    (PORT = 1521)
    (CONNECT_DATA =
    (SID = ORA7)
    (SRVR = DEDICATED)
    5. SQL*NET V2 Pipe Adapter를 사용중이라면 ps command를 통해서
    oracleSID (LOACL=YES)라는 Shadow Process로써 확인 할 수 있다.

    오랬만에 게시판에 들어오니 좀 썰렁하네요..
    자주 들어와서 확인좀 하겠습니다.
    SQL*NET V1 프로세스 수동 기동 중지는
    기동
    tcpctl start 중이
    tcpctl stop

  • SQL*NET SESSION의 DEAD CONNECTION 처리 방법

    제품 : SQL*NET
    작성날짜 : 1996-04-03
    SQL*NET SESSION의 DEAD CONNECTION 처리 방법
    ==========================================
    server에서 수행 중이던 프로그램이 비정상 종료한 경우에는 오라클의 smon이
    자동으로 detection하여 수행 중이던 transaction을 rollback하여
    정리하여 준다.
    그러나, Client Server 환경에서 PC를 Client로 사용 시 비정상적인 방법으로
    Server와 Disconnect 하면 Server 쪽에 있는 Dedicated Server가 남아 있다.
    이는 Sql*net V1 & V2에서 발생하던 문제로 Sql*net V2.1 이후에는 아래와
    같은 방법을 이용하면 Dead connection이 정상적으로 Disconnect 된다.
    * 환경 : Server - Sql*net tcp/ip V2.1.3
    Client - Sql*net V2.0
    * Setup 방법 : Server와 Client에 있는
    $ORACLE_HOME/network/admin/sqlnet.ora에
    sqlnet.expire_time=n
    으로 setting 한다.
    여기서 n은 분 단위이며 실제 disconnect는 n분보다 더 걸린다.
    일반적으로 sqlnet.expire_time=1로 설정하면 적당하다.

    Hi,
    Probe send - client and application still there - all fine
    Network cable on the client is removedAt the above stage if the Sever sents a probe then if does not receive any message from Client it is treated as DCD. (It will receive any error code or negative response from client instead of any active status communication)
    Application is shut down
    (Optionally the computer is rebooted)
    Network cable is reattached
    Next probe send from server
    At this point, the client is reachable, the Oracle NET component on the client is there, but the application on the client is gone without properly saying good bye to the DB server.
    Would DCD detect the dead connection in this sceanrio?If my above comment is dismissed and your case or assumptions continues, then we need to check the SQL_EXPIRE time which you have connected. If the every thing happens with in the time setted for Expire time then, still it will treat as DCD, your session is getting terminated the system got rebooted.
    You understanding with DCD is correct.
    We see sessions in V$SESSIONS that don't have a process on the client any more. We have SQLNET.EXPIRE_TIME set to 2 minutes on the server, but still these sessions show up after days. Sessions show up as inactive and are waiting on "SQL*NET message from client" for hours and days.See basically INACTIVE and DCD are different. Slight difference exits. As you said you find inactive sessions. If you want to cleanup those inactive sessions, as per oracle documenation, you can create a custom profile as per your requrement and assign some IDLE_TIME and update the respective user profile. That might help you out.
    - Pavan Kumar N

  • WINDOWS 용 SQL*NET 사용 시 ORA-6122

    제품 : SQL*NET
    작성날짜 : 1995-11-10
    WINDOWS 용 SQL*NET 사용 시 ORA-6122
    ===================================
    ORA-6122 "NETTCP: setup failure"는 SQL*NET 구성이 적절하게 설정되지 않은
    상태에서 WINDOWS 용 SQL*NET TCP/IP를 가지고 연결하려 할 때 발생합니다.
    구성을 점검하여 다음 사항을 제대로 설정했는지 확인하십시오.
    1. WINDOWS\WIN.INI를 조사해 보십시오. ORA_CONFIG 매개 변수를 정의하는
    ORACLE 부분이 있어야 합니다.
    [Oracle]
    ORA_CONFIG=C:\WINDOWS\ORACLE.INI
    2. ORACLE.INI(또는 ORA_CONFIG 매개변수가 지시하는 파일)을 보십시오.
    ORACLE_HOME이 WINDOWS용 SQL*NET TCP/IP와 다른 Oracle Windows 응용 프로
    그램이 설치된 디렉토리를 지시하는지 확인하십시오.
    디폴트는 다음과 같습니다.
    ORACLE_HOME=\ORAWIN
    3. 또한 ORACLE.INI에 TCP_VENDOR를 정확하게 설정했는지도 확인하십시오.
    유효한 업체 키 목록은 WINDOWS용 SQL*NET TCP/IP 설정의 표 3-4 '업체키'를
    참조하십시요.
    4. 경로에 C:\ORAWIN\BIN(또한 ORACLE_HOME을 설정한 BIN 디렉토리)이 있는지
    확인하십시오.
    DOS 프롬프트에서 SET을 입력하고 <return>을 누르면 됩니다.
    이 명령은 경로를 보여줍니다.
    5. ORAWIN\BIN 디렉토리에 SQLTCP.DLL과 SQLTCP1.DLL이 모두 있는지 확인하십시오.
    6. 경로의 다른 어떤 디렉토리에도 SQLTCP.DLL이 없는 것을 확인하십시오.
    7. ORAWIN\BIN 디렉토리와 경로의 다른 디렉토리에 MSOCKLIB.DLL이 있는지
    확인하십시오.
    또한 파일의 두 복사본을 가지고 있지 않도록 하십시오.
    복사본이 둘일 경우, 이전 복사본의 이름을 바꾸면 문제가 줄어들 수 있습니다.
    8. WINDOWS 디렉토리에 VSL.INI 파일이 있는지 확인하십시오.
    만약 없으면 ORACLE INSTALLER를 통해 SQL*NET를 다시 입력하십시오.

  • SQL*NET V2에서 DEDICATED로 접속하는 방법

    제품 : SQL*NET
    작성날짜 : 1996-04-17
    SQL*NET V2를 사용하면서 MTS(Multi Threaded Server) 방식이 아닌 DEDICATED
    방식으로 서버에 접속하려면 Client PC의 tnsnames.ora 화일을 다음과 같이 수
    정하면 됩니다(tnsnames.ora 화일은 보통 c:\orawin\network\admin 디렉토리에
    있음). 여기서 ORA_M을 사용하여 접속하면 MTS로 접속되고 ORA_D로 접속하면
    DEDICATED로 접속됩니다.
    Client가 PC가 아닌 경우에도 동일한 방법으로 수정하면 됩니다.
    ===================
    MTS로 접속하는 경우
    ===================
    ORA_M =
    (DESCRIPTION =
    (ADDRESS =
    (PROTOCOL = tcp)
    (HOST = krhp2)
    (PORT=1521))
    (CONNECT_DATA =
    (SID = ORA7)))
    =========================
    DEDICATED로 접속하는 경우
    =========================
    ORA_D =
    (DESCRIPTION =
    (ADDRESS =
    (PROTOCOL = tcp)
    (HOST = krhp2)
    (PORT=1521))
    (CONNECT_DATA =
    (SID = ORA7)(SRVR=DEDICATED)))

  • SQL*NET Easy Config

    I can't find the orainst.exe file on Oracle's site to setup SQL & ODBC on a client machine. Does anyone know where to get this?

    I'm not sure I follow your question...
    SQL*Net Easy Config is a utility that allows you to do things like configure your tnsnames.ora file after you have installed the Oracle client.
    The ODBC Data Source Administrator allows you to configure ODBC connections to your database after the Oracle client has been installed.
    The Oracle Universal Installer allows you to install the Oracle client in the first place.
    Which, if any, of these utilities are you referring to?
    Justin
    Distributed Database Consulting, Inc.
    http://www.ddbcinc.com/askDDBC

  • 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

  • SQL serever 2012 Setup has encountered an error when running a windows installer file

    I am trying to install SQL server 2012 Express on a windows 7 PC for 2 days now. I feel like banging my head against the wall.
    I keep getting the following errors here's the full log
    The following error has occurred:
    SQL Server Setup has encountered an error when running a Windows Installer file.
    Windows Installer error message: An error occurred during the installation of assembly 'Microsoft.VC80.ATL,version="8.0.50727.6229",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'. Please refer
    to Help and Support for more information. HRESULT: 0x8007054F. Windows Installer file: C:\Users\Receno\AppData\Local\Temp\SQL Server 2012\Setup\1033_ENU_LP\x64\setup\sqlsupport_msi\SqlSupport.msi Windows Installer log file: C:\Program Files\Microsoft SQL Server\110\Setup
    Bootstrap\Log\20150109_213740\SqlSupport_Cpu64_1_ComponentUpdate_1.log
    Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup.
    For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.2100.60&EvtType=0xDC80C325

    hmmm..so which hotfix do I apply ?
    SQL Server 2012
    All (Global) x64
    2012_RTM_DAC_CU11_2908007_11_0_2424_x64
    SQL Server 2012
    All (Global) x64
    2012_RTM_SapBI_CU11_2908007_11_0_2424_x64
    SQL Server 2012
    All (Global) x64
    SQLServer2012_RTM_CU11_2908007_11_0_2424_x64
    SQL Server 2012
    All (Global) x64
    2012_RTM_PPExcel_CU11_2908007_11_0_2424_x64
    SQL Server 2012
    All (Global) x64
    2012_RTM_RSShrPnt_CU11_2908007_11_0_2424_x64
    SQL Server 2012
    All (Global) x86
    2012_RTM_DAC_CU11_2908007_11_0_2424_x86
    SQL Server 2012
    All (Global) x86
    2012_RTM_SapBI_CU11_2908007_11_0_2424_x86
    SQL Server 2012
    All (Global) x86
    2012_RTM_PPExcel_CU11_2908007_11_0_2424_x86
    SQL Server 2012
    All (Global) x86
    SQLServer2012_RTM_CU11_2908007_11_0_2424_x86
    SQL Server 2012
    All (Global)
    x64
    2012_RTM_DAC_CU11_2908007_11_0_2424_x64
    <input id="chk471373" style="margin:0px;padding:0px;" type="checkbox" />
    SQL Server 2012
    All (Global)
    x64
    2012_RTM_SapBI_CU11_2908007_11_0_2424_x64
    <input id="chk471368" style="margin:0px;padding:0px;" type="checkbox" />
    SQL Server 2012
    All (Global)
    x64
    SQLServer2012_RTM_CU11_2908007_11_0_2424_x64
    <input id="chk471370" style="margin:0px;padding:0px;" type="checkbox" />
    SQL Server 2012
    All (Global)
    x64
    2012_RTM_PPExcel_CU11_2908007_11_0_2424_x64
    <input id="chk471371" style="margin:0px;padding:0px;" type="checkbox" />
    SQL Server 2012
    All (Global)
    x64
    2012_RTM_RSShrPnt_CU11_2908007_11_0_2424_x64
    <input id="chk471374" style="margin:0px;padding:0px;" type="checkbox" />
    SQL Server 2012
    All (Global)
    x86
    2012_RTM_DAC_CU11_2908007_11_0_2424_x86
    <input id="chk471372" style="margin:0px;padding:0px;" type="checkbox" />
    SQL Server 2012
    All (Global)
    x86
    2012_RTM_SapBI_CU11_2908007_11_0_2424_x86
    <input id="chk471369" style="margin:0px;padding:0px;" type="checkbox" />
    SQL Server 2012
    All (Global)
    x86
    2012_RTM_PPExcel_CU11_2908007_11_0_2424_x86
    <input id="chk471367" style="margin:0px;padding:0px;" type="checkbox" />
    SQL Server 2012
    All (Global)
    x86
    SQLServer2012_RTM_CU11_2908007_11_0_2424_x86
    SQL Server 2012
    All (Global)
    x64
    2012_RTM_DAC_CU11_2908007_11_0_2424_x64
    <input id="chk471373" style="margin:0px;padding:0px;" type="checkbox" />
    SQL Server 2012
    All (Global)
    x64
    2012_RTM_SapBI_CU11_2908007_11_0_2424_x64
    <input id="chk471368" style="margin:0px;padding:0px;" type="checkbox" />
    SQL Server 2012
    All (Global)
    x64
    SQLServer2012_RTM_CU11_2908007_11_0_2424_x64
    <input id="chk471370" style="margin:0px;padding:0px;" type="checkbox" />
    SQL Server 2012
    All (Global)
    x64
    2012_RTM_PPExcel_CU11_2908007_11_0_2424_x64
    <input id="chk471371" style="margin:0px;padding:0px;" type="checkbox" />
    SQL Server 2012
    All (Global)
    x64
    2012_RTM_RSShrPnt_CU11_2908007_11_0_2424_x64
    <input id="chk471374" style="margin:0px;padding:0px;" type="checkbox" />
    SQL Server 2012
    All (Global)
    x86
    2012_RTM_DAC_CU11_2908007_11_0_2424_x86
    <input id="chk471372" style="margin:0px;padding:0px;" type="checkbox" />
    SQL Server 2012
    All (Global)
    x86
    2012_RTM_SapBI_CU11_2908007_11_0_2424_x86
    <input id="chk471369" style="margin:0px;padding:0px;" type="checkbox" />
    SQL Server 2012
    All (Global)
    x86
    2012_RTM_PPExcel_CU11_2908007_11_0_2424_x86
    <input id="chk471367" style="margin:0px;padding:0px;" type="checkbox" />
    SQL Server 2012
    All (Global)
    x86
    SQLServer2012_RTM_CU11_2908007_11_0_2424_x86
    SQL Server 2012
    All (Global)
    x64
    2012_RTM_DAC_CU11_2908007_11_0_2424_x64
    <input id="chk471373" style="margin:0px;padding:0px;" type="checkbox" />
    SQL Server 2012
    All (Global)
    x64
    2012_RTM_SapBI_CU11_2908007_11_0_2424_x64
    <input id="chk471368" style="margin:0px;padding:0px;" type="checkbox" />
    SQL Server 2012
    All (Global)
    x64
    SQLServer2012_RTM_CU11_2908007_11_0_2424_x64
    <input id="chk471370" style="margin:0px;padding:0px;" type="checkbox" />
    SQL Server 2012
    All (Global)
    x64
    2012_RTM_PPExcel_CU11_2908007_11_0_2424_x64
    <input id="chk471371" style="margin:0px;padding:0px;" type="checkbox" />
    SQL Server 2012
    All (Global)
    x64
    2012_RTM_RSShrPnt_CU11_2908007_11_0_2424_x64
    <input id="chk471374" style="margin:0px;padding:0px;" type="checkbox" />
    SQL Server 2012
    All (Global)
    x86
    2012_RTM_DAC_CU11_2908007_11_0_2424_x86
    <input id="chk471372" style="margin:0px;padding:0px;" type="checkbox" />
    SQL Server 2012
    All (Global)
    x86
    2012_RTM_SapBI_CU11_2908007_11_0_2424_x86
    <input id="chk471369" style="margin:0px;padding:0px;" type="checkbox" />
    SQL Server 2012
    All (Global)
    x86
    2012_RTM_PPExcel_CU11_2908007_11_0_2424_x86
    <input id="chk471367" style="margin:0px;padding:0px;" type="checkbox" />
    SQL Server 2012
    All (Global)
    x86
    SQLServer2012_RTM_CU11_2908007_11_0_2424_x86

  • Microsoft SQL Server 2014 Setup error: Wait on the Database Engine recovery handle failed

    Hi,
    Having this annoying error trying to install SQL Server 2014 (RTM). I saw it's been asked several times... But each post seems a different cause and no definitive answer...
    I'm not doing an upgrade, so no "sa account" issue.
    Tried different media. Even three different distributions: trial, Standard and Enterprise.
    Tried disabling Microsoft antivirus/firewall.
    Of course tried restarting, updating, installing, uninstalling, repairing, etc., etc.
    I noticed the users folders under C:\Users weren't created. (Maybe something related to permissions?) After playing around, I managed for the users to be created and the service started. Though I couldn't log in.

    Summary for last "repair" attempt:
    Overall summary:
    Final result: Failed: see details below
    Exit code (Decimal): -2068578302
    Start time: 2014-04-27 23:54:21
    End time: 2014-04-27 23:59:48
    Requested action: Repair
    Setup completed with required actions for features.
    Troubleshooting information for those features:
    Next step for SQLEngine: Use the following information to resolve the error, and then try the setup process again.
    Next step for DQ: Use the following information to resolve the error, and then try the setup process again.
    Next step for FullText: Use the following information to resolve the error, and then try the setup process again.
    Next step for LocalDB: Use the following information to resolve the error, and then try the setup process again.
    Machine Properties:
    Machine name: CHARLY13C
    Machine processor count: 4
    OS version: Windows 8
    OS service pack:
    OS region: United States
    OS language: English (United States)
    OS architecture: x64
    Process architecture: 64 Bit
    OS clustered: No
    Product features discovered:
    Product Instance Instance ID Feature Language Edition Version Clustered Configured
    SQL Server 2012 DENALI MSSQL11.DENALI Database Engine Services 1033 Enterprise Edition 11.1.3128.0 No Yes
    SQL Server 2012 LocalDB 1033 Express Edition 11.1.3128.0 No Yes
    SQL Server 2014 HEKATON MSSQL12.HEKATON Database Engine Services 1033 Enterprise Edition 12.0.2000.8 No Yes
    SQL Server 2014 HEKATON MSSQL12.HEKATON Full-Text and Semantic Extractions for Search 1033 Enterprise Edition 12.0.2000.8 No Yes
    SQL Server 2014 HEKATON MSSQL12.HEKATON Data Quality Services 1033 Enterprise Edition 12.0.2000.8 No Yes
    SQL Server 2014 Management Tools - Basic 1033 Enterprise Evaluation Edition 12.0.2000.8 No Yes
    SQL Server 2014 Management Tools - Complete 1033 Enterprise Evaluation Edition 12.0.2000.8 No Yes
    SQL Server 2014 Client Tools Connectivity 1033 Enterprise Evaluation Edition 12.0.2000.8 No Yes
    SQL Server 2014 LocalDB 1033 Express Edition 12.0.2000.8 No Yes
    Package properties:
    Description: Microsoft SQL Server 2014
    ProductName: SQL Server 2014
    Type: RTM
    Version: 12
    SPLevel: 0
    Installation location: F:\x64\setup\
    Installation edition: Enterprise
    User Input Settings:
    ACTION: Repair
    AGTDOMAINGROUP: <empty>
    AGTSVCACCOUNT: <empty>
    AGTSVCPASSWORD: <empty>
    AGTSVCSTARTUPTYPE: Manual
    ASCONFIGDIR: Config
    ASSVCACCOUNT: <empty>
    ASSVCPASSWORD: <empty>
    CLTSTARTUPTYPE: 0
    CLTSVCACCOUNT: <empty>
    CLTSVCPASSWORD: <empty>
    CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140427_235420\ConfigurationFile.ini
    CTLRSTARTUPTYPE: 0
    CTLRSVCACCOUNT: <empty>
    CTLRSVCPASSWORD: <empty>
    ENU: true
    FAILOVERCLUSTERGROUP: <empty>
    FAILOVERCLUSTERNETWORKNAME: <empty>
    FTSVCACCOUNT: NT Service\MSSQLFDLauncher$HEKATON
    FTSVCPASSWORD: <empty>
    HELP: false
    IACCEPTSQLSERVERLICENSETERMS: false
    INDICATEPROGRESS: false
    INSTANCENAME: HEKATON
    ISSVCACCOUNT: NT AUTHORITY\Network Service
    ISSVCPASSWORD: <empty>
    ISSVCSTARTUPTYPE: Automatic
    QUIET: false
    QUIETSIMPLE: false
    SQLSVCACCOUNT: NT Service\MSSQL$HEKATON
    SQLSVCPASSWORD: <empty>
    UIMODE: Normal
    X86: false
    Configuration file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140427_235420\ConfigurationFile.ini
    Detailed results:
    Feature: Management Tools - Complete
    Status: Passed
    Feature: Client Tools Connectivity
    Status: Passed
    Feature: Management Tools - Basic
    Status: Passed
    Feature: Database Engine Services
    Status: Failed: see logs for details
    Reason for failure: An error occurred during the setup process of the feature.
    Next Step: Use the following information to resolve the error, and then try the setup process again.
    Component name: SQL Server Database Engine Services Instance Features
    Component error code: 0x84B40002
    Error description: The SQL Server feature 'SQL_Engine_Core_Inst' is not in a supported state for repair, as it was never successfully configured. Only features from successful installations can be repaired. To continue, remove the specified SQL Server feature.
    Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0x2841E06E%401204%402&EvtType=0x2841E06E%401204%402
    Feature: Data Quality Services
    Status: Failed: see logs for details
    Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
    Next Step: Use the following information to resolve the error, and then try the setup process again.
    Component name: SQL Server Database Engine Services Instance Features
    Component error code: 0x84B40002
    Error description: The SQL Server feature 'SQL_Engine_Core_Inst' is not in a supported state for repair, as it was never successfully configured. Only features from successful installations can be repaired. To continue, remove the specified SQL Server feature.
    Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0x2841E06E%401204%402&EvtType=0x2841E06E%401204%402
    Feature: Full-Text and Semantic Extractions for Search
    Status: Failed: see logs for details
    Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
    Next Step: Use the following information to resolve the error, and then try the setup process again.
    Component name: SQL Server Database Engine Services Instance Features
    Component error code: 0x84B40002
    Error description: The SQL Server feature 'SQL_Engine_Core_Inst' is not in a supported state for repair, as it was never successfully configured. Only features from successful installations can be repaired. To continue, remove the specified SQL Server feature.
    Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0x2841E06E%401204%402&EvtType=0x2841E06E%401204%402
    Feature: SQL Browser
    Status: Passed
    Feature: SQL Writer
    Status: Passed
    Feature: LocalDB
    Status: Failed: see logs for details
    Reason for failure: An error occurred during the setup process of the feature.
    Next Step: Use the following information to resolve the error, and then try the setup process again.
    Feature: SQL Client Connectivity
    Status: Passed
    Feature: SQL Client Connectivity SDK
    Status: Passed
    Feature: Setup Support Files
    Status: Passed
    Rules with failures:
    Global rules:
    There are no scenario-specific rules.
    Rules report file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140427_235420\SystemConfigurationCheck_Report.htm

  • 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

Maybe you are looking for

  • InDesign CS4 no longer shows triangle icon for modified images in Links

    My InDesign crashed the other day, and now it no longer gives me the yellow triangular icon in the Links panel to indicate that and image has been modified and needs to be updated. I typically do not connect the image to the original via Indesign, bu

  • Adobe not working for me...

    Hey guys, so whenever i go to youtube, it tells me this...."Hello, you either have JavaScript turned off or an old version of Adobe's Flash Player. Get the latest Flash player. " BUT, i have installed the flash player over 10 times, restarted my comp

  • Calculating value per second

    Hi all. I need to just calculate and save the values per second in the variable that how many times per second a variable is being revieved in the method as a parameter and then show that progress as int / second in the progress bar public void metho

  • Page Flow and Java Control interaction

    Hi everybody ! Even after to read some documents like http://dev2dev.bea.com/pub/a/2004/06/wlw_internals.html and http://dev2dev.bea.com/pub/a/2004/01/jones.html i still didn't get what is really happening "behind the scenes" between Page Flows and J

  • Can any one tell me what is JSF and where  why is it used

    hi can any one give me a brief introduction on JSF and where and why is it used.. if there is any good tutorial/documentation pls give me the links sanjay