RE: ORA-904 after table rename

2004-01-21 Thread Jamadagni, Rajendra
When required I did it through a logon trigger ... wait I still do it. Raj Rajendra dot Jamadagni at nospamespn dot com All Views expressed in this email are strictly personal. QOTD: Any clod can have facts, having

Re: ORA-904 after table rename

2004-01-20 Thread Mladen Gogala
Oradebug is the right way to go because, for some reason, alter system set events='904 trace name errorstack forever, level 10'; doesn't do anything. The only way to activate trace is to go to oradebug, attach the session (of course, one needs to do gymnastics with V$SESSION and V$PROCESS to find

Re: ORA-904 after table rename

2004-01-20 Thread Tanel Poder
Hi! Note that when you set an event with alter system, it will only apply for new sessions created, not for any existing ones. Tanel. - Original Message - To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED] Sent: Tuesday, January 20, 2004 4:19 PM Oradebug is the right way to

Re: ORA-904 after table rename

2004-01-20 Thread Mladen Gogala
On 01/20/2004 02:59:35 PM, Tanel Poder wrote: Hi! Note that when you set an event with alter system, it will only apply for new sessions created, not for any existing ones. And that, exactly is the problem. First, when you set event using alter system, the setting is system wide. Second, if you

RE: ORA-904 after table rename

2004-01-20 Thread Bobak, Mark
You can also use DBMS_SYSTEM.SET_INT_PARAM_IN_SESSION and DBMS_SYSTEM.SET_BOOL_PARAM_IN_SESSION, in lieu of oradebug. -Mark Mark J. Bobak Oracle DBA ProQuest Company Ann Arbor, MI Imagination was given to man to compensate him for what he is not, and a sense of humor was provided to console him

Re: ORA-904 after table rename

2004-01-20 Thread Tanel Poder
But you can't set events with it :( Tanel. - Original Message - To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED] Sent: Tuesday, January 20, 2004 10:39 PM You can also use DBMS_SYSTEM.SET_INT_PARAM_IN_SESSION and DBMS_SYSTEM.SET_BOOL_PARAM_IN_SESSION, in lieu of oradebug.

RE: ORA-904 after table rename

2004-01-20 Thread Bobak, Mark
For that, there is DBMS_SYSTEM.SET_EV. ;-) -Mark Mark J. Bobak Oracle DBA ProQuest Company Ann Arbor, MI Imagination was given to man to compensate him for what he is not, and a sense of humor was provided to console him for what he is. --Unknown -Original Message- Sent: Tuesday,

RE: ORA-904 after table rename

2004-01-20 Thread Stephen Andert
One thing I've been looking for is a way to set a string parameter in another session, The two you mention handle INTEGER and BOOLEAN. I want a way to set TRACEFILE_IDENTIFIER to a string in another session to make it easier to identify trace files. Any ideas? Stephen [EMAIL PROTECTED]

Re: ORA-904 after table rename

2004-01-20 Thread Tanel Poder
Ok, yeap I confused this with READ_EV, which can't read event from other sessions... Great job ;) Tanel. - Original Message - To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED] Sent: Tuesday, January 20, 2004 11:19 PM For that, there is DBMS_SYSTEM.SET_EV. ;-) -Mark Mark

FW: ORA-904 after table rename

2004-01-20 Thread Bobak, Mark
WhoopsMeant to send this to the list, not just Stephen. Mark J. Bobak Oracle DBA ProQuest Company Ann Arbor, MI Imagination was given to man to compensate him for what he is not, and a sense of humor was provided to console him for what he is. --Unknown -Original Message- Sent:

Re: ORA-904 after table rename

2004-01-20 Thread Mladen Gogala
On 01/20/2004 03:39:25 PM, Bobak, Mark wrote: You can also use DBMS_SYSTEM.SET_INT_PARAM_IN_SESSION and DBMS_SYSTEM.SET_BOOL_PARAM_IN_SESSION, in lieu of oradebug. Thanks, Mark! I've learned something from you today! Who says that one cannot teach an old bear new tricks. -- Please see the official

RE: ORA-904 after table rename

2004-01-19 Thread Norris, Gregory T [ITS]
It turns out that the user had configured TOAD to use a table filter, which causes it to create and store a query. As you've probably guessed, the query was referencing a column which no longer exists. On a related note, I initially tried to capture the failing query using alter system set

RE: ORA-904 after table rename

2004-01-19 Thread Chris Stephens
I went through a similar problem with the 904 error. I had to use oradebug to get a trace file to be produced. Good luck, Chris -Original Message- Sent: Monday, January 19, 2004 8:14 AM To: Multiple recipients of list ORACLE-L It turns out that the user had configured TOAD to use a

ORA-904 after table rename

2004-01-16 Thread Norris, Gregory T [ITS]
We're developing some schema update scripts for an in-house application, which includes renaming an existing table, and creating a new version using the original name. No problem... or so I thought. :( All seems well under OEM and SQL+, but I have a developer who consistently gets an ORA-904

Re: ORA-904 after table rename

2004-01-16 Thread jo_holvoet
] Sent by: [EMAIL PROTECTED] 01/16/2004 16:09 Please respond to ORACLE-L To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED] cc: Subject:ORA-904 after table rename We're developing some schema update scripts for an in-house application, which includes