Skip to Main Content

Oracle Database Discussions

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Block corruption with creating tables/inserting data

658887Sep 9 2008 — edited Sep 9 2008
I appear to have a corrupt block that I encounter when I reach a certain point in creating a table or inserting new data in an Oracle 10gR2 database. The error is

SQL Error: ORA-00604: error occurred at recursive SQL level 2
ORA-01578: ORACLE data block corrupted (file # 1, block # 59522)
ORA-01110: data file 1: 'E:\ORACLE\PRODUCT\10.2.0\ORADATA\IMAGES\SYSTEM01.DBF'
00604. 00000 - "error occurred at recursive SQL level %s"
*Cause: An error occurred while processing a recursive SQL statement
(a statement applying to internal dictionary tables).
*Action: If the situation described in the next error on the stack
can be corrected, do so; otherwise contact Oracle Support.



(I only get the first two lines when inserting new data)

Is there a way to mark this block so as to not use it. There is no existing object using this block -- the issue appears to occur when something tries to use it for the first time.

Edited by: user8026807 on Sep 9, 2008 8:13 AM

Comments

Timo Hahn

I recommend that you try this in 12.2.1.4 to see if you hit a problem in your version.
From your description we can only do some wild guesses, like changing the content delivery to immediate.
Timo

MaximusDecimus

Hi. Thanks for the reply.
I tried a similar task flow in 12.2.1.4 - this one uses the a read-only table and editable form to maintain the detail rows. I got the same issue when the task flow Data Control Scope was set to Isolated. Again, this only manifested on the first invocation of the task flow.
When I change the scope to Shared, it functions as expected initially and subsequently.
Any ideas?

Timo Hahn

This means that you miss some kind of initialization when you use isolated scope and start the task flow the first time.
The second time the needed init is done and it works.
Timo

MaximusDecimus

Hi Timo,
Many thanks for the reply.
I understand what you're saying, but I'm not sure what initialization is needed when using isolated scope? The task flow path creates a row in the master and detail view objects before getting to the problematic page fragment.
When the data control frame is created as part of the new transaction for the isolated scope, what else needs to be done to initialize anything?
Thanks again.

Timo Hahn

I have no idea what is missing. I would need to look at the running app and the code.

Timo

MaximusDecimus

Hi Timo,
Thanks for taking the time to reply.
I wouldn't expect you to comment on specifics of the application, my point is why any separate initialization should be needed when I'd expect the framework to initialize the relevant view object on creation of the data control frame?
The page in question has no references to any scoped variables, so I'm at a loss as to why the first invocation should be different to subsequent calls? If that is too simplistic a belief, or I'm missing something obvious then please let me know.
Thanks again.

Timo Hahn

I don't know. Maybe you hit a bug. Who knows?
Anyway, if you really want to know what's going on you'll have to open an SR with support.

Timo

MaximusDecimus

Hi Timo.
Yes maybe. Thanks for your help anyway.

1 - 8
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Oct 7 2008
Added on Sep 9 2008
8 comments
566 views