Unix/Linux Go Back    

HP-UX HP-UX (Hewlett Packard UniX) is Hewlett-Packard's proprietary implementation of the Unix operating system, based on System V.

Database replication process stopped in server


Thread Tools Search this Thread Display Modes
Old Unix and Linux 08-12-2016   -   Original Discussion by anaigini45
anaigini45's Unix or Linux Image
anaigini45 anaigini45 is offline
Registered User
Join Date: Oct 2009
Last Activity: 18 January 2018, 9:12 AM EST
Posts: 102
Thanks: 4
Thanked 0 Times in 0 Posts
Database replication process stopped in server


A database (Oracle) replication process was executed by the DBA team in one server (serverX). However, this replication process gets terminated, and there are no errors in the replication log. But there is error in the OS log files (syslog.log) :

Aug  8 16:51:47 L28dre02 sshd[10388]: subsystem request for sftp 
Aug  8 17:11:15 L28dre02 vmunix:
Aug  8 17:11:15 L28dre02 vmunix: Pid 11582 was killed due to failure in 
writing the signal context- possible stack overflow.
Aug  8 18:45:31 L28dre02 sshd[17209]: Accepted keyboard-interactive/pam 
for oracle from port 50190 ssh2

From the error "stack overflow", I found that the solution was to edit the value of the parameter 'PTHREAD_DEFAULT_STACK_SIZE'.
However, I am not sure how/where to locate the file in the server.

Another article I read says that change that parameter value in the file :

However, when I run echo $SYBASE in the server to look for the path, the error is :

L28dre02:/home/oracle:INTDB> echo $SYBASE
sh: SYBASE: Parameter not set.

How do I locate this parameter and change the value?

***The replication application used is 'DBVisit'.
Sponsored Links
Old Unix and Linux 08-17-2016   -   Original Discussion by anaigini45
Peasant's Unix or Linux Image
Peasant Peasant is offline Forum Advisor  
Registered User
Join Date: Mar 2011
Last Activity: 20 January 2018, 11:58 PM EST
Posts: 1,111
Thanks: 32
Thanked 332 Times in 286 Posts
Setup the profile of the user using ulimit -s to a higher value.
Possibly one suggested in your database vendor documentation.

If ulimit fails to set to <value>, you will have to adjust the maxssize kernel parameter, then use ulimit.

Be sure to read the manual pages of ulimit and maxssize parameter (this is what i like about hpux, man <kernel parameter> is goldenLinux )

Please for future note specify your shell (shell of the user the database processes runs under) and exact hpux version.
Folks here can be more exact in helping you with that information upfront.

I have not used the variable mentioned here so i cannot comment on that, give it a shot with standard tools mentioned above.

Hope that helps
Sponsored Links

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Linux More UNIX and Linux Forum Topics You Might Find Helpful
Thread Thread Starter Forum Replies Last Post
Killing A Stopped Process cokedude UNIX for Advanced & Expert Users 3 05-10-2010 08:57 PM

All times are GMT -4. The time now is 06:49 AM.