There are times when Integration Server will automatically reset the destination from Database to File (for example, when Integration Serverstarts up and the Audit Log function cannot connect to the external RDBMS or when the Audit Log function connects to the external RDBMS but it becomes unavailable for subsequent sessions). In such cases, Integration Server will change the destination for all loggers that are capable of writing to a file (such as the Error, Session, Service, Security, Guaranteed Delivery, API Gateway transaction loggers, and so on) to File. The loggers that can only write to RDBMS (such as the Document and Process Engine loggers) will become unavailable. When Integration Server restarts and the connection to the database is restored, Integration Server will set the destination for the loggers back to Database.

During audit logging, database errors are returned from the database drivers as SQLExceptions that contain a numeric code that represents an error or warning. If the numeric code is listed in the Integration Server_directory \instances\instance_name\config\auditing\transient.sql.errors.xml file, Integration Server considers the error to be transient. If the numeric code is not listed in that file, Integration Server considers the error to be non-transient. If you discover transient errors that are not listed in the transient.sql.errors.xml file, modify the file to include numeric codes for those errors.