It's the new way, the INN thing.
-Original Message-
Sent: Saturday, August 16, 2003 10:29 PM
To: Multiple recipients of list ORACLE-L
I have created my first 9i database on OS/390 v2.10.
On my Oracle 8i instance, I can connect to the database
using:
sys/[EMAIL PROTECTED]
The security is not as bad as it sounds.
The patch is to release major software and the
user gets prompted to enter the password. It
is not stored any place (just UNIX variables
during the running of the release). The
software upgrades are released once every
six months to year.
Not all patches re
Hi!
Note that if you set your init.ora parameter o7_dictionary_accessibility to
true, then you can connect as sys *without* sysdba or sysoper. But setting
this parameter to true (old behaviour) isn't a good idea anymore, but might
work for patching & maintenance type of work.
Tanel.
- Origin
First off, you should not be connecting as sys on a regular basis, so making it harder
is a good thing. Makes us think about what we're doing. Anyway, my experience is
that whenever you want to connect as SYS you have to do so AS SYSDBA.
Dick Goulet
Senior Oracle DBA
Oracle Certified 8i DBA
-
CREATE PUBLIC SYNONYM is a permission I'll give away freely, even to a PHB.
It's DROP PUBLIC SYNONYM that really needs some thought...
Installing Oracle in a shop that has never used UNIX or Oracle before is
never cheap, whether I do it or not. This particular shop was
OpenVMS/Ingres coming into
A manager who has to create public synonyms himself! Ordinarily I would have
had nothing but pure respect for the man who is obviously such a grease
monkey; but he proved to be just a monkey.
Damagement title with sys password; boy how I hate to be DBA there! No, to
be _anything_ there.
Arup Nand
On 2003.08.17 23:39, Tim Gorman wrote:
Babette,
Just this Friday, I was wrapping up an installation engagement and one of
the last things we did was change all the passwords. Standard practice.
Immediately, one of the development managers comes boiling out of his office
screaming "Who changed the
Babette,
This is how database security unravels. Pretty soon, the password to SYS is
embedded everywhere, used everywhere, and everyone knows it. Thus, the DBA
ends up with the pager and responsibility for fixing stuff, but everyone
else can cause that pager to go off with a stupid goof at 3:00a
Babette,
You can still achieve the objective using SYSTEM, which does not require a
SYSDBA connection. Or for that matter any user with DBA role. The trick is a
new privilege named "grant any object privilege"; any user with that
privilege can grant anything on objects owned by other schema. If yo
Well, you don't need to log on as sys to do that. There is a
new privilege in 9i (granted to DBA role, of course) called
"GRANT ANY OBJECT PRIVILEGE", which enables the DBA to grant
object privileges on objects belonging to other user. You can
easily log in as "system" and grant select on sys.dba_
Tim / Peter / Michael
Thanks for the information. I was afraid of that.
We have a patching mechanism and need to logon as
sys to grant access to sys objects for part of
the process. (to grant select on sys.dba_free_space
and execute on sys.dbms_util).
However, the patching mechanism only does a
In Oracle9i, SYS requires connecting as a privileged user using the
sysdba parameter. This is equivalent to "connect internal" in Oracle8i
which is now obsolete in Oracle9i.
-Original Message-
Sent: Sunday, August 17, 2003 12:29 AM
To: Multiple recipients of list ORACLE-L
I have create
Hi Babette
This is a feature of 9i. using SYS you have to always use "as sysdba "
same thing on Windows and Solaris at least and I am sure it is all other
OS's
Cheers
--
=
Peter McLarty E-mail: [EMAIL PROTECTED]
Technical Consultant
It's a 9i thing, across all platforms.
on 8/16/03 9:29 PM, Babette Turner-Underwood at [EMAIL PROTECTED] wrote:
>
> I have created my first 9i database on OS/390 v2.10.
>
> On my Oracle 8i instance, I can connect to the database
> using:
>
> sys/[EMAIL PROTECTED]
>
> HOWEVER, In Oracle 9i,
14 matches
Mail list logo
