Cheats In Pokemon Silver Online

Tuesday, June 23, 2009

Cheats In Pokemon Silver Online

Fixing the error: ORA-27102: out ot memory in Oracle and Solaris 10

By changing the files on a Oracle database on a server with a Solaris 9 to Solaris 10 and I found myself wanting to get the following error
SQL> startup ORA-27102 : out of
memory SVR4 Error: 22: Invalid argument

as the error message the server has insufficient memory, see the documentation says about $ oerr
ORA 27102 27102, 00000, "out of memory"
/ / * Cause: Out of memory / / * Action: Consult the trace file for details

 nothing encouraging picture. Let's review the last recorded in the file $ cat alert.log   Fri alert.log 

June 5 18:19:45 2009 Starting ORACLE instance (normal) Fri

 June 5 18:19:46 2009 WARNING: EINVAL Creating segment of size 0x000000008c400000 
 fix shm parameters in / etc / system or equivalent Oracle is trying 
 
 to create a shared memory segment 2G (depending on the size of SGA / PGA), but the operating system responded with an error message invalid argument (EINVAL). It also shows a small clue to configure 
 shm in / etc / system 
. 
 
 Before Solaris 10, 
 parameter was set shmsys: shminfo_shmmax 
 
 in / etc / system 
 with the maximum size of memory segment that can be created. The default value in Solaris 9 and earlier is 8M, while in Solaris 10 or higher is 1 / 4 of physical memory. You can verify as follows: 
 
 $ prtconf   size: 2048 Megabytes 
 $ id -p 
 uid=110(oracle) gid=201(dba) projid= 
 3 
 (default) 
 $ prctl -n project.max-shm-memory -i project  
 3 
  
 project: 3: default 
 NAME&nbsp;&nbsp;&nbsp;&nbsp;PRIVILEGE&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;VALUE&nbsp;&nbsp;&nbsp;&nbsp;FLAG&nbsp;&nbsp;&nbsp;ACTION&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;RECIPIENT  
 project.max-shm-memory 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;privileged&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;479M&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-&nbsp;&nbsp;&nbsp;deny&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-  
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;system&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;16.0EB&nbsp;&nbsp;&nbsp;&nbsp;max&nbsp;&nbsp;&nbsp;deny&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;- 
 
 Therein lies the problem, the system is using the default value of 479m in this case, when Oracle is trying to create a segment of memory (2G) greater than 479m. 
 
 The solution is to configure the system with a large enough size for the shared memory segment is created and can lift Oracle instance. 
 

In Solaris 9 and earlier, this can be done by adding the following line in
/ etc / system
, having to reboot the system to take the new value.

shminfo_shmmax = 0x000000008c400000
September
parameter in Solaris 10
shminfo_shmmax Sun is obsolete and not recommended to set in

/ etc / system In Solaris 10 and later, this value can be changed dynamically by the project with the help of resource control services. So as in Solaris 10 and later

project.max prctl-n-shm-memory-r-v

 2G-i project 3-n 
 $ prctl project.max-shm-memory-i project 3 
 NAME PRIVILEGE VALUE FLAG ACTION ; RECIPIENT  

project.max-shm-memory
        privileged      2.0G        -   deny                                 -
        system          16.0EB    max   deny                                 -

All changes made to the command
prctl

 apply to the system temporarily so you will be lost when you reboot. To make it permanent, create a project with the command 
 projadd

$ projadd-p 200-c 'Oracle config'-U-G dba oracle-K 'project.max-shm-memory = (privileged, 2G, deny) 'oracle Finally Make sure that the command was created with projects-l

or cat / etc / project

 
 $ projects-l ... 
 ... Oracle

projid: 200
        comment: "Oracle config"         users  : oracle         groups : dba
        attribs: project.max-shm-memory=(priv,2147483648,deny)
$ Cat / etc / project ... ... oracle: 200: config Oracle: oracle: dba: project.max-shm-memory = (priv, 2147483648, deny)
With these changes, Oracle should start the database normally.

 
 SQL> startup ORACLE instance started 
. 
  Total System Global Area 2333054160 bytes Fixed Size  734416 bytes 
 Variable Size 1191182336 bytes Database buffers  : 1073741824 bytes Redo buffers  
 67395584 bytes Database mounted. 
 Database opened. 
 
 Another case that may have the same symptom is when you increase the SGA on the instance tuning possibly a result which if greater than the segment of memory configured for the system, when you try to lift the instance will have this same behavior. 
 

Via

Mandalika's scratchpad

YOUR IMMIGRATION LAWYER 807464236

Tuesday, June 23, 2009

Cheats In Pokemon Silver Online

0 comments:

Post a Comment