Unable to log on through SAP GUi

Question

Hello Gurus,
Issue: Unable to logon through SAP GUI after giving the username and
Password. When the user name and password is entered the system gets to the process mode but hangs in the same stage.
When i check the R3trans -d the following is the result:
This is r3trans version 6.13 (release 640 - 12.12.05 - 14:24:42).
unicode enabled version
2EETW169 no connect possible: "DBMS = ORACLE --- dbs_o
ra_tnsname = 'B3Q'"
r3trans finished (0012).
It means the r3trans is not able to connect the DB. Please suggest a
OSS note for this issue or solution for this issue asap. This
is very urgent.
We are using Nw04,BW3.5, BI3.53, EP6.0 & Oracle 9i. The following are
the support pack details:
Operating system Windows NT
Machine type 4x Intel 8
Database system ORACLE
Release 9.2.0.4.0
Kernel release 640
Compilation NT 5.0 2
Patch Level 109
ABAP Load 1521
CUA load 16
Mode opt
DB client lib. OCI_920_SHARE
DB releases ORACLE 9.2.0..,
DBSL version 640.00
DBSL Patch Level 109
SAP_ABA 640 0016 SAPKA64016 Cross-
Application Component
SAP_BASIS 640 0016 SAPKB64016 SAP Basis
Component
PI_BASIS 2005_1_640 0007 SAPKIPYJ67 Basis Plug-In
(PI_BASIS) 2005_1_640
SAP_BW 350 0016 SAPKW35016 Business
Information Warehouse
BI_CONT 353 0009 SAPKIBIFP9 Business
Intelligence Content
AOFTOOLS 400_640 0000 - Add-On
Assembly Kit (AOFTOOLS 400_640)
Enterprise Portal 6.0:
J2EE Engine 6.40 PatchLevel 104329.313
Portal 6.0.17.0.0
Knowledge
Management
Collaboration 6.0.17.0.0 (NW04 SPS17)

Answer 1

Hello Veer .
Please try to do the following  ...
<b>ORA-01017: Invalid username/password; logon denied</b>
Message ORA-01017 can occur both in step 1a) and in step 1b) or 2). Depending on this, the problem can be corrected as follows:
1a) log entries:  Logon as OPS$ user to get <sapowner>'s password
                  Connecting as /@<sid> on connection 0 ...
ERROR => OCI-call 'olog' failed: rc = 1017
ERROR => CONNECTfailed with sql error '1017'
If you intend to use the standard password for <sapowner> anyway, you can ignore the error message at this point, as the OPS$ mechanism is not needed at all and the connect is carried out using <sapowner>/sap successfully afterwards. Note, however, that BR*TOOLS require a working OPS$ mechanism when executing via DB13!
           Otherwise, make sure that an appropriate OPS$ user is set up. To do this, proceed as follows:
Check whether the parameter
os_authent_prefix = ops$
is set correctly in init<sid>.ora. If you have to make a change, restart the database afterwards.
On Windows, make sure that the following parameter is set in sqlnet.ora:
SQLNET.AUTHENTICATION_SERVICES = (NTS)
Determine which operating system user <os_user> wants to create the connection. If this involves a connect initiated out of the R/3 System (for example, work process connect, DB13 actions), user <sid>adm is used under UNIX and user sapservice<sid> under NT. If you manually called the program that executes the connect, the user you are using is decisive here.
Use SVRMGRL to check whether the user OPS$<os_user> (or OPS$<domain>\ <os_user> for NT with Oracle >= 8.1.5) has been created at database level:
SELECT * FROM DBA_USERS WHERE USERNAME = 'OPS$<os_user>';
(for <os_user>, always use upper case)
If the system does not return an entry, create the user:
CREATE USER "OPS$<os_user>" DEFAULT TABLESPACE <user_tsp>
  TEMPORARY TABLESPACE PSAPTEMP IDENTIFIED EXTERNALLY;
Note that the name of the OPS$ user must be specified completely in uppercase letters (also the host and domain names in case of NT and W2K), since a logon as OPS$ user will not work if it is not:
  wrong:   CREATE USER "OPS$c11adm" DEFAULT TABLESPACE ...
          CREATE USER "OPS$sapdom\C11ADM" DEFAULT TABLESPACE ...
  correct: CREATE USER "OPS$C11ADM" DEFAULT TABLESPACE ...
           CREATE USER "OPS$SAPDOM\C11ADM" DEFAULT TABLESPACE ...
Tablespace <user_tsp> is used when newly creating objects, when no explicit tablespace name is specified. In connection with R/3, this is almost never the case. Therefore, you can specify any tablespace. Proposal:
         R/3 <= 4.6D:  <user_tsp> = PSAPUSER1D
        R/3 >= 6.10:  <user_tsp> = PSAP<sid>USR
Check whether the OPS$ user has sufficient authorizations. The following statement must at least return CONNECT and RESOURCE:
SELECT GRANTED_ROLE FROM DBA_ROLE_PRIVS
  WHERE GRANTEE = 'OPS$<os_user>';
If CONNECT and/or RESOURCE is missing, you can grant theseauthorizations as follows:
GRANT CONNECT, RESOURCE TO "OPS$<os_user>";
If all the settings described above have been made correctly on NT/ Windows 2000, but the error ORA-01017 is still displayed during the OPS$ Connect, the cause may be a start user set incorrectly for the SAP Service. Change to the services overview of the operating system and check the user who starts the service SAP<sid>_<instance_number>. If the user is not sapservice<sid>, enter sapservice<sid>. Other users (such as the local administrator) do not have an OPS$ user in the database, which leads to error ORA-01017. Check also whether the start user sapservice<sid> is a local user or a domain user. Domain users can be identified by the preceding domain name. Depending on this, the following OPS$ user should exist on database level:
Domain user:    <domain>\sapservice<sid>
OPS$ user:       OPS$<domain>\sapservice<sid>
Local user:      sapservice<sid>
OPS$ user:       OPS$<local_host>\sapservice<sid>
1b) log entries:  Logon as OPS$ user to get <sapowner>'s password
                  Connecting as /@<sid> on connection 0 ...
                  Now I'm connected to ORACLE
                  Got <sapowner>'s password from table SAPUSER
                  Disconnecting from connection 0 ...
                  Now I'm disconnected from ORACLE
                  Try to connect with the password I got from OPS$-user
                  Connecting as <sapowner>/<pwd>@<sid> on connection 0
ERROR => OCI-call 'olog' failed: rc = 1017
ERROR => CONNECTfailed with sql error '1017'
           An ORA-01017 message at this point indicates an incorrect <sapowner> password in the SAPUSER table. In this situation, proceed as follows.
Set the password consistently in SAPUSER and in the Oracle DDIC using the following BRCONNECT call (BRCONNECT >= 6.10):
brconnect -u system/<password> -f chpass -o <sapowner> -p <password>
Otherwise, change the password in the SAPUSER table:
DELETE FROM "OPS$<sid>ADM".SAPUSER;
INSERT INTO "OPS$<sid>ADM".SAPUSER VALUES ('<sapowner>', '<password>');
Important: The SAPUSER table should only exist once in every system: for OPS$<sid>ADM. For this reason, only execute the above-mentioned statements for OPS$<sid>ADM - irrespective of the operating system user actually being used. All other OPS$ users can access the SAPUSER table using a synonym.
If the connect still terminates in the same way, check once more the section "General checks".
2) log entries:  Try to connect with default password
                Connecting as <sapowner>/<pwd>@<sid> on connection 0
ERROR => OCI-call 'olog' failed: rc = 1017
ERROR => CONNECT failed with sql error '1017'
If you want to use the standard password sap and do not need the OPS$ mechanism, reset the <sapowner> password to sap:
ALTER USER <sapowner> IDENTIFIED BY sap;
If you do not want to use the standard password, the error cannot be avoided at this point. Set up the OPS$ mechanism as described above instead.
Regards
Rahul
Please Award points if help is useful  *****