2.1 Can't create the database

The runtime database cannot be created. The following message is displayed:

Cannot create database directory: <reason>

The runtime database cannot be created in the directory specified by the environment variable SNMDBDIR. If you did not specify the SNMDBDIR environment variable, the runtime database would be created in the directory specified in the snm_conf file. By default, they are /var/adm/snm for a Solaris 1.x machine or /var/opt/SUNWconn/snm for a Solaris 2.x machine

Usually <reason> will indicate the source of your problem. Check that the directory exists and is writable. Make sure that you have at least 1 Mbyte of disk space available in the directory.

2.2 Invalid Database Entries

If you choose the about option for loading ASCII databases and if the ASCII database file contains one or more invalid entries, the loading will abort.

The Console displays the line number in the file where the error is detected and a brief description of the error. All definitions in the file are backed out of the runtime database. Any other files that do not have errors are correctly read into the runtime database. Edit and fix the particular file that could not be loaded and reload it. There are two ways to reload the file:

1. If the Console is opened, invoke File >> Load >> Management Database. In the Load window you then receive, double-click SELECT on the name of the corrected file.

2. Restart the Console, specifying only the corrected file, by entering:

host% snm <corrected_file>

This causes the last runtime database (containing only those files that were read correctly) to be loaded, along with the corrected file. If you want to replace the runtime database instead of merging the database in <corrected_file>, above, with the runtime database, use the -i option as shown in Startup Commands section.

If you choose the replace option, the duplicates will be taken from the ASCII databases. The default is the ignore option, which ignores the duplicates.For more informatin on how tochoose the option, see the Administration Guide.

2.3 Not enough disk space

Not enough disk space is available for the runtime database.

This is generally indicated by a message like the following in your system console log:

netisam: not enough disk space: unix errno 28

Another possibility is a system console (not SNM Console) message: <filesystem_name> filesystem full. For either message, see the beginning paragraphs under "Letting Discover Build Your Database" for general information about disk space requirements for the SunNet Manager database. For a list of common NetISAM messages and descriptions, see the appendix in this Guide.

2.4 Missing information

You have specified a view on the Goto line that is not in the database. If this happens, the current view remains and the Goto line is cleared.

2.5 Already existing names in the database

Element name already exists.

If the element instance you are trying to create already exists in the runtime database, the following message appears in the footer of the element Properties window:

Cannot create; name already exists!

Only one element instance definition can exist for an element name. Once you have created an element instance, you can copy the glyph into different views (see "Copying Elements). To find instances of an element, refer to the instructions in "Finding Elements".

2.6 Extra elements in the database

There are multiple instances of an element in a database.

Use the Find option of the View menu to locate all instances of an element--see "Finding Elements". Within each view, delete the element.

2.7 Can't save the database

The path you specified does not exist or is not writable.

If the specified path is not a writable path, the following message appears in the footer of the Console:

Cannot open <file> - save failed.

Verify that the path exists and is writable.

2.8 Can't open a file

The following message appears in the Console footer:

Cannot open <file> for writing

This message could occur because the file name you specified does not have write permission. Make sure the directory has the appropriate permissions for access.

2.9 Can't save Strip Chart and Indicators in the Database

When a request is loaded from an ASCII file and the Restart field of the request has previously been set to True, Indicators and Strip charts associated with the display of the returned attribute values appear in the view from which the request was originally started. This occurs even if you moved the Indicator or Strip Chart into a different view before saving the runtime database to an ASCII file. (The reason for this is that Strip Charts and Indicators are not saved when you perform a save-database operation.)

2.10 Can't load icons and rasterfile into the database

Too many icons and rasterfiles are already loaded into the runtime database.

If the following message appears, you need to reduce the number of icons or rasterfiles in the runtime database.

Cannot load more than 1024 icons/rasterfiles