ETERNUS SF Disk Space Monitor User's Guide - Microsoft(R) Windows Server(TM) 2003/Solaris(TM) Operating System/Linux - 13.0

20.3 Solaris/Linux-specific Messages

This section explains messages that are specific to Solaris and Linux

Event ID	Category	Message	Action
DSA0006E OCM0006E	Error	Could not open file <file>: <reason>	Check file permissions. If the reason cannot be determined, contact a systems engineer.
DSA0041E OCM0041E	Error	Unable to write to file <file>: <reason>	Check disk space in the <spooldir> directory and file permissions. If the reason cannot be determined, contact a systems engineer.
DSA0100E OCM0100E	Error	TIS: Unable to allocate a memory block	Contact a systems engineer.
DSA0101E OCM0101E	Error	TIS: Missing RDF or TDF file name	This error could occur for several reasons. There are several files used by TIS (such as dcm.trd and dcm.ttd) that are installed with the product - they may have been moved or deleted, or had their permissions changed. The collect.txt file may have been incorrectly modified to specify an invalid (or missing) '.tdf' filename. Attempt to correct the error, otherwise Contact a systems engineer.
DSA0102E OCM0102E	Error	TIS: Session not established	Contact a systems engineer.
DSA0103E OCM0103E	Error	TIS: Invalid control block	Contact a systems engineer.
DSA0104E OCM0104E	Error	TIS: The field defined in the RDF as a CLOCK field contains invalid data	Contact a systems engineer.
DSA0105E OCM0105E	Error	TIS: Invalid stream number	Contact a systems engineer.
DSA0106E OCM0106E	Error	TIS: Buffer size too small	Contact a systems engineer.
DSA0107E OCM0107E	Error	TIS: Syntax error in file <file>	TDF and RDF files are normally installed or created by the application. If a script for an action set file template was modified, correct the error and retry the operation. Otherwise contact a systems engineer.
DSA0109E OCM0109E	Error	TIS: Error stream returned as follows: <text>	Typically this message will contain detailed text for a previous error, such as a "parse" error. If the reason cannot be determined from the message text, contact a systems engineer.
DSA0110E OCM0110E	Error	TIS: Parse error = <error>	If the reason cannot be determined from the message text, contact a systems engineer.
DSA0111E OCM0111E	Error	TIS: Unspecified error = <error_code>	Contact a systems engineer.
DSA0150W OCM0150W	Warning	DSA: No more input records.	This is a warning. If displayed by DSA Listener, confirm the system has network connectivity. If displayed repeatedly on a system, stop and restart DCM to ensure all DSAs are running on the system.
DSA0151E OCM0151E	Error	DSA: Unknown record type.	This event occurs when an undefined record appears in internal processing.
DSA0152E OCM0152E	Error	DSA: Invalid function parameter.	Check the DSAconfiguration.txt settings, or revert to the last known good copy of the file. Otherwise, contact a systems engineer.
DSA0153E OCM0153E	Error	DSA: Invalid function usage	Check the DSAconfiguration.txt settings, or revert to the last known good copy of the file. Otherwise, contact a systems engineer.
DSA0154E OCM0154E	Error	DSA: The configuration file cannot be opened or has an invalid format	A plain text file named 'DSAconfiguration.txt' needs to be in the <basedir>/control directory AND each entry in this file needs to have the format described in the default 'DSAconfiguration.txt' file.
DSA0155E OCM0155E	Error	DSA: Unable to allocate a memory block	Free up memory on the system by closing applications not required, or consider adding additional memory to the system.
DSA0156E OCM0156E	Error	DSA: Internal record transfer failure	Contact a systems engineer.
DSA0157E OCM0157E	Error	DSA: Internal library error	Contact a systems engineer.
DSA0158E OCM0158E	Error	DSA: Interrupted operation	Stop and restart DCM. If the problem persists, consult a systems engineer.
DSA0159E OCM0159E	Error	DSA: Processing failure	Contact a systems engineer.
DSA0160E OCM0160E	Error	Unexpected error = <error>	Contact a systems engineer, providing details of the error message.
DSA0161E OCM0161E	Error	DSA: <DSA> not stopped	Issue the 'ps -e' command to obtain the pid of the DSA process, then issue 'kill -9 <pid>' command to stop the process. Contact a systems engineer if this occurs other than rarely.
DSA0162E OCM0162E	Error	DSA: Output record to DSA too long	Contact a systems engineer, providing details of the error message.
DSA0300E OCM0300E	Error	Number of arguments passed by DCMD is incorrect	Contact a systems engineer.
DSA0301E OCM0301E	Error	Error in arguments passed by DCMD	The most likely cause is an error in the parameters specified for a DCA in the collect.txt file. Note: Not all command parameters are valid for all Unix system types.
DSA0305E OCM0305E	Error	Failure in popen system call	Contact a systems engineer.
DSA0307E OCM0307E	Error	Failure to read from a opened pipe	Contact a systems engineer if this message is seen frequently.
DSA0308E OCM0308E	Error	Unable to expand the process table (realloc)	Contact a systems engineer.
DSA0313E OCM0313E	Error	Bad host name <hostname>	Correct the host name in the dca_net.cmd file and re-run.
DSA0315W OCM0315W	Warning	Error in argument passed by DCMD: %s	Correct the argument in the collect.txt file and re-run.
DSA0318E OCM0318E	Error	Unable to open the DCA specific parameter file	Edit the collect file and at the appropriate entry for the DCA enter a valid parameter file name that the DCA can use.
DSA0324E OCM0324E	Error	Error in opening /etc/mnttab file	Contact a systems engineer.
DSA0325W OCM0325W	Warning	Error in statvfs system call. Error = <error>. Mount point = %s.	Contact a systems engineer.
DSA0348W OCM0348W	Warning	Unsupported argument [<argument>] for this platform ignored	Remove the unsupported switch from the collect.txt file template.
DSA0350E OCM0350E	Error	Unable to write to file	Check file permissions. Correct the problem and re-run.
DSA0358E OCM0358E	Error	Error in forking/executing the <process>. Error=<error>	Contact a systems engineer.
DSA0366E OCM0366E	Error	Error in opening collection parameter file	This message is output when Agents are started without policies having been set up. Check whether policies have been set up correctly. This message is output when the "dcmstart.args" file cannot be accessed. Check the access rights and the existence of the file.
DSA0387E OCM0387E	Error	Record ID missing or invalid	This may occur if the file written by a DCA is corrupted, perhaps by a system or application crash. Otherwise, contact the system administrator.
DSA0388E OCM0388E	Error	malloc failed	Contact a systems engineer.
DSA0389E OCM0389E	Error	realloc failed	Contact a systems engineer.
DSA0406E OCM0406E	Error	Environmental variable(s) not available	Check that /etc/opt/ssqc/ssqc.conf has been modified correctly.
DSA0426E OCM0426E	Error	Error in allocating memory (malloc)	Contact a systems engineer.
DSA0503E OCM0503E	Error	Error in determining host from inet address	Contact a systems engineer.
DSA0506E OCM0506E	Error	Error in getting host name details using gethostbyname system call or requested hostname not found	Refer to the UNIX TCP/IP manual for conditions under which the above call fails and contact the system administrator.
DSA0513E OCM0513E	Error	Error in set signal disposition using signal system call	Contact a systems engineer.
DSA0516E OCM0516E	Error	Error in executing kill system call	Contact a systems engineer.
DSA0539E OCM0539E	Error	Error in opening the dca .cmd file	If the file does not exist, create it. If it does exist, check the access permissions.
DSA0540E OCM0540E	Error	Wrong format in the dca .cmd file. <file>	Correct the contents of the .cmd file in the /<basedir>/control directory.
DSA0541E OCM0541E	Error	SQL error in the dca .cmd file. <file>	Correct the contents of the .cmd file in the /<basedir>/control directory.
DSA0543E OCM0543E	Error	Bad data received from UNIX. <command>	This message is output when the output results of a command are in an unexpected format. This may happen in the following situations. When a command that uses a timer is executed, but the execution results are not returned within the collection interval, because of temporary load on the server or some other reason. When the output format of a command has changed because a new version of the command is now being used. When a working file for internally storing the execution results of commands is damaged, due to system panic or some other reason.
DSA0544E OCM0544E	Error	Input buffer capacity exceeded	Contact a systems engineer.
DSA0545E OCM0545E	Error	Command failed to complete	Contact a systems engineer.
DSA0550W OCM0550W	Warning	Input records not in sequence	This indicates that the raw data appears to be wrong and cannot be evaluated. The result of I/O error in the console command output. Check space allocations for the temporary directory. The specification of an invalid command path. Check the specification of the command path. The wrong command being accessed in the search path. Check that the correct command is found first in the system search path. A change in the system specification of the command output. Inform SERC.
DSA0551W OCM0551W	Warning	Transaction '%s' timed out	A script transaction has timed out. This is dependant upon the timeout value specified in the script for that transaction type. If the transaction timeout is set to the maximum, this probably indicates that the script is hanging up or looping. If necessary run tracing and check the timing of events.
DSA0552E OCM0552E	Error	Variable name <variable name> not found	Check the configuration file, correct the spelling or add the variable and re-run.
DSA0553E OCM0553E	Error	Variable <variable value> not quoted	Check the configuration file, identify and correct the problem and re-run.
DSA0554E OCM0554E	Error	Variable <variable value> too long	Check the configuration file, identify and correct the problem and re-run.
DSA0556W OCM0556W	Warning	Data for interval discarded due to '%s'. Command=%s	This message is output when the status changes within the monitoring interval due to the specification for an operating system command and information is not collected. Some collected data will be lost, but this is not really a problem. If this happens frequently, contact a systems engineer.
DSA0557W OCM0557W	Warning	Bad data received from command '%s': %s	This indicates that the raw data appears to be wrong and cannot be evaluated. The system is busy or overloaded. If this is a problem, consider reducing the amount of data collected. The result of I/O error in the console command output. Check space allocations for the temporary directory. The specification of an invalid command path. Check the specification of the command path. The wrong command being accessed in the search path. Check that the correct command is found first in the system search path. A change in the system specification of the command output. Inform SERC.
DSA0558E OCM0558E	Error	Error accessing the PDB	Correct the problem if possible, otherwise contact the system administrator.
DSA0559W OCM0559W	Warning	Bad SQL Statement	If a file template containing SQL has been modified incorrectly, correct it, otherwise contact a systems engineer.
DSA0566E OCM0566E	Error	Maximum command execution time of sample interval exceeded	Systemwalker Service Quality Coordinator executes the commands provided by the operating system and middleware, analyzes the output results, and stores them as performance information. This message is output when the commands do not terminate in 30 seconds for some reason (such as the machine remaining in high load status). No action is required unless this message continues to be output.
DSA0600E OCM0600E	Error	Scripting error detected at line %s in script '%s': %s	A TIS scripting error occurred and been trapped. Check the script logic.
DSA0601E OCM0601E	Error	Failed to open the Oracle oratab file	Check that the oratab file exists (for example /var/opt/oracle/oratab) and that the user specified in the <basedir>/control/dca_ora.cmd file has the necessary access permissions.
DSA0603E OCM0603E	Error	Failed to find <sid> in the Oracle oratab file	Check that the oratab file has not been corrupted, then either (a) have the Oracle systems administrator set up a sid with the name of sid, or (b) change the collect.txt file to specify the appropriate sid.
DSA0604E OCM0604E	Error	Failed to connect to DBMS with username '<username>', sid '<sid>', ORACLE_HOME '<environment value>'	Correct the error and, in the case of a command file or collect file error, re-start DCM.
DSA0618E OCM0618E	Error	Unrecognizable field type.	Edit the sql file in the <basedir>/control directory used to create the pdb (default is 'createpdb.sql'), and check all field types specified are compatible for SQLite databases.
DSA0619E OCM0619E	Error	Unexpected return from SQL statement.	Edit the sql file in the <basedir>/control directory used to create the pdb (default is 'createpdb.sql'), and check all statements.
DSA0620W OCM0620W	Warning	Oracle restart detected. Interval data is being discarded.	This is a warning only. No corrective action is needed.
DSA0621E OCM0621E	Error	Cannot access V$INSTANCE synonym, interval data may be incorrect after Oracle restart. <Oracle error text>	Contact a systems engineer.
DSA0641E OCM0641E	Error	Error in trying to fork a process	Contact a systems engineer.
DSA0642E OCM0642E	Error	Error trying to perform setsid system call	Contact a systems engineer.
DSA0643E OCM0643E	Error	Polling error	If the problem persists, contact a network administrator.
DSA0644I OCM0644I	Information	SIGHUP Signal received	No action required.
DSA0700E OCM0700E	Error	Environment variable PERFMGR_BASEDIR has not been set. Stopping.	This variable is normally automatically set by programs by reading the /etc/opt/ssqc/ssqc.conf file. Check that the /etc/opt/ssqc/ssqc.conf file has been modified correctly.
DSA0701E OCM0701E	Error	Call to uname failed. Cannot get host name. Stopping.	This is an internal Unix fault. Refer to your system documentation.
DSA0702E OCM0702E	Error	Collect file name not supplied. Specify '-c collect.txt' in dcmstart.args.	Specify the -c collect file parameter in <basedir>/control/dcmstart.args, i.e. -ccollect.txt.
DSA0703E OCM0703E	Error	Errors in command line arguments. Stopping.	This message is output when the dcmd command cannot be executed because of a problem with a command line parameter. Contact a systems engineer if the problem cannot be resolved from the information in the message.
DSA0704E OCM0704E	Error	Errors in collect file. Line <number> ignored. Fields: <fields>	The number of the line that is in error is displayed along with the fields that caused the error. Check the syntax of the line in question and correct any errors. Restart DCM.
DSA0705I OCM0705I	Information	All DCAs have stopped as requested. Stopping DCMD.	This is not an error. It logs when the DCM found that all the DCAs had stopped.
DSA0707I OCM0707I	Information	Signaling DCAs to stop	This is not an error. It logs when the DCM signaled the DCAs to stop.
DSA0709W OCM0709W	Warning	Collect file has no valid entries.	Ensure that collect.txt is correctly specified in the <basedir>/control/dcmstart.args file. Inspect collect.txt and correct any entries in error; ensure that at least one collection entry is specified.
DSA0712E OCM0712E	Error	<DCA/DSA><ID> stopped unexpectedly. Restarting.	This message is output when the monitoring process cannot be started because of a problem with a definition or the environment, and an attempt to restart is made. No action is required unless "SSQC1304E" is output after this message.
SSQC1304E	Error	Too many attempts to start process. DCM cannot restart %1.	This message is output when the monitoring process cannot be started even though attempts to restart it have been made.
DSA0713E OCM0713E	Error	<DCA/DSA><ID> keeps stopping. It will not be restarted.	If the reason cannot be determined from previous errors, contact a systems engineer.
DSA0714E OCM0714E	Error	Cannot write pidfile. Check file permissions.	Check the /<basedir>/control/ directory permissions. Correct the problem and re-run.
DSA0715E OCM0715E	Error	atexit() failed	Contact a systems engineer.
DSA0716W OCM0716W	Warning	File system free threshold reached. <directory>	Reduce the space usage of the file system by, for example, deleting redundant files.
DSA0717E OCM0717E	Error	Insufficient free file system space. <directory>	Reduce the space usage of the file system by, for example, deleting redundant files and re-starting DCM.
DSA0718W OCM0718W	Warning	Usage threshold reached. <directory>	Reduce the space usage in the directory by, for example, deleting redundant files.
DSA0719E OCM0719E	Error	Usage too large. <directory>	Reduce the space usage in the directory by, for example, deleting redundant files and re-starting DCM.
DSA0720E OCM0720E	Error	PERFMGR_SPOOLDIR not set	Set and export PERFMGR_SPOOLDIR in file /etc/opt/ssqc/ssqc.conf and re-run.
DSA0721E OCM0721E	Error	PERFMGR_SPOOLDIR directory not found	Set and export PERFMGR_SPOOLDIR in file /etc/opt/ssqc/ssqc.conf and re-run. Check that the specified directory exists and that it is accessible.
DSA0722E OCM0722E	Error	Too many corrupted files.	This may occur if the file written by a DCA is corrupted, perhaps by a system or application crash. It may be necessary to delete the corrupt file or files from the spool directory. Otherwise, contact the system administrator.
DSA0723E OCM0723E	Error	PERFMGR_DSADIR not set.	Set and export PERFMGR_DSADIR in file /etc/opt/ssqc/ssqc.conf and re-run.
DSA0724E OCM0724E	Error	PERFMGR_DSADIR not found	Check that the directory specified by PERFMGR_DSADIR in file /etc/opt/ssqc/ssqc.conf exists and that it is accessible.
DSA0725E OCM0725E	Error	More than <maximum> valid <DCA/DSA> entries specified	Inspect the appropriate file (collect.txt for DCAs or DSAconfiguration.txt for DSAs) and ensure that fewer than maximum entries are defined.
DSA0726W OCM0726W	Warning	Unable to change the directory to <dir_name>	Ensure that /<basedir>/bin exists and has suitable permissions. Otherwise contact a systems engineer.
DSA0727E OCM0727E	Error	DSA configuration file has no valid entries	Inspect DSAconfiguration.txt and correct any entries in error, ensuring that at least one DSA is specified. (This error can occur after a user comments out existing entries for testing purposes and all entries are accidentally marked as comments, or if all entries contain errors.)
6330	Error	Syntax error was found in side definitionfile.(file=%1, line=%2)	Contact a systems engineer.
6331	Error	Error occurred so stopped.(detail=%1, errno=%2)	Contact a systems engineer.
6333	Information	Definition file has been changed so it was reloaded.	No action required.