get ora-00028 session killed error when run long query
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 5 of 5

Thread: get ora-00028 session killed error when run long query

  1. #1
    Join Date
    May 2002
    Posts
    12

    Question

    Can you guys help me figure out what is wrong with my net config?

    we can run query with small result set reruened against this table, but when we run the query with lots of data returned, we got 'the session has been killed' error. what am I looking for?

    thanks,

    cathy
    DBA OCP 8i

  2. #2
    Join Date
    Sep 2001
    Location
    NJ, USA
    Posts
    1,287
    Some information from u:
    -- OS on clien and on server
    -- type of network protocol
    -- what application u are using
    -- sqlnet.ora on server and client mashines
    ...
    any addition datas may help to solve ur problem

  3. #3
    Join Date
    May 2002
    Posts
    12
    Here are more detail:

    -- OS on clien and on server
    Window NT on both client and server

    -- type of network protocol
    TCP/IP

    -- what application u are using
    sqlplus

    -- sqlnet.ora on server and client mashines
    -- Client sqlnet.ora file as below:
    # SQLNET.ORA Network Configuration File: d:\Oracle\Ora81\network\admin\sqlnet.ora
    # Generated by Oracle configuration tools.

    NAMES.DEFAULT_DOMAIN = xxxx.xxxxxx.com

    SQLNET.AUTHENTICATION_SERVICES= (NTS)

    NAMES.DIRECTORY_PATH= (TNSNAMES)

    -- server sqlnet.ora file as below:
    AUTOMATIC_IPC = OFF
    TRACE_LEVEL_CLIENT = OFF
    names.directory_path = (TNSNAMES)
    names.default_domain = world
    name.default_zone = world


    -- server listener.ora as follow
    ################
    # Filename......: listener.ora
    # Node..........: local.world
    # Date..........: 24-MAY-95 13:23:20
    ################
    LISTENER =
    (ADDRESS_LIST =
    (ADDRESS=
    (COMMUNITY= TCP.world)
    (PROTOCOL= TCP)
    (Host= xx.xx.xx.xx)
    (Port= 1521)
    )
    (ADDRESS=
    (COMMUNITY= TCP.world)
    (PROTOCOL= TCP)
    (Host= xx.xx.xx.xx)
    (Port= 1526)
    )
    )
    STARTUP_WAIT_TIME_LISTENER = 0
    CONNECT_TIMEOUT_LISTENER = 10
    TRACE_LEVEL_LISTENER = ADMIN
    SID_LIST_LISTENER =
    (SID_LIST =
    (SID_DESC =
    (SID_NAME = ORCL)
    )
    (SID_DESC =
    (SID_NAME = xxx)
    )
    (SID_DESC =
    (SID_NAME = xxx)
    )
    (SID_DESC =
    (SID_NAME = xxx)
    )
    )
    PASSWORDS_LISTENER = (oracle)


    thanks, cathy

    DBA OCP 8i

  4. #4
    Join Date
    Jan 2002
    Posts
    146
    Hi,

    I presume you run your apps on the client side, can you try
    running it on the server side if it will be killed also?
    I'm just curious.

  5. #5
    Join Date
    Sep 2001
    Location
    NJ, USA
    Posts
    1,287
    In first: I don't sure about this my answer.
    Maybe problem in sqlnet parameter:

    SQLNET.AUTHENTICATION_SERVICES= (NTS)

    U have to check period, how often NT server check
    authentication datas on windows client. and which layer of
    OSI model NT have to use for this procedure.
    when u execute long query and use direct soket connection
    to oracle database they will use 3 upper layes of OSI models
    If NT authentication procedure use the same layes it may
    create conflict situation and NT network software MAY (I DON'T SURE) close soket.

    Try to exclude this parameter from sqlnet.ora file.


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


Click Here to Expand Forum to Full Width