Originally posted by: IBMFORUMS

Hi everybody

We have a NIM problem where we can’t create any resources (mksysb, spot, lppsource … etc) or install any fileset.
The error here:

0042-001 nim: processing error encountered on "master":
0042-053 m_mkbosi: there is no NIM object named "MKSYSB_MP006A_20Sep08"

The problem is that the mksysb resource “MKSYSB_MP006A_20Sep08” is deleted by mistake while the process is running. the profile of the master still have entry for this resource :

% lsnim -l master
master:
class = machines
type = master
max_nimesis_threads = 20
if_defined = chrp.mp.ent
comments = machine which controls the NIM environment
client_reg = no
platform = chrp
netboot_kernel = mp
if1 = net_49 mp003c_mgt 000D600B200A
cable_type1 = tp
Cstate = ready for a NIM operation
prev_state = ready for a NIM operation
Mstate = currently running
serves = LPP_AIX52ML4
serves = LPP_AIX52ML7
serves = LPP_AIX52TL10
serves = LPP_AIX53TL6
serves = LPP_AIX53TL7
serves = MKSYSB_MP002B_15Sep08
serves = MKSYSB_MP002C_15Sep08
serves = MKSYSB_MP003A_20Sep08
serves = MKSYSB_MP003B_15Sep08
serves = MKSYSB_MP003D_20Sep08
serves = MKSYSB_MP004B_20Sep08
serves = MKSYSB_MP005B_15Sep08
serves = MKSYSB_MP005C_16Sep08
serves = MKSYSB_MP005D_15Sep08
serves = MKSYSB_MP006A_20Sep08
serves = MKSYSB_MP006B_16Sep08
serves = MKSYSB_MP006C_17Sep08
serves = MKSYSB_MP006D_17Sep08
serves = MKSYSB_MP007B1_20Sep08
serves = MKSYSB_MP007E1_15Sep08
serves = MKSYSB_MP007F1_17Sep08
serves = MKSYSB_MP007H1_15Sep08
serves = MKSYSB_MP008A_15Sep08
serves = MKSYSB_MP008B_15Sep08
serves = MKSYSB_MP008D_15Sep08
serves = MKSYSB_MP009D_17Sep08
serves = MKSYSB_MP010A_20Sep08
serves = MKSYSB_MP010C_17Sep08
serves = MKSYSB_MP010D_17Sep08
serves = MKSYSB_MP010E_17Sep08
serves = MKSYSB_MP010F_20Sep08
serves = PKGS_SDD17
serves = PKGS_SSH52
serves = PKGS_SSH53
serves = SPOT_AIX52ML4
serves = SPOT_AIX52ML7
serves = SPOT_AIX52TL10
serves = SPOT_AIX53TL6
serves = SPOT_AIX53TL7
serves = boot
serves = nim_script
master_port = 1058
registration_port = 1059
Cstate_result = reset
reserved = yes
#AIX-Forum

Originally posted by: unixgrl

Have you removed the resource from NIM?
Try nim -o remove resourcename.

Also, do a "lsnim -l" and find out if any other resource such as a machine has this one allocated to it. If so, deallocate the resource or possibly remove the machine definition. If you can't clean this up nicely using the nim commands, you may need to do some odmdeletes.
#AIX-Forum

Originally posted by: cggibbo

You take regular backups of your NIM database, right? ;-)

Why don't you restore a previous copy of the database?
#AIX-Forum

Originally posted by: IBMFORUMS

No :)
#AIX-Forum

Originally posted by: CRM

There is an additional force (-F) flag that can be used which may help here. As per all force commands, make sure you take a backup first, be careful with the command etc etc.

regards

Chris
#AIX-Forum

Originally posted by: id=me

Hi Guys, did anyone solve this one? I have the same issue and have tried a heap of things to fix it. The resource does not exist, I can't remove it from the system even with the -F as it doesnt exist. My last resort will be to attempt to find and remove it from the nimdb/odm if it exits in there.
Please help :)
#AIX-Forum

Originally posted by: Kosala

I fixed something similar some time back through the ODM. There are bunch of tools, which used by NIM to manage the ODM. For example m_chattr, which is very handy when installations are really screwed up and you cannot release the lpp_resource from the client. Yet there is no option to remove a attabute... like m_rmattr. So it's highly unlikely that you can revert this using NIM commands. The only option is to remove it from the ODM. Don't remember the exact class but IIRC, it's something like nim_attr.

Kosala
#AIX-Forum

Originally posted by: id=me

Thanks Kosala, I did end up using odmdelete to fix the issue; Just for future reference to anyone who gets this problem, below are a list of instructions that I used to solve this problem.

tar -cvf /tmp/nim.tar /etc/objrepos/nim*

odmget nim_attr | grep -p <resource identified in the error>

OUTPUT SOMETHING LIKE BELOW
id = 0123456789
value = "resource identified in the error"
seqno = 0
pdattr = "96"

odmdelete -o nim_attr -q value=<resource identified in the error>

Hope this helps :)
#AIX-Forum

Originally posted by: IBMFORUMS

The resource is already removed.

I tried nim -o remove, didn't help.
I tried also to create the resource again, but fail with same error
#AIX-Forum