Skip to content
pvmehta.com

pvmehta.com

  • Home
  • About Me
  • Toggle search form
  • To Find Orphan OS processes. Linux/Unix
  • remove archfiles only when it is applied to DR rm_archfiles.sh Linux/Unix
  • Good Site for Oracle Internals Oracle
  • How To Limit The Access To The Database So That Only One User Per Schema Are Connected (One Concurrent User Per Schema) Oracle
  • perf_today.sql Oracle
  • For Search and replace unix command. Linux/Unix
  • Drop database in Oracle 10g Oracle
  • Process Map for CPU and Memory for OS processes Linux/Unix
  • Sample WW22 listener.ora Oracle
  • shr1.sql for MTS or Shared server configuration Oracle
  • Oracle Support Metalink ID 161818.1 Oracle
  • To see how much time or progress of long transaction Oracle
  • Good notes on Oracle Events Oracle
  • Monitor and Trace Unix processes using truss Linux/Unix
  • Formatter Explain plan Output 1 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

  • Oracle Identifiers Oracle
  • Facts about SCN and Rollback Segment Oracle
  • 751131.1 New Article Error 2819 While Requesting a Systemstate Dump Oracle
  • Implementing Listener Security Oracle
  • findx.sql /* Find Indexes on specified USER.TABLE_NAME */ Oracle
  • temp_use.sql diplays usage of temp ts Oracle

Leave a Reply Cancel reply

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

Categories

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

Recent Posts

  • 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
  • V$INSTANCE of Oracle in MYSQL24-Jul-2025
  • Day to day MYSQL DBA operations (Compared with Oracle DBA)24-Jul-2025
  • MYSQL and Oracle Comparison for Oracle DBA24-Jul-2025

Archives

  • 2025
  • 2024
  • 2023
  • 2010
  • 2009
  • 2008
  • 2007
  • 2006
  • 2005
  • 272332.1 CRS 10g Diagnostic Collection Guide Oracle
  • Find long Running Transaction Linux/Unix
  • load SPM baseline from cursor cache Oracle
  • How to Modify the statistics collection by MMON for AWR repository Oracle
  • How to Decide upto what level you can decrement your datafile size. ( Shrink Datafile) Oracle
  • Settting up get_vmstat.sh for colletinf CPU Usage. Oracle
  • Sequence Resetting Oracle
  • Insert cause enqueue locks Oracle

Copyright © 2025 pvmehta.com.

Powered by PressBook News WordPress theme