DBA5000-5999

DBA Message ID	Message	Explanation	User Response
DBA5006E	`evname` is an Event Monitor that writes to a named pipe. Event Analyzer does not support PIPE Event Monitors.	The Event Analyzer only handles traces produced by FILE Event Monitors.	Use a FILE Event Monitor.
DBA5007E	Event Monitor `event-monitor` does not exist.	The Event Monitor names specified with the -evm option could not be found in the catalogs for the database specified with the -db option. The Event Monitor may have been dropped or you may be trying to connect to the wrong database.	Make sure that the Database alias specified with the -db is properly cataloged and that the Event Monitor has not been dropped. If the latter is the case, re-create the event monitor.
DBA5250I	The number of records retrieved exceeded the limits of the window. A partial list is displayed.	The window height required to display the retrieved objects exceeds a system limit.	You can reduce the number of objects displayed in the window by doing the following: If the “Include” choice is available on the “View” menu, you can specify a subset of the objects to display in the window. When you select “Include”, a window appears and prompts you for a sub set of the criteria.
DBA5300E	Event Analyzer invocation error. Usage: db2eva [ - db database-alias -evm evmon-name ]	The command parameters for the db2eva command are: -db database-alias specifies the database for which the Event Monitor is defined, as cataloged on the machine where the trace is analyzed. -evm evmon-name the Event Monitor trace tables you want to analyze. The event monitor must be defined in the database specified in the -db parameter. If you specify the database and event monitor names, db2eva connects to the database, and issues a 'select target from sysibm.syseventmonitors' to locate the table where the Event Monitor writes its trace. The Event Monitor and related tables must not have been dropped when using this mode. If you do not specify any parameter, a dialog box will be opened to prompt for the database alias and the event monitor name you want to analyze.	Re-issue the command with valid arguments.
DBA5311E	Event Monitor invocation error. Usage: db2emcrt database-alias	The command parameter for the db2emcrt command is: database-alias specifies the database for which the event monitors are to be created or analyzed, as cataloged on the machine the db2emcrt command is invoked. database-alias overrides the database name specified in the trace.	Re-issue the command with valid arguments.
DBA5350E	An error occurred while opening file `file-name`.	The specified file could not be opened in read-only mode for an unknown cause.	Check the spelling of the directory specified by the -path option, its access authority, and that it contains a non-empty, readable trace file called 00000000.evt. NOTE: The first trace file for an Event Monitor is always named 00000000.evt and cannot be renamed.
DBA5351E	File `file-name` cannot be found.	There is no 00000000.evt file in the directory specified by -path.	Check the spelling of the directory specified by the -path option, its access authority, and that it contains the trace file 00000000.evt. NOTE: The first trace file for an Event Monitor is always named 00000000.evt and cannot be renamed.
DBA5352E	Path `path-name` cannot be found.	The -path option specifies a directory that does not exist.	Check the spelling of the directory specified by the -path option, its access authority, and that it contains the trace file 00000000.evt. NOTE: The first trace file for an Event Monitor is always named 00000000.evt and cannot be renamed.
DBA5353E	Access to `param-1` was denied.	The specified file could not be opened in read-only mode. The -path option may be specifying a directory to which you do not have sufficient access authority.	Check the access authority to the directory specified by the -path option. Verify that no one has locked the specified file in exclusive mode.
DBA5354E	The data cannot be read from `file-name`.	The Event Monitor trace file contains unexpected data, or cannot be accessed. The trace file was likely corrupted during transmission or has been removed.	Transmit your trace files from your server again. When transmitting trace files from a remote server, ensure that the transmission is done in binary mode.
DBA5355E	An Event Monitor log header could not be found in `file-name`.	The first file written to by an Event Monitor is named 00000000.evt and contains a data structure that identifies the trace characteristics. This data structure could not be read. Possible causes: The trace file was corrupted. The trace file is empty. This can happen if the Event Monitor is active but, has not flushed its buffers yet.	If the trace was transmitted from a remote server, retransmit, ensuring that the transmission is done in binary mode. If the trace file is empty, turn off the Event Monitor to force it to flush its buffer.
DBA5356E	Byte order not valid in `file-name`.	The Event Monitor log header (the first record written to a new trace) specifies whether the trace contains little-endian or big-endian (e.g., AIX) data. The value found in the trace file specified neither of these two supported types of data. The trace file was likely corrupted during transmission.	Transmit your trace files from your server again. When transmitting trace files from a remote server, ensure that the transmission is done in binary mode.
DBA5357E	Unexpected data was found at offset `offset-value` in file `file-name`.	The Event Monitor trace file contains unexpected data. The trace file was likely corrupted during transmission.	Retransmit your trace files from the server, ensuring that the transmission is done in binary mode.
DBA5358I	Cannot browse local file system without an active local Administration Server.	The file browser requires a Database Administration Server (DAS) instance to browse file systems. If this is a client installation, the DAS instance is not present and local file browsing is disabled.	For server installations, ensure the DAS instance is started and retry the operation.
DBA5500E	A system error has occurred. The Event Analyzer tool could not continue processing.	For an unknown reason a system error has occurred when trying to initialize the application environment.	Re-issue the command.
DBA5501W	Do you want to delete the event files associated with the event monitor `evname` that you are removing?		To delete the event files for the selected event monitor, click on OK. If you do not want to delete the event files, but still want the event monitor removed, click on NO. If you do not want to remove the event monitor, or delete the event files click on CANCEL.
DBA5502E	No selection was made from the list of Event types. You must select one or more types from the list.	When creating an event monitor, at least one Event type must be selected.	Select one or more of the Event type check boxes from the Create Event Monitor window.
DBA5503I	An Event monitor `evname` has been successfully created.	The event monitor has been successfully created and has been added to the database list of event monitors.	Click on OK to remove the message.
DBA5504W	Some event monitors were not removed because their event files could not be deleted. See the messages page from the journal notebook for the list of event monitors not removed.	Some of the selected event monitors may have been successfully removed, but others were not, because their associated event trace files could not be deleted. This occurs when either event files are read-only, or they are being used by another active process.	See the message page of the journal notebook for the list of event monitors that were not removed. To delete the files, end the process using them and check the access authority for the files. Then select the event monitor from the list of event monitors and choose remove from the menu.
DBA5505E	Maximum file size was not specified.	If maximum file size in 4K pages is selected on the create event monitor Options window, then the maximum size of the event files must be specified.	Enter a maximum file size of between 1 and 2,147,483,647 4K pages, or you can select the No Maximum option. If the No Maximum option is selected, the maximum number of event files is 1.
DBA5506E	Maximum number of files was not specified.	If Maximum number of files is selected on the create event monitor Options window, then the maximum number of event files must be specified.	Enter a maximum number of event files of between 1 and 2,147,483,647, or you can select No Maximum option.
DBA5507E	Buffer size was not specified.	An event monitor Buffer size in 4K pages must be specified.	You must enter an event monitor buffer size of between 1 and 2,147,483,647 4K pages.
DBA5508W	Do you want to delete the event files associated with the event monitors that you are removing?		To delete the event files for the selected event monitors, click on OK. If you do not want to delete the event files, but still want the event monitors removed, click on NO. If you do not want to remove the selected event monitors, or delete the event files click on CANCEL.
DBA5509E	The name entered for the event monitor is not valid.	The name entered in the event monitor Name field contains one or more characters that are not allowed. An event monitor can contain alphanumerics and must begin with a letter.	Remove from the name any characters that are not alphanumeric and make sure the name begins with a letter.
DBA5510E	When trying to activate the monitor, the directory for its data files was not found.	When activating an event monitor, the directory that was specified when the event monitor was created must exist. In order to flush its buffers, an event monitor needs an existing file and path.	Create the directory that was specified when creating the event monitor. Try to activate the event monitor again.
DBA5511E	Entry `name` is not valid because the value is out of the acceptable range.	The values for an event monitor's Maximum file size, Maximum number of files, and Buffer size must be between 1 and 2,147,483,647.	Enter a value in the entry fields that is within the given range.
DBA5512E	The character `character` entered for the event monitor name is not allowed.	A character entered in the event monitor name entry field is not a valid character for an event monitor name.	Remove from the event monitor name any characters that are not alphanumeric and make sure the name begins with a letter.
DBA5513E	The dynamic link library “DB2EVA.DLL” could not be loaded successfully.	During the initialization of the event analyzer the dll could not be loaded because the dll has been deleted or removed.	Reinstall the event analyzer by selecting the performance monitor during the installation process.
DBA5514I	The event files for event monitor `evname` could not be deleted.	The event files for the event monitor could not be deleted because the files are being used by an active process or are read-only.	To delete the files, end the process that is using them and check the access authority for the files. Select the event monitor again and choose remove from the menu.
DBA5515E	The database alias name or database name `dbname` could not be found.	The alias name that was entered on the command line has not been cataloged on this machine.	Either catalog the alias on this machine and reenter the command or re-issue the command with a valid alias name.
DBA5516W	Viewing the trace for this event monitor may take some time. Do you wish to continue processing?	The user has requested to view a large trace for an event monitor. Reading the files could take some time to complete.	If you want to continue processing the trace click on OK. If you do not wish to continue processing the trace file then click on NO.
DBA5517E	The event monitor could not be started due to a reason code of `reason-code`.	The event monitor could not be started for the reason specified by `reason-code`: The event monitor path is invalid. The device, where the event monitor is to be started, is not ready. Attachment to the admin server failed.	To start the event monitor, make sure that the event monitor path is valid, the admin server started, and the proper authorities exist on the device. Click on OK. If the problem persists, manually create the event monitor directory on the device and click on OK. To create the event monitor without starting it, deselect the Start now check box and click on OK.
DBA5518E	The event monitor could not be started because its output directory could not be created.	The directory could not be created for one of the following reasons. Proper authorities do not exist for creating directories on the requested file system. Create event monitor does not support directory creation on non-Intel platforms. Cannot create a directory of greater than 8 characters on a FAT file system.	Make sure the proper authorities exist for directory creation. On non-Intel platforms create the event monitor output directory manually.
DBA5519I	Event monitor table cannot be found in the event source database.	The event monitor table that holds the event monitor records cannot be found in the source database specified.	Ensure that the event monitor table exists in the source database and the table name is in the SYSIBM.SYSEVENTTABLES.
DBA5520E	Event monitor control table cannot be found in the event source database.	The event monitor control table cannot be opened.	Ensure that the event monitor control table exists in the source database and the table name is in the SYSIBM.SYSEVENTTABLES.
DBA5521I	Connection to the database is not established. The event monitor list cannot be retrieved.	A connection to the database is not established.	Please make sure the database manager command has been issued. If the problem persists, contact IBM Service.