Component : Oracle -

Solution : https://service.sap.com/sap/support/notes/480266 (SAP Service marketplace login required)

Summary :
When attempting to establish a database connection using privileged modes such as "CONNECT INTERNAL", "CONNECT/AS SYSDBA", or "CONNECT / AS SYSOPER" in SAP environments, users may encounter errors such as ORA-01017, ORA-01031, and others, indicating issues like invalid credentials or insufficient privileges. These connection types rely on operating system group memberships (e.g., UNIX's dba or WINDOWS' ORA__DBA groups) rather than Oracle's data dictionary entries. Resolving these errors typically involves ensuring that the operating system user belongs to the correct groups as these are fundamental for authenticating SYSDBA or SYSOPER roles. Additionally, sapdba roles must also correctly configure to overcome related instance status errors.

Key words :
relevant local groups ora_<sid>_dba, calling operating system user belongs, domain user <domain>\<sid>adm, relevant fix apar iy22458, create audit trail fileora-09817, incorrectly set nls parameters, means ora_<sid>_oper, <sid>adm/sapservice<sid>, slightly restricted sysoper privileges, $oracle_home/rdbms/lib directory

Related Notes :

625222	connect with sqlplus takes a long time on Windows 2000
614036	Composite SAP Note: ORA-12631/ORA-12638
602843	Environment settings for R/3/Oracle on UNIX
595874	Failure of domain controller causes Oracle failover
583861	UNIX: Errors due to Oracle executable
562863	FAQ: Logon mechanisms
554112	Important Changes in Oracle9i
445038	Problems when accessing Net8 configuration files
417561	Connect internal in Windows of 2000 domain
403269	AIX: Database can not be started, startsap hangs
175636	cannot startup Oracle (with no/meaningless error(s))
168243	Assigning sysdba and sysoper authorizations
148535	Database backup fails with RMAN-04005/ORA-01031
97953	UNIX: Relinking of the Oracle executables