AIX 5.3 ODM Delete

[ssbaix]

Hello,

I need to delete the below entry from the ODM.

PdAt:
uniquetype = "array/fcp/ibm-dac-V4"
attribute = "model_name"
deflt = "1742 "
values = ""
width = ""
type = "R"
generic = ""
rep = "s"
nls_index = 0

Because I now have two entries for the same uniquetype, see below:

PdAt:
uniquetype = "array/fcp/ibm-dac-V4"
attribute = "model_name"
deflt = "1742 "
values = ""
width = ""
type = "R"
generic = ""
rep = "s"
nls_index = 0

PdAt:
uniquetype = "array/fcp/ibm-dac-V4"
attribute = "model_name"
deflt = "1742 "
values = ""
width = ""
type = "R"
generic = ""
rep = "s"
nls_index = 0

Any help would be appreciated, thanks!

Shane

 

[sjm2]

1) Backup your system

2) odmdelete -o PdAt -q deflt = "1742

 

[ssbaix]

Thanks! I'll give this a try.

Shane

 

[ssbaix]

that did'nt work, see below:

tech3:/home/root (1006)#odmdelete -o PdAt -q deflt = "1742 "
0518-302 usage: odmdelete -o object_class [-q criteria]
Deletes objects from an object class.

Shane

 

[p5wizard]

Shane, you need to quote the -q argument like here below:

(for safety's sake)
[tt]odmget PdAt >/tmp/PdAt.odm[/tt]

(delete one of the records)
[tt]odmdelete -o PdAt -q 'deflt = "1742 "'[/tt]

And use the exact same number of spaces after the 1742 as in the second record (if that is the one you want to get rid of.)

How did that record get in there anyway?



HTH,

p5wizard

 

[ssbaix]

To make a long story short, we have an IBM DS4400 (1742-1RU) SAN system connected to several p5 servers running AIX. We recently upgraded to 5300-11-01-0944, and upon doing so, the AIX servers can no longer see the SAN system correctly. You can see below how the SAN system is supposed to look on the AIX servers (san_chk is a little script I wrote to collect SAN info):

ibm06:/home/root (340)#san_chk
fget_config -Av


lsdev -C | grep dar
dar0 Defined 1742 (700) Disk Array Router


lsdev -C | grep dac
dac0 Defined 30-68-02 1742 (700) Disk Array Controller


lsdev -Cc disk
hdisk0 Available 10-88-00-8,0 Other SCSI Disk Drive
hdisk1 Available 10-88-00-9,0 Other SCSI Disk Drive
hdisk2 Defined 30-68-02 1742 (700) Disk Array Device
hdisk3 Available 30-68-02 Other FC SCSI Disk Drive

And below is how it looks after the upgrade to 5300-11-01-0944:

ibm06:/home/root (340)#san_chk
fget_config -Av


lsdev -C | grep dar
dar0 Defined 1742 (700) Disk Array Router


lsdev -C | grep dac
dac0 Defined 30-68-02 1742 (700) Disk Array Controller


lsdev -Cc disk
hdisk0 Available 10-88-00-8,0 Other SCSI Disk Drive
hdisk1 Available 10-88-00-9,0 Other SCSI Disk Drive
hdisk2 Defined 30-68-02 1742 (700) Disk Array Device
hdisk3 Available 30-68-02 Other FC SCSI Disk Drive

The AIX servers can still communicate with the SAN, however, the I/O is pitifully slow.

So, they asked me to add the below stanza to the PdAt portion of the ODM:

PdAt:
uniquetype = "array/fcp/ibm-dac-V4"
attribute = "model_name"
deflt = "1742 "
values = ""
width = ""
type = "R"
generic = ""
rep = "s"
nls_index = 0

Then, I was asked to replace the same entry with the one below (the only difference are the spaces between the 2 and the “.

PdAt:
uniquetype = "array/fcp/ibm-dac-V4"
attribute = "model_name"
deflt = "1742 "
values = ""
width = ""
type = "R"
generic = ""
rep = "s"
nls_index = 0

After adding the entries, I unount the FS’s from the SAN, varyoff the VG’s, and rmdev all SAN devices. Next, I run cfgmgr and magically, the AIX servers can see the SAN correctly again. However, when I boot, the SAN goes back to the way you see below.

ibm06:/home/root (340)#san_chk
fget_config -Av


lsdev -C | grep dar
dar0 Defined 1742 (700) Disk Array Router


lsdev -C | grep dac
dac0 Defined 30-68-02 1742 (700) Disk Array Controller


lsdev -Cc disk
hdisk0 Available 10-88-00-8,0 Other SCSI Disk Drive
hdisk1 Available 10-88-00-9,0 Other SCSI Disk Drive
hdisk2 Defined 30-68-02 1742 (700) Disk Array Device
hdisk3 Available 30-68-02 Other FC SCSI Disk Drive

For some reason the change doesn’t stick. Nonetheless, IBM is supposed to release an efix any day now to resolve this.

Thanks.

Shane

 

[ssbaix]

IBM released the fix for this issue today:

IZ67192_53TL11SP1.091228.epkg.Z

Thanks,
Shane

 

[p5wizard]

Good luck with that fix, I hope it fixes your problem.

HTH,

p5wizard