RE: SAP on Oracle doubts
- From: "Blanchard, William" <wblanchard@xxxxxxxxxxxxxxxxxxxx>
- To: <Richard.Goulet@xxxxxxxxxxx>, <niall.litchfield@xxxxxxxxx>, "goran bogdanovic" <goran00@xxxxxxxxx>
- Date: Wed, 10 Feb 2010 08:32:55 -0600
You're right that SAP acts like soup nazis when it comes to the
database. However, as craptacular as their applications are visually
and technically, they are very functional.
WGB
_____
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Goulet, Richard
Sent: Wednesday, February 10, 2010 8:29 AM
To: niall.litchfield@xxxxxxxxx; goran bogdanovic
Cc: ORACLE-L
Subject: RE: SAP on Oracle doubts
Don't ever expect SAP to explain anything, because "they know better".
Another company that should go the way of the DODO bird.
Dick Goulet
Senior Oracle DBA/NA Team Lead
PAREXEL International
_____
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of
niall.litchfield@xxxxxxxxx
Sent: Wednesday, February 10, 2010 8:20 AM
To: goran bogdanovic
Cc: ORACLE-L
Subject: Re: SAP on Oracle doubts
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:
> Hi All,
>
> 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:
>
> 1. REMOTE_OS_AUTHENT=true
>
> 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?
>
>
>
>
>
> regards,
> goran
>
>
>
>
Other related posts:
