11-11-2005
Normally -- well thought out high availability systems have both a failover box and a backup site - a "sister" site with the same species of box that would allow you to run your mission critical app until the flood waters receded.
It's not even remotely practical to try something like that - how would you capture the registers? The PC (program counter) register would not mean anything, for example, going from a Sparc station to Linux running on a PC, for example.
If this were a reasonable choice, wouldn't you expect that big companies with mission critical apps would be doing something like this routinely? No company does a cross-platform thing like this - AFAIK.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Is it possible to migrate a UNIX program and use it in a NetWare or Windows 2000 network? I have a client that must have one of those two operating systems for the new program that they want. However, they've been using an older UNIX program for about 7 years and they want to be able to refer to... (7 Replies)
Discussion started by: refram
7 Replies
2. UNIX for Advanced & Expert Users
hi,
is there any tool that i can use to update my scripts (SH scripts)
form Unix to linux.
please mention any useful websites.
thanx in advance (2 Replies)
Discussion started by: omran
2 Replies
3. UNIX for Advanced & Expert Users
Hi all,
Would appreciate advise on my situation.
Currently server A is in production. Server A takes in data from Server X, does some processing and send to server Y. We are going to develop a different system in server B, something like an enhanced version of A. Server A will be retired once... (2 Replies)
Discussion started by: new2ss
2 Replies
4. UNIX for Dummies Questions & Answers
how can i migrate a running process in unix to another node for load balancing? (3 Replies)
Discussion started by: aisalihu
3 Replies
5. UNIX for Advanced & Expert Users
how can i migrate a running process in unix to another node? (1 Reply)
Discussion started by: aisalihu
1 Replies
6. Shell Programming and Scripting
Hi,
We are doing migration from DB2 to Teradata.
There are couple of things involving in the project.
Please see below following order
Autosys-Jil script
Profile script
Category1
Teradata script
Data stage job script
Tera data script
Export files script..
Like that we have 10000... (1 Reply)
Discussion started by: onesuri
1 Replies
7. UNIX for Advanced & Expert Users
We are about to get a new server and I need to prepare for migration to the new one. This will be my first migration so I'm sure I will be learning alot.
My current server is running CentOS 4.x and I want to move to a sever running Centos 5.x , thought it would make things easier.
The old... (1 Reply)
Discussion started by: mcraul
1 Replies
8. Red Hat
Hello experts,
My doubt is, shall we move process from one node to another node..?
This will be need when the cpu running on max load.
Thanks. (1 Reply)
Discussion started by: srigias
1 Replies
9. AIX
We have a 2 node oracle rac cluster one node is in frame 1 and other is in frame 2
Now,because of some hardware failure(processor card and cable) in frame 1 we will failover database services from lpar in frame 1 to lpar(oracle rac cluster node2) in frame2 and the entire replacement of hardware... (9 Replies)
Discussion started by: admin_db
9 Replies
10. AIX
I'm New to AIX / VIOS
We're doing a FC switch cutover on an ibm device, connected via SAN.
How do I tell if one path to my remote disk is lost? (aix lvm)
How do I tell when my link is down on my HBA port?
Appreciate your help, very much! (4 Replies)
Discussion started by: BG_JrAdmin
4 Replies
core(4) Kernel Interfaces Manual core(4)
NAME
core - format of core image file
DESCRIPTION
The HP-UX system writes out a file containing a core image of a terminated process when certain signals are received (see signal(5) for the
list of reasons). The most common causes are memory violations, illegal instructions, floating point exceptions, bus errors, and user-gen-
erated quit signals. The core image file is called and is written in the process's working directory (provided it is allowed by normal
access controls). A process with an effective user ID different from its real user ID does not produce a core image.
The file contains sufficient information to determine what the process was doing at the time of its termination. Core file contents con-
sist of objects that represent different segments of a process. Each object is preceded by a data structure, and each data structure
describes the corresponding object following it. The structure is defined in and includes the following members:
The space and addr members specify the virtual memory address in the process where the described object began. The len member is the
length of the object in bytes.
The following possible values for type are defined in
Process data as it existed at the time the core image was created.
This includes initialized data, uninitialized data, and the heap at the time the core image is generated.
A compiler-dependent data structure containing the exec data structure,
the magic number of the executable file, and the command (see the declaration of the structure in
The version number of the core format produced.
This number changes with each HP-UX release where the core format itself has changed. However, it does not neces-
sarily change with every HP-UX release. can thus be easily used by core-reading tools to determine whether they
are compatible with a given core image. This type is expressed by a four-byte binary integer.
The null-terminated version string associated with the kernel
at the time the core image was generated.
An architecture-dependent data structure
containing per-process information such as hardware register contents. See the declaration of the structure in
Process stack contents at the time the core image was created.
Objects dumped in a image file are not arranged in any particular order. Use information to determine the type of the object that immedi-
ately follows it.
SEE ALSO
adb(1), coreadm(1M), coreadm(2), setuid(2), crt0(3), end(3C), signal(5).
core(4)