Scribd
Upload
3K views2 pages

ORA-00800: Soft External Error, Arguments

This document describes an ORA-00800 soft external error related to failed priority elevation of the VKTM process in Oracle Database on IBM AIX. The error is caused by a known bug and can be ignored if the VKTM process is running at the desired priority level. A patch may fix the issue once available.

Uploaded by

oscar_86c7949
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
3K views2 pages

ORA-00800: Soft External Error, Arguments

This document describes an ORA-00800 soft external error related to failed priority elevation of the VKTM process in Oracle Database on IBM AIX. The error is caused by a known bug and can be ignored if the VKTM process is running at the desired priority level. A patch may fix the issue once available.

Uploaded by

oscar_86c7949
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

29/1/2020 Document 2551359.

1
Copyright (c) 2020, Oracle. All rights reserved. Oracle Confidential.

ORA-00800: Soft External Error, Arguments: [Set Priority Failed], [VKTM] [Check traces and OS
configuration] (Doc ID 2551359.1)

In this Document

Symptoms
Changes
Cause
Solution
References

APPLIES TO:

Oracle Database - Enterprise Edition - Version [Link] to [Link].0 [Release 12.2 to 18]
IBM AIX on POWER Systems (64-bit)

SYMPTOMS

ORA-00800: soft external error, arguments: [Set Priority Failed], [VKTM], [Check traces and OS configuration], [Check Oracle
document and MOS notes], []
during startup of database logged in [Link]
More messages in trace file:

kstmmainvktm: failed in setting elevated priority


Verify: SETUID is set on ORADISM and restart the instance
highres_enabled
VKTM running at (100ms) precision
kstmrmtickcntkeeper: param _dbrm_quantum will not be effective
-----

oradism was checked and the access rights are as expected:

#ls -l oradism
-rwsr-x--- 1 root dba 54428 May 19 09:04 oradism

CHANGES

CAUSE

Bug 28831618 : FAILED TO ELEVATE VKTM'S PRIORITY IN AIX WITH EVENT 10795 SET

This bug needs to be confirmed by checking the priority of the VKTM process:

[Link] 1/2
29/1/2020 Document 2551359.1

root# ps -ef | grep vktm


oracle 31654218 1 0 Oct 25 - 1:21 ora_vktm_DBEM << example output with the PID 31654218 needed in next
step

root# ps -A -o pid,tid,pri | grep 31654218

the output then should look like:


31654218 - 39

If the output shows 39 as priority then the vktm runs at the desired priority and the error message may be ignored.

SOLUTION

At the time of writing there is no patch available for this bug as it is still being worked on.

Please check for available patches for bug 28831618 for Your RDBMS version.

If no patch is available you may just ignore the error message.

REFERENCES

BUG:28831618 - FAILED TO ELEVATE VKTM'S PRIORITY IN AIX WITH EVENT 10795 SET
Didn't find what you are looking for?

[Link] 2/2

29/1/2020 Document 2551359.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=t1xrfmgi4_72&id=2551359.1
29/1/2020 Document 2551359.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=t1xrfmgi4_72&id=2551359.1

You might also like