Has anyone had Universe just hang at the uv command?   We are on an old version 11.1.3 under Solaris 10.  Thought it might be suspend files not getting set back but no.  No errors, could not find anything in the $uvhome logs.  A server reboot bought the system back without any file damage.   Trying to think of other places to look for root cause without any errors to review.  No known changes to system or environment.

Rebecca,

It is hard to say what was the root cause, after a reboot.  If it happens again the following may help:

Does it hang in every UniVerse Account, or just one specific account?

( If you cd to XDEMO or HS.SALES, does the uv command work?  )

If other accounts work, the problem can be with what is executed when you login.  ( ie. the LOGIN paragraph )
Note that is could be as simple as everyone waiting on a lock, when entering that account.

---

Also, if this is happening for all users, on all accounts:
have you suspended the database updates?

I understand the need to reboot if/when there are users who can not login, yet if you can contact your Rocket U2 Support Provider, when this occurs, they should be able to help determine root cause.  ( if that is not possible due to time constraints, get a uvdiag before rebooting, and  contact your Rocket U2 Support Provider earliest opportunity. )

---

Has anyone had Universe just hang at the uv command?   We are on an old version 11.1.3 under Solaris 10.  Thought it might be suspend files not getting set back but no.  No errors, could not find anything in the $uvhome logs.  A server reboot bought the system back without any file damage.   Trying to think of other places to look for root cause without any errors to review.  No known changes to system or environment.

Too many record locks from a basic program is one way to cause a problem. The Basic RELEASE command is a life saver. You could run a phantom process that executes LIST.READU EVERY, PORT.STATUS, and ANALYZE.SHM in a loop that pauses with the sleep command. The phantom output  is saved to a record in the &PH& file.

---

Has anyone had Universe just hang at the uv command?   We are on an old version 11.1.3 under Solaris 10.  Thought it might be suspend files not getting set back but no.  No errors, could not find anything in the $uvhome logs.  A server reboot bought the system back without any file damage.   Trying to think of other places to look for root cause without any errors to review.  No known changes to system or environment.

hi

at os shell,  cd uvhome
1/
I suggest to use 'port.status PID xxx LAYER.STACK' then you read the activity of the session.
if port.status is not recognized, you copy list_readu to port.status and it works.

2/
I suggest smat -a to check the smaphore locks/io locks, ... 

3/ read the uvhome/errlog to check last errors ? 

---