For database server-managed auditing, the -n option to the onaudit utility closes the current database server audit file, stores it in a specified directory, and opens a new audit file named servername.integer. The servername value is the name of the database server being audited, and integer is the next available integer. For example, if the last audit file saved for the maple database server was named maple.123, the next audit file is saved in a file called maple.124.

For Extended Parallel Server, the -n option to the onaudit utility closes the current database server audit file, stores it in the audit-file subdirectory for each coserver, and opens new audit files named servername.integer in each coserver-specific subdirectory of the path you specified for audit-file storage.

The subdirectory name is of the form servername.coserver_id, which combines the name of the database server and the number of the coserver that hosts the audit file. All audit files are stored locally on the coserver when the audited event occurs. Only one audit file directory exists for each coserver. The names of audit files in this directory are in the same form as for Dynamic Server. For more information, see Audit File Names.