Re: Valid Packages/Procedures/Triggers that are NOT ...
Have you tried checking dba_dependencies for the objects that go invalid? You may see a pattern. Jared On Tue, 2003-11-25 at 13:34, Tony Johnson wrote: > The original problem is that packages go invalid in the middle of the day with no > upgrading going on, > no physical changes happening in the database, nothing happening except the normal > day-to-day operation > of the system. > > We have seen this happening since 8i. > > We recently upgraded to 92040 and I have seen it once in the last week where it > produced a dump - > I dont know how many times it happened where no dump was produced. In 92021 we > could see it multiple > times in a day. > > There is a problem out there that Oracle can't seem to recreate. > > -Original Message- > Mladen Gogala > Sent: Tuesday, November 25, 2003 1:44 PM > To: Multiple recipients of list ORACLE-L > NOT - Found word(s) to be removed remove home list error e-mail in the > Text body. > > > Victoria, there is a whole slew of bugs with upgrade and patch application. > Here are two of them: > > Patch 3099699 > Description REPCA: CATPATCH LEAVES RDBMS UNUSABLE (INVALID OBJECTS IN, LBACSYS > [OLS]) > > Patch 2949941 > Description RULES ENGINE OBJECTS BECOME INVALID AFTER UPGRADE > > > There are quie a few others, not listed here. There was probably a SYS-owned object > left invalid > during upgrade, which caused dependency problems. Solution is to upgrade > to 9.2.0.4 now that you've already upgraded to 9.2.0.1 and run > $ORALCE_HOME/rdbms/utlirp > to recompile all invalid objects in the database. It's always advised to so after any > upgrade or patching of the database. > > On 11/25/2003 02:34:29 PM, [EMAIL PROTECTED] wrote: > > We had a weird situation yesterday on a database that had been upgraded > > from 8.1.6 to 9.2.0.1 over the weekend. Suddenly at 10:30 am, after being > > in production for a day and a half, 93 previously VALID packages, package > > bodies, triggers and procedures went INVALID. We have not been able to > > figure out what made them go invalid (they were all in the same > > application schema). Anyway, we recompiled all objects and all were then > > marked as VALID. However, some of the code still failed to work; (as an > > aside, we narrowed it down to those packages that contained ref cursors). > > Since the packages were apparently VALID, we did not recompile them again > > until after we bounced the database and generally chased our tails for a > > couple of hours. In a last-ditch effort, we recompiled all the objects > > again and the code started working. > > > > Do any of you know of a bug in 9i that would cause an INVALID package to > > be marked VALID? Or, when is a VALID package really INVALID? > > > > Thanks for your input. > > > > Vicki Pierce > > Database Administration > > x2401 > > Mladen Gogala > Oracle DBA > > > > Note: > This message is for the named person's use only. It may contain confidential, > proprietary or legally privileged information. No confidentiality or privilege is > waived or lost by any mistransmission. If you receive this message in error, please > immediately delete it and all copies of it from your system, destroy any hard copies > of it and notify the sender. You must not, directly or indirectly, use, disclose, > distribute, print, or copy any part of this message if you are not the intended > recipient. Wang Trading LLC and any of its subsidiaries each reserve the right to > monitor all e-mail communications through its networks. > Any views expressed in this message are those of the individual sender, except where > the message states otherwise and the sender is authorized to state them to be the > views of any such entity. > > -- > Please see the official ORACLE-L FAQ: http://www.orafaq.net > -- > Author: Mladen Gogala > INET: [EMAIL PROTECTED] > > Fat City Network Services-- 858-538-5051 http://www.fatcity.com > San Diego, California-- Mailing list and web hosting services > - > To REMOVE yourself from this mailing list, send an E-Mail message > to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in > the message BODY, include a line containing: UNSUB ORACLE-L > (or the name of mailing list you want to be removed from). You may > also send the HELP command for other information (like subscribing). > -- > Please see the official ORACLE-L FAQ: http://www.orafaq.net > -- > Author: Tony Johnson > INET: [EMAIL PROTECTED] > > Fat City Network Services-- 858-538-5051 http://www.fatcity.com > San Diego, California-- Mailing list and web hosting services > - > To REMOVE yourself from this mailing list, send an E-Mail message > to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in > the message BODY, include a line containing: UNSUB ORACLE-L > (or th
RE: [***SPAM***] - Re: Valid Packages/Procedures/Triggers that are NOT - Found word(s) to be removed remove home list error e-mail in the Text body.
The original problem is that packages go invalid in the middle of the day with no upgrading going on, no physical changes happening in the database, nothing happening except the normal day-to-day operation of the system. We have seen this happening since 8i. We recently upgraded to 92040 and I have seen it once in the last week where it produced a dump - I dont know how many times it happened where no dump was produced. In 92021 we could see it multiple times in a day. There is a problem out there that Oracle can't seem to recreate. -Original Message- Mladen Gogala Sent: Tuesday, November 25, 2003 1:44 PM To: Multiple recipients of list ORACLE-L NOT - Found word(s) to be removed remove home list error e-mail in the Text body. Victoria, there is a whole slew of bugs with upgrade and patch application. Here are two of them: Patch 3099699 Description REPCA: CATPATCH LEAVES RDBMS UNUSABLE (INVALID OBJECTS IN, LBACSYS [OLS]) Patch 2949941 Description RULES ENGINE OBJECTS BECOME INVALID AFTER UPGRADE There are quie a few others, not listed here. There was probably a SYS-owned object left invalid during upgrade, which caused dependency problems. Solution is to upgrade to 9.2.0.4 now that you've already upgraded to 9.2.0.1 and run $ORALCE_HOME/rdbms/utlirp to recompile all invalid objects in the database. It's always advised to so after any upgrade or patching of the database. On 11/25/2003 02:34:29 PM, [EMAIL PROTECTED] wrote: > We had a weird situation yesterday on a database that had been upgraded > from 8.1.6 to 9.2.0.1 over the weekend. Suddenly at 10:30 am, after being > in production for a day and a half, 93 previously VALID packages, package > bodies, triggers and procedures went INVALID. We have not been able to > figure out what made them go invalid (they were all in the same > application schema). Anyway, we recompiled all objects and all were then > marked as VALID. However, some of the code still failed to work; (as an > aside, we narrowed it down to those packages that contained ref cursors). > Since the packages were apparently VALID, we did not recompile them again > until after we bounced the database and generally chased our tails for a > couple of hours. In a last-ditch effort, we recompiled all the objects > again and the code started working. > > Do any of you know of a bug in 9i that would cause an INVALID package to > be marked VALID? Or, when is a VALID package really INVALID? > > Thanks for your input. > > Vicki Pierce > Database Administration > x2401 Mladen Gogala Oracle DBA Note: This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Wang Trading LLC and any of its subsidiaries each reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorized to state them to be the views of any such entity. -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Mladen Gogala INET: [EMAIL PROTECTED] Fat City Network Services-- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Tony Johnson INET: [EMAIL PROTECTED] Fat City Network Services-- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
Re: Valid Packages/Procedures/Triggers that are NOT
Victoria, there is a whole slew of bugs with upgrade and patch application. Here are two of them: Patch 3099699 Description REPCA: CATPATCH LEAVES RDBMS UNUSABLE (INVALID OBJECTS IN, LBACSYS [OLS]) Patch 2949941 Description RULES ENGINE OBJECTS BECOME INVALID AFTER UPGRADE There are quie a few others, not listed here. There was probably a SYS-owned object left invalid during upgrade, which caused dependency problems. Solution is to upgrade to 9.2.0.4 now that you've already upgraded to 9.2.0.1 and run $ORALCE_HOME/rdbms/utlirp to recompile all invalid objects in the database. It's always advised to so after any upgrade or patching of the database. On 11/25/2003 02:34:29 PM, [EMAIL PROTECTED] wrote: > We had a weird situation yesterday on a database that had been upgraded > from 8.1.6 to 9.2.0.1 over the weekend. Suddenly at 10:30 am, after being > in production for a day and a half, 93 previously VALID packages, package > bodies, triggers and procedures went INVALID. We have not been able to > figure out what made them go invalid (they were all in the same > application schema). Anyway, we recompiled all objects and all were then > marked as VALID. However, some of the code still failed to work; (as an > aside, we narrowed it down to those packages that contained ref cursors). > Since the packages were apparently VALID, we did not recompile them again > until after we bounced the database and generally chased our tails for a > couple of hours. In a last-ditch effort, we recompiled all the objects > again and the code started working. > > Do any of you know of a bug in 9i that would cause an INVALID package to > be marked VALID? Or, when is a VALID package really INVALID? > > Thanks for your input. > > Vicki Pierce > Database Administration > x2401 Mladen Gogala Oracle DBA Note: This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Wang Trading LLC and any of its subsidiaries each reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorized to state them to be the views of any such entity. -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Mladen Gogala INET: [EMAIL PROTECTED] Fat City Network Services-- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
Re: Valid Packages/Procedures/Triggers that are NOT
Hi Victoria Are you sure that nobody alter some table or view include in these pkgs ??. Mariano Database Administrator. From: [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]> Subject: Valid Packages/Procedures/Triggers that are NOT Date: Tue, 25 Nov 2003 11:34:29 -0800 We had a weird situation yesterday on a database that had been upgraded from 8.1.6 to 9.2.0.1 over the weekend. Suddenly at 10:30 am, after being in production for a day and a half, 93 previously VALID packages, package bodies, triggers and procedures went INVALID. We have not been able to figure out what made them go invalid (they were all in the same application schema). Anyway, we recompiled all objects and all were then marked as VALID. However, some of the code still failed to work; (as an aside, we narrowed it down to those packages that contained ref cursors). Since the packages were apparently VALID, we did not recompile them again until after we bounced the database and generally chased our tails for a couple of hours. In a last-ditch effort, we recompiled all the objects again and the code started working. Do any of you know of a bug in 9i that would cause an INVALID package to be marked VALID? Or, when is a VALID package really INVALID? Thanks for your input. Vicki Pierce Database Administration x2401 _ Charla con tus amigos en línea mediante MSN Messenger: http://messenger.latam.msn.com/ -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: mar666 mar666 INET: [EMAIL PROTECTED] Fat City Network Services-- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
RE: Valid Packages/Procedures/Triggers that are NOT
We have been seeing this ever since we went to 9i and in multiple calls to Oracle support they have not been of much help. Most of the time we get an error dump in udumo and things go on there merry way. A couple of times the packages go invalid and wont work but when looking at them thru OEM or other ways they all appear to be vaild. We do a complete recompile of everything and we are back up and running. -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of [EMAIL PROTECTED]Sent: Tuesday, November 25, 2003 12:34 PMTo: Multiple recipients of list ORACLE-LSubject: Valid Packages/Procedures/Triggers that are NOTWe had a weird situation yesterday on a database that had been upgraded from 8.1.6 to 9.2.0.1 over the weekend. Suddenly at 10:30 am, after being in production for a day and a half, 93 previously VALID packages, package bodies, triggers and procedures went INVALID. We have not been able to figure out what made them go invalid (they were all in the same application schema). Anyway, we recompiled all objects and all were then marked as VALID. However, some of the code still failed to work; (as an aside, we narrowed it down to those packages that contained ref cursors). Since the packages were apparently VALID, we did not recompile them again until after we bounced the database and generally chased our tails for a couple of hours. In a last-ditch effort, we recompiled all the objects again and the code started working. Do any of you know of a bug in 9i that would cause an INVALID package to be marked VALID? Or, when is a VALID package really INVALID? Thanks for your input. Vicki PierceDatabase Administrationx2401
RE: Valid Packages/Procedures/Triggers that are NOT
db will _try_ to recompile any code that is encountered after it gets marked as invalid. So, it may not be a bug after all. Raj Rajendra dot Jamadagni at nospamespn dot com All Views expressed in this email are strictly personal. QOTD: Any clod can have facts, having an opinion is an art ! -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]Sent: Tuesday, November 25, 2003 2:34 PMTo: Multiple recipients of list ORACLE-LSubject: Valid Packages/Procedures/Triggers that are NOTWe had a weird situation yesterday on a database that had been upgraded from 8.1.6 to 9.2.0.1 over the weekend. Suddenly at 10:30 am, after being in production for a day and a half, 93 previously VALID packages, package bodies, triggers and procedures went INVALID. We have not been able to figure out what made them go invalid (they were all in the same application schema). Anyway, we recompiled all objects and all were then marked as VALID. However, some of the code still failed to work; (as an aside, we narrowed it down to those packages that contained ref cursors). Since the packages were apparently VALID, we did not recompile them again until after we bounced the database and generally chased our tails for a couple of hours. In a last-ditch effort, we recompiled all the objects again and the code started working. Do any of you know of a bug in 9i that would cause an INVALID package to be marked VALID? Or, when is a VALID package really INVALID? Thanks for your input. Vicki PierceDatabase Administrationx2401**This e-mail message is confidential, intended only for the named recipient(s) above and may contain information that is privileged, attorney work product or exempt from disclosure under applicable law. If you have received this message in error, or are not the named recipient(s), please immediately notify corporate MIS at (860) 766-2000 and delete this e-mail message from your computer, Thank you.**4
