The community will be in read-only from Tuesday 11:59pm (PST) to Wednesday 10:30am (PST)
The community will be in read-only from Tuesday 11:59pm (PST) to Wednesday 10:30am (PST)
Project and Portfolio Management Practitioners Forum
cancel
Showing results for 
Search instead for 
Did you mean: 

Manually updating the database problem *URGENT*

Highlighted
b460
Regular Collector

Manually updating the database problem *URGENT*

Hi,

I need to manually update data within a field in multiple requests. The field I am updating is a user name field. The current value of the field is 'Daniel White'.

Within the Oracle client, as a test, I ran the following SQL to update the field:

update kcrt_request_details set parameter33 = '12345', visible_parameter33 = 'John Smith'
where request_id = '31422' and batch_number = '1'

This updated the data fine in the database, but when I went to view the request in PPM the data within the field was still 'Daniel White' and not 'John Smith'

Does anyone know why this would be happening?
10 REPLIES
Mahen M
Honored Contributor

Re: Manually updating the database problem *URGENT*

Check up whether you are updation the correct field.

Is your environment a clustered Environment?

Try clearing the cache under $PPM_HOME/bin, The command to run is
'sh kRunCacheManager.sh A'

Clear cache in all the servers.

Let me know if this does not work.

Regards,
Mahendran M
MDC_SMS
Acclaimed Contributor

Re: Manually updating the database problem *URGENT*

Hello,

Did you issue a commit?
StefanBienz
Super Collector

Re: Manually updating the database problem *URGENT*

The problem is that you don't update the LAST_UPDATE_DATE column in the KCRT_REQUEST_DETAILS table. If you update a Request directly in the DB, you always have to update this column, too, because that's what PPM uses for controlling the access of the server's cache. If this column has not changed, then the interface uses old cached values, resulting in the effect you had.

Cheers,
Stefan Bienz
Cirrus Consulting AG

Re: Manually updating the database problem *URGENT*

You will need to log into the application server and run the command:
sh kRunCacheManager.sh -A

This will definitely reflect the database changes in the front end.

- Nisha Kurien
Niraj Prabhu
Frequent Visitor

Re: Manually updating the database problem *URGENT*

I am sure just sh kRunCacheManager.sh -A would fix this issue.

Let us know if it is fixed.
Niraj P.
b460
Regular Collector

Re: Manually updating the database problem *URGENT*

Hi,

I was using "commit" after the update and it would not update the form after I refreshed the browser.

When I ran the kRunCacheManager.sh -A command it did update teh field after a browser refresh.

However when changing the Project Manager of a Project using the statement:

update kcrt_fg_pfm_project set prj_project_manager_user_id = '123456', prj_project_manager_username = 'Mark Milligan'
where request_id = '12341'

Then running the kRunCacheManager.sh -A command, after a browser refresh, the field within the form (using token KNTA_PROJECT_MANAGER) updated fine, but the "Project Manager" field at the top of the page (in between the "Project Status" and "Project Plan Period" fields) did not update.

Re: Manually updating the database problem *URGENT*

I believe the information for the field "Project Manager" at the top of the page (in between the "Project Status" and "Project Plan Period" fields) is stored in the table "pm_projects" field name - "PROJECT_MANAGER".

You will need to run the cache manager (sh kRunCacheManager.sh -A) to see the changes reflected in the front end.

Let me know if this fixes your issue.

-Nisha Kurien.
b460
Regular Collector

Re: Manually updating the database problem *URGENT*

Thnaks everyone, the command kRunCacheManager.sh A made it work.
Shravan Kathuri
Senior Member

Re: Manually updating the database problem *URGENT*

We had same issue not updating project manager.Eventhough we ran the kRunCacheManager A, it does not reflect the front end. But when i clicked on SAVE 2 times it got reflected. what are all the required tables to update in order to reflect the project manager field.

In pm_projects,project_manager field is null for all projects.

Thanks
Shravan.
Raji Venkatesan
Acclaimed Contributor

Re: Manually updating the database problem *URGENT*

Tables involved to update project manager from backend:
pm_projects, kcrt_fg_pfm_project, itg_trustee,
itg_group_participant_users



//Add this to "OnDomLoad" event