inalfa01
13th February 2008, 10:13
We run Baan 4c4 on AIX with an Oracle 9i database.
I want the archive company to be in another Oracle Database.
What has to be configured at Baan and Oracle side?
Markus Schmitz
13th February 2008, 12:48
This is actually a pretty common setup. here is what you do:
a) Create the new instance, ie. call it "archiv"
b) Create the user baan and all the other users with the same password as in the origional database
c) create the role r_baan and assign it to the users (same as connect and resource).
d) Create in Baan in "Maintain databases" two new database entries, ie. archiv and archiv+A, which basically set as parameter something like "ORACLE_SID=archiv"
e) Create a new company in baan and assign it the newly created database definitions.
That's it. Straight forward and works like a charm.
Regards
Markus
manojsharma
27th June 2008, 23:22
Hi,
I am also working on the Archiving and Having HP unix11.00 and Oracle 9.2.0.7, I would like to know the following
b. How to creat Baan Users with Same password? Is there is some command at Ora Admin or Unix to copy existing all Baan users with same password.
C. How to create R_Baan and assign it to the users.?
I have assign SID in the database.
Thanks in advance
Markus Schmitz
28th June 2008, 12:16
oraadmin is not a suitable tool to be used, when working with two databases, so you have to resort to sqlplus:
to create a user:
create user X identified by Y temporary tablespace Z;
grant r_baan to X;
grant connect to X;
grant resource to X;
naturally replace X,Y,Z according to your system.
I hope that helped,
Markus
manojsharma
28th June 2008, 14:40
Hi Markus,
when I connect to baan through bsp login and try to create table for archiving company, it says 0 table created and in error log I saw "Error : 540, database logon denied"
Thanks in advance.
manojsharma
28th June 2008, 15:55
Hi
The role R_BAAN is not available in second instance. how to create this.
Aakash Rathor
13th September 2023, 15:42
Hi @Markus & @manojsharma,
I am still stuck at the first step.
As per the DB team, they have created a new Db instance and provide us the details.
I have created new archiving companies and added it to the new DB instance.
However, now when I create companies using bsp or other super user account, I am getting same error as that of Manoj i.e. Logon denied.
Need this board's guidance here.
Thanks,
Aakash Singh
mark_h
15th September 2023, 14:58
Did you make sure this step was complete:
Create the user baan and all the other users with the same password as in the origional database
I have not done archiving, but I just had a case where our dev company (as BSP) if I tried to do anything with the tables I got login denied, Had to get DBA's to reset the account and I had to fix the baan password in our 4c4 instance.
Markus Schmitz
19th September 2023, 11:09
Hi Aakash,
It is a looooooooong time ago, that I was on the board here and also a very long time ago, that I worked with Baan. I am also impressed that there are still Baan IV customers around.
But here is what I recollect:
a) When a normal user works on an existing Baan company, then the Oracle Driver or Baan connects to the oracle instance using credentials specific to that user. These credentials are stored encrypted in a file called "ora_users" under $BSE/lib/ora (if I remember correctly).
This is the reason, that you need to create all oracle users of your "baan" instance with the same login and password also in the "archive" instance, as Mark said above.
b) When a super user, like bsp creates a completely new company or just a single table, then the Oracle driver is not using the user specific credentials, but the credentials of the oracle user "baan". This user owns the role "r_baan" and on table creation assigns the required read/write permissions of new tables to r_baan, All valid baan users on the other hand have r_baan assigned.
This is specified in a file called "ora_groups" in the same directory. For this to work again you need the oracle user "baan" in both instances with the same username/password and the ora_groups file needs to contain two entries, one for each oracle instance.
Depending on your baan version there was a binary (script) called ora_admin6.1, which you could use to manipulate these runtime files, or you could simply edit them in vi.
Good luck,
Markus
Aakash Rathor
25th September 2023, 17:14
Hello @Markus,
Thank you for your reply. It had some good information for me.
However, pardon me for being naive, I would like to ask one more question:
In the part a), you mentioned that "This is the reason, that you need to create all oracle users of your "baan" instance with the same login and password also in the "archive" instance, as Mark said above.".
How should this step be performed? Should it be done at Application level using "bsp" account or does it need to be done at the DB level by the DBA team?
In whatever ways, if possible, kindly guide with the steps too.
Thanks,
Aakash Singh
Markus Schmitz
25th September 2023, 17:17
Hi Aakash,
in Baan IV, this had to be done by your DBA.
In Baan VI they added functionality to do this from within the application, if I remember correctly. But I had left the BaaN universe before that happened, so I can not tell for sure.
In any case doing it on the DB level works for sure.
Regards
Markus