Symptoms:
When starting up the Oracle 19c, it raises an error on the trace file and also creates an incident file with the message:
ORA-00800: soft external error, arguments: [Set Priority Failed], [VKTM], [Check traces and OS configuration], [Check Oracle document and MOS notes], []
Cause:
As given by the MOS article (Doc ID 2718971.1)
"19c moved to OL7/UEK4. UEK4 requires rt_period and rt_runtime set for the cgroup from where the d/b is started.
Typically the root one unless the customer is setting up their own cgroups or using system user slices.
It requires the proper values such as the 95%. For this problem, ORA-800 will have the following message in the incident. "
Solution:
Check the priority of VKTM @RDBMS level:
SQL> select a.ksppinm "Parameter", b.ksppstvl "Session Value", c.ksppstvl "Instance Value", a.KSPPDESC "Describtion"
from x$ksppi a, x$ksppcv b, x$ksppsv c
where a.indx = b.indx and a.indx = c.indx and a.ksppinm like '_%' and a.ksppinm like '_highest_priority_process%';
If not "VKTM" is not prioritiesed, please elevate the priority :
SQL> alter system set "_high_priority_processes"='VKTM' scope=spfile;
Restart DB and verify the same
SQL> show parameter "_high_priority_processes";
As root user, change file permission and owner
$ chmod root.oinstall $ORACLE_HOME/bin/oradism
$ chmod u+s oradism
Restart the database and check if it solved the error.
Otherwise, check the MOM Doc ID given above.
No comments:
Post a Comment