8.1.7 on W2000
select owner, table_name, tablespace_name from dba_all_tables;
When I log into sqlplus as SYS is runs.
When I log into sqlplus as SYSTEM I get the error table or view does not
exit.
What is happening here and how do I fix it?
Thanks,
Ken
--
Please see the official ORACLE-L
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
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 owner, table_name,
]
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 PM
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 possible. Partly because it
bypasses auditing and the profile, and also because I tend to regard SYS
as being for Oracle-specific things (like running scripts from
From: Guy Hammond [EMAIL PROTECTED]
Organization: Fat City Network Services, San Diego, California
Reply-To: [EMAIL PROTECTED]
Date: Fri, 15 Jun 2001 01:55:43 -0800
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Subject: SYS vs SYSTEM
Hi all,
I generally use SYSTEM rather
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
recipients of list ORACLE-L [EMAIL PROTECTED]
Subject: SYS vs SYSTEM
Hi all,
I generally use SYSTEM rather than SYS for DBA work, and would like to
discourage the use of SYS as much as possible. Partly because it
bypasses auditing and the profile, and also because I tend to regard SYS
as being
recipients of list ORACLE-L [EMAIL PROTECTED]
Subject: SYS vs SYSTEM
Date: Fri, 15 Jun 2001 01:55:43 -0800
Hi all,
I generally use SYSTEM rather than SYS for DBA work, and would like to
discourage the use of SYS as much as possible. Partly because it
bypasses auditing and the profile, and also
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
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
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_ROLE to
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:
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
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
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
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
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]
Sent:
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
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
20 matches
Mail list logo
