Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from Salman on May 17 at 4:55 PM Dear Srinivas,
I appreciate your prompt reply to my issue. Yes, the database is running and I'm able to connect via SQL Net with SYS & SAPSR3 users. After doing a lot of reading in various threads posted on this subject, I decided to add environment variable dbms_type = ora. This has started giving a different issue:
Below is a brief log of likely the cause of problem in dev_w0:
*** ERROR => OCI-call 'OCIServerAttach' failed with rc=12154
[dboci.c 4447]
*** ERROR => CONNECT failed with sql error '12154'
[dbsloci.c 11175]
Here's full log of dev_w0:
| | | ---------------Original Message---------------
From: Salman
Sent: Tuesday, May 17, 2016 3:04 PM
Subject: disp+work.exe --- Stopped suddenly
Dear SAP experts,
I'm new to SAP Basis Administration. I have been reading threads about the above issue and quite honestly I'm confused after reading too much info. Not sure what to do. I'm also one of victims of "sap dispatcher process" where it stops suddenly though nothing apparently is played with it.
PROBLEM SCENARIO
My SAP is down since last night which started after a system crash. Before that, system was working 100% fine. Also, please note, SAP was working correct without any variables such as DBMS_TYPE as I'm pretty sure about it. I never saw this type of environment variable even when the system was working fine. I don't understand why this problem started happening all of a sudden and it's so strange to see this error??? However, I did make a change to default profile parameter "login/no_automatic_user_sapstar" and set it to 1 from 0 (just to check out how it behaves).
I need your suggestion and help here. Here's my current environment.
SAP: ECC6 EHP4 IDES
Windows: Windows Server 2008 R2 (64bit)
Oracle: 10.0.2.0.4
Here's the log of dev_w0 file: |
| Reply to this email to post your response. __.____._ |    _.____.__ |
