Handling oracle commit erros at Appilcaton level in case of AWT

Hi All,
Incase AWT, All transactions committed successfully in the TimesTen database will be successfully propagated to and committed in the Oracle database. Execution errors on Oracle cause the transaction in the Oracle database to be rolled back
BUT AWT recognizes this Errors later , Since AWT propagates the commoted updates to oracle syncronously (The errors may be reported in the AWT error file long after the commit to TimesTen occurs). How these kind of errors handled at Application level, since Timesten do not raise thease errors immediately , mean while application might assumes that it got commited in oracle , it may procede with another set of transactions .
Kindly help on this
Thanks,
-AK

This is a problem with any type of asynchronous propagation. Details of any AWT apply errors are reported in the datastores .awterrs file. You can process that file to determine if there were any errors and maybe take recovery action. If your application cannot tolerate this type of behaviour then asynchronous propagation is not appropriate for you and you should use a different option.
Chris

Similar Messages

  • Handling Oracle RAC Failover at the application layer

    Hi All,
    I am currently researching best practices for handling oracle RAC failover at the application layer since transactional statements (INSERT,UPDATE and DELETE) are not handled transparently. So I have few questions for the community:
    1. In case of a node failure would I need to roll back all of transactional statements that are part of the transaction or would I have to re-execute the one that failed only?
    2. Does things change with XA 2 phase commit transactions?
    Any input and/or architecture suggestions would be much appreciated.
    Regards,
    Dmitriy Frolov

    Hi,
    the Oracle RAC stack works very vell on its own, without the need of a third party clusterware. It will be aware of failures on the nodes.
    Database will be using ASM or RAW or NFS devices for Shared storage.
    Oracle Clusterware can also be configured to monitor your applications and to a failover to other nodes.
    However if you need a shared filesystem for your own applications, then you will have to use QFS or similar (which again than requires Sun Cluster).
    See: http://www.oracle.com/technology/products/database/clusterware/index.html
    Regards
    Sebastian

  • How to handle a comma in a field in CSV file during FCC ?

    Hi,
    I am having a requirement where we have to convert a CSV file into XML using File Content Conversion . The issue is one of the field in the file is having a comma inside. So the XML parser is taking it as a field separator and throwing an error.
    The contents of the file are as follows:
    "02975859","New Key","9","Failed, rejected by RTI server"
    How to handle a comma inside field "Failed, rejected by RTI server".
    Any help would be appreciated.
    Regards
    Pravesh

    Hi ,
    You have to write an java mapping programm to perdromance this task , in a estandar way i think is not possible , because the fiel adapter have just one option for the delimiter character.
    Here's some code that could help you
    Supouse a file in this way:
    1,rahul,siemens,mumbai
    2,consultant,12032005
    1,viswanath,sisl,hyderabad
    2,systemeng,23052005
    package TXTMapping;
    import java.io.BufferedReader;
    import java.io.FileInputStream;
    import java.io.FileOutputStream;
    import java.io.InputStream;
    import java.io.InputStreamReader;
    import java.io.OutputStream;
    import java.util.Map;
    import com.sap.aii.mapping.api.StreamTransformation;
    public class TMapping implements StreamTransformation {
    private Map map;
    public void setParameter (Map param){
    map = param;
    public void execute (InputStream in, OutputStream out){
    try{
    out.write("<?xml version ='1.0' encoding='UTF-8'?>".getBytes());
    out.write("<ns0:Output_Data xmlns:ns0=\"urn:javamapping_test\">".getBytes());
    String line = null;
    BufferedReader bin = new BufferedReader(new InputStreamReader(in));
    StringBuffer buffer = new StringBuffer();
    while((line = bin.readLine())!= null){
    String Company = null;
    String Name = null;
    String Place = null;
    String Desgn = null;
    String Since = null;
    char[] str= new char[100];
    str = line.toCharArray();
    String[] Data = new String[10];
    int S1 = 0;
    int s2 = 2;
    for (int i=2; i<line.length(); i++)
    if (str<i>==',' && str[0]=='1')
    Data[S1]= line.substring(s2,i);
    S1=S1+1;
    s2 = i+1;
    if (i == line.length()-1 && str[0] == '1')
    Data[S1]= line.substring(s2,i+1);
    Name = Data[0];
    Company = Data[1];
    Place = Data[2];
    out.write ("<Data>".getBytes());
    out.write ("<Header>".getBytes());
    out.write (("<Name>"Name"</Name>").getBytes());
    out.write (("<Company>"Company"</Company>").getBytes());
    out.write (("<Place>"Place"</Place>").getBytes());
    out.write ("</Header>".getBytes());
    if (str<i>==',' && str[0]=='2')
    Data[S1]= line.substring(s2,i);
    S1=S1+1;
    s2 = i+1;
    if (i == line.length()-1 && str[0] == '2')
    Data[S1]= line.substring(s2,i+1);
    Desgn = Data[0];
    Since = Data[1];
    out.write ("<Item>".getBytes());
    out.write (("<Designation>"Desgn"</Designation>").getBytes());
    out.write (("<Since>"Since"</Since>").getBytes());
    out.write ("</Item>".getBytes());
    out.write ("</Data>".getBytes());
    out.write("</ns0:Output_Data>".getBytes());
    catch(Throwable t){
    t.printStackTrace();

  • Oracle JDBC driver's Isolation levels

    Hi!
    Is there a JDBC driver for oracle that supports transaction isolation levels other than TRANSACTION_READ_COMMITED and TRANSACTION_SERIALIZABLE?
    Thanks!

    Hi!
    Is there a JDBC driver for oracle that supports transaction isolation levels other than TRANSACTION_READ_COMMITED and TRANSACTION_SERIALIZABLE?
    Thanks!

  • What is the solution of  non-oracle exception erro 100501

    what is the solution of non-oracle exception erro 100501

    I'm guessing that the TRUE parameter in My_Alert causes the procedure to raise a form_trigger_failure. In that case you could do this:
    Declare
      A number(10);
    Begin
      SELECT Sif_Code
      INTO A
      FROM Pro_Stp_Rcp_Item
      WHERE Sif_Code = :Pro_Stp_Rcp_Item.Sif_Code
      AND Rou_Code = :Routes.Rou_Code;
      My_Alert('Item Code Already Registered',1,TRUE);
    Exception
      When form_trigger_failure then
        raise;
      When No_Data_Found Then null;
      When Too_Many_Rows
        Then My_Alert('Item Code Already Registered',1,TRUE);
      When Others
        Then My_Alert(Sqlerrm||' - '||sqlcode,1,TRUE);
    End;As Steve says, the problem is really caused by When Others here. I've got no problem with trapping "Others" but in forms you might be better off having a generic catch-all in the on-error trigger.

  • Handling oracle forms errors (frm-nnnnn) locally

    is there a way to handle an oracle form error (e.g. frm-40508) locally in a way similar to handle oracle database errors.
    e.g.
    procedure insert_something is
    insert_error exception;
    pragma exception_init(insert_error,-40508);
    begin
    :c1.a := 1;
    :c1.b := 2;
    commit_form;
    exception
    when insert_error then
    <handle insert error on c1 block>;
    end;
    Edited by: mojo on Oct 7, 2008 4:34 AM

    by locally i mean within the pl/sql block that will have raised the error.
    an example i encoutnered recently, but by no means the only occasion i have wished such things:
    function mseRecStatus returnvarchar2 is
    rtnChar varchar2(32);
    begin
    rtnChar := get_record_property(mouseRec,mouseBlock,status);
    return rtnChar;
    end;
    This is called from a pre-pop-menu trigger. mouseRec and block are calculated previously. A right-click on a record item below the last record raises error frm-40741 (unable to locate record on block). it would be nice to be able to do something like the following without incolving an on-error trigger:
    function mseRecStatus returnvarchar2 is
    rtnChar varchar2(32);
    non_record_clicked exception;
    pragma exception_init(non_record_clicked,-40741);
    begin
    rtnChar := get_record_property(mouseRec,mouseBlock,status);
    return rtnChar;
    exception
    when non_record_clicked then
    return null;
    end;

  • Oracle SLA Metrics and System Level Metrics Best Practices

    I hope this is the right forum...
    Hey everyone,
    This is what I am looking for. We have several SLA's setup and we have defined many Business Metrics and we are trying to map them to System level metrics. One key area for us is Oracle. I was wondering is there is a best practice guide out there for SLA's when dealing with Oracle or even better, System Level Metric best practices.
    Any help would be ideal please.

    Hi
    Can you also include the following in the FAQ?
    1) ODP.NET if installed prior to this beta version - what is the best practice ? De-install it prior to getting this installed etc ..
    2) As multiple Oracle home's have become the NORM these days - this being a Client only should probably be non-intrusive and non-invasive.. Hope that is getting addressed.
    3) Is this a pre-cursor to the future happenings like some of the App-Server evolving to support .NET natively and so on??
    4) Where is BPEL in this scheme of things? Is that getting added to this also so that Eclipse and .NET VS 2003 developers can use some common Webservice framework??
    Regards
    Sundar
    It was interesting to see options for changing the spelling of Webservice [ the first one was WEBSTER]..

  • Experience using Oracle Forms 10g w IBM Rational Clear Case & Build Forge

    Does anyone have experience using Oracle Forms 10g w IBM Rational Clear Case & Build Forge for configuration mgmt?
    Janice

    Hi,
    We had also different Installation (Win2k3 R2 32Bit and 64Bit.).
    1.) For me personally I didn't recognize benefits with 64 bit
    2.) when using Itanium you defenitely have to recompile. We had one Itanium at one of our customers; As Itanium is not x86 compatible you need to recompile on Itanium. it got kicked out and used for another purpose in cause of this and as mentioned the performance weren't so much higher (or in other words not noticeable). Another reason for getting rid of the damn Itanium was that Forms/Reports on Itanium Platform had some annoying bugs; but this was 10.1.2.0.2 maybe in 10.1.2.3 they're fixed.
    3.) If you want to use Itanium you simply have to transfer your fmb/mmb/pll to your Itanium IAS, and use forms and reports compiler which comes with it to recompile them.
    Generally at the moment we suggest our customers to use 32bit.
    just my 10 cents ;)
    regards

  • Handling Oracle error messages

    I'm hoping this is a simple question.
    I have an updatable report I'm using to collect data. It's pretty vanilla - I just used the default templates. I have a unique index constraint on the form's underlying table. When I violate the constraint and attempt to save a row, I get redirected to what looks to be a default error page that isn't very user friendly.
    Can someone tell me how I can specify a different error message depending on the error number Oracle returns?
    Thanks for any info.

    The whole problem is divided in two parts: Exception is defined or not, I'll show you haow to handle exception that do not exist and want to trap them.
    I saw that there is no named exception for ORA error "-00054", which is raised when record is locked. So I define my exception as:
    busy_resource EXCEPTION;
      PRAGMA EXCEPTION_INIT(busy_resource, -00054);Now to handle this exception in the Appex process looks like:
    begin
      ...your code ...
      :PXX_msg := 'OK!';
    exception
      when busy_resource THEN
        :PXX_msg := 'Record is locked. Try later';
      when others then
        :PXX_msg := 'Unknown error!;
    end;where "PXX_msg" is hidden item acesable on the page, XX represent page number.
    And in "Process Error Message" part of process don't put anything because all errors are handled and error will never happened. If you want that part put in excepttion part "RAISE;" command so erro will be raised!!!
    And in "Process Success Message" of the same process put also:
    "&PXX_msg."
    So you can see the result in much pleasent way!
    You have the same variable as result and now all to do is imagine exceptions that could happened. For the first time allways try to put some logging in "WHEN OTHERS THEN" part top collect as much as possible errors that could happened.
    Hope this helps!

  • Ask about DML Handler for Streams at the Schema level ?

    Hi all !
    I use Oracle version 10.2.0.
    I have two DB is A (at machine A, and it used as source database) and B (at machine B - destination database). Some changes from A will apply to B.
    At B, I installed oracle client to use EMC (Enterprise Manager Console) tool to generate some script, and use them to configure Streams environment, I configured Streams at the Schema level (DML and DDL) => I successed ! But I have two problems is:
    + I write a DML Handler, called "emp_dml_handler" and want set it to EMP table only. So, I must DBMS_STREAMS_ADM.ADD_TABLE_RULES ? (I configured: DBMS_STREAMS_ADM.ADD_SCHEMA_RULES) such as:
    BEGIN
    DBMS_STREAMS_ADM.ADD_SCHEMA_RULES(
    schema_name => '"HOSE"',
    streams_type => 'APPLY',
    streams_name => 'STRMADMIN_BOSCHOSE_REGRES',
    queue_name => 'apply_dest_hose',
    include_dml => true,
    include_ddl => true,
    source_database => 'DEVELOP.REGRESS.RDBMS.DEV.US.ORACLE.COM');
    END;
    and after:
    DECLARE
    emp_rule_name_dml VARCHAR2(50);
    emp_rule_name_ddl VARCHAR2(50);
    BEGIN
    DBMS_STREAMS_ADM.ADD_TABLE_RULES(
    table_name => 'HOSE.EMP,
    streams_type => 'APPLY',
    streams_name => 'STRMADMIN_BOSCHOSE_REGRES',
    queue_name => 'apply_dest_hose',
    include_dml => true,
    include_ddl => true,
    source_database => 'DEVELOP.REGRESS.RDBMS.DEV.US.ORACLE.COM',
    dml_rule_name => emp_rule_name_dml,
    ddl_rule_name => emp_rule_name_ddl);
    DBMS_APPLY_ADM.SET_ENQUEUE_DESTINATION(
    rule_name => emp_rule_name_dml,
    destination_queue_name => 'apply_dest_hose');
    END;
    BEGIN
    DBMS_APPLY_ADM.SET_DML_HANDLER(
    object_name => 'HOSE.EMP',
    object_type => 'TABLE',
    operation_name => 'UPDATE',
    error_handler => false,
    user_procedure => 'strmadmin.emp_dml_handler',
    apply_database_link => NULL,
    apply_name => NULL);
    END;
    ... similar for INSERT and DELETE...
    I think that I only configure streams at the schema level and exclude EMP table, am i right ?
    + At the source, EMP table have a primary key. And I configured:
    ALTER TABLE HOSE.EMP ADD SUPPLEMENTAL LOG DATA (PRIMARY KEY) COLUMNS;
    ==> So, at the destination, have some works that I must configure the substitute key for EMP table ?
    Have some ideas for my problems ?
    Thanks
    Edited by: changemylife on Sep 24, 2009 10:45 PM

    If you want to discard emp from schema rule, then just add a negative rule, either on capture or apply.
    What is the purpose of :
    DBMS_APPLY_ADM.SET_ENQUEUE_DESTINATION(
    rule_name => emp_rule_name_dml,
    destination_queue_name => 'apply_dest_hose');sound like you are enqueunig into 'apply_dest_hose' all the rows for this table that comes from ... 'apply_dest_hose'
    Next you declare a DML_HANDLER that is attached to nobody :
    BEGIN
    DBMS_APPLY_ADM.SET_DML_HANDLER(
    object_name => 'HOSE.EMP',
    object_type => 'TABLE',
    operation_name => 'UPDATE',
    error_handler => false,
    user_procedure => 'strmadmin.emp_dml_handler',
    apply_database_link => NULL,
    apply_name => NULL);           <----- nobody rules the world!
    END;the sequence of evaluation is normally :
    APPLY_PROCESS (reader)
              |
              | -->  RULE SET
                          |
                          | --> RULE .....
                          | --> RULE
                                     |
                                     | --> evaluate OK then --> exist DML_HANDLER  --> YES --> call DML_HANDLER --> on LCR.execute call coordinator
                                                                                            |
                                                                                            | NO
                                                                                            |                                                                 
                                                                                       Implicit apply (give LCR to coordinator which dispatch to one apply server)    
                                                      Since your dml_handler is attached to null apply process it will never be called by anybody and your LCR for table emp will be implicit applied by its apply process.

  • Need a way to handle oracle.jbo.RowInconsistentException

    This exception throws (as you know :-) when the another user changes data, and after that the first user tries to commit his changes ,by calling "Commit" operation binding from a pageDef, in a usual way :
            BindingContainer bindings = getBindings();
            OperationBinding operationBinding =
                bindings.getOperationBinding("Commit");
            Object result = operationBinding.execute();
            if (!operationBinding.getErrors().isEmpty()) {
                 // check to see if is there RowInconsistentException , and if so,
                 // the question is, what to do in order to refresh current view row ?
                 // NOTE that this code resists in a base class for all backing bean , so how to
                // know which iterator's current row should be refreshed, and centalize this in
               // one place ?
            } So , I would like to refresh the current View row, in order to allow first user to see new data (made by another user), and give chance to override current data posted by another user. But problem is - how to know the ViewObject which should be refreshed
    Or is there any other, in practice proven method to handle RowInconsistentException ?
    - thanks in advance ,...

    Hi,
    User want this functionality during the transaction or when updating collection plan results in Quality result?
    Ashish

  • UTL file exception handling oracle 11g

    We use oracle 11g
    We use UTL file and exception handling in many place. Thanks in advance.
    We have many utl program and we are writing same exception handling code ,copy and paste .
    It is possible to create new UTL exception procedure and call it.
    I am not sure how to write generic UTL exception procedure and reuse the same.
    I am learning oracle etl files method.
    Please advise.
    sample program 1 :
    DECLARE
    fileHandler UTL_FILE.FILE_TYPE;
    BEGIN
    fileHandler := UTL_FILE.FOPEN('test_dir', 'test_file.txt', 'W');
    UTL_FILE.PUTF(fileHandler, 'Writing TO a file\n');
    UTL_FILE.FCLOSE(fileHandler);
    EXCEPTION
    when utl_file.invalid_path then
    raise_application_error(-20001,
    'INVALID_PATH: File location or filename was invalid.');
    when utl_file.invalid_mode then
    raise_application_error(-20002,
    'INVALID_MODE: The open_mode parameter in FOPEN was invalid.');
    when utl_file.invalid_filehandle then
    raise_application_error(-20002,
    'INVALID_FILEHANDLE: The file handle was invalid.');
    when utl_file.invalid_operation then
    raise_application_error(-20003,
    'INVALID_OPERATION: The file could not be opened or operated on as requested.');
    when utl_file.read_error then
    raise_application_error(-20004,
    'READ_ERROR: An operating system error occurred during the read operation.');
    when utl_file.write_error then
    raise_application_error(-20005,
    'WRITE_ERROR: An operating system error occurred during the write operation.');
    when utl_file.internal_error then
    raise_application_error(-20006,
    'INTERNAL_ERROR: An unspecified error in PL/SQL.');
    when utl_file.invalid_filename then
    raise_application_error(-20010, 'The filename parameter is invalid.');
    WHEN OTHERS THEN
    IF UTL_FILE.IS_OPEN(fileHandler ) THEN
    UTL_FILE.FCLOSE (fileHandler );
    END IF;
    RAISE;
    END;
    How to write generic procedure of utl exception handling ?
    please advise.
    create or replace procedure sp_utl_exception
    begin
    when utl_file.invalid_path then
    raise_application_error(-20001,
    'INVALID_PATH: File location or filename was invalid.');
    when utl_file.invalid_mode then
    raise_application_error(-20002,
    'INVALID_MODE: The open_mode parameter in FOPEN was invalid.');
    when utl_file.invalid_filehandle then
    raise_application_error(-20002,
    'INVALID_FILEHANDLE: The file handle was invalid.');
    when utl_file.invalid_operation then
    raise_application_error(-20003,
    'INVALID_OPERATION: The file could not be opened or operated on as requested.');
    when utl_file.read_error then
    raise_application_error(-20004,
    'READ_ERROR: An operating system error occurred during the read operation.');
    when utl_file.write_error then
    raise_application_error(-20005,
    'WRITE_ERROR: An operating system error occurred during the write operation.');
    when utl_file.internal_error then
    raise_application_error(-20006,
    'INTERNAL_ERROR: An unspecified error in PL/SQL.');
    when utl_file.invalid_filename then
    raise_application_error(-20010, 'The filename parameter is invalid.');
    WHEN OTHERS THEN
    IF UTL_FILE.IS_OPEN(fileHandler ) THEN
    UTL_FILE.FCLOSE (fileHandler );
    END IF;
    RAISE;
    end;

    Mahesh Kaila wrote:
    Hello,
    Common procedure to log exception in log file
    create or replace procedure sp_utl_exception (log_dir varchar2, log_file varchar2, exception_msg varchar2)
    is
    hnd_file   UTL_FILE.file_type;
    begin
    hnd_file := UTL_FILE.fopen (log_dir, log_file, 'A');
    UTL_FILE.put_line (hnd_file, exception_msg);
    UTL_FILE.fclose (hnd_file);
    exception
    when others
    then
    raise;
    end;
    Very poor implementation.
    a) Absolutely no need for that exception handler in there. It should be removed.
    b) As it's a procedure for logging exceptions relating to UTL_FILE, it would seem error prone to be logging the errors with UTL_FILE. For example, what is it supposed to do if the exception is raised because of lack of disk space in those file locations? How is it going to write out the exception with the disk full? Also, if the exception handler is used by multiple processes, then only 1 process at a time can access the log file to write it's exceptions, so it doesn't scale well. Better logging is done by having an autonomous transaction procedure that writes log/trace messages to dedicated table(s). That also means that the logs etc. can be viewed, as appropriate, from any client using SQL (either manually or through a application written to view logs etc.), rather than requiring physical/remote access to the server o/s to go and view the contents of the file, which in itself could lock the file and prevent any process from writing further logs whilst it's being used.

  • Handling Unit creation at Sales order Level

    Hi Experts ,
    Please let me know,how can a handling unit be created at sales order level.
    Your comments will be appreciated
    Regards
    Albert

    Albert Ackerman wrote:>
    > Hi Experts ,
    >
    > Please let me know,how can a handling unit be created at sales order level.
    >
    > Your comments will be appreciated
    >
    > Regards
    >
    > Albert
    Hi Albert,
    I am not sure if i got your requirement correctly.
    Nevertheless if you are asking where do you maintain Handling Type HT in sales order:
    Choose the line items double click (goto details of line items)
    Go to Excise Duty tab and put the required Handling type.
    If you want to know where do we configure Handling types.
    Goto
    SPRO->Industry Solution Oil&Gas(downstream)->TDP(Tariffs, Duties & Permits)->Global Settings->Parameter Definition->Set Handling Type.
    If you want to know the related tables for Handling type they are
    OIH07, OIH27
    Hope i addressed to your expectation.
    Post for furthur clarification
    Regards
    Abhishek Swarup

  • Oracle XA driver and isolation level

    We have an Entity EJB that has isolation level specified in its
    deployment descriptor and everything works fine if we use the non-XA
    Oracle 9i driver.
    However when we use the Oracle 9i Release 2 XA driver we get the
    following exception:
    java.sql.SQLException: Due to vendor limitations, setting transaction
    isolation for "Oracle 8.1.7 XA" JDBC XA driver is not supported.
    at
    weblogic.jdbc.jta.DataSource.setTxIsolationFromTxProp(DataSource.java:1126)
    at
    weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1109)
    at weblogic.jdbc.jta.Connection.getXAConn(Connection.java:145)
    at weblogic.jdbc.jta.Connection.getAutoCommit(Connection.java:247)
    at
    weblogic.jdbc.rmi.internal.ConnectionImpl.getAutoCommit(ConnectionImpl.java:173)
    at
    weblogic.jdbc.rmi.SerialConnection.getAutoCommit(SerialConnection.java:164)
    Note the 8.1.7 version that the container prints. The driver is
    definitely 9i and not 8.1.7 and it's the very first thing in the classpath.
    Is this a problem with the driver really or is it a WLS issue?
    Thanks,
    Dejan

    Hi,
    I removed the transaction isolation level setting from the deployment
    descriptor and it works now as expected.
    But in the meanwhile I also ran a test by using the driver directly
    without Weblogic and I was able to successfully set the transaction
    isolation level on the XA connections so I believe it's a Weblogic problem.
    Dejan
    Deyan D. Bektchiev wrote:
    Yes,
    We know about this but we just try to set it to the default one
    (READ_COMMITED) which is probably redundant for Oracle but might not
    be the default one for another DB vendor.
    Here is the part of the deployment descriptor:
    <transaction-isolation>
    <isolation-level>TRANSACTION_READ_COMMITTED</isolation-level>
    <method>
    <ejb-name>Event</ejb-name>
    <method-name>*</method-name>
    </method>
    </transaction-isolation>
    Dejan
    Slava Imeshev wrote:
    Deyan,
    I'm not 100% sure, but AFAIR oracle doesn't support all isolation
    levels.
    Which level do you set? Could you show us this part of the deployment
    descriptor?
    Slava
    "Deyan D. Bektchiev" <[email protected]> wrote in message
    news:[email protected]...
    Thanks for the reply Sree,
    Yes the 9i driver is the very first thing in the classpath as otherwise
    we wouldn't even be able to connect to the 9i database with the 8.1.7
    driver (we were getting lots of other exceptions when we were still
    using the 8.1.7 driver).
    I'll try removing the setting of the isolation level and I'll post the
    result to the newsgroup.
    Dejan
    Sree Bodapati wrote:
    hi Deyan,
    java.sql.SQLException: Due to vendor limitations, setting
    transaction
    isolation for "Oracle 8.1.7 XA" JDBC XA driver is not supported.
    should not have showed up with wrong version of oracle. If you can
    verifiy
    that the thin driver is the first thing in the classpath and you are
    indeed
    using the thin driver, This is a bug.
    But in this case it looks like you need to remove the
    TransactionIsolation
    level from the EJB descriptor to get this to work. can you try that? I
    will
    forward this to one of our EJB engineers and see if we can get some
    help
    for
    you.
    sree
    "Deyan D. Bektchiev" <[email protected]> wrote in message
    news:[email protected]...
    Sree,
    We already did but the only answer we got was that the Oracle 9i
    Release
    2 driver was not at all supported by Weblogic 7.0 SP1.
    But the certification page says that it is even certified...
    So which one is true: The Oracle 9i Release 2 driver is not
    supported or
    is supported?
    --dejan
    Sree Bodapati wrote:
    Please file a support case for this at [email protected]
    "Deyan D. Bektchiev" <[email protected]> wrote in message
    news:[email protected]...
    We have an Entity EJB that has isolation level specified in its
    deployment descriptor and everything works fine if we use the
    non-XA
    Oracle 9i driver.
    However when we use the Oracle 9i Release 2 XA driver we get the
    following exception:
    java.sql.SQLException: Due to vendor limitations, setting
    transaction
    isolation for "Oracle 8.1.7 XA" JDBC XA driver is not supported.
    at
    weblogic.jdbc.jta.DataSource.setTxIsolationFromTxProp(DataSource.java:1126
    at
    weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1109)
    at weblogic.jdbc.jta.Connection.getXAConn(Connection.java:145)
    at
    weblogic.jdbc.jta.Connection.getAutoCommit(Connection.java:247)
    at
    weblogic.jdbc.rmi.internal.ConnectionImpl.getAutoCommit(ConnectionImpl.jav
    a
    >
    173)
    at
    weblogic.jdbc.rmi.SerialConnection.getAutoCommit(SerialConnection.java:164
    Note the 8.1.7 version that the container prints. The driver is
    definitely 9i and not 8.1.7 and it's the very first thing in the
    classpath.
    Is this a problem with the driver really or is it a WLS issue?
    Thanks,
    Dejan

  • Handle doc/open event at folder level

    Hi,
    Is there a way to handle doc/open event at the folder level?

    javax.sing.table.AbstractTableModel.addTableModelListener(TableModelListener l)

Maybe you are looking for