Understanding Patches

I just installed Oracle 8.1.7.0.0 on a win2k test server. I noticed that my production server has Oracle 8.1.7.4.1 -- Why is it different? Is it because of patches? If it is because of patched, Should I install all patches from oracle that relates to 8.1.7 and Win2k onto my test server?
I am trying to get a better understanding of patches. If there are 20 patches for my 8.1.7 and Win2k, do I install all patches or do I have to be very familiar with the components of Oracle 8.1.7, before I install patches?

This extract from an Oracle article should answer to your questions :
On a regular basis Oracle provides patch sets that include generic and port specific fixes encountered by customers since the base product was released. This delivery mechanism is similar to the Microsoft Service Packs. Patch sets increment the 4th digit of the version number i.e. 8.1.7.1.0 to 8.1.7.2.0, these patch sets are fully regression tested in the same way that the base release is (i.e. 8.1.7.0.0). Customers are encouraged to apply these fixes.
If a customer encounters a critical problem that requires a fix prior to the next patch set becoming available, they can request that a one off fix is made available on top of the latest patch set. This delivery mechanism is similar to the Microsoft Hot Fixes and is known as a Oracle patch set exception (or interim patch). Unlike Unix platforms these patch set exceptions are delivered in a patch set exception bundle, which includes all fixes since the current patch set.
Patch set exceptions Prior to Oracle 9.x
Patch set exceptions increments the 5th digit of the version number i.e. 8.1.7.2.2 to 8.1.7.2.3, these patches are only unit tested and include all one off fixes since the last patch set. Customers should only apply these fixes if they have a problem fixed by one of the patch set exceptions.
Patch set exceptions from Oracle 9.x
From Oracle release 9.x onwards exceptions no longer increment the version number. The 5th digit will remain at 0 and the bundle will be known as Patch n (Patch Bundle n), where n represents the one off patch level (e.g. the first occurrence of this policy was 9.0.1.2.0 Patch 1 which must be applied on top of Patch Set 9.0.1.2.0). These bundled patches include all one off fixes since the last patch set and are only lightly tested (unit tested). Customers should only apply these fixes if they have a problem fixed by one of the patch set exceptions.

Similar Messages

Understanding Patch Clusters

I'm wondering if anyone has looked at the various patch clusters available on Sunsolve in detail:
e.g. For Solaris 10 SPARC there's the following:
     Solaris 10 SPARC 05/08 Patch Bundle Chunk 1/2/3
     Solaris 10 Sun Alert Patch Cluster
     Solaris 10
The first one supposedly brings you up to date as per the 05/08 media. It's the other two I'm puzzled about. The latter one is the "recommended" patch cluster and the definition of this is almost exactly the same as the definition for the Sun Alert Patch Cluster - and I believe there is a possiibility that these may be combined in future?
Anyway, digging deeper - the 2 clusters each have 119 patches included, and the only difference I can see is that despite both clusters being dated Sep 2008, the Recommended cluster has latest revisions of each patch whereas the Sun Alert one has many which are many revisions obsoleted (cf 118712-22 vs 118712-08).
This is backed up by the fact that the Sun Alert cluster is considerably smaller that the recommended one.
Anyone understand why there are these discrepanices?
Regards,
GXW

Thanks. That's a lot clearer now - so they do contain the same patches - the alert bundle contains the minimum level of each patch which fixes a know alert - and the recommended bundle contains the highest available versions of those patches.
Can I ask a follow-up question? If I do a "smpatch update" with my patchpro.patchset set to "current", which of the 3 patch bundles listed in my original post does this equate to?

Luupgrade -t does not understand patches with a .jar extension?

Hello,
The man pages for luupgrade reads like the below should work, but the command errors out. Does luupgade work with .jar patches? Command and ERROR is below. Along with list of patches I am trying to install.
epicbuild:/u1> luupgrade -t -n vx-rootdg02 -s /u1/SunPatches 'cat /u1/plist'
Validating the contents of the media </u1/SunPatches>.
ERROR: The media </u1/SunPatches> does not contain any software patches that can be installed.
epicbuild:/u1> ls -l /u1/SunPatches
total 79120
-rw-r--r-- 1 root other 174383 Jun 11 12:33 112834-06.jar
-rw-r--r-- 1 root other 5923240 Jun 11 12:33 113073-14.jar
-rw-r--r-- 1 root other 836345 Jun 11 12:33 113277-52.jar
-rw-r--r-- 1 root other 152780 Jun 11 12:33 114127-03.jar
-rw-r--r-- 1 root other 150255 Jun 11 12:33 114129-02.jar
-rw-r--r-- 1 root other 31616 Jun 11 12:33 116532-03.jar
-rw-r--r-- 1 root other 15678612 Jun 11 12:34 117171-17.jar
-rw-r--r-- 1 root other 17450644 Jun 11 12:35 118558-39.jar
-rw-r--r-- 1 root other 522 Jun 11 12:35 patchpro_dnld_2007.06.11@12:35:55:CDT.txt
epicbuild:/u1> cat /u1/plist
113277-52
112834-06
114129-02
114127-03
113073-14
116532-03
117171-17
118558-39
epicbuild:/u1>
Any suggestions on how I get the above patches applied to my alternate boot env?
If a patch requires the system in single user mode does that apply if applying the patch via luupgrade?

Hi,
I've hit the same problem, but I don't understand your solution. Are you saying the answer is no, luupgrade doesn't support .jar files and you have to "jar xf" each patch file?
Graham

Help understanding patch set 10.1.2.3.0

Server: windows server 2003
OAS: 10.1.2.0.2 Installation Type Forms and Reports Services (only)
Developer Suite: Forms [32 Bit] Version 10.1.2.0.2 (Production)
My problem is I need to install this 10.1.2.3.0 patch to fix the "sticky cursor" issue. It appears after reading the documentation for the patch that it also has many components for a full blown installation of OAS. We are only running "Forms and Reports Services ", i.e. only the infrastructure for Forms and Reports.
So my question is if I install this patch will it try and "upgrade" us to a full blown install of OAS? Also, is there a way to only install what's needed for forms and reports?
Thanks,
Whitney

No it will not upgrade your AS to a full blown AS (this is also mentioned in the release notes if I'm correct).

How to understand patch level

Hi experts.
I have this problem.
In my development portal, I see, under the System Administration->System Configuration->Collaboration the entry "Transports"
Instead,
in my production portal, I see, under the System Administration->System Configuration->Collaboration the entry "Groupware Transports"
The systems are EP 7.0 SPS level 17 but I have some doubts about the same patch level.
How can I see which is the patch level component of the above mentioned entries "Transports" and "Groupware Transports" ?
Thanks for your help.
Mario.

Mario,
https://wiki.sdn.sap.com/wiki/display/EP/Howtofindoutportalversion%2Cpatchlevelinformation%2Ccomponentsinstalledandsystemlevelinformation
Try accessing this url for your portal http://server:port/sap/monitoring/ComponentInfo with a System Admin Id
Good Luck!
Sandeep Tudumu

Applying 9.4.x patches - preventing Reader from shutting down and IE8 crashing?

So our base package is a 9.4.0 and trying to deploy the 9.4.2, 9.4.3 and 9.4.4 patches to thousands and thousands of users but without impacting them at the same time. This is on Windows 7.
I've been having no success in deploying these patches where it must meet these following requirements:
- do not prompt the user to close reader, cancel or ignore if Reader is opened
- and if I do suppress the above prompting, the Reader patch will go ahead and close Reader which I do not want to do.
As I understand, patching using MSP, you should have the ability to delay the completion of the updates when the workstation is rebooted because Reader is still running and thus certain files can't be updated, which is what we do with pretty well every other application that uses the MS Installer but the Reader patches seems to do it's own thing.
Lastly, when I have IE8 and Reader opened, and the PDF is already configured to open outside of the browser, during the 9.4.4 update, IE will crash because of the data execution protection has caught an exception with the ADobe PDF Link Helper:
Log Name:      Application
Source:        Application Error
Date:          5/26/2011 1:29:48 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      ----------
Description:
Faulting application name: iexplore.exe, version: 8.0.7600.16722, time stamp: 0x4d0c2f29
Faulting module name: AcroIEHelper.dll_unloaded, version: 0.0.0.0, time stamp: 0x4c9aa77e
Exception code: 0xc0000005
Fault offset: 0x734b6294
Faulting process id: 0x4f8
Faulting application start time: 0x01cc1bc877e6b8b9
Faulting application path: C:\Program Files\Internet Explorer\iexplore.exe
Faulting module path: AcroIEHelper.dll
Of course if I have IE closed then this doesn't occur but we can't force closing IE on the user as they could be doing something critical.
Anybody have any ideas how to workaround these two problems? At most, I could deploy 9.4.3 and just deal with the irritated users when Reader closes on them unexpectingly but the 9.4.4 patch can't be deployed because of the crash.

Also here is the power report although i dont think this is a power issue as it works when not charging.
Battery Information:
Model Information:
Serial Number:    W0010P8BMBWZA
Manufacturer:    SMP
Device Name:    bq20z451
Pack Lot Code:    0
PCB Lot Code:    0
Firmware Version:    201
Hardware Revision:    000a
Cell Revision:    158
Charge Information:
Charge Remaining (mAh):    5816
Fully Charged:    Yes
Charging:    No
Full Charge Capacity (mAh):    5854
Health Information:
Cycle Count:    604
Condition:    Normal
Battery Installed:    Yes
Amperage (mA):    0
Voltage (mV):    12474
System Power Settings:
AC Power:
System Sleep Timer (Minutes):    30
Disk Sleep Timer (Minutes):    10
Display Sleep Timer (Minutes):    20
Wake on AC Change:    No
Wake on Clamshell Open:    Yes
Wake on LAN:    Yes
Current Power Source:    Yes
Display Sleep Uses Dim:    Yes
GPUSwitch:    2
PrioritizeNetworkReachabilityOverSleep:    0
Battery Power:
System Sleep Timer (Minutes):    30
Disk Sleep Timer (Minutes):    10
Display Sleep Timer (Minutes):    20
Wake on AC Change:    No
Wake on Clamshell Open:    Yes
Display Sleep Uses Dim:    Yes
GPUSwitch:    2
Reduce Brightness:    Yes
Hardware Configuration:
UPS Installed:    No
AC Charger Information:
Connected:    Yes
ID:    0x0100
Wattage (W):    85
Revision:    0x0000
Family:    0x00ba
Serial Number:    0x00aa062d
Charging:    No

Patchset vs patches

Hi all,
I am not a DBA and am a bit confused about patches and patchsets.
I have read about them and I would just like confirmation, please.
From what I understand:
Patches are individual fixes for the Oracle database, which you can install one by one.
Patchsets instead contain all fixes to bugs that have been found in the version of Oracle Database in question, and get released not as frequently as Patches, i.e. once a quarterly.
If this is the case, can I assume that patchset for Oracle 11.2.0.2 released in July 2011 would contain all the fixes of individual patches for Oracle 11.2.0.2 released up to July 2011?
i.e. would this patchset coniatn the fix for Patch 9824435: ORA-600: INTERNAL ERROR CODE, ARGUMENTS: [KOKEGPINLOB1] that was released on 23rd March 2011?
My assumption is yes.
How can I determine what patchset has been installed against a DB (the opatch seems to only return patches) and what was fixed within that patchset?
Thanks very much in advance.

mBk77 wrote:
Could you just clarify, please:
The reply from 909592 seems to indicate that the July 2011 patchset would change the version from 11.2.0.1 to 11.2.0.2 applying all the individual fixes for 11.2.0.2. (11.2.0.1 not 0.2)Yes, if you apply all the patch sets till July 2011 then your db version will change to 11.2.0.1
The link from mbk77 seems to indicate that the July 2011 patchset may contain all the fixes for 11.2.0.2 up to July 2011. The article also seems to indicate that if you use PSU you should not go back to install individual patches.If you apply the all the CPU available then there is no need to apply the individual patches which were relesed prior to that.CPU contains only commulative cpu patches. And cpu patches are only security patches.
>
>
So, if the DBA states that the install of 11.2.0.2 was done with all the psu up to and including July 2011, could I assume that patches released for 11.2.0.2 prior to July 2011 (as per the example earlier mentioned) have been included?Oracle Critical Patch Updates (CPU) will contain both the PSU and CPU, so the DBA may choose to apply a whole CPU or only the selected patches in the PSU patch bundle.This is not correct AFAIK. CPU doesn't contain PSU(patchset update , which includes the BUG fixes). CPU only contains the security patches. However PSU does contain the CPU patches.
>
Go through the below doc once...
http://www.oracle.com/us/support/assurance/leveraging-cpu-wp-164638.pdf?ssSourceSiteId=otnen
@OP,
Its recommended to apply latest PSU based on your release i.e 11.2.0.2.0 (this will include all previouds PSU as well as CPU).
The Database Patch Set Updates and Critical Patch Updates that are released each quarter contain the same security fixes. However, they use different patching mechanisms, and Patch Set Updates include both security and recommended bug fixes. Consider the following guidelines when you are deciding to apply Patch Set Updates instead of Critical Patch Updates.
Critical Patch Updates are applied only on the base release version, for example 11.2.0.x.0
Patch Set Updates can be applied on the base release version or on any earlier Patch Set Update. For example, 11.1.0.7.2 can be applied on 11.1.0.7.1 and 11.1.0.7.0.
Once a Patch Set Update has been applied, the recommended way to get future security content is to apply subsequent Patch Set Updates. Reverting from an applied Patch Set Update back to the Critical Patch Update, while technically possible, requires significant time and effort, and is not advised.
Applying a Critical Patch Update on an installation with a Patch Set Update installed is not supported.
For more information on Patch Set Updates, see Note 854428.1, Patch Set Updates for Oracle Products.Hope this help

What is the best approach for patch management

Hi,
I'm new about patch management. I would like to ask you how manage patch on few Solaris 10 servers using command line.
I would like to know:
1. Using only command line how to download latest patches
2. There are some dependencies how to check this and install only those patches which meets dependecy requirements?
3. Is there possiblity to atomate this?
4. Is it possible to have one patch server and others servers will download and install this patches?
5. What if some patches are not installed?
6. How to find out which patches are necessary and which patches don't have to be installed? Or maybe or patches to be installed?
7. Could you please describe your approach for managing patches? Or maybe you can recommend some books/web page/articles that can help me to understand patch management.
Thanks in advance,
Daniel

smpatch is the command line tool to manage solaris patching. first you need to register yours system - this can be done using sconadm, detailed here:
http://sunsolve.sun.com/search/document.do?assetkey=1-9-82688-1
smpatch analyze will list all required patches and resolve dependencies. smpatch download will download all the required patches, and smpatch update will apply them. You can set up a Local Patch Server to download patches, then your clients will download the patches they require from it. This is detailed in chapter 6 of the update connection admin guide

Patching on PRD system and thereafter moving the logs to DR ?

Patching on PRD system and thereafter moving the logs to DR, will the patches take effect in DR ?
We have patched our PRD system to the latest APPL patch levels, we have a DR system in place, the link for which was disabled before we started our patching process. The DR system was successfully patched before taking up the activity on PRD.
The link between the PRD and DR is still not restored.
Now, that our PRD system is on the latest patch levels, my idea is restoring a full offline database backup of PRD on the DR system should make the DR system exactly identical to the PRD and the link between the two restored to allow for dynamic syncing thereafter.
Is my above view correct ?
Moreover, from my understanding, Patches are a bunch of SAP notes, SAP notes in-turn are basically code corrections for some objects, which ultimately means some entries are either written or deleted from database tables. My colleagues are of the view that instead of patching the DR server separately we could have actually restored the link and transferred the logs to the DR and the patches should have taken effect in the DR SERVER, is this alright ?
From my past experience I am aware that once you restore an offline database backup onto any system, the patch level in the target system would become similar to the source system(the system whose offline backup is actually being restored).
Thereby request the experts on the forum to give their views on the above.
Many Thanks in advance

when we take up any patching activity, can we just do it on the PRD and then move on the logs to the DR and the DR should also be on the same patch levels as PRD. ?
Yes, its a normal patching process for Primary-->Secondary setups.
You have to apply the application patches only on Production, then sync process takes care on DR (No need to apply the pathces here, infact you don't need to touch your exisiting DR system).
As a best practice - Just perform a Quality refresh before performing patching activity, then you can perform your test Patching/Upgrade activity in your Quality system itself (Not on DR).
Regards,
Nick Loy

Request: public patches

Is it possible to make patches for certain bugs available on a certain webpage? Sometimes patches are available which we don't know about (because I don't have the time to read every forum posting out there). If a patch is available, and you know about it, you first have to e-mail an Oracle employee and have to wait for his/her response. I must admit, today I got a response in only *5 minutes* (thank you Steve)! But like I said most of the times we just don't know that a patch exists. And I don't know if for each fixed bug a patch is created, but every patch is welcome! Because without a patch we need to wait another x months for a new release which fixes the problem... :( And I understand patches might not be "stable" enough to be released in the public, but everything is better then a broken feature! And if you guys don't want to reponsible for any problems we have with the patch just put a notice on the webpage. Another great thing about making the patches available to the public is that they get tested better! This way you guys can be sure of a much more stable future release. :)
So in short, making patches public is better for everyone! :)
Regards,
Peter

We are presently in the testing stage of a small BC4J/JClient patch that will be made available on Metalink and/or OTN. It will include the following fixes (many of which directly resulted from customer problem reports here in the forum after we shipped 9.0.3 Production):
[list=1]
[*]2675805 DMLEXCEPTION IS THROWN WHEN AN AM IS CHECKED OUT AFTER THE DB IS BOUNCED
The application module pool was throwing oracle.jbo.DMLException after the database had been restarted. Workaround is to set jbo.doConnection pooling to true.
[*]2673596 NPE CREATING SESSION FACADE AM AND TESTING
When running an EJB application module in the tester, you must first run the EJB session bean. Previously, if you did not do this a NullPointerException was thrown. This has been fixed so that an error dialog is displayed instead.
[*]2651507 UPGRADING APP FROM 9.0.2 CAN PRODUCE EXTRA FORMAT & FORMATTER MESSAGE BUNDLES
Migrating some applications from 9.0.2 to 9.0.3 produced extra and unnecessary message bundle files containing the formatter information. These files are no longer created.
[*]2646690 CLASSCASTEXCEPTION USING PCOLL PASSIVATION SPILL TO DISK IN OC4J 9.0.3
When using the JDBC 9.0.1.4 driver that ships with JDev 9.0.3 production, view row spillover was causing a ClassCastException when deployed in the 9.0.3 OC4J container due to a change in JDBC behavior for J2EE 1.3 compliance which the OC4J container sets by default (the driver itself doesn't, but OC4J forces the J2EE 1.3 compliant behavior to ON). This changes the return type of a database DATE field from Timestamp to Date, explaining the classcastexception in this case.
[*]2633087 NAVIGATION LOST IN UIX JSP PAGE WHEN CLICKING HIDE/SHOW DETAIL
In a simple UIX JSP application with Browse Form (with Hide/Show) option, navigation to the second page and clicking the Show/Hide would cause the record indicator to jump back to the first count.
[*]2631283 INSERTED DETAIL EO IN COMP. ASSOC. REMOVED ON SETATTRIBUTE ON FK
In a composition association, new details were not being added to the entity cache if they were in initialized state. This resulted in new detail rows being lost in the case where setAttribute was called on the foreign key attribute after a call to super.create()
[*]2623957 MASTER/DETAIL EO GETTER RETURNS NULL IN COMP ASSOC WHEN EO NOT DIRTY
For two entity objects joined by a composition association, calling the getMasterEO() accessor in the detail EntityImpl class was returning null - unless the master entity object had previously been changed.
[*]2612483 VO WIZARD PROBLEM WITH PASSIVATE CHECKBOXES
Previously passivation of transient attributes could be set only at the view object level, in the tuning page of the view object wizard. Now passivation can be enabled for individual transient attributes.
[*]2606781 RANGE SIZE -1 IS NOT PASSIVATED
This problem occurred when a view object's range size was changed and then the view object was passivated. The new range size was not being saved.
[*]2606626 NEW ROWS NOT PASSIVATED WHEN EXECUTE QUERY CALLED AFTER INSERTING ROWS
New view rows were not being passivated when the view object's max fetch size was set to 0.
[*]2131423 CAN'T CREATE VIEWLINK WITH NON-SQL DESTINATION VIEWOBJECT
This bug applied only to view objects with no SQL and only transient attributes: it was not possible to create a view link to these types of view objects.
[*]2632152 ERROR ON FOCUS-OUT AFTER SELECTING FROM BOUND POPLIST
In some JClient applications, selecting a value in a combo box and then switching focus out of the panel was causing an exception to be thrown (oracle.jbo.domain.DataCreationException).
[*]2625613 JULABEL DRAWS DISABLED TEXT FOR NON-UPDATEABLE FIELD
When a JULabel was bound to a view object attribute that was mapped to a non-updatable entity object usage, the JULabel was displayed as disabled. It's already not editable being a label, so disabling it was unintended, especially as this makes the display-only data harder to read for the user.
[list]

Can't open files in Camera Raw while in Bridge CS6

05/30/2014
Believe this issue/problem happened after automatic update from Adobe (but can't be sure).
Have always uploaded files from camera into Bridge then do some editing by opening JPEG and RAW (NEF) files in Camera Raw from Bridge.
Now, "Open in Camera Raw" is greyed out and I am unable to find a way to open files with Camera Raw from inside Bridge CS6. This seemed to happen suddenly and without any new software or applications being added to computer. All other apps/software working well.
Have tried various fixes found on Adobe community discussions without success. Problem now ongoing for over a week +.
Am able to open files in Photoshop with no problem but want to be able to do some quick edits using Camera Raw opening files from Bridge CS6.
I'm using Bridge CS6 Version 5.0.2.4. (as part of Adobe Creative Suite 6). Updater states I have most current version of Bridge installed.
I'm using an iMac computer with Intel Core i7 processor
OS X 10.8.5
Have found others with this same or very similar problems on forums but either can't understand patches/directions or unable to complete instructions on my computer.
for example see: Camera RAW update issue with Bridge CS6
From that link/discussion, one finds this "solution":
After you update to Camera Raw 8.4, Bridge CS6 in Mac OS doesn't display image metadata or allow you to edit images in Camera Raw.
To the top
Manually install the Camera Raw 8.4 plug-in.
Exit Adobe Bridge.
Download the file below.
Locate and double-click the downloaded file to decompress it. The resulting file is Camera Raw.plugin.
Navigate to the Macintosh HD folder.
Open the Library/Application Support/Adobe/Plug-Ins/CS6/File Formats folder.
IMPORTANT: Navigate to the root Library folder on your hard disk, not the Library folder under your user folder.
Copy the Camera Raw.plugin from step 3 into the File Formats folder.
IMPORTANT: This new file overwrites the file already in this folder. It's important that only one Camera Raw.plugin file is in this folder.
Open Adobe Bridge.
Camera Raw.plugin.zip
Mac OS Camera Raw 8.4 plug-in for manual installation
However, when I try the above, I have these issues:
1. When I double click on the downloaded file, my computer opens PhotoShop and an error message is displayed that states "Could not complete your request because Photoshop does not recognize this type of file." (I suspect this may mean my computer has automatically decompressed the file, but I am not certain of that).
2. Not completely certain I know how to "Navigate to the Macintosh HD folder" as suggested in step 4. above (OK, I'm new to Mac; long-time PC user….)
3. When I am in "Finder" and click on "GO" while holding down "Option" key, I find "Library". within that, I can find "Library/Application Support/Adobe" but there is no "Plug-Ins" folder within the "Adobe" subfolder.
4. Not sure how to tell if I am in the "root Library" on my hard disk vs. "Library under my user folder". (Again, new to Mac….)
I have NOT yet tried doing an "Uninstall" and then Re-installing the whole Adobe Creative Suite 6 and would like to avoid that if possible.
Would absolutely LOVE it if Adobe would simply push an update that would fix this problem or if someone would explain to me how I could restore the earlier version that worked perfectly for me.
Any help, suggestions (in very basic, simple terms that any idiot new to the world of Macintosh can understand) would be appreciated. Very frustrated with Adobe at the moment.
Mostly have liked the switch to Mac, but with this and my photo workflow coming to a screeching halt, having second thoughts. (But I suppose Adobe update for PC may cause problems as well.)
Thanks in advance for any help/suggestions.

05/30/2014
Literally minutes after I posted the above, I figured this out myself and now I'm a happy camper and things are back to normal!
Here was my error/issue: as a new Mac user, I was not negotiating/finding files on my hard drive correctly.
In case there are others out there with this same issue (and as dense as I apparently am ):
Here is what I did that resulted in a fix:
First Steps:
1. Quit/close Bridge
2. As noted in post above, go to this link to download Camera Raw Plugin file:
Camera RAW update issue with Bridge CS6
Link to get to download is near end of instructions, but I will attempt to insert that link to download here:
Camera Raw.plugin.zip
3. Once file has been downloaded, find it by using "Finder" Click on "Finder" and look on list of options on left side of Finder window to find "Downloads". On my computer, when clicking on "Finder" these options appear in the list at the left:
All My Files
Airdrop
Applications
Desktop
Documents
Downloads
Movies
Music
Pictures
4. Download you just did should be at or near the top of your downloads list and should be named as "Camera Raw.plugin" and will be 83.5 MB in size
5. I right-clicked (two fingers on touchpad) to bring up drop down options and selected "Copy 'Camera Raw.plugin'" from that list to copy file.
Now, you have copied the plug in that will fix this issue. The second set of steps below will walk you through how to replace the file that is on your hard drive with this plug in file that you have copied.
Second set of steps (and this is where, as a new Mac user, I was confused initially)
1. Again, click on "Finder" on your Mac
2. On top of screen, find "GO" and click on that. (You should see "Finder" in the upper right corner of your screen, then "File, Edit, View, GO, Window, Help" Click on the GO
3. In drop down menu that appears, click on "Computer"
4. Then, double click on "Macintosh HD" to open your hard drive
5. Next, double click on "Library" folder to open that.
6. Next, click on "Application Support" folder to open that.
7. Then, double click on "Adobe" folder to open that.
8. Then, double click on "Plug Ins" folder to open that
9. Now, double click on "CS6" to open that folder.
10. Finally, double click on the "File Formats" folder that appears.
11. NOW, you should see this:
12. Right click (two finger press if using a touch pad) to open window with options. Select "Paste Item" by clicking on that option.
13. You will be prompted with an option to keep existing file OR replace the file. Choose "Replace" to past the new "Camera Raw.plugin" file to this folder.
Finally, if you now go back and open Bridge CS6, you should be good to go.
Hope that helps someone out there.
Hopefully future updates will from Adobe will be better.

Applying Different Product Classifications To Different Groups

Sorry if I'm missing the obvious here, but I see no way of applying different product classification updates to different groups of PCs either through WSUS or through GPOs.
Originally in my environment we had one WSUS policy which my predecessor had rolled into the Default Domain Policy. In an effort to get away from this, and also to manage which types of updates get applied to which systems (critical and security updates
for some, and all updates to others) I created two new GPOs: WSUS > All Updates and WSUS > Selective Updates.
However, in configuring the GPOs I realized there is no way to designate the types of updates that are/aren't approved. So I went back to WSUS, and under the Options screen I opened 'Products and Classifications' and then switched to the 'Classifications'
tab. So here I can select/de-select individual update types, but there's no way for me to turn them on/off granularly. In other words, this seems to be a global setting.
So my question is this: How do I set up WSUS to automatically approve and install *only* security and critical updates for one group of systems, and automatically approve and install *all* updates for another group of systems? Do I need to use GPOs
in tandem with WSUS, or can WSUS do it on its own? Where would I go to configure something like this.
Sorry for the detail, but I'm really not seeing anything obvious anywhere and I can't believe I'd have to build a secondary WSUS server just to set up multiple classification groups.
Thanks,
Bob

Sorry if I'm missing the obvious here, but I see no way of applying different product classification updates to different groups of PCs either through WSUS or through GPOs.
That's because you don't. The WSUS server has one repository of updates, defined by Product Category, Update Classification, and Language. Updates are then targeted to computers by placing computers in a target group and approving an update for
that target group. All computers in the target group will evaluate each approved update, and if the update is installable, the computer will download and install the update.
Originally in my environment we had one WSUS policy which my predecessor had rolled into the Default Domain Policy. In an effort to get away from this, and also to manage which types of updates get applied to which systems (critical and security updates
for some, and all updates to others) I created two new GPOs: WSUS > All Updates and WSUS > Selective Updates.
So, all you really did here was declare two different WSUS Target Group(s). How you actually apply those GPOs to your client systems will determine which of either, or both, groups that a client system is a member of.
How do I set up WSUS to automatically approve and install *only* security and critical updates for one group of systems
You create an Automatic Approval rule to approve Security Updates and Critical Updates for THAT GROUP. (e.g. the "Selective Updates" group).
and automatically approve and install *all* updates for another group of systems?
You create an Automatic Approval rule to approve ALL update classifications for the "All Computers" group (note that you don't even need your "All Updates" group, you only need the "Selective Updates" group).
I will also take the moment here to severely warn you that approving ALL UPDATES for ALL COMPUTERS is a very dangerous thing to do, and frankly you don't even need a WSUS server to do that. Just enable Automatic Updates on the system and let 'em get their
updates from Microsoft directly and you'll have exactly the same behaviors with a lot less administrative overhead.
Additionally, based on the nature of the questions in this post, I would encourage you to thoroughly review these two resources in TechNet:
Understanding Patch and Update Management: Microsoft's Software Update Strategy
Manage Windows Server Update Services 3.0 SP2 in the WSUS Operations Guide
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

Getting S.M.A.R.T. when trying to install Mountain lion. Hard drive works pretty well. I understand that many users have been facing the same issue. Has apple patched it yet?

I'm getting S.M.A.R.T. error when trying to install Mountain lion. Hard drive works pretty well despite the Failing status. I understand that many users have been facing the same issue. My hard drive was/is working perfectly. Has Apple patched it yet?
Has someone found a solution which is not replacing the hard drive which works just fine? Or Is anyone aware of a procedure that can force the installation despite the S.M.A.R.T error? Below details of my hard drive
Thanks
ST31******ASQ:
Capacity:          1 TB (1,000,204,886,016 bytes)
Model:          ST31000528ASQ
Revision:          AP24
Serial Number:                      6V***5JR
Native Command Queuing:          Yes
Queue Depth:          32
Removable Media:          No
Detachable Drive:          No
BSD Name:          disk0
Rotational Rate:          7200
Medium Type:          Rotational
Partition Map Type:          GPT (GUID Partition Table)
S.M.A.R.T. status:          Failing
<Edited By Host>

If you haven't done so, run Disk Utility /Applications/Utilities
to run a live verification.
The drive may be ok at the moment, but that's not to say the drive may fail at anytime.
Hopefully you have all your important data backed up just in case.

Can somebody help me to understand/use MacPort patch files in terminal?!?

Hello everyone,   NOTE: I'm still trying to familiarize myself with mac terminal as I recently made the switch from Windows.
While I was searching online instructions for installing qt4-mac on 10.9 Mavericks I came accross thed macports ticket page for qt4-mac and I noticed that a lot of people are posting "patches" to download/apply so that it will work properly. I've successfully downloaded qt4-mac without having to download/apply patches manually, however I would like to know how to do it for future reference and bc I enjoy learning how to do new things.
The MacPort Patch guide provided basic instructions, but I am looking for some clarification on a few things. You don't have to answer every question any contribution is appreciated! Here are my main questions:
1. "create a unified diff patch file"   EXAMPLE: diff -u src/Makefile.in.orig src/Makefile.in > patch-src-Makefile.in.diff
What exactly is a unified diff patch file and it's purpose?
2. "Place the patch patch-src-Makefile.in.diff in the directory ${portpath}/files and use it in a port using the patchfiles keyword.${portpath} may be in a local Portfile repository during development, or files/ may be in a port's ${portpath} in the global MacPorts repository."   EXAMPLE: patchfiles patch-src-Makefile.in.diff    If fixing a particular problem or bug requires changes in multiple files -in those cases the patch filename should reference the problem or bug, for example: patch-<destroot_variable_fix>.diff
One of the patches listed on the macports ticket page is this: patch-src_corelib_global_qglobal.h.diffWould this be and example of "fixing a particular problem" using the syntax patch-<destroot_variable_fix>.diff???
3. I hope this isn't a dumb question, but How exactly do you download the patch file??
Example: On the macports ticket page one of the patches to download is:
   patch-src_3rdparty_clucene_src_CLucene_search_FieldCacheImpl.cpp.diff
When I click on the link for that specific patch it takes me to this page. I feel stupid for asking but how exactly do I download the patch?? Am I supposed to copy that the code from this page and paste it into terminal? Or is there a link or something else that I am not seeing?
Thanks for any help it is GREATLY appreciated, and ALL answers/references are welcome!! Again you don't have to answer every question any contribution is appreciated!

Hmmm...I'm not sure why tcpreplay required a patch for me but it didn't work until I applied the patch. Oh well, it's working now so I'll leave it at that.
I agree that learning isn't easy, I know it will take a substantial amount of effort and practice working with OS X terminal before I reach the same comfort level I have with Windows. I haden't taken into consideration the amount of time it actually took me to get where I'm at now using windows. I suppose I just disregarded the time/effort I put into learning command prompt...now that I'm actually thinking about it; it took me several years.
For the most part the transition to terminal hasn't been all that difficult; having a strong understanding of the concepts makes it a lot easier, now it's just a matter of knowing the actual commands to use. For the purpose of my work I mainly stick to network troubleshooting, configuration, and admin commands and some scripting. BC I already know the windows command I usually only have to lookup the OS X equivelant or a close second that will get the job done.
Every now and then I do venture off into unfamiliar territory with command line, as was the case today. Now that I've read up on patch/diff commands I see that they are fairly basic; this just happened to be my first encounter with patches using macports so it was all somewhat new.
Thanks for the advice on building my own packeges rather than relying on macports, that will definitely give me a more in depth understanding of OS X terminal aside from my current strongpoints. Terminal and command prompt are so vastly different that I can be strong in many different aspects of command prompt, but a complete beginner with any terminal commands that deviate from the networking commands.
But if I want to skillful in all aspects I have to put in the time and effort, thanks for the help and advice. If you have anymore advice I'm all ears, otherwise thank you and take care!

POS-DM, BIW & R/3 posting issue after BIW patch updation

Landscape details:
SAP IS-Retail (ECC 6.0), SAP POS (Triversity GM 9.5.10), PI 7.0, BIW/POS-DM 7.0
Issue Detail
We have upgraded the patch level of Support package BI_CONT in BIW from 5 to 11 in production server and after that following issues have started:
1.     The duplicate posting started in R/3 i.e. if some POS EoD (TLog) file is already posted from POS-DM to R/3 and if the same file comes to POS-DM again then it gets posted in R/3 again. It was not happening before updating the patch, it used to get stop in POS-DM only.
2.     We have some EANs which starts with ZERO, those POS transaction doesnu2019t get posted in BIW Cubes and R/3 wherein the ZERO prefix articles exists. It stuck in POS-DM with the error u201CUnknown EAN/UPC numberu201D. But this error comes only if we enable the u201CMstr Data Filteru201D check from General Setting in /N/POSDW/IMG. If we disable this check then the data gets posted in R/3 but it doesnu2019t go in RSA7 & BIW Cubes.
3.     Before updating the patch the u201CMstr Data Filteru201D check was disabled and our posting was happening perfectly in R/3 as well BIW. What we understand is that, this check is required to pick the Article Code from masters with reference of EAN number which comes in POS TLog file and then it gets posted. We had written a ROUTINE in update rules to pick the Article Code from masters after truncating ZERO prefix from EAN, because the masters which we upload in R/3 with ZERO prefix EAN are getting updated in BIW without ZERO prefix.
4.    In the T-Code /N/POSDW/MON0, we are not able to change the status of processed transaction from 4 (completed) to 1 (ready) or vice-a-versa. Earlier we were able to do the same. This is required to re-process the transactions after doing the corrections in errors occurred at the time of first processing.
Regards
Amar Preet Singh

Hi
1)Duplicate posting in R/3 : check the 'Tasks' configuration WPUUMS & WPUTAB in /N/POSDW/IMG in POSDM.
2) Write a Routine in BI side to allow EAN's with prefix Zeros
3) master data filter is used to check the data with BI master data. Master data filter should always be used while data posting.
4) The status should be first changed from completed to cancelled/rejected and then cancelled to Ready status.
    Then you will be able to reprocess the posdm data to ISR.
Regards
Abhijit

Understanding Patches

Similar Messages

Maybe you are looking for