![]() | ![]() |
Home |
|
|
Troubleshooting and Error Messages Guide |
|
| Chapter 3 Error Message Writeups |
|
| alter table Errors |
|
| Error 4964 |
17
Lock scheme conversion failed due to insufficient SQL Server memory. Please retry later when there is less load/users on the SQL server, or ask your System Administrator to reconfigure SQL Server with more memory.
Adaptive Server provides two data locking schemes:
Datapages locking, which locks only the data pages
Datarows locking, which locks only the data rows.
Since neither scheme locks index pages, they are referred to together as the data-only locking scheme.
An additional locking scheme, known as allpages locking, locks the data and index pages affected by queries. It is the default locking scheme.
When you use the alter table command to change a table's locking scheme from allpages locking to data-only locking, Adaptive Server creates memory structures to build a new table with the desired locking scheme and transfers data from the existing table.
Error 4964 indicates that there is not enough memory available in Adaptive Server's data cache to effect the lock scheme change. The problem can occur at various stages of table conversion:
when initializing a new Object Allocation Map (OAM) page
when initializing a new index structure
when building the new table.
Check the activity on your server and re-try the lock scheme conversion when there is less load on the system.
If the problem persists, check the memory allocation on your server. You may need to increase the memory allocated to the data cache.
Use sp_configure to view the current values of memory-related parameters on your system:
1> sp_configure "Memory Use" 2> go
Refer to "Configuring Memory" in the System Administration Guide for details on monitoring and adjusting memory allocation parameters.
All versions
|
|