While using direct load whether trigger get fired

Question

1. While using direct load whether trigger get fired?
2. Is it possible to log the errors with triggers if any event get failed?
Say for example am have a trigger audit  with insert event on a table A.
is it possible to have any error table to monitor when the event get failed. Like the audit table or else track the failure operation with  the audit trigger.

Answer 1

1. While using direct load whether trigger get fired?
Oracle doesn't use direct-path INSERT if the target table has any triggers or referential constraints.
See the SQL Language doc:
http://docs.oracle.com/cd/E11882_01/server.112/e26088/statements_9014.htm
  The target table cannot have any triggers or referential integrity constraints defined on it.
So you would not be using direct-path if the table has any triggers.
2. Is it possible to log the errors with triggers if any event get failed?
Say for example am have a trigger audit  with insert event on a table A.
is it possible to have any error table to monitor when the event get failed. Like the audit table or else track the failure operation with  the audit trigger.
Yes and No - DML Error logging can put rejected rows into an error table so that the entire INSERT will not get rolled back.
But some datatypes are not supported and there are other restrictions also:
See the SQL Language doc
http://docs.oracle.com/cd/E18283_01/server.112/e17118/statements_9014.htm#SQLRF55101
Restrictions on DML Error Logging
  The following conditions cause the statement to fail and roll back without invoking the error logging capability: 
Violated deferred constraints.
  Any direct-path INSERT or MERGE operation that raises a unique constraint or index violation.
  Any update operation UPDATE or MERGE that raises a unique constraint or index violation.
  You cannot track errors in the error logging table for LONG, LOB, or object type columns. However, the table that is the target of the DML operation can contain these types of columns. 
If you create or modify the corresponding error logging table so that it contains a column of an unsupported type, and if the name of that column corresponds to an unsupported column in the target DML table, then the DML statement fails at parse time.
  If the error logging table does not contain any unsupported column types, then all DML errors are logged until the reject limit of errors is reached. For rows on which errors occur, column values with corresponding columns in the error logging table are logged along with the control information.
See also the direct-path and dml error logging sections of the DBA guide
http://docs.oracle.com/cd/E18283_01/server.112/e17120/tables004.htm#InsertDMLErrorLogging