| ORA-00607 [message #220385] |
Tue, 20 February 2007 08:47  |
kregan77
Messages: 21
Registered: January 2007
|
Junior Member |
|
|
ORA-12008: error in materialized view refresh path
ORA-00607: Internal error occurred while making a change to a data block
ORA-00600: internal error code, arguments: [kddummy_blkchk], [27], [1386], [18038], [], [], [], []
I searched and found another post on here regarding this error and I think I understand that it means there is corruption in the redo log?? I am not a dba and need to go look up what exactly this means but in the meantime I was hoping someone could give me some insight into this error and make some suggestions. Most suggestions I've seen thus far from searching are to open a TAR with oracle. Is there anything else I can do? Is it at all possible that an error like this can be caused by software running against the database? I Have the trace file and am going to look at it - however, I fear my lack of experience will prohibit me from actually getting any real clues out of this though.
Thanks!
|
|
|
|
|
|
| Re: ORA-00607 [message #221574 is a reply to message #220385] |
Tue, 27 February 2007 09:11  |
kregan77
Messages: 21
Registered: January 2007
|
Junior Member |
|
|
Another facet to this problem that I would like you to consider:
Refreshing the view in TOAD does not result in the error... I"m not even sure how they are doing this - apparently they can right click it and refresh it. The way it is being done in the code is:
DBMS_MVIEW.REFRESH(params);
I'm sure its possible there are different routes of functionality between the way TOAD does it from this pl/sql approach. I'm trying to justify that this is not a software problem but an internal oracle issue that needs to be addressed via TAR.
Thanks!
|
|
|
|
| Re: ORA-00607 [message #221587 is a reply to message #221574] |
Tue, 27 February 2007 09:47 |
kregan77
Messages: 21
Registered: January 2007
|
Junior Member |
|
|
|
Actually I probably answered my own question... in TOAD they probably think they are refreshing the materialized view when in fact all they are doing is refreshing the toad client with the most recent data from the mview - which is NOT the same as DBMS_MVIEW.REFRESH. Can somone just confirm my theory? Thanks!
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
