How to ignore index during impdp...

Hi All,
I have Oracle 11g database, I want to import one schmea;s tables into 11g database. Table is having 2 millons records and table size is 54G.
During impdp this will definately take long time. As we had ignore=y and create index file option with IMP, do we have similar kind of thing with impdp?
If you have any idea then please suggest me.
Thanks in advance.

Hi ,
your suggested link and exclude option helps me.
I have one query , in my impdp if I mentioned exclude parameter like exclude=INDEX:IN('TESTEMP') , then will it exlude only TESTEMP table's index or entire schema's index?
my entire impdp command like below:
impdp system/********@testqa remap_schema=SCOTT:SCOTT dumpfile=SCOTT.dmp TABLE_EXISTS_ACTION=SKIP
exclude=INDEX:IN('TESTEMP') logfile=SCOTT_!.log directory=DATA_PUMP_DIR
when this dump is running I observed that it was taking too much time on this line "SCHEMA_EXPORT/TABLE/INDEX/INDEX"...so I though it create indexes for all the tables except which I exclude in command.
Please suggest me.
Thanks...

Similar Messages

How to ignore error during saving?

I got the following error during saving:
It appears every time when i save the ai file,
how can I ignore it?

I just got the font from fonts101.
does not seem to have any embedding issues for me...

How to ignore programmatically some items during a query ?

Hi all,
The process of my application is like this : first of all the end-user enters some criteria , then he/she presses a button to search for the possible results matching the criteria entered (execute_query). The possible results are displayed through a multirecord based datablock.
The criteria screen has two parts , say part_a and part_b. When the end-user does not enter any criteria in part_b then the datasource of the results block should be a table , say data_source_1 ; and if some criteria are entered in part_b then the datasource of the results block should be a view , say data_source_2.
The datasource data_source_1 has less number of columns than the datasource data_source_2 , but all of data_source_1's columns are included into data_source_2.
So my problem is when the datasource of the results block is set to data_source_1 then there are unknown columns when executing the query (alert error). All of the columns of data_source_2 are included in the results block , and all of the columns of data_source_1 are automatically there because mathematically speaking data_source_1 is included into data_source_2.
I have tried to use in the pre-query trigger of the results block this statement : set_item_property('results_possibles.column_a',queryable,property_false); but the same error still occurs.
So how to ignore these items ?
Thank you very much indeed.

After looking at what you did to try to solve the problem, I'm not sure what the actual problem is.
You can make both datasources have the same number of columns by selecting nulls:
data_source_1: select a, b, c, null as d, null as e from <table>
data_source_2: select a, b, c, d, e from <view>
If you have a field which is used to query a column which is included in data_source_2 but not in data_source_1, and that field is populated when you run the query, then just set the block's default_where to ignore that field.
eg
data_source_1: where...and c like nvl(:control.c,'%')
data_source_2: where...and c like nvl(:control.c,'%') and d like nvl(:control.d,'%')...

Performance problem because of ignored index

Hi,
We have a performance problem with kodo ignoring indexes in Oracle:
Our baseclass of all our persistent classes (LogasPoImpl) has a subclass
CODEZOLLMASSNAHMENIMPL.
We use vertical mapping for all subclasses and have 400.000 instances of
CODEZOLLMASSNAHMENIMPL.
We defined an additional index on an attribute of CODEZOLLMASSNAHMENIMPL.
A query with a filter like "myIndexedAttribute = 'DE'" takes about 15
seconds on Oracle 8.1.7.
Kodo logs something like the following:
[14903 ms] executing prepstmnt 6156689 SELECT (...)
FROM CODEZOLLMASSNAHMENIMPL t0, LOGASPOIMPL t1
WHERE (t0.myIndexedAttribute = ?)
AND t1.JDOCLASS = ?
AND t0.JDOID = t1.JDOID
[params=(String) DE, (String)
de.logas.zoll.eztneu.CodeZollMassnahmenImpl] [reused=0]
When I execute the same statement from a SQL-prompt, it takes that long as
well, but when I swap the tablenames in the from part
(to "FROM LOGASPOIMPL t1, CODEZOLLMASSNAHMENIMPL t0") the result comes
immediately.
I've had a look at the query plans, oracle creates for the two statements
and found, that our index on myIndexedAttribute is not used
by the first statement, but it is by the second.
How can I make Kodo use the faster statement?
I've tried to use the "jdbc-indexed" tag, but without success so far.
Thanks,
Wolfgang

Thank you very much, Stefan & Alex.
After computing statistics the index is used and the performance is fine
now.
- Wolfgang
Alex Roytman wrote:
ANALYZE TABLE MY_TABLE COMPUTE STATISTICS;
"Stefan" <[email protected]> wrote in message
news:btlqsj$f18$[email protected]..
When I execute the same statement from a SQL-prompt, it takes that longas
well, but when I swap the tablenames in the from part
(to "FROM LOGASPOIMPL t1, CODEZOLLMASSNAHMENIMPL t0") the result comes
immediately.
I've had a look at the query plans, oracle creates for the twostatements
and found, that our index on myIndexedAttribute is not used
by the first statement, but it is by the second.
How can I make Kodo use the faster statement?
I've tried to use the "jdbc-indexed" tag, but without success so far.I know that in DB2 there is a function called "Run Statistics" which you
can (and should do) on all tables involved in a query (at least once a
month, when there are heavy changes in the tables).
On information gathered by this statistics DB2 can optimize your queries
and execution path's
Since I was once involved in query performance optimizing on DB/2 I can
say you can get improvements of 80% on big tables on which statistics are
run and not. (Since the execution plans created by the optimizer differ
heavily)
Since I'm working now with Oracle as well, at least I can say, that Oracle
has a featere like statistics as well. (go into the manager enterprise
Console and click on a table, you will find a row "statisitics last run")
I don't know how to trigger these statistics nor whether they would
influence the query execution path on oracle (thus "swapping" tablenames
by itself), since I didn't have time to do further research on thatmatter.
But it's worth a try to find out and maybe it helps on you problem ?

How to utilize index in selection statement

hi
how to utilize index in selection statement and how is it reduces performance whether another alternative is there to reduce performance .
thanks

Hi Suresh,
For each SQL statement, the database optimizer determines the strategy for accessing data records. Access can be with database indexes (index access), or without database indexes (full table scan).The cost-based database optimizer determines the access strategy on the basis of:
*Conditions in the WHERE clause of the SQL statement
*Database indexes of the table(s) affected
*Selectivity of the table fields contained in the database indexes
*Size of the table(s) affected
*The table and index statistics supply information about the selectivity of table fields, the selectivity of combinations of table fields, and table size. Before a database access is performed, the database optimizer cannot calculate the exact cost of a database access. It uses the information described above to estimate the cost of the database access.The optimization calculation is the amount by which the data blocks to be read (logical read accesses) can be reduced. Data blocks show the level of detail in which data is written to the hard disk or read from the hard disk.
Inroduction to Database Indexes
When you create a database table in the ABAP Dictionary, you must specify the combination of fields that enable an entry within the table to be clearly identified. Position these fields at the top of the table field list, and define them as key fields.
After activating the table, an index is created (for Oracle, Informix, DB2) that consists of all key fields. This index is called a primary index. The primary index is unique by definition. As well as the primary index, you can define one or more secondary indexes for a table in the ABAP Dictionary, and create them on the database. Secondary indexes can be unique or non-unique. Index records and table records are organized in data blocks.
If you dispatch an SQL statement from an ABAP program to the database, the program searches for the data records requested either in the database table itself (full table scan) or by using an index (index unique scan or index range scan). If all fields requested are found in the index using an index scan, the table records do not need to be accessed.
A data block shows the level of detail in which data is written to the hard disk or read from the hard disk. Data blocks may contain multiple data records, but a single data record may be spread across several data blocks.
Data blocks can be index blocks or table blocks. The database organizes the index blocks in the form of a multi-level B* tree. There is a single index block at root level, which contains pointers to the index blocks at branch level. The branch blocks contain either some of the index fields and pointers to index blocks at leaf level, or all index fields and a pointer to the table records organized in table blocks. The index blocks at leaf level contain all index fields and pointers to the table records from the table blocks.
The pointer that identifies one or more table records has a specific name. It is called, for example, ROWID for Oracle databases. The ROWID consists of the number of the database file, the number of the table block, and the row number within the table block.
The index records are stored in the index tree and sorted according to index field. This enables accelerated access using the index. The table records in the table blocks are not sorted.
An index should not consist of too many fields. Having a few very selective fields increases the chance of reusability, and reduces the chance of the database optimizer selecting an unsuitable access path.
Index Unique Scan
If, for all fields in a unique index (primary index or unique secondary index), WHERE conditions are specified with '=' in the WHERE clause, the database optimizer selects the access strategy index unique scan.
For the index unique scan access strategy, the database usually needs to read a maximum of four data blocks (three index blocks and one table block) to access the table record.
select * from VVBAK here vbeln = '00123' ......end select.
In the SELECT statement shown above, the table VVBAK is accessed. The fields MANDT and VBELN form the primary key, and are specified with '=' in the WHERE clause. The database optimizer therefore selects the index unique scan access strategy, and only needs to read four data blocks to find the table record requested.
Index Range Scan
select * from VVBAP here vbeln = '00123' ......end select.
In the example above, not all fields in the primary index of the table VVBAP (key fields MANDT, VBELN, POSNR) are specified with '=' in the WHERE clause. The database optimizer checks a range of index records and deduces the table records from these index records. This access strategy is called an index range scan.
To execute the SQL statement, the DBMS first reads a root block (1) and a branch block (2). The branch block contains pointers to two leaf blocks (3 and 4). In order to find the index records that fulfill the criteria in the WHERE clause of the SQL statement, the DBMS searches through these leaf blocks sequentially. The index records found point to the table records within the table blocks (5 and 6).
If index records from different index blocks point to the same table block, this table block must be read more than once. In the example above, an index record from index block 3 and an index record from index block 4 point to table records in table block 5. This table block must therefore be read twice. In total, seven data blocks (four index blocks and three table blocks) are read.
The index search string is determined by the concatenation of the WHERE conditions for the fields contained in the index. To ensure that as few index blocks as possible are checked, the index search string should be specified starting from the left, without placeholders ('_' or %). Because the index is stored and sorted according to the index fields, a connected range of index records can be checked, and fewer index blocks need to be read.
All index blocks and table blocks read during an index range scan are stored in the data buffer at the top of a LRU (least recently used) list. This can lead to many other data blocks being forced out of the data buffer. Consequently, more physical read accesses become necessary when other SQL statements are executed
DB Indexex :Concatenation
In the concatenation access strategy, one index is reused. Therefore, various index search strings also exist. An index unique scan or an index range scan can be performed for the various index search strings. Duplicate entries in the results set are filtered out when the search results are concatenated.
Select * from vvbap where vbeln in ('00123', '00133', '00134').
endselect.
In the SQL statement above, a WHERE condition with an IN operation is specified over field VBELN. The fields MANDT and VBELN are shown on the left of the primary index. Various index search strings are created, and an index range scan is performed over the primary index for each index search string. Finally, the result is concatenated.
Full Table Scan
select * from vvbap where matnr = '00015'.
endselect
If the database optimizer selects the full table scan access strategy, the table is read sequentially. Index blocks do not need to be read.
For a full table scan, the read table blocks are added to the end of an LRU list. Therefore, no data blocks are forced out of the data buffer. As a result, in order to process a full table scan, comparatively little memory space is required within the data buffer.
The full table scan access strategy is very effective if a large part of a table (for example, 5% of all table records) needs to be read. In the example above, a full table scan is more efficient than access using the primary index.
In Brief
Index unique scan: The index selected is unique (primary index or unique secondary index) and fully specified. One or no table record is returned. This type of access is very effective, because a maximum of four data blocks needs to be read.
Index range scan: The index selected is unique or non-unique. For a non-unique index, this means that not all index fields are specified in the WHERE clause. A range of the index is read and checked. An index range scan may not be as effective as a full table scan. The table records returned can range from none to all.
Full table scan: The whole table is read sequentially. Each table block is read once. Since no index is used, no index blocks are read. The table records returned can range from none to all.
Concatenation: An index is used more than once. Various areas of the index are read and checked. To ensure that the application receives each table record only once, the search results are concatenated to eliminate duplicate entries. The table records returned can range from none to all.
Regards,
Balaji Reddy G
***Rewards if answers are helpful

How to ignore the popup message in TCD mode

Hi All,
I'm relatively new to all this. Could anyone kindly show me how to ignore those pop up message (which requires click 'yes' 'no') during the TCD recording and replay?
The trouble I'm having at the moment is that depending on the effective start date, transaction asks either:
1) Do you want to delimit the existing record in popup window
2) Do you want to delete the existing record in popup window
3) record created - no popup
What I want to achieve is that regardless of any of these messages, I still want the transaction to complete and having data updated.
Many thanks in advance.

Hello,
You can Ignore the message if the message is of following types:
If no message type is given for the rule with this mode in column MSGTYP, all application log messages are ignored.
If a particular message type (A, E, I, S, W, X) is specified, application log messages with exactly this type are ignored. If you want several message types (but not all) to be ignored, specify several rules with this mode and the message type to be ignored in each case
Please refer the below link:
http://help.sap.com/saphelp_nwpi711/helpdata/en/49/6f57112c293b5be10000000a42189b/frameset.htm
Hope the data was useful
Regards,
Swetha

Remove error during impdp

Hi,
How to remove error during import using impdp.
ORA-39082: Object type PACKAGE_BODY:"JISPBILCORBILLINGTST502"."COR_BILL" created with compilation warnings
ORA-39082: Object type VIEW:"JISPBILCORBILLINGTST502"."VWACTUALUNBILLEDUSAGE_CDR" created with compilation warnings
Thanks in advance

ORA-39082: Object type string created with compilation warnings
Cause: The object in the SQL statement following this error was created with compilation errors. If this error occurred for a view, it is possible that the base table of the view was missing.
Action: This is a warning. The object may have to be recompiled before being used.

How to block popups during downloading

how to block popups during downloading

What kind of pop-ups do you get?
Do you mean that you get some kind of alert or do additional Firefox windows open with content?
Do a malware check with a few malware scan programs. 
You need to use all programs because each detects different malware. 
Make sure that you update each program to get the latest version of the database before doing a scan.
* http://www.malwarebytes.org/mbam.php - Malwarebytes' Anti-Malware
* http://www.superantispyware.com/ - SuperAntispyware
* http://www.safer-networking.org/en/index.html - Spybot Search & Destroy
* http://www.lavasoft.com/products/ad_aware_free.php - Ad-Aware Free
* http://www.microsoft.com/windows/products/winfamily/defender/default.mspx - Windows Defender: Home Page
See also "Spyware on Windows": http://kb.mozillazine.org/Popups_not_blocked and [[Searches are redirected to another site]]

How to ignore blank/null key figure value in BI Queries

Reports on Multiprovider - we see some cells of a Key figure as blanks. These blanks are interpreted as zeros by the system and calculated accordingly resulting in incorrect values. As per our requirement, we need a count of all hard/real zeros only, not the blanks. For example, if there are 10 rows of which 6 are real zeros and 4 are blanks - our count should be 6 and not 10.
How to ignore the blanks in BEx queries please?
Thanks for your help.
Upender

Rakesh,
It is not possible to find a pattern because the report is on a MultiProvider with 2 InfoProviders- Purchasing documents DSO and Material Movements InfoCube.
Every Purchasing Document has several materials associated with it. These materials are compared with materials in Materials Movement. Not all materials in Purchasing Document are found in Materials Movement. For those Materials found in Materials Movement, the Quantity is obtained. For these found rows, the correct value is showing up - if the quantity is zero, it is showing in reports as zero. If the material is not found in Material Movements then Quantity shows up as blank values.
My requirement is ignore such blank quantities and not count them. Only Quantities with 0 values should be counted. Currently both blanks and zero values are counted showing inflated count.
Thanks,
Upender

How to specify index for cache in coherence-cache-config.xml

Hi All,
We want to apply indexing on cache data.
Suppose i have a EMPLOYEE object in coherence cache.
and i want to use employeeID for indexing purpose.
Can anybody help me to achieve this at Congregational level i.e. using xml file (coherence-cache-config.xml) .
Edited by: 981644 on Jan 16, 2013 1:51 AM

Hi,
I've posted some [url http://coherence.oracle.com/download/attachments/14647422/add-index-namespace.jar]code and the [url http://coherence.oracle.com/download/attachments/14647422/add-index-namespace-src.jar]source. It depends on coherence common version 2.3.0.39174 however I believe it will work with 2.0.0.23649 also. Coherence common library can be downloaded from [url http://coherence.oracle.com/display/INC10/coherence-common]here
Note: This is purely an example on how to achieve index creation via a cache configuration file and is not a part of the product thus is not covered by product support.
Here is an example cache configuration that uses the namespace:
<cache-config xmlns:service="class://com.oracle.coherence.environment.extensible.ServiceOperations">
 <caching-scheme-mapping>
 <service:index-add cache-name="dist-indexes">
 <extractor>
 <class-name>ReflectionExtractor</class-name>
 <init-params>
 <init-param>
 <param-type>string</param-type>
 <param-value>getName</param-value>
 </init-param>
 </init-params>
 </extractor>
 </service:index-add>
 
 <service:index-add cache-name="dist-indexes" pof-enabled="true">
 <pof-index>8,16,32</pof-index>
 </service:index-add>
 
 <service:index-add cache-name="dist-indexes" pof-enabled="true" enabled="{tangosol.index.add}">
 <pof-index>8,16,31</pof-index>
 </service:index-add>
 
 <service:index-add cache-name="dist-indexes">
 <extractor>
 <class-name>PofExtractor</class-name>
 <init-params>
 <init-param>
 <param-type>{class}</param-type>
 <param-value>null</param-value>
 </init-param>
 <init-param>
 <param-type>{object}</param-type>
 <param-value>
 <class-name>com.tangosol.io.pof.reflect.SimplePofPath</class-name>
 <init-params>
 <init-param>
 <param-type>{int[]}</param-type>
 <param-value>1,2,4</param-value>
 </init-param>
 </init-params>
 </param-value>
 </init-param>
 </init-params>
 </extractor>
 </service:index-add>
 </caching-scheme-mapping>
</cache-config>Thanks,
Harvey

How to ignore zero in select query

select * from EINA where EINAMATNR = yyyy and EINALIFNR = zzzz
In select query, how to ignore zero? for example, EINAMATNR = 0000000yyyy, EINALIFNR=000zzz
Maybe I can use LIKE keyword in sql query. Any other way?
Thanks.

Use the following conversion routines to convert yyyy & zzzz to remove the leading zeros and then pass it to your select query.
For Matnr -> CONVERSION_EXIT_MATN1_INPUT
For LIFNR ->CONVERSION_EXIT_alpha_input.
 CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
 EXPORTING
 input = yyyy
 IMPORTING
 output = t_lifnr.
 CALL FUNCTION 'CONVERSION_EXIT_MATN1_INPUT'
 EXPORTING
 input = zzzz
 IMPORTING
 output = t_matnr.
select * from EINA where EINA~MATNR = t_matnr and EINA~LIFNR = t_lifnr .

How to enforce index in oracle query

Hi all
how to enforce index in oracle query
Regards

Use INDEX hint to force Optimizer to use the specfied index.
You really need to investigate why Optimizer doesn't choose the index. Remember, INDEX SCAN are not always GOOD.
Jaffar

How to view Index fragmentation in sap ecc6 ?

how to view Index fragmentation in sap ecc6 ?

Hi Haimiao,
You can use brtools to get required information. For relevant steps use the link below
https://help.sap.com/saphelp_nw04/helpdata/en/08/5742154ae611d1894f0000e829fbbd/content.htm
Regards,
Deepak Kori

How to ignore the material with error in costing run ck40n

Hi
Pls, advice how to ignore parent material form costing run if the components of that material have errors. I need to run the costing run excluding erroneous parent item. Is any configuration on this..
Pls help..
K

Hi Kesharika Goona...
If you want to exclude any material from Costing Run, there are two ways...
1. Go to Material Master, Costing1 view, take the check box "Do Not Cost". If you opt for this check box, the system will not consider this material for costing.
2. Where you run the standard cost estimate in CK40N, once you save you costing run with the parameters like Costing Variant etc, When you select the "Parameters" agains the Flow step of "Selection", you will be asked to give the inputs like Material Number, Plant etc.
There, against the Material Number, on the extrem right side, you will see a arrow, press that arrow, and there you can see a tab "Exclude Single Values". There you have to give the material number which you want to exclude from the costing run press "Execute" icon on the botoom-left corner of that pop-up window..
If you still face problem, pls revert back
Srikanth Munnaluri

How to Ignore Header Line in FCC " Sender Side" .

Hi SDNrs,
I am getting a File Data after FCC with header Data.
How to Ignore that Header Line coming with actual data...
Like Employeeid , Name , Deptid
So this Employeeid , Name , Deptid is also coming as Data.
Or what approach Should be Used?
Regards
Prabhat Sharma.

Hi,
Use " Document Offset" parameter in Sender File CC.
http://help.sap.com/saphelp_nw04/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm
Thnaks
Amit

How to ignore index during impdp...

Similar Messages

Maybe you are looking for