cancel
Showing results for 
Search instead for 
Did you mean: 

insufficient privileges

Former Member
0 Kudos

SAP table reorganize failing with "ORA-01031: insufficient privileges" reported in the SQLPLUS

user name: conn

password: as sysdba

case1:

C:Documents and SettingsAdministrator>sqlplus

SQL*Plus: Release 10.2.0.2.0 - Production on Mon Aug 8 10:45:12 2011

Copyright (c) 1982, 2005, Oracle. All Rights Reserved.

Enter user-name: conn

Enter password:

ERROR:

ORA-01031: insufficient privileges

case 2:

C:Documents and SettingsAdministrator>sqlplus /nolog @sapdba_role.sql ER1

SQL*Plus: Release 10.2.0.2.0 - Production on Mon Aug 8 10:47:02 2011

Copyright (c) 1982, 2005, Oracle. All Rights Reserved.

SP2-0310: unable to open file "sapdba_role.sql"

SQL>

case 3:

C:Documents and SettingsAdministrator>sqlplus /nolog @sapdba_role.sql SR3

SQL*Plus: Release 10.2.0.2.0 - Production on Mon Aug 8 10:47:02 2011

Copyright (c) 1982, 2005, Oracle. All Rights Reserved.

SP2-0310: unable to open file "sapdba_role.sql"

SQL>

But the file "sapdba_role.sql" was really locates in the local disk.

The file's attributes is write that is this file can read and write.

Can you tell me what´s happen? How can I solve this problem?

Kind regards,

sophia

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Since you are in window. do the following.

Go to the directory where you have placed your .sql file. Suppose it is in C:\Documents and Settings\Administrator>

C:\Documents and Settings\Administrator>sqlplus

SQL*Plus: Release 10.2.0.2.0 - Production on Mon Aug 8 10:45:12 2011

Copyright (c) 1982, 2005, Oracle. All Rights Reserved.

Enter user-name: sys as sysdba <enter>

Put the password or just press enter (it may allow without password)

and in sql prompt

put "@xyz.sql"

Former Member
0 Kudos

Sophia,

Since you are Oracle 10g, take a look at the sapconn role in SAP Note 834917.

Let's try this:

1) Copy the sapconn_role.sql to c:\temp

2) open a cmd prompt

3) cd c:\temp

4) sqlplus /nolog @sapconn_role

If you need to continue looking into the sapdba_role.sql, do the same,

1) copy sapdba_role.sql to c:\temp

2) open a cmd prompt and cd c:\temp

3) run the command per SAP Note 134592

sqlplus /nolog @sapdba_role <schema>

sqlplus /nolog @sapdba_role SR3

NOTE: The schema user is the userid that owns the SAP tables. You can find the schema with:

sqlplus "/as sysdba"

set pages 100

select username from dba_users order by 1;

Do you have a sapr3 or sapsr3 userid? The SAPR3 is from older SAP installations and the SAPSR3 is from newer SAP installations.

Good luck,

Mike Kennedy

former_member204746
Active Contributor
0 Kudos

you are on Windows,

you should be using sidadm user for racle tasks, not Administrator...

problem should be fixed.

Former Member
0 Kudos

Mike,

Thank you very much for answering my questions.

I was following the steps which you have said in the above,the two file can be executed,but it also occurs errors.

the error message is:

ERROR:

ORA-01031:insufficient privileges

I was opened the file 'sapconn_role.sql' and 'sapdba_role.sql' found that

(connect / as sysdba;) in those files.

May be this command occured errors.

I think this command (connect / as sysdba;) equals as the following operatings:

C:\Documents and Settings\Administrator>sqlplus

SQL*Plus: Release 10.2.0.2.0 - Production on Mon Aug 8 10:45:12 2011

Copyright (c) 1982, 2005, Oracle. All Rights Reserved.

Enter user-name: conn

Enter password:

ERROR:

ORA-01031: insufficient privileges

How can I solve this problem?

Kind regards,

sophia

Former Member
0 Kudos

Eric,

thanks you very much.

Could tell me how to find the user "sidadm"?Is this user need to created in the windows system and use this user to login the windows system then executed the above two file?

Please explain me in detail!

Former Member
0 Kudos

Sophia,

As Eric mentioned, you appear to be logging into the windows box with the administrator user, correct? You should be logging in as the <sid>adm user on the windows box. Can you find the user? That would explain why you cannot connect "/as sysdba" since you are logged into the server with the incorrect OS user.

Mike K.