We have found the cause of the problem. If populate the varray for a row with 100
values, copy that data to a temporary table and then perform split and exchange
partition operations everything is fine. However if we populate the varray with 1000
values for a row and then perform the same
Hi!
If even Oracle hasn't seen this error, then probably we can't help much here
either. Just a wild guess, try to move this partition to another location
and select from it then (although koxsisz1 isn't a data layer error as far
as I understand). Try to read using index if available, then using
The error was first discovered when we tried to move a partition. ( alter table
archive_wave_i move partition SEP1103 tablespace CHANARCH_NLC_2003_09_DATA). The
table was renamed to OLD_archive_wave_i once it was determined that no new varray data
was accessible. My theory is that this is
Hi!
I'm on thin ice here, but I think KO means some sort of object layer (KOC is
Kernel-Object-Cache module as far as I understand), so koxsisz1 has probably
something to do with objects as well (thus not caching, x might mean execute
or transaction or anything else:). On the other hand, varrays
Ian,
I was going to recommend to try exporting your problematic partition with
direct=y, that way normal SQL query processing layer is bypassed in Oracle
kernel all data belonging to segment is read directly (thus hopefully
avoiding the koxsisz1 crash) ... but I'm not sure whether varrays don't
The varray data is stored in a LOB. So I expect direct export will not work. But
I'll give it a try.
Ian
-Original Message-
Sent: Thursday, September 18, 2003 1:35 PM
To: Multiple recipients of list ORACLE-L
Ian,
I was going to recommend to try exporting your problematic
Jeremy, you've been left out of the camel joke, evidently.
It will come around again. I guess pointless is better than useless :)
joe
Jeremy Pulcifer wrote:
So, Joe, are you pointless for a reason, or is there a joke I'm not
aware of.
-Original Message-
From: JOE TESTA
There is a utility called "ORA-600 Lookup
Utility" which is on Metalink which prompts you for the first argument listed in
the ORA-600 error that will give you an idea where the problem
lies.
-Original Message-From: JOE TESTA
[mailto:[EMAIL PROTECTED]]Sent: Thursday, December
Title: RE: ORA-600 error(solution for all of them).
So, Joe, are you pointless for a reason, or is there a joke I'm not aware of.
-Original Message-
From: JOE TESTA [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 12, 2002 7:29 AM
To: Multiple recipients of list ORACLE-L
Subject
To: Multiple recipients of list ORACLE-L
Subject:RE: ORA-600 Error
Hi Catherine,
Depending on your version, and whether you have set the
system profile
'Sign-On:Audit Level' to FORMS, you should be able
Hi Catherine,
Depending on your version, and whether you have set the system profile
'Sign-On:Audit Level' to FORMS, you should be able to view current online
forms users using
SELECT USER_NAME, USER_FORM_NAME, RESPONSIBILITY_NAME, TIME, PID
FROM APPS.FND_SIGNON_AUDIT_VIEW order by user_name
Raj,
You didn't tell me the Oracle Version. So I would assume this is most
current version.
Your error OERI:4427 is a transaction layer component internal error.
By any chance you are using 2 phase commits (or ditributed
transactions) in thiese databases? or database resource manager ?
---
Sorry I didn't mention this before, this is 9.0.1.0.0 and I am not sure
about any distributed transactions I'll check that though ... BTW all three
instances of errors are on COMMIT statement.
Thanks for the clue ...
Raj
__
Rajendra Jamadagni
13 matches
Mail list logo
