Re: ora 3113 error - end of communication channel

Dear all,

Problem was successfully solved by modifying parameters in /etc/sysconfigtab file:

proc:
max_proc_per_user = 512

ipc: shm_max=2139095040

I set them similar to parameters set in another node (node1). But I still wandering why these parameters were changed....

Konstantin.

Daniel Morgan <damorgan_at_exxesolutions.com> wrote in message news:<3F32CDDB.A7BE5D41_at_exxesolutions.com>...
> konstantin wrote:
>
> > Dear all,
> >
> > I have ora 3113 error. I've read already a lot about but still cannot
> > find a solution.
> > I have Oracle Enterprise Edition 8.1.7 running on Tru64 UNIX (COMPAQ)
> > - 2 node cluster version 5.1A.
> > The problem is the following - I can start automatically and manually
> > in one node e.g. node1 and cannot run in the second node though
> > principally it starts from the same disk (physical disk). Both
> > operating system and Oracle located in common RAID massive.
> > I cannot even start svrmgrl properly - I start receiving ora 3113 from
> > the beginning.
> >
> > Please see below content of trace file.
> >
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> > /usr/users/oracle/u01/app/oracle/product/8.1/rdbms/log/ora_1051486.trc
> > Oracle8i Enterprise Edition Release 8.1.7.2.0 - Production
> > With the Partitioning option
> > JServer Release 8.1.7.2.0 - Production
> > ORACLE_HOME = /usr/users/oracle/u01/app/oracle/product/8.1
> > System name: OSF1
> > Node name: node2
> > Release: V5.1
> > Version: 1885
> > Machine: alpha
> > Instance name: 2000
> > Redo thread mounted by this instance: 0 <none>
> > Oracle process number: 0
> > 1051486
> >
> > *** 2003-08-06 16:24:01.559
> > ksedmp: internal or fatal error
> > Exception signal: 11, code = 11fffa318
> > sc_onstack: 0000000000000000, sc_mask 0000000000000000
> > pc: 000000012137a000, ps: 0000000000000008, ownedfp: 0000000000000001
> > r00: 0000000000000020
> > r01: 00000000cccccccd
> > r02: 0000000000000276
> > r03: 0000000083126e98
> > r04: ffffffffd76da168
> > r05: 0000000000000276
> > r06: 0000000000000000
> > r07: 0000000000000000
> > r08: 0000000000000000
> > r09: 00000000380003d8
> > r10: 000000011fffad41
> > r11: 00000000380004b0
> > r12: 0000000000000000
> > r13: 000000014003afb8
> > r14: 0000000000000000
> > r15: 0000000000000001
> > r16: 00000000380003d8
> > r17: 0000000000000000
> > r18: 0000000000000140
> > r19: 0000000000000001
> > r20: 0000000000000000
> > r21: 0000000120333240
> > r22: 0000000000000000
> > r23: 000003ff800d2568
> > r24: 0000000000000000
> > r25: 0000000000000000
> > r26: 0000000121387578
> > r27: 00000001213889b0
> > r28: 000000012045aa18
> > r29: 000000014010abc8
> > r30: 000000011fffa620
> > r31: 0000000000000000
> > fpcr: 8900000000000000, fp_control: 0000000140134908
> > trap_a0: 0000000000000038, trap_a1: 0000000000000001, trap_a2:
> > 0000000000000000
> > fp_trap_pc: 000000012056d7c0, fp_trigger_sum: 0000000038002778,
> > fp_trigger_inst 000000000000001d
> > Exception signal: 11, code = 11fff9458
> > sc_onstack: 0000000000000000, sc_mask fffffffffe7ef057
> > ssexhd: crashing the process...
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> >
> > Any help very much appreciated.
>
> When it was installed were the installation instructions read and followed
> step-by-step or did someone just type runInstaller and wing it?
Received on Fri Aug 08 2003 - 01:58:53 CDT