Unable to log on through SAP GUi

[Former Member]

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)

[Former Member]

Hello

I faced the same problem. After creating OPS$user (steps mention in earlier posts), we run “sapdba_role.sql” script and it worked for me.

Ora<sid> 30> sqlplus /nolog @sapdba_role UNIX

SQL*Plus: Release 9.2.0.4.0 - Production on Wed Oct 20 11:07:01 2004

Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.

Disconnected from Oracle9i Enterprise Edition Release 9.2.0.4.0 - 64bit Production

With the Partitioning option

JServer Release 9.2.0.4.0 - Production

Check sapdba_role.log for any error.

Thanks

Sharmishtha

[Former Member]

If SAP implementation program shell we use

any windows related issues

please confirm me to chek out microsoft watch list

[Former Member]

Hello Veeraraghavan,

• Execute dpmon at command level to determine the status of the work processes.

• Cross check if the Oracle database is open state.

• Check the archive directory status

• Check for freespace in tablespaces

• Execute R3trans -x for detail log.

Could you also state what changes where executed on the system?

Regards,

Ammey Kesarkar

<i>'Award points for useful info'</i>

[Former Member]

i have posted the answers for your question.

when i do r3trans -x i get the same result when i do r3trans -d.Please advise asap

Execute dpmon at command level to determine the status of the work processes.

--> Dispatcher Queue Statistics Tue Feb 20 11:13:54 2007

===========================

--------

---

+

---

+

---

+

---

+--

---

+

Typ

now

high

max

writes

reads

--------

---

+

---

+

---

+

---

+--

---

+

NOWP

0

10

2000

408

408

--------

---

+

---

+

---

+

---

+--

---

+

DIA

1

6

2000

396

395

--------

---

+

---

+

---

+

---

+--

---

+

UPD

0

1

2000

1

1

--------

---

+

---

+

---

+

---

+--

---

+

ENQ

0

0

2000

0

0

--------

---

+

---

+

---

+

---

+--

---

+

BTC

0

1

2000

9

9

--------

---

+

---

+

---

+

---

+--

---

+

SPO

0

3

2000

42

42

--------

---

+

---

+

---

+

---

+--

---

+

UP2

0

0

2000

0

0

--------

---

+

---

+

---

+

---

+--

---

+

max_rq_id 582

wake_evt_udp_now 0

wake events total 633, udp 476 ( 75%), shm 157 ( 24%)

since last update total 0, udp 0 ( 0%), shm 0 ( 0%)

• Cross check if the Oracle database is open state.

Yes data base is open and i am able to login with the admin ID in the database

• Check the archive directory status

C: and 😧 drives have space of 2.52 GB in C and 54 GB in D

• Check for freespace in tablespaces

• Execute R3trans -x for detail log.

C:\Documents and Settings\Administrator.SAP-R3-QAS>r3trans -x

This is r3trans version 6.13 (release 640 - 28.11.06 - 18:05:00).

unicode enabled version

2EETW169 no connect possible: "DBMS = ORACLE --- dbs_o

ra_tnsname = 'B3Q'"

r3trans finished (0012).

[Former Member]

Hello Veeraraghavan,

Check Notes

403004 - Database connect using R3trans fails

42177 - tp and R3trans: Connect is not possible

Also try to paste work process log.

I guess R3trans - v (Verbose) would give some extra info.

Regards,

Ammey Kesarkar

[Former Member]

Hello Veer.

The processes will not show up unless the DB is up and then app instance ..

Log on as SIDADM -- you should be in the home directory and give the command "R3trans -x" then check the trans.log file in that directory . It must be give you some errors -- typically ORA XXXX (XXXX is the number) search with that error for sap notes .

you can also check the env variables - DIR_ENTRY and DBMS_TYPE .

Please let me know what you find .

Regards

Rahul

• Please award points if help is useful ****

[Former Member]

Hello Rahul,

This what i found. This if you check there is one error called CONNECT failed with sql error '1017'

4 ETW000 r3trans version 6.09 (release 640 - 26.10.04 - 15:45:42).

4 ETW000 unicode enabled version

4 ETW000 ===============================================

4 ETW000

4 ETW000 date&time : 21.02.2007 - 01:01:40

4 ETW000 control file: <no ctrlfile>

4 ETW000 R3trans was called as follows: r3trans -x

4 ETW000 trace at level 2 opened for a given file pointer

4 ETW000 [dev trc ,00000] Wed Feb 21 01:01:43 2007 0.000000

4 ETW000 [dev trc ,00000] db_con_init called 0.000000

4 ETW000 [dev trc ,00000] create_con (con_name=R/3) 0.000000

4 ETW000 [dev trc ,00000] Loading DB library 'dboraslib.dll' ... 0.000000

4 ETW000 [dev trc ,00000] load shared library (dboraslib.dll), hdl 0 12068 0.012068

4 ETW000 [dev trc ,00000] using "D:\usr\sap\B3Q\SYS\exe\run\dboraslib.dll"

4 ETW000 42 0.012110

4 ETW000 [dev trc ,00000] Library 'dboraslib.dll' loaded 20 0.012130

4 ETW000 [dev trc ,00000] function DbSlExpFuns loaded from library dboraslib.dll

4 ETW000 32 0.012162

4 ETW000 [dev trc ,00000] Version of 'dboraslib.dll' is "640.00", patchlevel (0.39)

4 ETW000 111 0.012273

4 ETW000 [dev trc ,00000] function dsql_db_init loaded from library dboraslib.dll

4 ETW000 30 0.012303

4 ETW000 [dev trc ,00000] function dbdd_exp_funs loaded from library dboraslib.dll

4 ETW000 44 0.012347

4 ETW000 [dev trc ,00000] New connection 0 created 29 0.012376

4 ETW000 [dev trc ,00000] 0: name = R/3, con_id = -000000001 state = DISCONNECTED, perm = YES, reco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO

4 ETW000 39 0.012415

4 ETW000 [dev trc ,00000] db_con_connect (con_name=R/3) 26 0.012441

4 ETW000 [dev trc ,00000] find_con_by_name found the following connection for reuse:

4 ETW000 29 0.012470

4 ETW000 [dev trc ,00000] 0: name = R/3, con_id = 000000000 state = DISCONNECTED, perm = YES, reco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO

4 ETW000 37 0.012507

4 ETW000 [dev trc ,00000] Got ORACLE_HOME=D:\ORACLE\B3Q\920 from environment

4 ETW000 261 0.012768

4 ETW000 [dev trc ,00000] -->oci_initialize 22 0.012790

4 ETW000 [dev trc ,00000] Client NLS settings: AMERICAN_AMERICA.UTF8 36816 0.049606

4 ETW000 [dev trc ,00000] Logon as OPS$-user to get B3Q's password 57 0.049663

4 ETW000 [dev trc ,00000] Connecting as /@B3Q on connection 0 ... 28 0.049691

4 ETW000 [dev trc ,00000] Allocating service context handle 32 0.049723

4 ETW000 [dev trc ,00000] Allocating server context handle 25 0.049748

4 ETW000 [dev trc ,00000] Attaching to DB Server B3Q (con_hdl=0,svchp=01DB2A44,svrhp=01DB35D4)

4 ETW000 57 0.049805

4 ETW000 [dev trc ,00000] Wed Feb 21 01:01:48 2007 5297713 5.347518

4 ETW000 [dev trc ,00000] Assigning server context 01DB35D4 to service context 01DB2A44

4 ETW000 53 5.347571

4 ETW000 [dev trc ,00000] Allocating user session handle 191 5.347762

4 ETW000 [dev trc ,00000] Starting user session (con_hdl=0,svchp=01DB2A44,srvhp=01DB35D4,usrhp=01DBBD6C)

4 ETW000 58 5.347820

4 ETW000 [dboci.c ,00000] *** ERROR => OCI-call 'OCISessionBegin' failed: rc = 1017

4 ETW000 17479 5.365299

4 ETW000 [dbsloci. ,00000] *** ERROR => CONNECT failed with sql error '1017'

4 ETW000 36 5.365335

4 ETW000 [dev trc ,00000] Try to connect with default password 90 5.365425

4 ETW000 [dev trc ,00000] Connecting as B3Q/<pwd>@B3Q on connection 0 ... 22 5.365447

4 ETW000 [dev trc ,00000] Assigning username to user session 01DBBD6C 23 5.365470

4 ETW000 [dev trc ,00000] Assigning password to user session 01DBBD6C 31 5.365501

4 ETW000 [dev trc ,00000] Starting user session (con_hdl=0,svchp=01DB2A44,srvhp=01DB35D4,usrhp=01DBBD6C)

4 ETW000 38 5.365539

4 ETW000 [dboci.c ,00000] *** ERROR => OCI-call 'OCISessionBegin' failed: rc = 1017

4 ETW000 2358 5.367897

4 ETW000 [dbsloci. ,00000] *** ERROR => CONNECT failed with sql error '1017'

4 ETW000 34 5.367931

4 ETW000 [dblink ,00419] ***LOG BY2=>sql error 1017 performing CON [dblink#1 @ 419]

4 ETW000 141 5.368072

4 ETW000 [dblink ,00419] ***LOG BY0=>ORA-01017: invalid username/password; logon denied [dblink#1 @ 419]

4 ETW000 31 5.368103

2EETW169 no connect possible: "DBMS = ORACLE --- dbs_ora_tnsname = 'B3Q'"

[Former Member]

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 *****

[Former Member]

Hello Veeraraghavan,

Have you checked the notes I mentioned in my previous post.

403004 - Database connect using R3trans fails

42177 - tp and R3trans: Connect is not possible

Note 403004 would solve your problem.

Regards,

Ammey Kesarkar

[Former Member]

Dear Ammey

More accurate notes would be 400241.

kai sahi bol lo ki nahi ?

Regards

Rahul

[Former Member]

Hello Rahul,

Yes indeed 400241 could prove to be more accurate note.

Note 403004 has the following related notes

Related Notes:

400241 - Problems with ops$ or sapr3 connect to Oracle

361641 - Creating OPS$ users on UNIX

180430 - Installing the ORACLE client software for UNIX

34479 - Collective note for problems with SQL-Net V2 ORACLE

I expect one would go through them as well incase the problem persist.

Regards,

Ammey Kesarkar

[ I wonder, what could have been the root cause of this problem? ]

[Former Member]

Dear Rahul & Ammey,

I am working on the inputs which you have given. Can this problem occur if there is a restore of the database.

This is our Test system and we do product testing in this system. When we did a fresh install of the system we did a oracle repositary backup. we do restore the repositary when we need to do the testing again.

Please let me know if this would have caused the issue.

Thanks,

Veera

[Former Member]

Yes, when you perform oracle repository restore then you have to configure OPS$ mechanisam.

Cheers,

-Sunil

[Former Member]

Dear Veer

Yes the restore of the repository can give this problem . Please check the post restore steps .

Run the script oradbusr.sql as user ora<dbsid> with the following parameters:

$ sqlplus /nolog @oradbusr.sql <SCHEMAOWNER> UNIX <SAPSID> x

You will find the oradbusr.sql script on the SAPINST CD in the directory UNIX/COMMON/INSTALL.

Now you have to enter the actual password of the database schema user into table OPS$<SAPSID>ADM.sapuser:

ora<dbsid>% sqlplus /nolog

> connect / as sysdba

> insert into ops$<sapsid>adm.sapuser values

('<SCHEMAOWNER>', '<password>');

Restart sapinst, confirm the empty message box ('notfound') with 'OK' and continue the installation until you get the message 'Installation finished successfully'.

Regards

Rahul

**Please award points if help is useful ***

[Former Member]

You can also read Note 605062 - FAQ: Restore and recovery

Regards

Rahul