ORA-04031:unable to allocate 32 bytes of memory :on UPGRADE to 10.2.0.4

Hi upgraded from 10.2.0.1 to 10.2.0.4 and I consistently start getting this error
ORA-00604: error occurred at recursive SQL level 1
ORA-04031: unable to allocate 32 bytes of shared memory ("shared pool","select job, nvl2(l
ast_date, ...","sql area","tmp")
even instance crashed couple of times...
Thanx
Gagan

What is the complete message for ORA-04031 (I mean what is there in place of '...'):
ORA-04031: unable to allocate 32 bytes of shared memory ("shared pool","select job, nvl2(l
ast_date, ...","sql area","tmp")

Similar Messages

  • ORA-04031: unable to allocate 64 bytes of shared memory

    Hi All,
    We are performing System copy on a distributed environment with OS Windows 2003 and DB Oracle 10.2.0.4
    While importing the Database (ABAP) only ,we are facing error and 5 import steps are failing  in Import ABAP phase.
    Error is "ORA-00604: error occurred at recursive SQL level 1
    ORA-04031: unable to allocate 4120 bytes of shared memory ("shared pool","select user#,type# from user...","Typecheck","kgghteInit")
    (DB) INFO: disconnected from DB"
    There is already one Oracel Instance OracleXX1 is runing this is the second instance and the server has around 1.75 GB RAM...i
    Can you please suggest what could be the error.
    Regards
    Ajay

    Dears,
    Please try increase your database parameter shared_pool_size in pfile and then try to resume the activity.
    Regards,
    Shivam

  • ORA-04031: unable to allocate 4096 bytes if shared memory

    Hello Gurus,
    Did anyone got this type of error before:
    ERROR:
    ORA-20414: Materialized View refresh failed - ORA-12008: error in materialized view refresh path
    ORA-04031: unable to allocate 4096 bytes of shared memory ("shared pool","IDX_MIF_SITE","pacdHds_kkpaco","stP_kkpacd: kkpodPacdInit")
    Every sunday full refresh of the data warehouse is scheduled. This sunday it didn't complete and gave us the above error. This can be solved by increasing the shared pool memory size. But DBA doesnot want to increase it every sunday(This has been going on for 3 weeks now) and it's not feasible to increase like this everytime.
    We want to find the actual cause of it and fix?
    Does anyone know the solution or can throw some light on this issue?
    Thanks,
    Sanjay

    We want to find the actual cause of it and fix?The cause is simple - you have run out of memory assigned to the Shared Pool in the SGA.
    The root cause is more of an issue. The Shared Pool is mostly used for keeping the SQL statements and supporting information (such as cursor support). Each unique SQL statement requires it's own area in the shared pool, however identical statements can used the same (shared) area. Shared Pool is also used to store the 'current' data dictionary (table, view, etc.) information. And in some cases, it's also used for 'large' operations such as direct path insert block builds.
    Some of the possible reasons for running out of shared pool might include
    - it's simply undersized;
    - not enough SQL is actually shareable;
    - the large pool has not been allocated.
    That second one is frequent when the application builds up SQL statements by concatenating pieces, including literals (user input) and then executing the unique statement. This is a common technique by developers using .Net, Perl or having SQL Server background. (That mode of operation is very susceptible to SQL Injection.)
    You can get a lot more info from:
    - searching the forum;
    - looking in the docco (Concepts manual and Performance Tuning guide);
    - books, like Tom Kyte's "Expert One on One Oracle", "Effective Oracle By Design", and newer on apress.com

  • ORA-04031: unable to allocate 33568 bytes of shared memory  in Oracle 10g

    Hi,
    I am getting following message frequently while taking export in Oracle 10g database:-
    EXP-00008: ORACLE error 4031 encountered
    ORA-04031: unable to allocate 33568 bytes of shared memory ("shared pool","DBMS_REPCAT_UTL","PL/SQL MPCODE","BAMIMA: Bam Buffer")
    ORA-06508: PL/SQL: could not find program unit being called: "SYS.DBMS_REPCAT_UTL"
    ORA-06512: at "SYS.DBMS_REPCAT_EXP", line 87
    ORA-06512: at line 1
    EXP-00083: The previous problem occurred when calling SYS.DBMS_REPCAT_EXP.schema_info_exp
    EXP-00008: ORACLE error 4031 encountered
    ORA-04031: unable to allocate 16416 bytes of shared memory ("shared pool","SELECT SYNNAM, SYNNAM, SYNTA...","kgghtInit","kgghtInit")
    EXP-00000: Export terminated unsuccessfully
    Whats could be the reason?

    There could be a few reasons causing the problem. From literal message it would look like your shared pool size is small and you need to increase. But the root cause of the problem is a little more complicated than that. I suggest you read metalink doc
    Diagnosing and Resolving Error ORA-04031
    Doc ID: Note:146599.1

  • ORACLE error ORA-04031: unable to allocate 16 bytes of memory

    Error
    UDI-04031: operation generated ORACLE error 4031
    ORA-04031: unable to allocate 16 bytes of shared memory ("shared pool","SELECT j
    generated during import operation, using documentation about migration from 10g XE to 11g XE.

    Hello,
    you could try to override the automatic memory management and setup your SGA to be larger by setting SGA_TARGET. If that doesn't help yet, you could even try to configure the memory size for the components in SGA manually, but I guess this won't be necessary.
    After your import is done, I'd recommend to use automatic memory management again.
    See the XE 2 Day DBA for details, especially the section on [url http://download.oracle.com/docs/cd/E17781_01/server.112/e18804/memory.htm#ADMQS174]Managing Memory. It's not a complete guide, but a rough introduction, but it'll probably help you understand the memory concepts in the database.
    Keep in mind that you may only assign 1 GB of memory in total when you setup your memory manually.
    -Udo

  • ORA-04031: unable to allocate 128 bytes of shared memory

    Hi,
    experts i need your advice here,
    in my application we have on so called Master view which has 550 columns, this view is left outer join with 60 other views, something like
    select c1
    from   master_view
             left outer join v1 on --
             left outer join v2 on --
             left outer join v60 the compilation of the master view takes around 140 secs, but when i give grants to other users, or i re compile again, it shows me the error
    ORA-04031: unable to allocate 128 bytes of shared memory plz assist me how i should resolve this issue,
    Regards
    nic

    Hi billy,
    your idea worked big big time,
    i encaspulated all the outer joins views in small small views and finally build mv on each views,
    the master view is plain equijoin, and has only 5 new mvs in its join condition,
    the performance is increased tremendously,
    thanks,
    some times i wonder y i dont get such ides ;-);
    all and all i can say,
    good judgement comes from good experience, but good experience comes from bad judgement...
    Regards
    nic

  • Ora-04031 unable to allocate shared memory

    Hi Guru's
    Could some one help me in finding the sql's/program which causing the ora-04031 unable to allocate 3896 bytes of shared memory.
    any suggestion is highly apprciated
    Kind Regards

    You may want to take look at:
    ORA-04031: unable to allocate 4032 bytes of shared memory
    >
    ORA-04031 unable to allocate n bytes of shared memory ("string","string","string","string")
    Cause: More shared memory is needed than was allocated in the shared pool.
    Action: If the shared pool is out of memory, either use the DBMS_SHARED_POOL package to pin large packages, reduce your use of shared memory, or increase the amount of available shared memory by increasing the value of the initialization parameters SHARED_POOL_RESERVED_SIZE and SHARED_POOL_SIZE. If the large pool is out of memory, increase the initialization parameter LARGE_POOL_SIZE.

  • ORA-04031 unable to allocate 4080 bytes of shared memory

    Hi Everyone,
    The error ORA-04031 has been consistently occuring in our production landscape.
    We have Applied Oracle patches in BI7.0 (2004s - Oracle 10.2.0.2) system as per SAP's suggestions.  (A set of 35 patches as per note 871096)
    (Patches List - 5369855,5253307,6340979,5618049,7133360,5895190,6826661,4704890,6005996,5188321,6447320,3748430,5442919,4952782,5458753,5941030,5345999,6153847,5530958,4883635,5636728,4668719,5635254,5063279,7237154,5103126,4638550,4770693,4864648,6046043,7608184,6729801,5363584,6771608,6435823)
    Applying oracle patches has not resolved this issue.  The error is reoccuring.  Now as per notes 1171650 and 830576 we have tuned in certain parameters.
    We also checked the Notes 869006 and 1120481 but nothing much is helpful. 
    A Go-Live is scheduled this week.  Could you please suggest what further actions need to be taken to identify the issue and resolve it.
    Thanks in advance.
    Best Regards
    Bhupesh

    Hi Stefan / Jens,
    Thanks for the help so far.
    Running the SQL statement produced more than 21000 rows.  We could get an idea as to which statement is using more memory.
    Top 5 statements are as below
    SQL> select * from (SELECT SQL_text, SHARABLE_MEM, PERSISTENT_MEM, RUNTIME_MEM FROM V$SQLAREA ORDER BY SHARABLE_MEM desc) where rownum <=5;
    SQL_TEXT
    SHARABLE_MEM PERSISTENT_MEM RUNTIME_MEM
      select a.segment_type,         round(a.mb,2) size_mb,         round(decode(seg_num,0,0,a.mb/a.seg_num),2) size_avg_mb,         a.seg_num,         a.ext_num,              nvl(b.more100ext,0) more100ext,         decode(lower(a.segment_type),'table',c.com_tab,                                      'index',d.com_ind,                                         'table partition',e.com_tpar,                                    'index partition',f.com_ipar,                         0) compressed,          decode(lower(a.segment_type),'table',g.log_tab,                                      'index',h.log_ind,                                'table partition',i.log_tpar,                                     'index partition',j.log_ipar,                                    'lobsegment',k.log_lob,                                 'lobindex',k.log_lob,                                     0) nologging  from (select segment_type,               nvl(count(*),0) seg_num,                    sum(nvl(bytes,0))/10
         1257431         441584      436528
      select a.username user_name,         a.user_id user_id,         round(nvl(b.mb,0),2) size_mb,         nvl(b.seg,0) segments,         nvl(c.tab,0) tables,     nvl(d.ind,0) indexes,          nvl(b.ext,0) extents,         a.default_tablespace default_tablespace,         a.temporary_tablespace temporary_tablespace,      to_char(a.created, 'dd.mm.yyyy') created,         to_char(a.created, 'hh:mm:ss') created,         a.account_status account_status,         a.profile profile  from    dba_users a,    (select owner, count() seg, sum(nvl(bytes,0))/1024/1024 mb,         sum(nvl(extents,0)) ext     from dba_segments group by owner) b, (select owner, count() tab from dba_segments     where segment_type='TABLE' group by owner) c,    (select owner, count(*) ind from dba_segments     where segment_type='INDEX' group by owner) d  where a.username=b.owner() and     a.username=c.owner() and        a.username=d.owner(+)
          578473         200064      196176
    SELECT count(*) over () as total_count,        sd_xe_ash_nm.event_name,        sd_xe_ash_nm.event_id,        sd_xe_ash_nm.parameter1 as p1text,        (CASE WHEN (sd_xe_ash_nm.parameter1 is NULL                 OR                    sd_xe_ash_nm.parameter1 = '0')              THEN 0              ELSE 1         END) as p1valid,     sd_xe_ash_nm.parameter2 as p2text,        (CASE WHEN (sd_xe_ash_nm.parameter2 is NULL                    OR                    sd_xe_ash_nm.parameter2 = '0')           THEN 0              ELSE 1         END) as p2valid,        sd_xe_ash_nm.parameter3 as p3text,        (CASE WHEN (sd_xe_ash_nm.parameter3 is NULL                         OR                    sd_xe_ash_nm.parameter3 = '0')              THEN 0              ELSE 1         END) as p3valid,        sd_xe_ash_nm.keh_evt_id,        nvl(xc.class#, 0) as class_num,             sd_xe_ash_nm.wait_class_id,        nvl(xc.keh_id, 0) as keh_ecl_id,    sd_xe_ash_nm.ash_cnt,         sd_xe_ash_nm.tot_wts_diff,
          453779         138168      132136
      select    a.name db_name,    round((nvl(b.data_KB,0)nvl(c.temp_KB,0))/1024/1024,2) size_gb,    round((nvl(b.data_KB,0)-nvl(d.data_free,0)             nvl(e.temp_KB_used,0))/1024/1024,2) used_gb,         round((nvl(d.data_free,0)nvl(c.temp_KB,0)-     nvl(e.temp_KB_used,0))/1024/1024,2) free_gb,    to_char(((nvl(b.data_KB,0)-nvl(d.data_free,0)           nvl(e.temp_KB_used,0))/(nvl(b.data_KB,0)+              nvl(c.temp_KB,0)))100, '999') percent_used,    to_char(((nvl(d.data_free,0)nvl(c.temp_KB,0)-           nvl(e.temp_KB_used,0))/(nvl(b.data_KB,0)              nvl(c.temp_KB,0)))100, '999') percent_free,    f.num_seg,    g.num_ts,    h.num_us, to_char((nvl(b.data_KB,0)/(nvl(b.data_KB,0)+             nvl(c.temp_KB,0)))100,'999') percent_data,    to_char((nvl(c.temp_KB,0)/(nvl(b.data_KB,0)+          nvl(c.temp_KB,0)))100,'999') percent_temp,    round(to_char((f.tab_kb/(nvl(b.data_KB,0)+                    nvl(c.temp_KB,0)))*100,'999'),0) percent_tab,    round(to_char((f.
          449213         154968      151184
      select ts,         round(size_mb,2) size_mb,         round(free_mb,2) free_mb,         round(decode(size_mb,0,'',(size_mb-           free_mb)100/size_mb),0) per_used,      autoextensible,         round(total_size_mb,2) tot_size_mb,         round(total_free_mb,2) tot_free_mb,         round(decode(total_size_mb,0,'',(total_size_mb-        total_free_mb)100/total_size_mb),0) per_tot_used,         files,         segments,         extents,         status,         contents  from    (select a.tablespace_name ts,         nvl(c.mb,0)nvl(e.mb,0) size_mb,            decode(lower(a.contents),'temporary',              nvl(e.mb,0)-nvl(f.used_mb,0),nvl(d.free_mb,0))           free_mb,            nvl(c.files,0)nvl(e.files,0) files,            nvl(b.seg,0) segments,            nvl(b.ext,0) extents,         decode(lower(a.contents),'temporary',         decode(sign(nvl(e.tot_mb,0)-nvl(e.mb,0)),1,'YES','NO'),         decode(sign(nvl(c.tot_mb,0)-nvl(c.mb,0)),1,'YES','NO'))
          429595         139184      136072
    SQL>
    Please suggest how to go ahead.
    Thanks & Regards
    Bhupesh

  • ORA-04031: unable to allocate

    hi gurus,
    I am getting the following error whenever try to access database from client side or login to SQL*Plus :
    ora 04031, 00000, "unable to allocate %s bytes of shared memory (\"%s\",\"%s\",\"%s")"
    But i can login on server and working properly.
    I am using oracle 9i release 1 on win 2k.
    Can any one help me to come out of this problem.
    Thanks
    Regards,
    Raghv

    Thanks Joel to have some time for this post.
    Hope these details will help you to understand the problem.
    How long is the virtual memory of your OS ?Minimum : 744 MB Maximum : 1488 MB
    How long is the RAM memory of the OS ?RAM : 640 MB
    Do you have several instances in the same OS ?No,only single instance
    Details from init.ora file:
    # Cache and I/O
    db_block_size=4096
    db_cache_size=33554432
    # Cursors and Library Cache
    open_cursors=300
    # Network Registration
    instance_name=orcl
    # Pools
    java_pool_size=33554432
    large_pool_size=1048576
    shared_pool_size=33554432
    # Processes and Sessions
    processes=150
    # Redo Log and Recovery
    fast_start_mttr_target=300
    Desired query output :
    SQL> select * from v$shared_pool_reserved;
    no rows selected
    SQL> select * from v$sgastat where name='free memory';
    POOL NAME BYTES
    shared pool free memory 3301916
    large pool free memory 4294613080
    java pool free memory 28954624
    SQL> select sum(bytes) from v$sgastat where pool = 'shared pool';
    SUM(BYTES)
    46137344
    SQL> select sum(bytes) from v$sgastat where pool = 'java pool';
    SUM(BYTES)
    33554432
    SQL> select sum(bytes) from v$sgastat where pool = 'large pool';
    SUM(BYTES)
    4.295E+09
    Regards,
    Raghv

  • 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.

  • ORA-04301:Unable to allocate 8144 bytes of shared memory

    I am using 64 bit version of oracle 10g Release 2 (10.2.0.1.0)
    I am randomly getting this error. The full error message is below:
    ORA-04301:Unable to allocate 8144 bytes of shared memory("large pool","COMPANYHISTORY","kxs-heap-w","qesaQBinit:buffer")
    The table name keeps changing as the queries change. Similarly sometimes instead of "large pool" I get "shared pool" in the above message.
    I tried increasing the shared pool size but the problem did not resolve.
    Please help
    Regards
    Madhup

    I have already tried that, but I am not able to solve the problem. Is there a way to compute how much space you should define for the shared pool, the large pool etc.
    Regards
    Madhup

  • Urgent help with ORA-01062: unable to allocate memory for define buffer

    Hello, Folks!
    I have a c++ code that is using OCI API that is running both in
    windows and in spark.
    (The same c++ code compiled and running in both platforms)
    and asking the same query.
    In windows, everything is OK but in spark
    it failes...
    The ORACLE Server is installed on win2003 station
    Both client and server ORACLE version is 10.2.0.1.0
    The code is running on spark(oracle instant client is installed)
    This query is a simple select query that selects only one field
    of type VARCHAR2(4000) (the same problem with happen with any
    string type field larger than 150 characters)
    The error occured when calling for OCIDefineByPos method
    when associating an item in a select-list with the type and output
    data buffer.
    The error message is: ORA-01062: unable to allocate memory for define
    buffer
    (This error message signifies that I need to use piecewise operation...)
    But it happens even if I make this varchar2 field to be of size larger
    than 150.
    It is not fair to use piecewise fetch for such a small fields sizes.
    May be there is not configuration setting that can enlarge this
    I know that I wrote here a very superficial description.
    If somebody knows something about this issue, please help
    Thanks

    I had a special luck today after searching the solution per weeks:)I have got a solution.
    When I get the size of the oci field, in the following expressioin
    l_nResult = OCIAttrGet(l_oParam->pOCIHandle(), OCI_DTYPE_PARAM, &(orFieldMD.m_nSize), NULL, OCI_ATTR_DATA_SIZE, m_oOCIErrInfo.pOCIError());
    orFieldMD.m_nSize was of type ub4 but according the manual it must be ub2.
    As a result, the number returned was very large (junk?) and I passed this value to OCIDefineByPos
    Now I changed the type and everything is working!!!
    In windows there is not problem with this expression :)
    Thanks
    Issahar

  • ORA-01659: unable to allocate MINEXTENTS beyond...

    Hi All,
    I have created a new table space as
    CREATE SMALLFILE
    TABLESPACE "FIRMGOLD"
    LOGGING
    DATAFILE '/gold3/gold/oradata/GOLD/FIRMGOLD.dbf' SIZE 2048M EXTENT
    MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO
    Then I went for creation of new user as
    CREATE USER "DIIS_FIRM_GOLD" PROFILE "DEFAULT"
    IDENTIFIED BY " DIIS_FIRM_GOLD " DEFAULT TABLESPACE " FIRMGOLD "
    TEMPORARY TABLESPACE "TEMP"
    QUOTA UNLIMITED
    ON " FIRMGOLD "
    ACCOUNT UNLOCK;
    GRANT ALTER ANY TRIGGER TO " DIIS_FIRM_GOLD " WITH ADMIN OPTION
    GRANT ALTER PROFILE TO " DIIS_FIRM_GOLD " WITH ADMIN OPTION
    GRANT ALTER RESOURCE COST TO " DIIS_FIRM_GOLD " WITH ADMIN OPTION
    GRANT ALTER ROLLBACK SEGMENT TO " DIIS_FIRM_GOLD " WITH ADMIN OPTION
    GRANT ALTER SESSION TO " DIIS_FIRM_GOLD " WITH ADMIN OPTION
    GRANT ALTER SYSTEM TO " DIIS_FIRM_GOLD " WITH ADMIN OPTION
    GRANT ALTER TABLESPACE TO " DIIS_FIRM_GOLD " WITH ADMIN OPTION
    GRANT ALTER USER TO " DIIS_FIRM_GOLD " WITH ADMIN OPTION
    GRANT BACKUP ANY TABLE TO " DIIS_FIRM_GOLD " WITH ADMIN OPTION
    GRANT CREATE ANY CLUSTER TO " DIIS_FIRM_GOLD " WITH ADMIN OPTION
    GRANT CREATE ANY INDEX TO " DIIS_FIRM_GOLD " WITH ADMIN OPTION
    GRANT CREATE ANY INDEXTYPE TO " DIIS_FIRM_GOLD " WITH ADMIN OPTION
    GRANT CREATE ANY JOB TO " DIIS_FIRM_GOLD " WITH ADMIN OPTION
    GRANT CREATE ANY LIBRARY TO " DIIS_FIRM_GOLD " WITH ADMIN OPTION
    GRANT CREATE ANY PROCEDURE TO " DIIS_FIRM_GOLD " WITH ADMIN OPTION
    GRANT CREATE ANY SEQUENCE TO " DIIS_FIRM_GOLD " WITH ADMIN OPTION
    GRANT CREATE ANY SYNONYM TO " DIIS_FIRM_GOLD " WITH ADMIN OPTION
    GRANT CREATE ANY TABLE TO " DIIS_FIRM_GOLD " WITH ADMIN OPTION
    GRANT CREATE ANY TRIGGER TO " DIIS_FIRM_GOLD " WITH ADMIN OPTION
    GRANT CREATE ANY VIEW TO " DIIS_FIRM_GOLD " WITH ADMIN OPTION
    GRANT SYSDBA TO " DIIS_FIRM_GOLD " WITH ADMIN OPTION
    GRANT "CONNECT" TO " DIIS_FIRM_GOLD " WITH ADMIN OPTION;
    GRANT "DBA" TO " DIIS_FIRM_GOLD " WITH ADMIN OPTION;
    After creating new user, I went for impdp of the dump(got from the existing user) then I encountered the following error,
    ORA-39171: Job is experiencing a resumable wait.
    ORA-01659: unable to allocate MINEXTENTS beyond 13 in tablespace CKCGOLD1
    I expected the new user “DIIS_FIRM_GOLD” to use the newly created tablespace FIRMGOLD, but instead it used old tablespace CKCGOLD1.
    When I ran the following script
    SELECT TABLESPACE_NAME,SUM(BYTES)/1024/1024 FREE_SPACE
    FROM DBA_FREE_SPACE
    GROUP BY TABLESPACE_NAME
    It returned
    TABLESPACE_NAME FREE_SPACE
    SYSTEM           221.875
    CKCGOLD2           1176.1875
    FAS_GENERAL      957.625
    JEWELGOLD      2038
    USERS           4.5625
    CKCGOLD1_I      1812
    RBS           1999.9375
    FIRMSILVER           1023.9375
    JEWELSILVER           1023.9375
    SYSAUX      21
    CKCGOLD1      26.625
    TABLESPACE_NAME FREE_SPACE
    CKCSILVER1_I      497.875
    FIRMGOLD      2038
    UNDOTBS1           1352.3125
    CKCSILVER1           1124.8125
    My new tablespace FIRMGOLD has not been used.
    Can anyone help me out in this regard.

    Hi,
    The impdp command i used is as below,
    impdp iis_firm_gold/****** REMAP_SCHEMA=iis_1_gold:iis_firm_gold dumpfile=exp_19082007_gold.dmp logfile=imp_19082007_gold_firm.log job_name=IMP_SAM19082007_GOLD_FIRM CONTENT=METADATA_ONLY TRANSFORM=oid:n
    So how should the remap_tablespace be used in the above command?
    U mean like, inserting "REMAP_TABLESPACE=CKCGOLD1:FIRMGOLD" in to my impdp command?
    Regards,
    SAM.

  • ORA-01659: unable to allocate MINEXTENTS beyond 9 in tablespace

    Hi all
    I received database dump from client and I am trying to Import into our database. I created tablespace and while trying to import, I am getting below error
    ORA-01659: unable to allocate MINEXTENTS beyond 9 in tablespace <>
    I increased the Size of the tablespace up to to 6gb still getting the same error.
    what I received is only structure without data. still why It's needed much space.
    My doubts are :
    1) How to know what is the size required to complete the dump
    2) s there any option to take export which can take less space when I import?
    My plan is not to replicate the DB but only to import the structure in a schema.
    We don't have a DBA so I am doing this task
    Thanks in adv

    Thanks Maran,
    ABLESPACE_NAME     BLOCK_ID     BLOCKS     BYTES
    medt          17          507904     4160749568
    medt          507921          507904     4160749568
    medt          1015825          507904     4160749568
    medt          1523729          507904     4160749568
    medt          2031633          507904     4160749568
    medt          2539537          507904     4160749568
    medt          3047441          507904     4160749568
    medt          3555345          507904     4160749568
    medt          4063249          131048     1073545216

  • ORA-01659: unable to allocate MINEXTENTS beyond 29 in tablespace

    Hi,
    I am importing data into MATRIXDEV schema with the following imp command.
    imp matrixdev/crm FILE=crmodrepodump1.dmp tables=odperf_request_summary INDEXES=N IGNORE=Y STATISTICS=NONE
    But i am getting following error. Even after adding new datafile to the CRMODREPO_DATA table space i am getting same error.
    ORA-01659: unable to allocate MINEXTENTS beyond 29 in tablespace
    Can some one help me in this??
    I have used following exp command for export.
    imp userid=matrixdev/crm file=crmodrepodump1.dmp log=crmodrepodump1.log statistics=NONE indexes=Y tables=odperf_request_summary
    Thanks

    ORA-01659: unable to allocate MINEXTENTS beyond string in tablespace string
    Cause: Failed to find sufficient contiguous space to allocate MINEXTENTS for the segment being created.
    Action: Use ALTER TABLESPACE ADD DATAFILE to add additional space to the tablespace or retry with smaller value for MINEXTENTS, NEXT or PCTINCREASE

Maybe you are looking for