ORA-01031 Error; please help

Question

hai, iam getting a strange error,
i have this procedure which is created successfully. but giving me insufficient privileges message inserted into error log.
Also when iam writing the create table statement individually, it is creating a table.
create table ACTIVITIES as select * from ACTIVITIES@x_old;
i have dba privilege on the current database
create or replace procedure get_old_tab_scr
is
lv_msg varchar2(500);
lv_code number(10);
begin
for i in (select table_name from user_tables@x_old)
loop
execute immediate 'create table '||i.table_name||' as select * from '||i.table_name||'@x_old';
dbms_output.put_line('create table '||i.table_name||' as select * from '||i.table_name||'@x_old');
end loop;
exception
when others then
lv_code := sqlcode;
lv_msg := sqlerrm;
insert into error_log values('get_old_tab_scr -'||sysdate||lv_code||'-'||lv_msg);
end;
can i get some help regarding this...

Answer 1

Purpose:
~~~~~~~~
Purpose of the document is to show the limitations of roles and privileges under
PL/SQL.
Due to these limitations, you may get errors in PL/SQL procedures/packages when
accessing certain objects or packages, but the same code works in SQL*Plus
The flagged errors are ORA-00942 or ORA-01933 or ORA-01031 and ORA-06512 or
PLS-00201 and ORA-06550 or ORA-28111 with Fine Grained Auditing (FGA)
Note that the generated errors may differ in each release.
Explanation:
~~~~~~~~~~~~
The fundamental misunderstanding with these problems is because of the misconception
that roles that are granted to one user can be applied to another by intermediate
objects such as views or pl/sql procedures, this is not possible, roles exist in
sessions and are associated with a user in an active session only, the privileges
of a role can not be transferred to objects.
If you're accessing tables/views in PL/SQL procedure or package and getting
either ORA-1031 or ORA-942 (or PLS-201), but the same select/update/insert/delete
works ok on SQL*Plus, then you need to check if the privileges have been granted
to the user creating the procedure via a role.
Privileges granted via role are disabled inside stored procedures
Detailed case studies follow: