[Spacewalk-list] Oracle is cranky today

[Dennis Pittman]

I would bet, the root problem is within your spacewalk configuration.  The oracle db error, is reporting on a condition that’s not acceptable.
You need to root down a little more to see what spacewalk was trying to complete when the error occurred.  On the other hand try restarting the tomcat or all of your spacewalk services to see if the error goes away.  It could be a problem where something got updated while your tomcat service was still running and executing on the previous configuration state.

Regards,

Dennis

From: spacewalk-list-bounces at redhat.com <spacewalk-list-bounces at redhat.com> On Behalf Of Peirce, Dean
Sent: Monday, June 24, 2019 2:50 PM
To: spacewalk-list at redhat.com
Subject: [Spacewalk-list] Oracle is cranky today


Hi all,
I’ve gotten a log full of messages like below today for the first time. Not sure if this issue is with Oracle, or spacewalk itself… My money is on the problem being with the db… Any thoughts?

Spacewalk 13580 2019/06/24 14:27:12 -04:00: ('rhnSQL.SQLError caught', SQLError(4068, 'ORA-04068: existing state of packages has been discarded\\nORA-04061: existing state of package body "GSPACWLK1.LOGGING" has been invalidated\\nORA-04065: not executed, altered or dropped package body "GSPACWLK1.LOGGING"\\nORA-06508: PL/SQL: could not find program unit being called: <file://nORA-06508:%20PL/SQL:%20could%20not%20find%20program%20unit%20being%20called:%20> "GSPACWLK1.LOGGING"\\nORA-06512: at line 1\\n'))


Thanks,

Dean
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20190624/336e705d/attachment.htm>