Sponsored Content
Operating Systems AIX AIX SP update and Oracle interaction Post 302914035 by bakunin on Thursday 21st of August 2014 12:35:01 PM
Old 08-21-2014
Quote:
Originally Posted by allenhibbert
mksysb is the backout plan

I do have the DBA team verify the oracle version is compatible with the intended OS update. I also read up to determine myself.

I'm curious if applying the SP while the databases are still up would cause issues. The oracle is 11G, on AIX 7 TL1 SP9. I'd try it in a test area, if I could.
You seem to come from a different flavour of Unix, so maybe a bit of background information about Alternate Disk Migration is in order. To expand on what ibmtech already explained:

One usually has a mirrored rootvg, which means that you have two identical disks carrying identical copies of the OS. ADM now does the following: it breaks up the mirror. Then you apply the update (or the installation - there is not only Alternate Disk Migration but also Alternate Disk Installation) to one of these copies. Then you reboot into this newly installed/updated environment.

If everything turns out OK you destroy the unchanged copy and remirror, so that you now have two copies of the new system images. If some problem occurs you reboot back into the old environment from the still existing (and unchanged) disk, destroy the new installation and remirror, arriving at the point you started from again.

Most of these steps are done behind the scenes by the provided procedures, but it helps to have a working picture of what is going on.

NOTE: at the end of the procedure do not forget to apply the bosboot command and maintain the system bootlist with bootlist command.

I hope this helps.

bakunin
 

4 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

update a oracle table using shell script

Hi, I would like to know how to update a table in Oracle database, if a command in one shell script either successfully completes or it fails.(like Y if its success or N if its a failure) While the command is running,I am able to view the log file created in the Unix machine.After the command... (2 Replies)
Discussion started by: ann_124
2 Replies

2. UNIX for Advanced & Expert Users

unix script for update or insert records from a file to a oracle table

Hi, I have delimited file(|). Sample data: 1|name|50009|DS24|0|12 2|name|30009|DS24|0|13 3|name|20409|DS24|0|14 4|name|20009|DS24|0|15 5|name|10009|DS24|0|16 I want to load this data into a oracle table (update and insert) Please help me the commands and also... (1 Reply)
Discussion started by: unihp1
1 Replies

3. UNIX for Advanced & Expert Users

oracle update not working

Hi, I have a oracle source with a field my_date =06/02/2009 I am trying to update the table to SYSDATE with a myscript.sql where I have UPDATE table set my_date=to_DATE(SYSDATE,'MM/DD/YYYY'); Now I try to run it with myupdate.SH script where I have sqlplus nolog @myscript.sql ... (4 Replies)
Discussion started by: RubinPat
4 Replies

4. Shell Programming and Scripting

How to update a Oracle table through shell scripting?

My Code is get_week_date() { `sqlplus -s ${DQM_SQL_LOGON}@${DQM_SID} << EOF SET ECHO OFF SET FEEDBACK OFF SET PAGES 0 SET SERVEROUTPUT ON SET VERIFY OFF SET TRIMSPOOL ON (update file_level_qc fq set FQ.DATA_FILE_NAME='Hyvee_Pharmacy_Solutions_201304_v1.txt'... (2 Replies)
Discussion started by: karthick.cho
2 Replies
re-preinstall(1M)					  System Administration Commands					 re-preinstall(1M)

NAME
re-preinstall - installs the JumpStart software on a system SYNOPSIS
cdrom-mnt-pt/Solaris_XX/Tools/Boot/usr/sbin/install.d/re-preinstall [-m Solaris_boot_dir] [-k platform_name] target-slice DESCRIPTION
re-preinstall installs the JumpStart software (preinstall boot image) on a system, so you can power-on the system and have it automatically install the Solaris software (perform a JumpStart installation on the system). When you turn on a re-preinstalled system, the system looks for the JumpStart software on the system's default boot disk. All new SPARC systems have the JumpStart software already preinstalled. The XX in Solaris_XX is the version number of the Solaris release being used. You can use the re-preinstall command in several ways. The most common way is to run re-preinstall on a system to install the JumpStart software on its own default boot disk. This is useful if you want to restore a system to its original factory conditions. (See the first procedure described in EXAMPLES.) You can also run re-preinstall on a system to install JumpStart software on any attached disk (non-boot disk). After you install the Jump- Start software on a disk, you can move the disk to a different system and perform a JumpStart installation on the different system. (See the second procedure described in EXAMPLES.) re-preinstall creates a standard file system on the specified target-slice (usually slice 0), and re-preinstall makes sure there is enough space on the target-slice for the JumpStart software. If sufficient space is not available, re-preinstall fails with the following message: re-preinstall: target-slice too small xx Megabytes required You can use the format(1M) command to create sufficient space on the target-slice for the JumpStart software. OPTIONS
The following options are supported: -k platform_name Platform name of the system that will use the disk with the JumpStart software. The default is the platform name of the system running re-preinstall. (Use the uname(1) command (-i option) to determine a system's platform name.) -m Solaris_boot_dir Absolute path to the Solaris_XX/Tools/Boot subdirectory of a mounted Solaris CD or a Solaris CD copied to disk that re-preinstall uses to install the JumpStart software. The default is root (/), which is where the Solaris CD is mounted in single-user mode. OPERANDS
The following operands are supported: target-slice Device name of the disk slice where the JumpStart software will be installed (usually slice 0), for example, c0t3d0s0. EXAMPLES
Example 1: Installing the JumpStart Software on a System's Own Default Boot Disk The following procedure installs the JumpStart software on a system's own default boot disk: 1. From the ok prompt, boot the system from the Solaris media CD or DVD in single-user mode: ok boot cdrom -s 2. The following command installs the Jumpstart software on the System default boot disk, c0t0d0s0 on a Solaris 9 system: example# /usr/sbin/install.d/re-preinstall c0t0d0s1 3. Reboot the slice: example# reboot disk:b Example 2: Installing the JumpStart Software on a System's Attached (non-boot) Disk The following procedure installs the JumpStart software on a system's attached (non-boot) disk: 1. Mount the Solaris CD or DVD if vold(1M) is not running or CD or DVD is not mounted. 2. Use the format(1M) command to determine the target-slice where JumpStart will be installed. 3. Use the uname(1) command (-i option) to determine the platform name of the system that will use the re-preinstalled disk 4. Run re-preinstall with the -m Solaris_boot_dir option if the Solaris CD or DVD is not mounted on /cdrom. The following command installs the JumpStart software on the system's attached disk for a system with a Sun4u kernel architecture, and it uses the Solaris CD or DVD mounted with vold(1M) on a Solaris 9 system: example# /cdrom/cdrom/s1/usr/bin/install.d/re-preinstall -m /cdrom/cdrom/s1 -k sun4u c0t2d0s0 EXIT STATUS
The following exit values are returned: 0 Successful completion. 1 An error has occurred. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcdrom (Solaris CD, | | |SPARC Platform Edition) | +-----------------------------+-----------------------------+ SEE ALSO
uname(1), eeprom(1M), format(1M), mount(1M), vold(1M), attributes(5) Solaris 10 Installation Guide: Basic Installations SunOS 5.10 9 Apr 2002 re-preinstall(1M)
All times are GMT -4. The time now is 01:31 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy