cancel
Showing results for 
Search instead for 
Did you mean: 

ORA-01031: insufficient privileges

Former Member
0 Kudos

HI ALL,

Iam tying to backup systems.i am getting following error.

BR0051I BRBACKUP 6.40 (3)

BR0055I Start of database backup: bdvknrrf.afd 2007-06-05 23.30.11

BR0280I BRBACKUP time stamp: 2007-06-05 23.30.12

BR0301E SQL error -1031 at location BrInitOraCreate-1

ORA-01031: insufficient privileges

BR0303E Determination of RDBMS version failed

BR0056I End of database backup: bdvknrrf.afd 2007-06-05 23.30.12

BR0280I BRBACKUP time stamp: 2007-06-05 23.30.12

BR0054I BRBACKUP terminated with errors

Backup was going fine.but i m getting error since the system was restarted once.Seems to be some privilege problem,i applied notes related to sapdbarole,but still the problem is not solved.

The UPDATESTATICS is successful but backup cannot be taken.

Has anyone got this sort of problem.

Please give me suggestions

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Trupti,

Follow Note Number 400241

Regards,

suraj

Answers (5)

Answers (5)

Former Member
0 Kudos

Hi Trupti,

Ask the database administrator to perform the operation or grant the required privileges. For Trusted Oracle users getting this error although granted the the appropriate privilege at a higher label, ask the database administrator to regrant the privilege at the appropriate label.

Regards,

Ganesh

Former Member
0 Kudos

Hi Trupti,

General checks

  • Check whether creating the OPS$ mechanism according to Note 50088 (WINDOWS) or 361641 (UNIX) solves the problem.

  • Table SAPUSER should occur in the system once only and be assigned to user OPS$<sid>ADM. To check this, use the following query:

SELECT OWNER FROM DBA_TABLES WHERE TABLE_NAME = 'SAPUSER';

If the system returns an owner <owner> other than OPS$<sid>ADM, then delete the corresponding SAPUSER tables:

DROP TABLE "<owner>".SAPUSER;

If the system does not return OPS$<sid>ADM, create the SAPUSER table as <sid>adm and enter the password:

CREATE TABLE "OPS$<sid>ADM".SAPUSER

(USERID VARCHAR2(256), PASSWD VARCHAR2(256));

INSERT INTO "OPS$<sid>ADM".SAPUSER VALUES ('<sapowner>', '<password>');

  • This section applies to NT in particular. But if more than one OPS$ user is used under UNIX as well, the checks need to be carried out in the same way.

  • Under NT, it is required that user sapservice<sid> can also access the SAPUSER table. In order to avoid problems with the data consistency, it does not make sense to create an additional SAPUSER table having the same contents. Instead, you should define a synonym. Check if a suitable synonym exists by using the following call:

SELECT OWNER, TABLE_OWNER, TABLE_NAME FROM DBA_SYNONYMS

WHERE SYNONYM_NAME = 'SAPUSER';

As first value, this call should return either OPS$SAPSERVICE<sid> or PUBLIC, followed by OPS$<sid>ADM and SAPUSER. If this is not the case, recreate the synonym after you have deleted it:

If PUBLIC is returned as first value:

DROP PUBLIC SYNONYM SAPUSER;

If another name <name> is returned as first value:

DROP SYNONYM "<name>".SAPUSER;

Now you can recreate the synonym (It is best not to use PUBLIC):

CREATE SYNONYM "OPS$SAPSERVICE<sid>".SAPUSER FOR

"OPS$<sid>ADM".SAPUSER;

To allow access to the synonym (or the associated table), a grant has to be executed. Only the OPS$ user to whom the actual table belongs has the authorization to do this - that is OPS$<sid>ADM. Therefore, you must log on with the corresponding operating system user (<sid>adm) and execute the following commands:

CONNECT /

GRANT SELECT, UPDATE ON SAPUSER TO "OPS$SAPSERVICE<sid>";

  • By default, R3trans uses SAPR3 as database user. With the environment variable, you can define another database user. This makes sense in particular with R/3 6.x, if SAPR3 is replaced by SAP<sid>. If with R/3 <= 4.x, dbs_ora_schema is set to another value than SAPR3, the connect fails since that user exists neither in the database nor in the SAPUSER table. Consequences include errors such as ORA-01403 or ORA-01017. Up to and including 4.6D, dbs_ora_schema should not be set in any user environment.

ORA-01004: default username feature not supported; logon denied

The OPS$ mechanism is not activated in Oracle. To make the general option of an OPS$ connect available, proceed as follows:

  • Set parameter

REMOTE_OS_AUTHENT = TRUE

in init<sid>.ora.

  • Restart the database.

On Windows, you must also set the parameter "SQLNET.AUTHENTICATION_SERVICE = (NTS)" in sqlnet.ora.

Regards,

Suraj

Former Member
0 Kudos

Hi Trupti

The problem lies with the permissions of the binaries in the Oracle directory.

You must be using <SID>ADM user..ryt?

Can you please let me know the Operating System which you are using?

Try starting and stoping oracle using ORA<SID> user and you will be able to log on to Oralce as well as start and stop Oracle database.

Your file permissions are incorrect in the oracle.

If possible please post the list of permissions for the $ORACLE_HOME/bin directory.

Regards

Sumit

[reward with points if useful]

Message was edited by:

Sumit Jain

Former Member
0 Kudos

ORA-1031 is database related.

check the user you are using (ok, ora<SID> is Unix.

check the database roles your db user has, should defnitely have role sapdba.

rerun sapconn.sql

rerun sapdba_role.sql

try again.

peter

Former Member
0 Kudos

the <i>BR0301E SQL error -1031 at location BrDdartRead-1</i> in the note you referenced is not identical to

BR0301E SQL error -1031 at location BrInitOraCreate-1

the problem happens during creating init<sid>.ora. Brbackup is not allowed to overwrite/create the file in %ORACLE_HOME%\database.

Check the security setting of this folder (amoung others, it should include a full access for ORA_<SID>_DBA, ORA_<SID>_OPER). Check that init<SID>.ora is not set to ReadOnly.

Background:

when upgrading to Oracle10 the profile mechanism is switched automatically to spfile<SID>.ora.

To keep br*tools still running (without major code changes) they automatically run the sql-statement <b>Create spfile from pfile;</b> which take a copy of the spfile parameters to the text-based init<SID>.ora.

regards

Peter

Former Member
0 Kudos

Sorry, pls chk the note 917293

Regards

Umesh K

Former Member
0 Kudos

hi

Thanks for your replies.

I have checked the privileges for folder.All access is given.

Also I have check note 917293.But the problem is i cannot connect to oracle as sysdba.I am getting following error.

SQL> connect / as sysdba

ERROR:

ORA-01031: insufficient privileges

Former Member
0 Kudos

Which platform ???

On NT some checks like SQLNET.AUTHENTICATION_SERVICES = (NTS)

Add the user to the ORA_DBA or ORA_sid_DBA group

Usually these things causes the connect error

Former Member
0 Kudos

yes,it isNT

i have checked SQLNET.AUTHENTICATION_SERVICES = (NTS).it is correct.

User is added to group

Former Member
0 Kudos

Hi Trupti,

is the user a local user or a domain user?

If it's a domain user, make sure that no local user with the same name exist. The groups <b>must</b> be local groups, no domain groups.

Best regards,

Elmar.

Former Member
0 Kudos

Hi,

1. check which user you are login, is it local or domain user.

2. check oracle service started or not, check under which user its started, if you have complecate make it oracle server under local user.

then you try connect / as sysdba

Regards

Former Member
0 Kudos

Have u chked 900525

Regards

Umesh K