Sponsored Content
Operating Systems Solaris Negative impact on Oracle DB after Solaris recommended patching Post 302821751 by Just Ice on Saturday 15th of June 2013 11:58:09 AM
Old 06-15-2013
if the patches installed were os patches, there is a possibility that some corruption to the db has occured especially if the db was active during the patch install ... however -- whether or not db was active during patching -- if possible, restore a pre-patch copy of the db into another directory and see if that works better ...
 

8 More Discussions You Might Find Interesting

1. UNIX and Linux Applications

upgrade to solaris 9 - mysql impact

I have 4 solaris 8 servers running mysql 5.0.22. I am considering upgrading to solaris 9 and wanted to know if mysql needs to be recompiled for mysql to run under solaris 9. Thank you (4 Replies)
Discussion started by: csgonan
4 Replies

2. Solaris

impact of upgrading the SOLARIS OS from 5.6to 5.8

Please give me some idea about the impact of upgrading the SOLARIS OS from 5.6 to 5.8. We are using object store database of version 5.1. will there be any impact on this. Please help me in this regard. Thanks in advance. (1 Reply)
Discussion started by: vamshikrishnab
1 Replies

3. Solaris

Solaris 10 Recommended Patches

Does anyone get the following error message below when trying to download solaris 10 recommended patch? End-of-central-directory signature not found. Either this file is not a zipfile, or it constitutes one disk of a multi-part archive. In the latter case the central directory and... (8 Replies)
Discussion started by: Sarccastik Dude
8 Replies

4. Solaris

Solaris Trunking and its impact on VCS cluster and others

Hello guys, I have a question regarding link aggregation / trunking in Solaris 9 Sun Trunking does not come by default in Solaris 9 unlike Solaris 10 where we can use the "dladm" command to trunk 4 physical NIC interfaces together. My question is in Solaris 9. Will the configurations of... (1 Reply)
Discussion started by: br1an
1 Replies

5. Solaris

Recommended patchset for Solaris and the patch bundle

Hello I recently downloaded and installed the latest patchset for Solaris 10 (update 5) running on SPARC. Actually I am new to Solaris (I come from Red Hat) and the security department asked me to update the system for security fixes. I logged in to Oracle support and used the recommended patch... (3 Replies)
Discussion started by: abohmeed
3 Replies

6. Solaris

Oracle stopped updating Solaris 10 recommended patch cluster ?

Dear All, Has Oracle stopped updating Solaris 10 recommended patch cluster ? From suport.oracle.com i could see the last patch bundle was released on 11th july and there has been no updates after that. Does anyone know about any official announcement from oracle on this ? Thanks ... (1 Reply)
Discussion started by: abhi_8029
1 Replies

7. Solaris

Patching Procedure in Solaris 10 with sun cluster having Solaris zone

Hi Gurus I am not able to find the patching procedure for solaris 10 ( sol10 u11) to latest patchset with sun cluster having failover zones so that same I should follow. Take an instance, there are sol1 and sol2 nodes and having two failover zones like sozone1-rg and sozone2-rg and currently... (1 Reply)
Discussion started by: nick101
1 Replies

8. Solaris

No New Solaris 10 Recommended cluster in a few months

Hi Guys, I'm looking to download the latest patche cluster, we install them on a monthly basis. I have not seen anything released in the last couple months since January. Did I miss an announcement? Are they going to start releasing quarterly? Or is it just so happening there are no... (2 Replies)
Discussion started by: BG_JrAdmin
2 Replies
GIT-QUILTIMPORT(1)						    Git Manual							GIT-QUILTIMPORT(1)

NAME
git-quiltimport - Applies a quilt patchset onto the current branch SYNOPSIS
git quiltimport [--dry-run | -n] [--author <author>] [--patches <dir>] [--series <file>] DESCRIPTION
Applies a quilt patchset onto the current Git branch, preserving the patch boundaries, patch order, and patch descriptions present in the quilt patchset. For each patch the code attempts to extract the author from the patch description. If that fails it falls back to the author specified with --author. If the --author flag was not given the patch description is displayed and the user is asked to interactively enter the author of the patch. If a subject is not found in the patch description the patch name is preserved as the 1 line subject in the Git description. OPTIONS
-n, --dry-run Walk through the patches in the series and warn if we cannot find all of the necessary information to commit a patch. At the time of this writing only missing author information is warned about. --author Author Name <Author Email> The author name and email address to use when no author information can be found in the patch description. --patches <dir> The directory to find the quilt patches. The default for the patch directory is patches or the value of the $QUILT_PATCHES environment variable. --series <file> The quilt series file. The default for the series file is <patches>/series or the value of the $QUILT_SERIES environment variable. GIT
Part of the git(1) suite Git 2.17.1 10/05/2018 GIT-QUILTIMPORT(1)
All times are GMT -4. The time now is 03:33 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy