Troubleshooting
Problem
When running the 'query archive' command this does not display all of the archived objects that have been stored for a given node/filespace.
Symptom
Although the 'query archive' command does not show the archived objects, a SELECT statement issued against the archives table displays all of the archived objects as expected.
Cause
This behavior is most likely caused by one of the following conditions:
a) the node/owner issuing the query does not have sufficient authorization to access all of the archived data
b) the archived data is pending deletion on the Tivoli Storage Manager Server
Diagnosing The Problem
The owner of the archived objects can be identified by issuing the following SELECT statement against the Tivoli Storage Manager Server:
select * from archives where node_name='<NODENAME>' and filespace_name='<filespace>'
For example, to display all of the archived objects associated with the ARCHIVENODE node and /tmp filespace, the following SELECT statement would be issued:
tsm: V6_SERVER>select * from archives where node_name='ARCHIVENODE' and filespace_name='/tmp'
NODE_NAME: ARCHIVENODE
FILESPACE_NAME: /tmp
FILESPACE_ID: 20
TYPE: FILE
HL_NAME: /archive/
LL_NAME: file2
OBJECT_ID: 95864140
ARCHIVE_DATE: 2013-05-17 14:57:23.000000
OWNER: guest
DESCRIPTION: Archive Date: 05/17/13
CLASS_NAME: DEFAULT
The results from this query will display the owner for each of the archived objects. In the output above we can see that the /tmp/archive/file2 object is owned by the guest user. Ensure that the user initiating the query/retrieval of these archived objects has sufficient authorization to access the objects.
As for determining whether any of the archived objects are pending deletion, the SHOW ARCHIVES command can be issued to make this determination. This command will display the current status of all archived objects associated with a given node/filespace. The syntax for this command is as follows:
show archives <node> <filespace>
The SHOW ARCHIVES command will display results similar to the following:
tsm: V6_SERVER>show archives archivenode /tmp
- fsName: /tmp, objName: /archive
hlID: 58BBFD37B332C6A169B073CE2D341C2FC324D112
llID: EBFB55F4432B592119A10592E4F26272CC72359E
objType: DIR, objId: 95864138, size: 0, mcName: DEFAULT
hasDir: yes, owner: root, desc: Archive Date: 05/17/13
Inserted 05/17/13 14:57:23 (UTC 05/17/13 21:57:23), retention initiated 05/17/13 14:57:23
fsName: /tmp, objName: /archive/file1
hlID: A5A19EF237DC840D53F7F615294558D04233C2C0
llID: 60B27F004E454ACA81B0480209CCE5081EC52390
objType: FILE, objId: 95864139, size: 1024, mcName: DEFAULT
hasDir: yes, owner: root, desc: Archive Date: 05/17/13
Inserted 05/17/13 14:57:23 (UTC 05/17/13 21:57:23), retention initiated ** EXPIRE IMMEDIATELY **
fsName: /tmp, objName: /archive/file2
hlID: A5A19EF237DC840D53F7F615294558D04233C2C0
llID: CB99B709A1978BD205AB9DFD4C5AAA1FC91C7523
objType: FILE, objId: 95864140, size: 1024, mcName: DEFAULT
hasDir: yes, owner: guest, desc: Archive Date: 05/17/13
Inserted 05/17/13 14:57:23 (UTC 05/17/13 21:57:23), retention initiated 05/17/13 14:57:23
Resolving The Problem
In each of the examples above we can see that the /tmp/archive/file1 object is currently pending deletion, meaning that a request to delete the object has been received from the client and the object will be deleted from the Tivoli Storage Manager server the next time the expiration process examines this node/filespace.
Archive objects that are pending deletion cannot be queried and/or retrieved by the client.
Product Synonym
TSM
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21638025