This section contains error messages raised by Adaptive Server system procedures.
When system procedure error messages are raised, the error number is displayed as 0 and the global variable @@error returns 0. This section includes non-zero error numbers along with the error message text. If you call Sybase Technical Support about an error in this section, include the error number that is shown here even though that number was not displayed when the error was raised.
0
Object does not exist in this database.
This error occurs when the object you specified does not exist in the current database when you run any of the following stored procedures:
sp_auditobject
sp_auditsproc
sp_depends
sp_estspace
sp_foreignkey
sp_help
sp_helpartition
sp_helpconstraint
sp_helpindex
sp_helptext
sp_primarykey
sp_procqmode
sp_remap
sp_spaceused
Make sure you are in the database in which the object resides before entering the stored procedure command.
Use the owner name in your object name specification if you are not the object owner.
All versions
0
The last-chance threshold for database %1! is now %2! pages.
This informational message is displayed when a last-chance threshold has been established on a newly created log device (sp_logdevice), or an existing one has been adjusted after a procedure which alters the size of a log device was executed (sp_dropsegment, sp_extendsegment). The threshold is established automatically by Adaptive Server.
No action is necessary.
All versions
0
Could not update the last-chance threshold for database %1!
Procedure lct_admin is run automatically when any attempt is made to add or modify the log segment of a database with sp_logdevice, sp_dropsegment, or sp_extendsegment. Error 17716 occurs when an attempt to run such a command has failed.
Check other messages displayed near the attempted command. They may give you additional information regarding the failure of lct_admin or may indicate the original command was not successful. If the command appeared to run successfully, except for this error message, contact Sybase Technical Support about evaluating the current status of the last-chance threshold in this database.
Before calling Technical Support, have the following information available:
Server version and SWR version level
Server error log
Text of all error messages
All versions
0
Partitioned objects cannot be moved.
Adaptive Server does not allow you to use sp_placeobject on partitioned objects. Error 17737 occurs when you try to use sp_placeobject to change future space allocations for a partitioned table.
If you want to use sp_placeobject on the table, use the unpartition clause of the alter table command to concatenate all partitions:
1> alter table table_name unpartition 2> go
Then run your sp_placeobject command again.
Refer to the Reference Manual for information about alter table and sp_placeobject.
All versions
0
Table '%1!' does not exist in database '%2!' -- cannot add thresholds.
systhresholds should exist in every database in Adaptive Server. Error 17870 occurs when the system table systhresholds does not exist in the current database, and sp_addthreshold or sp_modifythreshold was not able to add or modify the requested threshold.
Run dbcc checkalloc and dbcc checkdb to determine if the database is corrupted.
Contact Sybase Technical Support if systhresholds is missing from a database.
Have the following information ready when you call Technical Support:
Output of select @@version
Output of all error messages
Output of dbcc commands
Refer to “sp_addthreshold” in the Reference Manual for additional information.
All versions
0
There is no segment named '%1!'.
This error occurs when an attempt is made to add, drop, or modify (using sp_addthreshold, sp_dropthreshold, or sp_modifythreshold) a segment that does not exist in the current database.
Run sp_helpsegment to display segment information about the current database. If the segment does exist, check that you have spelled it correctly in your procedure. If the segment does not exist and you believe it has been dropped, use sp_addsegment to add it back.
If the requested segment does not exist and you are certain no one has dropped it, run dbcc commands to check the integrity of the database.
Refer to “sp_addthreshold” in the Reference Manual for additional information.
All versions
0
This threshold is too close to one or more existing thresholds. Thresholds must be no closer than 128 pages to each other.
This error occurs when an attempt is made to add or modify thresholds sp_addthreshold or (sp_modifythreshold) that are too close together.
Thresholds for a database cannot be closer than (size_of_threshold + (2 * @@thresh_hysterisis)). Ensure that the free space allocation allows enough pages. Rerun the command with the appropriate value for free space. Refer to “Managing Free Space with Thresholds” in the Adaptive Server Enterprise System Administration Guide for information about threshold size and hysteresis value.
All versions
0
Adding threshold for segment '%1!' at '%2!' pages.
This message is displayed after the successful completion of a sp_addthreshold command or a sp_modifythreshold command that adds a threshold.
No action is required.
All versions
0
A threshold at %1! pages is logically impossible for segment '%2!'. Choose a value between %3! and %4! pages.
This error occurs when an attempt is made to either add or modify a threshold (sp_addthreshold or sp_modifythreshold) for a number of pages that is greater than the segment named in the command.
Run sp_helpdb database_name to display the device fragments used by the specified database and the size of the device fragment. Then rerun the command with an appropriate page value for free_space.
All versions
0
Only the DBO of database '%1!' or a user with System Administrator (SA) role may add, delete, or modify thresholds in that database.
This error occurs when you try to run sp_addthreshold, sp_dropthreshold, or sp_modifythreshold and you are not the owner of the current database and do not have “sa” role.
If you are not the database owner, run sp_displaylogin to display roles currently assigned to you (you must have sso_role or sa_role to display this information about another user).
Ask your system administrator to give you sa_role or ask another user to execute the command.
All versions
0
Table '%1!' does not exist in database '%2!' -- cannot drop thresholds.
systhresholds should exist in every database in Adaptive Server. Error 17903 occurs when the system table systhresholds does not exist in the current database, and sp_dropthreshold is unable to drop the requested threshold.
Run dbcc checkalloc and dbcc checkdb to determine if there is corruption in the database.
Contact Sybase Technical Support if systhresholds is missing from a database.
Have the following information ready when you call Technical Support:
Output of select @@version
Output of all error messages
Output of dbcc commands
All versions
0
Segment '%1!' does not have a threshold at '%2!' pages.
This error occurs when an attempt is made to either drop or modify a threshold (sp_dropthreshold or sp_modifythreshold) that does not exist for the free space page allocation given in the command.
Run sp_helpthreshold without any options to display all the thresholds and their free page allocations for the current database. Then rerun the stored procedure with corrected parameters.
All versions
0
You may not drop the log's last-chance threshold.
The last-chance threshold is created and maintained by the Adaptive Server and cannot be dropped by a user. Error 17905 occurs when an attempt is made to drop the database last-chance threshold with sp_dropthreshold.
No action is required.
All versions
0
Dropping threshold for segment '%1!' at '%2!' pages.
This message is issued after successful completion of an sp_dropthreshold command or an sp_modifythreshold command that drops a threshold.
No action is required.
All versions
0
Database '%1!' has no thresholds -- table '%2!' does not exist.
systhresholds should exist in every database in Adaptive Server. Error 17910 occurs when the system table systhresholds does not exist in the current database and sp_helpthreshold is unable to output information from that table.
Run dbcc checkalloc and dbcc checkdb to determine if there is database corruption.
Have the following information ready if you call Sybase Technical Support:
Output of select @@version
Output of all error messages
Output of dbcc commands
All versions
0
This procedure can only affect thresholds in the current database. Say 'USE %1!', then run this procedure again.
Thresholds for a specified database may only be created or modified while in the database. Error 18031 occurs when you try to run sp_addthreshold, sp_dropthreshold, or sp_modifythreshold when you are not in the database for which you are running the command.
Determine the name of the current database:
1> select db_name() 2> go
Select the correct database:
1> use database_name 2> go
where database_name is the name of the database for which you want to run the threshold command.
Rerun the sp_addthreshold, sp_dropthreshold, or sp_modifythreshold command.
All versions
0
You may not alter the free space or segment name of the log's last-chance threshold.
The only parameter you can change for the last-chance threshold is the name of the procedure that will execute when the threshold is crossed. Error 18032 occurs when you try to modify the last-chance threshold name or free space allocation with sp_modifythreshold.
No action is required.
All versions
0
You cannot drop user because user '%1!' owns thresholds in database.
The user who created a threshold or last modified a threshold is the threshold owner. A user who owns a threshold cannot be dropped. Error 18033 occurs when you use sp_dropuser to try to drop a user who owns a threshold.
You have three options:
Drop the threshold procedure owned by the user. Then you can drop the user.
Have another user with appropriate privileges modify the threshold. Then you can drop the user.
If you want to inactivate the user Adaptive Server login while leaving the threshold active, use sp_locklogin to prevent use of the login.
All versions
0
Object must be a trigger, view or stored procedure.
The procedure sp_procqmode displays the query processing mode of a stored procedure, view, or trigger. The object name parameter is the name of the stored procedure, view, or trigger whose query processing mode you are examining. Error 18097 occurs when the object name you specify is not a trigger, view, or stored procedure.
Check the name of your object and make sure it is the name of a trigger, view, or stored procedure.
Refer to the Reference Manual for information about sp_procqmode.
All versions
0
Configuration option changed. The SQL Server must be rebooted before the change in effect since the option is static.
When you use sp_configure to modify a static parameter:
The configuration value is updated
The configuration file is updated
The change takes effect when you restart Adaptive Server
Error 18123 is an informational message letting you know that a static parameter has been changed and that the change will not take effect until Adaptive Server is restarted.
Shut down and restart Adaptive Server to make the parameter change take effect.
Refer to the Reference Manual for information about sp_configure.
All versions
0
Less memory moved than requested in cache '%1!'. Requested size = %2! Kb: from pool = %3!, to pool = %4!, actual memory moved = %5! Kb.
The Adaptive Server command sp_poolconfig allows you to create, drop, resize, and get information about memory pools within named data caches. You can use sp_poolconfig to move memory from one pool to another.
Error 18145 is an informational message that is displayed when the source pool you specified has less memory available then you requested to have moved to the destination pool. Adaptive Server moves as much memory as it can of the amount you requested and specifies in the message output how much was actually moved.
If the amount of memory that was moved to the destination pool is not enough:
If necessary, use sp_cacheconfig to enlarge the cache size.
Use sp_poolconfig to reconfigure the source pool to have a larger amount of memory available.
Refer to the Reference Manual for information about sp_poolconfig and sp_cacheconfig.
All versions
0
The command ’%1!’ can not be run in this server. The server is currently configured with mode ’%2!’.
In Adaptive Server’s High Availability (HA) cluster configuration, two nodes in a cluster can take over each other’s workload in the event of a failure; once the problem with the primary is resolved, you can use failback to move the primary companion’s shared disks from the secondary node back to the primary node and start the primary companion on the primary node.
Error 18750 is raised if you try to assign a (primary or secondary) server to a mode that is incompatible with its current state. For example, the error is raised if you issue sp_companion ’prepare_failback’ on the secondary companion, but the secondary is not in the correct state for failback.
Take the following steps:
Check the companion mode of your servers by issuing the following on both primary and secondary servers:
1> select @@cmpstate 2> go
This command returns a value denoting the current companion mode. Refer to “Determining the Companion’s Mode” in Using Sybase Failover in a High-Availability System for a description of the return values.
Check that the command which raised the 18750 message (appearing in the message text) is compatible with the server’s companion mode. For example, you cannot issue a suspend command to a server currently in failover mode.
At times the 18750 message may require corrective action. For example, if you issued prepare_failback and your primary companion is in normal companion mode but the secondary companion is in secondary failover mode, you will need to recover from this inconsistent state manually. The process involves shutting down both servers, restarting the secondary and repairing any suspect databases on the secondary. The steps for achieving this are platform-specific. Refer to one of the following:
Troubleshooting Sybase Failover on HP in Using Sybase Failover in a High-Availability System
Troubleshooting Failover on HACMP for AIX in Using Sybase Failover in a High-Availability System
Troubleshooting Failover on TruCluster for Digital Unix in Using Sybase Failover in a High-Availability System
Troubleshooting Sybase Failover on Windows NT in Using Sybase Failover in a High-Availability System
12.0 and later
