on 05-04-2015 8:39 AM
Hi,
i am getting an error in Sybase ASE 15.7 with ECC EHP7, whenever i start the server after half-an hour its throwing dump like
SAP SYSTEM MESSAGE: NO CONNECT TO DATABASE SESSION TERMINATED and i'm attaching all the logs please give some inputs to clear the issue
Regards,
Chida
Hi Adoni,Maria,
@Adoni you took the following actions.
1. After seeing error ocket. Socket returned error code 32 you started patching sybase correct?
2. Now during sybase patch post processing phase you have error for sapsso password correct?
@Maria - if he needs to stop/rollback patch is only option restore of backup?
Regards,
J
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi All,
1. The upgrade started at 30Th april form sybase ASE 15.7 SP131 to sybase ASE 15.7 SP 133 here are the screenshots
+ pwd
/sybase/ID1/ASE-15_0/install
for that ksh -x is i need to specify any env variables.
and there is note 2164138 - ASE: What happened to the 15.7 SP133 release?
based on note want to apply SDK for sybase how to apply?
Is there any parameters i accidently changed because in the same os i installed one more Central instance using MCOD but that is working fine.
Mainly I tried to install an ADD-ON in the syabse ecc server in the middle of the phase i noticed dump error in ADDON_CONFLICTS form that time the error is showing like it goes to dump after 20 mins whe server starts.
Please help me to clear the error.
Regards,
Chida
Hi Chida,
ksh -x only runs the details in foreground so you can see errors
Have you checked note 1701787 - SYB: Problems with SAP System Installation (Sybase ASE).
You will have to do the below step and apply open client 15.7 SP133 or wait till 11th May for SP134.
If you have already applied 15.7 SP133, you can correct the situation by downloading and applying the Open Client 15.7 SP133 release over the ASE SP133 environment.
From https://support.sap.com/software/patches/a-z-index.html Go to "S" -> "SDK for SAP ASE" -> 15.7 -> your platform
If you have not already downloaded SP133, please wait for the SP134 release which is released 11th May.
I would be concerned about the shared library error as well:
cannot open shared library libsysbcsi_core29.so
Kind Regards,
Johan
Hello,
In a Business Suite environment, the client package is the DBCLIENT, which can be downloaded from same site where ASE for Business Suite patches are downloaded.
Last one for ASE 15.7 is DBCLNT157SP17_0-20008025.SAR - Sybase ASE 15.7 FOR BUS. SUITE DBCLIENT.SAR SP17 PL0.
The procedure to patch the DBCLIENT is detailed in the SAP Note 1599814 you already consulted to do the upgrade, item 5) Update of the ODBC and JDBC drivers.
SDK is not applicable in a BS context.
The ASE has already being upgraded to SP133 according to errorlog, but the post-installation tasks couldn't be executed because of the sapsso login error. The password is asked at the very beginning of the ASEup script so nothing has been done actually in this post-installation phase.
If you don't know the sapsso password, follow this note 2008256 - How to reset master password for sapsso user and I also recommend you to read following SAP Notes to understand why the password has to be also modified in secure storage:
1796540 - SYB: Password changes with sybctrl
1706410 - SYB: Security - Changing passwords for database
users
With which OS user are you logged to execute the upgrade?
The initial problem is an unexpected lost of connection issue. If the issue still occurs after the upgrade (and it should), check the system log , network state, and your machine memory resources.
Regards,
Cris
Hi All,
1. No need to apply SDK in BS context right? and i used ROOT user to sybase patch upgrade.
2. based on note 2008256 - How to reset master password for sapsso user i got a erroe while starting the sybase server
using command ./startserver -f RUN_ID1 in sidadm. and root also.
3. according to note 1706410 - SYB: Security - Changing passwords for database users
I used command startsaop all in sidadm to start sybase ASE DB.
after i logged in using isql -U sapsa -S ID1 -X
it is asking SSO ROLE
4. 1796540 - SYB: Password changes with sybctrl
I am not aware of sybctrl how to add the files i checked in folder found dev_sybctrl is i need to add the lines .
Regards,
Chida
Hello,
The SAP Note 1599814 indicates you have to log on with user syb<sid> for the upgrade, so you will have the ASE librairies in the path, correct permissions and the correct environment variables set.
Once you are logged with correct OS user, try again the procedure detailed in note 2008256 - How to reset master password for sapsso user (I mentioned the other SAP Notes to understand why the password has to be also modified in secure storage, they cannot apply if you don't know the sapsso password.).
Ideally, we should try to keep this thread focused on the initial disconnection issue.
HTH
Cris
{For future upgrades, note that the recommended procedure to upgrade the ASE is detailed in SAP note 1982469 - SYB: Updating SAP ASE with saphostctrl / sapdbctrl.}
Hi All,
Thanks for your reply, i reread the note 1599814 and login to sybsid executed the ./ASEup.sh -DREINSTALL
Is it correct method what i did? and i didnot get any information in websites regarding libsybcsi_core29.so why i'm getting this issue
If i want to start sybase ASE using command ./startserver -f RUN_SID is i need to set any environmental variables in sidadm?
Regards,
Chida
Hi Chida,
1. User sybsid has the correct env variables
2. On one of your working system search for location of the file libsybcsi_core29.so and perhaps as workaround you can copy it to directory on your non working system /sybase/ID1/ASE-15_0/bin/dataserver
3. type in command env as user sybsid and paste results here also.
4. if you run command whoami your current user should be sybsid for install.
Kind Regards,
Johan
Hi,
Thanks for replying All
1. The ENV of sysid1 is
[sybid1@tamc bin]$ env
TERM=xterm
REMOTEHOST=192.168.1.1
HOME=/sybase/ID1
PATH=/sybase/ID1/ASE-15_0/jobscheduler/bin:/sybase/ID1/ASE-15_0/bin:/sybase/ID1/ASE-15_0/install:/sybase/ID1/OCS-15_0/bin:/usr/lib64/qt-3.3/bin:/usr/local/bin:/bin:/usr/bin:/usr/sap/ID1/SYS/exe/uc/linuxx86_64:/usr/sap/ID1/SYS/exe/run:/home/id1adm:.
SHELL=/bin/csh
MAIL=/var/spool/mail/sybid1
LOGNAME=sybid1
HOSTTYPE=x86_64-linux
VENDOR=unknown
OSTYPE=linux
MACHTYPE=x86_64
SHLVL=2
PWD=/sybase/ID1/ASE-15_0/bin
USER=sybid1
GROUP=sapsys
HOST=tamc
HOSTNAME=tamc
LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=01;05;37;41:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lz=01;31:*.xz=01;31:*.bz2=01;31:*.tbz=01;31:*.tbz2=01;31:*.bz=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.rar=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.axv=01;35:*.anx=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=01;36:*.au=01;36:*.flac=01;36:*.mid=01;36:*.midi=01;36:*.mka=01;36:*.mp3=01;36:*.mpc=01;36:*.ogg=01;36:*.ra=01;36:*.wav=01;36:*.axa=01;36:*.oga=01;36:*.spx=01;36:*.xspf=01;36:
G_BROKEN_FILENAMES=1
SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass
KDEDIRS=/usr
KDE_IS_PRELINKED=1
LANG=en_US.UTF-8
LESSOPEN=|/usr/bin/lesspipe.sh %s
QTDIR=/usr/lib64/qt-3.3
QTINC=/usr/lib64/qt-3.3/include
QTLIB=/usr/lib64/qt-3.3/lib
SAPSYSTEMNAME=ID1
DIR_LIBRARY=/usr/sap/ID1/SYS/exe/run
RSEC_SSFS_DATAPATH=/usr/sap/ID1/SYS/global/security/rsecssfs/data
RSEC_SSFS_KEYPATH=/usr/sap/ID1/SYS/global/security/rsecssfs/key
rsdb_ssfs_connect=1
INCLUDE=/sybase/ID1/OCS-15_0/include:
LIB=/sybase/ID1/OCS-15_0/lib:
SAP_JRE7_32=/sybase/ID1/shared/SAPJRE-7_1_027_32BIT
SAP_JRE7=/sybase/ID1/shared/SAPJRE-7_1_027_64BIT
SAP_JRE7_64=/sybase/ID1/shared/SAPJRE-7_1_027_64BIT
SYBASE_OCS=OCS-15_0
SYBASE=/sybase/ID1
SYBASE_ASE=ASE-15_0
SYBROOT=/sybase/ID1
SYBASE_JRE_RTDS=/sybase/ID1/shared/SAPJRE-7_1_027_64BIT
SYBASE_WS=WS-15_0
dbms_type=syb
dbs_syb_schema=SAPSR3
dbs_syb_server=tamc
dbs_syb_dbname=ID1
dbs_syb_port=4901
LC_ALL=en_US.UTF-8
2. What i understand 2nd point is can i copy form other sybase DB installed systems sybase/SID/ASE-15_0/bin/dataserver to /sybase/ID1/ASE-15_0/bin/dataserver is it work?
3. Why the No conected to database session terminated. I tried to install on ADD-ON Named called persos200 before i checked all the prerequisites using note 1776739 and using saint in 000-DDIC i tried to install under background mode after sometime when i try check the status i got dump error No conected to database session terminated and its in the phase on ADDON_CONFLICTS Phase.
Even i tried in dialogue mode also same error after that i rest queue OCS_RESET_QUEUE in SM37. my view is it a cause for that dump error.
Regards,
Chida
Hello Chida,
For the libsybcsi_core29 load issue, try by sourcing sybase ASE environment script:
SYBASE.csh or SYBASE.sh depending on your shell (echo $SHELL to check which are you using).
According to your last post, the initial issue reported here started after you installed an ADD-ON, which let me think that this could explain why we have no evidence of an ASE problem so far.
This is just a suggestion, but from my point of view you need to focus in your ADD-ON installation to try to clarify if the installation went wrong. Maybe the Software Logistics SNC could help with this: http://scn.sap.com/community/it-management/alm/software-logistics
Regards
Cris
Hi Adoni,
Also have you done the following.
1. Stopsap including DB's
2. cleanipc INSTANCENUMBER remove (do this once for each instance number)
3. ps -ef |grep sap ps-ef |grep SYB see if anything is still running
4. If all is cleaned and stopped nothing is running please restart SAP
5. If there is still error run R3trans -d and attach trans.log here.
Johan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi All
1. How was the SAP system or the ASE stopped/started ?
Could you please clarify if the ASE is up and running when you get the message
SAP SYSTEM MESSAGE: NO CONNECT TO DATABASE SESSION TERMINATED ?
When the SAP server starts using startsap all it starts fine it works fine after 20 minutes the gui-logon will show the error message
SAP SYSTEM MESSAGE: NO CONNECT TO DATABASE SESSION TERMINATED
even it wont work to login sybase isql -U sapsa -S SID -X throws error
2. actually i did a sybase patch upgrade in that post installation phase it's prompting sapsso password but its not working even i tried alter locklogin but its not workig and the post inst phase is still pending. only sapsa and sapsr3 is working.
3.Please find the r3trans -d logs below.
Regards,
Chida
Hi Adoni,
So you are actually in the midst of an upgrade what version of ASE and what version patch install are you running?
Did you follow patch procedure as such:
http://scn.sap.com/docs/DOC-63856
What do you see in log /Sybase/<SID>/log/ directory.?
Regards,
Johan
Hi All,
The sybase ASE 15.0.7 and i used the below note to did but in the post installation actvity
./ASEup.sh -DNO_INSTALL it's asking the sapsso password. then i give the master password its throwing error.
1599814 - SYB: Installing Service Packs for SAP Sybase ASE 15.7 (UNIX + Linux)
The reason why i did patch upgrade to resolve session terminated no connect to database
Regards,
Chida
Hi All
I checkd the note before and i put instead of -psa i used -psapsso but the reason is i'm unable to start the sybase server using commands like ./startserver only DB is up and runnig when i uses the startsap db
Is i accidently changed any parameters and any environmental variables i need to specify.
Regards,
Chida.
Hi,
1. Stop DB
2. Edit RUN_ID1.sh - you have already done this
3. Start script RUN_ID1.sh to output to screen i.e.
ksh -x
RUN_ID1.sh
When it outputs to screen look for line like this:
Process the script so it outputs to your screen then look like above take that password and logon as SAPSSO change to new password as per KBA article.
REMEMBER to stop currently running DB first.
Kind Regards,
Johan
Hello,
So far I cannot see any evidence of a password issue with sapsso that could justify to change it.
Keep in mind, and this is very important, that running ASE on a Business Suite environment has specific procedures that may not be the same as in an ASE standalone installation, i.e changing logins password. The passwords for ASE logins are stored 1) in the secure storage used by the SAP Application Server and SAP tools and 2) in the ASE.
I'd recommend to not proceed to change it if you're not familiar with this.
In the other hand, there is no evidence of an ASE issue so far, and I don't think a patch upgrade will solve your ODBC connection issue. Besides, you are already on the last available patch for ASE for Business Suite:
Adaptive Server Enterprise/15.7/EBF 24258 SMP SP133 /P/x86_64/Enterprise Linux/ase157sp133x/3921/64-bit/FBO/Thu Apr 9 04:36:59 2015
In all the dev_w* log we can see the problem is that the connection from the SAP system to ASE was established, i.e:
C dbsybslib.dll patch info
C SAP patchlevel 0
C SAP patchno 114
C Last SYBASE DBSL patchlevel 0
C Last SYBASE DBSL patchno 114
C Last SYBASE DBSL patchcomment SYB IQ: performance enhancement for LOAD statement (2130587)
C spid 14 comm rd ODBC
C spid 28 unc rd ODBC
C Driver: Adaptive Server Enterprise (ANSI) Driver release: 15.7.0.1330
C Driver full version: SAP ASE ODBC Driver/15.7/SP133 PL/P/x86_64/Linux/drvmain/Build 1330/64-bit/Normal/Tue Mar 31 UTC 02:54:21 2015/SQLLEN8
C Driver uses SQLLEN8
C dbs/syb/cache_size: 300
C GetServerInfo version: Adaptive Server Enterprise/15.7/EBF 24258 SMP SP133 /P/x86_64/Enterprise Linux/ase157sp133x/3921/64-bit/FBO/Thu Apr 9 04:36:59 2015
C GetServerInfo release: 15.7.0.133
C GetServerInfo architecture: x86_64
C GetServerInfo edition: P
C GetServerInfo byte width: 64 bit
C DbSlConnect hdl: 0
C trace file set
B Connection 0 opened (DBSL handle 0)
M
M Mon May 4 13:51:59 2015
M ThDbConnect: db_connect o.k.
but then the connection is lost :
C (30046) [08S01] [SAP][ASE ODBC Driver]Connection to the server has been lost. Connection died wh
C ile writing to socket. Socket returned error code 32
I'd first check the system log and network state, and I'll add, your machine memory resources.
HTH
Cris
Hello,
The logs provided are not very helpful I'm afraid: ASE log shows ASE is up and running, Backup Server log shows an error that has occurred intermitenly since February, can be just ignored (it looks like there is an attempt to start it when it is already started) - note a Backup Server that cannot start won't prevent the dataserver to start-, and the startdb.txt starts before the ASE start (at 10:10:33 and ASE starts at 10:10:34) which could explain the error 'ASE instance not available'.
How was the SAP system or the ASE stopped/started ?
Could you please clarify if the ASE is up and running when you get the message
SAP SYSTEM MESSAGE: NO CONNECT TO DATABASE SESSION TERMINATED ?
Is the SAP system available or it is about one or more worker processes disconnected?
Could you please also attach the sapstartsrv.log and the dev_w* log of the wp involved?
Thanks
Regards,
Cris
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI,
If it is not an already running version of the DB. please check the following note.
Note 1928596:SAP SYBASE ASE : How to remove a ghost backup server process ?
Also to test if the port is available telnet into the port.
Kind Regards,
Johan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi All,
1. I already followed the above all notes but no solution. how come backup server is running already even i follw the below notes if any port issue how do i change port number in interfaces and services files.
1928596 - SAP SYBASE ASE : How to remove a ghost backup server process ?
1920535 - Net-Library routine sybnet_listen() failed in srv__start_net when starting Backup Server
1819873 - SYB: SYBASE ASE 15.7 does not start on platform
2. It use to start while using command startsap db
whenever i iuse to start sybase server using ./startsrever -f RUN_SID (cd /sybase/sid/ASe-15/install)
[root@ install]# ./startserver -f RUN_ID1
[root@ install]# /sybase/ID1/ASE-15_0/bin/dataserver: error while loading shared libraries: libsybcsi_core29.so: cannot open shared object file: No such file or directory
3., and i am unable to login with sapsso and sa user to login. only sapsa nad sapsr3 is working i tried to change the passwords againg it is throwing sso_role error. i tried the note 2008256 - How to reset master password for sapsso user
but it throwing the above startserver error.
startdb.log
------------------------------ Mon May 4 13:51:47 IST 2015
LOGFILE FOR STARTING SYBASE ASE
starting database ID1 ...
------------------------------ Mon May 4 13:51:47 IST 2015
checking required environment variables
------------------------------ Mon May 4 13:51:47 IST 2015
check if Sybase ASE processes are running
ASE instance already running (pid of engine #0 is: 20076 )
------------------------------ Mon May 4 13:51:47 IST 2015
check if Sybase Backupserver is running
Backupserver instance already running (pid of backupserver is: 6862 )
Database already running
please let you suggest solution to clear the issue.
Regards,
Chida
Hello,
I am not familiar with ECC EHP7, but I am trying to understand the problem from the ASE point of view. From the logs I see that ID1 database server starts successfully without any issues, while ID1_BS (the backup server) sometimes fails to start because the instance already is running. I am afraid I cannot understand dev_disp.txt
In my previous comment I asked for the ID1 log before the restart, because I understand you have some connectivity issue and maybe there we can see a message explaining what happened.
Regards,
Kimon
Hi All
Ples efind the dev_w0 attached file.
Also after you stopped SAP before restart it.
Did you stop service named SYBBCK_ID1_bs before starting SAP again?
before restart the OS i followed the note to kill the backup server 1928596 - SAP SYBASE ASE : How to remove a ghost backup server process ? used showserver command to check the SYBBCK_ID1_bs and killed using kill PID-number
after that i checked using ps -eaf | grep sybmultbuf.
[root@tamc install]# showserver
F S UID PID PPID C PRI NI ADDR SZ WCHAN STIME TTY TIME CMD
4 S root 6862 6861 0 80 0 - 6289 poll_s 10:20 pts/4 00:00:00 /sybase/ID1/ASE-15_0/bin/backupserver -e/sybase/ID1/ASE-15_0/install/ID1_BS.log -N25 -C20 -M/sybase/ID1/ASE-15_0/bin/sybmultbuf -SID1_BS.
Hello,
ASE sa login is locked in a Business Suite context, and under normal circunstances, you don't need to unlock it. So it is expected you cannot connect with it, use sapsa instead.
The reason for which the ./startserver failed is due to the OS user profile and its environment variables.
Anyway, ASE data server is up and running.
There is no login failed errors, so until now, there is no reason to change the password of sapsso.
Backup Server is totally unrelated here.
The problem is that the connection from the SAP system to ASE was established then lost :
C (30046) [08S01] [SAP][ASE ODBC Driver]Connection to the server has been lost. Connection died wh
C ile writing to socket. Socket returned error code 32
Check the system log and network state.
Also, has something changed in your environment recently?
Cris
Hello,
The id1.txt is clear and it contains the messages for an ASE startup. Probably the real error message is before this startup (in another file?). I think you should send these older messages.
The id1_bs.txt says that backup server could not start because its port was occupied, probably you tried to start an instance already running.
Regards,
Kimon
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
88 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.