Skip to content
pvmehta.com

pvmehta.com

  • Home
  • About Me
  • Toggle search form
  • Sending email with file attachment. Linux/Unix
  • TNSNAMES entries details Oracle
  • Jai Shree Ram Oracle
  • Monitor and Trace Unix processes using truss Linux/Unix
  • Error Handling in Proc Oracle
  • 751131.1 New Article Error 2819 While Requesting a Systemstate Dump Oracle
  • Good Link from metalink 1 Oracle
  • AWR settings- MMON is not taking snapshot. Oracle
  • My FTP Job Scheduling for www.pvmehta.com PHP/MYSQL/Wordpress
  • SQL_PLAN.sql for checking real execution plan Oracle
  • Good Oracle Architecture In Short and point to point Oracle
  • Some OS level threshold for performance. Linux/Unix
  • Python class import from different folders Python/PySpark
  • Oracle Data Direct to TAPE Oracle
  • exp syntax in oracle 10g 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

  • get_vmstat_linux Oracle
  • export import with parameter file. Oracle
  • Changing the Global Database Name Oracle
  • mutex in Oracle 10.2.0.2 or Oracle 10g Oracle
  • v$event_name Oracle
  • Jai Shree Ram 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 (400)
  • PHP/MYSQL/Wordpress (10)
  • POSTGRESQL (1)
  • Power-BI (0)
  • Python/PySpark (7)
  • RAC (18)
  • rman-dataguard (26)
  • shell (150)
  • SQL scripts (348)
  • SQL Server (6)
  • Uncategorized (3)
  • Videos (0)

Recent Posts

  • Running PDB on single node in RAC09-Apr-2026
  • find_arc.sql09-Apr-2026
  • pvm_pre_change.sql08-Apr-2026
  • find_encr_wallet.sql08-Apr-2026
  • find_pdbs.sql08-Apr-2026
  • Creating a Container Database using dbaascli08-Apr-2026
  • track_autoupgrade_copy_progress.sql01-Apr-2026
  • refre.sql for multitenant01-Apr-2026
  • prepfiles.sh for step by step generating pending statistics files10-Mar-2026
  • tracksqltime.sql05-Mar-2026

Archives

  • 2026
  • 2025
  • 2024
  • 2023
  • 2010
  • 2009
  • 2008
  • 2007
  • 2006
  • 2005
  • v$event_name Oracle
  • TRUNCATE Privs Oracle
  • tar and untar a dolder with all its subfolder. Linux/Unix
  • Sending SQLPLUS output in HTML format Oracle
  • Handling LOB data in Oracle Oracle
  • MYSQL for Oracle DBA MYSQL
  • move_arch_files.ksh Linux/Unix
  • longtx.sql with the flag whether session is blocking any DML locks or not. Oracle

Copyright © 2026 pvmehta.com.

Powered by PressBook News WordPress theme