| Solution ID: prim29944 |
| Deleted Objects reappear when Project Management is closed and reopened. |
| Status: Reviewed |
| Version(s): 5.0 |
| Problem: | Deleted Activities reappear when Project Management is closed and reopened. |
| Problem: | Trying to remove a license from a user. When Project Management is closed and reopened the license is not removed. |
| Problem: | Event Code Error: TINAT-2680-D. |
| Problem: | Deleted activity comes back in Project Management. |
| Problem: | The Purge Deletes function does not work. |
| Problem: | Deleted tasks return in Project Management. |
| Problem: | Loops reported for non-existent relationships. |
| Problem: | Deleted relationships reappear after reopening Project Management. |
| Problem: | SQL Monitor shows delete quires running commands to delete from the wrong schema. ex: DELETE FROM ADMUSER_1.PROJISSU WHERE PROJ_ID = :PROJ_ID and (WORKSPACE_ID IS NOT NULL) |
| Cause: | Cause 1: Enabling Server Roles for privuser has the effect of changing the logical delete views used by Privuser to filter out logically deleted records from displaying in the application. |
| Cause: | Cause 2: Missing Logical Delete Views could also cause the application to look directly at the physical tables. |
| Cause: | Cause 3: The “PRIVATE” database User is incorrectly configured as ADMUSER, rather PRIVUSER. If ADMUSER is accessing the tables it looks DIRECTLY at the table and sees ALL records including logically deleted records. |
| Cause: | Cause 4: Multiple PMDB Schemas located in the same Oracle Instance. PRIVUSER has GRANT SELECT, INSERT,UPDATE, DELETE for all tables in both schemas. |
| Fix: |
Fix 1: Make sure, in SQL Server Enterprise Manager, that security logins privuser and pubuser are not granted Server Roles. To verify and correct this issue:
|
| Fix: | Fix 2: Run Schema Validation to check for missing Logical Delete Views. Recreate missing logical delete views with the statements found in the create scripts in the install\database\scripts directory for the type of database being used. SEE ALSO: prim29487 - ”How to validate a PMDB / MMDB database schema?” |
| Fix: | Fix 3: Administer Private database logins to change the DB User to the ‘privuser’ User account. SEE ALSO: Solution ID prim24867 - ”How to administer the private database logins username and password” for instructions on changing the private database login. Image may be NSFW. |
| Fix: | Fix 4: Revoke the SELECT, INSERT, UPDATE, DELETE privilege for PRIVUSER for the incorrect schema. FOR EXAMPLE: Schema1′s Users – ADMUSER, PRIVUSER and PUBUSER. ( Correct Schema ) Schema2′s Users – ADMUSER_1, PRIVUSER_1 and PUBUSER_1. ( Incorrect Schema ) REVOKE SELECT, INSERT, UPDATE, DELETE ON ADMUSER_1.ACCOUNT to PRIVUSER; The revoke statement needs to run for every table in the schema. You can use the ordp_grn.sql script found on CD1 in the \install\database\scripts\install\or\drop\pmdb directory. This script will need to be edited to add the schema owner (admuser_1.) before the name of each table. The PRIVUSER will still have the SELECT, INSERT, UPDATE, DELETE privilege on the ADMUSER SCHEMA.
|
