Unable to install BOE4 on LINUX with an Oracle repository

[Former Member]

Hi, I'm trying to install BOE4 on Linux 5.7. At the installation, the default DB2 database is the only option! so i am forced to use DB2 at this stage. After the installation is complete I try to re-point the new node to an Oracle db instead, This fails after creating 7 oracle tables (so connectivity does not seem and issue).

I've also tried creating a 2nd node on the same server, and this also fails with the same error.

Any ideas?

[denis_konovalov · Accepted solution]

The proper install package does has an option to use non-default Database, please review installation guide for unix which shows the steps.

As to the second issue - which error do you receive?
You should never-ever re-point existing SIA to a new CMS DB, you always, always have to create new SIA.

What exact version is your Oracle DB?

What exact version is your Oracle Client?

What is your LD_LIBRARY_PATH variable is set to?

What is your PATH variable set to?

[Former Member · Accepted solution]

On top of what Denis said (find how to install on another DB rather than the default one and the variables check), I would recommend you re-run the install using your Oracle DB after having downloaded the packages available here for RH 5.7 or above (only for the SP02 installer):

http://service.sap.com/sap/support/notes/1630886

Regards

[Former Member · Accepted solution]

Thanks for your help on this Denis

at our first attempt to install: there was an option to select a database type, when we selected Oracle we got this error

......

an error has occurred

"you cannot proceed because the following has failed validation:

Cannot verify database login information. (INS00104)

...............

according to this SAP thread http://scn.sap.com/thread/2054941 This thread tells us to 're-point'

after creating the node(s) using DB2 first.

Oracle Client (64) is 11.2, Oracle DB is 11.2. i'm not sure about the paths (yet) but I am able to logon using sqlpllus ok.

[denis_konovalov · Accepted solution]

if it says "re-point" it is wrong

does the Oracle user you use has Connect and Resource roles on the schema you're connecting to ?

[Former Member · Accepted solution]

Please review the KB provided in my previous answer, it contains the answer to your issue.

Regards

Romain

[Former Member · Accepted solution]

@ Romain: Could you please put in the details of the notes. Somehow it is blocking me.

[Former Member · Accepted solution]

@Denis: Could you please elaborate as to why we should not repoint an existing SIA to a new Database? I would like to understand why you do not recommend this.

Thanks

[denis_konovalov · Accepted solution]

Because when you simply point SIA to a new CMS DB, SIA is not properly registers with that CMS DB.

Only new SIA process properly registers SIA with CMS DB and creates all required DB records.

[Former Member · Accepted solution]

Thanks for the quick update Denis. Just to add to this I was under the impression that we can always use the same SIA to repoint to a new empty schema. This wont really any issues as anyhow new entries and server pids would have to be created. Thus it should get properly registered.

Why is it that only a new SIA can get itself registered to a new DB and a old SIA cannot.

Please correct me as far as my understanding is correct, first the SIA has to be created in any case and then the CMS DB. We usually need to make a connection(Datasource) for the SIA with the CMS DB. So why cant the old SIA push all the entries into the new CMS Db?

Thanks,

A.

[denis_konovalov · Accepted solution]

Because the code used to point SIA to CMS DB and code used to create new SIA are different, that's why the functionality differs.

When you install the product, a temporary CMS is started first, without any SIA, it is that temp CMS that creates CMS DB and then registers first SIA into it.

If you go thru the install logs you'll see this process.

[Former Member · Accepted solution]

You need a S-User account to access the KB (an account granting you access to the Service Market Place). The general rules of usage forbid copy/paste of KB content so Im afraid I cannot do that.

Still, this KB contains a known bug in the SP02 installer on RH5.7 and above leading to the issue you encounter when trying to map to the existing Oracle DB. However, it also contain packages to be downloaded (available in the KB) and swapped in the SP02 installer to fix this.

[Former Member · Accepted solution]

Hi Romain, do I also need to replace every subsequent fix pack (before installing/applying) with these packaged files?

[Former Member · Accepted solution]

Hi,

No, this fix, as defined in the KB, would only need to be replaced in installers prior to patch 2.8. However, at this date, the current patch available is 2.17 so I would not recommend installing anything under patch 2.8.

In short,

- swap the libs in SP02 installer, finish your install successfully

- patch to 2.17, WITHOUT modifying the installer

This is clearly documented in the KB. Or so I believe (If not, feel free to let us know what you consider should require improvement to make it clearer)

Regards

[Former Member · Accepted solution]

Thanks very much to Denis, Romain and A.

using all your advice it has now worked.

to recap, Linux 5.7 environment, Oragle 11g database used for repositories.

I uninstalled and removed all the existing BOE4 files

I used the latest BOE4 base installation files, replaced the 3 files that Romain mentioned above, and it installed ok using Oracle as the repository database. Then installed fixpack 17.

on the server I used, the whole process took nearly 3 hours.

Thanks again guys.