DBAsupport.com Forums - Powered by vBulletin
Page 1 of 2 12 LastLast
Results 1 to 10 of 15

Thread: ORA-27102 out of memory error

  1. #1
    Join Date
    Jun 2001
    Posts
    243
    Hi, my backup failed last night due to this error...

    here is my /etc/system...

    can you give me some advice?....

    * set shmsys:shminfo_shmmax=384000000
    set shmsys:shminfo_shmmax=0x4000000
    set shmsys:shminfo_shmmin=1
    set shmsys:shminfo_shmmni=1024
    set shmsys:shminfo_shmseg=1024
    set semsys:seminfo_semmsl=400
    set semsys:seminfo_semmni=120
    #set semsys:seminfo_semmns=200

    what's the ideal shmmax?...do I need semmns?
    am I missing any shmsys:shminfo_???

    Thank you

  2. #2
    Join Date
    Jun 2001
    Posts
    243
    here is my SGA info..

    Total System Global Area 494829552 bytes
    Fixed Size 69616 bytes
    Variable Size 359297024 bytes
    Database Buffers 134217728 bytes
    Redo Buffers 1245184 bytes

  3. #3
    Join Date
    Nov 2000
    Location
    greenwich.ct.us
    Posts
    9,092
    What does the trace file say?
    Jeff Hunter

  4. #4
    Join Date
    Jun 2001
    Posts
    243
    trace file doesn't tell me anything? you mean trace file in bdump or udump?

  5. #5
    Join Date
    Oct 2000
    Posts
    467
    if your backups failed, what was the backup error ? Are you backing up using RMAN and is it a hot/cold backup ?
    If any errors , then it should be in bdump and/or udump. Can you check and see what it says or post it here ?
    Vinit

  6. #6
    Join Date
    Nov 2000
    Location
    greenwich.ct.us
    Posts
    9,092
    Yes, in bdump or udump. Probably in udump...
    Jeff Hunter

  7. #7
    Join Date
    Jun 2001
    Posts
    243
    I'm not using RMAN...I'm doing cold backup....
    here is the .trc from bdump:

    Oracle8i Enterprise Edition Release 8.1.6.1.0 - Production
    With the Partitioning option
    JServer Release 8.1.6.1.0 - Production
    ORACLE_HOME = /ora01/app/oracle/product/8.1.6
    System name: SunOS
    Node name: d2kserv
    Release: 5.7
    Version: Generic_106541-11
    Machine: sun4u
    Instance name: JOPES
    Redo thread mounted by this instance: 0
    Oracle process number: 22
    Unix process pid: 26900, image: oracle@d2kserv (ARC0)

    *** SESSION ID:(21.1) 2001-11-01 00:11:54.364
    *** 2001-11-01 00:11:54.364

    nothing here...


    nothing on .trc on udump either.

    here is the log from backup:

    Listing of filesystem /ora01/oradata/JOPES/backups
    total 292394
    drwxrwx--- 2 oracle dba 2048 Nov 1 00:06 .
    drwxrwxr-x 3 oracle dba 512 Sep 27 10:17 ..
    -rw-r--r-- 1 oracle dba 111533 Nov 1 00:06 control04.ctl.Z
    -rwxrwx--- 1 oracle dba 62 Nov 1 00:03 cr_JOPES.sql
    -rwxrwx--- 1 oracle dba 149495808 Feb 26 2001 force_module_uln.dmp
    -rwx------ 1 oracle dba 10 Nov 1 00:03 restore_JOPES
    Filesystem kbytes used avail capacity Mounted on
    /dev/dsk/c0t5d0s6 25742040 21304028 4180592 84% /voldb
    No archive files exist to be backed up.
    Starting database JOPES...
    Starting JOPES database ... Please wait...
    Warning: This make take a minute or two to execute...

    Oracle Server Manager Release 3.1.6.0.0 - Production

    Copyright (c) 1997, 1999, Oracle Corporation. All Rights Reserved.

    Oracle8i Enterprise Edition Release 8.1.6.1.0 - Production
    With the Partitioning option
    JServer Release 8.1.6.1.0 - Production

    SVRMGR> Connected.
    SVRMGR> ORA-27102: out of memory
    SVR4 Error: 12: Not enough space
    SVRMGR> Server Manager complete.

    Database "JOPES" warm started.
    Waiting for JOPES database to start... 1
    Waiting for JOPES database to start... 2
    Waiting for JOPES database to start... 3
    Waiting for JOPES database to start... 4
    Waiting for JOPES database to start... 5
    Waiting for JOPES database to start... 6
    Waiting for JOPES database to start... 7
    Waiting for JOPES database to start... 8
    Waiting for JOPES database to start... 9
    Waiting for JOPES database to start... 10
    Waiting for JOPES database to start... 11
    Waiting for JOPES database to start... 12
    Waiting for JOPES database to start... 13
    Waiting for JOPES database to start... 14
    Waiting for JOPES database to start... 15
    Waiting for JOPES database to start... 16
    Waiting for JOPES database to start... 17
    Waiting for JOPES database to start... 18
    Waiting for JOPES database to start... 19
    Waiting for JOPES database to start... 20
    Waiting for JOPES database to start... 21
    Waiting for JOPES database to start... 22
    Waiting for JOPES database to start... 23
    Waiting for JOPES database to start... 24
    Waiting for JOPES database to start... 25
    Waiting for JOPES database to start... 26
    Waiting for JOPES database to start... 27
    Waiting for JOPES database to start... 28
    Waiting for JOPES database to start... 29
    Waiting for JOPES database to start... 30
    Waiting for JOPES database to start... 31
    Waiting for JOPES database to start... 32
    Waiting for JOPES database to start... 33
    Waiting for JOPES database to start... 34
    Waiting for JOPES database to start... 35
    Waiting for JOPES database to start... 36
    Waiting for JOPES database to start... 37
    Waiting for JOPES database to start... 38
    Waiting for JOPES database to start... 39
    Waiting for JOPES database to start... 40
    Waiting for JOPES database to start... 41
    Waiting for JOPES database to start... 42
    Waiting for JOPES database to start... 43
    Waiting for JOPES database to start... 44
    Waiting for JOPES database to start... 45
    Database JOPES is now online...
    Warning: Database JOPES is ALREADY online


    ------- Done with BACKUP of JOPES database at 11/01/01 00:10:38 -------




  8. #8
    Join Date
    Nov 2000
    Location
    greenwich.ct.us
    Posts
    9,092
    Did some init.ora parameters get changed recently?
    Jeff Hunter

  9. #9
    Join Date
    Jan 2001
    Posts
    126
    Hi,

    When the database/application is shutdown, check if any memory segments are still attached. Use command ipcs to find these and remove them using ipcrm command. Now the memory is clean and you should be able start the database.

    shmmax seems to be low. Check the available memory/swap space on your system and set this value accordingly. Also semmns should be at least 2 * db processes + 20.

    Baliga

  10. #10
    Join Date
    Jun 2001
    Posts
    2
    Here if what my /etc/system file looks like
    set shmsys:shminfo_shmmax=4294967295
    set shmsys:shminfo_shmmin=1
    set shmsys:shminfo_shmmni=100
    set shmsys:shminfo_shmseg=400
    set semsys:seminfo_semmns=3100
    set semsys:seminfo_semmni=140
    set semsys:seminfo_semmsl=450
    set semsys:seminfo_semopm=100
    set semsys:seminfo_semvmx=32767

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