Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Does anyone know what triggers the USER_ID field in the log.xml to be populated? The value also exists in the V$DIAG_ALERT_EXT view.

I've found by observing the logs that if a temp tablespace fills up, it will log the USER_ID of the problematic SQL statement causing the issue. But other than that, it appears that value is always NULL.

share|improve this question

Log.xml is the new log format of oracle database will be substitute the actual alert.log in future (according to oracle roadmap). Basically you can find in the log.xml all information available in the alert.log with some more details, like the USER_ID. However the database log file does not aim to alert you about specific user issue but only to problem might be considered database-wide.

This means that for almost all problem there is no USER_ID, like for

ORA-00257: archiver error. Connect internal only, until freed.

But for some issues caused and related to specific user action the USER_ID will be present. For example the alert log provide you only this line:

ORA-1555 snapshot too old: rollback segment number %s with name \"%s\" too small" 

(in 11g you have also part of sql statement)

The log.xml will show more data. Furthermore, log.xml is close part of ADRCI, the tool for incident diagnose and management, and to do its own work needs more data than the simpe ORA-xxxx.

So, everytime a USER_ID is applicable to the error you will find in the log.xml, otherwise no.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.