I couldnt get it to work for anyone other than someone in the dba group
already on linux. if you're in the dba group you can connect / as sysdba
anyways, so i guess i'm missing where the security hole is.
joe
[EMAIL PROTECTED] 08/23/01 04:41PM
Okay have a look at bug 1919536, it allows a
To: Multiple recipients of list ORACLE-L
Subject: database upgrade policy?
Hi Listers
I'm on 8.1.6.0.0 and wondering about upgrading to 8.1.6.3.1(?)
as I get the occasional ORA-600/ORA-7445.
Do you upgrade to the latest subversion as a matter of policy
(and not test very much
recipients of list ORACLE-L
Subject: database upgrade policy?
Hi Listers
I'm on 8.1.6.0.0 and wondering about upgrading to 8.1.6.3.1(?)
as I get the occasional ORA-600/ORA-7445.
Do you upgrade to the latest subversion as a matter of policy
(and not test very much) to prevent possible errors
ORACLE-L
Subject: database upgrade policy?
Hi Listers
I'm on 8.1.6.0.0 and wondering about upgrading to 8.1.6.3.1(?)
as I get the occasional ORA-600/ORA-7445.
Do you upgrade to the latest subversion as a matter of policy
(and not test very much) to prevent possible errors
or only upgrade
imp Monkey (and DBA)Ft. Lauderdale, FL,
USA -Original Message- From: Mark Marsden
[SMTP:[EMAIL PROTECTED]] Sent: Wednesday, August 22, 2001
11:45 To: Multiple recipients of list ORACLE-L
Subject: database upgrade policy?
Hi Listers I'm on 8.1.6.0.0 and wondering about upgrading to
8.1.6.3
ORACLE-L
Subject: database upgrade policy?
Hi Listers
I'm on 8.1.6.0.0 and wondering about upgrading to 8.1.6.3.1(?)
as I get the occasional ORA-600/ORA-7445.
Do you upgrade to the latest subversion as a matter of policy
(and not test very much) to prevent possible errors
or only upgrade
t ORACLE-L
Subject: database upgrade policy?
Hi Listers I'm on 8.1.6.0.0 and wondering about upgrading to
8.1.6.3.1(?) as I get the occasional ORA-600/ORA-7445.
Do you upgrade to the latest subversion as a matter of policy (and not
test very much) to prevent possible errors or only upgrade if you have
-
From: Mark Marsden [SMTP:[EMAIL PROTECTED]]
Sent: Wednesday, August 22, 2001 11:45
To: Multiple recipients of list ORACLE-L
Subject: database upgrade policy?
Hi Listers
I'm on 8.1.6.0.0 and wondering about upgrading to 8.1.6.3.1(?)
as I get the occasional ORA-600/ORA-7445.
Do
To: Multiple recipients of list ORACLE-L
Subject: database upgrade policy?
Hi Listers
I'm on 8.1.6.0.0 and wondering about upgrading to 8.1.6.3.1(?)
as I get the occasional ORA-600/ORA-7445.
Do you upgrade to the latest subversion as a matter of policy
(and not test very much) to prevent
On Thu, Aug 23, 2001 at 09:11:56AM -0800, JOE TESTA wrote:
you are crazy :) but i like it anyways.
since i'm running it on a non -supported platform anything i find wouldnt be any
good anyways :)
we'll look forward to you sharing your experiences :)
--
What doesn't kill you will make
AIL PROTECTED]] Sent: Wednesday, August 22, 2001
11:45 To: Multiple recipients of list ORACLE-L
Subject: database upgrade policy?
Hi Listers I'm on 8.1.6.0.0 and wondering about upgrading to
8.1.6.3.1(?) as I get the occasional ORA-600/ORA-7445.
Do you upgrade to the latest subversion a
what was the bug
From: George Schlossnagle [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Subject: Re: database upgrade policy?
Date: Thu, 23 Aug 2001 10:52:29 -0800
We just had a total database lost under 9i. Known bug
omers as there is no
simple way out of this scenario."
Buyer beware.
- Original Message -
From:
JOE
TESTA
To: [EMAIL PROTECTED] ; [EMAIL PROTECTED]
Sent: Thursday, August 23, 2001 2:08
PM
Subject: Re: database upgrade
policy?
George, are you willing to expa
be quite serious for customers as there is no simple way out of
this scenario.
Buyer beware.
- Original Message -
From: JOE TESTA
To: [EMAIL PROTECTED] ; [EMAIL PROTECTED]
Sent: Thursday, August 23, 2001 2:08 PM
Subject: Re: database upgrade policy?
George, are you
In the case of 816, it is desupported in October, so get to 817 ASAP.
In the case of patches, try to watch for problems noted in MetaLink. Things like
SQL*Net Demial Of Service fixes, I like to get them in right away. Otherwise, most
client make me implement if it is not broken, do not patch
George,
Can you go into details about the error please? We are starting testing on
9i, and I AM interested ...
Raj
__
Rajendra Jamadagni MIS, ESPN Inc.
Rajendra dot Jamadagni at ESPN dot com
Any opinion expressed here is
, 2001 11:45
To: Multiple recipients of list ORACLE-L
Subject: database upgrade policy?
Hi Listers
I'm on 8.1.6.0.0 and wondering about upgrading to 8.1.6.3.1(?)
as I get the occasional ORA-600/ORA-7445.
Do you upgrade to the latest subversion as a matter of policy
(and not test very
: database upgrade policy?
Hi Listers
I'm on 8.1.6.0.0 and wondering about upgrading to 8.1.6.3.1(?)
as I get the occasional ORA-600/ORA-7445.
Do you upgrade to the latest subversion as a matter of policy
(and not test very much) to prevent possible errors
or only upgrade if you have
At 03:16 PM 8/23/2001, George Schlossnagle wrote:
DATABASE OPEN RESETLOGS. A choice tidbit from the bug report:
This could be quite serious for customers as there is no simple way out
of this scenario.
i think that wins my vote for understatement of the month!;-)
--
Bill Shrek Thater
Okay have a look at bug 1919536, it allows a user to log in as sysdba when
using sqlplus in 9i.
Initial testing on our system proves that this is true, luckily the db is
locked down except for sys admin and dba group.
Raj
__
Rajendra Jamadagni
Subject: database upgrade policy?
Hi Listers
I'm on 8.1.6.0.0 and wondering about upgrading to 8.1.6.3.1(?) as I
get the occasional ORA-600/ORA-7445.
Do you upgrade to the latest subversion as a matter of policy (and not
test very much) to prevent possible errors or only upgrade if you
]
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Subject: Re: database upgrade policy?
Date: Thu, 23 Aug 2001 11:16:02 -0800
Sure. We seemed to be suffering from bug 1904199 or a variant. We
experienced frequent deadlocks on resources:
Sat Aug 4 08:03:21 2001
Errors in file /opt/db
, USA
-Original Message-
From: Mark Marsden [SMTP:[EMAIL PROTECTED]]
Sent: Wednesday, August 22, 2001 11:45
To: Multiple recipients of list ORACLE-L
Subject: database upgrade policy?
Hi Listers
I'm on 8.1.6.0.0 and wondering about upgrading to 8.1.6.3.1(?)
as I get
Highly depends.
I tend to stay back from the latest versions for some time.
I also tend to upgrade for functionality, and upgrade when I have existing
problems that are told to be fixed.
Sometimes if I start falling back versions and have no reason either way, I
will upgrade my development
Hi Listers
I'm on 8.1.6.0.0 and wondering about upgrading to 8.1.6.3.1(?)
as I get the occasional ORA-600/ORA-7445.
Do you upgrade to the latest subversion as a matter of policy
(and not test very much) to prevent possible errors
or only upgrade if you have problems?
Do you upgrade to major
On Wed, Aug 22, 2001 at 07:45:27AM -0800, Mark Marsden wrote:
Hi Listers
I'm on 8.1.6.0.0 and wondering about upgrading to 8.1.6.3.1(?)
as I get the occasional ORA-600/ORA-7445.
Doc ID: Note:123178.1
Product / Platform: Oracle8i, Release 2 (8.1.6)
Error Correction Support ends on:
Title: RE: database upgrade policy?
Don't upgrade unless there is a very good reason.
All of these are candidates
1. current oracle version is unstable
2. specific bug addressed by an upgrade/patch, as identified by support
3. need to utilize new feature
4. desupport date coming up
We were running 8.1.6.0.0 and just recently encountered the ORA-7445 errors,
which caused core dumps and invalidated the referential integrity of our
database. Oracle recommended the 8.1.6.3 patchset. We decided to skip that
and go for 8.1.7 but for some reason Oracle mailed us the 9i CDs. I
a a glutton for punishment. Dev, sure why not, just dont let the
developers get to attached to the new features, prod?, i wouldnt update any prod
database(unless forced to by oracle corp) until 9.1 at earliest, yes there are
some kewl things, but heck the latest 8.1.7 patchset has 22
-
From: Mark Marsden [SMTP:[EMAIL PROTECTED]]
Sent: Wednesday, August 22, 2001 11:45
To: Multiple recipients of list ORACLE-L
Subject: database upgrade policy?
Hi Listers
I'm on 8.1.6.0.0 and wondering about upgrading to 8.1.6.3.1(?)
as I get the occasional ORA-600/ORA-7445.
Do
Subject: database upgrade policy?
Hi Listers
I'm on 8.1.6.0.0 and wondering about upgrading to 8.1.6.3.1(?)
as I get the occasional ORA-600/ORA-7445.
Do you upgrade to the latest subversion as a matter of policy
(and not test very much) to prevent possible errors
or only upgrade
Certifiable Gimp Monkey (and DBA)
Ft. Lauderdale, FL, USA
-Original Message-
From: Mark Marsden [SMTP:[EMAIL PROTECTED]]
Sent: Wednesday, August 22, 2001 11:45
To: Multiple recipients of list ORACLE-L
Subject: database upgrade policy?
Hi Listers
I'm on 8.1.6.0.0 and wondering about
Just for the PLEASURE of using OUI!
-Original Message-
From: Kevin Kostyszyn [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 22, 2001 6:07 PM
To: Multiple recipients of list ORACLE-L
Subject: RE: database upgrade policy?
I have people here who just want to upgrade
it can turn into HELL.
Lisa Koivu
Certifiable Gimp Monkey (and DBA)
Ft. Lauderdale, FL, USA
-Original Message-
From: Mark Marsden [SMTP:[EMAIL PROTECTED]]
Sent: Wednesday, August 22, 2001 11:45
To: Multiple recipients of list ORACLE-L
Subject: database upgrade policy?
Hi
34 matches
Mail list logo
