DataPump to a single index tablespace sqlfile gives ORA-31655

Similar Questions

• Should I consider index tablespace too?

  Hello
  
  We have 6 Tablespaces that represent DATA and 6 other TABLESPACES which represent the INDEX, we db backup using RMAN.
  
  In order to cover ourself completely against the loss of a single table, I intend to perform the backup of data by Data Pump (expdp/impdp).
  
  The question I have is... what I have to do an EXPDP of Tablespaces INDEX also? If this isn't the case, then when I go to restore DATA STORAGE spaces on my test server, how can ensure me that the index entries are created automatically in the TS of the INDEX, so that data access is faster?
  
  
  Concerning
  
  Learner

  Dear learner1,

  This thread is going in recovery and the backup policy Manager, but I'll try to address your concerns.

  You can always use the flashback of the Oracle 10 g database feature (if it is already enabled) and you can use the recyclebin in flashback the paintings from before the fall.

  If there is a critical table or diagram of your database, you can use the datapump or the classic export for the operation of separate backup utility. However, as damorgan has already stated that the most reliable way to backup/restore/recover the database is the RMAN. This does not mean that you should not use other means as cold, utility backup etc export.

  You can separate the index and storage of data in your database and when you lost the index tablespace, you can recreate the indexes and storage space if you already have the DDL of the relevant indices. Restoration of databases with the impdp will not recover the index tablespaces because you did not save the front index tablespaces.

  Also, we have an application that uses separate storage for the data and the indexes and I had a problem once with a data index file and he was not very tall, so I simply removed the tablespace, data files, indexes and recreate the tablespace, index and its partitions because I had the index DDL. Of course, this is not connected with storage of data. If you lose the tablespace data, your data is lost and the recovery should be used.

  Hope that helps.

  Ogan

• Siebel Database Configuration Assistant unable to identify the indexes tablespace

  Hello
  
  I install Siebel CRM 8.1.1 on AIX platform. We have a RAC database has allowed the backend and that two tablespace is created, other data and another for the index. Now in the wizrd of configuration database to the name of these two storage spaces; provide us with the name of tablespae of data in the Tablespace filed Table and index tablespace in the tablespace index rating of the Setup Wizard. Now when we click on the next button. The wizrd of configuration gives error of unable to identify the indexes tablespace.
  
  Why is - what happens as index tablespace is correctly created in the database. Please help me in this. Quick Respance you will be appreciated.
  
  Kind regards
  
  Abgrall

  If you ran:

  change the quota unlimited on user SIEBEL

  ?

• Remove the constraint of PK to win space on INDEX tablespace

  I dropped a huge table (which has recently imported for testing) INDEX by deleting the PK constraint to win space on INDEX tablespace. But INDEX tablespace is not reduced image.

  Please notify.

  Kind regards

  Veera

  The tablespace not to shrink because it's a performance inhibitor.

  However, you can see the free space within the increase of tablespace, and this space is generally available for other objects.

• by specifying the index tablespace in to disable the primary key constraint

  Hello
  during the ETL I want to disable constraints PK/UK to speed up the load;
  on activation of the constraint, the corresponding indices are created in a different tablespace while they were initially on the creation of the table itself
  I tried to disable PK / UK with the option 'keep the index', the index value corresponding to the status of "unusable" and use ' alter session set skip_unusable_indexes = true', but then I can't insert rows with the error.

  Error: ORA-01502: index 'xxx' or partition of such index is in unusable state

  can anyone tell if there is a way to allow the PK/UK constraint and specify the storage space for the corresponding indices, or keep the index and inserts works?
  I'd like to avoid to drop constraints / indexes and re-create them both from scratch after the load
  Thank you for the advice
  Thank you
  Rgds

  >
  can anyone tell if there is a way to allow the PK/UK constraint and specify the storage space for the corresponding indices, or keep the index and inserts works?
  I'd like to avoid to drop constraints / indexes and re-create them both from scratch after the load
  >
  Have you tried specifying the table space in the USING clause when you activate the constraint?

  ALTER TABLE emp ENABLE PRIMARY KEY USING INDEX TABLESPACE myTS;
  

  See DBA guide
  http://docs.Oracle.com/CD/B28359_01/server.111/b28310/indexes003.htm
  >
  Creating an Index associated with a constraint

  Oracle database applies a UNIQUE key or a constraint integrity PRIMARY KEY on a table by creating a unique index on the unique key or primary key. This index is created automatically by the database when the constraint is enabled. No action is required by you when you run the CREATE TABLE or ALTER TABLE statement to create the index, but you can optionally specify an ESCALATION using clause to exercise control over his creation. This includes them when a constraint is defined and enabled, and when a constraint defined but disabled is selected.
  >
  Note the last sentence two sentences:
  >
  You can optionally specify an ESCALATION using clause to exercise control over his creation. This includes them when a constraint is defined and enabled, and when a constraint defined but disabled is selected.
  >
  You realize, I hope, that the only way can Oracle KNOWS that the index contains valid values is to rebuild?

• How to import tables, index, tablespace, etc. of a DMP.

  Hello
  
  I would like to know how to import tables, index, tablespace, etc. of an export an Oracle 10.2.0.1 to apply on an Oracle 11.2.0 DMP. When I import the DMP file a unique Tablespace, for example, will users tablespace data.
  
  On the basis of origin, we have different tablespace each separated with different content (tables, index) and I would like to know if it is posible to import the same schema, tables, index, tablespace quite with a DMP alone, Export. I can't use DBUA because the database on the 10.2 software is missing, I have only one file (24 GB) DMP DMP!.
  
  Thanks for the reply,
  
  Sorry for my English :).
  
  Kind regards.

  The standard solution is

  -Make sure that the target user doesn't have the UNLIMITED TABLESPACE privilege, using REVOKE
  -Make sure that the target user has no QUOTA on the default tablespace using ALTER USER... QUOTA
  -Make sure that there is quota on the tablespace (s) of the target, using ALTER USER... QUOTA
  -import indexes = n
  -empty the index orders in a separate file
  IMP indexfile =...
  -run this file

  --------------
  Sybrand Bakker
  Senior Oracle DBA

• index to around index tablespace

  Hello
  
  I want to move the index of old to new index tablespace tablespace?
  
  who controls what should I use?
  
  Thanks in advance.

  Select index_name, tablespace_name of dba_indexes where index-name = "PK_CUSTOMER";

  You probably have the same index name (and table name) in two different patterns.

  Integrate INDEX_OWNER and valid in your request on DBA_INDEXES

  Hemant K Collette

• MATERIALIZED View Log Index Tablespace

  Is anyone aware of the syntax or a framework to be able to specify the index of a materialized view of the journal storage space?

  We chunk our objects by tablespace - index, tables, CLOB.

  Creating a materialized view log and specifying the storage space in which it should be created created the mv log in the correct location, but the index that is created uses the default tablespace for the user.

  And Yes, I Googled it. LMGTFY

  create materialized view log on MY_TEST tablespace my_tablespace ;
  

  select table_name, tablespace_name
    from user_tables
   where table_name like 'MLOG%';
  

  TABLE-NAME	TABLESPACE_NAME
  MLOG$ _MY_TEST	MY_TABLESPACE

  select table_name, index_name, tablespace_name
    from user_indexes
   where table_name like 'MLOG%';
  

  TABLE-NAME	INDEX_NAME	TABLESPACE_NAME
  MLOG$ _MY_TEST	I_MLOG$ _MY_TEST	USERS

  I found these documents:

  Index on MLOG$ (materialized view Log): difference in behavior between 11.2.0.3 and 11.2.0.4 (Doc ID 1959657.1)

  Materialized View Log (Mlog$) Index not created in its default Tablespace (Doc ID 1959658.1)

  I guess you are running 11.2.0.4, right?

  In previous versions, no index has been created automatically for the journal of MV.

  Kind regards

  Bashar

• index tablespace space

  
  Hello

  I have a spatial table in a tablespace (USERS) and I created a spatial index for this table in a different tablespace (IDXDATA) to the following help.

  Index is created, but its tablespace does not appear when I saw ALL_INDEXES query dictionary.

  CREATE INDEX pl_vpoint_sidx ON pl_vpoints (geometry) INDEXTYPE IS MDSYS. SPATIAL_INDEX

  parameters ('tablespace = idxdata');

  Select index_name, index_type, table_name, tablespace_name of all_indexes where owner = "XYZ";

  XYZ FIELD PL_VPOINTS NULL PL_VPOINT_SIDX

  Hi Don,

  I'm not sure but I think this happens because a spatial index is a 'normal' table in your schema (tables MDRT_ # $). So if you created in a different tablespace, you will need to use the SDO-views to get the index table name, then search what tablespace this table is:

  Select sii.table_name, sii.column_name, sii.index_name, sii.sdo_index_table, ut.tablespace_name sdo_index_tablespace

  of user_sdo_index_info sii, ut user_tables

  where ut.table_name = sii.table_name;

  Check the user_sdo_index_metadata and the user_sdo_index_info a view, they contain a lot of useful information (replace user with s/n If you have rights, then you will get an additional column, 'owner' according to the usual data dictionary views).

  HTH,

  Stefan

• Reclaim the storage space for the Index tablespace. The fastest approach

  Hello world
  My version of the database is 10.2.0.4
  I have a partitioned table that has divided the indexes that are found on a tablespace called INDEX01.
  the space allocated to the tablespace INDEX01 is about 10 terabytes, however the space used is about 1.5 tera-bytes.
  I need to recover to the level of the storage space. I decided to recreate the tablespace INDEX01.
  I did not create index scripts so I came with two approaches
  1. to move the index partitions in a different tablespace, drop the tablespace INDEX01, recreate the tablespace INDEX01 and then replace the index partitions.
  2. intentionally mark the unusable index partitions, drop the tablespace INDEX01, recreate the tablespace INDEX01 and then rebuild the index partitions.
  
  step 2 seems faster but I need to know if it would work and impact? (the tablespace would pass with the marked index unsable partitions) and I hope that the original table is not affected?
  
  concerning
  Samuel

  Samuel K wrote:
  Hello world
  My version of the database is 10.2.0.4
  I have a partitioned table that has divided the indexes that are found on a tablespace called INDEX01.
  the space allocated to the tablespace INDEX01 is about 10 terabytes, however the space used is about 1.5 tera-bytes.
  I need to recover to the level of the storage space. I decided to recreate the tablespace INDEX01.
  I did not create index scripts so I came with two approaches
  1. to move the index partitions in a different tablespace, drop the tablespace INDEX01, recreate the tablespace INDEX01 and then replace the index partitions.
  2. intentionally mark the unusable index partitions, drop the tablespace INDEX01, recreate the tablespace INDEX01 and then rebuild the index partitions.

  Since you're talking about the abolition of the index, I guess that you have application downtime. Since this is the case, you may want to consider the fact that an index rebuild can analyze the existing index in order to collect relevant data - provides the index is not unusable, and you do not have a reconstruction in line.

  The fastest option - if INDEX01 is a locally managed tablespace - would probably be:
  

  
  Find partitions of index holding at the beginning of the file and rebuild (nologging, parallel, perhaps for speed) in a different tablespace.
  Find the clues that are 'next' in the repository and rebuild in the same tablespace. If the tablespace is locally managed, then the index will fill the empty space at the beginning of the files.
  Work on the files gradually moving toward the front of the space of tables, indexes, and leaving the 'next' bit of the empty file.
  Finish by copying back the small number of partitions of index you rebuilt in the tablespace to spare (and drop this tablespace).
  Shrink the large tablespace.
  

  Concerning
  Jonathan Lewis

  p.s. I wrote a small script some time ago to report the measure ordering in a tablespace - it can help you to choose the order of rebuild.
  http://jonathanlewis.WordPress.com/2010/02/06/shrink-tablespace/

• A single subscription App CC gives access to Fireworks CS6?

  I only really want Fireworks CS6. Unfortunately it doesn't seem to be a way to buy a key for it more.

  I have been informed that FW CS6 comes with a subscription to creative cloud, but I'm not really all other applications. I can't select CS6 of fireworks from the simple App option for creative cloud.

  The closest option you, I can think is to get Dreamweaver as a single subscription App I always use that sometimes if I am migrating away from him. If I subscribe to Dreamweaver CC as a single application, will I have to install and use Fireworks CS6 access as it is is more updated?

  If not, how can I have FW CS6 access without having to buy any creative cloud?

  You can always purchase Fireworks cs6 perpeptual permits:

  Adobe - Adobe Fireworks CS6 shop

  concerning

• Transform a no Unique Index in a single index

  Hello

  Version: 11.2.0.4.0 Enterprise Edition

  We got a non-unique Index for a primary key constraint. I would like to change that in a unique index. I know that you can not change the index to change. Is the only way to disable the primary key, delete the index and re-enable the constraint or is there a better solution? It is a 24/7 platform.

  sql_colder

  Windows service exist for a reason.

  You can also create clues online in an operational database.

  There is no other method outside the use of DBMS_REDEFINITION.

  Think about it: what is the business case to change the index?

  -----------

  Sybrand Bakker

  Senior Oracle DBA

• You BUY a button and then take me to your page of cloud to adobe where I can't just buy but have to pay in a plan to use it. You have even as a single application. What gives? Your new cloud app purchase is terrible. I hate that it comes with pictures

  I really see why many are annoyed and frustrated by your new purchase method. Trying to lose loyal customers of the past and those of the present. I really hope that you get a glimpse of what you really do.

  It's funny, I tried and seen no upgrade option, it only took me to the creative cloud. Now, today I tried again and it shows the option more price. Thank you. Go figure.

• Subqueries, addressing deep gives ORA-00904: invalid identifier

  Why the following query gives the error:
  

  with T as
  (
   select 1 ID from dual union all
   select 2 ID from dual
  )
  select ID from T
  where 1 = (
     select Cnt from
        (
         select count(*) Cnt
         from T innerT
         where innerT.ID = T.ID
        )
  )
  /*ORA-00904: "T"."ID": invalid identifier*/
  ;

  But this query succeeds:
  

  with T as
  (
   select 1 ID from dual union all
   select 2 ID from dual
  )
  select ID from T
  where 1 = (   
        select count(*) Cnt
        from T innerT
        where innerT.ID = T.ID
        )
  /*1
  2*/
  ;

  Why the first query gives grammatice "error? There in one addressing deep enough level to the outside world, which seems to be a problem:

  innerT.ID = T.ID

  Can you explain why such a thing is not allowed?

  Hello

  I think it's because correlated subqueries cannot be nested rather than on a single level.
  The inner query external very table T is 2 levels.

  In the second case, there only one & level between inner query and table T, so it works.

  I'll try to find some useful links to this topic...

  And here's one:
  AskTom

  Published by: Nicosa 31 May 2010 06:02
  (I can't get the link to display correctly...)

  Published by: Nicosa 31 May 2010 06:02

• Private DB link does not not present despite entry TNS pattern gives ORA-02019: Description of the connection to remote database not found

  Hi DBAs,

  I have created a new schema and granted create database link and create databases of public link privileges.

  After that I created the link private DB for which TNS entry is present in TNSNAMES.ora but everything by testing the link, I get the error:

  ' ORA-02019: Description of the connection to the remote database not found. '

  Kind regards

  Ritz

  Try using:

  CREATE the DATABASE LINK "VENUS.ritz.ac.uk".

  CONNECT TO 'VENUSREADONLY' IDENTIFIED BY 'FLAMING0READ0NLY' WITH THE HELP OF "VENUS."

  Your dblink seem to give the entry not TNS service name.

  Kind regards

  --

  Bertrand

  PS you have to hide people with disabilities before posting.