DBAsupport.com Forums - Powered by vBulletin
Results 1 to 4 of 4

Thread: ora -27123 svr4 error:22:invalid argument

  1. #1

    Exclamation

    Hi,

    Can anyone help me out with this error ra -27123 svr4 error:22:invalid argument

    The sga is about 1.8gigs of memory which includes 180mgs for the shared pool. If we increase this by 10megs we get this error.

    WE are running on Solaris 2.6 and Oracle 8.1.5.0

    WE had no problem when this was set to 200mg but suddenly it started to get this error and had to be reduced to 180. This is far to small for the current db. Has anyone come accross this before or knows of a solution please!!!....Is it the semphors? They are set as follows:

    * Oracle Shared Memory Parameters
    set shmsys:shminfo_shmmax=2147483647
    set shmsys:shminfo_shmmni=100
    set shmsys:shminfo_shmmin=1
    set shmsys:shminfo_shmseg=200

    * Oracle Shared Semaphores Parameters
    set semsys:seminfo_semmns=2000
    set semsys:seminfo_semmni=70
    set semsys:seminfo_semmsl=110
    set semsys:seminfo_semopm=100
    set semsys:seminfo_semvmx=32767

    * Oracle Message Queue Parameters
    set msgsys:msginfo_msgmap=1026
    set msgsys:msginfo_msgmnb=65535
    set msgsys:msginfo_msgseg=8192
    set msgsys:msginfo_msgtql=512
    set msgsys:msginfo_msgmax=4096
    set maxusers=96
    The brain is a wonderful organ; it starts working the moment you get up in the morning and does not stop until you get into the office.

  2. #2
    Join Date
    Feb 2001
    Location
    Paris, France
    Posts
    809
    look at stack size using command 'ulimit -a'.
    it should be at least 8192Kb, else increase it

  3. #3
    Hi,

    have checked the stack size and it is 8192. Have you got any other idea's?
    The brain is a wonderful organ; it starts working the moment you get up in the morning and does not stop until you get into the office.

  4. #4
    Join Date
    Feb 2001
    Location
    Paris, France
    Posts
    809
    looks like a problem with sgabeg
    here is an article taken from Metalink :

    Solution Description:
    =====================

    For RDBMS version 8.1.X , change your attach address by doing the
    following steps to relocate the SGA:

    1. Shutdown any databases using the current "ORACLE_HOME".

    2. Change your location to the "/lib" directory

    % cd $ORACLE_HOME/lib

    3. Make a backup copy of 'libserver8.a'.

    % cp libserver8.a libserver8.a.orig

    4. Change your location to the "rdbms/lib" directory

    % cd $ORACLE_HOME/rdbms/lib

    5. Generate the "ksms.s" file

    % $ORACLE_HOME/bin/genksms -b > ksms.s

    For example, changing the attached address starting at
    0x80000000 to 0x60000000 would be:

    % $ORACLE_HOME/bin/genksms -b 0x60000000 >ksms.s

    6. Regenerate the 'ksms.o' object:

    % make -f ins_rdbms.mk ksms.o

    7. Archive 'ksms.o' into 'libserver8.a'

    %ar r $ORACLE_HOME/lib/libserver8.a ksms.o

    8. Relink

    % make -f ins_rdbms.mk ioracle


    Solution Explanation:
    =====================

    Changing the 'sgabeg' in 'ksms.o' will allow you to increase SGA size and
    allocate the memory in a contiguous segment.


    NOTE: If the above process does not resolve the problem, you may be
    using an older version of the Sun Solaris architecture (Sun4c).
    If this is the case, repeat all the steps shown above and change
    the value for Step 5 to be the same as the old value less one
    zero.

    For example:

    Old Value for Step 5: 0x80000000

    New Value for Step 5: 0x8000000

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