SYBASE ASE: Der Aufruf 'lockf' für Datenbank/Archivierungsgerät ist während der Arbeit an Stripe-Gerät mit Fehlernummer 37 fehlgeschlagen (keine Sperren verfügbar)

Question

Ich versuche, einen Sybase-Datenbankabbild an einen NFS-Speicherort auszuführen, aber den folgenden Fehler auftritt unter

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' } 

Dinge habe ich versucht, das Problem zu beheben:

• ohne Streifen zu Datenbank-Dump versucht auf
• Starten Sie den nfslock Service
• Dump Datenbank zu einem anderen FS - WORKING. Also ich denke, ich habe nur Probleme mit dem NFS
• Restart BS

Schätzen Sie Ihre Hilfe zu diesem Thema. Danke

Answer 1

Ich wollte nur teilen, dass dies gelöst wurde, indem Sie eine Mount-Option in der NFS (nach unserem System) verwenden.