8.1.7 personal and ORA-03113 error

Got a colleague trying to install 8.1.7 personal on to a laptop running XP on a P3 chip, 512 ram.
Installation runs through to the creation of the database and then falls over with a 03113. Click on abort and install finishes. Go back and try to create the database manually and get the same error.
An ides?

Please Favour to me that i am asking about some installation guidlines from you
1. can personal oracle 8 support for windows 2000 professional.
2. personal oracle 8 for NT same For Windows 2000 professional.
please Send me suggesstion soon as possible for my email account [email protected]

Similar Messages

  • SDO_RELATE and ORA-03113 error

    Hello,
    I am trying to use the SDO_RELATE function and I receive the following error:
    ERROR at line 1:
    ORA-03113: end-of-file on communication channel
    Using the following SQL
    SELECT ufi FROM ROADLINE A
    WHERE MDSYS.SDO_RELATE(
    A.GEOMETRY, mdsys.sdo_geometry( 2003,null,null,
    mdsys.sdo_elem_info_array(1,1003,3),
    mdsys.sdo_ordinate_array(132,-12,133,-11)),
    'mask=ANYINTERACT querytype=WINDOW') = 'TRUE'
    A similar search using the SDO_FILTER instead of SDO_RELATE and removing the mask=ANYINTERACT works ok.
    Can anyone suggest anything?
    Thanks in advance.
    Gunter

    Hi Gunter,
    It looks like there may be other issues. Can you post the version of Oracle you are using, and try debugging just a little bit more to try to narrow the problem down?
    This might help to determine which geometry the failure is occuring at:
    create table tt as select ufi,geometry
    from roadline where rownum < 1;
    declare
    ufi number ;
    window_geom mdsys.sdo_geometry := mdsys.sdo_geometry( 2003,null,null, mdsys.sdo_elem_info_array(1,1003,3),
    mdsys.sdo_ordinate_array(132,-12,133,-11));
    theGeom mdsys.sdo_geometry ;
    TYPE geomcursor is REF CURSOR ;
    aCursor geomcursor;
    relationship varchar2(30);
    begin
    open aCursor FOR 'SELECT ufi, geometry from roadline A WHERE SDO_filter( A.GEOMETRY,:WINDOW_GEOM, ''querytype=WINDOW'') = ''TRUE''' using window_geom;
    loop
    FETCH aCursor INTO ufi, theGeom ;
    EXIT WHEN aCursor%NOTFOUND ;
    execute immediate 'insert into tt values (:ufi,:theGeom)'
    using ufi,theGeom;
    execute immediate 'commit';
    relationship := sdo_geom.relate(theGeom,'anyinteract',window_geom,0.05);
    end loop;
    end;
    If you see the same error, hopefully it will be determining the relationship between the last geometry in the table tt and the query window. If you can check this, and if this is the case post the geometry that is failing as well as the contents of user_sdo_geom_metadata for roadline that would be great.
    Dan

  • Deleting application results in ORA-03113 error

    I'm having trouble deleting applications from my workspace. Every time I attempt to delete an application, I get an ORA-03113 error.
    It doesn't seem to matter whether or not I choose to include the Application Definition or Supporting Objects when deleting.
    If I cancel and keep trying to delete the application, the db crashes. When this happens the .trc file shows multiple memory errors and the alert log shows multiple core dumps.
    db version = *10.2.0.1*
    apex version = *3.2*
    If anyone has experience with similar issues, any suggestions would appreciated. This problem has been a real pain.
    Keith Malay
    www.sds-cg.com

    Keith,
    There are quite a few hits on Metalink for this error. You may want to go there and see if you can find a patch (of which there seems to be several) or some other method of troubleshooting this problem.
    Here is what Doc ID: 1020463.6 has to say in the introduction:
    The ORA-3113 error is a general error reported by Oracle client tools,
    which signifies that they cannot communicate with the oracle shadow
    process. As it is such a general error more information must be collected
    to help determine what has happened.
    Than note's title is "Diagnosing ORA-3113 Errors".
    Good luck,
    Don.

  • Ora-03113 error in version 8.0.5

    kindly guide me through the procedure to solve ora-03113 error "end of file on communication channel" in database version 8.0.5

    after instance started up, in sqlplus type:
    SQL> show parameter background_dump_dest
    NAME TYPE VALUE
    background_dump_dest string /oracle/home92/admin/dump ->>>> this is in my caseGo to that folder (which is in your case) and there should be alert_YOUR_DB_NAME.log and open it with text editor and copy/paste last 100 lines here.
    Edited by: drop.any on Nov 2, 2009 2:53 AM

  • Ora-03113 error with XMLTABLE inside subquery or view

    I'm getting ORA-03113 error if I use a result of XMLTABLE inside a subquery of another query (whether XMLTABLE is inline, or from a view). Code below to reproduce this - vastly simplified and now rather meaningless - but produces same error. Has anyone saw this error re. XMLTABLE or know of metalink bugs on this ? I couldn't find anything. I'm having to use deprecated table(xmlsequence) instead, which doesn't get this error.
    --DROP TABLE TEST
    CREATE TABLE TEST(ID number(10), CUST_REF varchar2(50 char), XMLDATA XMLTYPE);
    INSERT INTO TEST(ID, CUST_REF, XMLDATA) VALUES (1, 'XYZ',
    XMLTYPE('<?xml version="1.0" encoding="utf-16"?>
    <TESTXML
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns="urn:ABC-123:TESTXML">
    <collections>
    <TRANSACTION_COLLECTION>
    <TRANSACTION>
    <RECORD_ID>1</RECORD_ID>
    <TRANSACTION_ID>7791786</TRANSACTION_ID>
    <AMOUNT>335</AMOUNT>
    <TYPE>I</TYPE>
    <DC>DR</DC>
    </TRANSACTION>
    </TRANSACTION_COLLECTION>
    </collections>
    </TESTXML>'));
    COMMIT;
    CREATE VIEW TEST_XMLVIEW
    AS
    SELECT
    ID,
    CUST_REF,
    xmltbl.RECORD_ID,
    xmltbl.TRANSACTION_ID,
    xmltbl.AMOUNT,
    xmltbl.TYPE,
    xmltbl.DC
    FROM TEST,
    XMLTable(XMLNamespaces(DEFAULT 'urn:ABC-123:TESTXML'),
    '/TESTXML/collections/TRANSACTION_COLLECTION/TRANSACTION' PASSING TEST.XMLDATA
    COLUMNS
    "RECORD_ID" number(10) PATH 'RECORD_ID',
    "TRANSACTION_ID" VARCHAR(200 CHAR) PATH 'TRANSACTION_ID',
    "DC" VARCHAR(200 CHAR) PATH 'DC',
    "TYPE" VARCHAR(200 CHAR) PATH 'TYPE',
    "AMOUNT" NUMBER(38,8) PATH 'AMOUNT')
    AS xmltbl;
    WITH SUM_AMOUNTS (ID, CUST_REF, SUM_1, SUM_2, SUM_3)
    AS
    (SELECT ID, CUST_REF, SUM(AMOUNT) AS SUM_1, SUM(AMOUNT) AS SUM_2, SUM(AMOUNT) + SUM(AMOUNT) AS SUM_3
    FROM TEST_XMLVIEW
    GROUP BY ID, CUST_REF)
    select
    ID,
    CUST_REF,
    SUM_1,
    SUM_2,
    SUM_3
    from SUM_AMOUNTS;
    Version Details:
    Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
    PL/SQL Release 11.2.0.2.0 - Production
    CORE     11.2.0.2.0     Production
    TNS for 64-bit Windows: Version 11.2.0.2.0 - Production
    NLSRTL Version 11.2.0.2.0 - Production

    Has anyone saw this error re. XMLTABLE or know of metalink bugs on this ? I couldn't find anything.Really?
    Go to the trace directory and find the relevant trace/incident file.
    On my system, I can see something like this :
    ORA-07445: exception encountered: core dump [evaopn3()+656] [ACCESS_VIOLATION] [ADDR:0x0] [PC:0x234A5B6] [UNABLE_TO_READ] []Copy/paste that line into the ORA-00600/ORA-07445 look-up tool on My Oracle Support and run the search for your version.
    You will find this article :
    *ORA-7445 (evaopn3) [ID 860969.1]*
    and at the bottom of the page, among the known related bugs, this one :
    *Bug 12724375 : ORA-7445 [evaopn3] from XQuery with GROUP BY*

  • ORA 03113 error creating database

    On Oracle 8.1.7, I've get an ORA 03113 error when creating the database. Pressing ignore leaves it hanging at 90%. I've tried creating db by copying files from CD and creating with custom parameters but same issue. There have been other threads regarding this error but no responses. I couldn't find any logs with specific error messages in my temp directory. Are there any logs I can refer to? How can I resolve this issue? I am on NT 4, SP6. Thanks.

    Hi Tim,
    Have you checked the setup files for the appropriate Net8 driver correctly installed on the server? I'd look at this you not have the correct Oracle networks drivers or a compatibility issue with them. Try reinstalling net8. This is really a Two-Task Common error (TTC) in the net8 stack.
    HTH
    Steve
    On Oracle 8.1.7, I've get an ORA 03113 error when creating the database. Pressing ignore leaves it hanging at 90%. I've tried creating db by copying files from CD and creating with custom parameters but same issue. There have been other threads regarding this error but no responses. I couldn't find any logs with specific error messages in my temp directory. Are there any logs I can refer to? How can I resolve this issue? I am on NT 4, SP6. Thanks.

  • CTX_DDL.SYNC_INDEX  gives ORA-03113 error

    I am trying to use the CTX_DDL.SYNC_INDEX command in order to update the full Text Index on a table, which contains a word document as a binary object, but I get an ORA-03113 error every time I do this. I get the same error if the table contains an Excel file. It works perfectly OK if the table contains simple text files.

    Hi Barbara - thanks for your response.
    In answer to your questions;
    Oracle version is 9.2.0.1.0
    Table structure is created with following sql;
    CREATE TABLE DOCUMENTFILE
         (DOCUMENTFILEID      NUMBER (10,0) NOT NULL,
         DATA                LONG RAW,
         FILE_SIZE           NUMBER (10,0),
         FILENAME           VARCHAR2 (510),
         ENCRYPTIONKEY           VARCHAR2 (100),
         VALIDATIONKEY           VARCHAR2 (100),
         MIMETYPE           VARCHAR2 (255),
         FILEEXTENSION           CHAR (3),
         DELETED           NUMBER (1,0)
    Index is created with following command
    CREATE INDEX ORGANISATION_TEXT_INDEX
    ON COLLABORATOR.ORGANISATION(ORGANISATION_NAME)
    INDEXTYPE IS CTXSYS.CONTEXT PARAMETERS ('');
    Resync command is as follows
    EXEC CTX_DDL.SYNC_INDEX('DOCUMENT_TEXT_INDEX');
    I am testing by runing the command via SQL Plus
    In response to question 'Are you using inso_filter or auto_filter? ' - I dont know
    Thanks for your help,
    Peter

  • ORA-00001 and ORA-06512 error on  DBMS_WM.ResolveConflicts

    We are getting unique constraint error in Production Database. We are able to merge most of the workspaces with no issues. One workspace is givign errors on merge.
    Here is the code
    begin
    dbms_wm.gotoworkspace('denialletterspoc_onmzpulp');
    dbms_wm.setdiffversions('denialletterspoc_onmzpulp','LIVE');
    dbms_wm.SetConflictWorkspace('denialletterspoc_onmzpulp');
    commit;
    DBMS_WM.BeginResolve('denialletterspoc_onmzpulp');
    DBMS_WM.ResolveConflicts(
    workspace => 'denialletterspoc_onmzpulp',
    table_name => 'MCM_MESSAGE',
    where_clause => ' id in (8403026,10134822,8259485,8259488,8426289,8426287,10186643,8426288) ',
    keep => 'CHILD'
    exception when others then
    DBMS_WM.RollbackResolve('denialletterspoc_onmzpulp');
    raise;
    end;
    ORA-00001: unique constraint (T2.MCM_MESSAGE_PK) violated
    ORA-06512: at line 16
    I looked at the date in XXX_lt tables and it does not look suspecious. Please help us understand
    ORA-00001 and ORA-06512 error.
    Amit Gangwar

    Hi, Ben
    Our OWM_VERSION is 10.2.0.4.3.
    I tried disable and enable constraint MCM_MESSAGE_PK. But didn't fix our issue.
    Split where clause from " id in (...) " syntax to " id = ... " syntax will reduce performance heavily. And I did some test that " id in (...) " syntax works well in our dev env.
    I opened our trace file and get below plsql block. When I perform it get same error with our original codes. Please notice the part of "forall wm_indx in WM_rowids.first .. WM_rowids.last execute immediate 'begin insert into T2.MCM_MESSAGE_lt ... ...", error occurred here. But if I change the "forall" syntax to normal " for ... loop" syntax then no error here. Can you give me some advice or suggestion?
    DECLARE
    WM_rowids wmsys.lt_ctx_pkg.rowidTabType;
    WM_rowids_vt wmsys.lt_ctx_pkg.rowidTabType;
    WM_curver wmsys.lt_ctx_pkg.int_tab;
    WM_vtRow wmsys.lt_ctx_pkg.int_tab;
    WM_nextver wmsys.lt_ctx_pkg.nextver_tab;
    WM_found integer := 0;
    BEGIN
    dbms_wm.gotoworkspace('denialletterspoc_onmzpulp');
    dbms_wm.setdiffversions('denialletterspoc_onmzpulp','LIVE');
    dbms_wm.SetConflictWorkspace('denialletterspoc_onmzpulp');
    /* update the auxilliary table of snapshots */
    /* These are rows in the current version that have already been resolved once */
    update T2.MCM_MESSAGE_aux st
    set (snapShotChild, snapShotParent, versionParent) =
    (select p.WM_childds, p.WM_parentds, p.WM_parentver
    from T2.MCM_MESSAGE_pkc p
    where p.ID = st.ID),
    value = '0',
    wm_opcode = 'CC'
    where st.versionChild = 614
    and (ID) in (select ID
    from T2.MCM_MESSAGE_pkc p
    where (id in (8403026,
    10134822,
    8259485,
    8259488,
    8426289,
    8426287,
    10186643,
    8426288)));
    select distinct WM_ridchild bulk collect
    into WM_rowids
    from T2.MCM_MESSAGE_pkc
    where (id in (8403026,
    10134822,
    8259485,
    8259488,
    8426289,
    8426287,
    10186643,
    8426288))
    and WM_childver != 614;
    if (WM_rowids.first is not null) then
    WM_found := 1;
    forall wm_indx in WM_rowids.first .. WM_rowids.last
    update T2.MCM_MESSAGE_lt
    set retireTime = wmsys.owm_9ip_pkg.activeTimeForDML,
    nextver = wmsys.lt_ctx_pkg.getNextVer(nextver,
    614,
    version,
    'denialletterspoc_onmzpulp',
    'CRS_LEAF',
    22)
    where rowid = WM_rowids(wm_indx)
    returning wmsys.lt_ctx_pkg.getCurNextVer bulk collect into WM_nextver;
    /* These are the rows that have not yet been resolved after the latest BeginResolve */
    forall wm_indx in WM_rowids.first .. WM_rowids.last execute immediate
    'begin insert into T2.MCM_MESSAGE_lt(ID,DPS_APPLICATION_ID,TYPE_ID,NAME,PRIVILEGED,CAMPAIGN_ID,TEXT,FILE_NAME,GRAPHIC_WIDTH,GRAPHIC_HEIGHT,DESCRIPTION,ACTIVE,INCLUDE_IN_LIBRARY,MESSAGE_FILTER_ID,OP_USER_ID,OP_WORKSPACE,OP_TIME,version,createtime,retiretime,nextver,delstatus,ltlock)
    (select t1.ID,t1.DPS_APPLICATION_ID,t1.TYPE_ID,t1.NAME,t1.PRIVILEGED,t1.CAMPAIGN_ID,t1.TEXT,t1.FILE_NAME,t1.GRAPHIC_WIDTH,t1.GRAPHIC_HEIGHT,t1.DESCRIPTION,t1.ACTIVE,t1.INCLUDE_IN_LIBRARY,t1.MESSAGE_FILTER_ID,t1.OP_USER_ID,t1.OP_WORKSPACE,t1.OP_TIME,614, wmsys.owm_9ip_pkg.activeTimeForDML, null,:1, sign(delstatus)*(abs(delstatus)+1),
    wmsys.lt_ctx_pkg.checkngetlock(''C'', t1.ltlock, t1.nextver, ''denialletterspoc_onmzpulp'', 0,
    ''MODIFY'', t1.version, t1.delstatus, 0, 1)
    from T2.MCM_MESSAGE_lt t1
    where t1.rowid = :2); end;'
    using WM_nextver(wm_indx),
    WM_rowids(wm_indx)
    end if;
    if (WM_found = 1) then
    wmsys.lt_ctx_pkg.update_modified_tables('T2',
    'MCM_MESSAGE',
    614,
    'denialletterspoc_onmzpulp',
    22);
    end if;
    if (WM_found = 1) then
    forall wm_indx in WM_rowids.first .. WM_rowids.last
    delete from T2.MCM_MESSAGE_aux
    where (ID) in (select ID
    from T2.MCM_MESSAGE_lt
    where rowid = WM_rowids(wm_indx))
    and childState = 'denialletterspoc_onmzpulp';
    end if;
    /* now insert new syncing information about these rows */
    execute immediate 'insert into T2.MCM_MESSAGE_aux (
    select ID,
    p.WM_childstate, p.WM_parentstate,
    p.WM_childds, 614, p.WM_parentds, p.WM_parentver, ''0'',''CC''
    from T2.MCM_MESSAGE_pkc p
    where ( id in (8403026,10134822,8259485,8259488,8426289,8426287,10186643,8426288) ) )';
    END;
    Thanks
    Amos

  • Ora - 01110 and ora 01157 error

    Hi,
    I am using linux 9i and solaris 5.8 .while i am connecting to the database it shows the ora - 01110 and ora 01157 error.i moved the temp datafile to some location after that only i receiced that error.then i moved the temp file to the particular location.after that what i can to do to resolve the error.
    plz in detail sql query.
    Thanks
    gobi.

    Can you detail how you are moving the file? Are you using one of the following methods:
    With the database down
    move/rename the file with OS commands
    mount the database and issue the following
    alter database rename file '<original path and file name>' to '<new path and file name>';
    Open the database
    or
    With the database open take the tablespace the contains the files to be moved/rename offline.
    move/rename the files with OS commands.
    alter tablespace <tablespace name> rename datafile '<original path and file name>' to '<new path and file name>';
    Bring the tablespace back online.

  • ORA-03113 and ORA-01041 errors

    One of our customer is getting intermittent errors in the XA log.
    ORACLE XA: Version 8.0.5.0.0. RM name = 'Oracle_XA'.
    095809.6179..0:
    ORA-03113: end-of-file on communication channel
    095820.6179..0:
    ORA-01041: internal error. hostdef extension doesn't exist
    What could possible be wrong ?
    null

    Rajesh Mahajan (guest) wrote:
    : One of our customer is getting intermittent errors in the XA
    log.
    : ORACLE XA: Version 8.0.5.0.0. RM name = 'Oracle_XA'.
    : 095809.6179..0:
    : ORA-03113: end-of-file on communication channel
    : 095820.6179..0:
    : ORA-01041: internal error. hostdef extension doesn't exist
    : What could possible be wrong ?
    Hi Rajesh , in my opinion you lost the communication with your
    server . The server could be shutdown an restart again while
    your aplication is running or waiting for any execution. With
    Oracle Forms this happen an the forms loose the conection with
    the server , but seems that this aplication was already running.
    You only get close the forms , in NT , with the Task Manager
    and End the Task . In the Sql Plus ocuurs the same but you can
    close the section or make another conection with your database.
    I hope help you ,
    Regards
    Lourival
    null

  • SQL*Net and Datapump export disconnects with ORA-03113 error

    Hi,
    I have some trouble with an Oracle 11.2.0.1.0 server installation on a Windows 2008 R2 server.
    If I am connected with SQL*Plus on the database server to an instance it randomly disconnects me, but no longer than after 30-60 seconds even though I am active running simple select queries.
    I can connect again without any error and soon it disconnects me again.
    If I am running an expdp, datapump export it starts but displays error UDE-03113 and then ORA-03113. The datapump export continues in the background and finish successfully though.
    When having a look at the Alert.log for the database instance I see this error everytime it happens:
    Fatal NI connect error 12547, connecting to:
    (LOCAL=NO)
    VERSION INFORMATION:
         TNS for 64-bit Windows: Version 11.2.0.1.0 - Production
         Oracle Bequeath NT Protocol Adapter for 64-bit Windows: Version 11.2.0.1.0 - Production
         Windows NT TCP/IP NT Protocol Adapter for 64-bit Windows: Version 11.2.0.1.0 - Production
    Time: 22-JUL-2012 21:10:40
    Tracing not turned on.
    Tns error struct:
    ns main err code: 12547
    TNS-12547: TNS:lost contact
    ns secondary err code: 12560
    nt main err code: 0
    nt secondary err code: 0
    nt OS err code: 0
    opiodr aborting process unknown ospid (19800) as a result of ORA-609
    Mon Jul 23 02:00:00 2012
    I don't believe it is an network problem as each command I am running is on the server console. No other errors in the OS event log so I need some help where to start...
    Thanks in advance!
    Best Regards
    Martin Gabrielsson

    Thanks, no windows firewall turned on, I turned on SQL*Net tracing and this is the last part of the trc file after doing a simple select query on a table with 3 rows. After the select query has been runned I am disconnected... Any idea, help is really appreciated!
    +2012-07-30 18:15:28.658650 : nsbasic_brc:packet dump+
    +2012-07-30 18:15:28.658660 : nsbasic_brc:01 74 00 00 06 00 00 00 |.t......|+
    +2012-07-30 18:15:28.658668 : nsbasic_brc:00 00 06 01 1A 00 26 00 |......&.|+
    +2012-07-30 18:15:28.658676 : nsbasic_brc:00 00 00 00 0F 00 00 00 |........|+
    +2012-07-30 18:15:28.658684 : nsbasic_brc:00 00 00 00 00 00 00 00 |........|+
    +2012-07-30 18:15:28.658693 : nsbasic_brc:00 00 00 00 00 00 00 00 |........|+
    +2012-07-30 18:15:28.658701 : nsbasic_brc:00 00 00 00 00 00 00 00 |........|+
    +2012-07-30 18:15:28.658708 : nsbasic_brc:00 00 00 00 00 00 00 00 |........|+
    +2012-07-30 18:15:28.658717 : nsbasic_brc:00 00 00 00 07 96 2C 00 |......,.|+
    +2012-07-30 18:15:28.658725 : nsbasic_brc:25 06 4D 52 20 20 20 20 |%.MR....|+
    +2012-07-30 18:15:28.658734 : nsbasic_brc:03 C2 1A 5F 04 C3 02 10 |..._....|+
    +2012-07-30 18:15:28.658742 : nsbasic_brc:43 06 43 4C 4F 53 45 44 |C.CLOSED|+
    +2012-07-30 18:15:28.658750 : nsbasic_brc:FF FF FF FF FF FF FF FF |........|+
    +2012-07-30 18:15:28.658758 : nsbasic_brc:FF FF 06 4C 50 49 4D 20 |...LPIM.|+
    +2012-07-30 18:15:28.658767 : nsbasic_brc:20 FF FF FF FF FF FF FF |........|+
    +2012-07-30 18:15:28.658775 : nsbasic_brc:FF FF FF FF FF 0A 4D 41 |......MA|+
    +2012-07-30 18:15:28.658783 : nsbasic_brc:52 47 41 42 20 20 20 20 |RGAB....|+
    +2012-07-30 18:15:28.658791 : nsbasic_brc:FF 3C 77 68 65 65 6C 20 |.<wheel.|+
    +2012-07-30 18:15:28.658799 : nsbasic_brc:73 68 6F 70 20 20 20 20 |shop....|+
    +2012-07-30 18:15:28.658807 : nsbasic_brc:20 20 20 20 20 20 20 20 |........|+
    +2012-07-30 18:15:28.658815 : nsbasic_brc:20 20 20 20 20 20 20 20 |........|+
    +2012-07-30 18:15:28.658824 : nsbasic_brc:20 20 20 20 20 20 20 20 |........|+
    +2012-07-30 18:15:28.658832 : nsbasic_brc:20 20 20 20 20 20 20 20 |........|+
    +2012-07-30 18:15:28.658840 : nsbasic_brc:20 20 20 20 20 20 20 20 |........|+
    +2012-07-30 18:15:28.658848 : nsbasic_brc:20 20 20 20 20 20 02 C1 |........|+
    +2012-07-30 18:15:28.658856 : nsbasic_brc:05 07 78 66 05 03 10 09 |..xf....|+
    +2012-07-30 18:15:28.658864 : nsbasic_brc:38 02 C1 02 FF 03 C2 08 |8.......|+
    +2012-07-30 18:15:28.658872 : nsbasic_brc:42 FF 01 58 04 01 00 00 |B..X....|+
    +2012-07-30 18:15:28.658880 : nsbasic_brc:00 14 00 01 02 00 00 00 |........|+
    +2012-07-30 18:15:28.658888 : nsbasic_brc:7B 05 00 00 00 00 02 00 |{.......|+
    +2012-07-30 18:15:28.658897 : nsbasic_brc:00 00 03 00 20 00 00 00 |........|+
    +2012-07-30 18:15:28.658905 : nsbasic_brc:00 00 00 00 00 00 00 00 |........|+
    +2012-07-30 18:15:28.658912 : nsbasic_brc:00 00 00 00 00 00 00 00 |........|+
    +2012-07-30 18:15:28.658921 : nsbasic_brc:00 00 00 00 00 16 00 00 |........|+
    +2012-07-30 18:15:28.658929 : nsbasic_brc:01 00 00 00 36 01 00 00 |....6...|+
    +2012-07-30 18:15:28.658937 : nsbasic_brc:00 00 00 00 00 00 00 00 |........|+
    +2012-07-30 18:15:28.658945 : nsbasic_brc:00 00 00 00 E0 53 D1 22 |.....S."|+
    +2012-07-30 18:15:28.658953 : nsbasic_brc:00 00 00 00 00 00 00 00 |........|+
    +2012-07-30 18:15:28.658961 : nsbasic_brc:00 00 00 00 00 00 00 00 |........|+
    +2012-07-30 18:15:28.658969 : nsbasic_brc:00 00 00 00 00 00 00 00 |........|+
    +2012-07-30 18:15:28.658977 : nsbasic_brc:00 00 00 00 00 00 00 00 |........|+
    +2012-07-30 18:15:28.658987 : nsbasic_brc:00 00 00 00 00 00 00 00 |........|+
    +2012-07-30 18:15:28.658996 : nsbasic_brc:00 00 00 00 00 00 00 00 |........|+
    +2012-07-30 18:15:28.659004 : nsbasic_brc:00 00 00 00 00 00 00 00 |........|+
    +2012-07-30 18:15:28.659012 : nsbasic_brc:00 00 00 00 17 4F 52 41 |.....ORA|+
    +2012-07-30 18:15:28.659021 : nsbasic_brc:2D 30 31 34 30 33 3A 20 |-01403:.|+
    +2012-07-30 18:15:28.659029 : nsbasic_brc:64 61 74 61 20 73 61 6B |data.sak|+
    +2012-07-30 18:15:28.659038 : nsbasic_brc:6E 61 73 0A |nas. |+
    +2012-07-30 18:15:28.659046 : nsbasic_brc:exit: oln=0, dln=362, tot=372, rc=0+
    +2012-07-30 18:15:28.659054 : nioqrc:exit+
    +2012-07-30 18:16:09.583993 : nioqsn:entry+
    +2012-07-30 18:16:09.584062 : nioqsn:exit+
    +2012-07-30 18:16:09.584086 : nioqrc:entry+
    +2012-07-30 18:16:09.584097 : nsbasic_bsd:entry+
    +2012-07-30 18:16:09.584107 : nsbasic_bsd:tot=0, plen=318.+
    +2012-07-30 18:16:09.584116 : nttfpwr:entry+
    +2012-07-30 18:16:09.584146 : ntt2err:entry+
    +2012-07-30 18:16:09.584162 : ntt2err:soc 564 error - operation=6, ntresnt[0]=530, ntresnt[1]=54, ntresnt[2]=0+
    +2012-07-30 18:16:09.584171 : ntt2err:exit+
    +2012-07-30 18:16:09.584178 : nttfpwr:exit+
    +2012-07-30 18:16:09.584192 : nserror:entry+
    +2012-07-30 18:16:09.584203 : nserror:nsres: id=0, op=67, ns=12571, ns2=12560; nt[0]=530, nt[1]=54, nt[2]=0; ora[0]=0, ora[1]=0, ora[2]=0+
    +2012-07-30 18:16:09.584213 : nsbasic_bsd:exit (-1)+
    +2012-07-30 18:16:09.584224 : nioqrc:send failed: bl = 1, nicbl = 1+
    +2012-07-30 18:16:09.584234 : nioqper: error from nioqrc+
    +2012-07-30 18:16:09.584242 : nioqper: ns main err code: 12571+
    +2012-07-30 18:16:09.584250 : nioqper: ns (2) err code: 12560+
    +2012-07-30 18:16:09.584258 : nioqper: nt main err code: 530+
    +2012-07-30 18:16:09.584266 : nioqper: nt (2) err code: 54+
    +2012-07-30 18:16:09.584275 : nioqper: nt OS err code: 0+
    +2012-07-30 18:16:09.584285 : nioqer:entry+
    +2012-07-30 18:16:09.584293 : nioqer: incoming err = 12150+
    +2012-07-30 18:16:09.584301 : niomapnserror:entry+
    +2012-07-30 18:16:09.584311 : niqme:entry+
    +2012-07-30 18:16:09.584321 : niqme:reporting NS-12571 error as ORA-12571+
    +2012-07-30 18:16:09.584330 : niqme:exit+
    +2012-07-30 18:16:09.584337 : niomapnserror:exit+
    +2012-07-30 18:16:09.584344 : nioqce:entry+
    +2012-07-30 18:16:09.584352 : nioqce:exit+
    +2012-07-30 18:16:09.584359 : nioqer: returning err = 12571+
    +2012-07-30 18:16:09.584366 : nioqer:exit+
    +2012-07-30 18:16:09.584374 : nioqrc: returning error: 12571+
    +2012-07-30 18:16:09.584381 : nioqrc:exit+
    +2012-07-30 18:16:09.584396 : nioqrs:entry+
    +2012-07-30 18:16:09.584412 : nioqrs: state = interrupted (1)+
    +2012-07-30 18:16:09.584425 : nscontrol:entry+
    +2012-07-30 18:16:09.584435 : nscontrol:cmd=45, lcl=0x0+
    +2012-07-30 18:16:09.584442 : nscontrol:normal exit+
    +2012-07-30 18:16:09.584450 : nscontrol:entry+
    +2012-07-30 18:16:09.584457 : nscontrol:cmd=1, lcl=0x0+
    +2012-07-30 18:16:09.584464 : nscontrol:normal exit+
    +2012-07-30 18:16:09.584476 : nioqsm:entry+
    +2012-07-30 18:16:09.584485 : nioqsm: Sending break packet (1)...+
    +2012-07-30 18:16:09.584493 : nscontrol:entry+
    +2012-07-30 18:16:09.584500 : nscontrol:cmd=45, lcl=0x0+
    +2012-07-30 18:16:09.584508 : nscontrol:normal exit+
    +2012-07-30 18:16:09.584516 : nsdo:entry+
    +2012-07-30 18:16:09.584525 : nsdo:cid=0, opcode=67, *bl=1, *what=17, uflgs=0x100, cflgs=0x3+
    +2012-07-30 18:16:09.584534 : nsdo:rank=64, nsctxrnk=0+
    +2012-07-30 18:16:09.584543 : nsdo:nsctx: state=8, flg=0x400d, mvd=0+
    +2012-07-30 18:16:09.584552 : nsdo:gtn=32, gtc=32, ptn=10, ptc=8191+
    +2012-07-30 18:16:09.584560 : nsdofls:entry+
    +2012-07-30 18:16:09.584569 : nsdofls:DATA flags: 0x0+
    +2012-07-30 18:16:09.584577 : nsdofls:normal exit+
    +2012-07-30 18:16:09.584587 : nsdo:sending NSPTMK packet+
    +2012-07-30 18:16:09.584596 : nspsend:entry+
    +2012-07-30 18:16:09.584605 : nspsend:plen=11, type=12+
    +2012-07-30 18:16:09.584614 : nttwr:entry+
    +2012-07-30 18:16:09.584628 : ntt2err:entry+
    +2012-07-30 18:16:09.584638 : ntt2err:soc 564 error - operation=6, ntresnt[0]=530, ntresnt[1]=54, ntresnt[2]=0+
    +2012-07-30 18:16:09.584646 : ntt2err:exit+
    +2012-07-30 18:16:09.584657 : nttwr:exit+
    +2012-07-30 18:16:09.584668 : nspsend:0 bytes to transport+
    +2012-07-30 18:16:09.584677 : nspsend:transport write error+
    +2012-07-30 18:16:09.584684 : nspsend:error exit+
    +2012-07-30 18:16:09.584692 : nsdo:error sending NSPTMK packet+
    +2012-07-30 18:16:09.584700 : nserror:entry+
    +2012-07-30 18:16:09.584709 : nserror:nsres: id=0, op=67, ns=12571, ns2=12560; nt[0]=530, nt[1]=54, nt[2]=0; ora[0]=0, ora[1]=0, ora[2]=0+
    +2012-07-30 18:16:09.584719 : nsdo:nsctxrnk=0+
    +2012-07-30 18:16:09.584726 : nsdo:error exit+
    +2012-07-30 18:16:09.584737 : nioqsm:send-break: failed to send break...+
    +2012-07-30 18:16:09.584746 : nioqper: error from send-marker+
    +2012-07-30 18:16:09.584753 : nioqper: ns main err code: 12571+
    +2012-07-30 18:16:09.584761 : nioqper: ns (2) err code: 12560+
    +2012-07-30 18:16:09.584769 : nioqper: nt main err code: 530+
    +2012-07-30 18:16:09.584776 : nioqper: nt (2) err code: 54+
    +2012-07-30 18:16:09.584784 : nioqper: nt OS err code: 0+
    +2012-07-30 18:16:09.584792 : nioqsm:exit+
    +2012-07-30 18:16:09.584799 : nioqer:entry+
    +2012-07-30 18:16:09.584808 : nioqer: incoming err = 12152+
    +2012-07-30 18:16:09.584817 : niomapnserror:entry+
    +2012-07-30 18:16:09.584824 : niqme:entry+
    +2012-07-30 18:16:09.584833 : niqme:reporting NS-12571 error as ORA-12571+
    +2012-07-30 18:16:09.584840 : niqme:exit+
    +2012-07-30 18:16:09.584847 : niomapnserror:exit+
    +2012-07-30 18:16:09.584854 : nioqce:entry+
    +2012-07-30 18:16:09.584861 : nioqce:exit+
    +2012-07-30 18:16:09.584868 : nioqer: returning err = 12571+
    +2012-07-30 18:16:09.584876 : nioqer:exit+
    +2012-07-30 18:16:09.584884 : nioqrs:nioqrs: Couldn't send break. returning 12571+
    +2012-07-30 18:16:09.584894 : nioqrs:exit+
    +2012-07-30 18:16:09.584912 : nioqds:entry+
    +2012-07-30 18:16:09.584921 : nioqds: disconnecting...+
    +2012-07-30 18:16:09.584933 : nsclose:entry+
    +2012-07-30 18:16:09.584945 : nsvntx_dei:entry+
    +2012-07-30 18:16:09.584953 : nsvntx_dei:exit+
    +2012-07-30 18:16:09.584964 : nstimarmed:entry+
    +2012-07-30 18:16:09.584973 : nstimarmed:no timer allocated+
    +2012-07-30 18:16:09.584980 : nstimarmed:normal exit+
    +2012-07-30 18:16:09.584994 : nttctl:entry+
    +2012-07-30 18:16:09.585009 : nttctl:entry+
    +2012-07-30 18:16:09.585021 : nsfull_cls:entry+
    +2012-07-30 18:16:09.585031 : nsfull_cls:cid=0, opcode=65, *bl=0, *what=0, uflgs=0x0, cflgs=0x0+
    +2012-07-30 18:16:09.585040 : nsfull_cls:nsctx: state=8, flg=0x4009, mvd=0+
    +2012-07-30 18:16:09.585048 : nsdo:entry+
    +2012-07-30 18:16:09.585056 : nsdo:cid=0, opcode=67, *bl=0, *what=1, uflgs=0x0, cflgs=0x1+
    +2012-07-30 18:16:09.585065 : nsdo:nsctx: state=8, flg=0x4009, mvd=0+
    +2012-07-30 18:16:09.585074 : nsdo:gtn=32, gtc=32, ptn=10, ptc=8191+
    +2012-07-30 18:16:09.585082 : nsdo:normal exit+
    +2012-07-30 18:16:09.585089 : nsdofls:entry+
    +2012-07-30 18:16:09.585097 : nsdofls:DATA flags: 0x40+
    +2012-07-30 18:16:09.585105 : nsdofls:sending NSPTDA packet+
    +2012-07-30 18:16:09.585113 : nspsend:entry+
    +2012-07-30 18:16:09.585120 : nspsend:plen=10, type=6+
    +2012-07-30 18:16:09.585128 : nttwr:entry+
    +2012-07-30 18:16:09.585140 : ntt2err:entry+
    +2012-07-30 18:16:09.585150 : ntt2err:soc 564 error - operation=6, ntresnt[0]=530, ntresnt[1]=54, ntresnt[2]=0+
    +2012-07-30 18:16:09.585158 : ntt2err:exit+
    +2012-07-30 18:16:09.585165 : nttwr:exit+
    +2012-07-30 18:16:09.585173 : nspsend:0 bytes to transport+
    +2012-07-30 18:16:09.585181 : nspsend:transport write error+
    +2012-07-30 18:16:09.585188 : nspsend:error exit+
    +2012-07-30 18:16:09.585196 : nserror:entry+
    +2012-07-30 18:16:09.585205 : nserror:nsres: id=0, op=67, ns=12571, ns2=12560; nt[0]=530, nt[1]=54, nt[2]=0; ora[0]=0, ora[1]=0, ora[2]=0+
    +2012-07-30 18:16:09.585215 : nsdofls:exit (-1)+
    +2012-07-30 18:16:09.585223 : nsbfr:entry+
    +2012-07-30 18:16:09.585230 : nsbaddfl:entry+
    +2012-07-30 18:16:09.585239 : nsbaddfl:normal exit+
    +2012-07-30 18:16:09.585247 : nsbfr:normal exit+
    +2012-07-30 18:16:09.585254 : nsbfr:entry+
    +2012-07-30 18:16:09.585261 : nsbaddfl:entry+
    +2012-07-30 18:16:09.585268 : nsbaddfl:normal exit+
    +2012-07-30 18:16:09.585276 : nsbfr:normal exit+
    +2012-07-30 18:16:09.585283 : nsfull_cls:normal exit+
    +2012-07-30 18:16:09.585291 : nsiocancel:entry+
    +2012-07-30 18:16:09.585303 : nsiofrrg:entry+
    +2012-07-30 18:16:09.585313 : nsiofrrg:cur = 5e5f3f8+
    +2012-07-30 18:16:09.585321 : nsbfr:entry+
    +2012-07-30 18:16:09.585328 : nsbaddfl:entry+
    +2012-07-30 18:16:09.585335 : nsbaddfl:normal exit+
    +2012-07-30 18:16:09.585342 : nsbfr:normal exit+
    +2012-07-30 18:16:09.585350 : nsiofrrg:exit+
    +2012-07-30 18:16:09.585358 : nsiocancel:exit+
    +2012-07-30 18:16:09.585365 : nsclose:closing transport+
    +2012-07-30 18:16:09.585375 : nttdisc:entry+
    +2012-07-30 18:16:09.585438 : nttdisc:Closed socket 564+
    +2012-07-30 18:16:09.585453 : nttdisc:exit+
    +2012-07-30 18:16:09.585463 : nsclose:global context check-out (from slot 0) complete+
    +2012-07-30 18:16:09.585471 : nsnadisc:entry+
    +2012-07-30 18:16:09.585484 : nadisc:entry+
    +2012-07-30 18:16:09.585496 : nacomtm:entry+
    +2012-07-30 18:16:09.585506 : nacompd:entry+
    +2012-07-30 18:16:09.585513 : nacompd:exit+
    +2012-07-30 18:16:09.585521 : nacompd:entry+
    +2012-07-30 18:16:09.585527 : nacompd:exit+
    +2012-07-30 18:16:09.585535 : nacomtm:exit+
    +2012-07-30 18:16:09.585545 : nas_dis:entry+
    +2012-07-30 18:16:09.585553 : nas_dis:exit+
    +2012-07-30 18:16:09.585562 : nau_dis:entry+
    +2012-07-30 18:16:09.585577 : nau_dis:exit+
    +2012-07-30 18:16:09.585587 : naeetrm:entry+
    +2012-07-30 18:16:09.585596 : naeetrm:exit+
    +2012-07-30 18:16:09.585604 : naectrm:entry+
    +2012-07-30 18:16:09.585613 : naectrm:exit+
    +2012-07-30 18:16:09.585623 : nagbltrm:entry+
    +2012-07-30 18:16:09.585632 : nau_gtm:entry+
    +2012-07-30 18:16:09.585640 : nau_gtm:exit+
    +2012-07-30 18:16:09.585648 : nagbltrm:exit+
    +2012-07-30 18:16:09.585657 : nadisc:exit+
    +2012-07-30 18:16:09.585665 : nsnadisc:normal exit+
    +2012-07-30 18:16:09.585675 : nsvntx_dei:entry+
    +2012-07-30 18:16:09.585682 : nsvntx_dei:exit+
    +2012-07-30 18:16:09.585694 : nsopenfree_nsntx:nlhthdel from mplx_ht_nsgbu, ctx=5e5e0e0 nsntx=5e5e6c0+
    +2012-07-30 18:16:09.585703 : nsiocancel:entry+
    +2012-07-30 18:16:09.585710 : nsiofrrg:entry+
    +2012-07-30 18:16:09.585718 : nsiofrrg:exit+
    +2012-07-30 18:16:09.585725 : nsiocancel:exit+
    +2012-07-30 18:16:09.585732 : nsmfr:entry+
    +2012-07-30 18:16:09.585741 : nsmfr:2944 bytes at 0x5e5e6c0+
    +2012-07-30 18:16:09.585748 : nsmfr:normal exit+
    +2012-07-30 18:16:09.585755 : nsmfr:entry+
    +2012-07-30 18:16:09.585763 : nsmfr:240 bytes at 0x5f2a610+
    +2012-07-30 18:16:09.585771 : nsmfr:normal exit+
    +2012-07-30 18:16:09.585778 : nsmfr:entry+
    +2012-07-30 18:16:09.585785 : nsmfr:280 bytes at 0x63c010+
    +2012-07-30 18:16:09.585792 : nsmfr:normal exit+
    +2012-07-30 18:16:09.585803 : nladtrm:entry+
    +2012-07-30 18:16:09.585820 : nladtrm:exit+
    +2012-07-30 18:16:09.585828 : nsmfr:entry+
    +2012-07-30 18:16:09.585836 : nsmfr:1496 bytes at 0x5e5e0e0+
    +2012-07-30 18:16:09.585844 : nsmfr:normal exit+
    +2012-07-30 18:16:09.585851 : nsclose:normal exit+
    +2012-07-30 18:16:09.585859 : nioqds:exit+
    +2012-07-30 18:16:09.585868 : nsbfree:entry+
    +2012-07-30 18:16:09.585876 : nsbgetfl:entry+
    +2012-07-30 18:16:09.585884 : nsbgetfl:normal exit+
    +2012-07-30 18:16:09.585894 : nsbaddfl:entry+
    +2012-07-30 18:16:09.585901 : nsbaddfl:normal exit+
    +2012-07-30 18:16:09.585909 : nsbfree:normal exit+
    +2012-07-30 18:16:09.585916 : nsbfree:entry+
    +2012-07-30 18:16:09.585923 : nsbgetfl:entry+
    +2012-07-30 18:16:09.585930 : nsbgetfl:normal exit+
    +2012-07-30 18:16:09.585938 : nsbaddfl:entry+
    +2012-07-30 18:16:09.585945 : nsbaddfl:normal exit+
    +2012-07-30 18:16:09.585952 : nsbfree:normal exit+
    +2012-07-30 18:16:09.585961 : nigtrm:Count in the NI global area is now 2+
    +2012-07-30 18:16:09.585974 : nsbfrfl:entry+
    +2012-07-30 18:16:09.585982 : nsbrfr:entry+
    +2012-07-30 18:16:09.585991 : nsbrfr:nsbfs at 0x5f26470, data at 0x5f26520.+
    +2012-07-30 18:16:09.585999 : nsbrfr:normal exit+
    +2012-07-30 18:16:09.586006 : nsbrfr:entry+
    +2012-07-30 18:16:09.586015 : nsbrfr:nsbfs at 0x5f28540, data at 0x5f285f0.+
    +2012-07-30 18:16:09.586025 : nsbrfr:normal exit+
    +2012-07-30 18:16:09.586033 : nsbrfr:entry+
    +2012-07-30 18:16:09.586040 : nsbrfr:nsbfs at 0x5e5f480, data at 0x5e5f530.+
    +2012-07-30 18:16:09.586048 : nsbrfr:normal exit+
    +2012-07-30 18:16:09.586055 : nsbrfr:entry+
    +2012-07-30 18:16:09.586063 : nsbrfr:nsbfs at 0x5f2a610, data at 0x5f2a9f0.+
    +2012-07-30 18:16:09.586073 : nsbrfr:normal exit+
    +2012-07-30 18:16:09.586082 : nsbrfr:entry+
    +2012-07-30 18:16:09.586090 : nsbrfr:nsbfs at 0x62c7d0, data at 0x5f2ca10.+
    +2012-07-30 18:16:09.586098 : nsbrfr:normal exit+
    +2012-07-30 18:16:09.586106 : nsbfrfl:normal exit+
    +2012-07-30 18:16:09.586153 : nigtrm:Count in the NL global area is now 3+

  • ORA-03113 error when using Oracle 9i with Mapx 5.0

    Hello,
    I am using Personal Oracle 9i Release 2 with Mapx5.0 on Delphi.
    Accessing the layers using tab files also as server layers..,
    and commonly using the method of Mapx Layer.SearchAtPoint
    Search is done on region, line as well as on point objects...,
    at some point of time it flashes me the error
    ORA-03113 end-of-file on communication channel
    I am not exactly able to figure out when it gives..,
    but i m getting it after some clicks on the layers
    The same executable is working fine with Oracle 8.1.7
    As anybody faced such a problem and knows the possible cause
    Thanks,
    Binoy

    There is some java bug that is causing some problems if you are using 9.2.0.3. Here is some information:
    Workaround for bug 2755842:
    Event 10499 can be set (any non-zero level) to revert to the old behaviour.
    ==================================================
    Setting the EVENT 10499
    =======================
    Check if the database server is using a server parameter (spfile) a parameter (init.ora) file.
    From sqlplus, connect as sysdba and execute the command:
    show parameters spfile
    If the value is NULL or empty, then spfile is NOT enabled and init.ora is used.
    1) If SPFILE is used:
    SQL> show parameters spfile
    NAME TYPE VALUE
    spfile string
    %ORACLE_HOME%\DATABASE\SPFILE%ORACLE_SID%.ORA
    a) Using sqlplus logon as sysdba
    b) Execute: alter system set event="10499 trace name context forever,level 4" scope=spfile
    sid='*';
    c) shutdown
    d) startup the database
    2) If INIT.ORA is used:
    a) In the init<SID>.ora file, add the parameter event="10499 trace name context forever,level 4"
    b) Stop and start the database
    Hope this is it.
    Dan

  • Remote Connection Timeouts - ORA-03113 Errors

    I have two Sun Solaris servers running Oracle 10.1.0.4. One is our production server, the other is our test server. Both servers are using the same parameters in the SQLNET.ORA file located on each server. All Oracle Net files are located under /var/opt/oracle. The TNS_ADMIN environmental variable is set to /var/opt/oracle on both servers.
    When I connect to the production server via TOAD, OEM, or SQL*Plus from my desktop, I can remain connected as long as I like. If after two hours, I want to run another SQL, I type it in and it runs.
    When I connect to the test server via TOAD, OAM, or SQL*Plus from my desktop, I can remain connected for only 30 mins of inactivity. After which, if I issue a new SQL statement, I receive an ORA-03113 end-of-file communication channel error.
    I believe I've checked everything on both servers and they appear identical. Both of these server sit behind a firewall. So my feeling is that only the firewall could be causing the idle timeout connections to be dropped on the test server.
    Anyone have any ideas on this??
    P.S. - I realize that killing idle connections is actually a good thing, but I'm trying to verify the reason for the difference and not whether this is or is not a good networking practice.

    user583592 wrote:
    I have two Sun Solaris servers running Oracle 10.1.0.4. One is our production server, the other is our test server. Both servers are using the same parameters in the SQLNET.ORA file located on each server. All Oracle Net files are located under /var/opt/oracle. The TNS_ADMIN environmental variable is set to /var/opt/oracle on both servers.
    When I connect to the production server via TOAD, OEM, or SQL*Plus from my desktop, I can remain connected as long as I like. If after two hours, I want to run another SQL, I type it in and it runs.
    When I connect to the test server via TOAD, OAM, or SQL*Plus from my desktop, I can remain connected for only 30 mins of inactivity. After which, if I issue a new SQL statement, I receive an ORA-03113 end-of-file communication channel error.
    I believe I've checked everything on both servers and they appear identical. Both of these server sit behind a firewall. So my feeling is that only the firewall could be causing the idle timeout connections to be dropped on the test server.
    Anyone have any ideas on this??
    P.S. - I realize that killing idle connections is actually a good thing, but I'm trying to verify the reason for the difference and not whether this is or is not a good networking practice.The firewall could very well be the culprit. I had that problem at a previous employer. Why not check with your network guys and find out?

  • ORA-03113 error in ifsconfig 9.0.1

    Hi,
    I'm new to Oracle, and I'd like to see what IFS can do. Unfortunatelly, I get an error message when lauching ifsconfig.
    First I "complete 9Ifs configuration" on the first screen. Then I enter my TNS service name and th SYS password.
    When clicking Next, the oracle connection test begins, until it gets to the "Verifying Oracle JServ" phase (the fifth one). It then fails and I got the following error message :
    "Oracle test failed.
    The following error occured: oracle.ifs.utils.action.ActionFailedExecption:errir executing loadjava process. The output given was:
    Error while creating class oracle/ifs/installer/Testjave
    ORA-03113: end-of-file on communication channel
    The following operations failed class oracle/ifs/installer/Testjava:creation
    exiting:failures occured during processing"
    Can anyone help me ?
    Thanks.

    This error means that the JServer in Oracle database is either not configured or it is misconfigured.
    Please reconfigure your JServer if you have not already done so.
    Also note that it is JServer and not JServ. They are two totally different things.

  • InterMedia Text with USER_DATASTORE and ORA-03113

    Hi,
    I have problems using Oracle's InterMedia Text-index with a
    USER_DATASTORE. I'm using Oracle 8.1.7 on Windows NT 4.0.
    What I try to do is to create a context-index on multiple columns
    of multiple tables. I created a table containing the original
    tablenames and primary keys plus a char(1)-column to index, a
    user_datastore, a procedure in a user-schema, a
    wrapping-procedure in ctxsys' schema and finally the index. All
    works fine so far but I get an ORA-03113 "end-of-file on
    communication channel" error when querying the table with
    contains. The procedure itself works.
    Here's what I tried in detail:
    I created a table "alldocs" containing the tablename and
    primary-key-value of each line of each table plus a dummy-column
    for the index:
    create table alldocs(
    table varchar2(30) not null,
    id number not null,
    data char(1),
    primary key(tabelle, id)
    I filled this table:
    insert into alldocs (select 'MYDOCS', id, 'a' from mydocs);
    insert into alldocs (select 'OTHERDOCS', id, 'b' from otherdocs);
    The user's procedure - only dummy for testing - is:
    create procedure test.GetAllDocsData(row IN ROWID, data IN OUT
    NOCOPY CLOB) IS
         tabname varchar2(30);
         myid     number;
         tmpclob clob;
    begin
         dbms_lob.createtemporary(tmpclob, TRUE);
         dbms_lob.writeappend(tmpclob, 34, 'Ein Text mit ca. 20
    Zeichen Ldnge.');
         data := tmpclob;
    end;
    In ctxsys' schema I defined the following procedure and the
    datastore:
    create or replace procedure sysGetAllDocsData(rid in rowid, tlob
    in out clob) is
    begin
    test.GetAllDocsData(rid, tlob);
    end sysGetAllDocsData;
    grant execute on sysGetAllDocsData to test;
    call ctx_ddl.create_preference('MyUserDS', 'user_datastore');
    call ctx_ddl.set_attribute('MyUserDS', 'procedure',
    'sysGetAllDocsData');
    call ctx_ddl.set_attribute('MyUserDS', 'output_type', 'CLOB');
    Finally I defined the index:
    create index test.alldocs_ctx on test.alldocs(data)
         indextype is ctxsys.context
         parameters ('DATASTORE CTXSYS.MyUserDS FILTER
    CTXSYS.INSO_FILTER LEXER BASIC_LEXER');
    This all works without errors. But when querying like this:
    select * from test.alldocs where contains('data', 'Text')>0
    the answer is
    ORA-03113: end-of-file on communication channel
    I hope someone can help.
    Greetings
    Ralf

    Hi Ralf,
    please define first your own preferences like this:
    exec CTX_DDL.drop_preference('MY_LEXER');
    exec CTX_DDL.create_preference('MY_LEXER','BASIC_LEXER');
    exec CTX_DDL.set_attribute('MY_LEXER','ALTERNATE_SPELLING',
    'GERMAN');
    exec CTX_DDL.set_attribute('MY_LEXER','BASE_LETTER','YES');
    exec CTX_DDL.set_attribute('MY_LEXER','MIXED_CASE', 'NO');
    exec CTX_DDL.set_attribute('MY_LEXER','INDEX_THEMES','NO');
    exec CTX_DDL.set_attribute('MY_LEXER','INDEX_TEXT', 'YES');
    exec CTX_DDL.set_attribute('MY_LEXER','COMPOSITE', 'GERMAN');
    exec ctx_ddl.Drop_Preference ('MY_FILTER');
    exec ctx_ddl.Create_Preference ('MY_FILTER','NULL_FILTER');
    exec ctx_ddl.drop_section_group ('MY_SECTION');
    exec ctx_ddl.create_section_group
    ('MY_SECTION','NULL_SECTION_GROUP');
    and then create your index with this preferences. You only need
    an INSO filter if you want to index pdf,word,...
    create index test.alldocs_ctx on test.alldocs(data)
         indextype is ctxsys.context
         parameters ('DATASTORE CTXSYS.MyUserDS FILTER
    CTXSYS.INSO_FILTER LEXER BASIC_LEXER');create index test.alldocs_ctx on test.alldocs(data)
         indextype is ctxsys.context
         parameters ('
    DATASTORE CTXSYS.MyUserDS
    lexer MY_LEXER
    filter MY_FILTER
    section group MY_SECTION');
    Then see in the token table what tokens are in the index:
    select token_text from dr$alldocs_ctx$i;
    If you got also an ORA-3113 see in alert.log if there is a trace
    referenced with this error and have a look in this file to find a
    better error message.
    Good luck.
    Thomas

Maybe you are looking for