Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

Database Administration (MOSC)

ORA-04021 seen in tracefile

Jun 18, 2024 7:28AM in Database Administration (MOSC) 4 commentsAnswered ✓

This question is not about the "ORA-04021" itself, but about the format of this message.

Normally alert.log-errormessages look like this: ORA-xxxxx: <short error text>
This kind of ORA-04021 message has no colon and no <short error text>, only the name of the trace file, which containes the "ORA-04021".

What, if my alert log monitoring would only cover ORA-messages with colon?
Is my monitoring missing out on anything important?
Or is it reasonably safe to ignore this "seen in tracefile" messages?

(I think it's more a question of philosophy. I look forward to your opinions.)

0

Howdy, Stranger!

To view full details, sign in to My Oracle Support Community.

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month