"Van M. Etheridge" wrote:
>
> Hi Ken,
>
> My guess is that you need to set up sys.dba_all_tables with a public
> synonym.
>
> HTH
>
> Van
>
> -Original Message-
> Sent: Thursday, November 29, 2001 11:50 AM
> To: Multiple recipients of list ORACLE-L
>
> 8.1.7 on W2000
>
> select owne
Hi Ken,
My guess is that you need to set up sys.dba_all_tables with a public
synonym.
HTH
Van
-Original Message-
Sent: Thursday, November 29, 2001 11:50 AM
To: Multiple recipients of list ORACLE-L
8.1.7 on W2000
select owner, table_name, tablespace_name from dba_all_tables;
When I
TED]
>Reply-To: [EMAIL PROTECTED]
>To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]>
>Subject: RE: SYS vs SYSTEM
>Date: Fri, 15 Jun 2001 13:27:12 -0800
>
>How about oradim and server manager?
>
>-Original Message-
>Sent: Friday, June 15, 2001 5:02
How about oradim and server manager?
-Original Message-
Sent: Friday, June 15, 2001 5:02 PM
To: Multiple recipients of list ORACLE-L
Trying to connect using INTERNAL via SQLPLUS.
Platform is Solaris 2.6, Oracle 9i. Logged in as oracle user. Oracle user
is a member of the dba group an
>Roles created by a user never go away. They are not attached
>to the user.
Just keep in mind that the role is automatically assigned to the user who
created it. And this can land you in a *bit* of a problem when you import
that user in another database and bump into MAX_ENABLED_ROLES (which
de
Trying to connect using INTERNAL via SQLPLUS.
Platform is Solaris 2.6, Oracle 9i. Logged in as oracle user. Oracle user
is a member of the dba group and CONNECT INTERNAL works fine in 8i.
See following error message for 9i:
ORA-09275: CONNECT INTERNAL is not a valid DBA connection
-Origi
It's gone. And for SYS logins, you must login as "SYS as sysdba" or "SYS as
sysoper".
The threat of internal going away has been around for a long time. It looks
like they finally acted upon it.
Defry
- Original Message -
To: "Multiple recipients of list ORACLE-L" <[EMAIL PROTECTED]>
> Do you use a DBA account? Is there a better way?
Actually I use "connect / as sysdba" for startup and shutdown. That is
probably considered to be connecting as SYS, although I'm not sure if it
exactly the same as "connect sys/".
Since I'm not actually connecting with the SYS account/password
Is it the same old rumor or it could be confirmed 100%?
-Original Message-
Sent: Friday, June 15, 2001 3:26 PM
To: Multiple recipients of list ORACLE-L
Well you will have alot of scripts to change, internal is gone in 9i.
"Walking on water and developing software from a specification a
Ah, you take me for a fool! It's in one file per instance!
And the Rman job is one file per machine - shared by all instances!
thank you, thank you, hat tipping, hat tipping. crowd roaring.
Tom Mercadante
Oracle Certified Professional
-Original Message-
Sent: Friday, June 15, 2001
Well you will have alot of scripts to change, internal is gone in 9i.
"Walking on water and developing software from a specification are easy if
both are frozen."
Christopher R. Spence
Oracle DBA
Fuelspot
-Original Message-
Sent: Friday, June 15, 2001 2:41 PM
To: Multiple recipients
Greg,
I was told by Oracle Support when I started using Rman under version 8.0 to
use SYS or INTERNAL, as it is "better".
Between you and me, "better" is quite subjective. But, I wrote scripts that
connect as INTERNAL, and it has been working fine ever since, so I did not
re-visit it.
Do you u
Well, you could always set synonyms so they wouldn't notice. I typically
make SYS off limits by making the password inaccessible. IDENTIFIED BY
VALUES 'no way';
Henry
-Original Message-
Sent: Friday, June 15, 2001 5:56 AM
To: Multiple recipients of list ORACLE-L
Hi all,
I generally u
Tom,
Why do you use SYS exclusively for startup and shutdown, since your DBA priv
account could also accomplish this?
- Greg
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Greg Moore
INET: [EMAIL PROTECTED]
Fat City Network Services-- (858) 538-5051 FAX: (85
That might be true in Oracle 8, but was a problem in Oracle 7. Just being paranoid.
>>> [EMAIL PROTECTED] 06/15/01 11:11AM >>>
Bill,
Roles created by a user never go away. They are not attached to the user.
They belong to the system (I just tried this in 816 - created a user,
granted CREATE_ROL
Bill,
Roles created by a user never go away. They are not attached to the user.
They belong to the system (I just tried this in 816 - created a user,
granted CREATE_ROLE to that user, connected as that user, created a role and
dropped the user - the role still exists).
Likewise grants to databa
What account I use depends on what I am doing. For example to set up roles, grant
rights, and create users I use the SYSTEM account. For anything else, I use my DBA
account. The reason is that if I ever leave and my account is removed, all those
rights that I granted and all the roles that I cr
it makes absolute sense. And if the developers refuse to understand it,
liken it to running things as root on a Unix box. Too easy to inadvertently
do major damage.
to make their lives easier (and therefore your own), why not create synonyms
for the SYS.x calls you want them to make so t
One thing I noticed is SYSTEM can do about 95% of the things SYS can do.
There isn't a whole lot you cannot do with SYSTEM. But there is some.
Using another account is sound advice as your less likely to own important
objects, and less likely to drop them as you would never prepend SYS. in a
drop
Thats the same as here. We use SYSTEM for all our automated scripts.
-Original Message-
Sent: Friday, June 15, 2001 4:56 AM
To: Multiple recipients of list ORACLE-L
Hi all,
I generally use SYSTEM rather than SYS for DBA work, and would like to
discourage the use of SYS as much as pos
Hi,
I wouldn't use any of the oracle specific users for DBA stuff (except maybe
startup & shutdown)
Create another user with DBA rights.
jack
"Guy Hammond"
Guy:
Maybe I'm too conservative, but I don't even use SYSTEM unless necessary and
I hardly ever use SYS. I will usually create my own account and grant it DBA
privileges. IMHO, your reasoning here is sound. SYS, as you point out, can
do absolutely anything. Therefore, my reasoning is "don't use a
22 matches
Mail list logo
