Hi,

Good to have such a nice forum to discuss things.

Right now I am stuck in a problem of creating a database user which is linked to a baan user. I have tried to create the user in the following ways.

1. through baan dba module.
2. by inserting entries in ora_users file , using encrypt6.2 & also creating the corresponding user in the oracle env & granting it the connect role.

3. using the ora_admin / maint scripts.

All these methods lead to one error 514.

My current baan env is

version baan erp 5.0b
Os - solaris
oracle 8 on unix

I have to deliver the installed servers by tommmorow. anyhelp in this matter is appreciated.

thanking you in advance

regards
max

514 ESECURITY (ORACLE)
Security error; probably no user / group permission

I cannot help you more than post here what 514 error code means.

Maybe other guys can post more Info.

Good Luck.

There are a couple of things you can do to get around or solve this error.
1. Edit the Ora_users file. Copy a line in the file and edit it to reflect the new user you are adding.
bsp:bsp:encrypted_password:baan_group
to
new_user:bsp:encrypted_password:baan_group

2. Check out authorization into Oracle. Make sure the baan_group is in Oracle.
2.1 Make sure the new_users is in oracle and has authorizations to connect, and has the role/membership of the baan_group.
2.2 Make sure the encypted_password is equal to the password in Oracle.

I have checked the following things in the current environment.

1. the user is present in baan & unix.
2. using the dba module in baan I an not able to create a entry in the ora_users file. It fires an error Invalid username / password. Error 12705. This error is logged in the log.ora8_maint.. file.
3. I have tried creating user & grp at oracle level & then in baan & then trying to link these two. But the I get the same error.

Any inputs will be helpfull.

max

Maximus,

Is your $BSE/lib/ora/ora_groups properly configured? Is your baan 'group' user able to logon to the database? e.g. you can test this by creating a dummy table using the session 'create tables'.

Yes my baan group user is able to logon to the oracle db.

Thruogh baan as well as through oracle sqlplus.

But I still could not get the baan user converted to db user.

I am still facing the NLS parameter issue.

If any other info might be usefull in resolving the problem please do write back, I will be happy to provide the info.

thanks, all of you.
regards
max

Is Your BAAN-user the same as the ORACLE-user?
If so, the $BSE/lib/ora/ora_users file should contain:
<baanuser>:<oracleuser>:<encrypted password>:<baan group>
p.e.: bsp:bsp:4QAVtL3vQ\U)CR}eXW*Tz5D&6Y1T8Z:baan
or ab12345:ab12345:4QAVtL3vQ\U)CR}eXW*Tz5D&6Y1T8Z:baan

Regards,

D.E.

I also have the same requirement and tried ora8_admin6.1 script and it is jumping/spreading all over the screen and not able to type somthing!

To add a new user to existing group copy and paste the previous line would do but the new group is difficult.

When you cut and paste make sure the carriage returns and properly done in places.

To use the ora8_admin tool you must set your TERM properly first (VT100)

Maximus, what is the NLS issue you have?

BaaN recommends the NLS settings as

nls_lang:american_america.we8iso8859p1

and NOT

AMERICAN_AMERICA.US7ASCII

We had problem with corrupted report layouts that I encountered this issue. Here are the case details from the BaaN Support site -

Error "Index n out of dims[n] n " on form, report, menu layout tables on ORACLE
Author T Chakrab Creation Date: 11 Mar 1998 Alternate ID:
Solution No: 1955 Solution Version: 1.0 Status: Published
Product: ttB40b Sub Product: ttadv Session: advformedit
Package: tt Version: B40 Release: b
Solution Type: PAR REPORT
Symptom information
VAT report with errors
Index out of dims error when trying to maintain a report layout
ttadv335.layo index 284 out of dims (1) 260

NPROa,

I had to shorthen your post because the layout was, well a bit messed up. The NLS character set choice depends really on your application needs. You could still use US7ASCII. The important thing is that you keep the NLS settings compatable on database, server and client level. The index out of dims error is caused by updating the tables ttadv334/ttadv335/ttadv364 with conflicting NLS settings. Reason for that is it messes up the binary 'layout' fields of these tables.

For characterset my recommendation however would also be to use WE8ISO8859P1 or similar.

Hi Pat,

Its NPRao ;-)

and thanks for formatting the post.

Can you please explain the cause and effect, background info about the different NLS settings. I didnt get any much info from BaaN on this topic, perhaps you can share your knowledge here.

Thanks!

Hi All,

Right now I have manually added the required users to the ora_users file. I am not very sure when the user might face a problem becasue of this. I have about a week with me to get the right solution so keep you thinking caps on & pour in your ideas. I will try out the NLS config suggested .

If any other input is needed from me on this problem please post a message & I will get back.

Thank you for the help, keep them coming.

max

Dear All,

Copying ora_user is a standard procedure recommended by implementation partner to non baan administrators and no problems in last 12months!

Only thing no information stored in dba tables for this addition and next time do the same to link a baan user to db user.

Maximus,

One thing to keep into account is that you should make a choice as how to add/delete users: either you use the DBA module in Baan and convert to runtime - or - you manually manipulate the ora_users file each time. You will definatively get problems when you switch between both methods.

NPRao, I will see if I can dig up a document that describes the NLS issues very well.

Hi Pat,

I will stick to the current method of editing the ora_users file. I wanted to check that if I edit the ora_users file, do I still have to male entries in the baan dba tables. Are the entries required. The entries seem to be useless as these entries cannot be converted to the db users. But I have still maintained the entries. All the entries are with status "Not yet created in RDBMS". Does the porting set or the tools version have a effect on this problem.
I have 6.02a.03.03 installed on the servers. Do I need to upgrade the porting set or the tools

max

You can modify runtime files and keep system running.
But the rule is stick to one method.

Remember to keep copy of these run time files.
Remove from menu these sessions so no one attempt to create.

Recommended practice is to follow inserting entries in tools table and do convert to run time files. You have two places where it stored.

I joined a company where Oracle DBA was handling the baan admin and he opted to modify unix files and now no option(easy) to follow him!

If you run any tools from baan VST or IBaanSupportEye tools then
that will pick all these omissions to baan support.

Even then filling the information on tables would solve that!!

Give more information on OS,DB and Baan Version so we can recommend the portingset levels.
6.1c.06.02 is stable and 03 introduce restriction on refers to.

Originally posted by maximus
Hi Pat,

I will stick to the current method of editing the ora_users file. I wanted to check that if I edit the ora_users file, do I still have to male entries in the baan dba tables. Are the entries required. The entries seem to be useless as these entries cannot be converted to the db users. But I have still maintained the entries. All the entries are with status "Not yet created in RDBMS". Does the porting set or the tools version have a effect on this problem.
I have 6.02a.03.03 installed on the servers. Do I need to upgrade the porting set or the tools

max

Max,

I think the entries in your DBA tables are indeed useless if you stick to the direct method of changing the ora_users file. You can automate user maintenance to a good degree using UNIX shell scripts. I have always found the Baan DBA module in its current incarnation to be absolute useless.