This is Oracle 8.0.4 on Windows NT4.0 with SAP R/3 4.0B - our quality-assurance system (QAS), that's been running fine for nearly four years. Suddenly, I'm no longer able to connect or open the database. No recent configuration changes have been made. Here's the session:
Oracle Server Manager Release 22.214.171.124.0 - Production
(c) Copyright 1997, Oracle Corporation. All Rights Reserved.
Oracle8 Enterprise Edition Release 126.96.36.199.0 - Production
With the Partitioning option
PL/SQL Release 188.8.131.52.0 - Production
SVRMGR> connect internal
ORA-01017: invalid username/password; logon denied
The message is misleading because there is no password file (the normal setup for this version with SAP) and no password is need. I've referred to SAP notes, which tell me:
- Unlike normal database users, SYSDBA/SYSOPER/INTERNAL connections are not based on information in the Oracle data dictionary but authenticated via local operating-system groups, which allows connection when the database is stopped.
- Based on membership of these two groups (ORA_<sid>_DBA, ORA_<sid>_OPER), CONNECT INTERNAL automatically executes a SYSDBA or SYSOPER connect.
In our case, the administrative OS user is 'QASadm'; a second user 'SAPServiceQAS' runs SAP background processes. I've confirmed through NT's User Manager that both are members of local groups ORA_QAS_DBA and ORA_QAS_OPER.
I've also checked to ensure the NT service 'OracleServiceQAS' is running. Nevertheless, my
hunch is that this service could be the problem... but don't know what to try.
The last entries in the alert log indicate successful recovery from a stuck archive (but I doubt this is related).
I'd be very grateful for any assistance on this.