Home > database >  Call a stored procedure to ora - 01031 and ora - 06512
Call a stored procedure to ora - 01031 and ora - 06512

Time:09-25

As title, in the procedure of board, call a stored procedure called the ora - 01031 and ora - 06512
Check some of the information without permission, but seems to have basic permissions have to foot, what do you suggest,

CodePudding user response:

A stored procedure call, there are two kinds of rights, a caller permissions, one is the owner permissions,

Your current session connection user, and belongs to the user of the process, is the same?

CodePudding user response:

reference 1st floor wmxcn2000 response:
a stored procedure call, there are two kinds of rights, a caller permissions, one is the owner permissions,

Your current session connection user, and belongs to the user of the process, is the same?

It should be the same user,

Error:
ORA - 01031: insufficient privileges
ORA - 06512: an "SYS. DBMS_SESSION", line 108
ORA - 06512: an "TMIS3USER PKG_TMIS_MGMT", line 17

CodePudding user response:

Explicit assign permissions, grant this,

CodePudding user response:

reference wmxcn2000 reply: 3/f
explicitly assign permissions, grant this,

New tmis3user, already with grant permissions,
Just checked, the sys user some authority gives him, but is still the same,

CodePudding user response:

reference wmxcn2000 reply: 3/f
explicitly assign permissions, grant this,

New tmis3user, already with grant permissions,
Just checked, the sys user some authority gives him, but is still the same,

CodePudding user response:

1, the program calls time error, refers to the use of external, such as Java,.net this call? If so check the connect to the database with the user whether right

2, used to create the stored procedure directly test would test error, have a try, change the user line not line

3, to create public synonyms, give you need to use the user permissions

CodePudding user response:

refer to 6th floor xu176032 response:
1, the program calls time error, refers to the use of external, such as Java,.net this call? If so check the connect to the database with the user whether right

2, used to create the stored procedure directly test would test error, have a try, change the user line not line

3, to create public synonyms, assign permissions to you need to use user


Connected users of the data is no problem,



In the application calls the procedure of dbms_session. Clear_context ()
But when an error:
ORA - 01031: insufficient permissions
ORA - 06512: in the "SYS. DBMS_SESSION", line 108
ORA - 06512: in "GIS. PGGIS_SESSION", line 17
ORA - 06512: in the line 1

I login with sys, then grant execute on sys. Dbms_session to TMIS3USER.
But still there is no effect,

CodePudding user response:

The UP

CodePudding user response:

refer to 7th floor AresZone response:
Quote: refer to the sixth floor xu176032 response:

1, the program calls time error, refers to the use of external, such as Java,.net this call? If so check the connect to the database with the user whether right

2, used to create the stored procedure directly test would test error, have a try, change the user line not line

3, to create public synonyms, assign permissions to you need to use user


Connected users of the data is no problem,



In the application calls the procedure of dbms_session. Clear_context ()
But when an error:
ORA - 01031: insufficient permissions
ORA - 06512: in the "SYS. DBMS_SESSION", line 108
ORA - 06512: in "GIS. PGGIS_SESSION", line 17
ORA - 06512: in the line 1

I login with sys, then grant execute on sys. Dbms_session to TMIS3USER.
But still there is no effect,


Use this try:

Grant execute on dbms_session to TMIS3USER

CodePudding user response:

refer to the eighth floor AresZone response:
UP




You can consider this:
http://blog.itpub.net/4227/viewspace-630724/

Is actually, if at first you at the time of setting the context is to specify the package, then it must be set by package, but cannot directly call clear_context function,

Need to pay attention to, when establish context specifies the PACKAGE, then set the context or clear context setting needs to be done through the process of the PACKAGE, if try to directly call SET_CONTEXT or CLEAR_CONTEXT may be insufficient permissions error:

SQL> The EXEC DBMS_SESSION. SET_CONTEXT (' MY_CONTEXT ', 'A', '50')
The BEGIN DBMS_SESSION. SET_CONTEXT (' MY_CONTEXT ', 'A', '50'); END;
*
Line 1 error:
ORA - 01031: insufficient permissions
ORA - 06512: in the "SYS. DBMS_SESSION", line 101
ORA - 06512: in the line 1
SQL> The EXEC DBMS_SESSION. CLEAR_CONTEXT (' MY_CONTEXT, NULL, 'ATTR2')
The BEGIN DBMS_SESSION. CLEAR_CONTEXT (' MY_CONTEXT, NULL, 'ATTR2'); END;
*
Line 1 error:
ORA - 01031: insufficient permissions
ORA - 06512: in the "SYS. DBMS_SESSION", line 115
ORA - 06512: in the line 1

CodePudding user response:

references 9 f yupeigu response:
Quote: refer to 7th floor AresZone response:

Quote: refer to the sixth floor xu176032 response:

1, the program calls time error, refers to the use of external, such as Java,.net this call? If so check the connect to the database with the user whether right

2, used to create the stored procedure directly test would test error, have a try, change the user line not line

3, to create public synonyms, assign permissions to you need to use user


Connected users of the data is no problem,



In the application calls the procedure of dbms_session. Clear_context ()
But when an error:
ORA - 01031: insufficient permissions
ORA - 06512: in the "SYS. DBMS_SESSION", line 108
ORA - 06512: in "GIS. PGGIS_SESSION", line 17
ORA - 06512: in the line 1

I login with sys, then grant execute on sys. Dbms_session to TMIS3USER.
But still there is no effect,


Use this try:

Grant execute on dbms_session to TMIS3USER


Thank you, but this authority also has been given in the past,nullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnull
  • Related