I'm attempting to create a baan user.

The oracle database is remote.

When I had to do this a couple weeks ago, I ended up calling Infor to assist.

Anyway, I was trying to confirm the steps, and also trying to see where I went wrong on this.

Basically, these are the steps.


1. Create DB user
2. Create OS user
3. link OS user to DB user, using ora8_admin6.1
4. link OS user to baan user, using maintain user data session
5. tack on any session authorizations

Well, the issue is that, according to support, that tool "ora8_admin6.1" is designed to only work with local databases. I guess that is possible.

In this case, I recall that the support technician did the following:

(a) /baan/bse/bin/encrypt6.1 <oracle_password>
this above command generated an encrypted password, i'll call it
<oracle_encrypted_password>
(b) Then, appended to /baan/bse/lib/ora/ora_users the following
<osusername>:<dbusername>:<oracle_encrypted_password>:baan

These (1) and (2) above took the place of the (3) above.

Is this correct?

I'm asking as I just tried this, and it didn't work, and am about to submit a support case.

Is there any other way?

Thanks!

it's not osuser it's baan user. (usually they're the same, but it's possible that it is different)

Other than that the steps look correct.

To create the DB user though you need to:
create user <username> identified by 'password';
grant connect, resource to <username>;
grant r_baan to <username>;

Did you do those steps?

Also, I'm pretty sure ora8_admin6.1 will work if you have oracle_service_name: in your db_resource file and or ORACLE_SERVICE_NAME in your environment.



Dave

it's not osuser it's baan user. (usually they're the same, but it's possible that it is different)

Other than that the steps look correct.

To create the DB user though you need to:
create user <username> identified by 'password';
grant connect, resource to <username>;
grant r_baan to <username>;

Did you do those steps?

Also, I'm pretty sure ora8_admin6.1 will work if you have oracle_service_name: in your db_resource file and or ORACLE_SERVICE_NAME in your environment.



Dave

Dave, thanks for your clarification. It now makes more sense.

So, it's more like this? (according to my steps above)
1. create db user
2. create os user
3. Link baan user to db user
4. link baan user to os user

OK, now I'm looking for this db_resource file. Thanks. I would have thought that it'd be in the same folder as the ora_users file, or in baan/bse/bin or baan/bse/lib somewhere but alas, grep to the rescue, it is in /baan/bse/lib/defaults

Hi,

You can find the file in $BSE/lib/defaults/

Regs

pet

OK, I've located the file, but I see nothing in it that suggests an oracle service name.

ora_init:0111000
ssts_set_rows:2
dbsinit:01
ora_timeout:{300,60,60,60,60}
lock_retry:0
oracle_client_home:/baan/bse/lib/ora/oracle_home
ora_column_format:7
nls_lang:american_america.we8iso8859p1

I'm really confused now.

There are no examples!

Also, when I search for the knowledge base U7155CUS, I get an SQL error on the site.

I am referencing this solution ID: 152685 ... It is so far the best documentation that I can find, but it still doesn't tell me what to do .... I would really like an example ... why is the example blank?

In porting sets 6.1c.05.02 there is a new concept of oracle_client_home(ref. Appendix C of U7155CUS) . Typically if $BSE/bin/ora_update (ref. to solution 15219) is run then this parameter get set to $BSE/lib/ora/oracle_home in the db_resource file and a directory $BSE/lib/ora/oracle_home gets created with oracle client libraries (compatible with oracle driver) .
Now, if sqlnet is being used to connect to oracle database (i.e. in $BSE/lib/tabledef6.1 file has TWO_TASK set) then TNS_ADMIN=<location of tnsnames.ora file>must be set in the $BSE/lib/tabledef6.1 file(or in session ttaad4110m000 and Convert to RTDD).
However ora8_maint6.1 does not read the tabledef6.1 file. It reads the oracle env parameters from unix env and db_resource file. So you have to set TNS_ADMIN and TWO_TASK in the unix env while running ora8_maint6.1.
You can also set two_task or oracle_service_name and oracle_local_template in the db_resource file to solve this problem.

EXAMPLE(S):



WORK-AROUND:

That's a standard template that baan support uses (solution description, example, etc.), they're not required to create an example, and sometimes it doesn't make sense (to the solution writer) to do so.

All of the actual docs for baan are available via the document search which is a different area on the site than knowledge base.

Look for the oracle driver manual for baan 4, that will explain all of the OS level files.

the db_resource setting is just oracle_service_name:<servicename>
that's all lower case, and with a colon.

Oracle has 2 ways of handling SQL*Net connections, TWO_TASK (old oracle8 style) and SERVICE_NAME ( new oracle 9 style)

if your system is setup for two_task then service_name may not work.

if that's the case you can try two_task: in your db_resource as well.

When you try this know that once you set this, if it's not correct, you may not be able to connect to Baan until you undo it. so better to try on a test box or off hours.

Dave