Re: INSTANCE KILLER !!!

There is a nice error like this that involves the to_char and to_date functions. I can't remember the details, but you can bring down the database connect process (with a core-dump) if you put in some wierd date formats (e.g. 'YYYYYYYYYYYYYY'). Check out instances of these two functions.

JJ

Peter Mckenzie wrote in message <7l6kue$41c$1_at_nnrp1.deja.com>...
>I believe I have isolated the problem to a procedure within the package.
>My script was generated by another script and as a result there are a
>lot of spaces on the right hand of each line ( I hadn't bothered to
>remove them yet ). When I manually added a space to one of the lines it
>may have pushed it over a magical limit ? No matter what caused the
>instances to crash the main point I am making is that IT SHOULD NEVER
>HAPPEN. I should get an error when running the script. A parsing
>problem should NEVER bring down a database. THIS IS A SERIOUS ORACLE
>PROBLEM - A TAR HAS BEEN RAISED
>
>
>In article <37737341.59862B2F_at_lucent.com>,
> Kenneth C Stahl <kstahl_at_lucent.com> wrote:
>
>> What may be happening - and this is only a broad guess based on my own
>> experiences with problems that I have handled in the past - is that
>the
>> error you have is something that the parser simply can't make any
>sense of
>> because it doesn't have a rule for it.
>> Ken
>>
>> Peter Mckenzie wrote:
>>
>> > I have a script for creating a database package which kills Oracle
>> > instances when it is run !!!
>
>
>Sent via Deja.com http://www.deja.com/
>Share what you know. Learn what you don't.
Received on Mon Jun 28 1999 - 17:26:06 CDT