Can't put system in maintenance mode

[Khatary]

Hi,

when i try to put the system in maintenace mode to be able to restore database i get this

</home/oms> platform_cntrl begin_maintenance

The system cannot be put into maintenance mode unless it is shutdown
first.
</home/oms>

when I shutdown the system can't access user oms with command su - oms which has all configurations

Any help will be appreciated. Thanks in advance

[Sunitha_Mod]

Hello @Khatary, 

Thank you for posting! Could you please let us know which HPE product are you referring to? So we can direct your query to the correct board. 

Looking forward to your response. 

[Khatary]

thanks for your reply, I'm a beginner in this but i think it's hp-ux

[Khatary]

hi @Sunitha_Mod  is that answer enough?

[Patrick Wallek]

So this message, "The system cannot be put into maintenance mode unless it is shutdown first", is likely referring to your OMS system rather than HP-UX.  You likely need to shutdown OMS, however you do that, and then try to put it in maintenance mode.

Since this is an add-on product, you probably need to go to the vendor for support.

[Khatary]

Unfortunatly we don't have vendor support on this because we will migrate to an other one soon but still depend on it.

I understand that i have to shutdown the OMS but it's already down...take a look on the output below

</home/oms> platform_cntrl status
Overall System status..............................[]]
[platform]
ROOT Subsys Control............................[Down]
Apache daemon................................[Down]
LDAP daemon..................................[Down]
Orbix Subsys Control.........................[Down]
Iona Orbix itlocator.......................[Down]
Iona Orbix itnode_daemon...................[Down]
Iona Orbix itnaming........................[Down]
Iona Orbix itevent.........................[Down]
Oracle OMS DB instance.......................[Down]
Oracle CNA DB instance.......................[Down]
Oracle BPM DB instance.......................[Down]
[cna]
CNA Start....................................[Down]
CNA SysMan Main............................[Down]
CNA SysMan M16...........................[Down]
CNA SysMan MADM..........................[Down]
CNA SysMan CMUX..........................[Down]
CNA SysMan AMU...........................[Down]
[bpm]
BPM Subsys Control...........................[Down]
BPM Router.................................[Down]
BPM Reporter...............................[Down]
BPM JVM....................................[Down]
[oms]
OMS Subsys Control...........................[Down]
License Manager............................[Down]
Parameter Server...........................[Down]
Software Backup Utility....................[Down]
FM Subsys Control..........................[Down]
fm_fls...................................[Down]
fm_gfs...................................[Down]
fm_alarms................................[Down]
fm_tcas..................................[Down]
fm_pses..................................[Down]
fm_notif.................................[Down]
fm_gateway...............................[Down]
jvm1.......................................[Down]
jvm2.......................................[Down]
jvm3.......................................[Down]
jvm4.......................................[Down]
jvm5.......................................[Down]
jvm7.......................................[Down]
jvm9.......................................[Down]
Resource Monitor...........................[Down]
</home/oms>

[Duncan Edmonstone]

This very much appears to be a problem with your app (apparently Lucent OMS), so I am not sure how asking about it on a HP-UX forum is going to get you any meaningful help. There's a fairly small bunch of contributors here now anyway, and the chnaces that any of them know OMS well enough to help you debug this is very low indeed.

>> Unfortunatly we don't have vendor support on this because we will migrate to an other one soon but still depend on it.

My instinct is to go find the person that made the decision not to keep support for an app you still used (even if it was heading for retirement) and make it their problem to fix. If that person is you, I guess you screwed up.

Other things you might do? Do you have anyone that knows UNIX shell scripting? It wouldn't surprise me if that "platform_cntrl" command isn't just a shell script. Examining the contents might give you a clue what is going on (it might for example suggest a log file to go look at), but the chances of anyone helping you remoteley debug this via a forum are extremely slim.