Filter
Top Products
ANR4052I Audit command: Invalid lock state encountered for node node name the node will
be unlocked.
Explanation: A database audit process encounters an invalid lock state value for
the node indicated. Because FIX=YES has been specified, the audit function sets the
node’s lock state to unlocked.
System Action: Audit processing continues.
User Response: If you want the lock state for the specified node to be set to a
value other than unlocked, use the LOCK NODE command to change the value
after the audit command has completed.
ANR4053I Audit command: Invalid Node conversion state encountered for node node name.
Explanation: A database audit process encounters an invalid Node conversion
state value for the node indicated.
System Action: Audit processing continues.
User Response: If FIX=YES has not been specified for the audit command, you
may want to run this command again, and specify FIX=YES so that the audit
process can correct the problem. However, next time this node logs onto the server,
the node conversion state will be reset.
ANR4054I Audit command: Invalid Node conversion state encountered for node node name
the node will be set as an ADSM Version 2 node.
Explanation: A database audit process encounters an invalid Node conversion
state value for the node indicated. Because FIX=YES has been specified, the audit
function sets the node as an ADSM version 2 node.
System Action: Audit processing continues.
User Response: The specified node must use the ADSM Version 2 client program
to access the server after the audit completes.
ANR4055I Audit command: Invalid lock state encountered for administrator administrator
name.
Explanation: A database audit process encounters an invalid lock state value for
the administrator indicated.
System Action: Audit processing continues.
User Response: If FIX=YES has not been specified for the audit command, you
may want to run this command again, and specify FIX=YES so that the audit
process can correct the problem.
498
Version 3 Release 7