ORACLE RAC SCRIPTS COMANDOS

 ./runcluvfy.sh  stage -pre crsinst -n usblddb1010,usblddb2011

Move SPFILE from local file system Oracle 11G

Move SPFILE from local file system
to ASM diskgroup

Step 1:

SQL> create spfile='+DG_DATA' from PFILE=’/u01/pfileORCL.ora’ ;

Login to ASM and insure the location of newly created SPFILE.

Step 2 :

move your current SPFILE with other name 

[oracle@rac122 dbs]$ mv spfileORCL1.ora spfileORCL1.ora_old

Create a default pfile and add the location of SPFILE which we created on above ASM Diskgroup.

[oracle@rac122 dbs]$ vi initORCL.ora

spfile='+DG_DATA/+DG_ORCL/ORCL/parameterfile/spfile.268.871385721'
Bounce Oracle Instance in order to read the server parameter file from new location (ASM Diskgroup).  Its read the default pfile and redirected to ASM Diskgroup location.

SQL> startup

ORACLE instance started.

Total System Global Area  551165952 bytes

Fixed Size                  2230232 bytes

Variable Size             230688808 bytes

Database Buffers          314572800 bytes

Redo Buffers                3674112 bytes

Database mounted.

Database opened.

SQL> show parameter spfile

NAME       TYPE        VALUE

---------- ----------- ---------------

Spfile    string     DG_ORCL/ORCL/parameterfile/spfile.268.871385721

Optimal SHMMAX for Oracle

According to Maximum SHMMAX values for Linux x86 and x86-64 [ID 567506.1]. Oracle Global Customer Support officially recommends a " maximum" for SHMMAX of:
32-bit servers - 3 gigabytes:  Note:  Oracle notes that you cannot set SHMMAX to exactly 4 gig because setting SHMMAX to 4GB exactly will give you 0 bytes as max, as this value is interpreted as a 32-bit number and it wraps around.)
64-bit servers - Half the RAM - "1/2 of physical RAM" on the server
 For example, if your server has 128 gigabytes of RAM, you can set SHMMAX to 64 gigabytes.
However, the maximum size of a shared memory segment is limited by the size of the available user address space. On 32-bit systems, this is two to the 32 power (2**32) pr about 4 gig. The "theoretical limit" for SHMMAX is the amount of physical RAM that you have on the server.
You can use your max SGA size (sga_target or memory_target variables) to determine the optimal setting for SHMMAX

Solaris 11 Permitir conexiones con root

Open Terminal window and switch to root user.

1. Change the file /etc/ssh/sshd_config PermitRootLogin yes with PermitRootLogin no and save file.
    vi /etc/ssh/sshd_config 
  PermitRootLogin yes
2. Comment out the “CONSOLE=/dev/console” line in /etc/default/login.
    vi /etc/default/login
  #CONSOLE=/dev/console
3.Remove “;type=role” from the root entry in /etc/user_attr or use the below command.
 rolemod -K type=normal root
4. Restart the Services.
#svcadm restart svc:/network/ssh:default