Highlighted
robles Absent Member.
Absent Member.
1294 views

nss /notransaction=volume

I posted this in the install/upg and the cluster forum, but no solution. If anyone here has a clue I appreciate a response ASAP.

I was in the process of upgrading a 60sp5 cluster node that loads iprint volume that has nss transaction enabled -
Per wiki, TID 3463889 says to disable transaction and delete uxaction.log before activating again. I couldn't get to the log to delete it when the volume was deactivated and when activated it's in use and can't delete it.
Also, before the upgrade, I tried changing the load cluster script to NSS /NOTRANSACTION=PRINT, unloaded and reloaded it , but when loaded again, i did nss /volumes and PRINT displayed with "user transaction" (even with notransaction in the load script) and I still couldn't delete the log....

So i had to take the iprint resource offline to continue the scheduled server upg.
Any clue how i can delete this log so i can load the resource, now that both cluster nodes have been upgraded to 65sp6?? Per TID, server might abend or print may not load properly if log is not deleted.

Please advise, I'm wating for your response.
Thanx many.
Haydee
0 Likes
3 Replies
nekstedt1 Absent Member.
Absent Member.

Re: nss /notransaction=volume

robles,

Make sure there's nothing else besides iPrint that uses the uxaction.log
Have a look at TID 3258645, you might need to backrev to SP5 to be able
to delete the log.


--
_________________________________________
Niclas Ekstedt, CNA/CNE/CNS/CLS
Systems Engineer/NSC Sysop
Telindus Sweden AB

Niclas Ekstedt Sr Consultant Atea Sverige AB
0 Likes
robles Absent Member.
Absent Member.

Re: nss /notransaction=volume

TID 3258645 says "(.. NDPS does use TTS to track its print jobs. After unloading NDPS, the uxaction log could then be deleted).
*This must not work for cluster volumes, because after i unloaded NDPS, i could not get to the uxaction.log to delete it, and when it was loaded i couldn't delete it because it said it was in use..
*And, When I did nss /volumes this was the only volume using TTS. So in order to continue with the upgrade, only thing to do was to take it offline instead of migrating it to the node that was already upgraded to 65sp6.

However, After carefully reading this TID 3463889 I realize it says:
"(a change made to the transaction record structure from a version previous to the NSS5a)"...
*Before upgrading from NW60sp5 to NW65sp6 I installed the "NW6NSS5c" patch on the NW60sp5 server and did a pool rebuild on all the volumes including the "NDPS print volume" and sys volume.

Do you think this would have fix the problem? And now that servers are 65sp6, it might be save to join the server to the cluster and load the NDPS print resource volume with no abends?

*There is no way i can backrev to 65sp5 because i did the upg using the overlay 65sp6 CD.

Please advise.
thanx again
haydee
0 Likes
nekstedt1 Absent Member.
Absent Member.

Re: nss /notransaction=volume

robles,

> TID 3258645 says "(.. NDPS does use TTS to track its print jobs. After
> unloading NDPS, the uxaction log could then be deleted). *This must not
> work for cluster volumes, because after i unloaded NDPS, i could not get
> to the uxaction.log to delete it, and when it was loaded i couldn't
> delete it because it said it was in use..


So at this point only the volume were mounted, iPrint NDPS/iPrint wasn't
loaded?

> However, After carefully reading this TID 3463889 I realize it says: "(a
> change made to the transaction record structure from a version previous
> to the NSS5a)"...
> *Before upgrading from NW60sp5 to NW65sp6 I installed the "NW6NSS5c"
> patch on the NW60sp5 server and did a pool rebuild on all the volumes
> including the "NDPS print volume" and sys volume.


OK

> Do you think this would have fix the problem? And now that servers are
> 65sp6, it might be save to join the server to the cluster and load the
> NDPS print resource volume with no abends?


Hopefully, but there's only one way of finding out, and that's to try the
hard way 😞 Should it still be a problem I recommend opening up a case
with Novell.

> *There is no way i can backrev to 65sp5 because i did the upg using the
> overlay 65sp6 CD.


OK, I see.


--
_________________________________________
Niclas Ekstedt, CNA/CNE/CNS/CLS
Systems Engineer/NSC Sysop
Telindus Sweden AB

Niclas Ekstedt Sr Consultant Atea Sverige AB
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.