Goran,as they used to say in Istanbul airport to english football teams "welcome to hell".
SAP mandates a number of initialisation parameters (that vary by Oracle and SAP release) including undocumented ones, and sometimes also including ones that make no difference at all (FILESYSTEMIO_OPTIONS is mandated on Windows for example). The recommendations that you have below are almost certainly sourced directly from a note from the SAP support knowledge base.
Clearly there are security implications here so it might be worth doing a SAP knowledge base search around SOX compliance to see if these requirements can be removed. I'd leave the SAP dba in the DBA group though because most all database administration is likely to end up being done by them through the SAP admin tools for Oracle. In recent releases these tools have got reasonably smart - so for example just because you use BRTOOL to backup your database that doesn't mean that the backup can't be an RMAN hot backup - these advances have not always been appreciated by BASIS consultants.
On , goran bogdanovic <goran00@xxxxxxxxx> wrote:
I assume some of you have already done SAP projects with Oracle DB.I am currently in involved in one such project where I am responsible for a database side. The SAP consultant has come up with necessary configurations regarding DB and DB server which makes me say 'hmmm'.
He can't explain it why it is necessary or is there any other way to do it - something like 'take it or leave it'. Since I don't have experience regarding SAP on Oracle I have few questions and will appreciate if you can share your knowledge/experience.
so, here are the requirements:
Q1: is it really necessary? Q2: if yes, any workaround possible?
2. SAP System Administrator OS user must be in OS DBA group
Q1: is it really necessary? Q2: is there any other way to do it?
3. SAP Database Administrator OS user must be in OS DBA group Q1: ist it really necessary? Q2: is there any other way to do it?