Skip to content
pvmehta.com

pvmehta.com

  • Home
  • About Me
  • Toggle search form
  • Nice Article about semaphores and init.ora Processes parameter relations Linux/Unix
  • arch_configUOCIOTTO.ora Oracle
  • Oracle 10g Installation/Applying Patches Tips Oracle
  • Sort with ASCII order and Numeric Order Linux/Unix
  • Error Handling in Proc Oracle
  • checking connectivity between two servers Linux/Unix
  • chk_space_SID.ksh Linux/Unix
  • My Minimum Tuning Programs Oracle
  • Ports used by Oracle Software Oracle
  • logminer and my_lbu Oracle
  • tblwopk.sql tablewopk.sql Oracle
  • DBMS_UTILITY.ANALYZE_SCHEMA Oracle
  • Histogram information Oracle
  • Rename Oracle Instance Name Oracle
  • check_copy_progress.sh Linux/Unix

Default User Profile

Posted on 27-May-2009 By Admin No Comments on Default User Profile

Problem Description

——————-

The DBA needs to know which values are assigned to limits set to DEFAULT

for a given profile. Querying DBA_PROFILES does not display the actual values

but rather lists DEFAULT for those LIMITs.

Solution Description

——————–

From the SQL*Plus prompt, type:

SQL> select * from dba_profiles where profile = ‘DEFAULT’;

PROFILE RESOURCE_NAME RESOURCE_TYPE LIMIT

———- —————————- ————- ——————–

DEFAULT COMPOSITE_LIMIT KERNEL UNLIMITED

DEFAULT SESSIONS_PER_USER KERNEL UNLIMITED

DEFAULT CPU_PER_SESSION KERNEL UNLIMITED

DEFAULT CPU_PER_CALL KERNEL UNLIMITED

DEFAULT LOGICAL_READS_PER_SESSION KERNEL UNLIMITED

DEFAULT LOGICAL_READS_PER_CALL KERNEL UNLIMITED

DEFAULT IDLE_TIME KERNEL UNLIMITED

DEFAULT CONNECT_TIME KERNEL UNLIMITED

DEFAULT PRIVATE_SGA KERNEL UNLIMITED

DEFAULT FAILED_LOGIN_ATTEMPTS PASSWORD UNLIMITED

DEFAULT PASSWORD_LIFE_TIME PASSWORD UNLIMITED

DEFAULT PASSWORD_REUSE_TIME PASSWORD UNLIMITED

DEFAULT PASSWORD_REUSE_MAX PASSWORD UNLIMITED

DEFAULT PASSWORD_VERIFY_FUNCTION PASSWORD NULL

DEFAULT PASSWORD_LOCK_TIME PASSWORD UNLIMITED

DEFAULT PASSWORD_GRACE_TIME PASSWORD UNLIMITED

16 rows selected.

The value of the LIMIT column corresponds to the “default” value.

You can change the default profile by changing the value in the LIMIT column.

SQL> ALTER PROFILE DEFAULT limit ;

Ex:

SQL> ALTER PROFILE DEFAULT LIMIT FAILED_LOGIN_ATTEMPTS 5 PASSWORD_LOCK_TIME 1;

When you create a new profile, you must set at least one limit. It automatically

uses the default limits for all other resources not explicitly initialized.

Ex:

SQL> CREATE PROFILE test LIMIT connect_time 60;

Profile created.

SQL> select * from dba_profiles where profile = ‘TEST’;

PROFILE RESOURCE_NAME RESOURCE_TYPE LIMIT

———- —————————- ————- ——————–

TEST COMPOSITE_LIMIT KERNEL DEFAULT

TEST SESSIONS_PER_USER KERNEL DEFAULT

TEST CPU_PER_SESSION KERNEL DEFAULT

TEST CPU_PER_CALL KERNEL DEFAULT

TEST LOGICAL_READS_PER_SESSION KERNEL DEFAULT

TEST LOGICAL_READS_PER_CALL KERNEL DEFAULT

TEST IDLE_TIME KERNEL DEFAULT

TEST CONNECT_TIME KERNEL 60

TEST PRIVATE_SGA KERNEL DEFAULT

TEST FAILED_LOGIN_ATTEMPTS PASSWORD DEFAULT

TEST PASSWORD_LIFE_TIME PASSWORD DEFAULT

TEST PASSWORD_REUSE_TIME PASSWORD DEFAULT

TEST PASSWORD_REUSE_MAX PASSWORD DEFAULT

TEST PASSWORD_VERIFY_FUNCTION PASSWORD DEFAULT

TEST PASSWORD_LOCK_TIME PASSWORD DEFAULT

TEST PASSWORD_GRACE_TIME PASSWORD DEFAULT

Only the resource CONNECT_TIME has a value of 60 in the column LIMIT. All other

values refer to the DEFAULT limit – which means you have to look at the DEFAULT

profile to see which value is under LIMIT by using:

SQL> select * from dba_profiles where profile = ‘DEFAULT’;

Explanation

———–

If you only query DBA_PROFILES, this does not give sufficient information for

the default profile values. You need to query DBA_PROFILES where profile = ‘DEFAULT’

in order to see the default values.

Oracle, SQL scripts

Post navigation

Previous Post: Privilege to describe the table.
Next Post: How To Limit The Access To The Database So That Only One User Per Schema Are Connected (One Concurrent User Per Schema)

Related Posts

  • V$transaction notes for finding XID composition. Oracle
  • load SPM baseline from cursor cache Oracle
  • Important Script Method for tuning Oracle
  • ORA-1841 Error Connecting to Upgraded Database After Set PASSWORD_LIFE_TIME Oracle
  • Load testing on Oracle 19C RAC with HammerDB Oracle
  • Another export with Query Oracle

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Categories

  • Ansible (0)
  • AWS (2)
  • Azure (1)
  • Django (0)
  • GIT (1)
  • Linux/Unix (149)
  • MYSQL (5)
  • Oracle (393)
  • PHP/MYSQL/Wordpress (10)
  • POSTGRESQL (1)
  • Power-BI (0)
  • Python/PySpark (7)
  • RAC (17)
  • rman-dataguard (26)
  • shell (149)
  • SQL scripts (342)
  • SQL Server (6)
  • Uncategorized (0)
  • Videos (0)

Recent Posts

  • Complete Git Tutorial for Beginners25-Dec-2025
  • Postgres DB user and OS user.25-Dec-2025
  • Trace a SQL session from another session using ORADEBUG30-Sep-2025
  • SQL Server Vs Oracle Architecture difference25-Jul-2025
  • SQL Server: How to see historical transactions25-Jul-2025
  • SQL Server: How to see current transactions or requests25-Jul-2025
  • T-SQL Vs PL/SQL Syntax25-Jul-2025
  • Check SQL Server edition25-Jul-2025
  • Checking SQL Server Version25-Jul-2025
  • Oracle vs MYSQL Architecture differences (For DBAs)24-Jul-2025

Archives

  • 2025
  • 2024
  • 2023
  • 2010
  • 2009
  • 2008
  • 2007
  • 2006
  • 2005
  • standard Monitoring – 1 Oracle
  • create database syntax Oracle
  • fdisk -l explaination about Primary-Logical-Extended Partitions Linux/Unix
  • Find_stale_dr.sql finding stale physical DR.. Oracle
  • _B_TREE_BITMAP_PLANS issue during 8.1.7 to 9.2.0.8 upgrade Oracle
  • fuser to check who is using diretory Linux/Unix
  • move_arch_files.ksh /* Good One */ Linux/Unix
  • Rman Notes -1 Oracle

Copyright © 2026 pvmehta.com.

Powered by PressBook News WordPress theme