Unable to create auto-indexing loop tunnel
I am modifying a VI created by someone else, and in the block diagram there is a loop tunnel that is supposed to be auto-indexing. But when I open the file the loop tunnel is non auto-indexing and will not allow me to change it to auto-indexing (when I right click it says "Disable Indexing" but it is light gray and cannot be clicked on). When the same file is opened on another computer the tunnel is auto-indexing and the VI runs without any errors. How can I fix this problem?
Using Labview 2013
This normally happens when you install DAQmx before installing LabVIEW. The DAQmx installer will autodetect what programming language support needs installed. So you do not need to do anything special other than install the drivers after installing LabVIEW.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
Similar Messages
-
Unable to Create database index
Hello All,
I have a table where I'm trying to define indexes.
I make the additional entry for indexes via SE11.
Call transaction SE11.
Enter the table ..
Choose "Change".
Choose "Indexes ...".
Choose the "Create Index" icon and enter the table name and the index name.
However when I goto SE14 to create in the database, ->
Choose "Edit".
Choose "Indexes ...".
Select the index.
Choose continue.
-> Select 'Background' as the processing type.
> Choose "Create database index".
Here, I'm unable to te database index just because it is grayed out.
I tried with user DDIC also.
Can any one help with the reason that I am unable to create it.
Thanks a lot in advance.
Regards,
PradeepHello Pradeep,
Steps to create an Index
1. Goto SE11
2. Enter table name and F6(Change)
3. Select "Indexes" from the Application Tool bar
4. Select "Create Index" Option
5. Select one option
"Non-Unique index"
or
"Unique Index"
In case of a Non-Unique Index, you can use the radio buttons to define whether the index should be created for all database systems, for selected database systems or not at all in the database.
Check the proper Type of the Index in SE11 again. This should solve your problem.
Regards,
Subrahmanya P -
Unable to create spatial index
I have a spatial table called ROAD11
in that table I have a MDSYS.SDO_GEOMETRY column named "GEOMETRY".
after creating that table, I inserted a row, in the USER_SDO_GEOM_METADATA.
Here is what is present in USER_SDO_GEOM_METADATA
SQL> SELECT * FROM USER_SDO_GEOM_METADATA WHERE TABLE_NAME='ROAD11';
ROAD11
GEOMETRY
SDO_DIM_ARRAY(SDO_DIM_ELEMENT('X',0,20000,.000005),SDO_DIM_ELEMENT('Y,0,20000,.000005))
1 row selected
Now when I am trying to create an index on that table with the syntax.
SQL> CREATE INDEX ROAD11 ON ROAD11(GEOMETRY)
INDEXTYPE IS MDSYS.SPATIAL_INDEX;
CREATE INDEX ROAD11 ON ROAD11(GEOMETRY)
ERROR at Line 1:
ORA-29855: error occured in the execution of ODCIINDEXCREATE routine
ORA-13249: internal error in Satial index:[mdidxrbd]
ORA-13249: Error in Spatial index: index build failed
ORA-13249: Error in Spatial index: [mdrcrtxfergm]
ORA-13000: dimension number is out of range
ORA-06512: at "MDSYS.SDO_INDEX_METHOD_9I", line 7
ORA-06512: at line 1
This error is comeing while creating an index.
I am useing Oracle 9i.Please help me out in solving the problem.
Suprabuddha.can you post a sample geometry?
-
Auto-indexing is slow for arrays with 1 dimensions
Hi,
I was looking at the performance of operations on all individual elements in 3D arrays, especially the difference between auto-indexing (left image) and manual-indexing (right image, calling "Index array" and "Replace array subset" in the innermost loop). I'm a bit puzzled by the results and post it here for discussion and hopefully somebody's benefit in the future.
Left: auto-indexing; right: manual-indexing
In the tests I added a different random number to all individual elements in a 3D array. I found that auto-indexing is 1.2 to 1.5 times slower than manual-indexing. I also found that the performance of auto-indexing is much more dependent on the size the dimensions: an array with 1000x200x40 elements is 20% slower than an array with 1000x40x200 elements. For manual-indexing there is hardly any difference. The detailed results can be found at the end of this post.
I was under the impression that auto-indexing was the preferred method for this kind of operation: it achieves exactly the same result and it is much clearer in the block diagram. I also expected that auto-indexing would have been optimized in LabView, but the the tests show this is clearly not the case.
What is auto-indexing doing?
With two tests I looked at how auto-index works.
First, I looked if auto-indexing reorganizes the data in an inefficient way. To do this I made a method "fake-auto-indexing" which calls "Array subset" and "Reshape array" (or "Index array" for a 1D-array) when it enters _every_ loop and calls "Replace array subset" when exiting _every_ loop (as opposed to manual-indexing, where I do this only in the inner loop). I replicated this in a test (calling it fake-auto-indexing) and found that the performance is very similar to auto-indexing, especially looking at the trend for the different array lengths.
Fake-auto-indexing
Second, I looked if Locality of reference (how the 3D array is stored in memory and how efficiently you can iterate over that) may be an issue. Auto-indexing loops over pages-rows-columns (i.e. pages in the outer for-loop, rows in the middle for-loop, columns in the inner for-loop). This can't be changed for auto-indexing, but I did change it for manual and fake-indexing. The performance of manual-indexing is now similar to auto-indexing, except for two cases that I can't explain. Fake-auto-indexing performs way worse in all cases.
It seems that the performance problem with auto-indexing is due to inefficient data organization.
Other tests
I did the same tests for 1D and 2D arrays. For 1D arrays the three methods perform identical. For 2D arrays auto-indexing is 15% slower than manual-indexing, while fake-auto-indexing is 8% slower than manual-indexing. I find it interesting that auto-indexing is the slowest of the three methods.
Finally, I tested the performance of operating on entire columns (instead of every single element) of a 3D array. In all cases it is a lot faster than iterating over individual elements. Auto-indexing is more than 1.8 to 3.4 times slower than manual-indexing, while fake-auto-indexing is about 1.5 to 2.7 times slower. Because of the number of iterations that has to be done, the effect of the size of the column is important: an array with 1000x200x40 elements is in all cases much slower than an array with 1000x40x200 elements.
Discussion & conclusions
In all the cases I tested, auto-indexing is significantly slower than manual-indexing. Because auto-indexing is the standard way of indexing arrays in LabView I expected the method to be highly optimized. Judging by the tests I did, that is not the case. I find this puzzling.
Does anybody know any best practices when it comes to working with >1D arrays? It seems there is a lack of documentation about the performance, surprising given the significant differences I found.
It is of course possible that I made mistakes. I tried to keep the code as straightforward as possible to minimize that risk. Still, I hope somebody can double-check the work I did.
Results
I ran the tests on a computer with a i5-4570 @ 3.20 GHz processor (4 cores, but only 1 is used), 8 GB RAM running Windows 7 64-bit and LabView 2013 32-bit. The tests were averaged 10 times. The results are in milliseconds.
3D-arrays, iterate pages-rows-columns
pages x rows x cols : auto manual fake
40 x 200 x 1000 : 268.9 202.0 268.8
40 x 1000 x 200 : 276.9 204.1 263.8
200 x 40 x 1000 : 264.6 202.8 260.6
200 x 1000 x 40 : 306.9 205.0 300.0
1000 x 40 x 200 : 253.7 203.1 259.3
1000 x 200 x 40 : 307.2 206.2 288.5
100 x 100 x 100 : 36.2 25.7 33.9
3D-arrays, iterate columns-rows-pages
pages x rows x cols : manual fake
40 x 200 x 1000 : 277.6 457
40 x 1000 x 200 : 291.6 461.5
200 x 40 x 1000 : 277.4 431.9
200 x 1000 x 40 : 452.5 572.1
1000 x 40 x 200 : 298.1 460.4
1000 x 200 x 40 : 460.5 583.8
100 x 100 x 100 : 31.7 51.9
2D-arrays, iterate rows-columns
rows x cols : auto manual fake
200 x 20000 : 123.5 106.1 113.2
20000 x 200 : 119.5 106.1 115.0
10000 x 10000 : 3080.25 2659.65 2835.1
1D-arrays, iterate over columns
cols : auto manual fake
500000 : 11.5 11.8 11.6
3D-arrays, iterate pages-rows, operate on columns
pages x rows x cols : auto manual fake
40 x 200 x 1000 : 83.9 23.3 62.9
40 x 1000 x 200 : 89.6 31.9 69.0
200 x 40 x 1000 : 74.3 27.6 62.2
200 x 1000 x 40 : 135.6 76.2 107.1
1000 x 40 x 200 : 75.3 31.2 68.6
1000 x 200 x 40 : 133.6 71.7 108.7
100 x 100 x 100 : 13.0 5.4 9.9
VI's
I attached the VI's I used for testing. "ND_add_random_number.vi" (where N is 1, 2 or 3) is where all the action happens, taking a selector with a method and an array with the N dimensions as input. It returns the result and time in milliseconds. Using "ND_add_random_number_automated_test.vi" I run this for a few different situations (auto/manual/fake-indexing, interchanging the dimensions). The VI's starting with "3D_locality_" are used for the locality tests. The VI's starting with "3D_norows_" are used for the iterations over pages and columns only.
Attachments:
3D_arrays_2.zip 222 KBRobert,
the copy-thing is not specific for auto-indexing. It is common for all tunnels. A tunnel is first of all a unique data space.
This sounds hard, but there is an optimization in the compiler trying to reduce the number of copies the VI will create. This optimization is called "in-placeness".
The in-placeness algorithm checks, if the wire passing data to the is connected to anything else ("branch"). If there is no other connection then the tunnel, chance is high that the tunnel won't create an additional copy.
Speaking of loops, tunnels always copies. The in-placeness algorithm cannot opt that out.
You can do a small test to elaborate on this: Simply wire "0" (or anything less than the array sizy of the input array) to the 'N' terminal.......
Norbert
PS: Auto-indexing is perfect for a "by element" operation of analysis without modification of the element in the array. If you want to modify values, use shift registers and Replace Array Subset.
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it. -
Dear all,
In one of the CLAD sample exams the question is as follows:
Auto-indexing at loop boundary is a feature that allows: (more than one answer may apply)
a. Arrays to be automatically traversed from one iteration to the next
b. Array functions to automatically index array elements
c. Functions that use arrays to automatically index them
d. Arrays to be automatically accumulated at loop boundaries
I thought B and D are correct, however according to the sample exam the correct answers are A and D. The justification given is "Auto-indexing is a feature for loops interacting with arrays. Array functions themselves do not have iterative auto-indexing features.". I thought A relates to shift registers?
Thank you in advanceJeff·Þ·Bohrer wrote:
While a bit missleading in wording A is correct Auto indexing input tunnels traverses the row index of an array such that row i is on the wire inside the loop. Shift registers and feedback nodes cannot auto index. Those nodes pass data between loop iterations
I have to disagree with you Jeff. The sentence says traverse arrays from one iteration to the next. The arrays are not being passed on to the next iteration. The rows are being indexed, not moved on to the next iteration.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions -
Convert "1D array of dynamic data" to "Dynamic data" after auto-indexing with loop
Hi -
I have a question about how exaclty auto-indexing works with the Dynamic Data type when exiting a while loop. I'd like to use the DAQ assistant to record data through an analog input (on the MyDAQ) and then replay that data through an analog output. This works fine if I use the DAQ Assistant to record data for a set amount of time:
However, I run into trouble when I try to use a While loop with a stop button to record data for an arbitrary amount of time. I set the dynamic data tunnel out of the While loop to "Indexing", but then when it exits the loop, it becomes "1-D Array of Dynamic Data" instead of just "Dynamic Data", and get a broken wire when I try to connect it to the input of the DAQ Assistant. I've also tried converting the dynamic data to Array and Waveform data types inside the loop, but have the same issue (they become 2D Array and 2D Array of Waveform respectively when leaving the loop). Try as I might using blocks like Convert to/from Dynamic Data Type, or Array Subset, I'm unable to get them back down to just Dynamic Data or Waveform, which will be accepted by the DAQ Assistant:
One other small note - I'm not sure if using the "Build Array" function with a shift register accomplishes exactly the same thing as just auto-indexing an array out of the loop - so I've tried both, but still have the broken wire issue.
I'm assuming this is just a simple issue of using the right block to convert "1D Array of [Something]" to just plain [Something]. Any help appreciated.
Attachments:
PWM_FlatSequence.vi 101 KB
PWM_FlatSequence_While.vi 129 KBI have been facing problem for all temperature values placing the Write to Measurement File outside the Loop.
In Error message it says" Source: 1D array of dynamic data and Sink: Dynamic data".
Is there any means of convering 1D array of dynamic data to dynamic data?
I would highly appreciate any help.
Attachments:
Temperature Logger.vi 110 KB -
Creating an array without using "auto-indexing"
Hello,
it is terrible! I'm new in working with LV5.0 (Evaluation) and I can't
find any examples how to write data into an array without using the
function "auto-indexing" of the "WHILE" or "FOR"-loops..
The values do not appear all at the same time, so I can't use the
"create_array" function.
So I want to "collect" all occured values and then write them e.g. in a
file.
Did I miss anything in the description ???
Who can help me?
Thanks, CHZCHZ wrote in message news:[email protected]..
> Hello,
> it is terrible! I'm new in working with LV5.0 (Evaluation) and I can't
> find any examples how to write data into an array without using the
> function "auto-indexing" of the "WHILE" or "FOR"-loops..
> The values do not appear all at the same time, so I can't use the
> "create_array" function.
> So I want to "collect" all occured values and then write them e.g. in a
> file.
The "Create array" function can be configured to take arrays as well as
elements. You have to use a loop that iterates as often as necessary,
checking for new data. When it receives new data, it adds the new data to
the existing array. It's probably easier to attach a small example than to
describe it in more
detail.
[Attachment Array.zip, see below]
Attachments:
Array.zip 10 KB -
Using auto-indexing tunnels to write data files?
Hi,
I am using ni-motion controller to control a servo motor and collect position and torque data. I want to write the collected data to TDMS files.
Recently I learned about the producer/consumer design pattern and I figured that would be a good approach to ensure that writing the files didn't slow down my data collection timed loop.
However, I also figured out that my program seems to run well if I wire the data I collect to auto-indexing tunnels. Then I use a structure that only executes after all the data collection is done to write the arrays I built to TDMS files.
Is there any reason that the latter method would be advised against? Can the auto idexing tunnels slow down my loop enough for it cause concern? I am only collecting about 5000 data points for each channel.
Cheers,
Kenny
Solved!
Go to Solution.Well, autoindexing tunnels don't write data files, they just accumulate data until the loop completes. If this is a FOR loop with a known number of iterations, the size of the output data can be allocated in one swoop, which is very efficient. If you are autoindexing on a WHILE loop, the final array size is not known, so LabVIEW needs to make a guess and and requires occasional new memory allocations whenever the last guess is exceeded. This is inefficient.
One problem with these approaches is if the program or computer crashes. In this case the data in the shift register is lost forever, while if you would stream it to disk, you would have most of the data acquired so far.
If you use a proper producer/consumer architecture, you should be able to asynchronously write the data and it will not slow down your acquisition. No need ot wait for the competion of data gathering.
LabVIEW Champion . Do more with less code and in less time . -
Unable to create the Rule Index (SEM_APIS.CREATE_RULES_INDEX) getting error
Hi,
I am trying to create the Rule Index with the below script its giving the temp table space error.
The number of records in that specific table is 17473708 (17+ M) and the available temp space is 120GB.
Execute SEM_APIS.CREATE_RULEBASE('ecc_md_rb')
--Insert to mdsys.semr_ecc_md_rb Values(.............)
BEGIN
SEM_APIS.CREATE_RULES_INDEX(
'ecc_rule_indx',
SEM_Models('FOUNDATION'),
SEM_Rulebases('RDFS','ecc_dm_rb'));
END;
Create rule index statement is running more than 8hrs and i tried with the sem_apis.create_entailment its also giving the same Temp table space error.
Please find the below error details
BEGIN sem_apis.create_entailment('ecc_rule_inx', sem_models('FOUNDATION'), sem_rulebases('OWLPRIME','ecc_dm_rb'),SEM_APIS.REACH_CLOSURE,'RDFS2-, RDFS3-, RDFS4a-, RDFS4b-, RDFS5-, RDFS6-, RDFS7-, RDFS8-, RDFS9-, RDFS10-, RDFS11-, RDFS12-, RDFS13-','USER_RULES=T'); END;
Error at line 1
ORA-29532: Java call terminated by uncaught Java exception: oracle.jdbc.driver.OracleSQLException: ORA-01652: unable to extend temp segment by 64 in tablespace TEMP
ORA-06512: at "MDSYS.SDO_SEM_INFERENCE";, line 4866
ORA-06512: at "MDSYS.RDF_APIS";, line 16
ORA-06512: at line 1
Please Help me to create rule index.
Note: I am using Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
Regards,
Kavitha.Hi,
Please use the create_entailment API.
As far as temp tablespace goes, please create a bigfile temp tablespace. You can follow Slide #36 of the
following document.
http://download.oracle.com/otndocs/tech/semantic_web/pdf/2010_ora_semtech_wkshp.pdf
Thanks,
Zhe Wu -
Unable to create Indexes on F table
Hi
We are unable to create Indexes on one of our Cube's fact table...I tried creating with Process chain , Batch and also tried with SE11 ...table name ... Indexes ...Activate...
Its showing active object generated but the warning msg Index does not exist in database system MSSQL still exist and not creating indexes...When I activate the indexes its not showing this warning for all other cubes...Please advice
regardsHi Sam,.
The index creation on F table is taken care by the system itself. When you activate the cube, the DIM and F table are created and at the same time, indexes are created.
To create your own indes, though, go to se11...>F Table name-->Indeexes-it will show you system created indexes.
There will be a create sign....click there... and give the name of the index(like 1, 2). It will open up the maintain index page, where you have to mention all the parameter.
Thanbks...
Shambhu -
I am running an SQL(CE) script to create a DB. All script commands succeed, but the DB get "broken" after creating the last costaint: after running the script, viewing table properties of Table2 and clicking on "Manage relations" gives the following error: Unable to create foreign key: InvalidArgument=Value of '0' is not valid for 'index'. Parameter name: index. Wondering what does that refer to...
Here it is the script. Please note that no error is thrown by running the following queries (even from code that passing the queries by hand, one-by-one to sql server management studio).
CREATE TABLE [table1] (
[id_rubrica] numeric(18,0) NOT NULL
, [id_campo] numeric(18,0) NOT NULL
, [nome] nvarchar(100) NOT NULL
GO
ALTER TABLE [table1] ADD PRIMARY KEY ([id_rubrica],[id_campo]);
GO
CREATE UNIQUE INDEX [UQ__m_campi] ON [table1] ([id_campo] Asc);
GO
CREATE TABLE [table2] (
[id_campo] numeric(18,0) NOT NULL
, [valore] nvarchar(4000) NOT NULL
GO
ALTER TABLE [table2] ADD PRIMARY KEY ([id_campo],[valore]);
GO
ALTER TABLE [table2] ADD CONSTRAINT [campo_valoriFissi] FOREIGN KEY ([id_campo]) REFERENCES [table1]([id_campo]);
GO
Sid (MCP - http://www.sugata.eu)I know this is kind of old post, but did this realy solved your problem?
I'm getting this same error message after adding a FK constraint via UI on VS2008 Server Explorer.
I can add the constraint with no errors, but the constraint is not created on the DataSet wizard (strongly typed datasets on Win CE 6) and when I click "Manage Relations" on the "Table Properties" this error pop out:
"InvalidArgument=Value or '0' is not valid for 'index'.
Parameter name: index"
Even after vreating my table with the relation in SQL the same occurs:
CREATE TABLE pedidosRastreios (
idPedidoRastreio INT NOT NULL IDENTITY PRIMARY KEY,
idPedido INT NOT NULL CONSTRAINT FK_pedidosRastreios_pedidos REFERENCES pedidos(idPedido) ON DELETE CASCADE,
codigo NVARCHAR(20) NOT NULL -
Unable to create index ..can anyone help me
Dan,
I have created the following table and the values are as following,
create table zonetemp(
name varchar2(15),
SHAPE MDSYS.SDO_GEOMETRY)
insert into zonetemp values('Raju',
MDSYS.SDO_GEOMETRY(2003,null,null,
MDSYS.SDO_ELEM_INFO_ARRAY(1,1003,3),
MDSYS.SDO_ORDINATE_ARRAY(10,30,40,10)))
insert into zonetemp values('Kalpan',
MDSYS.SDO_GEOMETRY(2003,null,null,
MDSYS.SDO_ELEM_INFO_ARRAY(1,1003,3),
MDSYS.SDO_ORDINATE_ARRAY(0,20,40,0)))
insert into zonetemp values('Chetan',
MDSYS.SDO_GEOMETRY(2003,null,null,
MDSYS.SDO_ELEM_INFO_ARRAY(1,1003,3),
MDSYS.SDO_ORDINATE_ARRAY(0,40,40,20)))
commit
I am unable to index the table.
exec geocoder_http.setup_locator_index('ZONETEMP','SHAPE');
ERROR at line 1:
ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-13219: failed to create spatial index table [ZONET_SHAPE_IDX_HL13N1$]
ORA-06512: at "MDSYS.SDO_INDEX_METHOD", line 7
ORA-06512: at line 1
ORA-06512: at "MDSYS.GEOCODER_HTTP", line 168
ORA-06512: at line 1
My Query :
SELECT NAME FROM ZONETEMP A
WHERE SDO_FILTER(A.SHAPE,MDSYS.SDO_GEOMETRY(2001,null,MDSYS.SDO_POINT_TYPE(20,20, 0), NULL, NULL)),'QUERYTYPE='WINDOW') ='TRUE'
Basically these gemoteries are polygon.
what i want to do is query this table with the operator SDO_FILTER with reference geomotry as POINT and find the corresponding polygon in which it is found.
Is it Possible?Is this a valid Query?
N.B for the ploygon definations one can asssume a gird layout of 40*40.
nullHi Raju,
There are a few things I would change below.
The first is that optimized rectangles (which you are using) need to be specified as lower left then upper right, assuming the lowest values are in the lower left corner of the coordinate system.
The way you've specified them is upper left, lower right which will not work.
The second thing I would change is your create index statement. You shouldn't be using locater to create the index - locator is a separate product should be used only with point geometries.
Your create index statement should look something like this:
create index zonetemp_sidx on zonetemp(shape)
indextype is mdsys.spatial_index
parameters ('sdo_level=NN');
where NN above is an integer number representing the tiling level you are going to use for the index. This is workload dependent, but I will give you a range of 8-12 to start with - you can protype using real data and figure out what gives you the best performance - if it is 12 you may want to go higher.
Also, you will have had to preload user_sdo_geom_metadata.
Finally, your query looks good, although I would change it slightly to set the third ordinate to NULL rather than 0, i.e.:
SELECT NAME
FROM ZONETEMP A
WHERE SDO_FILTER (A.SHAPE,
MDSYS.SDO_GEOMETRY(2001,null,
MDSYS.SDO_POINT_TYPE(20,20,NULL),
NULL, NULL)),'QUERYTYPE='WINDOW')
='TRUE'
Hope this helps,
dan -
Array Size doesn't work correctly after "Auto-indexed Tunnel"
Array Size returns value even if Empty Array is detected after "Auto-indexed Tunnel" tha generates 2D array.
See example + VI with correct output as I expected.
OR
There is problem with generating 2D array --- It's empty. 1D array is generated in right way. 100 x 0 but not Emptu Array.
Attachments:
ArraySize_Bug.vi 9 KB
ArraySize_Corrected.vi 19 KBNot a bug. This is correct behavior that is consistent with other parts of LabVIEW.
The decision to handle multi-dimensional arrays like this was made long ago and is an enshrined part of the LabVIEW language spec. It will not be changed. -
IDES system copy ..error during IMPORT_ABAP..unable to create indexes
Hi all,
I am doing a IDES system copy. I ran the report SMIGR_CREATE_DLL , the export activities have been completed successfully as well on the source system. Now on the target system, during the import, I am getting the following error in the log file SAPDFACT.log.
(DB) ERROR: DDL statement failed
(CREATE INDEX "/BI0/E0RSTT_C06~P" ON "/BI0/E0RSTT_C06" ( "KEY_0RSTT_C06P" , "KEY_0RSTT_C06T" , "KEY_0RSTT_C06U" , "KEY_0RSTT_C061" , "KEY_0RSTT_C062" , "KEY_0RSTT_C063" , "KEY_0RSTT_C064" , "KEY_0RSTT_C065" , "KEY_0RSTT_C066" , "KEY_0RSTT_C067" , "KEY_0RSTT_C068" ) TABLESPACE PSAPSR3 STORAGE (INITIAL 65536 NEXT 0000002560K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) NOLOGGING COMPUTE STATISTICS )
DbSlExecute: rc = 99
(SQL error 1408)
error message returned by DbSl:
ORA-01408: such column list already indexed
(DB) INFO: disconnected from DB
The owner for this table is SAPSR3. Some oracle forums suggested to drop the index before recreating it. But when i do "drop index SAPSR3."/BI0/E0RSTT_C06~P..it says.."the specified index does not exist". But when I go to recreate this index, it doesn get created successfully. After that when I re-run the import, it again fails. Suprisingly..now if i go to check if this index is present thru a sql querry:
select owner, object_name, object_type from dba_objects where object_name='SAPSR3."/BI0/E0RSTT_C06~P"', it tells "no rows selected". This is happening everytime, I create an index, where it gets created successfully, and the import again fails with the same error in SAPDFACT.log.
I found an SAP note 885441 named..common errors during migration..although mine isnt a migration..my both source and destination are Red hat 64 bit platform.
The note 1st asks to download the latest R3load..which I did and extracted in the kernel directory of the source..then it also asked to edit the .TSK file..in my case..SAPDFACT.TSK..where the lines:
I /BIC/E<Cubename>~<index> C err
to I /BIC/E<Cubename>~<index> C ign..
I did that..this time..the import again fails..but in the SAPDFACT.log..it complains about some other index..n the same gets generated in the .TSK file as well..the earlier index error is not again generated.
I am not sure..what is going wrong..my export went through successfully.i have done the prep steps for export as well..before that i ran the SMIGR_CREATE_DLL report as well..
Any inputs are highly appreciated..
Thanks,
AkshayHi,
Check SAP Note 1166589 - Table converter: DB error when creating secondary indexes
Thanks
Sunny -
Unable to create a bitmap index
Hi,
I want to create a bitmap index on one of the colums on a table. I fired following query and it failed.
SQL> CREATE BITMAP INDEX TRANS_N_BITMAPIDX_VEH_PLATFORM ON TRANSACTION_NEW(VEH_PLATFORM) LOCAL;
Error starting at line 2 in command:
CREATE BITMAP INDEX TRANS_N_BITMAPIDX_VEH_PLATFORM ON TRANSACTION_NEW(VEH_PLATFORM) LOCAL
Error at Command Line:2 Column:70
Error report:
SQL Error: ORA-01408: such column list already indexed
01408. 00000 - "such column list already indexed"
*Cause:
*Action:I found there is a combined NORMAL index with VEH_PLATFORM column called ‘IDX$$_30AA00021’. It has following columns
• VEH_PLATFORM
• VEH_MODEL
• MODL_YR_NBR
• VEH_MAKE
• TXN_PROCS_DT
But I was able to create bitmap index on VEH_MODEL,MODL_YR_NBR and VEH_MAKE columns without any error.
Why does it error out for VEH_PLATFORM column?
Regards,
SamHi,
I am sure that BITMAP index is only created for
VEH_MAKE
VEH_MODEL
MODL_YR_NBR
BUILD_REGION
VEH_LINE_SERIES
TRANS_CTG_ID
and not for VEH_PLATFORM.
SQL> SELECT * FROM USER_INDEXES WHERE INDEX_TYPE='BITMAP' AND TABLE_NAME='TRANSACTION_NEW';
INDEX_NAME INDEX_TYPE TABLE_OWNER TABLE_NAME TABLE_TYPE UNIQUENESS COMPRESSION PREFIX_LENGTH TABLESPACE_NAME INI_TRANS MAX_TRANS INITIAL_EXTENT NEXT_EXTENT MIN_EXTENTS MAX_EXTENTS PCT_INCREASE PCT_THRESHOLD INCLUDE_COLUMN FREELISTS FREELIST_GROUPS PCT_FREE LOGGING BLEVEL LEAF_BLOCKS DISTINCT_KEYS AVG_LEAF_BLOCKS_PER_KEY AVG_DATA_BLOCKS_PER_KEY CLUSTERING_FACTOR STATUS NUM_ROWS SAMPLE_SIZE LAST_ANALYZED DEGREE INSTANCES PARTITIONED TEMPORARY GENERATED SECONDARY BUFFER_POOL FLASH_CACHE CELL_FLASH_CACHE USER_STATS DURATION PCT_DIRECT_ACCESS ITYP_OWNER ITYP_NAME PARAMETERS GLOBAL_STATS DOMIDX_STATUS DOMIDX_OPSTATUS FUNCIDX_STATUS JOIN_INDEX IOT_REDUNDANT_PKEY_ELIM DROPPED VISIBILITY DOMIDX_MANAGEMENT SEGMENT_CREATED
TRANS_N_BITMAPIDX_MAKE BITMAP VISUAL TRANSACTION_NEW TABLE NONUNIQUE DISABLED 2 6102 20 305 611 12226 N/A 12226 2208 11-MAY-11 1 1 YES N N N DEFAULT DEFAULT DEFAULT NO YES NO NO NO VISIBLE N/A
TRANS_N_BITMAPIDX_MODEL BITMAP VISUAL TRANSACTION_NEW TABLE NONUNIQUE DISABLED 2 11284 158 71 144 22813 N/A 22813 2321 11-MAY-11 1 1 YES N N N DEFAULT DEFAULT DEFAULT NO YES NO NO NO VISIBLE N/A
TRANS_N_BITMAPIDX_BUILD_REGION BITMAP VISUAL TRANSACTION_NEW TABLE NONUNIQUE DISABLED 2 2911 5 582 1161 5808 N/A 5808 5808 11-MAY-11 1 1 YES N N N DEFAULT DEFAULT DEFAULT NO YES NO NO NO VISIBLE N/A
TRANS_N_BITMAPIDX_MODL_YR_NBR BITMAP VISUAL TRANSACTION_NEW TABLE NONUNIQUE DISABLED 2 2911 5 582 1161 5808 N/A 5808 5808 11-MAY-11 1 1 YES N N N DEFAULT DEFAULT DEFAULT NO YES NO NO NO VISIBLE N/A
TRANS_N_BITMAPIDX_TRANS_CTG_ID BITMAP VISUAL TRANSACTION_NEW TABLE NONUNIQUE DISABLED 2 7547 43 175 359 15457 N/A 15457 2345 11-MAY-11 1 1 YES N N N DEFAULT DEFAULT DEFAULT NO YES NO NO NO VISIBLE N/A
TRANS_N_BITMAPIDX_VEH_LINE_S BITMAP VISUAL TRANSACTION_NEW TABLE NONUNIQUE DISABLED 2 10581 253 41 84 21477 N/A 21477 2247 11-MAY-11 1 1 YES N N N DEFAULT DEFAULT DEFAULT NO YES NO NO NO VISIBLE N/A
6 rows selectedRegards,
Sam
Maybe you are looking for
-
Need help with backup for iphone 4
hey all, i just upgraded to IOS 5.1.1, and i was pretty mad to find out all my contacts were wiped out after i did this. so i plugged it in my computer, went into iTunes, and tried to restore from backup...well, that would have worked out fine, excep
-
Create Records through OData using Jquery
Hi All, I have created a OData Service in SAP ECC system in format http://hostname:portno/sap/opu/odata/sap/Z_PORDER_SRV/PurchaseOrderHeaderCollection I am trying to create a record from front end using JQuery. I am able to retrieve all the records
-
Hi All, We have many hundreds of A/R accounts with balanaces in excess of 365 days where the balances can be measured in pennies. Manually writing these off is far too time consuming. Is it possible to MASS write off. Thanks for your help. I guess "
-
Anybody using Batch Job Monitoring?
Hi Team, Looking for some Solman BPM Batch Job monitoring help with the "job not started" monitor. It's not detecting the alerts. Thanks, Milton
-
ITunes 10.7.0.21 smart playlist last skipped not updating
This is the playlist which I have. Any song which I play get removed(as expected) once when it finishes. But songs which I skip still remain in the playlist. Despite me having a rule saying Last Skipped not in last 30 days. This is driving me nuts! I