Getting following error from NIM server: 0042-302 m_bos_inst:
I'm using SMIT to restore a system from a recent mksysb image, but I'm getting the following error:
0042-001 nim: processing error encountered on "master":
0042-302 m_bos_inst: the state of "shprgn" prevents this operation
from succeeding. Use the "reset" operation to correct
its state then retry the intended operation.
What is this reset operation to which it refers? Is that performed on the client or the server?
0042-001 nim: processing error encountered on "master":
0042-302 m_bos_inst: the state of "shprgn" prevents this operation
from succeeding. Use the "reset" operation to correct
its state then retry the intended operation.
What is this reset operation to which it refers? Is that performed on the client or the server?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Just so I get this straight, when NIM refers to resources, it's referring to things like spot files and source depots, right?
Right, and mksysb resources, scripts, exclude files etc.
ASKER
OMG! I'll get back to you.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Whew, that was scary! This is the message I got from the reset:
warning: 0042-001 m_deallocate: processing error encountered on "master":
0042-175 c_ch_nfsexp: An unexpected result was returned by the
"/usr/sbin/exportfs" command:
exportfs: /export/nim/mksysb/shprgn_
I thought I had lost my backup image! I don't what this message is trying to tell me, but /export/nim/mksysb/shprgn_
warning: 0042-001 m_deallocate: processing error encountered on "master":
0042-175 c_ch_nfsexp: An unexpected result was returned by the
"/usr/sbin/exportfs" command:
exportfs: /export/nim/mksysb/shprgn_
I thought I had lost my backup image! I don't what this message is trying to tell me, but /export/nim/mksysb/shprgn_
I assume NIM tried to "unexport" the file. (Yes, mksysb images are exported to clients as files).
Did you specify "Force"? It often helps yet doesn't do any harm.
I hope you didn't try to export anything by yourself! Let NIM do all the NFS work!
You can check if there's any machine still holding a resource allocation:
#!/bin/ksh
for m in $(lsnim | grep standalone |awk '{print $1}'); do
A=$(lsnim -c resources $m); [[ ! -z $A ]] && printf "%16s %16s\n" $m "$A"; done
No output - no allocated resources.
Did you specify "Force"? It often helps yet doesn't do any harm.
I hope you didn't try to export anything by yourself! Let NIM do all the NFS work!
You can check if there's any machine still holding a resource allocation:
#!/bin/ksh
for m in $(lsnim | grep standalone |awk '{print $1}'); do
A=$(lsnim -c resources $m); [[ ! -z $A ]] && printf "%16s %16s\n" $m "$A"; done
No output - no allocated resources.
Sad to say, but my day is over now.
CU tomorrow, Good night!
wmp
CU tomorrow, Good night!
wmp
ASKER
I know this will sound dumb, but do I shut the system down from the HMC prior to starting the restore? I guess my real question is, in what state should the system be when I initiate the restore?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER