DBAsupport.com Forums - Powered by vBulletin
Page 1 of 2 12 LastLast
Results 1 to 10 of 12
  1. #1
    Join Date
    Jul 2002
    Lincolnshire, IL
    Hi friends,
    My Oracle 8.1.6 database is running on SUN SPARC Solaris. I'm trying to startup the database but after mounting it throws "ORA-03113: end-of-file on communication channel"
    I have checked my SID. it is correct. plz tell me what is the problem and the solution also.
    Thanks in advance...
    "Greatest Rewards come only with Greatest Commitments!"

  2. #2
    Join Date
    Oct 2000
    Saskatoon, SK, Canada
    Expat from oracle metalink.

    Connecting to Oracle  ====================
           If the ORA-3113 error occurs when actually connecting to Oracle then 
           continue with this section. If you connect to Oracle successfully and get
           the error on an established connection, please go to the next section
          'An Established Connection'.
            Local Connections
            For local connections check the following:
                1)      Have you installed the Parallel Server Option?
                      ORA-3113 will occur if you have installed the Parallel
                      Server Option but do NOT have a Distributed Lock Manager
                      installed or running. 
                       To deinstall the Parallel Server Option:
                                Shut down any Oracle instances
                              % script /tmp/relink.out
                              % cd $ORACLE_HOME/rdbms/lib
                              # 'oracle' should not exist so delete it if it present
                              % rm -f oracle
                              % make -f oracle.mk no_parropt ioracle
                              % exit
                        If the above reports any errors Oracle support will need to
                        see the contents of the file /tmp/relink.out.
                 2)     Try using the SQL*Net V1 driver for local connections:
                                setenv TWO_TASK P:
                        Then try the client tool. If this now works you may have a
                       problem with the default SQL*Net driver.
                 3)     Your 'oracle' executable may be corrupt. Relink it as follows:
                                Log in as the 'oracle' user.
                              % script /tmp/relink.out
                              % cd $ORACLE_HOME/rdbms/lib
                              % rm -f oracle
                                      % make -f oracle.mk ioracle
                              % exit
                        If this reports any errors Oracle support will need to see
                      the contents of the file /tmp/relink.out .
                 4)     Some Unix platforms need LD_LIBRARY_PATH to be set
                     correctly to resolve any dynamically linked libraries.
                    As the user with the problem:
                              % script /tmp/ldd.out
                              % id
                              % cd $ORACLE_HOME/bin
                              % ldd oracle
                              % exit
                        If the 'ldd' command does not exist go to the next step below.
                      Check that all lines listed show a full library file. If there
                      are any 'not found' lines reported contact Oracle support
                      with the output of /tmp/ldd.out.
                 5)     If you cannot connect as the Oracle user AND your system has
                     the 'truss' command try the following when logged in as
                     'oracle' (using the relevant client tool):
                     % truss -o /tmp/truss.out -f sqlplus user/password 
                             Exit from sqlplus (or the problem tool)
                        Keep the file /tmp/truss.out safe - Oracle MAY need to see it.

    [Edited by sambavan on 10-10-2002 at 11:14 AM]

    Life is a journey, not a destination!

  3. #3
    Join Date
    Sep 2002
    check memory and kernel parameters (sempahores)

    I got this error today when the processes parameter in the init.ora was set to high and the kernel couldnt cope with it

  4. #4
    Join Date
    Oct 2002

    Shared Memory: How do I?

    Shared Memory: How do I?
    This was taken from another forum on Shared Memory: Just an FYI.....

    Thanks to all. I was trying to determine the current shared memory status, and
    how to change their values.

    Original question:

    Do you know how to determine what the current value settings are for
    the following:


    I have checked the /etc/system file and there are no entries for the
    above, I assume that means the system is runing the defaults. What are
    the defaults? I used the command sysdef and some of the above are listed
    but, with the value 0. Does that mean the default is 0 or 0 represents
    some default? How do I find out what the actual default values are?
    Any help on this would be appreciated.


    Response #1 -- Deepak_D_Wilson@notes.seagate.com
    Hope this article helps you:-

    The solaris 2.X kernel comes configured with defaults for shared memory
    parameters which may not be enough for large applications, such as databases.
    Many database manufacturers, such as Oracle, Sybase and Informix
    require that shared memory parameters be increased to handle their
    system. In general, any program which makes shared memory system
    service calls will be affected.

    Here are the shared memory parameters, what they are, what their default
    values are, and what they represent. Please note that the maxima listed
    here are based on values which will fit into their datatype, which is a
    (4-byte) integer, and are not realistic. Realistic maxima are not easily
    figured, as they must account for many factors, including the amount of
    kernel memory required by everything else on the system, and the
    amount of memory the system has.

    shmmax 1048576 (1Meg) 2147482647

    This is the maximum size of a shared memory segment, or the largest
    value which can be requested of shmget(2). Setting this value high
    does not hurt anything as the resource it controls is not
    preallocated, but rather is allocated on demand.

    shmmin 1 2147482647

    This is the minimum size of a shared memory segment. There is no need
    to change this from the default, as doing so will only break code
    which allocates less than the new shmmin value allows.

    shmseg 6 2147482647

    This is the maximum number of shared memory segments per process. It
    is used as a high limit, which is checked before another segment is
    allocated. No resources are preallocated based on its value.

    shmmni 100 2147482647

    This is the maximum number of shared memory identifiers that can exist
    systemwide. Every shared memory segment has an associated identifier,
    returned from shmget(). Resources are preallocated based on this
    value, (112 bytes of kernel memory per identifer) so don't set it too high.

    Shared memory parameters are changed by editing the /etc/system file with
    lines of the form:

    set shmsys:shminfo_variable = value

    For example:

    set shmsys:shminfo_shmmni = 150

    to change shmmni to 150.

    After changing the /etc/system file, reboot the system to have it take

    All InterProcess Communication (IPC) parameters, including those for shared
    memory, are checked by doing the following:

    $ sysdef -i

    Look toward the bottom of the output, for something like:

    * IPC Shared Memory
    1048576 max shared memory segment size (SHMMAX)
    1 min shared memory segment size (SHMMIN)
    100 shared memory identifiers (SHMMNI)
    6 max attached shm segments per process (SHMSEG)

    The values at the left will reflect the values set in the /etc/system file.
    If the values are zeros, load the shared memory module and try sysdef -i
    Do the following to load the shared memory module:

    # modload /kernel/sys/shmsys

    Response #2 -- Carlo Cosolo

    Carlo suggested I call SecurID tech support, as he had problems with their
    parameters and Sol 2.5.

    Response #3 -- Ju-Lien Lim

    man sysdef

    Response #4 -- jyoung@educate.com

    man ipcs

    Response #5 -- Glenn Satchell - Uniq Professional Services

    You can inspect the current value in th ekernel using adb:

    # adb -k
    physmem 3e40
    symbol not found

    This means that this system is not using _any_ shared memory stuff as
    the modules haven't even been loaded.

    If you already have these values configured then just use the larger of
    the two values (securid recommendation or current).

    Response #6 -- "K.Ravi"

    In Solaris, the shared memory module (or any other driver/module for that
    matter) is not loaded into memory unless some process needs it. To know the
    defaults, run 'modload /kernel/sys/shmsys' as root and then run 'sysdef'. If
    sysdef doesn't report all the values, try this:
    # adb -k /dev/ksyms /dev/mem

    "Live Life to the Fullest"

  5. #5
    Join Date
    Jul 2002
    Lincolnshire, IL
    Thanks for reply. half an hour bach the DB was running perfectly...then i need to restart the server and I shutdown the DB. After some 20 mins when I tried to srartup the Oracle I got the error after DB was mount.
    I shutdown the DB and reduced my SGA parameters from init.ora file. Still I'm getting the same problem...

    sambavan could you plz elaborate your answer...
    Thanks a lot...
    "Greatest Rewards come only with Greatest Commitments!"

  6. #6
    Join Date
    Jul 2002
    Lincolnshire, IL
    Hi ,
    Here are few lines from my alert.log...any idea from this...
    Plz help me out...

    Database mounted in Exclusive Mode.
    Completed: alter database mount
    Sun Oct 10 20:54:17 1999
    alter database open
    Beginning crash recovery of 1 threads
    Sun Oct 10 20:54:18 1999
    Thread recovery: start rolling forward thread 1
    Recovery of Online Redo Log: Thread 1 Group 3 Seq 14577 Reading mem 0
    Mem# 0 errs 0: /data/oracle/dbfiles/oradata/SCB/redo01.log
    Sun Oct 10 20:54:18 1999
    Thread recovery: finish rolling forward thread 1
    Thread recovery: 3 data blocks read, 3 data blocks written, 39 redo blocks read
    Crash recovery completed successfully
    Sun Oct 10 20:54:18 1999
    Thread 1 advanced to log sequence 14578
    Thread 1 opened at log sequence 14578
    Current log# 1 seq# 14578 mem# 0: /data/oracle/dbfiles/oradata/SCB/redo03.log
    Successful open of redo thread 1.
    Sun Oct 10 20:54:18 1999
    SMON: enabling cache recovery
    SMON: enabling tx recovery
    Sun Oct 10 20:54:18 1999
    Errors in file /data/oracle/admin/SCB/bdump/scb_smon_903.trc:
    ORA-00600: internal error code, arguments: [kcbrbr_2], [3], [16878170], [8], [], [], [], []
    SMON: terminating instance due to error 600
    Instance terminated by SMON, pid = 903

    "Greatest Rewards come only with Greatest Commitments!"

  7. #7
    Join Date
    Apr 2001
    Bangalore, India

    trace file


    Please update with the contents of the file


    copy first few important lines.

    Thomas Saviour(royxavier@yahoo.com)
    Technical Lead (Databases)
    Thomson Reuters (Markets)


  8. #8
    Join Date
    Oct 2002

    AW the ORA-0600

    Yuck...You got an ORA_0600. These are errors that could be anything. These errors should be reported to ORACLE for support.

    "Live Life to the Fullest"

  9. #9
    Join Date
    Oct 2000
    Saskatoon, SK, Canada
    This error could be related to few things like a redo corruption, dictionary corruptions and etc. So, my suggestion to you at this juncture would be to contact oracle with the trace file. That will reveal what exactly caused the problem and it would require more interaction with the oracle support. Once other thing that concerns me was that you might not be able to get support for 8.1.6 as it was desupported in the begining of this year. But still its worth the try.


    Life is a journey, not a destination!

  10. #10
    Join Date
    Jul 2002
    Lincolnshire, IL
    Hi Friends,
    Here are some of the first few inmportant lines from /data/oracle/admin/SCB/bdump/scb_smon_903.trc

    Oracle8i Enterprise Edition Release - Production
    With the Partitioning option
    JServer Release - Production
    ORACLE_HOME = /data/oracle
    System name: SunOS
    Node name: sunsvr
    Release: 5.7
    Version: Generic_106541-08
    Machine: sun4u
    Instance name: SCB
    Redo thread mounted by this instance: 1
    Oracle process number: 6
    Unix process pid: 903, image: oracle@sunsvr (SMON)

    *** SESSION ID:(5.1) 1999-10-10 20:54:18.515
    *** 1999-10-10 20:54:18.515
    ksedmp: internal or fatal error
    ORA-00600: internal error code, arguments: [kcbrbr_2], [3], [16878170], [8], [], [], [], []

    "Greatest Rewards come only with Greatest Commitments!"

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

Click Here to Expand Forum to Full Width

We have made updates to our Privacy Policy to reflect the implementation of the General Data Protection Regulation.