Windows Store apps (Universal Windows Platform apps). Can run on.Net 4.0 or newer, or, if not available, on.Net 3.5 with reduced functionality (will work on Windows 7 or newer with no updates installed). Bulk Crap Uninstaller is licensed under Apache 2.0 open source license, and can be used in both private and commercial settings for. Dotnet-core-uninstall whatif -all-below 2.2.301 -sdk Step 3 - Uninstall.NET Core SDKs and Runtimes. Dotnet-core-uninstall remove uninstalls.NET Core SDKs and Runtimes that are specified by a collection of options. The tool can't be used to uninstall SDKs and Runtimes with version 5.0 or above.
This page shows the installation of Oracle Grid Infrastructure 11.2.0.4 which I performed as part of the Oracle Linux 6.7 with Oracle 11.2.0.4 RAC installation cookbook.
First of all we need to run the installer, making sure to unset any Oracle environment variables which might interfere with the installation process (to be honest I should also check the PATH environment variable here but I happen to know it's not got any Oracle stuff in it):
Having run the installer, we start by skipping the software updates:
We then choose the option to Install and Configure Oracle Grid Infrastructure for a Cluster:
At the Specify Cluster Configuration screen we add the SCAN Name of dbscan.local and then click on the Add button to add the second node:
This brings up the Add Cluster Node Information box, in which we can add dbserver02.local with its virtual IP address of dbserver02-vip.local:
Clicking OK takes us back to the Specify Cluster Configuration screen again. If not already configured, it's time to setup the SSH connectivity. Clicking on the SSH Connectivity button brings up the option to add the OS Password for the oracle user, after which we click Setup:
Once SSH has been configured we can move to the next screen, which allows us to Specify Install Locations. The Oracle Base location defaults to /u01/app/oracle but I've had to override the Software Location to /u01/app/11.2.0/grid. I've also chosen a password for the SYSASM user and set the OSASM group to be dba:
Next we need to configure the ASM disk devices. My initial ASM diskgroup defaults to DATA but I need to set the Redundancy to EXTERNAL because I'm using an All Flash Array which has built in redundancy. None of the devices I've allocated will initially show up because I need to modify the ASM_DISKSTRING parameter. I do this by clicking on the Change Discovery Path button:
I configured my LUNs with names such as /dev/mapper/oradata* and /dev/mapper/orareco* so I'll set the Disk Discovery Path value to /dev/mapper/ora* and click OK to return to the previous screen:
Now I can see my devices in the Add Disks box. I'll select all eight of the oradata* devices to place into the +DATA diskgroup, leaving behind the two orareco* devices for use later on when I configure the +RECO diskgroup:
The Perform Prerequisite Checks screen complains that I don't have enough swap space. However, I disagree – so I'm going to override it by clicking on the Ignore All checkbox and then clicking Next:
Now we're good to go. Here's the Summary screen, on which I will click the Install button:
After some time the installer asks me to Execute Configuration Scripts on both nodes as the root user:
So first I'll run the orainstRoot.sh script on each of my servers in turn, starting with dbserver01:
The output from dbserver02 is identical so I won't repeat it here.
Now I'll run the root.sh script on dbserver01:
App Uninstall 2 0 4k
You can see that, as part of the execution of this script on dbserver01, an ASM instance was created, the diskgroup DATA was created and then the OCR and voting disk elements of Grid Infrastructure were created.
Now to run the root.sh script on dbserver02. The output will be shorter because the cluster entities already exist – the second node merely needs to join the cluster:
On completion of this script for both servers I return to the Execute Configuration Scripts box and click OK. After a while I see the final screen telling me that the installation was a success:
My cluster is now active. I can check this by setting my environment to the corresponding ASM instance and then running the crsctl command:
Finally, I can use the ASMCMD utility to check that my diskgroup and underlying disks are all present and correct:
App Uninstaller Mac
Perfect!
Bulk Crap Uninstaller (in short BCUninstaller or BCU) is a free (as in speech and beer) bulk program uninstaller with advanced automation. It excels at removing large amounts of applications with minimal to no user input, while requiring next to no technical knowledge.
It can detect most applications and games (even portable or not registered), clean up leftovers, force uninstall, automatically uninstall according to premade lists, and much more.
You can read the manual here.
In its basic form BCU is easy to use by most users, but it also has tools useful for power users, system admins and developers. Some of the most notable features of Bulk Crap Uninstaller:
Very thorough installed application detection
BCUninstaller can detect, manage and uninstall applications from the following sources:
- Normal registered applications (same as Programs and Features and many other uninstallers)
- Hidden/protected registered applications
- Applications with damaged or missing uninstallers
- Portable applications (looks in common locations and on portible drives, configurable)
- Chocolatey packages
- Oculus games/apps
- Steam games/apps
- Windows Features
- Windows Store apps (Universal Windows Platform apps)
- Windows UpdatesApplications from all of these sources are threated the same - you can filter, export and automatically uninstall them in the same way.
Fast, automatic uninstall
App Uninstall 2 0 4 Hp
The main feature of BCUninstaller is its ability to fully or nearly fully automate the process of uninstalling multiple applications. BCU always attempts to use the application's original uninstaller to avoid issues found in uninstall managers that blindly remove files to achieve uninstall automation (e.g. failing to unregister context menu entries or services).
- Uninstall any number of applications in a single batch
- Minimal to no user input is required during uninstallation
- Uninstall multiple items at once to speed up the process (with collision prevention)
- Console interface can automatically uninstall applications based on conditions with no user input
- Quietly uninstall many uninstallers that don't support silent uninstallation
- Uninstall applications even if they don't have any uninstallers
- Uninstall applications by window, shortcut or directory
- Can handle crashing and hanging uninstallers
Other features
While detection and uninstallation are the two main features of BCU that receive the most focus, it also has many useful tools built on top of that framework.
- Find and remove leftovers after uninstallation
- Clean Program Files directories from unused or empty folders
- Manually uninstall any application, bypasing it's uninstaller (Force uninstall)
- Startup manager
- Application ratings
- Huge amount of data about applications is collected and displayed. User can freely browse, filter and export everything
- Filtering with common presets or based on fully custom rules with Regex support
- Verification of uninstaller certificates
- Large amount of configurability
- Can run user-specified commands before and after uninstalling
- Can run on .Net 4.0 or newer, or, if not available, on .Net 3.5 with reduced functionality (will work on Windows 7 or newer with no updates installed)
- Fully portable, settings are saved to a single file
BCU is translated to Arabic, Czech, Dutch, English, French, German, Hungarian, Italian, Polish, Portuguese (Brazil and Portugal), Russian, Slovenian and Spanish at the moment of writing this. More to come! If you want to help translate BCU to a new language or update and existing translation please start an issue or contact me through the feedback form.
The system requirements are fairly lax since BCU was designed to work on any PC it is thrown at. If it boots, the chances are BCU will manage to run on it.
- OS: Windows Vista or newer is recommended. BCU will also work on XP and 2003 with reduced functionality and possibly some bugs. Both 32bit and 64bit versions are supported.
- .NET: Recommended .NET 4.0 or newer, can run on only .NET 3.5 with reduced functionality.
- RAM: Around 300MB or more of free RAM.
- CPU: Doesn't really matter.
- Free space: 50MB or more.
- HDD: Anything will work, but slower drives can make scan times quite a bit longer.
Bulk Crap Uninstaller is licensed under Apache 2.0 open source license, and can be used in both private and commercial settings for free and with no obligations, as long as no conditions of the license are broken.
