Unix Addiction

HOW TO INSTALL ORACLE BINARIES AND ORACLE DATABASE FOR 11gr2 IN SOLARIS 11.X, AND PREVIOUS PREPARATION FOR THE OS ENVIRONMENT Preparing the Solaris 11.3 OS for database installation 1.-Create Zpool and ZFS Files system Create Zpool #zpool create data c5t025340000233000865d0 Create ZFS Files System #zfs create  data/oracle-bin  (For Install BINARIES) #zfs create  data/u01        (For Install DATABASE) #zfs create  data/arch        (For REDOLOG) #zfs create  data/backup      (and RMAN BACKUP) The number one rule for setting up an Oracle database on ZFS is to set ZFS recordsize equal to the database block size for the file systems that contain the Oracle data files. recordsize = db_block_size 2.-In this case we are installing a OLTP Database, we will set the File System Recordsize to 8k, as zfs recommend #zfs set recordsize=8k data/oracle-bin #zfs set recordsize=8k data/u01 #zfs set recordsize=8k data/arch 3.-Mount ZFS files system in the res

1) Boot your system and wait until the GRUB2 menu appears. 2) In the boot loader menu, highlight any entry and press e . 3) Find the line beginning with linux. At the end of this line, append the following: init=/bin/sh Or if you face a panic, instead of "ro" change to "rw" to sysroot as example below: rw init=/sysroot/bin/sh 4) Press F10 or Ctrl+X to boot the system using the options you just edited. Once the system boots, you will be presented with a shell prompt without having to enter any user name or password: sh-4.2# 5) Load the installed SELinux policy: sh-4.2# /usr/sbin/load_policy -i 6) Execute the following command to remount your root partition: sh4.2# mount -o remount,rw / 7) Reset the root password: Raw sh4.2# passwd root 9) Reboot the system. From now on, you will be able to log in as the root user using the new password set up during this procedure.  

Sumary: With this method we do not need a previous backup from the source database. The database cloning is performed through the network using rman script. Is important that source database be in archive mode and both databases (source and target databases) are of 11g version onwards. For this scenario the source database and destination database will have differents directories for control file, datafiles, redologs and tempfiles. 1- This is the information for two database environtments : Primary server    : 10.1.0.1 target server     : 10.1.0.2 (Destiny server) Primary DB        : TST Target DB         : TSTAUX  (Database to be copied) 2- In both servers under $ORACLE_HOME/network/admin in tnsnames.ora set the following entries : TST_DB=     (DESCRIPTION =     (ADDRESS = (PROTOCOL = TCP)(HOST = 10.1.0.1)(PORT = 1529))     (CONNECT_DATA =     (SID = tst)     )      ) TSTAUX_DB=      (DESCRIPTION =     (ADDRESS = (PROTOCOL = TCP)(HOST = 10.

      Sumary: With this method we do not need a previous backup from the source database. The database cloning is performed through the network using rman script. Is important that source database be in archive mode and both databases (source and target databases) are of 11g version onwards. For this scenario the source database and destination database will have the same directory structure for control file, datafiles, redologs and tempfiles. 1- This is the information for two database environtments : Primary server : 10.1.0.1 target server     : 10.1.0.2 (Destiny server) Primary DB     : TST Target DB        : TSTAUX  (Database to be copied) 2- In both servers under $ORACLE_HOME/network/admin in tnsnames.ora set the following entries : TST_DB=   (DESCRIPTION =     (ADDRESS = (PROTOCOL = TCP)(HOST = 10.1.0.1)(PORT = 1529))     (CONNECT_DATA =       (SID = tst)     )   ) TSTAUX_DB=   (DESCRIPTION =     (ADDRESS = (PROTOCOL = TCP)(HOST = 10.1.0.2)

1.Update Subscription Manager Package, validate first that system is registered   #yum -y update subscription-manager* 2.-Delete the Yum Cache   rm –rf /var/cache/yum/* 3.-Clean with command to be sure that it was cleaned correctly #yum clean all 4.-Set the release to tie teh Red Hat OS, where  you are working to the specific release to avoid to update for example from 6.6 to 6.8 Stable in this case.   These is usable if you need to have support and the application is only supported in a specific release #subscription-manager release --set=6.7 --proxy=http://<ipaddress_proxy>:8080 --proxyuser=<proxyuser> -proxypass=<proxypassword> or if you have Access directly to internet #subscription-manager release --set=6.7 5.-Update the OS   yum -y update    

Oracle 11g introduces the "duplicate from active database database to stand by". This feature allows the creation of a stand by database without need a previous backup. The primary database need to be in archive mode. This is possible by using one RMAN script. It will copy the server parameter file to the standby host, start the auxiliary instance using the server parameter file and will copy control, redologs  and datafiles over the network to the stand by host. 1- Create a single instance database (for this case, our primary database will be tst).    Primary server     : 10.1.0.1    Secondary server   : 10.1.0.2       TNS alias for Primary – TST_PR    TNS alias for standby – TST_DRP       Primary DB_NAME Parameter=tst      Primary DB_UNIQUE_NAME Parameter=tst_pri    Standby DB_NAME Parameter=tst      Standby DB_UNIQUE_NAME Parameter=tst_drp       ALTER SYSTEM SET LOG_ARCHIVE_CONFIG='DG_CONFIG=(ep0_pri,tst_drp)';    alter system set db_unique_name

Updating Solaris 11.X to 11.3 Download Repository Certificate s accessing with MOS user https://pkg-register.oracle.com/register/certificate/ Upload them to the server and rename as below pkg.oracle.com.certificate.perm pkg.oracle.com.key.perm root@:~# pkg unset-publisher This option below delete the currently repository and add the new one root@:~# pkg set-publisher -k  /root/pkg.oracle.com.key.pem -c /root/pkg.oracle.com.certificate.pem -G "*" -g https://pkg.oracle.com/solaris/support/ solaris root@:~# pkg publisher PUBLISHER                   TYPE     STATUS P LOCATION solaris                     origin   online F http://pkg.oracle.com/solaris/support/ root@# pkg update Validate previous boot environment root@:~# beadm list BE      Flags Mountpoint Space  Policy Created --      ----- ---------- -----  ------ ------- solaris NR    /          12.58G static 2016-03-15 07:11 root@:~# root@:~# PHASE