Login | Sign Up
ErrorKey - Search engine for Error codes and messages     
  Windows NT  [ 735 result(s) ]
 1501 Severity Level 20  -  Sort failure  SYBASE SQL Server
This error occurs during index creation when SQL Server fails to complete a sort operation. There are a number of different states for this error, each indicating a different reason for the failure: When this error occurs, no index is created. In SQL Server release 10.0 and later, the configuration parameters csortbufsize and csortpgcount control how SQL Server uses memory during sorting. csortbufsize controls the sort buffer size and State Meaning 2 When creating a high-level index structure, SQL Server is unable to build a parent node in the ancestor list. 3 When creating a high-level index structure, SQL Server is unable to build a parent node from the root of the tree. 4 When creating a high-level index structure, SQL Server is unable to build a parent node from the new root of the ancestor tree. 6 This state occurs when SQL Server is adding the results of an internal sort of a special leaflet node to an external merge in progress and a single internal merge step has a merge order greater than 8. 7 This state occurs when SQL Server is adding the results of an internal leaf merge node and the previous merge step caused the merge order to be greater than 8. 8 This state occurs when SQL Server is starting a non-sort of already sorted data to create a clustered index and it cannot find a page to an index that was supposed to have been built for the sorted data. 9 This state occurs when SQL Server is unable to allocate and initialize space for managin
1. If you have not changed the values of csortbufsize or csortpgcount, call Sybase Technical Support. 2. To determine your current values for the csortbufsize and csortpgcount variables, shut down SQL Server and enter the following command (see below for syntax for operating systems other than UNIX): % buildmaster -yall -dmaster_device | grep sort 3. To change the value of csortbufsize (use similar commands for csortpgcount), enter one of the following commands: 4. Restart SQL Server and retry the index creation command that generated the 1501 error. 5. If you are unable to resolve this error by adjusting the csortbufsize and csortpgcount values (for example, setting them back to 0), call Sybase Technical Support. Additional Information See create index in the SQL Server Reference Manual and the Transact- SQL User’s Guide for information about creating indexes. Operating System Command UNIX % buildmaster -ycsortbufsize=new_value -dmaster_device VMS $ buildmaster /alter="csortbufsize=new_value" /disk="master_device" OS/2, Microsoft Windows NT bldmastr -ycsortbufsize=new_value -dmaster_device Novell NetWare LOAD BLDMASTR -ycsortbufsize=new_value -dmaster_device Stratus VOS buildmaster.pm -ycsortbufsize=new_value -dmaster_device
 No More Alarms Available Error  -  uasetalarm: no more alarms available  SYBASE SQL Server
The Transact-SQL command waitfor defines a specific time, time interval, or an event for the execution of a statement block, stored procedure, or transaction. SQL Server uses alarms to carry out waitfor commands correctly. The number of alarms needed by SQL Server is related to the requirements of an application and the number of instances of that application being run simultaneously. The maximum number of alarms available for use by SQL Server is controlled by the cnalarm configuration parameter. When SQL Server needs more than the number of alarms available, the message “uasetalarm: no more alarms available” is written to the error log.
1. Shut down SQL Server. (SQL Server must be shut down before any buildmaster commands are run.) 2. Determine the current value of cnalarm (this example shows syntax for UNIX; refer to the examples below for syntax for other operating systems): % buildmaster -yall -dmaster_device | grep cnalarm where master_device is the name (including path) of the master device for this SQL Server. 3. Change the value of cnalarm to a value larger than the current value: - UNIX: % buildmaster -ycnalarm=new_value -dmaster_device - VMS: $ buildmaster /alter="cnalarm=new_value" - /disk="master_device" - OS/2, Microsoft Windows NT: bldmastr -ycnalarm=new_value -dmaster_device - Novell NetWare: LOAD BLDMASTR -ycnalarm=new_value -dmaster_device - Stratus VOS: buildmaster.pm -ycnalarm=new_value -dmaster_device 4. Restart SQL Server. Each alarm structure uses 20 bytes of memory. If you raise the value of cnalarm significantly, readjust SQL Server’s memory use accordingly.

Kerberos Errors (1)
SQL Server Analysis Services (SSAS) (1)
SQL Server System Error Messages  (12)
SQL Server Distributed Queries Error Messages  (1)
SAP R/3 Error Code (2)