- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- ./tprmalim00.ksh[198]: 10563 Killed and code=137
Categories
Company
Local Language
Forums
Discussions
Knowledge Base
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Knowledge Base
Forums
Discussions
- Cloud Mentoring and Education
- Software - General
- HPE OneView
- HPE Ezmeral Software platform
- HPE OpsRamp
Knowledge Base
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-11-2012 05:40 AM
05-11-2012 05:40 AM
Hi.
we are using
version:
HP-UX hva03ads B.11.31 U ia64 0291095592 unlimited-user license
compiler:
Hewlett-Packard Company - 41 - HP C/aC++ Version A.06.25
- when i execute shell script tprmalim00.ksh with parameters. it is showing 10563 killed and exit code=137.
- Actually this script executing one binary file with some parameters. finally the binary file will update the table.
version_encours/cmd --> tprmalim00.ksh -p NB_INC_TOT
Environnement oracle
====================
ORACLE_HOME : /logiciel/oracle/client_10204
ORACLE_SID : sqlnet_10204
TNS_ADMIN : /logiciel/oracle/tnsadmin
NLS_LANG : american_america.al32utf8
Nom du listener : LISTENER
+------------------------------------------------------------+
| Programme |
+------------------------------------------------------------+
| Repertoire : .
| Script ksh : tprmalim00.ksh
| Parametre(s) : -p NB_INC_TOT
+------------------------------------------------------------+
| Serveur traitement |
+------------------------------------------------------------+
| Serveur : hprx3710
| Utilisateur : sop_btch
| Home : /sopre701/sop/sop_btch
+------------------------------------------------------------+
| Serveur sgbd |
+------------------------------------------------------------+
| TNS : sopaut10_re7
| Utilisateur : sop_adm
+------------------------------------------------------------+
[info] tprmalim00.ksh -----------------------------------
[info] tprmalim00.ksh DEBUT 11/05/12 14:18:49 - PID 10523
[info] tprmalim00.ksh -----------------------------------
[info] tprmalim00.ksh ENV - uid=121(sop_btch) gid=110(sop) on hprx3710
[info] tprmalim00.ksh -----------------------------------
[info]
[info] ______________________________________________________________________
[info] 11/05/12 14:18:49, tprmalim00.ksh DEBUT calcul de la valeur d'un prm de la TK10_PRM
[info] tprmalim00.ksh . Parametre : NB_INC_TOT
[info] tprmalim00.ksh . Niveau de log : normal
[info] tprmalim00.ksh . Fichier de trace : /dev/null
[info]
./tprmalim00.ksh[198]: 10563 Killed
[info]
[info] 11/05/12 14:18:49, tprmalim00.ksh FIN calcul de la valeur d'un prm de la TK10_PRM - code=137
[info] ______________________________________________________________________
[info]
[info] tprmalim00.ksh -----------------------------------
[info] tprmalim00.ksh FIN 11/05/12 14:18:49 code=137
[info] tprmalim00.ksh -----------------------------------
kindly help on this.
Solved! Go to Solution.
- Tags:
- SIGKILL
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-11-2012 12:10 PM - edited 05-22-2012 09:34 PM
05-11-2012 12:10 PM - edited 05-22-2012 09:34 PM
Re: ./tprmalim00.ksh[198]: 10563 Killed and code=137
>10563 killed and exit code=137.
1) Either somebody did a SIGKILL on your process. You need to track that person down.
2) Or you have dld unsats and dld printed a nice message and then killed itself.
If the latter, you need to track down the stderr output.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-22-2012 09:10 PM