Category Archives: privileges

Oracle 12c – User privilege analysis

April 11, 2017 Larry Catt Leave a comment

Oracle 12c gives the ability to perform a user privilege analysis to bounce against granted privileges. This allows you to reduce granted privilege down to what the individual user actually needs and no more. This article gives a procedure to perform User privilege analysis.

Logon oracle server as the oracle software owner than logon to sqlplus with sysdba privilegs. If this is done by none privileged user account, the user must have the CAPTURE_ADMIN role granted.

[root@linux2 ~]# su – oracle

Last login: Thu Dec 15 07:50:00 EST 2016 on pts/1

Enter database to use:

1 – ORCL

2 – CDB1

Option >

[oracle@linux2 ~]$ sqlplus / as sysdba

SQL*Plus: Release 12.1.0.2.0 Production on Thu Dec 15 13:05:59 2016

Connected to:

Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 – 64bit Production

With the Partitioning, OLAP, Advanced Analytics, Real Application Testing

and Unified Auditing options

SQL>

Define the privilege analysis policy with the CREATE_CAPTURE procedure of DBMS_PRIVILEGE_CAPTURE package. This example below will capture all privileges used.

BEGIN

DBMS_PRIVILEGE_CAPTURE.CREATE_CAPTURE(

name => ‘user_priv_capture’,

description => ‘Capture the privileges by user test’,

type => DBMS_PRIVILEGE_CAPTURE.G_DATABASE);

END;

Enable the privilege analysis policy.

SQL> EXEC DBMS_PRIVILEGE_CAPTURE.ENABLE_CAPTURE (‘user_priv_capture’);

PL/SQL procedure successfully completed.

SQL>

Logon as the user test and perform DML processing.

SQL> connect test/test

Connected.

SQL> insert into test.test_times(pers_id, first_name) values(99,’test’);

1 row created.

SQL> commit;

Commit complete.

SQL> exit

Disconnected from Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 – 64bit Production

With the Partitioning, OLAP, Advanced Analytics, Real Application Testing

and Unified Auditing options

[oracle@linux2 ~]$

Logon as sysdba and disable the privilege analysis policy’s recording of privilege use.

[oracle@linux2 ~]$ sqlplus / as sysdba

SQL*Plus: Release 12.1.0.2.0 Production on Thu Dec 15 13:25:29 2016

Connected to:

Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 – 64bit Production

With the Partitioning, OLAP, Advanced Analytics, Real Application Testing

and Unified Auditing options

SQL> EXEC DBMS_PRIVILEGE_CAPTURE.DISABLE_CAPTURE (‘user_priv_capture’);

PL/SQL procedure successfully completed.

SQL>

Generate privilege analysis results.

SQL> EXEC DBMS_PRIVILEGE_CAPTURE.GENERATE_RESULT (‘user_priv_capture’);

PL/SQL procedure successfully completed.

SQL>

Query the table dba_used_privs to see privileges used during the capture period.

SQL> column username format a12

column sys_priv format a15

column object_owner format a10

column object_name format a25

set pagesize 500

SELECT username, sys_priv, object_owner, object_name FROM dba_used_privs WHERE capture = ‘user_priv_capture’;

SQL> SQL> SQL> SQL> SQL>

USERNAME SYS_PRIV OBJECT_OWN OBJECT_NAME

———— ————— ———- ————————-

TEST CREATE SESSION

TEST SYS USER_TABLES

APEX_040200 SYS DBMS_OUTPUT

TEST CREATE SESSION

TEST SYS DUAL

APEX_040200 SYS DBMS_OUTPUT

TEST CREATE SESSION

TEST SYS DUAL

APEX_040200 SYS DEFAULT_JOB_CLASS

TEST CREATE SESSION

TEST SYSTEM PRODUCT_PRIVS

TEST SYS DBMS_APPLICATION_INFO

17 rows selected.

SQL>

Optionally, drop the privilege analysis policy.

EXEC DBMS_PRIVILEGE_CAPTURE.DROP_CAPTURE (‘user_priv_capture’);

Larry Catt

OCP

12c, Administration, privileges, Users

Oracle 12c – User privilege analysis overview

March 18, 2017 Larry Catt Leave a comment

Oracle 12c contains the feature to analyze the privileges actually used by an individual user account in order to implement least privilege policies within the RDBMS. This article gives an overview of User privilege analysis in Oracle 12c.

Privilege analysis is provided by Oracle Data Vault and it allows for creation of profile which captures system and object privileges used by a user.
This profile can be used to bounce used privileges against granted privileges.
You can reduce privileges that are not in use through this analysis.
It is possible to perform privilege analysis with or without have Database Vault configured and enabled.
It is possible to administer privilege analysis by EM Cloud Control or the package DBMS_PRIVILEGE_CAPTURE
The role CAPTURE_ADMIN grants execute privilege on DBMS_PRIVILEGE_CAPTURE package and select on views to results.
The DBMS_PRIVILEGE_CAPTURE package allows you to create/enable/disable/drop privilege analysis policies.
Only one privilege analysis policy can be enabled in the database at a time, but the DBMS_PRIVILEGE_CPATURE.G_DATABASE privilege analysis can be done with one other user defined policy at the same time.
Analysis policies running will still be running after DB restart.
Privilege analysis policies must be disabled, before reports can be generated.
Policies must be disabled before they are dropped.
Dropping a privilege policy, also drops all collected data by that policy.
List of some view available with Privilege Analysis:
1. DBA_PRIV_CAPTURES — Lists information about existing privilege analysis policies
2. DBA_USED_PRIVS — Lists the privileges that have been used for reported privilege analysis policies
3. DBA_UNUSED_PRIVS — Lists the privileges that have not been used for reported privilege analysis policies
4. DBA_USED_OBJPRIVS — Lists the object privileges that have been used for reported privilege analysis policies. It does not include the object grant paths.
5. DBA_UNUSED_OBJPRIVS — Lists the object privileges that have not been used for reported privilege analysis policies. It does not include the object privilege grant paths.
6. DBA_USED_SYSPRIVS — Lists the system privileges that have been used for reported privilege analysis policies. It does not include the system privilege grant paths.
7. DBA_UNUSED_SYSPRIVS — Lists the system privileges that have not been used for reported privilege analysis policies. It does

Larry Catt

OCP

12c, CDB, Multitenant, PDB, privileges, Users

Users accounts in Multitenant Database

November 19, 2016 Larry Catt Leave a comment

Oracle 12c multitenant database consist of a CDB which houses one or more PDB which house application data. Now this design has direct implications on user accounts and how they are implemented. This article attempts to briefly cover the implementation of user accounts in the Oracle 12c multitenant architecture.

Oracle 12c multitenant database have two class of user accounts: Common and Local. Common users belong to the root container (CDB) and have full access to PDBs within the CDB. Local users belong a particular PDB and do not have access to the root container (CDB) which houses them. They following rules govern User accounts in the multitenant database architecture:

Common user have the same identity in the root and every PDB.
Common users can connect to root and PDB.
Common users connected to root can perform ALTER PLUGGABLE DATABASE, CREATE USER/ROLE that affect multiple PDBs.
Local users apply to only one PDB.
Local users cannot connect to CDB their PDB is contained in.
Local users cannot cross PDBs but same username can exist in two different PDB in same CDB.
Most privileges only apply in current container. IE user must first connect to container to query tables in that container and they cannot do it from the root.

Larry Catt

OCP

12c, CDB, Multitenant, PDB, privileges, Users

Privileges of Local Users in Oracle Multitenant Database

October 2, 2015 Larry Catt Leave a comment

In Oracle Multitenant Databases, local users only have access and privileges to a single PDB and not the CDB. You can have the same user name across multiple PDBs housed in the same CDB, but the users share no privileges and only shares a common name. This procedure give a brief overview of local user privileges in Oracle 12c Multitenant Databases. Listed below are the stated restriction on local user privileges.

A privilege granted locally can only be used in that container, even if granted by common user.
Both common and local users can grant privileges locally.
Both common and local users can grant privileges to other common or local users.
Grantor must connect to container and specify CONTAINER=CURRENT clause.
Common and Local user can grant privileges locally if they have appropriate privileges.

A privilege granted locally can only be used in that container, even if granted by common user.

As the common user c##dba logon to pdb1 and pdb2 creating users user_local.

SQL> connect c##dba/password@pdb1

Connected.

SQL> create user user_local identified by password;

User created.

SQL> connect c##dba/password@pdb2

Connected.

SQL> create user user_local identified by password;

User created.

SQL>

Now connect to pdb1 as c##dba and grant the user user_local the DBA role. Connect as user_local and create an additional local user user_test. NOTE: The user user_local can successfully connect to pdb1 and create an additional local user in this PDB.

SQL> connect c##dba/password@pdb1

Connected.

SQL> grant dba to user_local;

Grant succeeded.

SQL> connect user_local/password@pdb1

Connected.

SQL> create user user_test identified by password;

User created.

SQL>

Now attempt to connect to pdb2 with local user user_local. NOTE: The user user_local does not even have permission to connect to pdb2, even though the user exists in pdb2.

SQL> connect user_local/password@pdb2

ERROR:

ORA-01045: user USER_LOCAL lacks CREATE SESSION privilege; logon denied

Warning: You are no longer connected to ORACLE.

SQL>

Both common and local users can grant privileges locally.

Using local_user created above from pdb1, you can grant privileges to the newly created user user_test logon as local_user.

SQL> connect user_local/password@pdb1

Connected.

SQL> grant resource to user_test;

Grant succeeded.

SQL>

Both common and local users can grant privileges to other common or local users.

Using local_user created above from pdb1, you can grant privileges to the newly created user user_test logon as local_user.

SQL> connect user_local/password@pdb1

Connected.

SQL> grant resource to user_test;

Grant succeeded.

SQL>

Grantor must connect to container and specify CONTAINER=CURRENT clause or specify no CONTAINER clause. CONTAINER=ALL is not available in PDB.

As the user_local grant resource to user_test without a container clause and CONTAINER=ALL clause.

SQL> connect user_local/password@pdb1

Connected.

SQL> grant resource to user_test;

Grant succeeded.

SQL> grant resource to user_test container=all;

grant resource to user_test container=all

ERROR at line 1:

ORA-65029: a Local User may not grant or revoke a Common Privilege or Role

SQL>

Common and Local user can grant privileges locally if they have appropriate privileges.

Local user_local can create additional users in PDB pdb1 once the user has been granted the DBA role.

SQL> connect c##dba/password@pdb1

Connected.

SQL> grant dba to user_local;

Grant succeeded.

SQL> connect user_local/password@pdb1

Connected.

SQL> create user user_test identified by password;

User created.

SQL>

This completes the overview of privileges for local users in Oracle 12c Multitenant Database.

Larry Catt

OCP

12c, CDB, Multitenant, privileges, Users

Privileges of Common Users in Oracle Multitenant Database

September 21, 2015 Larry Catt Leave a comment

Privileges for Common Users in Oracle 12c multitenant database architecture have unique constraints allowing for privileges at the CDB level and the PDB levels. Common users may or may not have privileges at all containers in the multitenant database or they may be restricted to only a few. Additionally, privileges maybe restricted to objects in individual containers. The following are general rules governing privileges of common users and we will examine each rule in the below procedures:

A privilege granted commonly can be used in every container and future container.
Only common users can grant common privileges.
Granter of common privileges must connect to root and specify CONTAINER=ALL clause.
Can include system and object privilege.
Privileges should never be given to public.

A privilege granted commonly can be used in every container and future container.

Using the common user C##DBA we will create the user at the CDB level and grant DBA privileges with the CONTAINER clause equal to all.

SQL> show con_name

CON_NAME

——————————

CDB$ROOT

SQL> create user c##dba identified by password;

User created.

SQL> grant dba to c##dba container=all;

Grant succeeded.

SQL> connect c##dba/password@cdb1;

Connected.

SQL> create user c##user identified by password container=all;

User created.

SQL>

Now alter the session to container PDB1 as the same user and create a user there. NOTE: Permissions are good both in CDB1 and PDB1 for Common users. This is true because container clause was set to ALL.

SQL> show user

USER is “C##DBA”

SQL> alter session set container=PDB1;

Session altered.

SQL> show user

USER is “C##DBA”

SQL> create user pdb1_user identified by password;

User created.

SQL>

Only common users can grant common privileges.

As the common user c##dba grant resource to common user c##user.

SQL> connect c##dba/password@cdb1;

Connected.

SQL> grant resource to c##user;

Grant succeeded.

SQL>

Granter of common privileges must connect to root and specify CONTAINER=ALL clause for privileges to be granted in all containers.

This one is a little tricky because it appears that you can do it, however the key is common privilege, you can have privileges in the CDB and a few PDB and it not be common. This procedure shows an example of this scenario.
Connect to PDB1 as the common user c##dba and grant dba to the user c##user.

SQL> connect c##dba/password@pdb1

Connected.

SQL> grant dba to c##user;

Grant succeeded.

SQL>

Now a user with common privilege of DBA should be able to connect to any PDB in the CDB, however when we try to connect to pdb2, it fails. Further more when we look at the view dba_role_privs, we note that user C##USER does have DBA role, but not commonly.

SQL> connect c##user/password@pdb2

ERROR:

ORA-01045: user C##USER lacks CREATE SESSION privilege; logon denied

Warning: You are no longer connected to ORACLE.

SQL> connect c##dba/password@pdb1

Connected.

SQL> column grantee format a30

select grantee, common from dba_role_privs where grantee=’C##USER’;

SQL>

GRANTEE COM

—————————— —

C##USER NO

SQL>

Now logon to the root container as the C##DBA user and grant the DBA role to C##USER. Then view the dba_role_privs table and attempt to connect to PDB2.

SQL> connect c##dba/password@cdb1

Connected.

SQL> grant dba to c##user container=all;

Grant succeeded.

SQL> column grantee format a30

select grantee, common from dba_role_privs where grantee=’C##USER’;

SQL>

GRANTEE COM

—————————— —

C##USER NO

C##USER YES

SQL> connect c##user/password@pdb2

Connected.

SQL>

Can include system and object privilege.

Revoke all rights from user C##USER. If you are following from the above example, the user C##USER has been granted the DBA role twice locally and once commonly. So revoke Common grant at ROOT container and local root grant. Then connect to PDB1 to remove local grant at PDB1.

SQL> connect c##dba/password@cdb1

Connected.

SQL> column grantee format a30

select grantee, common from dba_role_privs where grantee=’C##USER’;

SQL>

GRANTEE COM

—————————— —

C##USER NO

C##USER YES

SQL> revoke dba from c##user container=ALL;

Revoke succeeded.

SQL> column grantee format a30

select grantee, common from dba_role_privs where grantee=’C##USER’;

SQL>

GRANTEE COM

—————————— —

C##USER NO

SQL> revoke dba from c##user container=current;

Revoke succeeded.

SQL> column grantee format a30

select grantee, common from dba_role_privs where grantee=’C##USER’;

SQL>

GRANTEE COM

—————————— —

C##USER NO

SQL> connect c##dba/password@pdb1

Connected.

SQL> revoke dba from c##user;

Revoke succeeded.

SQL>

SQL> column grantee format a30

select grantee, common from dba_role_privs where grantee=’C##USER’;

SQL>

no rows selected

SQL>

Now reconnect to C##DBA at the root level and grant connect and select on V$SESSIONS commonly the user C##USER. To test common privilege to objects.

SQL> connect c##dba/password@cdb1

Connected.

SQL> grant create session to c##user container=all;

Grant succeeded.

SQL> grant select on sys.v_$session to c##user container=all;

Grant succeeded.

SQL>

Connect the C##USER and execute a select statement on v$session and v$sql objects to validate access from root container. NOTE: We are able to access object v$session but not v$sql.

SQL> connect c##user/password@cdb1

Connected.

SQL> select count(*) from v$session;

COUNT(*)

———-

SQL> select count(*) from v$sql;

select count(*) from v$sql

ERROR at line 1:

ORA-00942: table or view does not exist

SQL>

Connect to PDB1 and repeat the above queries to validate common access privileges to objects.

SQL> connect c##user/password@pdb1

Connected.

SQL> select count(*) from v$session;

COUNT(*)

———-

SQL> select count(*) from v$sql;

select count(*) from v$sql

ERROR at line 1:

ORA-00942: table or view does not exist

SQL>

Privileges should never be given to public from common account.

Once a privilege is granted to public, all users have access to that privilege, which is a huge security risk. However, there is no restrictions built into Oracle to prevent this from occurring. We will demonstrate this by the creation of new user c##dba2, grant the new user no privileges, grant dba role to public, connect to both the CDB and PDB, and finally create a user. This is extremely dangerous, because granting privileges to public grants access to system and object privileges to every user. Finally we will revoke DBA role from public and note that the new user c##dba2 can no longer connect.

SQL> connect / as sysdba

Connected.

SQL> alter session set container=cdb$root;

Session altered.

SQL> create user c##dba2 identified by password;

User created.

SQL> grant dba to public container=all;

Grant succeeded.

SQL> connect c##dba2/password@cdb1

Connected.

SQL> connect c##dba2/password@pdb1

Connected.

SQL> create user testing identified by password;

User created.

SQL> connect / as sysdba

Connected.

SQL> revoke dba from public container=all;

Revoke succeeded.

SQL> connect c##dba2/password@cdb1

ERROR:

ORA-01045: user C##DBA2 lacks CREATE SESSION privilege; logon denied

Warning: You are no longer connected to ORACLE.

SQL>

This completes overview of Privileges for Common Users in Oracle Multitenant Databases.

Larry Catt

OCP

11g, Oracle, Oracle 10g, oracle 9i, privileges, script, SQL, sqlplus

Oracle – ORA-00604: error occurred at recursive SQL level 1 and revoking a user privileges.

January 17, 2009 Larry Catt Leave a comment

A schema is considered all of the objects owned by a single user within the Oracle database. When a user has a privilege revoked in the database, but owns a particular object which requires that privilege, errors will result. This article will recover an error which will result from a user having a privilege revoked which is require by one of the objects he owns.

1. Logon to your Oracle database server as the Oracle software owner.

2. Logon to SQLPLUS with SYSDBA privileges.

mylinux:> sqlplus ‘/ as sysdba’

SQL*Plus: Release 10.2.0.4.0 – Production on Sat Jan 17 11:00:09 2009

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

Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 – 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL>

3. Create the user LJCATT and grant him the DBA role and create procedure privileges.

SQL> create user ljcatt identified by password10;

User created.

SQL> grant dba to ljcatt;

Grant succeeded.

SQL> grant execute on utl_file to ljcatt;

Grant succeeded.

4. Connect as the user ljcatt and create a procedure named test_file.

SQL> connect ljcatt
Enter password:
Connected.

SQL> create or replace procedure test_file
is
2 3 v_record varchar2(50) := ‘Testing file creation’;
4 v_file varchar2(30) := ‘testfile’;
5 v_dir varchar2(100) := ‘/home/lcatt’;
6 v_write utl_file.file_type;
7 begin
8
9 v_write := utl_file.fopen(v_dir, v_file, ‘w’, 4000);

10 11 –utl_file.fopen(v_dir, v_file, ‘w’, 100);
12
13 utl_file.put_line(v_write, v_record);

14 15 utl_file.fclose(v_write);
16
17 end test_file;
/ 18

Procedure created.

5. Reconnect to the database with SYSDBA privileges and revoke the DBA from ljcatt and grant the create session privilege. Then attempt to reconnect as the user LJCATT.

SQL> connect / as sysdba
Connected.
SQL> revoke dba from ljcatt;

Revoke succeeded.

SQL> grant create session to ljcatt;

Grant succeeded.

SQL> connect ljcatt
Enter password:
ERROR:
ORA-00604: error occurred at recursive SQL level 1
ORA-00900: invalid SQL statement
ORA-06512: at line 8

Warning: You are no longer connected to ORACLE.

6. NOTE: The error is received due to this user owning objects which he does not have privileges to create or access. This is shown below by reconnecting as SYSDBA and displaying objects owned by the user LJCATT.

SQL> connect / as sysdba
Connected.

SQL> select owner, object_name from dba_objects where object_name like ‘TEST_F%’
and owner=’LJCATT’

OWNER OBJECT_NAME
————————- ————————–
LJCATT TEST_FILE

7. As SYSDBA, re-grant the DBA role to LJCATT and attempt to reconnect.

SQL> grant dba to ljcatt;

Grant succeeded.

SQL> connect ljcatt
Enter password:
Connected.
SQL>

Now that the user LJCATT has the specific privileges required by the objects he owns, he is able to connect without error.

Larry J. Catt, OCP 9i, 10g
oracle@allcompute.com
www.allcompute.com

11g, Oracle, Oracle 10g, oracle 9i, privileges

Oracle – User does not have permissions on Oracle package UTL_FILE.

January 13, 2009 Larry Catt Leave a comment

Oracle provides the package UTL_FILE to produce OS layer files from within the Oracle RDBMS. Due to this procedures ability to create OS layer files from within the database, its access must be controlled through system privileges. This article will show a common PLS-00201 error, which indicates a lack of access permissions and how to resolve it.

1. Logon to your Oracle database server as the Oracle software owner.

2. Create a file called create_file.sql with the following SQL.

create or replace procedure test_file
is

v_record varchar2(50) := ‘Testing file creation’;
v_file varchar2(30) := ‘test_file.txt’;
v_dir varchar2(512) := ‘/home/lcatt’;
v_write utl_file.file_type;
begin

v_write:=utl_file.fopen(v_dir, v_file, ‘w’, 2000);

utl_file.put_line(v_write, v_record);

utl_file.fclose(v_write);

end test_file;
/

3. Logon to SQL*PLUS as the SYSDBA and create the user account LJCATT with the privileges: connect, create session, and resource to LJCATT.

mylinux:> sqlplus ‘/ as sysdba’

SQL*Plus: Release 10.2.0.4.0 – Production on Tue Jan 13 22:26:07 2009

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

Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 – 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL>

SQL> create user ljcatt identified by ljcatt;

User created.

SQL> grant connect to ljcatt;

Grant succeeded.

SQL> grant create session to ljcatt;

Grant succeeded.

SQL> grant resource to ljcatt;

Grant succeeded.

SQL>

4. Reconnect to SQL*PLUS as LJCATT and execute the file create_file.sql to create your procedure

Mylinux:/home/lcatt:>sqlplus ljcatt

SQL*Plus: Release 10.2.0.4.0 – Production on Tue Jan 13 22:43:17 2009

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

Enter password:

Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 – 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> set feedback on
SQL> set echo on
SQL>@./create_file.sql

SQL> create or replace procedure test_file
is
2 3
4 v_record varchar2(50) := ‘Testing file creation’;
5 v_file varchar2(30) := ‘test_file.txt’;
6 v_dir varchar2(512) := ‘/home/lcatt’;
7 v_write utl_file.file_type;
8 begin
9
10 v_write:=utl_file.fopen(v_dir, v_file, ‘w’, 2000);
11
12 utl_file.put_line(v_write, v_record);
13
utl_file.fclose(v_write);
14 15
16 end test_file;
17 /

Warning: Procedure created with compilation errors.

SQL> show errors
Errors for PROCEDURE TEST_FILE:

LINE/COL ERROR
——– —————————————————————–
7/9 PL/SQL: Item ignored
7/9 PLS-00201: identifier ‘UTL_FILE’ must be declared
10/1 PL/SQL: Statement ignored
10/1 PLS-00320: the declaration of the type of this expression is
incomplete or malformed

12/1 PL/SQL: Statement ignored
12/19 PLS-00320: the declaration of the type of this expression is
incomplete or malformed

14/1 PL/SQL: Statement ignored

LINE/COL ERROR
——– —————————————————————–
14/17 PLS-00320: the declaration of the type of this expression is
incomplete or malformed

SQL>

5. NOTE: The error received indicates that we do not have permissions to use the package UTL_FILE. Now connect to the database as sydba, execute the grant command: grant execute on utl_file to ljcatt;

SQL> connect / as sysdba
Connected.
SQL> grant execute on utl_file to ljcatt;

Grant succeeded.

SQL>

6. Connect back to the database as the user LJCATT, re-execute the SQL file create_file.sql, and execute the procedure test_file.

SQL> connect ljcatt
Enter password:
Connected.
SQL> create or replace procedure test_file
2 is
3
4 v_record varchar2(50) := ‘Testing file creation’;
5 v_file varchar2(30) := ‘test_file.txt’;
6 v_dir varchar2(512) := ‘/home/lcatt’;
7 v_write utl_file.file_type;
8 begin
9
10 v_write:=utl_file.fopen(v_dir, v_file, ‘w’, 2000);
11
12 utl_file.put_line(v_write, v_record);
13
14 utl_file.fclose(v_write);
15
end test_file;
16 17 /

Procedure created.

SQL> execute test_file

PL/SQL procedure successfully completed.

SQL>

The procedure now compiles without error and executes, due to the owner having proper privileges on the package UTL_FILE.

Larry J. Catt, OCP 9i, 10g
oracle@allcompute.com
www.allcompute.com

Catt Solutions

Category Archives: privileges

Oracle 12c – User privilege analysis

Oracle 12c – User privilege analysis overview

Users accounts in Multitenant Database

Privileges of Local Users in Oracle Multitenant Database

Privileges of Common Users in Oracle Multitenant Database

Oracle – ORA-00604: error occurred at recursive SQL level 1 and revoking a user privileges.

Oracle – User does not have permissions on Oracle package UTL_FILE.

Oracle tips and tricks.