topic Re: problems with SYSMAN in Operating System - OpenVMS

problems with SYSMAN

SAMI AHMAD — Thu, 11 Jun 2009 18:21:12 GMT

I am trying to execute a remote command on a node but its not accepting the password, though
I know the username/password is correct since I can login into THS1 using that username password.
what is going on here? some nodes I have no problem executing the command and some wont let me in.

thanks

SYSMAN> set env/node=THS1
Remote Password:
%SYSMAN-I-ENV, current command environment:
Individual nodes: THS1
At least one node is not in local cluster
Username ORACLE will be used on nonlocal nodes

SYSMAN> do show network
%SYSMAN-I-OUTPUT, command execution on node THS1
%SYSMAN-I-NODERR, error returned from node THS1
-SYSTEM-F-INVLOGIN, login information invalid at remote node

Re: problems with SYSMAN

Robert Gezelter — Thu, 11 Jun 2009 18:37:21 GMT

Sami,

A number of things can prevent an account from being used for SYSMAN.

It would be helpful if a SHOW/FULL ORACLE from within AUTHORIZE was done, and the results posted.

As an example, what are the privileges of ORACLE (note, the default privileges), is the account locked for some reason>

- Bob Gezelter, http://www.rlgsc.com

Re: problems with SYSMAN

SAMI AHMAD — Thu, 11 Jun 2009 18:42:43 GMT

no the account is not locked since I can login interactively.
here is the account/full for account oracle.

Username: ORACLE Owner: Sami Ahmad
Account: UIC: [277,102] ([ORACLE])
CLI: DCL Tables: DCLTABLES
Default: DISK$ORACLE:[ORACLE9I]
LGICMD:
Flags:
Primary days: Mon Tue Wed Thu Fri
Secondary days: Sat Sun
No access restrictions
Expiration: (none) Pwdminimum: 10 Login Fails: 0
Pwdlifetime: 30 00:00 Pwdchange: 11-JUN-2009 14:56
Last Login: 11-JUN-2009 09:25 (interactive), 11-JUN-2009 14:07 (non-interactive)
Maxjobs: 0 Fillm: 2048 Bytlm: 500000
Maxacctjobs: 0 Shrfillm: 0 Pbytlm: 0
Maxdetach: 0 BIOlm: 1000 JTquota: 16384
Prclm: 100 DIOlm: 1000 WSdef: 8192
Prio: 4 ASTlm: 1000 WSquo: 16384
Queprio: 4 TQElm: 1000 WSextent: 16384
CPU: (none) Enqlm: 10000 Pgflquo: 1500000
Authorized Privileges:
CMKRNL GROUP GRPNAM IMPERSONATE LOG_IO NETMBX
OPER PFNMAP PRMGBL PRMMBX SHARE SYSGBL
SYSLCK SYSNAM SYSPRV TMPMBX WORLD
Default Privileges:
CMKRNL GROUP GRPNAM IMPERSONATE LOG_IO NETMBX
OPER PFNMAP PRMGBL PRMMBX SHARE SYSGBL
SYSLCK SYSNAM SYSPRV TMPMBX WORLD
Identifier Value Attributes
ORA_DBA %X80010002
ORA_AGENT_ID %X80010004

Re: problems with SYSMAN

Robert Gezelter — Thu, 11 Jun 2009 19:15:46 GMT

Sami,

Are there any OPCOM messages on the remote system relating to the connection attempt?

- Bob Gezelter, http://www.rlgsc.com

Re: problems with SYSMAN

Robert Gezelter — Thu, 11 Jun 2009 19:19:02 GMT

Sami,

Also, what versions of OpenVMS are involved (both systems)?

- Bob Gezelter, http://www.rlgsc.com

Re: problems with SYSMAN

SAMI AHMAD — Thu, 11 Jun 2009 19:20:47 GMT

I dont see any, I do see batch jobs starting and completing so OPCOM msgs are coming to my screen but not related to the connection attempt.

Re: problems with SYSMAN

SAMI AHMAD — Thu, 11 Jun 2009 19:21:25 GMT

7.3-2 on both

Re: problems with SYSMAN

SAMI AHMAD — Thu, 11 Jun 2009 20:00:00 GMT

no i was wrong , I had not enabled OPCOM msgs so I was not seeing them . The remote node is indeed throwing an opcom msg when the connection is initiated as follows, but what does it tell us? :

Message from user SYSTEM on THS1
Event: Access Control Violation from: Node LOCAL:.THS1 Session Control,
at: 2009-06-11-16:58:30.182-04:00Iinf
NSAP Address=/0A64108D,
Source=UIC = [0,0]ORACLE,
Destination=name = SMISERVER,
Destination User="",
Destination Account="",
Node Name=
eventUid 16ED73CB-56A9-11DE-82B4-0008029125CA
entityUid DFFBF425-4619-11DE-8460-AA0004008304
streamUid E4F22F18-4619-11DE-8655-AA0004008304

Re: problems with SYSMAN

Hoff — Thu, 11 Jun 2009 20:17:16 GMT

http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1287033

And if that thread doesn't allow you to sort out the trigger, read Volker's answer from the end of the thread, and post up that information.

Re: problems with SYSMAN

Andy Bustamante — Fri, 12 Jun 2009 15:20:43 GMT

On the node that's failing, check to see that SMISERVER is running. This is started automatically on clustered nodes, but on stand alone nodes must be manually added to systartup_vms.com.

Andy Bustamante