on 05-12-2010 2:09 PM
is there any issues with changing default name of listener for a sap system?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No, there shouldn't be...
thanks for the response..
is it recommended to change?
wondering how other shops have it set.
Why do you want to change it? There is no need for it...
(if it ain't broken, don't try to fix it..)
Kind regards,
Mark
I am with you. Auditors are requesting.
I am just looking for reason why I should leave it alone.
the issue is the auditors do no know sap...they just look at oracle for sap as another oracle system and recommend global changes.
i wish sap would publish something to help us sap dba's.
seems everytime i have to change something for an auditor something for sap breaks.
Ok, I understand... Well, during the installation of an SAP system, you get the option for listener parameters, and one of them is the listener name. You can just enter what you want as a listener name.
Hope this is answering your question.
Hello,
In genereral, you only NEED to change, if you want to run more than one listener on one box.
I.E. if you have DEV and QAS on the same host.
I have one customer with 15 SAP systems running on a single host and thus we have 15 listeners there.
No prob with this, beside you need to specify the listener name in lsnrctl commands
Like
lsnrctl start LISTENER_DEV
Was there any reason given by the auditor why this is considered to be a good idea.
Next thing he will require is the listener password (which is not a so big deal to circumvent)
and tcp.invited_nodes (which is quite helpfull and good practice to implement).
Volker
no reason so i assume some best practice thing...
they might come back w/ password request - dunno
i use OS authentication for 10.2
hoping that is enough
Ya, see it the same way.
But I have been argued, that there had been listener-bugs and if os auth is
exploited, it would be good to have password security in addition.
Hummm, local OS-auth as implemented bypasses the password anyway.
I showed it to the auditor, that with a password in place, you can
shut down the listener without a password as a dba-member...
"Please do it anyway..."
BTW, I do not have a system to play with available right now.
Maybe someone can test...
Is it still that you can start a LISTENER with default values, if
no listener with name LISTENER is configured ?
I mind to remember it was that way in 8.something.
I reconfigured LISTENER to LISTENER_DEV and
lsnrctl start
fired up a listener LISTENER on port 1521 without LISTENER being configured.
But don't know if it is still that way in 10.2.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.