Skip to content
pvmehta.com

pvmehta.com

  • Home
  • About Me
  • Toggle search form
  • AWR settings- MMON is not taking snapshot. Oracle
  • Nice Article about semaphores and init.ora Processes parameter relations Linux/Unix
  • USE_NL and INDEX hints example Oracle
  • Very Good Oralce Internal Tuning Book Oracle
  • v$event_name Oracle
  • fuser to check who is using diretory Linux/Unix
  • Default User Profile Oracle
  • shutdown linux Linux/Unix
  • grep multuple patterns Linux/Unix
  • Jai Shree Ram Oracle
  • To see only files and/or folders using LS command Linux/Unix
  • Remove duplicate rows from table Oracle
  • get_vmstat.ksh Linux/Unix
  • FRA Information. Oracle
  • ORA-01220 Oracle

ORA-1841 Error Connecting to Upgraded Database After Set PASSWORD_LIFE_TIME

Posted on 05-Jun-2009 By Admin No Comments on ORA-1841 Error Connecting to Upgraded Database After Set PASSWORD_LIFE_TIME

Problem:

~~~~~~~~

When you upgrade the database from Oracle V7 to V8, and then create a profile

which limits password_life_time, existing users cannot login to the database.

New users can login without a problem.

To reproduce this problem:

1. Create a test user (test1) in a V7 database:

grant connect, resource to test1 identified by test1;

connect test1/test1

2. Upgrade this database to V8 and test if user test1 can connect:

sqlplus test1/test1

connected

3. Create and assign a profile that limits password_life_time:

create profile testprofile limit password_life_time 10;

alter user test1 profile testprofile;

4. Try to connect as user test1:

sqlplus test1/test1

ERROR:

ORA 1841: (full) year must be between -4713 and +4713 / +9999

Solution:

~~~~~~~~~

Alter the user and change the password,

– or –

Alter the profile and change password_life_time to unlimited.

You can ‘change’ the password for every user in such a way that it keeps the

original value (useful when you do not want to trouble users with a password

change) by using the method from Note 1051962.101

Explanation:

~~~~~~~~~~~~

This is Bug 711547

Oracle, SQL scripts

Post navigation

Previous Post: check_copy_progress.sh
Next Post: Restoring a user’s original password 1051962.101

Related Posts

  • Error Handling in Proc Oracle
  • Explain Plan Doesn’T Change For Sql After New Statistics Generated Oracle
  • Goog notes on X$ tables Oracle
  • findinfo.sql (SQL for getting CPU and Active session info) Oracle
  • Changing Instance Name ( No DB_NAME) Oracle
  • Remove duplicate rows from table 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
  • reset Sequence Oracle
  • scp with ssh2 Linux/Unix
  • Caching sequence in Memory Oracle
  • RMAN : Consistent Backup, Restore and Recovery using RMAN Oracle
  • Oracle Recommended Patches — Oracle Database ID 756671.1 Oracle
  • Benefits and Usage of RMAN with Standby Databases Oracle
  • To see how much time or progress of long transaction Oracle
  • Default User Profile Oracle

Copyright © 2026 pvmehta.com.

Powered by PressBook News WordPress theme