Revoking UTL_* execute from PUBLIC and ACLs

-
Version -- Oracle 11.2.0.4

In most of the oracle production dbs public executes are revoked as per the security requirements.
But doing so can cause some of the functionalities to fail.

Here we will discuss the effect on ACLs by revoking public execute on UTL_* packages.

Revokes -->

'revoke execute on UTL_TCP from public'
'revoke execute on UTL_HTTP from public'
'revoke execute on UTL_SMTP from public'

now the ACL will not work since the users assigned to ACL do not have the required privileges on ULT packages.
But this also triggers another event.

select * from dba_network_acls will return a ora-00600 as below.

 
ERROR at line 1:
ORA-00600: internal error code, arguments: [qmxqtmChkXQAtomMapSQL:2], [], [], [], [],
[], [], [], [], [], [], []

10046 trace for the session shows below,



 XDB.DBMS_CSX_INT is invalid.

Querying dba_objects show lots of invalid objects owned by XDB and SYS.

To resolve,

First UTL pacakage privileges were granted to XDB user,

grant execute on utl_http to xdb;

grant execute on utl_smtp to xdb;

grant execute on utl_tcp to xdb;

Then run  utlrp.sql to validate all invalids.

Above will allow to query on XDB and ACL realted views including dba_network_acls.

To get ACLs working the related users need to be provided with execute privileges on the UTL packages.
Eg. If the ACL principle is aclusr then,

grant execute on utl_http to aclusr;

grant execute on utl_smtp to aclusr;

grant execute on utl_tcp to aclusr;


Comments

Post a Comment

Popular posts from this blog

ORA-16433: The database or pluggable database must be opened in read/write

-
Image
ORA-16433 is an error returned when a database cannot be opened. This can be a result of multiple conditions including, The inconsistency of the database Physical corruption Loss of dependent files or access issues etc.. More often than not the solution is to recover from available backups, but there can be situations where backups are not available, specially on UAT or Test setups. Although not the ideal scenario, in this type of situation you might want to open the databases even with inconsistency.  In Comes --> _ALLOW_RESETLOGS_CORRUPTION First, if you are in a position to use _ALLOW_RESETLOGS_CORRUPTION=TRUE, that means it has to be a critical moment, and when you come across more ora- errors while you are trying to reopen the databsae, that can be annoying. Note - _ALLOW_RESETLOGS_CORRUPTION=TRUE must only be used after Oracle support confirmation as a last resort. Also make sure to take cold backup before proceeding. Basic steps to be followed to resolve ORA 16433 af...
Read more

Oracle Multitenant - Create new service for PDB using DBMS_SERVICE

-
Image
When an Oracle PDB is created it starts up a default service with the PDB name. For direct connections to    PDB this service can be used. But there are situations where new service name is required in PDB level, common example is after a PDB restoration/clone, in order to enable application connections without changes in connection string. Setting service_names parameter in PDB level is not possible hence it is not an option in multitenant setup. How to create a new PDB service on Oracle 12C Check the current services, here only the default service is running, SQL> show pdbs; CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 3 NFACTORPDB READ WRITE NO SQL> select service_id, name, pdb from dba_Services; SERVICE_ID NAME PDB ---------- ---------------------------------------- ---------- 7 nfactorpdb NFACTORPDB SQL> ...
Read more

Wait for unread message on broadcast channel - Blocking Sessions

-
Image
What is Wait for unread message on broadcast channel wait event? Wait for unread message on broadcast channel is a wait event where source destination communication is involved and the database is waiting for a reply from remote party. Mostly this wait is seen related to data pump export (expdp) or import (impdp) operations. Although categorized in idle wait class "Wait for unread message on broadcast channel" can become the blocking session for some other sessions. Common causes for stuck sessions waiting on this wait event includes, Broken databases links, where remote database is not responding. Abnormally killed remote processes causing the sessions to wait. When a session is waiting on "Wait for unread message on broadcast channel" it can become a blocking session for dependent sessions. Most probably these sessions will be waiting on "library cache pin" or related concurrency wait events. The blocking_session column of (g)v$session view...
Read more