2016-11-17 32 views
0

我试图将一个sybase数据库转储到NFS位置,但遇到以下错误下面SYBASE ASE:在带有错误号37(无锁可用)的条带设备上工作时,数据库/归档设备的'lockf'调用失败

1> use master 
2> go 
1> dump database FIP to '/ddbackup/FIP/dump/test3.dmp' 
2> stripe on '/ddbackup/FIP/dump/test3.dmp.S1.dmp' 
3> stripe on '/ddbackup/FIP/dump/test3.dmp.S2.dmp' with compression=100 
4> go 
Backup Server: 4.172.1.4: The value of 'allocated pages threshold' has been set to 40%. 
Backup Server session id is: 29. Use this value when executing the 'sp_volchanged' system stored procedure after fulfilling any volume change request from the Backup Server. 
Backup Server: 4.41.1.1: Creating new disk file /ddbackup/FIP/dump/test3.dmp. 
Backup Server: 4.41.1.1: Creating new disk file /ddbackup/FIP/dump/test3.dmp.S1.dmp. 
Backup Server: 4.41.1.1: Creating new disk file /ddbackup/FIP/dump/test3.dmp.S2.dmp. 
Backup Server: 4.141.2.87: [11] The 'lockf' call failed for database/archive device while working on stripe device '/ddbackup/FIP/dump/test3.dmp' with error number 37 (No locks available). Refer to your operating system documentation for further details. 
Backup Server: 6.53.1.1: OPERATOR: Volume on device '/ddbackup/FIP/dump/test3.dmp' cannot be opened for write access. Mount another volume. 
Backup Server: 6.78.1.1: EXECUTE sp_volchanged 
     @session_id = 29, 
     @devname = '/ddbackup/FIP/dump/test3.dmp', 
     @action = { 'PROCEED' | 'RETRY' | 'ABORT' }, 
     @bs_name = { NULL | 'FIP_BS' } 
Backup Server: 4.141.2.87: [11] The 'lockf' call failed for database/archive device while working on stripe device '/ddbackup/FIP/dump/test3.dmp.S2.dmp' with error number 37 (No locks available). Refer to your operating system documentation for further details. 
Backup Server: 6.53.1.1: OPERATOR: Volume on device '/ddbackup/FIP/dump/test3.dmp.S2.dmp' cannot be opened for write access. Mount another volume. 
Backup Server: 6.78.1.1: EXECUTE sp_volchanged 
     @session_id = 29, 
     @devname = '/ddbackup/FIP/dump/test3.dmp.S2.dmp', 
     @action = { 'PROCEED' | 'RETRY' | 'ABORT' }, 
     @bs_name = { NULL | 'FIP_BS' } 
Backup Server: 4.141.2.87: [11] The 'lockf' call failed for database/archive device while working on stripe device '/ddbackup/FIP/dump/test3.dmp.S1.dmp' with error number 37 (No locks available). Refer to your operating system documentation for further details. 
Backup Server: 6.53.1.1: OPERATOR: Volume on device '/ddbackup/FIP/dump/test3.dmp.S1.dmp' cannot be opened for write access. Mount another volume. 
Backup Server: 6.78.1.1: EXECUTE sp_volchanged 
     @session_id = 29, 
     @devname = '/ddbackup/FIP/dump/test3.dmp.S1.dmp', 
     @action = { 'PROCEED' | 'RETRY' | 'ABORT' }, 
     @bs_name = { NULL | 'FIP_BS' } 

事情我试图解决这个问题:

  • 试过数据库转储没有条纹的上
  • 重新启动nfslock服务
  • 转储数据库到不同的FS - 工作。所以我想我只有 问题与NFS
  • 重启BS

感谢您对这个帮助。谢谢

+0

Stackoverflow旨在成为一种编程资源。这个问题是更多的服务器/基础设施相关[Serverfault](http://serverfault.com)是这个问题的更好的位置。此外,请检查这个问题的答案,看看他们是否可能引导你在正确的方向:http://serverfault.com/questions/61594/what-does-no-locks-available-mean –

回答

0

只是想分享,这是通过在nfs(按我们的系统管理员)使用挂载选项解决。

相关问题