How to set stack for Oracle's user?

Hi all!

I've got a problem.
Primary: Sun Sparc V890, 64bit
Standby: HP-Proliant ML 350, 64bit

In the machine that I've got configured physical standby database, the alert_log_file point me one error:

Sat Feb 28 00:40:08 2009
ORA-00202: control file: '/u01/app/oracle/datafile/controlstd01.ctl'
ORA-27047: unable to read the header block of file
Additional information: 2

And I could not startup mount this standby database. After a time, I found this error caused by

$ ulimit -s
10240
$ ulimit -a
time(seconds)        unlimited
file(blocks)         unlimited
data(kbytes)         unlimited
stack(kbytes)        10240
coredump(blocks)     unlimited
nofiles(descriptors) 256
vmemory(kbytes)      unlimited
$ ulimit -Ha
time(seconds)        unlimited
file(blocks)         unlimited
data(kbytes)         unlimited
stack(kbytes)        unlimited
coredump(blocks)     unlimited
nofiles(descriptors) 65536
vmemory(kbytes)      unlimited

But the stack was not the same in Primary database

$ ulimit -a
time(seconds)        unlimited
file(blocks)         unlimited
data(kbytes)         unlimited
stack(kbytes)        8192
coredump(blocks)     unlimited
nofiles(descriptors) 256
vmemory(kbytes)      unlimited
$ ulimit -Ha
time(seconds)        unlimited
file(blocks)         unlimited
data(kbytes)         unlimited
stack(kbytes)        unlimited
coredump(blocks)     unlimited
nofiles(descriptors) 65536
vmemory(kbytes)      unlimited

One is 8192, the other is 10240 bytes.

I know that I can force the stack for standby in .profile - shell for Oracle. But I did not know how to set it?

May you guide me? Thank you very much!

And, when I define the block in both of server, I found that:
Primary:

$ df -g | grep "block size"
/                  (/dev/md/dsk/d10   ):         8192 block size          1024 f
rag size
/devices           (/devices          ):          512 block size           512 f
rag size
/system/contract   (ctfs              ):          512 block size           512 f
rag size
/proc              (proc              ):          512 block size           512 f
rag size
/etc/mnttab        (mnttab            ):          512 block size           512 f
rag size
/etc/svc/volatile  (swap              ):         8192 block size          8192 f
rag size
/system/object     (objfs             ):          512 block size           512 f
rag size
/platform/sun4u-us3/lib/libc_psr.so.1(/platform/sun4u-us3/lib/libc_psr/libc_psr_
hwcap2.so.1):     8192 block size          1024 frag size
/platform/sun4u-us3/lib/sparcv9/libc_psr.so.1(/platform/sun4u-us3/lib/sparcv9/li
bc_psr/libc_psr_hwcap2.so.1):     8192 block size          1024 frag size
/dev/fd            (fd                ):         1024 block size          1024 f
rag size
/tmp               (swap              ):         8192 block size          8192 f
rag size
/var/run           (swap              ):         8192 block size          8192 f
rag size
/vnporadataSYSTEM  (/dev/dsk/c4t600A0B8000482FB20000045247E9D08Ad0s0):     8192
block size          1024 frag size
/vnprctl           (/dev/dsk/c4t600A0B8000482FB20000044C47E9CED8d0s0):     8192
block size          1024 frag size
/u01               (/dev/md/dsk/d30   ):         8192 block size          1024 f
rag size
/u02               (/dev/md/dsk/d40   ):         8192 block size          1024 f
rag size
/vnporadataUSERS   (/dev/dsk/c4t600A0B8000482FB20000044F47E9CF52d0s0):     8192
block size          1024 frag size
$

In standby:

$ df -g | grep "block size"
/                  (/dev/dsk/c1t0d0s0 ):         8192 block size          1024 f
rag size
/devices           (/devices          ):          512 block size           512 f
rag size
/system/contract   (ctfs              ):          512 block size           512 f
rag size
/proc              (proc              ):          512 block size           512 f
rag size
/etc/mnttab        (mnttab            ):          512 block size           512 f
rag size
/etc/svc/volatile  (swap              ):         4096 block size          4096 f
rag size
/system/object     (objfs             ):          512 block size           512 f
rag size
/etc/dfs/sharetab  (sharefs           ):          512 block size           512 f
rag size
/lib/libc.so.1     (/usr/lib/libc/libc_hwcap1.so.1):     8192 block size
  1024 frag size
/dev/fd            (fd                ):         1024 block size          1024 f
rag size
/tmp               (swap              ):         4096 block size          4096 f
rag size
/var/run           (swap              ):         4096 block size          4096 f
rag size
/u01               (/dev/dsk/c1t0d0s3 ):         8192 block size          1024 f
rag size
/export/home       (/dev/dsk/c1t0d0s7 ):         8192 block size          1024 f
rag size
$

Same block size, but some thing was different, such as:
In primary

/etc/svc/volatile  (swap              ) :         8192 block size          8192 frag size 

/dev/fd            (fd                ) :         1024 block size          1024 frag size
/tmp               (swap              ) :         8192 block size          8192 frag size
/var/run           (swap              ) :         8192 block size          8192 frag size

In standby

/etc/svc/volatile  (swap              ) :         4096 block size        4096 frag size
/dev/fd            (fd                ) :         1024 block size          1024 frag size
/tmp               (swap              ) :         4096 block size          4096 frag size
/var/run           (swap              ) :         4096 block size          4096 frag size

May you clarify more about them? Do them - the difference parameter affect to asynchronous data which will be transferred from primary to standby database? If yes, what should I do?

Thank you very much!

You're using Oracle 8i or 10g ?

Thank you for your reply, incredible

I am using Oracle 10g - 10.2.0.1, Solaris 10.

It's because you are doing cross platform transfer.You can't use Solaris files as is on HP machine. The Endian is different between Solaris and HP platform.

Thank you for your reply!

If I set ulimit -s 8192 in .profile of Oracle, will the problem resolve?

I cant guarantee you on that. But definitely you need to try. :o