• Topic
  • Discussion
  • UdaWikiWeb.NonSelectInRO(Last) -- Owiki? , 2016-08-19 15:00:36 Edit owiki 2016-08-19 15:00:36

    Error Messages (N)

    A B C D E F G H I J K L M N O P Q R S T U V W X Y Z #

    Non SELECT in r/o connection

    The "Non SELECT in r/o connection" error message suggest that you have read-only permissions on the table against which you are trying to query. Review this possibility. Additionally, your OpenLink Session Rules Book may be enforcing READONLY connections. The following instructions will help you to verify or dismiss this fact:

    1. Use a text editor to open the oplrqb.ini file which you find in the /bin sub-directory of your OpenLink server components installation.

    2. Scroll down to [Domain Aliases].

    3. Locate the domain, which you pass in the Domain or ServerType field of your client's DSN. For example:

    Informix 7 = inf7
    


    4. Scroll down to [Mapping Rules].

    5. Locate your domain alias abbreviation. For example:

    inf7:*:*:*:*:*:* = accept generic_inf7
    


    6. Find the [generic_xxxx] section which is associated with your alias. For example:

    [generic_inf72]
    Description = Default settings for Informix 7.2 agent
    Program = inf72_sv
    Environment = INFORMIX72
    OpsysLogin = Yes
    ReUse = never
    ;CommandLine =
    ;ConnectOptions =
    ;Directory = /tmp
    ;Database =
    ;Userid =
    ;Password =
    ReadOnly = Yes
    


    7. Insure that ReadOnly is set to No. For example:

    ReadOnly = No
    


    9. If you make changes, restart or reinitialize your OpenLink Request Broker.

    Finally, one build of OpenLink's 3.2 software (3.20.09.14) contains a bug. These 3.2 clients issue a SQLSetConnectOption ODBC API call, which sets the SQL_ACCESS_MODE to 1. This enforces a read-only connection. Below, you will see a sample ODBC API call associated with this problem:

    ENTER SQLSetConnectOption
    HDBC 091D14D8
    UWORD 101 <SQL_ACCESS_MODE>
    SQLLEN 1
    


    If your 3.2 software contains this bug, you will need to upgrade your software. (The fix was introduced in OpenLink 4.0.) If you are uncertain about the presence of a bug, forward a trace and your client driver version to OpenLink Product Support.

    Evidence

    Session Rules Book
    Request Broker Log
    Database Agent Version String


    Referenced by...