Memory allocation failure w/ cross-platform load

[unknown]

Hi Folks,

I've got a dump file from a 64-bit Solaris 12.5.3 version of
Sybase. I'm trying to load it on a 32-bit 12.5.3 Windows
install (actually, 2 different installs). It gives me an
error mentioning a memory allocation problem (but I'm
wondering if the dump file is corrupt).

The source is:
12.5.3/EBF 13325 ESD#7/P/Sun_svr4/OS
5.8/ase1253/1951/64-bit/FBO/Fri Mar 24 11:00:22 2006

The target is:
12.5.3/EBF 13331 ESD#7/P/NT (IX86)/OS
4.0/ase1253/1951/32-bit/OPT/Fri Mar 24 02:17:56 2006

The error is:
Backup Server: 1.1.2.26: Memory allocation failed in
bs_remap_runlist for a
M_IO_LIST allocation. This DUMP or LOAD session must exit.
Msg 8009, Level 16, State 1:

Now the troubleshooting guide says the machine in this
situation is likely short on virtual memory and you should
shut down unnecessary processes. Well, the trouble is, this
machine is already pretty stripped down to the bare stuff
needed (all it does is run Sybase) and it's got several
hundred MB of available RAM and the page file is only about
half the allowed size.

So, do I just have a bad dump file or can anyone suggest
something else to try?

JMCraig

[Manish Negandhi]

Post by unknown
Hi Folks,
I've got a dump file from a 64-bit Solaris 12.5.3 version of
Sybase. I'm trying to load it on a 32-bit 12.5.3 Windows
install (actually, 2 different installs). It gives me an
error mentioning a memory allocation problem (but I'm
wondering if the dump file is corrupt).
12.5.3/EBF 13325 ESD#7/P/Sun_svr4/OS
5.8/ase1253/1951/64-bit/FBO/Fri Mar 24 11:00:22 2006
12.5.3/EBF 13331 ESD#7/P/NT (IX86)/OS
4.0/ase1253/1951/32-bit/OPT/Fri Mar 24 02:17:56 2006
Backup Server: 1.1.2.26: Memory allocation failed in
bs_remap_runlist for a
M_IO_LIST allocation.  This DUMP or LOAD session must exit.

Few possibilities...
(1) your dump might be corrupt , you might want to take new dump and
try to load it
(2) If you used ftp to transfer dump files from Solaris to Windows,
you need to use binary mode while transferring file, if you have not
already done so, you might want to ftp dump files again with binary
mode and check if load works...

-HTH
Manish Negandhi
[TeamSybase]

[A. M.]

Post by unknown
I've got a dump file from a 64-bit Solaris 12.5.3 version of
Sybase. I'm trying to load it on a 32-bit 12.5.3 Windows
install (actually, 2 different installs). It gives me an
error mentioning a memory allocation problem (but I'm
wondering if the dump file is corrupt).

How did you come about the dump file and how did
you transfer it? Check its size against the original
(if you have it). Alternately, try loading it on
a Solaris server running ASE. If backup server
complains there, the file is corrupt.

Post by unknown
Now the troubleshooting guide says the machine in this
situation is likely short on virtual memory and you should
shut down unnecessary processes. Well, the trouble is, this
machine is already pretty stripped down to the bare stuff
needed (all it does is run Sybase) and it's got several
hundred MB of available RAM and the page file is only about
half the allowed size.
So, do I just have a bad dump file or can anyone suggest
something else to try?

Check the file first.

-am © MMVIII

[unknown]

Well, the advice about verifying the file was right on the
money. Unfortunately, I had to rely on someone else sending
it to me and I didn't know how it had been handled--not
precisely.

Today, using a web conferencing tool, we checked the file
sizes (the one I had was 3 MB too big--sounds like it had
gotten <cr> characters added). Then we worked together to
transfer the file (I ensured that he used binary mode).

The file is loading now and no complaints about memory
allocation problems. Next time I see the backup server
complaining about memory allocations that failed (when there
didn't seem any sensible reason why they would), I'll check
the file first!

Thanks,

JMCraig