This content has been marked as final. Show 12 replies
We have experienced the same problem. Got a little assistance via Oracle's "My Support" tool but to no avail. Currently, we are Claim Diggerless.
How to change Claim Digger / Schedule Analyzer Database configuration [ID 895397.1] - check this in knowledge base .
I know how to configure claim digger. It just doesn't start when you push the button
Have you change your computer name, change of computer name stops claim digger.
Same machine, same database. All I have done is instal v7 SP1
While my experience with V.7 is quite limited I have seen this in V.6 as well. It is generally a combination of things that resolves the problem some of which you may need IT assistance with if this is not a stand-alone database.
1.) Delete C:\Program Files\Common Files\Primavera Common\Java\BREBootStrap.xml
2.) Run C:\Program Files\Common Files\Primavera Common\Java\dbconfig.cmd and create a new configuration. (requires DB connection info and pubuser password)
3.) Run C:\Program Files\Common Files\Primavera Common\Java\admin.cmd and delete all existing configurations except the new one created in step 2. (requires privuser password)
4.) Run C:\Program Files\Common Files\Primavera Common\Java\dbconfig.cmd and create a new configuration. Assuming you deleted the "Primavera Configuration" in step 3 it should automatically name it this.
5.) Run C:\Program Files\Common Files\Primavera Common\Java\admin.cmd and delete the configuration you created in step 2.
6.) Open P6v7 and attempt to launch Claim Digger. Note that sometimes I have seen it open up behind the client app and have had to alt-tab to bring it to the front.
7.) If it now launches but prompts for a password you should be able to type in your information and connect. To prevent it from asking for a password in the future I have had to do the following:
a.) reset your P6 password to blank (as in no password).
b.) logout and back into P6 with no password.
c.) launch Claim Digger and it should open without prompting for a password.
d.) reset your P6 password back to whatever it was.
e.) logout and back into P6 with your changed password.
f.) test claim digger.
Note that these are the steps I use to resolve this in V.6. As we do not yet run V.7 I do not know if everything is the same.
Edited by: ARE_DC on Apr 20, 2010 7:10 AM
No problem at all in P6v7 SP1.
Its working as designed.
When did SP1 get released for P6v7? I have recently looked on Oracles site but could not find any information about a service pack for v7.
SP1 was released recently...in the last month or so. Look for solution ID 1073886.1 in Oracle Support.
Will do, thank you.
How much you want to bet that the folder name specified for Claiim Digger is 'Schedule Comparison' and not 'Claim Digger'?
Its not something new as its been clearly shown in P6 Reference Manual as
Installed with the PM module, Schedule Comparison (also appearing in the PM client user interface as Claim Digger depending on the industry settings you chose during installation) compares two projects, or a project and an associated baseline, to determine what data has been added, deleted, or modified from the schedules.