Find error table created using DBMS_ERRLOG

Question

Hello,
I am working on Oracle 10.2.0.5 and have a requirement to log the Error records without allowing the Load process to fail. In order to achieve this, I have decided to use the DBMS_ERRLOG functionality provided.
However, there is a catch. The application has approx. 100+ database tables, which are loaded with data received in flat files, and many of them have length nearning 30 characters.
Now, DBMS_ERRLOG, will automatically create an error table corresponding to database table, but will only consider first 25 characters. And since, many tables have similar names differing only towards the end. Hence, my question is, Is there any data dictionary view which might store the underlying database table name?
I am aware of two options to achieve this:
1. Maintain a document to reference each Error table to its database table. This being a manual approach, I am trying to avoid it.
2. Use the USER_TAB_COMMENTS, which will store the table name in comment. Although I have seen this happening, but do not see this as sure-shot approach, since I do not remember reading this anywhere in documentation.
Can anybody suggest a better approach to manage the situation?

Answer 1

padders answer is a good one.  I do not see the problem since you can create the error log tables with names of your choosing in any schema you want.  Don't let oracle name the tables.  Use SQL to create the PL/SQL for all your tables based on a tag you put in the table comments or based on another table with the table names to be logged.
  DBMS_ERRLOG.create_error_log
    dml_table_name      => 'real_schema.my_thirty_character_table_name',
    err_log_table_name  => 'my_thirty_character_table_name',
    err_log_table_owner => 'error_schema',
    skip_unsupported    => TRUE
Table_Name
Error_Table_Name
Error_SchemaHeader
my_thirty_character_table_name
my_thirty_character_table_name
error_schema
my_short_name
my_short_name_err_log
support
With so many tables I would write a generator to create all the error log tables and the DML (insert, update or merge statements) with error logging for all the tables based on the above table and maybe put the DML in an API package that can be called from your app.