This section contains error messages for Adaptive Server dump and load commands.
16
Unable to write statistics for object %ld in database %ld. Please run update statistics on this table after loading this database or prior to accessing the table in the loaded database.
The systabstats system table stores table- and index-level statistics such as page and row counts, empty pages, number of leaf and non-leaf pages in an index, cluster ratios and average length of data and index rows for each object.
Descriptors are in-memory representations of Adaptive Server objects. Table descriptors contain (among other information) current statistics for the table. Adaptive Server periodically flushes these statistics to systabstats so that queries have access to the most current statistics for a table and its indexes. Statistics are flushed to systabstats during:
checkpoints
database dumps
the housekeeper task
update statistics
optdiag runs
sp_flushstats
Error 3019 is raised when Adaptive Server attempts to flush table statistics to systabstats during a database dump, but due to contention for the systabstats row or some other reason, the server is unable to write out the statistics.
Error 3019 is raised with the following states:
State |
Meaning |
|---|---|
1 |
Cannot flush statistics during a transaction. |
1 |
Failed attempt to flush statistics to systabstats. |
This is not a serious error. It indicates that the dump will not contain the latest statistics maintained in memory for the table, and consequently when the dump is loaded, systabstats will not contain the latest statistics.
You can resolve the issue by running update statistics for the table after loading the database.
The syntax for update statistics appears in the Performance and Tuning Guide.
11.9.2 and later
10
Unable to write statistics for index %ld of object %ld in database %ld. Please run update statistics on this index after loading this database or prior to using this index in the loaded database.
The systabstats system table stores table- and index-level statistics such as page and row counts, empty pages, number of leaf and non-leaf pages in an index, cluster ratios and average length of data and index rows for each object.
Descriptors are in-memory representations of Adaptive Server objects. Table descriptors contain (among other information) current statistics for the table. Adaptive Server periodically flushes these statistics to systabstats so that queries have access to the most current statistics for a table and its indexes. Statistics are flushed to systabstats during:
checkpoints
database dumps
the housekeeper task
update statistics
optdiag runs
sp_flushstats
Error 3020 is raised when Adaptive Server is unable to flush the statistics for an index to systabstats during a database dump. Since the systabstats on the dump will not contain the latest statistics for the index, a subsequent database load will result in systabstats containing outdated statistics for the index.
This is not a serious error, since the statistics can be readily updated. Queries can run normally even when systabstats does not contain the latest index statistics for the table.
You can resolve the issue by running update statistics after loading the database. Take these steps:
Identify the table and object named in the message. You can determine the table name using
1> use database_name 2> go1> select object_name(object_id) 2> go
where object_id is the object identified in the message.
Run update statistics, ensuring that the statistics for the index in question are included. Several options are available with update statistics, for example:
update statistics table_name index_name
update index statistics table_name
update index statistics table_name index_name
The syntax for update statistics appears in the Performance and Tuning Guide.
11.9.2 and later
16
Data on dump will not fit into current database. Need %d Mbyte database.
This error occurs when an attempt is made to load a database dump into a database smaller than the dumped database. You cannot use dump database or load database to shrink a database, regardless of the amount of actual data in the database.
If your goal is to load the database from the dump, you must increase the size of the database being loaded into to at least the configured size of the dumped database. You can do this with either the alter database command or by dropping and re-creating a larger database.
If your goal is to shrink the total size of a database, you cannot use dump and load. You must copy all the data out of the database using bcp, drop the database and re-create a smaller database, then re-create the database structure with scripts, and reload the data with bcp.
The database being loaded into must have identical data and log mapping, and identical segment mappings, as the dumped database. Refer to Error 2558 and the System Administration Guide for more information.
All versions
16
The database you are attempting to LOAD was DUMPed under a different sort order ID (%d) or character set ID (%d) than the ones running on this server (SortOrd = %d, CharSet = %d). If the sort orders differ, at least one of them is non-binary.
A database cannot be loaded into a Server using load database unless the sort order of the Server that dumped the database matches the sort order of the Server being loaded into. Error 3120 occurs when you try to load a database on an Adaptive Server with a different sort order from that of the dumped database.
You have the following options:
Move the data via bcp rather than load.
Change the sort order of the Adaptive Server. Refer to “Configuring Character Sets, Sort Orders, and Languages” in the System Administration Guide for instructions.
If the server into which you are attempting to load is a new server, you can:
Reinstall the server with the correct sort order
Re-create the databases with the load option
Retry the load
All versions
16
No dump device has been specified.
This error may be caused by a hardware problem.
This error occurs when Adaptive Server is unable to access a dump device during a database dump . This error is fatal and stops the dump from completing.
Error 3201 is most likely caused by one of the following:
The device you specified for the dump is offline or otherwise unavailable to Adaptive Server.
Permissions for the dump device are not set correctly for user “sybase” or the user performing the dump (read and write privileges are required).
A previous dump aborted and Adaptive Server believes the dump device is still in use.
Check to make sure the device you specified is defined for your Adaptive Server:
1> select * from master..sysdevices 2> where status = 16 or status = 24 3> go
low high status cntrltype name phyname mirrorname --- ------ ------- ---------- ---------- ---------- --------- 0 20000 16 3 tapedump1 /dev/rmt4 NULL 0 20000 16 2 tapedump2 /dev/rst0 NULL
If the device is not there, you can use sp_addumpdevice to add it.
At the operating system level, check the permissions for the dump device for user “sybase” or the user performing the dump (read and write privileges are required).
If you have still not solved the problem, check your operating system error log for operating system errors. If no errors are logged in your operating system error log and there are no other errors in your Adaptive Server or Backup Server error log, contact Sybase Technical Support for assistance.
Refer to “Specifying the Database and Dump Device” in the System Administration Guide for information about dump devices.
If you call Technical Support, have the following information on hand:
Server version and SWR Rollup level
Backup Server version
Adaptive Server and Backup Server error logs
Text of all error messages
select * from sysdevices output
Operating system error log
All versions
16
Backup Server has detected a SQL Server error.
This error may be caused by a hardware problem.
Error 3203 is displayed when a problem occurs with a remote procedure call to the Backup Server. In this case, the error is on the Adaptive Server side.
The error message output includes:
vsn – the virtual socket number.
return – the return value: 0 means successful; -2 means failure.
status – the ending status, displayed in decimal value. The most common value is 524288 which usually means an I/O error.
Some causes are:
Write protect is turned on (it must be off when loading a tape because the device is opened read/write).
No dump exists on the media being accessed (for example, a blank tape or the wrong device specified).
The media that contains the dump is not readable.
Check the Adaptive Server and Backup Server error logs to determine the cause of the error being sent from the Adaptive Server.
Test the connection between the Backup Server and the Adaptive Server by logging into the Adaptive Server through isql and typing:
1> execute backupserver...sp_ps 2> go
where backupserver is the name of your Backup Server. This executes sp_ps on the Backup Server.
If you need to call Technical Support, have the following information on hand:
Server version and SWR Rollup level
Backup Server version
Adaptive Server and Backup Server error logs
Text of all error messages
Operating system error log
All versions
20
DUMP failed in database %.*s: error occurred executing RPC.
When a dump database command is processed, the Backup Server scans for allocated pages to determine what pages to dump. It begins this scan as soon as it receives an RPC (remote procedure call). Error 3211 is raised when an Adaptive Server RPC to the Backup Server returns an error.
Error 3211 occurs with the following states:
State |
Meaning |
|---|---|
1 |
An error occurred in the RPC stream. |
2 |
The RPC itself returned an error. |
Check the Adaptive Server and Backup Server error logs to determine the cause of the error being sent from Adaptive Server.
Test the connection between the Backup Server and the Adaptive Server by logging into the Adaptive Server through isql and typing:
1> execute backupserver...sp_ps 2> go
where backupserver is the name of your Backup Server. This executes sp_ps on the Backup Server.
If you need to call Technical Support, have the following information on hand:
Server version and SWR Rollup level
Backup Server version
Adaptive Server and Backup Server error logs
Text of all error messages
Operating system error log
All versions
20
DUMP failed in database %.*s: unexpected status executing RPC: %d.
Dumps and loads are performed by an Open Server program known as Backup Server. Adaptive Server communicates with Backup Server using Remote Procedure Calls (RPC's). When a dump database command is processed, for example, Adaptive Server uses RPC's to send parameters to Backup Server. Error 3212 is raised when an Adaptive Server RPC to the Backup Server returns an unexpected status which Adaptive Server cannot process.
Check the Adaptive Server and Backup Server error logs to determine the cause of the error.
Test the connection between the Backup Server and the Adaptive Server by logging into the Adaptive Server through isql and typing:
1> execute backupserver...sp_ps 2> go
where backupserver is the name of your Backup Server. This executes sp_ps on the Backup Server.
If you need to call Technical Support, have the following information on hand:
Server version and SWR Rollup level
Backup Server version
Adaptive Server and Backup Server error logs
Text of all error messages
Operating system error log
All versions
10
Backup Server session id is: %ld. Use this value when executing the 'sp_volchanged' system stored procedure after fulfilling any volume change request from the Backup Server.
Dumps and loads are performed by an Open Server program known as Backup Server. During the backup and restore process, it may be necessary to change tape volumes. If Backup Server detects the need to change the currently mounted volume, it requests a volume change by sending messages to either the client or its operator console. After mounting another volume, the operator notifies Backup Server by executing the sp_volchanged system procedure on Adaptive Server.
3216 is an informational message that Backup Server issues when starting a dump or load operation. The message notifies the operator of the current session ID; the operator needs this information if it becomes necessary to execute sp_volchanged during the dump/load operation.
This is an informational message. No action is necessary.
All versions
21
I/O failed while attempting to clear pages starting at page %ld of disk number %ld.
This error may be caused by a hardware problem.
During a load database, create database, or alter database command, Adaptive Server initializes the non-allocated database pages. Error 3225 occurs if an I/O error occurs during this process.
This error can be caused by an operating system problem such as insufficient disk space (for a file system) or a disk going offline.
Check your operating system error logs to determine whether you have run out of disk space or are having other problems that could explain the I/O errors. Refer to “Checking the Operating System Error Log” in Encyclopedia of Tasks for assistance.
All versions
24
For logical disk device '%.*s', neither primary device '%.*s' nor secondary device '%.*s' is active. %s cannot continue.
During dumps and loads, Adaptive Server must translate the logical device names into physical device names and pass these to Backup Server, which performs the dump/load. For each device, Adaptive Server first checks whether the primary physical device is in the active state; if not, it checks whether the secondary (mirror) device is active.
Error 3230 is raised when neither the primary nor secondary devices are active. This is a fatal error which breaks your connection to Adaptive Server.
The error may be caused by:
the device being offline
an Adaptive Server problem, which results when you create a device using a previously used vdevno.
Examine the Adaptive Server error log and the operating system log to see if the device(s) used in the dump/load are offline or otherwise unavailable to the server. See “Checking the Operating System Error Log” in the Encyclopedia of Tasks chapter for assistance.
If the device(s) are active, shut down and restart Adaptive Server, and retry the dump/load operation.
Have the following information ready when you call Sybase Technical Support:
Server version and SWR rollup level
Text of all error messages.
All versions
17
%s for database '%S_DBID' failed: an alarm function could not be installed.
Dumps and loads are performed by an Open Server program named Backup Server. In preparation for the dump, Adaptive Server must install an alarm function, which is a timing mechanism required during the dump. Using the alarm function, Backup Server can go into a `sleep' state at an appropriate point and awaken periodically to check the progress of the dump.
Error 3233 is raised when you perform a dump, but there are not enough alarms available to allow Adaptive Server to install an alarm function for the dump, causing the dump to abort.
The available alarms are controlled by the configuration parameter number of alarms. To resolve the problem, change the value of number of alarms to a number larger than the current value.
Refer to No More Alarms Available Error for directions on increasing the number of alarms.
Since the waitfor command utilizes alarms, frequent use of the command can also lead to 3233 errors. Check use of this command in statement blocks, stored procedures and transactions.
All versions
18
Unable to obtain the SQL Server's current working irectory. The SQL Server must have search permission on its current working directory and the name must be shorter than %d bytes.
Dumps and loads are performed by an Open Server program known as Backup Server. When you issue a dump database or load database command, Adaptive Server communicates certain information about its working environment to Backup Server. Error 3240 is raised when Adaptive Server is unable to determine its current working directory for Backup Server.
This error commonly occurs when Adaptive Server is started from a directory other than the sybase home directory; the user ID of the user starting Adaptive Server may not have the appropriate permissions for the directory from which it was started.
To resolve the error, check that the SYBASE variable is set to the correct sybase home directory and is no longer than 255 bytes.
Make corrections if necessary, and restart Adaptive Server.
Scripts that start up Adaptive Server must always set the directory to the sybase home directory before starting Adaptive Server.
All versions
