Could not fork a virtual processor: errno = 12

Hello The past week I had a problem with a memory bank of my SUN450 with solaris 8 The problem is already fixed, but I try to rebuilt a secondary instance with HDR y it is no possible, the steps are the same i had used alltimes: onstape -s -L 0 in the primary server in stanard mode ontape -p in the secondary as cold restore The online.log repors: Could not fork a virtual processor: errno = 12 I have another instance for probes, that is almost the same, and I can put online this instance with no problems, but the secondary doesen´t want to wake up I´m using IDS 9.30FC7 ¿Any idea? Thank tou very much in advance Hugo

Hi, hmm. Errno 12 on Solaris means "Not enough space". The question is, what resource is short. Most probably it is memory ... Can you check, how much physical memory you now have available on the machine ? (e.g. "/usr/platform/<platform-name>/sbin/prtdiag -v") Then check your onconfig parameters (BUFFERS, SHMVIRTSIZE, possibly NETTYPE with "ipcshm" values). If that doesn't help, try to bring up the secondary in standard mode with "-iv" (i.e. "oninit -iv", just for a test). Maybe this will show more output and give a better hint as to where the resource shortage is. Regards, Martin -- Martin Fuerderer IBM Informix Development Munich, Germany Information Management forum.subscriber@iiug.org wrote on 26.01.2005 17:47:44: > Hello > > The past week I had a problem with a memory bank of my SUN450 with solaris 8 > The problem is already fixed, but I try to rebuilt a secondary instance with HDR y it is no possible, the steps are the same i had used alltimes: > > onstape -s -L 0 in the primary server in stanard mode > ontape -p in the secondary as cold restore> > The online.log repors: > > Could not fork a virtual processor: errno = 12 > > I have another instance for probes, that is almost the same, and I can put online this instance with no problems, but the secondary doesen´t want to wake up > > I´m using IDS 9.30FC7 > > ¿Any idea? > Thank tou very much in advance > > Hugo > > >

Thanks Folks The problem is now solved; I think it was a daemon, not a Solaris daemon, a daemon from the hell ;-) Very strange: to verify if was a memory or configuration problem, I restore the instance with ontape –r, ¡¡¡ oh surprise !!! it works (with the same configuration, noting change) after this it try again with ontape –p, and again ¡¡¡ oh surprise !!! it works. Thinking in a lan problem, I change the server from a fiber switch to a cooper switch. After all this everything was like a sunny day and the restore of HDR was a piece of cake, with the same procedure follow before Greetings Hugo

Thanks everybody The problem is now solved; I think it was a daemon, not a Solaris daemon, a daemon from the hell ;-) Very strange: to verify if was a memory or configuration problem, I restore the instance with ontape –r, ¡¡¡ oh surprise !!! it works (with the same configuration, noting change) after this it try again with ontape –p, and again ¡¡¡ oh surprise !!! it works. Thinking in a lan problem, I change the server from a fiber switch to a cooper switch. After all this everything was like a sunny day and the restore of HDR was a piece of cake, with the same procedure follow before Greetings Hugo