Two days ago, I have a yahoo message from my friends about her SAP Production server which un-accidentally have been changed its SAP database owner schema. She uses SAP ECC 5 version and using Oracle Database 10g. After several hours being headache looking for solution, the problem was solved. So the main problem is that SAP logon mechanism using 2 place to save its user and password. SAP save it on Oracle dictionary and SAPUSER table. One of it password hadn’t changed yet.
Here is I have copied some articles from saptechies.com :
1. What are the default database users in the SAP environment?
The following database users exist in the SAP environment:
SAPR3 / SAP<sid> / SAP<xyz> / SAPSR3
The SAPR3 / SAP<sid> / SAP<xyz> / SAPSR3 user is the owner of all R/3 objects. The work processes log on to the database with this user. The SAPR3 user was always used for older R/3 releases. However, since several R/3 systems may be present in the same database within MCOD with current releases, you can replace the SAPR3 user with a system-specific SAP<sid> user here. You can define this during the installation. To avoid confusion during homogeneous system copies, as of 4.7 SR1 you can use an SID-independent username, SAP<xyz>, with “SAP” followed by any three characters (see Note 617444). In the meantime, the system proposes the username SAPSR3 by default – irrespective of the SID that the system actually uses.
The SAP® NetWeaver is a comprehensive application and integration platform
that consists of several components and tools.
Important components are e.g. the NetWeaver Application Server,
NW Business Intelligence, NW Exchange Infrastructure,
NW Master Data Management, NW Mobile, NW Portal,
Auto-ID infrastructure, NW Identity management.
Relevant tools are e.g. Adaptive Computing Controller,
NetWeaver Composition Environment, NW Developer Studio,
NW Visual Composer, SAP® Solution Manager.
Just like for the former basis kernel the security of this platform is controlled
by corresponding system security parameters.
The following overview provides a short introduction in the relevant aspects
of selected parameters.
You can review the current settings with the help of the report
RSPFPAR or RSPARAM [via transaction SE38 e.g].
The parameter change history is available through transaction TU02.
The system profile parameters are stored in files on the operation system level
[an instance, a start and default.pfl] and are supposed to configure the different instances.
Dynamic parameters can be changed on the fly, while for static parameters a
restart of the corresponding instance is necessary to activate the setting.