Anonymous_User Absent Member.
Absent Member.
888 views

NDPSM unable to see database volume

The server in question is running NW6.5 sp4, upgraded from NW6.0. The
server has a pair of mirrored hard disks. Under NW6.0 the volumes were set
up using the Traditional File System. As part of the process to upgrading
to NW6.5 I wanted to move to NSS and I needed to increase the size of the
DOS partition and the SYS volume. To accomplish this I broke the mirror,
repartitioned the second drive, used VCU to move the volumes from TFS to the
new NSS partitions, let VCU rename the volumes, then made the second drive
the primary drive. Once this process was done I had the new Sys, Data, and
Apps volumes along with the Sys_old, Data_old and Apps_old volumes on the
TFS drive. I decided to leave the *_old volumes in place for a couple weeks
"just in case". I then proceeded with the NW6.5 upgrade. NDPS Manager
continued to function just fine after the upgrade. But, last night I
deleted the *_Old volumes, repartitioned that disk, and set up mirroring of
the NSS partitions. When the server restarted the NDPS Manager screen was
telling me that it could not see the Data volume where the NDPS database is
stored. It gave me the option of trying to move the database, but the only
volume available in the list was ZEN (a volume I created after the TFS to
NSS conversion). In iManager I deleted the NDPS manager and recreated it,
once again specifying the Data volume as the volume to store the database.
When I started NDPSM on the server I once again received the error stating
that the Data volume could not be found on the server. The only way I could
get the NDPS manager working was to specify the new ZEN volume as the
database volume when I set up the NDPS Manager using iManager.

I don't understand why NDPSM worked until I deleted the *_Old volumes.

What do I need to do to allow NDPSM to see the current DATA volume?

Will this problem manifest itself in other ways as well?

Thanks for your help,

Brad Johnson


0 Likes
4 Replies
Anonymous_User Absent Member.
Absent Member.

Re: NDPSM unable to see database volume

Brad Johnson,

> I don't understand why NDPSM worked until I deleted the *_Old volumes.


All I can think of is, because the NDPS Manager object in DS referenced
the old data volume object. In DS all objects have a GUID, references
between objects uses these GUIDs. So even if you rename or move an object
the reference is still intact. So when you created the NSS volumes, they
got of course new GUIDs. Once you deleted the old volumes the old volume
objects lost their physical host volume and thus became invalid.

> What do I need to do to allow NDPSM to see the current DATA volume?


Make sure the volume objects in DS are valid and pointing to the new NSS
volumes. You might need to recreate them. But bare in mind that deleting
the volume objects will cause any object referencing them loose their
references. Objects like print queues, directory maps and the Home
directory path attribute of users comes to mind.


--
___________________________________________
Niclas Ekstedt, CNA/CNE/CNS/CLS
Network Consultant/NSC Sysop
InfraSystems Solutions

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: NDPSM unable to see database volume

How do I confirm that the DS objects are valid and point to the new NSS
volumes. Everything I look at in ConsoleOne or iManger looks just fine.
All the trustee assignments and print queues moved over with the VCU
procedure just fine. When I deleted the old NDPS Manager, because I
couldn't get it to work, the deletion process also deleted the *.psm file
which was located on the current (NSS) Data volume. This says to me that
everything looked normal from iManager's perspective. I am trying to avoid
removing and recreating the volume objects. If I did, would I have to
reassign file system rights for users and groups as well?

Another thing I forgot to note originally: I performed the same upgrade
procedure on an identical server and everything has worked, including NDPS.
I am not sure why this server is reacting differently.

Thanks,

Brad Johnson



"Niclas Ekstedt" <niclas.ekstedt@nospam.infrasystems.se> wrote in message
news:pan.2006.01.06.14.53.44.618262@nospam.infrasystems.se...
> Brad Johnson,
>
>> I don't understand why NDPSM worked until I deleted the *_Old volumes.

>
> All I can think of is, because the NDPS Manager object in DS referenced
> the old data volume object. In DS all objects have a GUID, references
> between objects uses these GUIDs. So even if you rename or move an object
> the reference is still intact. So when you created the NSS volumes, they
> got of course new GUIDs. Once you deleted the old volumes the old volume
> objects lost their physical host volume and thus became invalid.
>
>> What do I need to do to allow NDPSM to see the current DATA volume?

>
> Make sure the volume objects in DS are valid and pointing to the new NSS
> volumes. You might need to recreate them. But bare in mind that deleting
> the volume objects will cause any object referencing them loose their
> references. Objects like print queues, directory maps and the Home
> directory path attribute of users comes to mind.
>
>
> --
> ___________________________________________
> Niclas Ekstedt, CNA/CNE/CNS/CLS
> Network Consultant/NSC Sysop
> InfraSystems Solutions
>



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: NDPSM unable to see database volume

Brad Johnson,

> How do I confirm that the DS objects are valid and point to the new NSS
> volumes.


In Console One, try browsing the volumes. By double clicking the volume
object you should see the contents of the volume. If that displays fine,
then they're valid.

> Everything I look at in ConsoleOne or iManger looks just fine.
> All the trustee assignments and print queues moved over with the VCU
> procedure just fine. When I deleted the old NDPS Manager, because I
> couldn't get it to work, the deletion process also deleted the *.psm
> file which was located on the current (NSS) Data volume. This says to
> me that everything looked normal from iManager's perspective.


Yes, I would expect the VCU to handle the reference part OK. Looks like it
has for some objects but not NDPS. Perhaps something just corrupted when
doing the NDPS objects.

> I am trying to avoid removing and recreating the

volume objects. If I
> did, would I have to reassign file system rights for users and groups as
> well?


No trustees are part of the file system and will remain intact even if the
volume object is recreated.

> Another thing I forgot to note originally: I

performed the same upgrade
> procedure on an identical server and everything has worked, including
> NDPS. I am not sure why this server is reacting differently.


As I said. The VCU should have handled the references OK. Looks like it
just had some problems on this one server. Why, I honestly don't know 😞


--
___________________________________________
Niclas Ekstedt, CNA/CNE/CNS/CLS
Network Consultant/NSC Sysop
InfraSystems Solutions

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: NDPSM unable to see database volume

Well, I finally got everything working again. I ran an unattended full
repair within DSRepair. After doing the repair I was able to create the
NDPS Manager once again using the Data volume as the database volume. I
started NDPSM without error. So, my problem seems to be solved.

Thank you for all your help,

Brad Johnson



"Niclas Ekstedt" <niclas.ekstedt@nospam.infrasystems.se> wrote in message
news:pan.2006.01.07.05.25.09.710278@nospam.infrasystems.se...
> Brad Johnson,
>
>> How do I confirm that the DS objects are valid and point to the new NSS
>> volumes.

>
> In Console One, try browsing the volumes. By double clicking the volume
> object you should see the contents of the volume. If that displays fine,
> then they're valid.
>
>> Everything I look at in ConsoleOne or iManger looks just fine.
>> All the trustee assignments and print queues moved over with the VCU
>> procedure just fine. When I deleted the old NDPS Manager, because I
>> couldn't get it to work, the deletion process also deleted the *.psm
>> file which was located on the current (NSS) Data volume. This says to
>> me that everything looked normal from iManager's perspective.

>
> Yes, I would expect the VCU to handle the reference part OK. Looks like it
> has for some objects but not NDPS. Perhaps something just corrupted when
> doing the NDPS objects.
>
>> I am trying to avoid removing and recreating the

> volume objects. If I
>> did, would I have to reassign file system rights for users and groups as
>> well?

>
> No trustees are part of the file system and will remain intact even if the
> volume object is recreated.
>
>> Another thing I forgot to note originally: I

> performed the same upgrade
>> procedure on an identical server and everything has worked, including
>> NDPS. I am not sure why this server is reacting differently.

>
> As I said. The VCU should have handled the references OK. Looks like it
> just had some problems on this one server. Why, I honestly don't know 😞
>
>
> --
> ___________________________________________
> Niclas Ekstedt, CNA/CNE/CNS/CLS
> Network Consultant/NSC Sysop
> InfraSystems Solutions
>



0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.