cancel
Showing results for 
Search instead for 
Did you mean: 

SQL error 904 accessing DFKKRDI: ORA-00904

Former Member
0 Kudos


Hi Experts,

We are perfromed client export & import from production to quality.

Export is ended with rerturn code 12, As we go through in to logs noticed subject line error.

Following is the error log:

  Main export
  Transport request   : PRDKT00070
  System              : PRD
  tp path             : tp
  Version and release: 380.10.20 720

  SQL error 904 accessing DFKKRDI: ORA-00904:
  protocol: 12, returned: 8, calculated: 12, compared: 8
  Incorrect export. Request not imported.
  Main export
  End date and time : 20150913184733
  Ended with return code:  ===> 12 <===
  ######################################

I have gone through sap notes, where it recommends to relink, re install database. Is there any work around to sort out the issue.

Any additional notes and scn links greatly helpful,Kindly help me to resolve this issue.

Thanks in advance.

Thanks & regards,

Jaswanth.

Accepted Solutions (0)

Answers (1)

Answers (1)

manumohandas82
Active Contributor
0 Kudos

Hi Jaswanth ,

Need more info for checking on this error .

Do you get any system Dumps  ( ST22 ) ?

Have you checked the following Notes

731 - Collective note: ORA-00904


Thanks ,

Manu

Former Member
0 Kudos

Hello Manu,

Thanks for your response.

I have been throught 731 note, Checked the consistency of the table as below.

Point 5 in 731 note is closely relates to my issue. Error occured during client export, as I gone through note 12826 found relink, reinstallation of databse.

Unfortunartely no system dump is generated for this activity.

Assuming parameter ctc=0 is maintained in tp profile. is this parameter value involved in this issue.

Please correct me if am wrong.

Regards,

Jaswanth.

JPReyes
Active Contributor
0 Kudos

I seen situations were reactivating the table solve the issue, SE11 -> Table -> Activate

Worth trying

Regards, JP

Former Member
0 Kudos

Hi Juan,

Thanks for your response.

Can I ask you the remedial action(re activate) would not have any impact on production system. Because there is inconsistency in mentioned table.


Please add your inputs.

Kind regards,

Jaswanth.

JPReyes
Active Contributor
0 Kudos
Because there is inconsistency in mentioned table.

Go to SE11 -> Table -> Do a consistency check, if there is an issue you need to solve it, you can post your results here.

Just to add, if you are having an issue on the production system the changes most likely came in a transport so you should see the same issues on your QAS system. You can test there.

Regards, Juan

Former Member
0 Kudos

Hi Juan,

Thanks for your response.

Below are the results:

One last query, we would need to re export the client, or can we use same file for import.

Your help is much appreciated.

Thanks & regards,

Jaswanth.

JPReyes
Active Contributor
0 Kudos

Hi Jaswanth,

Seems like you have a field in a runtime object that does not exist in the database. You can check this with your abaper and do the necessary adjustments in SE14. once the inconsistencies are fixed re-export the client.

Regards, JP

Reagan
Advisor
Advisor
0 Kudos

The solution that worked for me in the past was to "Activate and Adjust the database table" with the "Save Data" option selected.