Koh-kghu sessi,pl/sql vc2

hi
i am trying the blow code ..and getting error ...
we have 10g databse
can anybody please explain ...what is this all about
SQL> ed
Wrote file afiedt.buf
  1  declare
  2  a varchar(4000);
  3  b long raw;
  4  cursor c1 is select databuf from long_raw_table;
  5  begin
  6  open c1;
  7  loop
  8  fetch c1 into b ;
  9  exit when c1%notfound;
10  a:=UTL_RAW.CAST_TO_VARCHAR2(b);
11  dbms_output.put_line(a);
12  end loop;
13* end;
SQL> /
PL/SQL procedure successfully completed.
SQL> set serveroutput on
SQL> /
declare
ERROR at line 1:
ORA-04030: out of process memory when trying to
allocate 16396 bytes (koh-kghu sessi,pl/sql vc2)

hemu wrote:
can anybody please explain ...what is this all aboutUsing DBMS_OUTPUT. It is not a write-to-screen routine. It is a database package that uses PGA memory. Writing to DBMS_OUTPUT means putting data into its buffer variable.
When the client call has completed, the client can then interrogate this buffer variable and display the contents.
Your code is "writing" chunks of data into this buffer variable - that consumes server memory. It also consumes the most expensive of server memory - private and non-shared process memory. How much data is your code "writing" via DBMS_OUTPUT into this PL/SQL buffer variable? 100MB? 500MB? 1GB? More?
Do you really think that this is a scalable and effective approach to get data from the database and passing that to a client - using expensive PGA memory as a buffer area?

Similar Messages

  • HOT Problem connecting with Exporting application!

    When I try to export my ApEx application I receive an error:
    ORA-04030: out of process memory when trying to allocate num 16396 bytes (koh-kghu sessi,pl/sql vc2)
    Error exporting flow 101. ORA-04030: out of process memory when trying to allocate num 16396 bytes (koh-kghu sessi,pl/sql vc2)
    Best Regards

    Hi,
    If you haven't already contacted your DBA about this, you really should.
    If you are the DBA, then you should be taking a look at your memory parameters to see if they're suitable for your situation. If you're unsure then either seek the assitance of another DBA or file a support request with Oracle.

  • Out of process memory when indexing

    i'm trying to build an contains index
    on a big table (3M records)
    and i get this error:
    ERROR at line 1:
    ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
    ORA-20000: interMedia Text error:
    DRG-50857: oracle error in drueixe
    ORA-04030: out of process memory when trying to allocate 22172 bytes (PLS
    non-lib hp,PH1DRV ENGINE SPACE)
    ORA-04030: out of process memory when trying to allocate 40972 bytes (koh-kghu
    sessi,pl/sql vc2)
    ORA-06512: at "CTXSYS.DRUE", line 126
    ORA-06512: at "CTXSYS.TEXTINDEXMETHODS", line 78
    ORA-06512: at line 1
    what parameters must i change on
    my init.ora, or should i add
    a memory parameter in my creating index script
    I NEED HELP PLEASE???

    on 8.1.7 oracle server with
    Patch_8.1.7.0.1.tar intermedia text
    on
    Sun SPARC Solaris (64-BIT)
    this happens when i try to set
    the max max_index_memory parameter
    (i've got to do this because if
    i don't the index cannot be created
    because of the extension of the temporary
    tablespace 8go is too small??)
    (ORA-01652: unable to extend temp segment by 13 in tablespace TEMP)
    i've already indexed this table but it was on
    a linux server with 8.1.6 version?
    I wonder if it's because of wrong memory
    configuration ??
    null

  • Getting the following error while running the apex 3.2 report

    Hello All,
    I am running apex 3.2 on oracle 10g.
    I am getting the following error ..
    ORA-04030: out of process memory when trying to allocate 16328 bytes (koh-kghu call ,pl/sql vc2)
    Pls let me know what's the cause of this error..
    thanks/kumar

    Server error, sounds like you have some server issues there, see this blog for possible answers..: http://www.dba-oracle.com/t_ora_04030_out_process_memory.htm
    Thank you,
    Tony Miller
    Webster, TX

  • Configuration error

    Hi all,
    I've a big problem with the repository configuration. I've passed o7_dictionary_accessibility, I've passed JDBC patch, now I've a new problem, during repository creation, at about 47%, I found this error on install.log: ORA-04031: unable to allocate 1036 byte of shared memory ("large pool","unknown object","koh-kghu sessi","pl/sql
    Thanks in advance,
    Alex

    Thanks for your reply.
    I've installed DB2 first and then created tables in it.
    Then I've installed only the Foundation services.
    These are re-installs, I've installed them only once and when I started the Configuration then it was giving the above error.

  • PGA Limits for 11.1.0.7 on AIX 6.1

    With an 11gR1 Database running under AIX I have the Impression, that requests for pga memory get an ORA-04030 too early. In the following statements there is a skript, that consumes more an more pga memory. It always stops when ~ 113MB of pga are consumed, but there should be posssible much more in my opinion. I shut down other database instances on the same server, I increased ulimit for rss and stack but the result is always the same. After the skript the 'session pga memory max' for my SID is 113MB.
    Why is more pga cosumption not possible?
    select name, to_number(value)/1024 KB
    from v$parameter
    where name like 'pga%'
    or name like 'memory%'
    or name like 'sga%';
    NAME KB
    sga_max_size 3,670,016
    sga_target 3,670,016
    memory_target 4,620,288
    memory_max_target 6,291,456
    pga_aggregate_target 950,272
    create table temp_pga as
    select * from v$pgastat;
    select n.name, sum(t.value)/1024 KB
    from v$sesstat t,
    v$statname n
    where n.statistic# = t.statistic#
    and n.name in ('session pga memory', 'session pga memory max', 'session uga memory', 'session uga memory max')
    group by n.name
    order by 1;
    NAME KB
    session pga memory 65,484
    session pga memory max 160,590
    session uga memory 25,379
    session uga memory max 68,069
    select
    s.sid,
    n.name,
    sum(t.value/1024) KB
    from
    v$statname n,
    v$session s,
    v$sesstat t
    where
    s.sid=t.sid
    and n.statistic# = t.statistic#
    and s.audsid = SYS_CONTEXT('userenv','sessionid')
    and n.name in ('session pga memory', 'session pga memory max', 'session uga memory', 'session uga memory max')
    group by
    s.sid, n.name
    order by 2;
    SID NAME KB
    94 session pga memory 1,832
    94 session pga memory max 2,536
    94 session uga memory 616
    94 session uga memory max 1,240
    declare
    type array is table of long index by binary_integer;
    l_data array;
    begin
    loop
    l_data(l_data.count+1) := rpad('*',32000,'*');
    end loop;
    end;
    FEHLER in Zeile 1:
    ORA-04030: Zu wenig Prozessspeicher für Versuch 32712 Bytes zuzuweisen (koh-kghu call ,pl/sql vc2)
    select n.name, sum(t.value)/1024 KB
    from v$sesstat t,
    v$statname n
    where n.statistic# = t.statistic#
    and n.name in ('session pga memory', 'session pga memory max', 'session uga memory', 'session uga memory max')
    group by n.name
    order by 1;
    NAME KB
    session pga memory 77,988
    session pga memory max 291,431
    session uga memory 32,088
    session uga memory max 77,023
    select
    s.sid,
    n.name,
    sum(t.value/1024) KB
    from
    v$statname n,
    v$session s,
    v$sesstat t
    where
    s.sid=t.sid
    and n.statistic# = t.statistic#
    and s.audsid = SYS_CONTEXT('userenv','sessionid')
    and n.name in ('session pga memory', 'session pga memory max', 'session uga memory', 'session uga memory max')
    group by
    s.sid, n.name
    order by 2;
    SID NAME KB
    94 session pga memory 1,384
    94 session pga memory max 113,832
    94 session uga memory 616
    94 session uga memory max 1,240
    select n.name, v.value before, n.value after, n.unit
    from
    v$pgastat n,
    temp_pga v
    where n.name = v.name
    order by n.unit, n.name;
    NAME BEFORE AFTER UNIT
    aggregate PGA auto target 819,505,152 715,511,808 bytes
    aggregate PGA target parameter 973,078,528 973,078,528 bytes
    bytes processed 21,978,394,624 22,010,895,360 bytes
    extra bytes read/written 1,066,005,504 1,066,005,504 bytes
    global memory bound 104,857,600 104,857,600 bytes
    maximum PGA allocated 454,460,416 454,460,416 bytes
    maximum PGA used for auto workareas 106,148,864 106,148,864 bytes
    maximum PGA used for manual workareas 0 0 bytes
    PGA memory freed back to OS 9,104,392,192 9,222,684,672 bytes
    total freeable PGA memory 48,103,424 52,101,120 bytes
    total PGA allocated 143,251,456 164,831,232 bytes
    total PGA inuse 64,303,104 77,556,736 bytes
    total PGA used for auto workareas 1,277,952 1,529,856 bytes
    total PGA used for manual workareas 0 0 bytes
    cache hit percentage 95 95 percent
    max processes count 82 82
    over allocation count 0 0
    process count 49 63
    recompute count (total) 5,239 5,240

    I found my problem. After changing the ulimit parameters for the oracle user I didn't restart the listener, only the database.
    As new client connections inherit their limits from the listener process the old values were still valid.

  • Installing 9iAS 1.0.2.2 (Portal) on 9i database

    Installing 9iAS 1.0.2.2 on 9i database and getting an
    error: "ORA-04031: unable to allocate 40972 bytes of shared
    memory ("large pool","unknown object","koh-kghu sessi","pl/sql
    Errors encountered in the Install process. Installation
    Aborted."
    Error occured on 49% of installation process of Portal
    configuration!!!!
    Anyone have any ideas?
    Thanks,
    Janez

    I had the same problem. Try this:
    Please see if the Windows NT 4.0 Option Pack is installed. You can normally see
    this in Control Panel, Add/Remove Programs.
    There are two solutions/workarounds:
    Solution One: Make a Registry Export
    1. Start REGEDIT. Navigate to the key HKEY_LOCAL_MACHINE\Software\
    Microsoft\Transaction Server\Setup(OCM)
    2. Choose Registry, Export Registry File. Select to export the current branch.
    3. Enter a filename, e.g. pre-ias.reg
    4. With 'Setup(OCM)' highlighted, press the Delete key. At the 'confirm key
    delete' prompt, answer Yes.
    5. Install the 9i Application Server.
    6. Re-establish the registry key by double clicking the filename you created.
    Solution Two: Uninstall the Option Pack
    This solution takes more time, but if you don't need the Option Pack you can
    remove it.
    Remove the NT Option Pack, install 9iAS, then you can install the Option Pack
    again.
    Explanation
    It appears that the Universal Installer hangs on a specific registry key that
    belongs to a component of the Option Pack.
    null

  • Understanding Memory Error

    DB version : 11.2
    Please help me to understand the Issue. Is database missing initialization parameter for max. allocate memory for Individual session ?
    Sample anonymous block ran on database:
    DECLARE
    l_strings DBMS_SQL.varchar2a;
    BEGIN
    FOR indx IN 1 .. 2 ** 31 - 1
    LOOP
    l_strings (indx) := RPAD ('abc', 32767, 'def');
    END LOOP;
    END;
    Expected Result : ORA-04030: out of process memory when trying to allocate 40932 bytes.
    Actual result : Hanged whole multi-user database server and caused to reboot the server.
    Thanks,
    --Anan                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

    11.2.what? I'm guessing 11.2.0.1 since my XE 11.2.0.2 handles it ok; .0.1 seems to be generally buggy.
    Edited by: BrendanP on 04-Jan-2013 14:01
    This is what I got, which indicated that the transaction failed but that the database did not go down:
    SPOOL Mem
    DECLARE
    l_strings DBMS_SQL.varchar2a;
    BEGIN
    FOR indx IN 1 .. 2 ** 31 - 1
    LOOP
    l_strings (indx) := RPAD ('abc', 32767, 'def');
    END LOOP;
    END;
    SELECT * FROM DUAL;
    SPOOL OFF
    DECLARE
    ERROR at line 1:
    ORA-04030: out of process memory when trying to allocate 40932 bytes (koh-kghu
    call ,pl/sql vc2)
    D
    XHowever, I was running another job at the same time, and this is what happened to that job:
    ERROR:
    ORA-03114: not connected to ORACLE
    BEGIN
    ERROR at line 1:
    ORA-03113: end-of-file on communication channel
    Elapsed: 00:10:53.05
    SQL> So, perhaps there is some confusion here, and the rogue transaction actually just uses all the available common memory, thus crashing other transactions, but not the database, and therefore it may not be a bug?
    Edited by: BrendanP on 04-Jan-2013 14:08
    Although I suppose it shouldn't have disconnected me, just dropped the transaction?

  • Installing 9iAS 1.0.2.2 on 9i database

    Installing 9iAS 1.0.2.2 on 9i database and getting an
    error: "ORA-04031: unable to allocate 40972 bytes of shared
    memory ("large pool","unknown object","koh-kghu sessi","pl/sql
    Errors encountered in the Install process. Installation Aborted."
    Error occured on 49% of installation process! Anyone have any
    ideas?
    Thanks,
    Janez

    Dear Janez,
    I understand the disappointment you are going through right now,
    because I my self went through the same feeling of frustration
    for a long time before I could successfully install Oracle9iAS
    1.0.2.2 in conjunction with an Oracle9i 9.0.1 database (on the
    Windows platform).
    First of all, for some reason (???) Oracle no longer allows any
    user to connect as SYS without the "as SYSDBA" clause. The OPCA
    wizard requests the SYS password and connect string for the
    database where it has to create the Portal Repository. I believe
    that the "opca.jar" has the login credentials hard-coded
    as "SYS" (without the "as SYSDBA" clause). To work around this,
    set the parameter O7_DICTIONARY_ACCESSIBILITY=TRUE in the
    database INIT.ORA file.
    The next problem I faced was with the Oracle JDBC driver that
    was supplied along with the Oracle9i database (release 9.0.1). I
    found that I was not being able to establish a simple connection
    using the classes111.zip or classes12.zip provided with the
    Oracle9i database itself. I then visited the Oracle Technology
    Network to search for Oracle9i JDBC drivers and downloaded the
    classes12.zip file listed for the Solaris platform (there were
    no JDBC drivers listed for the Oracle9i database on Windows
    NT/2000, only Oracle8i release 8.1.7).
    Then I ran the Portal Configuration Assistant batch file
    (launch.bat) after replacing the existing classes111.zip in the
    script's CLASSPATH with the classes12.zip I had just downloaded.
    Now I was getting the same error message that you have listed.
    I then attempted to create the Portal 3.0.9 repository manually
    instead of using the Configuration Wizard and was finally able
    to do so. I am outlining the steps below that you have to follow
    to do the same.
    1. With a text editor, open the following file:
    <ORACLE_HOME>\portal30\admin\plsql\cat\catload.sql
    2. Comment out the following line:
    REM spool ..\..\portal30\admin\plsql\cat\catldscr.sql
    3. Add a new line to indicate the correct location of
    catldscr.sql for a manual installation:
    spool catldscr.sql
    4. Save and close the file.
    5. With a text editor, open the following file:
    <ORACLE_HOME>\portal30\admin\plsql\owa\owaload.sql
    6. Comment out the following line:
    REM spool ..\..\portal30\admin\plsql\owa\wpildscr.sql
    7. Add a new line to indicate the correct location of
    wpildscr.sql for a manual installation:
    spool wpildscr.sql
    8. Save and close the file.
    9. Open a Command Prompt and set the ORACLE_HOME like:
    set ORACLE_HOME=E:\Oracle\iSuites
    10. From the %ORACLE_HOME%\portal30\admin\plsql
    directory, run the onetime script to install the PL/SQL Web
    Toolkit packages:
    onetime.cmd -p <SYS_Password> -l onetime.log -c <connect_string>
    11. Then run the Oracle9iAS Portal installation script from the
    Command Prompt (%ORACLE_HOME%\portal30\admin\plsql\winstall) to
    install the Oracle9iAS Portal product. This may take about 2 to
    3 hours.
    winstall.cmd -s portal30 -p portal30 -u users -t temp -d users -
    l users -o portal30_sso -i portal30_sso_ps -r 12345 -c
    <connect_string> > winstall.log
    12. At a DOS prompt, run the %ORACLE_HOME%\portal30
    \admin\plsql\ssodatan script. This script configures your login
    via the Single Sign-On (SSO) Server.
    ssodatan.cmd -w http://<Machine_Name>:<Port_No.>/pls/portal30/ -
    l http://<Machine_Name>:<Port_No.>/pls/portal30_sso/ -s
    portal30 &#8211;p portal30 -o portal30_sso -d portal30_sso -e
    portal30_sso_ps -c <connect_string>
    13. Stop and restart your HTTP server:
    net stop OracleiSuitesHTTPServer
    net start OracleiSuitesHTTPServer
    14. In the DOS prompt, run the following two commands to install
    the Portal Online Help.
    cd %ORACLE_HOME%\portal30\admin\plsql\wwu
    contimp.cmd -s portal30 -p portal30 -o portal_help -m reuse &#8211;u
    database_user -d ..\..\..\doc\site\hlp30ca.dmp -c
    <connect_string>
    Hope this helps.
    Sudip.

  • Memory Leak in Materialized View !!

    Hi,
    I'm facing memory leak problem while
    creating/refreshing materialized view
    with geometry object.
    Platform Win NT 4.0
    Oracle: 8.1.7.0.0
    Details:
    Step 1:
    I'm converting lat/long (Point data) to cartesian using user defined albers projection.
    Step 2:
    Following is the function.
    +++
    create or replace function get_projected_long_lat (Long in Number,Lat in Number)
    Return MDSYS.SDO_GEOMETRY
    DETERMINISTIC
    IS
    LatDec Number;
    LongDec Number;
    Geom MDSYS.SDO_GEOMETRY := mdsys.sdo_geometry(null,null,null,null,null);
    LatLongProj MDSYS.SDO_GEOMETRY;
    Diminfo_array MDSYS.SDO_DIM_ARRAY := MDSYS.SDO_DIM_ARRAY(
    MDSYS.SDO_DIM_ELEMENT('X', -79.5, -88, .00000005),
    MDSYS.SDO_DIM_ELEMENT('Y', 24, 31.5,.00000005));
    Begin
    LongDec := -(substr(long,1,2) + substr(long,3,2) * (1/60) +
    substr(long,5) * (1/60) * (1/60));
    LatDec := (substr(lat,1,2) + substr(lat,3,2) * (1/60) +
    substr(lat,5) * (1/60) * (1/60));
    Geom.sdo_gtype := 2001;
    Geom.sdo_srid := 8307;
    Geom.sdo_point := NULL;
    Geom.sdo_elem_info := mdsys.sdo_elem_info_array(1,1,1);
    Geom.sdo_ordinates := mdsys.sdo_ordinate_array(LongDec,LatDec);
    LatLongProj := SDO_CS.TRANSFORM(Geom, Diminfo_array, 600000);
    Return(LatLongProj);
    End get_projected_long_lat;
    +++
    Step 3:
    Creating materialized view
    ++
    CREATE MATERIALIZED VIEW GPTEST
    BUILD IMMEDIATE
    REFRESH COMPLETE START WITH SYSDATE NEXT SYSDATE + 1
    WITH ROWID
    AS
    (select rownum sdo_gid,
    get_projected_long_lat (a.longitude,a.latitude) geometry
    from br@dblnk a, gr@dblnk b
    ++++
    - Each time i refresh the view memory increase linearly, And I get the following error at some point after memory is full.
    ERROR at line 9:
    ORA-00600: internal error code, arguments: [kghfrf1], [0], [], [], [], [], [],
    ORA-04030: out of process memory when trying to allocate 25100 bytes (pga
    heap,control file cache)
    ORA-04030: out of process memory when trying to allocate 16396 bytes (koh-kghu
    sessi,kgmtgob)
    ORA-04030: out of process memory when trying to allocate 16396 bytes (koh-kghu
    sessi,kolcpcon kolcol)
    ORA-04030: out of process memory when trying to allocate 16396 bytes (koh-kghu
    sessi,kolcalm coll)
    ORA-04030: out of process memory when trying to allocate 16396 bytes (koh-kghu
    sessi,kolcalm coll)
    or
    *** 2001-07-25 15:07:42.087
    ksedmp: internal or fatal error
    ORA-04030: out of process memory when trying to allocate 33292 bytes (cursor work he,kllcqas:kllsltba)
    ORA-04030: out of process memory when trying to allocate 20012 bytes (callheap,KQL tmpbuf)
    ORA-04030: out of process memory when trying to allocate 16396 bytes (koh-kghu sessi,kolcalm coll)
    Can anyone help??
    Thanks
    null

    this may be related to pl/sql memory leak. The bug number is 1371158, and it is fixed in 9i.
    dan

  • Data pump issue for oracle 10G in window2003

    Hi Experts,
    I try to run data pump in oracle 10G in window 2003 server.
    I got a error as
    D:\>cd D:\oracle\product\10.2.0\SALE\BIN
    D:\oracle\product\10.2.0\SALE\BIN>expdp system/xxxxl@sale full=Y directory=du
    mpdir dumpfile=expdp_sale_20090302.dmp logfile=exp_sale_20090302.log
    Export: Release 10.2.0.4.0 - Production on Tuesday, 03 March, 2009 8:05:50
    Copyright (c) 2003, 2007, Oracle. All rights reserved.
    Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Produc
    tion
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    ORA-31626: job does not exist
    ORA-31650: timeout waiting for master process response
    However, I can run exp codes and works well.
    What is wrong for my data pump?
    Thanks
    JIM

    Hi Anand,
    I did not see any error log at that time. Actually, it did not work any more. I will test it again based on your emial after exp done.
    Based on new testing, I got below errors as
    ORA-39014: One or more workers have prematurely exited.
    ORA-39029: worker 1 with process name "DW01" prematurely terminated
    ORA-31671: Worker process DW01 had an unhandled exception.
    ORA-04030: out of process memory when trying to allocate 4108 bytes (PLS non-lib hp,pdzgM60_Make)
    ORA-06512: at "SYS.KUPC$QUEUE_INT", line 277
    ORA-06512: at "SYS.KUPW$WORKER", line 1366
    ORA-04030: out of process memory when trying to allocate 65036 bytes (callheap,KQL tmpbuf)
    ORA-06508: PL/SQL: could not find program unit being called: "SYS.KUPC$_WORKERERROR"
    ORA-06512: at "SYS.KUPW$WORKER", line 13360
    ORA-06512: at "SYS.KUPW$WORKER", line 15039
    ORA-06512: at "SYS.KUPW$WORKER", line 6372
    ORA-39125: Worker unexpected fatal error in KUPW$WORKER.DISPATCH_WORK_ITEMS while calling DBMS_METADATA.FETCH_XML_CLOB [PROCOBJ:"SALE"."SQLSCRIPT_2478179"]
    ORA-06512: at "SYS.KUPW$WORKER", line 7078
    ORA-04030: out of process memory when trying to allocate 4108 bytes (PLS non-lib hp,pdzgM60_Make)
    ORA-06500: PL/SQL: storage error
    ORA-04030: out of process memory when trying to allocate 16396 bytes (koh-kghu sessi,pmucpcon: tds)
    ORA-04030: out of process memory when trying to allocate 16396 bytes (koh-kghu sessi,pmucalm coll)
    Job "SYSTEM"."SYS_EXPORT_FULL_01" stopped due to fatal error at 14:41:36
    ORA-39014: One or more workers have prematurely exited.
    the trace file as
    *** 2009-03-03 14:20:41.500
    *** ACTION NAME:() 2009-03-03 14:20:41.328
    *** MODULE NAME:(oradim.exe) 2009-03-03 14:20:41.328
    *** SERVICE NAME:() 2009-03-03 14:20:41.328
    *** SESSION ID:(159.1) 2009-03-03 14:20:41.328
    Successfully allocated 7 recovery slaves
    Using 157 overflow buffers per recovery slave
    Thread 1 checkpoint: logseq 12911, block 2, scn 7355467494724
    cache-low rba: logseq 12911, block 251154
    on-disk rba: logseq 12912, block 221351, scn 7355467496281
    start recovery at logseq 12911, block 251154, scn 0
    ----- Redo read statistics for thread 1 -----
    Read rate (ASYNC): 185319Kb in 1.73s => 104.61 Mb/sec
    Total physical reads: 189333Kb
    Longest record: 5Kb, moves: 0/448987 (0%)
    Change moves: 1378/5737 (24%), moved: 0Mb
    Longest LWN: 1032Kb, moves: 45/269 (16%), moved: 41Mb
    Last redo scn: 0x06b0.9406fb58 (7355467496280)
    ----- Recovery Hash Table Statistics ---------
    Hash table buckets = 32768
    Longest hash chain = 3
    Average hash chain = 35384/25746 = 1.4
    Max compares per lookup = 3
    Avg compares per lookup = 847056/876618 = 1.0
    *** 2009-03-03 14:20:46.062
    KCRA: start recovery claims for 35384 data blocks
    *** 2009-03-03 14:21:02.171
    KCRA: blocks processed = 35384/35384, claimed = 35384, eliminated = 0
    *** 2009-03-03 14:21:02.531
    Recovery of Online Redo Log: Thread 1 Group 2 Seq 12911 Reading mem 0
    *** 2009-03-03 14:21:04.718
    Recovery of Online Redo Log: Thread 1 Group 1 Seq 12912 Reading mem 0
    *** 2009-03-03 14:21:16.296
    ----- Recovery Hash Table Statistics ---------
    Hash table buckets = 32768
    Longest hash chain = 3
    Average hash chain = 35384/25746 = 1.4
    Max compares per lookup = 3
    Avg compares per lookup = 849220/841000 = 1.0
    *** 2009-03-03 14:21:28.468
    tkcrrsarc: (WARN) Failed to find ARCH for message (message:0x1)
    tkcrrpa: (WARN) Failed initial attempt to send ARCH message (message:0x1)
    *** 2009-03-03 14:26:25.781
    kwqmnich: current time:: 14: 26: 25
    kwqmnich: instance no 0 check_only flag 1
    kwqmnich: initialized job cache structure
    ktsmgtur(): TUR was not tuned for 360 secs
    Windows Server 2003 Version V5.2 Service Pack 2
    CPU : 8 - type 586, 4 Physical Cores
    Process Affinity : 0x00000000
    Memory (Avail/Total): Ph:7447M/8185M, Ph+PgF:6833M/9984M, VA:385M/3071M
    Instance name: vmsdbsea
    Redo thread mounted by this instance: 0 <none>
    Oracle process number: 0
    Windows thread id: 2460, image: ORACLE.EXE (SHAD)
    Dynamic strand is set to TRUE
    Running with 2 shared and 18 private strand(s). Zero-copy redo is FALSE
    *** 2009-03-03 08:06:51.921
    *** ACTION NAME:() 2009-03-03 08:06:51.905
    *** MODULE NAME:(expdp.exe) 2009-03-03 08:06:51.905
    *** SERVICE NAME:(xxxxxxxxxx) 2009-03-03 08:06:51.905
    *** SESSION ID:(118.53238) 2009-03-03 08:06:51.905
    SHDW: Failure to establish initial communication with MCP
    SHDW: Deleting Data Pump job infrastructure
    is it a system memory issue for data pump? my exp works well
    How to fix this issue?
    JIM
    Edited by: user589812 on Mar 3, 2009 5:07 PM
    Edited by: user589812 on Mar 3, 2009 5:22 PM

  • My oc4j is error while I operate the mapviewer again, why?

    when I zoom out or zoom in the mapviewer client,the map appearance is very slowly, and some layers are not appeared,why.
    start the mapviewer for the first,the OC4J are all right,
    but after operating to the mapviewer again,
    the OC4J tips are following this:
    04/03/08 15:11:33 java.sql.SQLException: ORA-29902: error in executing ODCIIndex
    Start() routine
    ORA-13209: internal error while reading SDO_INDEX_METADATA table
    ORA-29400: data cartridge error
    ORA-04031: unable to allocate 4036 bytes of shared memory ("large pool","unknown
    object","cursor work he","qesaQBInit:buffer")
    ORA-06512: at "MDSYS.SDO_INDEX_METHOD_9I", line 232
    ORA-06512: at line 1
    04/03/08 15:11:33 Message:SQL Exception while querying theme: TRSPPLL
    Description: Nested exception is:
    java.sql.SQLException: ORA-29902: error in executing ODCIIndexStart() routine
    ORA-04031: unable to allocate 16396 bytes of shared memory ("large pool","unknow
    n object","koh-kghu sessi","kodpunp:PNTYadt")
    ORA-04031: unable to allocate 16396 bytes of shared memory ("large pool","unknow
    n object","koh-kghu sessi","pmucalm coll")
    thank you very much!

    You should check your shared_pool_size and java_pool_size
    parameters on the database.
    This error occurs when these are not set high enough.
    Increase their size and restart the db and try the
    mapviewer again.

  • ORA-29855 - Unable to allocate shared memory

    Hi,
    We are encountering troubles (unable to allocate shared memory) while indexes creation. We tried to increase the share_size_memory (actually 52 mb) but this had no effect on this error. The Oracle error code is ORA-29855.
    The database is version 8.1.7, hosted on a Linux machine (RedHat 7.2) with 512 mb of memory. The code used for the index creation works fine on other machines (code from 9iAS Wireless installation) running with Windows 2000 as operation system.
    Any help or comment will be appreciated.
    Thanks,
    Fabrice Clari.
    The error message is:
    java.sql.SQLException: ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
    ORA-13200: internal error [ROWID:AAAGDwAAFAAAAvjAAA] in spatial indexing.
    ORA-13206: internal error [] while creating the spatial index
    ORA-13011: value is out of range
    ORA-00600: internal error code, arguments: [kope2ucoll700], [], [], [], [], [], [], []
    ORA-04031: unable to allocate 16396 bytes of shared memory ("large pool","unknown object","koh-kghu sessi","kolcalm coll")
    ORA-06512: at "MDSYS.SDO_INDEX_METHOD", line 8
    ORA-06512: at line 1

    Which portion of shared memory did you increase? The error indicates you need to increase large_pool_size. It seems you may also have other problems since you have several errors, and this only relates to the ORA-04031 error.

  • Validate_layer_with_context error

    BEGIN sdo_geom.validate_layer_with_context('COPPER', 'GEOM', 'VAL_RESULTS', 100); END;
    ERROR at line 1:
    ORA-04030: out of process memory when trying to allocate 16408 bytes (koh-kghu sessi,mdvgrr elmbr)
    ORA-06512: at "MDSYS.SDO_3GL", line 439
    ORA-06512: at "MDSYS.SDO_GEOM", line 3848
    ORA-06512: at line 1
    Is this a known bug in Oracle 9.2.0.2? Will I need to got to 9.2.0.3 to get this to work?
    R Clement
    Alaska DNR

    Hi Richard,
    This is reported in bug 2698729, and I don't see any info about it being fixed as of today.
    Sorry,
    Dan

  • Error creating spatial indexes

    I'm using oracle 10g2.
    I retrieve the following error message during spatial index creation:
    ERROR at line 1:
    ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
    ORA-13249: internal error in Spatial index: [mdidxrbd]
    ORA-13249: Error in Spatial index: index build failed
    ORA-13236: internal error in R-tree processing: [failed to cluster in memory]
    ORA-13232: failed to allocate memory during R-tree creation
    ORA-13236: internal error in R-tree processing: [failed to allocate memory
    4387752 (mdrtsalloc)]
    ORA-04031: unable to allocate ORA-04031: unable to allocate 4387800 bytes of
    shared memory ("large pool","unknown object","koh-kghu sessi","kpmalloc")
    bytes of shared memory ("","","","")
    ORA-06512: at "MDSYS.SDO_INDEX_METHOD_10I", line 10
    I've already tried to increase memory, shared and large pool, actually I have the following settings:
    Shared pool 500
    Buffer cache 200
    Large pool 200
    Pool Java 20
    I've already installed data and created spatial indexes on other machine correctly with the same data with less memory use, and I can't find any difference.
    Could anybody help me?

    Andre,
    I didn't think the , and ; in the sdo_geom_metadata would be causing the problem because he indicated that he could build indexes on other data - I assume he uses the same diminfo values for these as well. But, one can never be too sure!
    But certainly, follow what the error messages indicate.
    The Oracle Error message manual says:
    "ORA-13232: failed to allocate memory during R-tree creation
    Cause: This feature assumes a minimum of 64K memory for bulk creation.
    Action: Create the index for a small subset of the data. Then, use transactional insert operations for the rest of the data."
    The spatial manual says:
    "Before you create a spatial index, be sure that the rollback segment size and the SORT_AREA_SIZE parameter value are adequate, as described in Section 4.1.1."
    One way to change the sort area size is to alter your existing session before
    executing the create index statement. So, from 4.1.1. this can be done via:
    ALTER SESSION SET SORT_AREA_SIZE = 20000000;
    Also, do what Andre suggests. On my laptop with 1G of memory as a matter of course I change the SGA from the default to being much larger.
    regards
    S

Maybe you are looking for