Skip to content
pvmehta.com

pvmehta.com

  • Home
  • About Me
  • Toggle search form
  • On solaris 10, “S” link is not part of $ORACLE_HOME/bin/oracle as default. ( For 9.2.0.8) Oracle
  • The most important Tuning Notes Oracle
  • 284785.1 How to check RAC Option is currently linked into the Oracle Binary Oracle
  • RMAN : Consistent Backup, Restore and Recovery using RMAN Oracle
  • Reclaim temp tablespace for oracle 8, 8i Oracle
  • create a folder in multiple places Linux/Unix
  • fuser to check who is using diretory Linux/Unix
  • VIvek Encryption Package and Its Usage Oracle
  • Passing from Unix to PLSQL using bind variables Linux/Unix
  • RAC 11g with vmware Oracle
  • set_env_dba Linux/Unix
  • T-SQL Vs PL/SQL Syntax SQL Server
  • Reading parameter file and printing Linux/Unix
  • Identical Dblink Issue… Oracle
  • FGA Part-I 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

  • v$event_name Oracle
  • sbind.sql Find Bind variable from sql_id sqlid Oracle
  • How to set Processes Parameter Oracle
  • Find Plan Hash value fphv.sql Oracle
  • Jai Shree Ram Oracle
  • Load testing on Oracle 19C RAC with HammerDB 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 (150)
  • MYSQL (5)
  • Oracle (403)
  • PHP/MYSQL/Wordpress (10)
  • POSTGRESQL (1)
  • Power-BI (0)
  • Python/PySpark (7)
  • RAC (18)
  • rman-dataguard (26)
  • shell (151)
  • SQL scripts (349)
  • SQL Server (6)
  • Uncategorized (5)
  • Videos (0)

Recent Posts

  • Key Management in Oracle: The Core Issue: Missing Master Key12-May-2026
  • SAT Mathematics 10 questions and answer at the end.30-Apr-2026
  • top 10 AI news today30-Apr-2026
  • runon_allpdbs_show_conname.sh23-Apr-2026
  • runon_allcdbs_find_pdbs.sh23-Apr-2026
  • 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

Archives

  • 2026
  • 2025
  • 2024
  • 2023
  • 2010
  • 2009
  • 2008
  • 2007
  • 2006
  • 2005
  • Add new columns in dataframe Python/PySpark
  • Adding or Dropping Online Redo Log Files When Physical Standby in place Oracle
  • Ports used by Oracle Software Oracle
  • Drop tempfiles from database Oracle
  • USE_NL and INDEX hints example Oracle
  • Implementation of key based authentications Linux/Unix
  • track_autoupgrade_copy_progress.sql Oracle
  • Find sort details from Db find_sort.sql Oracle

Copyright © 2026 pvmehta.com.

Powered by PressBook News WordPress theme