Creating an Oracle Profile

Administering users with different policies have the possibility of major security in oracle database that compliam with all security departments in each organization.

In Oracle 19, have the same way to create profiles as Oracle 12.1, 12.2 , 18 and 19.

CREATE PROFILE GANDALF LIMIT 
   SESSIONS_PER_USER          UNLIMITED 
   CPU_PER_SESSION            UNLIMITED 
   CPU_PER_CALL               3000 
   CONNECT_TIME               45 
   LOGICAL_READS_PER_SESSION  DEFAULT 
   LOGICAL_READS_PER_CALL     1000 
   PRIVATE_SGA                15K
   COMPOSITE_LIMIT            5000000; 

Here, you have an small explanation about each parameter :

  1. SESSIONS_PER_USER: The user can have any number of concurrent sessions.
  2. CPU_PER_SESSION: In a single session, the user can consume an unlimited amount of CPU time.
  3. CPU_PER_CALL: A single call made by the user cannot consume more than 30 seconds of CPU time.
  4. CONNECT_TIME: A single session cannot last for more than 45 minutes.
  5. LOGICAL_READS_PER_SESSION: In a single session, the number of data blocks read from memory and disk is subject to the limit specified in the DEFAULT profile.
  6. LOGICAL_READS_PER_CALL: A single call made by the user cannot read more than 1000 data blocks from memory and disk.
  7. PRIVATE_SGA: A single session cannot allocate more than 15 kilobytes of memory in the SGA.
  8. COMPOSITE_LIMIT: in a single session, the total resource cost cannot exceed 5 million service units. The formula for calculating the total resource cost is specified by the ALTER RESOURCE COST statement.

Those are not the only paramters ,but this its a great example to start diferent tests.

How to RU Patch Deinstallation

Hello Guys !

I’m here again, to give an small explanation of why, we need know how to deinstall an Release Update.

Why ?

It’s depends, on my case, the last RU had some issues in the import datapump.

After review all cases and aply some workarounds, and debug and review all logs and traces with the ADRCI tool to stay sure of my desicion, deinstall.

Additional Documentation

I review the oracle document from MOS: Database 19c Release Updates and Revisions Bugs Fixed Lists (Doc ID 2523220.1)

Hands on

The first step is verificate the number of the RU, to start with the procediment:

select CON_ID,
TO_CHAR(action_time, 'YYYY-MM-DD') AS action_time,
PATCH_ID,
PATCH_TYPE,
ACTION,
DESCRIPTION,
SOURCE_VERSION,
TARGET_VERSION
from CDB_REGISTRY_SQLPATCH
order by CON_ID, action_time, patch_id;

This query help us, with the list of the number, to verified the last patch applied.

Continuar leyendo «How to RU Patch Deinstallation»
A %d blogueros les gusta esto: