- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: SAP transport abort sig received from OS
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
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
тАО10-30-2000 05:56 AM
тАО10-30-2000 05:56 AM
SAP transport abort sig received from OS
first I have to apologize for the misposting of my last question, an obvious system administration issue in the database section. :-/
So I was lucky to have an immediate response from the system wizards despite.
Seems they scour every field.
Now to my database question.
We have Oracle/SAP DBMS running on the HP-UX boxes.
From the dba I received a call inquiring about an error reported from a transport.
I hear they are doing lots of transports in SAP. Somehow they have to keep their 6+ replication servers busy to justify the spendings. ;-)
The prog seems to be "tp" and the error it threw is roughly:
(heard it only cited on the phone)
"tp: terminate on signal 6 from OS"
Well, from "kill -l" I know that SIG 6 corrosponds to an Abort signal on our HP-UX boxes.
Has anyone an idea who or what may have sent the abort signal to the transport process?
Is there a way to trace it in retrospect?
I haven't yet come to know all of the SAP logfiles.
Seems they keep me ignorant here.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-30-2000 06:24 AM
тАО10-30-2000 06:24 AM
Re: SAP transport abort sig received from OS
Difficult problem. A SIGABRT should have caused the tp process to core dump. So by examining the core (your developers/DBA's should be able to do this also) you should get a much better idea what caused it - if you can find the core file!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-08-2000 05:17 AM
тАО11-08-2000 05:17 AM
Re: SAP transport abort sig received from OS
sorry, for the late response.
I simply lost this thread.
Meanwhile the issue is obsolete, and the error has never appeared ever since.
The core file (if it ever existed) may have been eradicated by my filesystem core scanner run as a cronjob.
Since we have no developers here luckily core files are dumped only every now and then when an application misbehaves.
BTW, does it work to prevent core files by creating a symbolic link to /dev/null from a 0-Byte touched core file in a directory?
Somewhere in this forum I also noticed the hint to make it read-only.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-08-2000 05:25 AM
тАО11-08-2000 05:25 AM
Re: SAP transport abort sig received from OS
To prevent a core file from being created, you can touch a file named 'core' in the directory or directories in which you don't want to have them created. Change the permissions to read-only and you will leave only a 0-byte file.
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-08-2000 07:15 AM
тАО11-08-2000 07:15 AM
Re: SAP transport abort sig received from OS
rc/1000=6: The target system is not defined, e.g. rc=6004 means that the R3trans export wrote warnings, but the target system was not defined in the TPPARAM transport profile.
Hope help you
Ess
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-08-2000 07:16 AM
тАО11-08-2000 07:16 AM
Re: SAP transport abort sig received from OS
rc/1000=6: The target system is not defined, e.g. rc=6004 means that the R3trans export wrote warnings, but the target system was not defined in the TPPARAM transport profile.
Hope help you
Ess
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-08-2000 07:16 AM
тАО11-08-2000 07:16 AM
Re: SAP transport abort sig received from OS
rc/1000=6: The target system is not defined, e.g. rc=6004 means that the R3trans export wrote warnings, but the target system was not defined in the TPPARAM transport profile.
Hope help you
Ess