RE: ORA-1410 Silliness

2003-01-02 Thread Koivu, Lisa
Title: RE: ORA-1410 Silliness Vladimir, Thanks for your reply. I have tested the cursor. It does not include any bind variables. There are no broken rowids, as all objects passed analyze ... validate structure cascade. I also tested the scenario you describe in your code below. The code

RE: ORA-1410 Silliness

2003-01-02 Thread Koivu, Lisa
Title: ORA-1410 Silliness Hi Waleed, No. This is the name of the package. Thanks Lisa -Original Message-From: Khedr, Waleed [mailto:[EMAIL PROTECTED]]Sent: Tuesday, December 31, 2002 3:04 PMTo: Multiple recipients of list ORACLE-LSubject: RE: ORA-1410 Silliness I see

RE: ORA-1410 Silliness

2003-01-02 Thread Jamadagni, Rajendra
Title: ORA-1410 Silliness Lisa, This is probably nottrue ... Oracle doesn't, has never been able to pinpoint exact line number (in cases such as these) especially with pl/sql packages. I believe the problems can be found by executing following query ... select line, type, source from

RE: ORA-1410 Silliness

2003-01-02 Thread Koivu, Lisa
Nope... -Original Message-From: ora ak [mailto:[EMAIL PROTECTED]]Sent: Tuesday, December 31, 2002 4:54 PMTo: Multiple recipients of list ORACLE-LSubject: RE: ORA-1410 Silliness Did u do any migration recently . "Koivu, Lisa" [EMAIL PROTECTED] wrote:

RE: ORA-1410 Silliness

2003-01-02 Thread Mercadante, Thomas F
Title: ORA-1410 Silliness Lisa, I know someone else may have suggested this, but I am thinking that maybe you do need to rebuild the index that was being used by the query. It could be you have a bad index that still has an entry for a record, but the record does not exist? Sounds

RE: ORA-1410 Silliness

2003-01-02 Thread Koivu, Lisa
Title: RE: ORA-1410 Silliness Amount of data, definately. This table grows by ~2.5GB weekly. Have you ever seen data volume begin to cause problems? Thanks Rachel -Original Message- From: Rachel Carmichael [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 31, 2002 5:05 PM

RE: ORA-1410 Silliness

2003-01-02 Thread Khedr, Waleed
Title: ORA-1410 Silliness Is the error reproducible if you replace the bulk insert with regular insert? Waleed -Original Message-From: Koivu, Lisa [mailto:[EMAIL PROTECTED]]Sent: Thursday, January 02, 2003 8:14 AMTo: Multiple recipients of list ORACLE-LSubject: RE: ORA

Re: ORA-1410 Silliness

2003-01-02 Thread Babu Nagarajan
Title: ORA-1410 Silliness Lisa I dont recollect exactly but I think I have seen this happen when you start getting too close to the max_open_cursor limit... something like Oracle cant open a cursor as it is at the max limit and a fetch call might be issued.. Checkyr max_open_cursor limit

RE: ORA-1410 Silliness

2003-01-02 Thread Mercadante, Thomas F
recipients of list ORACLE-LSubject: RE: ORA-1410 Silliness Nope... -Original Message-From: ora ak [mailto:[EMAIL PROTECTED]]Sent: Tuesday, December 31, 2002 4:54 PMTo: Multiple recipients of list ORACLE-LSubject: RE: ORA-1410 Silliness Did u do any migration

RE: ORA-1410 Silliness

2003-01-02 Thread Sherman, Edward
. This happens even if the partition has been made USABLE after query start. Good luck Ed -Original Message-From: Koivu, Lisa [mailto:[EMAIL PROTECTED]]Sent: Tuesday, December 31, 2002 12:49 PMTo: Multiple recipients of list ORACLE-LSubject: RE: ORA-1410 Silliness You asked

RE: ORA-1410 Silliness

2003-01-02 Thread Rachel Carmichael
total speculation since I'm not a PL/SQL expert -- could the amount of data you are manipulating in the stored procedure somehow blow out available memory? --- Koivu, Lisa [EMAIL PROTECTED] wrote: Amount of data, definately. This table grows by ~2.5GB weekly. Have you ever seen data volume

RE: ORA-1410 Silliness

2003-01-02 Thread Koivu, Lisa
Title: ORA-1410 Silliness Hi Raj, Thanks for your reply. I always suspected that the line numbers were wrong but since I couldn't say decisively why I had to rely upon what the gui's told me (darn gui...) You proved it. That line is actually pointing to my generic error logging proc

RE: ORA-1410 Silliness

2003-01-02 Thread Koivu, Lisa
Title: RE: ORA-1410 Silliness Not at this point. I believe when the pl/sql tables get too big it blows up with ora-4031 or one of the common memory errors, I've seen it happen before. I may have only a stupid windows machine, but I have so much RAM... kudos to the brilliant people who didn't

RE: ORA-1410 Silliness

2003-01-02 Thread Fink, Dan
Title: ORA-1410 Silliness Lisa, The answer is very, very simple...Don't take a day off! No day off...no error...no failed loads... Seriously, it sounds like either an index corruption (temporary) or an oracle bug. Is there anything in the alert log or in trace files? Try setting a trap

RE: ORA-1410 Silliness

2003-01-02 Thread Jamadagni, Rajendra
Title: RE: ORA-1410 Silliness I am no pl/sql expert either, but me think that would cause a ORA-4031 ... been there ... done that ... before I learned to code in a better way. Raj __ Rajendra Jamadagni MIS, ESPN Inc. Rajendra dot Jamadagni

RE: ORA-1410 Silliness

2003-01-02 Thread Jamadagni, Rajendra
Title: RE: ORA-1410 Silliness Lisa, try to see if you can (I think you should) use dbms_session.free_unused_user_memory ... this is very handy for applications where large pl/sql tables (oops ... arrays) are used frequently. Raj

RE: ORA-1410 Silliness

2003-01-02 Thread Koivu, Lisa
Title: RE: ORA-1410 Silliness Thanks again Raj. I will definately look into it. Lisa -Original Message-From: Jamadagni, Rajendra [mailto:[EMAIL PROTECTED]]Sent: Thursday, January 02, 2003 11:39 AMTo: Multiple recipients of list ORACLE-LSubject: RE: ORA-1410 Silliness

Re: ORA-1410 Silliness

2003-01-02 Thread Vladimir Begun
Lisa . I've read some messages of this thread -- there is 100% probability :) that you incorrectly identified the statement which errors 1410. PL/SQL engine could not point to the line 1970 -- it's in the middle of the statement -- something is strange there. Do you handle exceptions in your

RE: ORA-1410 Silliness

2003-01-02 Thread Koivu, Lisa
Title: RE: ORA-1410 Silliness Vladimir, you are 100% right :) Thanks for your reply. Lisa -Original Message- From: Vladimir Begun [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 02, 2003 1:48 PM To: Multiple recipients of list ORACLE-L Subject: Re: ORA-1410 Silliness Lisa

Re: ORA-1410 Silliness

2003-01-02 Thread Stephane Faroult
Jamadagni, Rajendra wrote: Lisa, This is probably not true ... Oracle doesn't, has never been able to pinpoint exact line number (in cases such as these) especially with pl/sql packages. I believe the problems can be found by executing following query ... select line, type, source

Re: ORA-1410 Silliness

2003-01-02 Thread Vladimir Begun
Jamadagni, Rajendra wrote: Oracle doesn't, has never been able to pinpoint exact line number (in Can you please prove it? Do not you think that this statement contradicts to the sql query you provided below. :) There is quite some difference with GUI which pulls/[s]pools PL/SQL code out and

RE: ORA-1410 Silliness

2003-01-02 Thread Jamadagni, Rajendra
Title: RE: ORA-1410 Silliness Okay ... I need to be clearer ... this is because editors have no concept of line-of-code that Oracle uses. For Oracle one 3 page insert statement is one statement, whereas an editor will treat it as a bunch of line numbers (when it encounters a linefeed

ORA-1410 Silliness

2002-12-31 Thread Koivu, Lisa
Title: ORA-1410 Silliness Hello all, 8.1.7, Windows 2000 SP2 Here's the error: * ERROR at line 1: ORA-01001: invalid cursor ORA-06512: at ELVIS.CLEANUP_VEGAS_PK, line 1970 ORA-01410: invalid ROWID ORA-06512: at line 1 Has anyone seen this error before? I run into this error

Re: ORA-1410 Silliness

2002-12-31 Thread Robert Eskridge
Lisa, Tuesday, December 31, 2002, 7:43:54 AM, you wrote: KL Usually when this happens I can re-fire the load and it will KL complete, no problem. It's a big annoyance and it seems like every KL time I take a day off it happens. How does it know you are taking a day off? Maybe you shouldn't set

RE: ORA-1410 Silliness

2002-12-31 Thread Farnsworth, Dave
Title: ORA-1410 Silliness Sounds like another Elvis sighting!! -Original Message-From: Koivu, Lisa [mailto:[EMAIL PROTECTED]]Sent: Tuesday, December 31, 2002 7:44 AMTo: Multiple recipients of list ORACLE-LSubject: ORA-1410 Silliness Hello all, 8.1.7, Windows 2000 SP2

RE: ORA-1410 Silliness

2002-12-31 Thread Orr, Steve
Title: ORA-1410 Silliness Is there a column with a datatype of rowid? -Original Message-From: Koivu, Lisa [mailto:[EMAIL PROTECTED]]Sent: Tuesday, December 31, 2002 6:44 AMTo: Multiple recipients of list ORACLE-LSubject: ORA-1410 Silliness Hello all, 8.1.7, Windows

Re: ORA-1410 Silliness

2002-12-31 Thread KENNETH JANUSZ
Title: ORA-1410 Silliness Elvis? No way. It's got to be a Raelian clone. Ken Janusz - Original Message - From: Farnsworth, Dave To: Multiple recipients of list ORACLE-L Sent: Tuesday, December 31, 2002 8:34 AM Subject: RE: ORA-1410 Silliness Sounds like

RE: ORA-1410 Silliness

2002-12-31 Thread Koivu, Lisa
Title: ORA-1410 Silliness Nope... nothing named rowid. -Original Message-From: Orr, Steve [mailto:[EMAIL PROTECTED]]Sent: Tuesday, December 31, 2002 9:29 AMTo: Multiple recipients of list ORACLE-LSubject: RE: ORA-1410 Silliness Is there a column with a datatype of rowid

RE: ORA-1410 Silliness

2002-12-31 Thread Koivu, Lisa
Title: RE: ORA-1410 Silliness Yea, yea, well... my environment here leaves a lot to be desired :) Heck my database isn't even being BACKED UP aside from the backups I scream for. Don't even ask. As an aside that I forgot to mention: I am not using FOR UPDATE OF in any of my procedures

RE: ORA-1410 Silliness

2002-12-31 Thread Jamadagni, Rajendra
Title: ORA-1410 Silliness But "cloned" rows ought to have different rowids ... Raj __ Rajendra Jamadagni MIS, ESPN Inc. Rajendra dot Jamadagni at ESPN dot com Any opinion expressed here is personal and doesn't reflect that o

RE: ORA-1410 Silliness

2002-12-31 Thread Mercadante, Thomas F
Title: ORA-1410 Silliness Lisa, What is your cursor doing? Perhapsrow-migration is occuring thus causing the rowid to become invalid? Tom Mercadante Oracle Certified Professional -Original Message-From: Koivu, Lisa [mailto:[EMAIL PROTECTED]]Sent: Tuesday, December 31, 2002

RE: ORA-1410 Silliness

2002-12-31 Thread John Weatherman
of list ORACLE-LSubject: Re: ORA-1410 Silliness Elvis? No way. It's got to be a Raelian clone. Ken Janusz - Original Message - From: Farnsworth, Dave To: Multiple recipients of list ORACLE-L Sent: Tuesday, December 31, 2002 8:34 AM Subject

RE: ORA-1410 Silliness

2002-12-31 Thread Koivu, Lisa
Title: ORA-1410 Silliness If I had a Raelian clone for a sysadmin I would have less problems than I do now. GRRR -Original Message-From: KENNETH JANUSZ [mailto:[EMAIL PROTECTED]]Sent: Tuesday, December 31, 2002 9:59 AMTo: Multiple recipients of list ORACLE-LSubject: Re

RE: ORA-1410 Silliness

2002-12-31 Thread Koivu, Lisa
Title: ORA-1410 Silliness Hi Tom, Row movement is disabled on this table. Cursor is only selecting from a raw data table, formatting/cleaning up data and loading it into a temp table (which also passed analyze table cascade) and then the temp table is swapped into the proper partition

RE: ORA-1410 Silliness

2002-12-31 Thread Kevin Lange
Title: ORA-1410 Silliness How about posting the table structure and the lines around 1970 in the Elvis package. -Original Message-From: Koivu, Lisa [mailto:[EMAIL PROTECTED]]Sent: Tuesday, December 31, 2002 9:04 AMTo: Multiple recipients of list ORACLE-LSubject: RE: ORA

RE: ORA-1410 Silliness

2002-12-31 Thread Whittle Jerome Contr NCI
Title: RE: ORA-1410 Silliness Actually if you had a clone of your SA, you might have twice as many problems. Jerry Whittle ASIFICS DBA NCI Information Systems Inc. [EMAIL PROTECTED] 618-622-4145 -Original Message- From: Koivu, Lisa [SMTP:[EMAIL PROTECTED]] If I had

RE: ORA-1410 Silliness

2002-12-31 Thread Jamadagni, Rajendra
Title: RE: ORA-1410 Silliness Anything with a Materialized View?? Raj __ Rajendra Jamadagni MIS, ESPN Inc. Rajendra dot Jamadagni at ESPN dot com Any opinion expressed here is personal and doesn't reflect that of ESPN Inc. QOTD: Any

RE: ORA-1410 Silliness

2002-12-31 Thread Koivu, Lisa
Title: ORA-1410 Silliness You asked for it. Here goes. It is partitioned on julian_run_date. Please don't hammer me about the design. I wasn't given a chance to improve on it. It is basically a mainframe file that I have stored history of. SQL desc vegas_martName Null? Type

RE: ORA-1410 Silliness

2002-12-31 Thread Koivu, Lisa
Title: RE: ORA-1410 Silliness Hi Raj, No materialized view. That would be too high-tech for this company. And it might kill Elvis more than once. -Original Message-From: Jamadagni, Rajendra [mailto:[EMAIL PROTECTED]]Sent: Tuesday, December 31, 2002 10:49 AMTo: Multiple

RE: ORA-1410 Silliness

2002-12-31 Thread srini . chavali
Lisa, I am joining this thread late - so apologies if my suggestion has already been looked into ! The first error message is ORA-01001 (Invalid Cursor). There is an article on MetaLink (1007395.6) about the various causes for this error. Have you read this article and verified that the

RE: ORA-1410 Silliness

2002-12-31 Thread Kevin Lange
Title: ORA-1410 Silliness Very straight forward. and LONG . (Yea, I read to your last message). Could that be the issue here ?? Is the record too long or some buffer being overwritten in Oracle when there is so long of record and so much data ?? Have you tried (or do you already

RE: ORA-1410 Silliness

2002-12-31 Thread Rachel Carmichael
dumb question -- did you extract the insert statement and run it in sqlplus? Does it run there or does it go boom as well? --- Koivu, Lisa [EMAIL PROTECTED] wrote: You asked for it. Here goes. It is partitioned on julian_run_date. Please don't hammer me about the design. I wasn't given a

RE: ORA-1410 Silliness

2002-12-31 Thread Koivu, Lisa
Title: ORA-1410 Silliness Well, I don't think that's the issue. I'm issuing bulk inserts and using pl/sql tables in this procedure. That functionality has been in place since February and these errors only started surfacing in the last couple of months. I could decrease the commit

RE: ORA-1410 Silliness

2002-12-31 Thread Koivu, Lisa
Title: RE: ORA-1410 Silliness Yes, I do exchange partition but the error happens long before I hit the procedure that does that. It blows up on the load. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 31, 2002 1:44 PM To: [EMAIL

RE: ORA-1410 Silliness

2002-12-31 Thread Koivu, Lisa
Title: RE: ORA-1410 Silliness I just read it and most of these scenarios are specific to OCI. This is straight pl/sql. However I did check max open cursors (I believe that's a different error, I've seen that one before) and that's not the problem. I may be wrong, but when an error happens I

RE: ORA-1410 Silliness

2002-12-31 Thread Khedr, Waleed
Title: ORA-1410 Silliness I see "ELVIS.CLEANUP_VEGAS_PK" in the error message. Is it the primary key index for a table? If yes, then it may need to be rebuilt. Regards, waleed -Original Message-From: Koivu, Lisa [mailto:[EMAIL PROTECTED]]Sent: Tuesday, December 31,

RE: ORA-1410 Silliness

2002-12-31 Thread Koivu, Lisa
Title: RE: ORA-1410 Silliness Hi Rachel, Just tried it and it works. Thanks for your suggestion. Lisa -Original Message- From: Rachel Carmichael [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 31, 2002 2:19 PM To: Multiple recipients of list ORACLE-L Subject: RE: ORA-1410

Re: ORA-1410 Silliness

2002-12-31 Thread Vladimir Begun
Lisa . Enable SQL tracing . Launch your code . Identify (exactly) the cursor which fails with ORA-01410 and what bind vars are. . Pull out the statement from your code . Run it in 'standalone' mode . If it fails identify rowids which look broken. Check the phys. entities those rowids point

RE: ORA-1410 Silliness

2002-12-31 Thread ora ak
ecember 31, 2002 1:44 PMTo: Multiple recipients of list ORACLE-LSubject: RE: ORA-1410 Silliness Very straight forward. and LONG . (Yea, I read to your last message). Could that be the issue here ?? Is the record too long or some buffer being overwritten in Oracle when there is so long

RE: ORA-1410 Silliness

2002-12-31 Thread Rachel Carmichael
Okay this means that the statement itself, which is being pointed to by the error line, is not the real culprit. Unfortunately, I don't know of a good debugger for PL/SQL that lets you step through line by line. let me rephrase that, I know of no freeware one :) since you say this has only