| Solution ID: prim34059 |
| Errors when deleting UDFs (User Defined Fields) or when executing Admin/Purge Deletes using the Compression Server Client |
| Status: Reviewed |
| Version(s): 5.0 |
| Fact: | Compression Server Client |
| Fact: | PMDB and MMDB reside in the same Oracle Instance |
| Problem: | When deleting a UDF (User Defined Field) through Project Management, the following error is generated: SQLSE-1751-A error SQL Server Error: ORA-06550: line 1, column 7: PLS-00306: wrong number or types of arguments in call to ‘CASCADE_DELETE’orde ORA-06550: line 1, column 7: PL/SQL: Statement ignored Session -1 — privuser (PM.exe) — Cp1252 — 2064-6C66-10.49.198.104 DB Connection oracle.jdbc.driver.OracleConnection@21447f Request type: GET_SP_RESULT Command text: CASCADE_DELETE Parameter count: 14 0 — INPUT — String = UDFTYPE 1 — INPUT — String = 286 2 — RESULT — Integer = 0 3 — RESULT — String = 4 — INPUT — String = 5 — INPUT — String = 6 — INPUT — String = 7 — INPUT — String = UDFTYPE 8 — INPUT — String = 286 9 — RESULT — Integer = 0 10 — RESULT — String = 11 — INPUT — String = 12 — INPUT — String = 13 — INPUT — String = Block count: 0 Total data size: 0 bytes (before compression) Total job time spent to push in the queue: 0 ms Total job time: 0 ms (not including compression) |
| Problem: | When executing Admin/Purge Deletes the following error occurs: Purge Deletes failed with the following error: CLEANUP_LOGICAL_DELETES Error: SQL Server Error: ORA-06550: line 1, column 7: PLS-00306: wrong number or types of arguments in call to ‘CLEANUP_LOGICAL_DELETES’ ORA-06550: line 1, column 7: PL/SQL: Statement ignored Session -1 — privuser (PM.exe) — Cp1252 — 2064-6C66-10.49.198.104 DB Connection oracle.jdbc.driver.OracleConnection@21447f Request type: GET_SP_RESULT Command text: CLEANUP_LOGICAL_DELETES Parameter count: 8 0 — INPUT — Integer = 0 1 — RESULT — Integer = 0 2 — RESULT — String = 3 — INPUT — Integer = 1 4 — INPUT — Integer = 0 5 — RESULT — Integer = 0 6 — RESULT — String = 7 — INPUT — Integer = 1 Block count: 0 Total data size: 0 bytes (before compression) Total job time spent to push in the queue: 0 ms Total job time: 0 ms (not including compression) |
| Problem: | “Your database is not set for optimal refresh performance. To correct this problem, please contact your System Administractor or see Part2 of the Primavera Administrator’s Guide.”
NOTE: This message only appears when connecting to the PM database using compression server. It does not appear when connecting directly to the PM database using the Oracle client (no compression server). |
| Fix: | Run the following queries through sqlplus under a DBA account.(ex. SYS) NOTE: Privuser is the default private database login for PMDB and Privuser1 is the default private database login for MMDB. These accounts may be different in your environment.If so, replace names accordingly in the below queries: select GRANTEE, privilege from sys.dba_sys_privs where GRANTEE in (select granted_role from sys.dba_role_privs where grantee = ‘PRIVUSER’) or grantee = ‘PRIVUSER’; select GRANTEE, privilege from sys.dba_sys_privs where GRANTEE in (select granted_role from sys.dba_role_privs where grantee = ‘PRIVUSER1′) or grantee = ‘PRIVUSER1′; The only grants the Privuser accounts should have are listed below. If Privuser has more grants, the grants must be removed in order to fully resolve this issue. GRANTEE PRIVILEGE —————————— —————————————- CONNECT CREATE VIEW CONNECT CREATE TABLE CONNECT ALTER SESSION CONNECT CREATE CLUSTER CONNECT CREATE SESSION CONNECT CREATE SYNONYM CONNECT CREATE SEQUENCE CONNECT CREATE DATABASE LINK |
