SAP Note 11369 - ORA-1452 during import after export from other system.

-
Symptom

ORA-1452 cannot CREATE UNIQUE INDEX; duplicate keys found
when you import a dataset that was exported from a source system into a target system.

Reason and Prerequisites

A table in the source system contains duplicate keys, although a UNIQUE index existed there. This may result from rollback problems with ORACLE 7.0.13 in connection with cluster tables containing long raw fields.

Solution
Determine the keys:
DESCRIBE sapr3.;
???Fields with entry NOT NULL

Determine the duplicate records (summary diplay of the records
with multiple key values):

select alldata.rowid, alldata.*
from
alldata,
(SELECT , ...,
FROM

GROUP BY , ...,
HAVING COUNT(*) > 1) keydata
where alldata.=keydata.
and ...
and alldata.=keydata.;

For example:
Table with duplicate keys is sapr3.dk with 2 key columns c1 and c2

select alldata.rowid, alldata.*
from SAPR3.dk alldata,
(SELECT c1, c2 FROM SAPR3.dk GROUP BY c1, c2
HAVING COUNT(*) > 1) keydata
where alldata.c1=keydata.c1
and alldata.c2=keydata.c2;

When large tables are involved, we recommend that you create the index that could not be created as NONUNIQUE before you start the query. This will result in a significantly shorter runtime for the query. Check the records output by the query to make sure they are absolutely identical (non-key fields). If in doubt, contact the developer to find out how to correct the inconsistency. If the records are absolutely identical, the duplicate record can be deleted. The best way to do this is by using the ROWID selected above:

DELETE
FROM SAPR3.
WHERE keyfeld_1 = key_value_1
AND keyfeld_2 = key_value_2
...
AND keyfeld_n = key_value_n
AND ROWID <> ;

Once all the duplicate records have been deleted, the index which could not be created must be created as a UNIQUE INDEX.

Keyword: ORA-1452

Comments

Post a Comment

Popular posts from this blog

SAP Note 11489 - What to do when there are print problems in QM.

-
Symptom Either an incorrect inspection instruction or sample drawing instruc- tion is printed, or none at all. Errors in the print control settings in the Customizing application cannot be ruled out. If no inspection instruction or sample drawing instruction is printed, two different situations can exist: a) In the inspection lot transactions, no sample drawing instruction or inspection instruction can be printed after the sample has been calculated. b) In the inspection lot transactions, the documents can be printed, but not immediately from the stock postings. Error messages: QA162, CO412 (among others) Transaction codes: QA01, QA02, QA03, MB01 (among others) Cause and prerequisites There can be several reasons for this situation: 1. The print form does not exist, the print form does not exist in the required language nor does it exist in the client concerned, or the print form is not activated (system installation). 2. The table settings are incorrect (Customizing...
Read more

SAP Note 11507 - Fields returned wrong in elec. bank statement.

-
Symptom The bank sends an incorrect business transaction code. This code does not exist in the system. It is not possible to process the corresonding line in the electronic bank statement. Cause and prerequisites Bank error Solution Either a) or b) a) Temporarily define the incorrect business transaction code in the system, process the statement, then delete the transaction code afterwards. b) Change the business transaction code in the database: 1.) Transaction : SE16 Table : FEBKO Application : 0001 Sender bank : 'Bank code' (15-digit) 'Account number' Statemnt ID : 'Year'(4-digit) 'Statement number'(5-digit) ShortKey : select "Output" --> Note the displayed ShortKey! 2.) Transaction : SE16 Table : FEBEP ShortKey : noted value BusTransCode : select "Output" --> Note the incorrect BusTr...
Read more

SAP Note 11477 - Check deposit: fields are not printed.

-
Symptom You want to print out more fields than those specified in the standard form, F_M40S_CHEQUE, on the check deposit list (for example, FEBSCK-KUNNR = Customer number, ...). Cause and prerequisites Outputting other fields on the check deposit form is not supported. Output is not possible for most fields because the relationship between form and check is not 1:1, but instead N:1. For example, one check could be used to pay the invoices of several customers. In addition to the fields available in the standard form, the fields in table FEBEP can be output for each check. However, only a few of the fields in FEBEP are filled. Solution If organizational measures can guarantee a 1:1 relationship, you can enter the required field in the "Issuer" field manually and print it on the form. Of course, you can do this only if you are not using the "Issuer" field. Additional key words SAPMF40S, FF68
Read more