Unable to add the user ORACLE10G onto VMS V8.1-2

[Srikanth Arunachalam]

Hi,

While I do the following, am getting the error. Please help.
$authorize
UAF> ADD /ACCOUNT=ORACLE10G /PASSWORD=ORACLE/UIC=[277,100]/DEVICE=device/DIRECTO
RY=[ORACLE10G]/OWNER="ORACLE DBA"
_new username: ORACLE10G

%UAF-W-INVSTR, string too long for field \ORACLE10G\

Thanks,
Srikanth

[Wim Van den Wyngaert · Accepted solution]

The length of the account field is limited to 8 char. So, use ora10g or something like that.

Wim

[Ian Miller.]

I think ORACLE10G is too long for the ACCOUNT field. Try ORACLE

[Hein van den Heuvel]

Hmmm,

Thanks for posting the exact command and error message. Great!

Having said that, Please help me understand how that error message could have been any more explicit and clear?

"%UAF-W-INVSTR, string too long for field \ORACLE10G\"

Regards,
Hein.

[Steven Schweda]

> [...] more explicit and clear?

"%UAF-W-INVSTR, string too long (len>8) for
field \ORACLE10G\"

Or "(max len = 8)", or similar.

But I wouldn't call the existing message bad.

[Ian Miller.]

the error message could have said which field. The value ORACLE10G was used in more than one field.

[Srikanth Arunachalam]

Thanks everybody, Although I managed to add user using authorize. When I am trying to login it doesnt allow me to do so. This is a new system for us. Please let me know if I am missing anything in the step.

ADD /ACCOUNT=ORA10G /PASSWORD=ORACLE/UIC=[277,100] /DEVICE=DSA0/DIRECTORY=[ORA10G]/OWNER="ORACLE DBA"

MODIFY ORA10G/ENQLM=150

ADD/IDENTIFIER ORA_OMC_DBA

GRANT/IDENTIFIER ORA_OMC_DBA ORA10g

ADD/IDENTIFIER/ATTRIBUTES=SUBSYSTEM ORA_SGA

$ SET H 0

Welcome to HP OpenVMS Industry Standard 64 Operating System, Version V8.2-1

Username: ORA10G
Password:
User authorization failure

Thanks,
Srikanth

[Ian Miller.]

try clearing the disuser flag. In authorize
MOD ORACLE10G/FLAGS=NODISUSER

[Jan van den Ende]

Srikanth,

a UAF ADD is implemented as a COPY from the DEFAULT username.
Any settings yoou do explicitly modify are those of DEFAULT.
For you, SET HOST 0 gives an authorisation failure. Like Ian said, it could be the Flag=DISUSER.
It could also be that ACCESS REMOTE is not enabled. Even the EXPIRATION can be specified in the past. (or to be complete, you could have mis-typrd Username and/or Password). All of these give Authotisation Failure, although the ACCOUNTNG info, and the messages given to priv'd processes with REPLY/ENABLE=SECURITY are more specific.

So, various checks to make.
Easiest to find out on another session with SECURITY & OPER priv, and REPLY/ENABLE during the failing LOGIN attempt.

hth

Proost.

Have one on me.

jpe

[Srikanth Arunachalam]

Hi All,

thanks for your help. Ian's solution did help.

Regards,
Srikanth

[Robert Gezelter]

Srikanth,

Please heed Jan's comment about the quotas and other settings on the Oracle account.

The default settings are generally NOT suitable for an application like Oracle. Please check the Oracle Release Notes or the Installation Guide to get the correct settings.

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