Sqlnet.ora query

I'm currently working with a customer that requires some changes to be made to their sqlnet.ora file. We have both reviewed "When do SQLNET.ORA changes take effect ? (Doc ID 562589.1)" on MOS but are finding the knowledge document a little unclear.
If I explain the situation we are in first: they have a 3-node RAC environment and recently made changes to their sqlnet.ora file in order to fix some service died error messages, then restarted the listeners for the changes to take effect. However, they were still seeing service died following the restart of the listener in the alert log. They decided to bounce the instance and this cleared the messages. The DB is in dedicated mode.
Is it the case that until the instance is bounced then the changes will not take place for the currently connected processes? Therefore the error messages will continue. Or should they only need to restart/reload the listener for the changes to take place.
My interpretation of the MOS note is that because they are in dedicated mode that they should only need to restart the listener.
Many thanks in advance,
Kerri

968642 wrote:
Thank you for your response.
Changes were made to the sqlnet.ora file. So does this mean that the instance would need to be bounced in order for all connections to see the new settings?
They had a situation where they updated the sqlnet.ora file back in July, these changes were not picked up until two weekends ago as they had not bounced the instance or the listeners between now and then. This is contrary to what the document says, hence why I am asking. As if the document was correct, then we would expect from July - October, that the changes would have come into effect.
The following change was added in July:
sqlnet.outbound_connect_timeout=1There are two entities that use sqlnet.ora - clients and listeners. Some of the parameters in sqlnet.ora apply only to clients. Some apply only to listeners. Some apply to both.
Clients read it when they initiate a connection request.
Listeners read it when they start or reload. If you didn't start or reload your listener then it didn't see the changes. And you indicated that the instances and listeners were not bounced until two weeks ago. The instance really doesn't matter, but the listener certainly does. (Well, the instance may matter, but only from the standpoint that when an instance is using a db_link, it is acting as a client. See above comment on clients)
Edited by: EdStevens on Oct 31, 2012 7:13 AM

Similar Messages

  • SQL query to find sqlnet.ora parameters

    Hi All,
    I am working 11g RAC /solaris 9
    I want have sql query to find values of sqlnet.ora parameters
    May be values of SQLNET.INBOUND_CONNECT_TIMEOUT
    SQLNET.SEND_TIMEOUT, SQLNET.RECV_TIMEOUT
    Thanks
    raj

    The sqlnet.ora file is the profile configuration file. It resides on the client machines and the database server.
    Profiles are stored and implemented using this file. The database server can be configured with access control parameters in the sqlnet.ora file.
    These parameters specify whether clients are allowed or denied access based on the protocol.
    The sqlnet.ora file enables you to do the following:
    Specify the client domain to append to unqualified names
    Prioritize naming methods
    Enable logging and tracing features
    Route connections through specific processes
    Configure parameters for external naming
    Configure Oracle Advanced Security
    Use protocol-specific parameters to restrict access to the database
    By default, the sqlnet.ora file is located in the ORACLE_HOME/network/admin directory. The sqlnet.ora file can also be stored in the directory specified by the TNS_ADMIN environment variable.
    You can not query on this file sqlnet.ora as tnsnames.ora file.
    Regards
    Mahir M. Quluzade

  • Questions on sqlnet.ora, listener.ora files in RAC environment.

    Experts,
    I've some confusion with below files in RAC environment.
    sqlnet.ora
    listener.ora
    These files are available in two locations: <GRID_HOME> & <DB_HOME>.
    My questions:
    1. Why do we have two versions of files ?
    2. When I query lsnrctl status from BOTH the homes, it says it is using listener.ora from <GRID_HOME> as shown below.
    Listener Parameter File D:\app\11.2.0\grid\network\admin\listener.ora
    3. What is the use of files which are in <DB_Home>
    4. If you make some changes to listener using "Netmgr" tool, we expect it will update listener.ora in <GRID_HOME>. Interestingly, it is changing the contents of listener.ora in <DB_HOME> .
    Can anyone please clarify it ?
    Thanks in advance.

    859875 wrote:
    1. Why do we have two versions of files ? In the past, the CRS s/w did not include ASM (ASM did not provide support for cluster voting and registration disks). Thus the networking components such as SQL*Net and the Listener were not part of the CRS installation.
    With Grid Infrastructure, ASM supports cluster voting and registration disks and is recommended to be used for that (as oppose to the old style of raw disks or using an external cluster-based cooked file system like <i>ocfs</i>). And with ASM comes the SQL*Net networking layer and s/w (such as the Listener). As ASM ships with Grid Infrastructure, it now also includes the same networking layer as what the RDBMS installation will. Thus both <GRID_HOME> and <DB_HOME> will contain the same networking components.
    However, only a single Listener is for example needed. And that can only run from a single base location. So for operational use, only one version will be actively in use.

  • Dead conection detection and sqlnet.ora

    Hello,
    I´m having some doubts regarding the sqlnet.ora.
    I´m configuring the sqlnet.expire_time=10 parameter in sqlnet.ora, restarted the listener and then I connected via a web conection and turned off my computer (client connection)
    Sometimes in 18 or 20 minutes the connection closes, sometimes it remains connected for hours. I turned the trace on and I see a message that the net service read the sqlnet.expire_time = 10 parameter.
    What could be wrong ? Anybody here had this kind of problems configuring dead conections detection ?
    Another doubt. How can I set a inactivity time ? for example , if the user don´t make a query in 30 minutes he´s disconected... I already tried it configuring in Enterprise manager but it also failed.
    SQLNET.EXPIRE_TIME
    Purpose:
    Determines time interval to send a probe to verify the session is alive
    Default: None
    Minimum Value: 0 minutes
    Recommended Value: 10 minutes
    Example:
    sqlnet.expire_time=10
    Thank you in advance,
    Felipe

    looking at the trace files we can see that the expire time is configured to 5 minutes . But making tests (like disconecting the net cable) I see a user conected and the 20 after 20 minutes it still conected ...
    --- TRACE CONFIGURATION INFORMATION FOLLOWS ---
    [13-SEP-2005 13:58:50:591] New trace stream is /oracle/db/9.2.0.4/network/admin/trace/svr_22551.trc
    [13-SEP-2005 13:58:50:591] New trace level is 6
    [13-SEP-2005 13:58:50:591] --- TRACE CONFIGURATION INFORMATION ENDS ---
    [13-SEP-2005 13:58:50:591]
    --- PARAMETER SOURCE INFORMATION FOLLOWS ---
    [13-SEP-2005 13:58:50:591] Attempted load of system pfile source /oracle/db/9.2.0.4/network/admin/sqlnet.ora
    [13-SEP-2005 13:58:50:591] Parameter source loaded successfully
    [13-SEP-2005 13:58:50:591]
    [13-SEP-2005 13:58:50:591] -> PARAMETER TABLE LOAD RESULTS FOLLOW <-
    [13-SEP-2005 13:58:50:591] Successful parameter table load
    [13-SEP-2005 13:58:50:591] -> PARAMETER TABLE HAS THE FOLLOWING CONTENTS <-
    [13-SEP-2005 13:58:50:591] SQLNET.EXPIRE_TIME = 5
    [13-SEP-2005 13:58:50:591] TRACE_DIRECTORY_SERVER = /oracle/db/9.2.0.4/network/admin/trace
    [13-SEP-2005 13:58:50:591] SQLNET.ENCRYPTION_TYPES_SERVER = (RC4_128)
    [13-SEP-2005 13:58:50:591] SSL_CIPHER_SUITES = (SSL_RSA_EXPORT_WITH_DES40_CBC_SHA, SSL_RSA_EXPORT_WITH_RC4_4
    0_MD5)
    [13-SEP-2005 13:58:50:592] SQLNET.ENCRYPTION_TYPES_CLIENT = (RC4_128)
    [13-SEP-2005 13:58:50:592] WALLET_LOCATION = (SOURCE = (METHOD = FILE) (METHOD_DATA = (DIRECTORY = /oracle/d
    b/9.2.0.4/network/admin)))
    [13-SEP-2005 13:58:50:592] TRACE_LEVEL_SERVER = admin
    [13-SEP-2005 13:58:50:592] NAMES.DIRECTORY_PATH = (TNSNAMES, ONAMES, HOSTNAME)
    [13-SEP-2005 13:58:50:592] sqlnet.crypto_seed = fewkpfrepgomrepogmropegjerpogjpejvvmmrpm
    [13-SEP-2005 13:58:50:592] SQLNET.CRYPTO_CHECKSUM_TYPES_CLIENT = (MD5)
    [13-SEP-2005 13:58:50:592] SQLNET.CRYPTO_CHECKSUM_TYPES_SERVER = (MD5)
    [13-SEP-2005 13:58:50:592] SSL_VERSION = 3.0
    [13-SEP-2005 13:58:50:592] SQLNET.CRYPTO_CHECKSUM_SERVER = accepted
    [13-SEP-2005 13:58:50:592] SQLNET.ENCRYPTION_CLIENT = accepted
    [13-SEP-2005 13:58:50:592] SSL_CLIENT_AUTHENTICATION = TRUE
    [13-SEP-2005 13:58:50:592] NAMES.DEFAULT_DOMAIN = sids.mg.gov.br
    [13-SEP-2005 13:58:50:592] --- PARAMETER SOURCE INFORMATION ENDS ---
    [13-SEP-2005 13:58:50:592]
    --- LOG CONFIGURATION INFORMATION FOLLOWS ---
    [13-SEP-2005 13:58:50:592] Log stream will be "/oracle/db/9.2.0.4/network/log/sqlnet.log"
    [13-SEP-2005 13:58:50:592] Log stream validation not requested
    [13-SEP-2005 13:58:50:592] --- LOG CONFIGURATION INFORMATION ENDS ---
    If anybody here experienced this same problem please let me know..

  • Sqlnet.ora doesn't seem to be read since oci8 1.3.4

    Hello,
    I used to use oci8 version 1.2.3 and I wanted to update to last version (1.3.4). Everything works fine except the fact that "sqlnet.ora" does not seems to be read anymore.
    I use the following string to describe my database in oci_connect: "MEN1PRD".
    In sqlnet.ora there is the parameter NAMES.DEFAULT_DOMAIN which is set to "WORLD".
    In the tnsname.ora I have a full definition for "MEN1PRD.WORLD".
    With oci8 1.2.3, it worked but since I upgraded to 1.3.4 this is not the case anymore. I have to use the same ID in oci_connect and tnsname.org. The sqlnet.ora NAMES.DEFAULT_DOMAIN does not seem to be used anymore.
    The version of php (5.2.3) is still the same, the configure options are the sames, the oracle lib is the same (9.2) and the php.ini parameters are the same too. I just changed the oci8 version.
    Has anyone the same problem ? Is this a normal behaviour ? If yes, why
    and is there a workaround ?
    Thanks for your answers.
    ++ Jerome
    Reproduce code:
    Piece of code which used to work (version 1.2.3) and doesn't work
    anymore (version 1.3.4):
    $conn = oci_connect('EDUCATION', 'manager', 'MEN1PRD');
    Piece of code which works (version 1.3.4):
    $conn = oci_connect('EDUCATION', 'manager', 'MEN1PRD.WORLD');
    Content of sqlnet.ora (which is in the same directory as tnsname.ora):
    NAMES.DIRECTORY_PATH= (TNSNAMES, ONAMES, HOSTNAME)
    NAMES.DEFAULT_DOMAIN = WORLD
    LOG_DIRECTORY_SERVER = /var/tmp
    Contenat of tnsname.ora
    MEN1PRD_RAC =
    ( DESCRIPTION =
    ( ADDRESS = ( PROTOCOL = TCP )( HOST = host1 )( PORT = 1521 ) )
    ( ADDRESS = ( PROTOCOL = TCP )( HOST = host2 )( PORT = 1521 ) )
    ( LOAD_BALANCE = yes )
    ( CONNECT_DATA =
    ( SERVER = DEDICATED )
    ( SERVICE_NAME = SN_MEN1PRD )
    Init script:
    export ORACLE_HOME=/usr/local/oracle/VERSIONS/Linux/CL.9.2.0
    PATH=$PATH:$ORACLE_HOME/bin:$ORACLE_HOME/network/admin:$ORACLE_HOME/lib:/usr/local/bin
    export ORACLE_SID=MEN1PRD
    export HOSTNAME=`hostname`
    export NLS_LANG=FRENCH_FRANCE.WE8ISO8859P15
    export LC_ALL=fr_FR
    export LANG=fr_FR
    Expected result:
    The connexion is made to the database
    Actual result:
    [Mon Feb 16 18:05:14 2009] [error] [client 127.0.0.1] PHP Warning:
    oci_connect() [function.oci-connect]:
    ORA-12154: TNS:could not resolve service name in /var/www/docs/test1.php
    on line 2

    See http://pecl.php.net/bugs/bug.php?id=15988 It's a problem with 9.2 - 10.2.0.3, fixed in 10.2.0.4
    Discussions about best solution is ongoing; currently centering around not using session pooling code path in PHP OCI8 when using Oracle prior to 11.

  • Sqlnet.ora trace files getting generated even after turning off tracing

    Hi,
    I have recently added the following parameters to the sqlnet.ora file.
    TRACE_LEVEL_SERVER=16
    TRACE_FILE_SERVER=SERVER
    TRACE_DIRECTORY_SERVER=/ftpland/trace
    TRACE_TIMESTAMP_SERVER=on
    Even after removing these enteries from the sqlnet.ora I still see the trave files being generated.
    #####enable tracing###################
    #Trace_level_server=0
    #Trace_filelen_server=1000
    #Trace_fileno_server=1
    #Trace_timestamp_server=on
    #Trace_directory_server=/opt/oracle/product/10.2.0/network/trace
    #Diag_adr_enabled=off
    AUTOMATIC_IPC = ON
    TRACE_LEVEL_CLIENT = OFF
    SQLNET.EXPIRE_TIME = 10
    NAMES.DEFAULT_DOMAIN = bsca.eds.com
    NAME.DEFAULT_ZONE = bsca.eds.com
    SQLNET.CRYPTO_SEED = "232166927-1713903352"
    NAMES.DIRECTORY_PATH = (ONAMES,TNSNAMES)
    NAMES.PREFERRED_SERVERS =
          (ADDRESS_LIST =
            (ADDRESS =
              (COMMUNITY = TCP.bsca.eds.com)
              (PROTOCOL = TCP)
              (Host = oraclenames1.bsca.eds.com)
              (Port = 1575)
            (ADDRESS =
              (COMMUNITY = TCP.bsca.eds.com)
              (PROTOCOL = TCP)
              (Host = oraclenames2.bsca.eds.com)
              (Port = 1575)
    NAME.PREFERRED_SERVERS =
          (ADDRESS_LIST =
            (ADDRESS =
              (COMMUNITY = TCP.bsca.eds.com)
              (PROTOCOL = TCP)
              (Host = oraclenames1.bsca.eds.com)
              (Port = 1575)
    (ADDRESS =
              (COMMUNITY = TCP.bsca.eds.com)
              (PROTOCOL = TCP)
              (Host = oraclenames2.bsca.eds.com)
              (Port = 1575)
    BEQUEATH_DETACH=YES
    Regards,
    VN

    SID_LIST_LISTENER =
      (SID_LIST =
        (SID_DESC =
          (GLOBAL_DBNAME =ROSDMP.bsca.eds.com)
          (ORACLE_HOME = /opt/oracle/product/10.2.0)
          (SID_NAME = ROSDMP)
    TRACE_LEVEL_LISTENER=16
    I believe, this is the reason, you are seeing trace files even after disabling it in sqlnet.ora

  • How to supply wallet location to OCI client for SSL connection other than sqlnet.ora

    I have a oracle 11g database server and I am connecting to it through OCI client in OBIEE Admin tool. This is working fine, but now the requirement is we need to connect to an SSL enabled database.
    For this I had to update the sqlnet.ora under $ORACLE_HOME/network/admin in OBIEE installation and specify the wallet location where I placed the wallet containing appropriate certificates.
    The above is working fine for me. But due to certain restrictions, we cannot create this sqlnet.ora. Is there a way we can pass this wallet location through some environment variables so that sqlnet.ora is not required?
    If we create a jdbc connection, we can specify the wallet location through jdbc connection properties. Is there any such equivalent for OCI based connection. I dont mind how we make the wallet location available to OCI client, so long as I dont have to create a sqlnet.ora.
    Any pointers is greatly appreciated

    Hi,
    sqlnet.ora file is required if you want to set the wallet location to another directory by using the WALLET_LOCATION parameter.
    If you do not want to use sqlnet.ora then you need to use the default wallet location.
    The wallet is placed, by default, in $ORACLE_BASE/admin/<global_db_name>/wallet.
    If this directory does not exist or ORACLE_BASE is not set, the default location is: $ORACLE_HOME/admin/<global_db_name>/wallet
    Regards,
    Ravi

  • Sqlnet.ora file 11.5.10.2

    Hi,
    I always disabled or commented the 2 lines sqlnet.ora file to accept all database connections...
    tcp.validnode_checking=yes
    tcp.invited_nodes=
    I commented the above lines in sqlnet.ora file and bounced the listener..now i am able to connect to the database...
    When ever I run the autoconfig in database tier..... these 2 lines are going to be uncommented...
    how we can do this for permenant for checking the above 2 lines sqlnet.ora file..
    do we need to add any custom context variables in Context file..if it is so..how can we do it..please help me in this regard....

    tcp.validnode_checking=yes
    tcp.invited_nodes= <list your applications tier nodes here>
    These actually ARE recommended in Production. Basically what you're saying by setting these is that the SQL*Net Listener for the database will ONLY talk to these known hosts. This prevents some random person from connecting directly to your database from a PC somewhere.
    The downside here is that if you have a large number of users who use a client-side tool (like ADI or Discoverer), then you'll have to list their IP addresses here. This can be quite difficult in a DHCP-enabled environment.
    The way autoconfig works, it basically replaces any autoconfig managed files whenever it runs (which is why your customizations get clobbered).
    So, in situations where there isn't a context variable that you can update, you'll have to make a custom template.
    When autoconfig runs, it checks first for the existence of the custom template (and validates that it isn't based on an older version than the currently installed one) and will use that instead of the delivered one.
    Simple way to do a custom template:
    1) Identify the template being used (Database tier, it'll be under $ORACLE_HOME/appsutil somewhere... Apps tier it's generally under $AD_TOP/admin/template or $FND_TOP/admin/template).
    2) Create a "custom" directory under the "template" directory where your template lives.
    3) Copy that template into the "custom" directory.
    4) Edit this copy.
    -- James

  • Windows 2000  run "emctl start subagent" errinfo " can find sqlnet.ora"

    system info
    windows 2000 server sp4
    Oracle Enterprise Manager 10g Grid Control
    Win32_Grid_Control_agent_download_10_2_0_3_0
    C:\OracleHomes\agent10g\BIN>emctl start subagent
    Running sub agent .....stopped
    find info in emsubagent.nohup
    NL-00462: error loading parameter file C:\OracleHomes\agent10g\network\admin\sqlnet.ora
    NL-00405: cannot open parameter file
    SNL-00821: Message 821 not found; No message file for product=NETWORK, facility=SNL
    32-bit Windows Error: 2: No such file o

    Hi,
    Did you manage to run the subagent?
    I try to send SNMP trap.
    bash-2.05$ /home/oracle/agent10g/network/snmp/peer # ulimit -n 1024
    bash-2.05$ /home/oracle/agent10g/network/snmp/peer # ./start_peer -a
    Starting master_peer ...
    ./master_peer CONFIG.master NOV >master_peer.out 2>&1 &
    Done!
    Starting encap_peer ...
    ./encap_peer -t 1162 -s 1160 -c CONFIG.encap >encap_peer.out 2>&1 &
    Done!
    Starting /usr/sbin/snmpd ...
    /usr/sbin/snmpd -c snmpd.conf udp:1161 >snmpd.out 2>&1 &
    Done!
    bash-2.05$ agent10g/bin> ulimit -n 1024
    And I changed targets.xml.
    But...
    bash-2.05$ ./emctl start subagent
    Oracle Enterprise Manager 10g Release 4 Grid Control 10.2.0.4.0.
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    Starting sub agent .....started
    bash-2.05$ ./emctl status subagent
    Oracle Enterprise Manager 10g Release 4 Grid Control 10.2.0.4.0.
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    Sub agent is not running..
    Edited by: user3648527 on 20.01.2011 23:35

  • Tnsnames.ora, sqlnet.ora & listener.ora files are not exit

    DB version: 10.2
    Hello All,
    I just joined the project and notice tnsnames.ora, sqlnet.ora & listener.ora files are not exit under $ORACLE_HOME/network/admin.
    But still we can connect to the database,
    From command prompt or via enterprise manager studio from client site.
    Any idea?
    OR
    what is the best way to create above files in the existing database?
    DN

    tnsnames.ora and sqlnet.ora are client side files, listener.ora and sqlnet.ora are server side files.
    Listener.ora need not exist if using defaults and dynamic registration of services. It may be possible to cope without all those files, depending on the environment.
    Is the database on the local or remote computer and how are you connecting (from sqlplus)?
    Maybe you have a tnsnames.ora somwhere else? (Try using find command) Maybe TNS_ADMIN is set?

  • Connect with ldap.ora and sqlnet.ora

    Hi
    I am trying to connect Raptor to 9i oracle server. Our server connects using ldap.ora and sqlnet.ora files. I looked at some threads about this issue but do not understand how to connect. Is there a step by step instruction for connecting this way?
    Thanks
    DH

    Hi VRamirez,
    That's a pretty cool workaround. I'm sorry to hear it didn't work perfectly.
    Here is the "low tech" workaround anyone can use -
    From the %ORACLE_HOME% where your sqlnet.ora is, run %ORACLE_HOME%\bin\tnsping eg.
    C:\> tnsping oracle.world
    TNS Ping Utility for 32-bit Windows: Version 10.2.0.1.0 - Production on 21-APR-2006 22:56:31
    Copyright (c) 1997, 2005, Oracle. All rights reserved.
    Used parameter files:
    c:\oracle\oracli92\network\admin\sqlnet.ora
    Used LDAP adapter to resolve the alias
    Attempting to contact (DESCRIPTION=(SOURCE_ROUTE=OFF)(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=oracle.xxxx.xx)(
    PORT=xxxx)))(CONNECT_DATA=(SID=ORCL))(SRVR=SHARED))
    OK (200 msec)
    C:\>
    Now copy the (DESCRIPTION=...) and paste it into the advanced TNS info tab in the Connections dialog. This works for me for everything but RAC TNS aliases which have load balancing and failover configured -- the advanced TNS info tab chokes on those. For such connections, I was able to use the JDBC string.
    -Natalka
    http://toolkit.rdbms-insight.com

  • Disadvantages of SQLNET.EXPIRE_TIME in SQLNET.ORA

    Hi,
    Could any body tell me please what would be side effects and disadvantages of using SQLNET.EXPIRE_TIME parameter in the sqlnet.ora file when there are frequent network timeouts?
    Does Oracle recommends network problems should be resolves or SQLNET.EXPIRE_TIME parameter is harmless to keep connectivity between clients and server?
    Thanks

    Hi,
    it has affects on pmon, which maybe cleans up resources which are held by the "dead" shadow process. PMON will clean up after the expire_time, when there is no connection.
    "Negative" effects... i don't have seen really negative affects... the network traffic maybe increase (depends on your amount of connections).. but this should not be a problem.
    Regards
    Stefan

  • Database connectivity requiring oracle wallet, tnsnames.ora, and sqlnet.ora

    We have a new datasource that I need to write a report against.  In order to access the db, I have to install an Oracle wallet on my pc that contains a certificate.  I then have an entry in the sqlnet.ora file that references this wallet, and I have an entry in my tnsnames file.  I wrote a report successfully on my pc.  We then have our Business Objects installation on a Sun Solaris machine with Unix.  We installed the wallet, added the sqlnet.ora entry, and the tnsnames.ora entry.  I am able to connect to the db from the unix command prompt by typing sqlplus username@dbname successfully.  However, when I place my Crystal Report in Bus. Obj. I cannot get it to work.  I go to the CMC, select the report, choose Process, Database.  I am entering Use custom database logon info and choosing Oracle as my database driver.  I then enter the tnsnames entry into the server and enter my username and password and check the use use same database logon as when report is run.  I get the error The database logon information for this report is either incomplete or incorrect.  I'm guessing the report is not using the certificate in the wallet when it is trying to log on, but I'm not sure.  Does anyone have any suggestions or experience with this?  Thanks in advance for any help.

    Hi Angie,
    you should install the 32bit Oracle driver on your Solaris machine and adjust the LD_LIBRARY_PATH environment variable (in the profile of the BOBJ installation user) to point to the path of the 32bit libraries of your Oracle driver.
    BOBJ is not a native 64bit software and can therefore work only with the 32bit versions of the database drivers.
    Regards,
    Stratos
    Edited by: Efstratios Karaivazoglou on Jul 15, 2009 4:49 PM

  • Path of Sqlnet.ora and Tnsnames.ora

    Hi all
    Why I have one
    Sqlnet.ora
    in
    C:\ORAWIN95\NETWORK\ADMIN
    and
    one in
    C:\ORAWIN95\NET80\ADMIN
    and
    Tnsnames.ora
    in
    C:\ORAWIN95\NET80\ADMIN
    and
    C:\ORAWIN95\NETWORK\ADMIN
    and
    C:\ORAWIN95\NET80\TNSAPI
    why they are duplicated?
    thanks
    Sobrinho

    It looks like you have (or had) multiple versions of SQL*Net.
    Oracle 8 put everything in %oracle_home%\net80 while Oracle 7 and 9 use %oracle_home%\network

  • The importance of SQLnet.ora file

    DB version:10gR2
    I have seen databases where SQLnet.ora file is absent or an SQLnet.ora file with most of the entries commented out like
    NAMES.DIRECTORY_PATH= (TNSNAMES, EZCONNECT)
    #SQLNET.EXPIRE_TIME=700
    # New parameter for 10.2
    #SQLNET_INBOUND_CONNECT_TIMEOUT=120I have two questions
    1. If you were asked to set the parameters for SQLNET.ora file for an OLTP database, what would your settings be?
    2. Is it absolutely necessary to have an SQLNET.ora file in a 'production quality' Database?
    Edited by: Citizen_2 on Feb 18, 2009 2:59 AM
    Corrected the spelling of SQLnet.ora in subject line

    Hi,
    SQLNET.ORA can be used for different purposes,
    first to identify the method to connect from client like tnsnames
    Second it can be used to bypass the network layer by setting the parameter automatic_ipc=on
    Third, we can set to check the client whether its active after certain interval.
    If sqlnet.ora is not there, then it will take the default values.
    Thanks
    santhanam

Maybe you are looking for