cancel
Showing results for 
Search instead for 
Did you mean: 

ORA-07445: exception encountered: core dump

Former Member
0 Kudos

Hi,

I am getting the following alert in alert.log file of our BW server :

ORA-07445: exception encountered: core dump [] [] [] [] [] [].

The SQ statement SELECT /*+ STAR_TRANSFORMATION FACT( T_00 ) */ T_00 . "ISSTOTSTCK" "K____464" , T_00 . "ISSVS_VAL" "K____155" , T_00 . "RECTOTSTCK" "K____463" , T_00 . "RECVS_VAL" "K____156" FROM "/BIC/FC_0IC_C03" T_00 , "/BIC/DC_0IC_C032" T_01 , "/BI0/SMATERIAL" T_02 , "/BIC/DC_0IC_C036" T_03 , "/BI0/SPLANT" T_04 , "/BIC/DC_0IC_C03P" T_05 , "/BIC/DC_0IC_C038" T_06 , "/BI0/SVENDOR" T_07 , "/BIC/DC_0IC_C03T" T_08 WHERE ( T_00 . "KEY_C_0IC_C032" = T_01 . "DIMID" ) AND ( T_01 . "SID_0MATERIAL" = T_02 . "SID" ) AND ( T_00 . "KEY_C_0IC_C036" = T_03 . "DIMID" ) AND ( T_03 . "SID_0PLANT" = T_04 . "SID" ) AND ( T_00 . "KEY_C_0IC_C03P" = T_05 . "DIMID" ) AND ( T_00 . "KEY_C_0IC_C038" = T_06 . "DIMID" ) AND ( T_06 . "SID_0VENDOR" = T_07 . "SID" ) AND ( T_00 . "KEY_C_0IC_C03T" = T_08 . "DIMID" AND T_00 . "SID_0CALMONTH" = T_08 . "SID_0CALMONTH" ) AND T_08 . "SID_0CALDAY" BETWEEN 19901031 AND 20081031 AND T_08 . "SID_0CALMONTH" BETWEEN 199010 AND 200810 AND T_00 . "SID_0CALMONTH" BETWEEN 199010 AND 200810 AND T_02 . "MATERIAL" = '088476' AND T_04 . "PLANT" = 'A002' AND T_05 . "SID_0RECORDTP" = 0 AND T_07 . "VENDOR" = 'DT037'

We have recently upgraded our oracle from 9.2.0.6 to 9.2.0.8.

Our OS is IBM AIX.

System is up an running.

Kindly suggest.

Regards,

Rahul.

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Thanks.

Former Member
0 Kudos

Hi Rahul,

Check this link.This might help you...

[http://ora-07445.ora-code.com/]

Thanks & Regards,

Sudheer.

Former Member
0 Kudos

Hi Juan,

Thanks.

We have already appilied all patches.

Regards,

Rahul.

JPReyes
Active Contributor
0 Kudos

Check if Note 1040300 - Wrong values with Star Transformation Hint 9.2.0.8 /10.2.0.2 helps.

It might just do the trick.

Regards

Juan

JPReyes
Active Contributor
0 Kudos

This is most likely an Oracle bug... did you completed all the steps after upgrading the database?... I think you're missing an Oracle patch.

If you can't find the missing patch open an OSS message.

Regards

Juan