Using Oracle 10.2. I'm still learning the basics, and now I'm having a problem with users I've created myself. They can't login. When I attempt to login, I get the error:

The application requires more database privileges than you have
currently been granted.

No hint of what's missing. I have added the CONNECT role to the users, which appears to be the only role needed according to the manual. I also added the RESOURCE role. Finally, I added the SELECT_CATALOG_ROLE and I could login, but there's no mention of that in the manual.

Is CONNECT really the only role needed to login, and why isn't it enough in my case?

Gustaf

On Mar 6, 9:49*am, Gustaf <gust... (AT) algonet (DOT) se> wrote:
You haven't provided enough information to answer that question:

* For which release of Oracle was this application originally written?
* Which release of Oracle (all four or five numbers) are you using
which generates these errors?

CONNECT has been dramatically altered in 10.1.0.x and later releases
of Oracle. The granted privileges have been seriously reduced to
nothing more than CREATE SESSION. In 9.0.1.x and 9.2.0.x the CONNECT
role possessed these additional privileges:

ALTER SESSION
CREATE CLUSTER
CREATE DATABASE LINK
CREATE SEQUENCE
CREATE SYNONYM
CREATE TABLE
CREATE VIEW

Thus an application which relied upon the CONNECT role in 9iR2 and
earlier releases would not properly function against a 10gR1 or later
database.

Provide more information and a better answer may be forthcoming.


David Fitzjarrell

On Mar 6, 9:49*am, Gustaf <gust... (AT) algonet (DOT) se> wrote:
You haven't provided enough information to answer that question:

* For which release of Oracle was this application originally written?
* Which release of Oracle (all four or five numbers) are you using
which generates these errors?

CONNECT has been dramatically altered in 10.1.0.x and later releases
of Oracle. The granted privileges have been seriously reduced to
nothing more than CREATE SESSION. In 9.0.1.x and 9.2.0.x the CONNECT
role possessed these additional privileges:

ALTER SESSION
CREATE CLUSTER
CREATE DATABASE LINK
CREATE SEQUENCE
CREATE SYNONYM
CREATE TABLE
CREATE VIEW

Thus an application which relied upon the CONNECT role in 9iR2 and
earlier releases would not properly function against a 10gR1 or later
database.

Provide more information and a better answer may be forthcoming.


David Fitzjarrell

On Mar 6, 9:49*am, Gustaf <gust... (AT) algonet (DOT) se> wrote:
You haven't provided enough information to answer that question:

* For which release of Oracle was this application originally written?
* Which release of Oracle (all four or five numbers) are you using
which generates these errors?

CONNECT has been dramatically altered in 10.1.0.x and later releases
of Oracle. The granted privileges have been seriously reduced to
nothing more than CREATE SESSION. In 9.0.1.x and 9.2.0.x the CONNECT
role possessed these additional privileges:

ALTER SESSION
CREATE CLUSTER
CREATE DATABASE LINK
CREATE SEQUENCE
CREATE SYNONYM
CREATE TABLE
CREATE VIEW

Thus an application which relied upon the CONNECT role in 9iR2 and
earlier releases would not properly function against a 10gR1 or later
database.

Provide more information and a better answer may be forthcoming.


David Fitzjarrell

On Mar 6, 9:49*am, Gustaf <gust... (AT) algonet (DOT) se> wrote:
You haven't provided enough information to answer that question:

* For which release of Oracle was this application originally written?
* Which release of Oracle (all four or five numbers) are you using
which generates these errors?

CONNECT has been dramatically altered in 10.1.0.x and later releases
of Oracle. The granted privileges have been seriously reduced to
nothing more than CREATE SESSION. In 9.0.1.x and 9.2.0.x the CONNECT
role possessed these additional privileges:

ALTER SESSION
CREATE CLUSTER
CREATE DATABASE LINK
CREATE SEQUENCE
CREATE SYNONYM
CREATE TABLE
CREATE VIEW

Thus an application which relied upon the CONNECT role in 9iR2 and
earlier releases would not properly function against a 10gR1 or later
database.

Provide more information and a better answer may be forthcoming.


David Fitzjarrell

On Mar 6, 12:09*pm, "fitzjarr... (AT) cox (DOT) net" <fitzjarr... (AT) cox (DOT) net> wrote:
Oracle stated a long time ago that the connect and resource roles were
provided only for backward compatiability.

The unnamed application should be using specific object and system
privileges. Check the vendor documentation.

End user applicaitons should not need create privileges. Create
privileges should be necessary only on initial installation.

HTH -- Mark D Powell --

On Mar 6, 12:09*pm, "fitzjarr... (AT) cox (DOT) net" <fitzjarr... (AT) cox (DOT) net> wrote:
Oracle stated a long time ago that the connect and resource roles were
provided only for backward compatiability.

The unnamed application should be using specific object and system
privileges. Check the vendor documentation.

End user applicaitons should not need create privileges. Create
privileges should be necessary only on initial installation.

HTH -- Mark D Powell --

On Mar 6, 12:09*pm, "fitzjarr... (AT) cox (DOT) net" <fitzjarr... (AT) cox (DOT) net> wrote:
Oracle stated a long time ago that the connect and resource roles were
provided only for backward compatiability.

The unnamed application should be using specific object and system
privileges. Check the vendor documentation.

End user applicaitons should not need create privileges. Create
privileges should be necessary only on initial installation.

HTH -- Mark D Powell --

On Mar 6, 12:09*pm, "fitzjarr... (AT) cox (DOT) net" <fitzjarr... (AT) cox (DOT) net> wrote:
Oracle stated a long time ago that the connect and resource roles were
provided only for backward compatiability.

The unnamed application should be using specific object and system
privileges. Check the vendor documentation.

End user applicaitons should not need create privileges. Create
privileges should be necessary only on initial installation.

HTH -- Mark D Powell --

fitzjarrell (AT) cox (DOT) net wrote:

The Oracle version is 10.2.0.1. I don't know what 'application' means here. Is it yet another name for 'user', 'account' and 'schema'? So far, I'm doing everything in Enterprise Manager.

That's what I see too. A new user only has the CONNECT rule by default, and the CONNECT role only has the CREATE SESSION privilege. But that's obviously not enough to use the account.

Gustaf