![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||
Solution Type Problem Resolution Sure Solution 1563052.1 : Increase of the Parameter " project.max-shm-memory" in Solaris fails with error "TASK_PROJ_PURGE" not allowed while "strict subs"
Created from <SR 3-7401531501> Applies to:Solaris SPARC Operating System - Version 10 1/13 U11 and laterSPARC SuperCluster T4-4 - Version All Versions and later Oracle Solaris on SPARC (64-bit) Oracle Solaris on x86-64 (64-bit) SymptomsIncrease of the parameter " project.max-shm-memory " fails with Error projmod -sK "project.max-shm-memory=(privileged,10G,deny)" user.dba
Bareword "TASK_PROJ_PURGE" not allowed while "strict subs" in use at /usr/sbin/projmod line 641. Execution of /usr/sbin/projmod aborted due to compilation errors.
CauseCause was due to "use strict;" being enabled in file /usr/sbin/projmod Solution1. Take a backup of the /usr/sbin/projmod 2. Comment the line "use strict;" in /usr/sbin/projmod 3. Increase the project.max-shm-memory variable Ex : projmod -sK "project.max-shm-memory=(privileged,10G,deny)" user.dba
References<NOTE:1526424.1> - 11.2.0.3 DBUA Fails : ORA-27102: Out Of Memory, "SP2-0640: Not Connected"Attachments This solution has no attachment |
||||||||||||
|