Create unique index on flow table

Hi
I always get this error 'Create unique index on flow table ERROR" while implementing SCD2. Please help me.I have made an Update Key which is a combination of 4 columns that want a new row to be inserted if there is a change in data.One of the above columns is the EMPLOYEE ID,
My surrogate key is the table's primary key but I have not defined it as a key in mapping and also I have turned off the Primary Key Constraint Option in Controls Panel as NO.
Where am I wrong? Also please tell me what to take care off while making Natural Key ?

There are two solutions:
1. Only use uppercase in the table name
2. go in Topology>Physical Architecture and edit the technology, then click on
the "Language" tab and set "Object Delimiter" to empty.
Thanks,
Sutirtha

Similar Messages

Create Unique Index On Flow does not work for table names 23 characters

I have a "create unique index on flow table" step that is dynamically generated by the IKM.
The index name that is generated by the IKM is based on the table name except that the created index name is prefixed with "I$_" and ends with "_idx". Obviously, since Oracle table names can not exceed 30 characters in length, the index creation step will fail if the base table name exceeds 23 characters.
I have tried to substring the index name generation step in the IKM so that it only uses the first 23 characters of the table name, but have not had any luck with using the "substring" command together with snpRef.getTable call.
This is the section of the IKM that I desire to change:
- <Field name="Txt" type="java.lang.String">
- <![CDATA[
create unique index      <%=snpRef.getTable("L","INT_NAME","W")%>_idx
on          <%=snpRef.getTable("L","INT_NAME","W")%> (<%=snpRef.getColList("", "[COL_NAME]", ", ", "", "UK")%>)
<%=snpRef.getUserExit("FLOW_TABLE_OPTIONS")%>
]]>
</Field>
I would like to change the above to something similar to the following (note the only change is the addition of substring(1,23))
- <Field name="Txt" type="java.lang.String">
- <![CDATA[
create unique index <%=snpRef.getTable("L","INT_NAME","W")*.substring(1,23)*%_idx
on          <%=snpRef.getTable("L","INT_NAME","W")%> (<%=snpRef.getColList("", "[COL_NAME]", ", ", "", "UK")%>)
<%=snpRef.getUserExit("FLOW_TABLE_OPTIONS")%>
]]>
</Field>
Any help greatly appreciated. Thanks.

As the index is temporary, just like the I$ talbel, the easiest way is to replace the table name with some unique identifier like the session is:
bq. I$_<%=odiRef.getSession("SESS_NO")%>_idx
If for some reason that is not unique enough, add the NNO:
bq. I$_<%=odiRef.getSession("SESS_NO")%><%=odiRef.getSession("NNO")%> \\ _idx

ERROR ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found

Hi,
SAPSSRC.log
C:\usr\sap\BW1\SYS\exe\run/R3load.exe: START OF LOG: 20071018195059
C:\usr\sap\BW1\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#12 $ SAP
C:\usr\sap\BW1\SYS\exe\run/R3load.exe: version R6.40/V1.4
Compiled Nov 30 2005 20:41:21
C:\usr\sap\BW1\SYS\exe\run/R3load.exe -ctf I C:/temp/51030721/EXP2/DATA/SAPSSRC.STR C:\Program Files\sapinst_instdir\NW04\SYSTEM\ABAP\ORA\NUC\DB/DDLORA.TPL C:\Program Files\sapinst_instdir\NW04\SYSTEM\ABAP\ORA\NUC\DB/SAPSSRC.TSK ORA -l C:\Program Files\sapinst_instdir\NW04\SYSTEM\ABAP\ORA\NUC\DB/SAPSSRC.log
C:\usr\sap\BW1\SYS\exe\run/R3load.exe: job completed
C:\usr\sap\BW1\SYS\exe\run/R3load.exe: END OF LOG: 20071018195059
C:\usr\sap\BW1\SYS\exe\run/R3load.exe: START OF LOG: 20071018195133
C:\usr\sap\BW1\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#12 $ SAP
C:\usr\sap\BW1\SYS\exe\run/R3load.exe: version R6.40/V1.4
Compiled Nov 30 2005 20:41:21
C:\usr\sap\BW1\SYS\exe\run/R3load.exe -dbcodepage 4103 -i C:\Program Files\sapinst_instdir\NW04\SYSTEM\ABAP\ORA\NUC\DB/SAPSSRC.cmd -l C:\Program Files\sapinst_instdir\NW04\SYSTEM\ABAP\ORA\NUC\DB/SAPSSRC.log -stop_on_error
DbSl Trace: ORA-1403 when accessing table SAPUSER
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): WE8DEC
(DB) INFO: ABTREE created #20071018195134
(IMP) INFO: import of ABTREE completed (39 rows) #20071018195134
(DB) INFO: ABTREE~0 created #20071018195134
(DB) INFO: AKB_CHKCONF created #20071018195134
(IMP) INFO: import of AKB_CHKCONF completed (0 rows) #20071018195134
(DB) INFO: AKB_CHKCONF~0 created #20071018195134
(DB) INFO: AKB_INDX created #20071018195134
(IMP) INFO: import of AKB_INDX completed (0 rows) #20071018195134
(DB) INFO: AKB_INDX~0 created #20071018195134
(DB) INFO: AKB_USAGE_INFO created #20071018195134
(IMP) INFO: import of AKB_USAGE_INFO completed (0 rows) #20071018195134
(DB) INFO: AKB_USAGE_INFO~0 created #20071018195134
(DB) INFO: AKB_USAGE_INFO2 created #20071018195134
(IMP) INFO: import of AKB_USAGE_INFO2 completed (0 rows) #20071018195134
(DB) INFO: AKB_USAGE_INFO2~0 created #20071018195134
(DB) INFO: APTREE created #20071018195134
(IMP) INFO: import of APTREE completed (388 rows) #20071018195134
(DB) INFO: APTREE~0 created #20071018195134
(DB) INFO: APTREE~001 created #20071018195134
(DB) INFO: APTREET created #20071018195134
(IMP) INFO: import of APTREET completed (272 rows) #20071018195134
DbSl Trace: Error in exec_immediate()
DbSl Trace: ORA-1452 occurred when executing SQL statement (parse error offset=35)
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "APTREET~0" ON "APTREET" ( "SPRAS", "ID", "NAME" ) TABLESPACE PSAPBW1 STORAGE (INITIAL 44981 NEXT 0000000040K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) )
DbSlExecute: rc = 99
(SQL error 1452)
error message returned by DbSl:
ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found
(DB) INFO: disconnected from DB
C:\usr\sap\BW1\SYS\exe\run/R3load.exe: job finished with 1 error(s)
C:\usr\sap\BW1\SYS\exe\run/R3load.exe: END OF LOG: 20071018195134
C:\usr\sap\BW1\SYS\exe\run/R3load.exe: START OF LOG: 20071018195314
C:\usr\sap\BW1\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#12 $ SAP
C:\usr\sap\BW1\SYS\exe\run/R3load.exe: version R6.40/V1.4
Compiled Nov 30 2005 20:41:21
C:\usr\sap\BW1\SYS\exe\run/R3load.exe -dbcodepage 4103 -i C:\Program Files\sapinst_instdir\NW04\SYSTEM\ABAP\ORA\NUC\DB/SAPSSRC.cmd -l C:\Program Files\sapinst_instdir\NW04\SYSTEM\ABAP\ORA\NUC\DB/SAPSSRC.log -stop_on_error
DbSl Trace: ORA-1403 when accessing table SAPUSER
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): WE8DEC
(DB) ERROR: DDL statement failed
(DROP INDEX "APTREET~0")
DbSlExecute: rc = 103
(SQL error 1418)
error message returned by DbSl:
ORA-01418: specified index does not exist
(IMP) INFO: a failed DROP attempt is not necessarily a problem
DbSl Trace: Error in exec_immediate()
DbSl Trace: ORA-1452 occurred when executing SQL statement (parse error offset=35)
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "APTREET~0" ON "APTREET" ( "SPRAS", "ID", "NAME" ) TABLESPACE PSAPBW1 STORAGE (INITIAL 44981 NEXT 0000000040K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) )
DbSlExecute: rc = 99
(SQL error 1452)
error message returned by DbSl:
ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found
(DB) INFO: disconnected from DB
C:\usr\sap\BW1\SYS\exe\run/R3load.exe: job finished with 1 error(s)
C:\usr\sap\BW1\SYS\exe\run/R3load.exe: END OF LOG: 20071018195315
I'm getting this error "duplicate keys found". I'm finished installing the central instance and during the database instance, i got this error. I'm installing BW 3.5 on x64 windows server 2003 platform. I'm using NU kernel 6.40.
Thanks for your suggestions on how to resolve this error.
Reward points guaranteed.

Issue solved by deleting central and database instance and started a new build. it finished without an error.
Thank you.

Creating spatial index on spatial table

Hi there. Just a quick query on creating spatial indexes on spatial tables. I have a table called System_Sessions which has the following four fields and types:
USER_ID NUMBER(10)
SESSION_ID NUMBER(10)
SESSION_BOUNDARY MDSYS.SDO_GEOMETRY (polygon)
START_POINT MDSYS.SDO_GEOMETRY (point)
I am inserting one row per user session into this table. I also need to retrieve the session ids of previous sessions involving a particular user based on the session's start point. The query i am running is an sdo_within_distance query which looks as follows:
Select session_id from joeweaker.system_sessions where user_id = 1003 and SDO_WITHIN_DISTANCE(start_point,
(MDSYS.SDO_GEOMETRY(2001, 8265, MDSYS.SDO_POINT_TYPE
(-105.0,40.0, NULL),NULL, NULL)), 'DISTANCE = 10000')='TRUE';
However I encounter the following error whenever I attempt to execute this query:
ORA-13226: interface not supported without a spatial index
ORA-06512: at "MDSYS.MD", line 1723
ORA-06512: at "MDSYS.MDERR", line 8
ORA-06512: at "MDSYS.SDO_3GL", line 255
I know I haven't built the spatial index on the table so I was hoping that somebody might show me how to do this. Thnaks a lot, Joe

Thnaks a lot Dan for the prompt reply. I have done as you advised and everything appears to be fine. However I have a second table called Session_Interest_Areas which appears as follows:
USER_ID----NUMBER(10)
SESSION_ID----NUMBER(10)
AREA_ID----NUMBER(10)
AREA_BOUNDARY----MDSYS.SDO_GEOMETRY
I inserted the necessary detail into the user_sdo_geom_metadata table and then attempted to create the index as follows (exactly the same format as my other spatial tables:
create index session_interest_areas_idx on
session_interest_areas (area_boundary)
indextype is mdsys.spatial_index;
When I execute this query I get the following stream of error messages:
ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-13249: internal error in Spatial index: [mdidxrbd]
ORA-13249: Error in Spatial index: index build failed
ORA-13249: Error in spatial index: [mdrcrtxfergm]
ORA-13249: Error in spatial index: [mdpridxtxfergm]
ORA-13200: internal error [ROWID:AAAHocAAJAAAAC8AAA] in spatial indexing.
ORA-13206: internal error [] while creating the spatial index
ORA-13373: Element of type Extent is not supported for Geodetic data
ORA-06512: at "MDSYS.SDO_INDEX_METHOD_9I", line 7
ORA-06512: at line 1
Why does this give me an error when the same approach worked fine for my other spatial tables? Is it something to do with the SRID? Also the index appears to have been created so I presume it has been created incorrectly. Thanks for your time, Joe

Cannot create text index in partition table on Oracle 10g

I try to create context index in a table with 15 millions records. The table is divided 5 partitions and each patition has 3 millions records. When I create the context index in the table, the same error always arised. The follow are my work:
--First create my own lexer
begin
ctx_ddl.createperference('my_chinese_lexer','chinese_lexer');
end;
--Second create index
create index idx_part_text3 on tb_test_part(text3)
indextype is ctxsys.context local (
partition p1_ix,
partition p2_ix,
partition p3_ix ,
partition p4_ix,
partition p5_ix)
parameters('lexer my_chinese_lexer') parallel;
--error message
create index idx_part_text3 on tb_test_part(text3)
Error in 1 line:
ORA-12801: Parellel Query Server P000 send error signal
ORA-29855: Error on execute ODCIINDEXCREATE program
ORA-06510: PL/SQL: User Defined Error
ORA-06512: In "CTXSYS.DRIDISP", line 244
ORA-04030: Try to alloc 65548 Bytes (CTX PRM heap,draccbx:message buffer) Out of memory
ORA-06512: In "CTXSYS.DRIPARX", line 10
ORA-06512: In "CTXSYS.TEXTINDEXMETHODS", line 359
ORA-04030: Try to alloc 65548 Bytes (CTX PRM heap,draccbx:message buffer) Out of memory
ORA-06512: In "CTXSYS.DRUE", line 191
ORA-06512: In "CTXSYS.DRUE", line 49
ORA-06512: In "CTXSYS.DRUE", line 24
ORA-06512: In "CTXSYS.DRUE", line 186
ORA-06512: In "CTXSYS.DRVDDL", line 682
ORA-04030: Try to alloc 65548 Bytes (CTX PRM heap,draccbx:message buffer) Out of memory
ORA-04030: Try to alloc 65548 Bytes (CTX PRM heap,draccbx:message buffer) Out of memory
ORA-06512: In "CTXSYS.DRUE", line 191
ORA-06512: In "CTXSYS.DRUE", line 49
ORA-06512: In "CTXSYS.DRUE", line 24
ORA-06512: In "CTXSYS.DRVDDL", line 452
ORA-06510: PL/SQL: User Defined Error
BTW:
My oracle 10g run on linux AS3 box with 4xP4 and 6G Mem.
I set pga_aggregate_target=2200M, and at the beginning of creating index, the max pga alloced is about 1100M, but when one patition finished, the error arised and the max pga alloced suddenly reached 3500M. So in every times, the index status is always like below:
P1_ix usable
P2_ix Inprogress
P3_ix Inprogress
P4_ix Inprogress
P5_ix Inprogress
Thx for any help!

Try to increase LARGE_POOL_SIZE.
PGA_AGGREGATE_TARGET is not only parameter that can meddle in parallel execution.
Looks like parallel execution parameters is not correctly set. Check it all, including PARALLEL_EXECUTION_MESSAGE_SIZE.

Create unique index from duplicate rows

Dear
I created an index like
create index tablename_idx on tablename (FIELD1,FIELD2);
It should be
create unique index tablename_idx on tablename (FIELD1,FIELD2,filed3);
How can I delete those duplicate records and create the UNIQUE index ?
Thanks and regards
Fahmed

> How can I delete those duplicate records
[url http://forums.oracle.com/forums/search.jspa?threadID=&q=delete+duplicate+records&objID=f75&dateRange=all&userID=&numResults=15]http://forums.oracle.com/forums/search.jspa?threadID=&q=delete+duplicate+records&objID=f75&dateRange=all&userID=&numResults=15
Regards,
Rob.

How to create unique index on a View

Hi All,
11.2.0.1
How do I create an index on a view or any workaround that my view wont get duplicates?
SQL> create unique index indx01 on db_backup_details_vw(id);
create unique index indx01 on db_backup_details_vw(id)
ERROR at line 1:
ORA-01702: a view is not appropriate here
Thanks a lot,
Kinz

I'm thinking of using a distinct clause here.
if i get 5 duplicate rows in my selection set because of the join condition, can't i discard the remaining 4 using a distinct clause.
Observe this
SQL> select * from a;
T1 T2
1 4
2 4
3 4
SQL> select * from b;
T1 T2
1 4
2 5
in both a,b t1 is the primary key. so we'll write a join on t2 (non PK).
SQL> select b.t1,b.t2 from a,b where a.t2=b.t2;
T1 T2
1 4
1 4 -- duplicates
1 4
Now create view with distinct clause
create view ab as select distinct b.t1,b.t2 from a,b where a.t2=b.t2;
SQL> select * from ab;
T1 T2
---------- ---------- -- no duplicates
1 4
CSM

W_PARTY_D_U1 = ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found.

Hi,
We are implementing OBIA 11.1.1.7.1 which comes with ODI for Fianance and Procurement analytics.When we do full load from EBS the load plan gets failed and it throws the below error
Caused By: java.sql.SQLException: ORA-20000: Error creating Index/Constraint : W_PARTY_D_U1 => ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found.
Please help us to resolve the same.
Thanks
Rama

This might need Patch:10402735
if helps mark

Can I create unpartitioned index on partitioned table??

Hi,
I am not clear about the concepts of partitioned and non partitioned index.I was under impression that If we create a index on partitioned table it will be automatically becomes a partitioned index.But I cheked in my DB there are many unpartitioned indexes on large partitioned tables.
Which one of these is efficient? wht is the concept of local and global related to these partitioned and unparitioned.I am bit confused.pls help me.
Thanks

There's nothing prevent you from creating a nonpartitioned index on partitioned table. The official name for it is Global Nonpartitioned Indexes
Global Nonpartitioned Indexes
Global nonpartitioned indexes behave just like a nonpartitioned index. They are commonly used in OLTP environments and offer efficient access to any individual record.
http://download-west.oracle.com/docs/cd/B19306_01/server.102/b14220/partconc.htm#i461446

How to create better index on a table--

Hi
I have table called CS_LM_CUST.Every day I am getting 1,50,00
records every day.And all the records I am inserting.And every
two months data I am doing purging.My requirement is to load
chaged data between 2 days i.e current day feed minus previous
day feed difference data only I need to do.
For taking the differrence data I have given the sql statement
like this.
SELECT
CUST_NO,ORIG_BR_COD,LANG_COD,NATL_CTRY_COD,CUST_NAM,DMCL_CTRY_COD
,CUST_GFCID,CUST_GFPID,STD_INDS_COD FROM CS_LM_CUST WHERE
ORIG_BR_COD = p_Branch AND REC_EXTRC_DT = CurrentDate
MINUS
SELECT
CUST_NO,ORIG_BR_COD,LANG_COD,NATL_CTRY_COD,CUST_NAM,DMCL_CTRY_COD
,CUST_GFCID,CUST_GFPID,STD_INDS_COD FROM CS_LM_CUST WHERE
ORIG_BR_COD = p_Branch AND REC_EXTRC_DT = PreviousDate
And for updating the differed data sql statement is given like
this.
UPDATE CS_LM_CUST
          SET newrec_flg = 'Y'
          WHERE cust_no = g_CSLMCUST.cust_no AND
          orig_br_cod = g_CSLMCUST.ORIG_BR_COD AND
          rec_extrc_dt = g_CSLMCUST.rec_extrc_dt;
Index has been created on cust_no,orig_br_cod,rec_extn_dt.But
the updating part is taking lot of time.Nearly 45mts.Could any
one suggest better indexing on this table which will satisfy
DML statement like SELECT,UPDATE.
The table below fields
CUST_NO
REC_TYP
LANG_COD
NATL_CTRY_COD
REC_EXTRC_DT
CUST_NAM
DMCL_CTRY_COD
CUST_GFCID
CUST_GFPID
ORIG_BR_COD
SYS_NAM
DATA_TYP
STD_INDS_COD
ACTN_TYP
EVENT_TYP
MSG_DT_TM_STMP
FORMAT_OK_FLG
MSG_ID
NEWREC_FLG
I have tried alot for creating all the possible ways.But it
satisfy either SELECT or UPDATE at a time.
Thanks & Regards
Srinivas Nimishakavi

Hi, General practice is clustered index would be created by Primary key if one created. That would identify the row ie., no duplicate rows. You can create composite key (combination of more than one column) as primary key. Other widely used practice
is to use surrogate key like identity key which assigned unique number. Please note that you only got one clustered index .
" Clustered indexes sort and store the data rows in the table or view based on their key values. These are the columns included in the index definition. There can be only one clustered index per table, because the data rows themselves can be sorted in only
one order. "
Since you already got quite few non-clustered indexes, you have to rebuild/reorganize once you create clustered index.

Is it worth creating secondary index on BKPF table ?

Hello,
One of my clients is using ECC version 5.0. I have a requirement wherein I need to fetch the data from BKPF table based on AWKEY, BUKRS and GJAHR. There is no standard secondary index available.
I have decided to create a secondary index on these fields in the following order:
1) MANDT
2) AWKEY
3) BUKRS
4) GJAHR
I know that creating secondary indexes does improve performance during data retrieval. But when I checked the total number of entries in BKPF table in production system, there are more than 20 lac 2 million records.
I am worried that creation of secondary index will create another table of such a large size in production that has data sorted on the above fields. Also, the RAM of production system is 6 GB.
Please suggest if creation of secondary index is a good measure OR should I recommend the client to increase the system RAM?
Regards,
Danish.
Edited by: Thomas Zloch on Oct 3, 2011 3:01 PM

Hi,
Secondary Index on BKPF-AWKEY has been successfully created in production. The report which used to timeout in foreground as well as in background is now executing in less than 10 seconds !!
Client is very much satisfied with this. But, there is one problem that we are facing now is that when the user is changing an existing billing document via VF02, on SAVE, system takes a very long time to save the changes done.
We monitored the processes via SM50 and found that there was a sequential read on BKPF table.
Before transporting the index in production, system approximately took not more than 5 seconds to save the Billing Document. But now system takes more than 20 minutes just to save the billing document via VF02.
I really don't know what has gone wrong. I can't figure out if I have missed any step while creating the index.
I did the following,
1) Created a Secondary index on BKPF, saved it in the transport request and activated it. Since the index was not existing in database ORACLE, I activated and adjusted the table via SE14. Now, index exists on database as well. Working perfectly in development.
2) Imported the transport request to Production. Checked in SE11. Index was existing and active. Also, index existed in database ORACLE.
Have I missed anything ? Is it required to activate and adjust the database via SE14 in production too ?
Regards,
Danish.

How to create secondry index on database table

how to create secondry index on database table

Hi
By trx SE11:
- Choose your table and press CHANGE ICON, so INDEX
When you create an index you should consider if your index is contained in another index.
If the fields of your index are:
- FIELD1, FLIED2, FIELD3
...it'll be triggered only if the select is:
SELECT * FROM <TABLE> WHERE FIELD1
                        AND FIELD2
                        AND FIELD3
A select like this
SELECT * FROM <TABLE> WHERE FIELD1
                        AND FIELD3
                        AND FIELD2
doesn't use your index.
Max

SPLIT PARTITION creating the index in different Table Space

I am splitting the table every month. After splitting the Index is also Splitting. (It is natural). But it is creating in default table Space.
I want to split INDEX and creating into the index table space “ACTIVITY_IND_TS_1”
CREATE TABLE PART
PK_KEY NUMBER(15) NOT NULL,
PK_ID NUMBER(1) NOT NULL
TABLESPACE USERS PARTITION BY RANGE (PK_ID)
PARTITION PK_ID_PRD1 VALUES LESS THAN (1)
LOGGING
TABLESPACE ACTIVITY_TAB_TS_1,
PARTITION PK_ID_PRD2 VALUES LESS THAN (2)
LOGGING
TABLESPACE ACTIVITY_TAB_TS_1,
PARTITION PK_ID_PRD3 VALUES LESS THAN (3)
LOGGING
TABLESPACE ACTIVITY_TAB_TS_1,
PARTITION PK_ID_PRD4 VALUES LESS THAN (4)
LOGGING
TABLESPACE ACTIVITY_TAB_TS_1,
PARTITION PK_ID_PRD_MAXVALUE VALUES LESS THAN (MAXVALUE)
LOGGING
TABLESPACE ACTIVITY_TAB_TS_1
NOCACHE
NOPARALLEL
ENABLE ROW MOVEMENT;
CREATE INDEX PART_IX ON PART(PK_ID)
LOCAL (PARTITION PK_ID_PRD1 TABLESPACE ACTIVITY_IND_TS_1,
PARTITION PK_ID_PRD2 TABLESPACE ACTIVITY_IND_TS_1,
PARTITION PK_ID_PRD3 TABLESPACE ACTIVITY_IND_TS_1,
PARTITION PK_ID_PRD4 TABLESPACE ACTIVITY_IND_TS_1,
PARTITION PK_ID_PRD_MAXVALUE TABLESPACE ACTIVITY_IND_TS_1)
PARALLEL
NOLOGGING;
select unique tablespace_name from user_tab_partitions; -- ACTIVITY_TAB_TS_1
select unique tablespace_name from user_ind_partitions; -- ACTIVITY_IND_TS_1
ALTER TABLE PART SPLIT PARTITION PK_ID_PRD_MAXVALUE
AT (5) INTO (PARTITION PK_ID_PRD5, PARTITION PK_ID_PRD_MAXVALUE);
select unique tablespace_name from user_tab_partitions; -- ACTIVITY_TAB_TS_1
select unique tablespace_name from user_ind_partitions; -- ACTIVITY_TAB_TS_1 ACTIVITY_IND_TS_1
Edited by: sk123 on May 5, 2009 1:05 PM

Hello,
Once you split partition you need to rebuild indexes if you want indexes to be in their own tablespaces
ALTER TABLE PART
SPLIT PARTITION PK_ID_PRD_MAXVALUE AT
(6)
INTO (PARTITION PK_ID_PRD5
TABLESPACE ACTIVITY_TAB_TS_1
PARTITION PK_ID_PRD_MAXVALUE);
ALTER INDEX PART_IX
REBUILD PARTITION PK_ID_PRD5
TABLESPACE ACTIVITY_IND_TS_1;
ALTER INDEX PART_IX
REBUILD PARTITION PK_ID_PRD_MAXVALUE
TABLESPACE ACTIVITY_IND_TS_1;Regards

Non Unique Indexes on Dimension Table

Hello ,
I have Material Dimension that has Product MainGroup, Brand , SPC code broken from Product Hierarchy.
As per Business Requirement , we don't want to use the Product Hierarchy , that should need to split into 3 pieces.
Since The Cube Dimensions already reached the 13 , we can not increase the dimensions to keep these 3 fields into separate dimensions.
I heard from Basis guy as <b>we can have index on three fields in same dimension table</b> & read some negative impact on aggregate definition.
Is it true , which one is true , am not sure.
Which one impact causes more worst & usefull..?
Could please some experts throw some light on this.
Cheers
Martin

Martin -
Not sure what you mean by "read some negative impact on aggregate definition".
But as far as adding additional indices on other columns of a dimension table, that certainly is doable. I have never done this as part of an actual intentiional design, but it seems like a valid apporach if you are limited by dimensions. I'm assuming when you say you already have 13, that the 13 does not include the three standard dimensions for time, request, (drawing a blank, is it currency), so that you really have 16 dimensions, 13 of which are user defined.
We have added dimension tabl e indices in our shop when we have found large dimension tables that, either from poor initial design, or changes to the data and/or queries, have resulted in full tables scans against large dimension tables. In some cases, the query costs of the full scan of the dimension table was more than the cost for the access of the fact table itself.
These indices must be added by your DBA as they can not be added thru the Admin Wkbench. You should also probably keep a record of any of these indices you create because if for some reason you delete the tables and reactivate the cube, you'll probably lose them.
Pizzaman

Cannot CREATE UNIQUE INDEX; duplicate keys found

I have 10g when I did an expdp from prod (an AIX 5.3 ) and impdp to a test (a RHEL3 ) with TABLE_EXISTS_ACTION=TRUNCATE, there are some index errors ORA-01452 for some of the tables but not all. As I compared the difference between , The only difference I noticed was that the one with error is the table has data, those tables without error have no data. So how which parameter I can use in impdp to avoid ? read the utility doc, have not found clear picture.
Chi

In 11510,
The duplicate row loaded is person 6272 with effective date 1994 and 1991. This needs to be fixed in vision.
Workflow SIL_PositionDimension_Full calls mapping SIL_PositionDimension to load target W_POSITION_D from source W_POSITION_DS. W_POSITION_D.INTEGRATION_ID maps to W_POSITION_DS.INTEGRATION_ID, but EFFECTIVE_FROM_DT is a more complicated many to one mapping.
Extract to W_POSITION_DS ;
SDE_ORA_PositionDimension_NonEmployee
- W_POSITION_DS.INTEGRATION_ID from PER_ALL_PEOPLE_F.PERSON_ID
SDE_ORA_PositionDimension_NoAssignments
- W_POSITION_DS.INTEGRATION_ID from JTF_RS_RESOURCE_EXTNS_TL RESOURCE_ID
-- PER~6272,4,01-JAN-94
-- PER~6272,4,01-JAN-91
select all t.*
from
select all
count(*) as n
, t.INTEGRATION_ID
, t.DATASOURCE_NUM_ID
, t.EFFECTIVE_FROM_DT
--, t.*
from baw.W_POSITION_D t
group by
null
, t.INTEGRATION_ID
, t.DATASOURCE_NUM_ID
, t.EFFECTIVE_FROM_DT
) t
where ( ( n > 1 ) )
;

Create unique index on flow table

Similar Messages

Maybe you are looking for