Unlock your Agile PLM system
Ever import a dump file and have your Agile PLM system refuse to start? Even if it imports and starts up, have you ever been unable to log in? Do not get discouraged, the fix is an easy one!
2. About Us
PLM Mechanic specializes in the technical
aspects of Oracle’s Agile PLM solution
We offer the following service:
– Agile PLM installations and upgrades
– Agile PLM maintenance and help desk functions
– Agile PLM hosting
– Customization
PLM Mechanic also has several product
offerings
3. Introduction
Ever import a dump file and have your Agile PLM
system refuse to start? Even if it imports and starts
up, have you ever been unable to log in? Do not
get discouraged, the fix is an easy one!
While you could do it from SQL Plus, I recommend
downloading and installing SQL Developer from
Oracle because it’s free and a lot easier to read the
output.
Now for the fix…
4. Get the old password
If your Agile system uses an account other than
‘agile,’ you need to know what the prior
passwords were. If you only know the
unencrypted version that Agile PLM was
installed with, create a test user in another
environment with the same passwords and then
look up the values in the database. If the
passwords match another environment, simply
look them up using the SQL from step 2.
5. 1. Open SQL Developer
Open SQLDeveloper and connect to the database for your Agile PLM
system
6. 2. Double check key the accounts
Execute the following SQL. If your admin
account is actually administrator, use
administrator in the statement, not admin
Note the passwords if you will need to change
these back. If doing data load activities in a
non-production environment for example and
the dump will need to be migrated back, save
these passwords!
7. 3. Update the passwords
Now we can update the passwords. This
example uses the encrypted version of ‘agile’
-- password agile = 37NVDUC0INA5N9OG6LRP0P8V9VR3DST0
update agileuser set login_pwd='37NVDUC0INA5N9OG6LRP0P8V9VR3DST0'
where loginid in ('admin', 'ifsuser', 'etluser', 'superadmin');
If you do this on a regular basis you could make a sql file and simply call it
from the command line.