1. After signing your process, temporarily declare authorization: authidcurrent_user. The Code is as follows: createorreplaceprocedureproc_test_nameauthid
1. After signing your process, temporarily declare authorization: authid current_user. The Code is as follows: create or replace procedure proc_test_name authid
1. After signing your process, temporarily declare authorization: authid current_user.
The Code is as follows:
Create or replace procedure proc_test_name authid current_user
As
Begin
Execute immediate 'create database link dblink_name connect to user_name identified by user_pwd using ''db _ remote ''';
End;
2. authorize your user again.
Grant create database link to user_name (permanent ).
Oracle does not provide a clear explanation of the above operations, and there are few online materials. I discussed the possible cause with my colleagues. It may be a small bug in Oracle permission management. In Oracle, the permission sub-system permission and object permission. dba should be a role-type permission, which indicates that users under this role can do anything ,, however, "You can do it" does not mean you can do it directly, but you still need to "Apply". It is indeed a bit confusing.