Help! Agile PLM won’t start after a database import!

782 views
624 views

Published on

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!

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
782
On SlideShare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
14
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Help! Agile PLM won’t start after a database import!

  1. 1. Help! Agile PLM won’t startafter a database import!
  2. 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. 3. IntroductionEver import a dump file and have your Agile PLMsystem refuse to start? Even if it imports and startsup, have you ever been unable to log in? Do notget discouraged, the fix is an easy one!While you could do it from SQL Plus, I recommenddownloading and installing SQL Developer fromOracle because it’s free and a lot easier to read theoutput.Now for the fix…
  4. 4. Get the old passwordIf your Agile system uses an account other than‘agile,’ you need to know what the priorpasswords were. If you only know theunencrypted version that Agile PLM wasinstalled with, create a test user in anotherenvironment with the same passwords and thenlook up the values in the database. If thepasswords match another environment, simplylook them up using the SQL from step 2.
  5. 5. 1. Open SQL Developer Open SQLDeveloper and connect to the database for your Agile PLM system
  6. 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. 7. 3. Update the passwordsNow we can update the passwords. Thisexample uses the encrypted version of ‘agile’-- password agile = 37NVDUC0INA5N9OG6LRP0P8V9VR3DST0update agileuser set login_pwd=37NVDUC0INA5N9OG6LRP0P8V9VR3DST0where loginid in (admin, ifsuser, etluser, superadmin);If you do this on a regular basis you could make a sql file and simply call itfrom the command line.
  8. 8. Contact Us Web: http://www.plmmechanic.com Blog: http://www.plmmechanic.com/blog Twitter: @PLMMechanic Email: sales@plmmechanic.com Phone: 512-827-2262 Fax: 512-582-2932

×