This section uses Unix syntax and examples. For the
equivalent Windows information, refer to your Utility
Programs guide for Windows.
Let us say that your master device is full and is producing 1105 errors (system segment is full). As a last resort, you have run the dump transaction command with the truncate_only or no_log option, which did not free any database space. You cannot even run alter database to add rows to the sysusages system table, because the system segment is full. This section details how to manually rebuild Adaptive Server in this common situation, focusing on these six system tables:
sysdevices represents the available physical devices.
sysdatabases represents the databases known to Adaptive Server.
sysusages plots how individual databases use the device fragments, such as for data and transaction logging.
syslogins holds the login information about users allowed to work in the server.
sysconfigures contains the user-settable configuration parameters.
syscharsets contains the character sets and sort orders defined for Adaptive Server use.
Your Adaptive Server configuration may include other system tables of critical importance. If so, be sure to include them when recreating the original environment. For example:
sysservers holds the names of other remote servers.
sysremotelogins contains the login information for the remote hosts.
sysloginroles may be necessary for sites doing extensive group/security work.
The following procedures rely on the bcp command. If bcp is unavailable, see “If You Cannot Use bcp or a Dump”.
