Silently Uninstall Oracle 10g from Windows 10 - oracle

Currently have Oracle 10gR2 running across a number of machines, I am trying to figure out how to silently uninstall it. No need to retain any data etc.
To install it we currently run the following :
#c:\build\buildfiles\oracle\oraclexeuniv.exe /s /f1"C:\build\buildfiles\oracle\oraclexe-install.iss" /f2"c:\build\buildfiles\oracle\oraclexe-install.log"
I can see from searching online that a similar method can be used to uninstall, but by calling a file with the correct parameters to facilitate an uninstall. However I cant find any information on what needs to be in this file.
This link https://community.oracle.com/tech/developers/discussion/2413545/silent-unistall-of-oracle-xe does have an example, but when I use that data in my Remove file, I get a error of -3 returned.
Any help greatly appreciated.

Related

Message file \ORANT\DBS\FMCUS.MSB not found Oracle Forms 6i

I install Oracle Developer Suite 6i on Windows 10 Professional 64-bit, but when i run form builder, its give the error \ORANT\DBS\FMCUS.MSB not found. but when i search this file in in installed 6i directory this file is exist there, when i google this error, i found a solution: its suggest me to run the form builder in compatibility mode of windows XP service pack 2. but still its show the same error given below:
Message file \ORANT\DBS\FMCUS.MSB not found
Kindly suggest me what should i do to get rid from this error. Thank You!
Typically errors like this mean the software does not know precisely where it is installed. A couple of options that might resolve this (I say might because that is some very old software you've got there).
Try setting ORACLE_HOME as an environment variable
Look in the registry for the the key which nominates where Forms is installed and set ORACLE_HOME there.
Create a batch file which sets ORACLE_HOME and then launches Forms
If you still have an old installation of Oracle Developer Suite. Look for the keys like :
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\KEY_OH155385982] and
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Oracle\KEY_OH267560998].
Export them as Key_ODS64.reg and Key_ODS64_Wow.reg, respectively.
Go to your new installation's machine and Import by double-clicking.

remove oracle multiple home

I don't know what I did. I accidentally installed multiple Oracle on my machine. It could have been that I did not realize I installed successfully. I end have 5 Oracle home folders
anyway, I kept having problem connecting to Oracle. SQL developer works, but sql/plus and C# have not been working.
There is a chance multiple Oracle Home cause the problems. I don't know. I decide to uninstall and reinstall again and see what happen
I run deinstaller. It removes successfully on dbhome_5 folder. The files in dbhome_5 folder still exist, I cannot uninstall Oracle in other 4 folders
dbhome_1
dbhome_2
dbhome_3
dbhome_4
Deinstaller could not detect anything. Therefore, I cannot uninstall
Those 5 instances still exist.
I can install against. That mean dbhome_6. I don't know it will create confusion again.
How to uninstall / completely remove Oracle 11g (client)?
This page tell us how to clean remove. I don't to do uninstall because I cannot. Do I have to manually remove all the files?
I just want the machines to have clean environment before the next installation
I have the feeling that was what happened before. I fail to configure. I uninstall. Then I have 5 folder
I am using Oracle 11 universal installer version 11.2.1.0
Thanks
Having done this before myself, I know how confusing it can get.. worse even, that the configuration for different oracle data access clients about which home to use can be in different places, so your sql plus can end up using one install whereas your c# is using another
I'd recommend to follow the manual removal instructions you found on the linked page; do it for every oracle home you can find (search your entire drive for e.g. tnsnames.ora)
Remove everything (maybe preserve any tnsnames you find as it will make configuring the reinstall a bit easier) and then reinstall it, just once this time:)

How to tell System.Data.OracleClient to use the 64 bit Oracle Driver

I am trying to run a .NET application which uses System.Data.OracleClient on a Win7 x64 workstation. The workstation has a 32bit Oracle client installed, which leads to the following error message:
Attempt to load Oracle client libraries threw BadImageFormatException. This problem will occur when running in 64 bit mode with the 32 bit Oracle client components installed.
So this is my long journey of tries and failures:
I tried to install the Oracle client win64_11gR2_client. But during the setup process it crashes without any comment.
I followed an answer from a different SO thread, tried and extracted the instantclient-basic-windows.x64-11.2.0.2.0, and put the folder containing the binaries in the windows PATH variable. I still get the same error message though (even after rebooting).
I followed the "alternative way" from this answer and copied the files oci.dll, orannzsbb11.dll, and oraociei11.dll into the bin/ folder of my web site project. Still the same error message.
I tried and copied all files from the instant client into that directory and tried again, without success.
I installed ODAC112021Xcopy_x64.zip and put the installation folder and the bin folder in the windows PATH variable. No success.
I put my hope on this answer and reviewed the DllPath in the registry (which is actually supposed to relate to ODP.NET as opposed to System.Data.OracleClient) and saw that DllPath points to the correct x64 installation of ODAC, so, if my application wasn't using System.Data.OracleClient, it should work,b but since it does use that, it still failed.
I googled and stackoverflew but didn't find anything else that the posts I already referred to.
I carefully crafted this SO question in the hope of getting any insightful advice from an enlightened SO user.
After getting the first answer from b_levitt, I tried and added the following lines to the Global.asax at Application_Start:
Environment.SetEnvironmentVariable("ORACLE_HOME", #"C:\OracleProducts\Odac-11.2.0.2.1-x64");
Environment.SetEnvironmentVariable("PATH", #"C:\OracleProducts\Odac-11.2.0.2.1-x64;C:\OracleProducts\Odac-11.2.0.2.1-x64\bin");
C:\OracleProducts\Odac-11.2.0.2.1-x64 is where I installed the ODAC 64 bit xcopy version. No success either.
On a related note, I even tried to force my .NET app into 32bit mode without success, but that's a different thing. I need a forward-looking solution, which means 64bit.
Your #5 should have worked but you also need to set the ORACLE_HOME environment variable. I've done this many times including recently with the very xcopy install that you are using. Please check out my experience with the xcopy install and let me know what kind of additional errors that you get.
In my case I was setting it up for asp.net, but winforms is even easier. You can open a cmd window, use the "set" command to set both the PATH and the ORACLE_HOME environment variables and then run your app from that same cmd window. Once you get the bugs worked out, you can use the Environment.SetEnvironmentVariable to set these within your code.
For the record, I do avoid installing the oracle client on client machines by handling all of the business logic via web services. That way I only need the oracle components on the web server.
I had the same problem you have. I found most of my answers through Oracle forums and here at stackoverflow. I can't post links for reference but I can give you some things to try out.
Also include OraOps11w.dll in your bin directory along with the other Oracle dll files.
Go to the project properties|Reference Paths, add C:\Windows\Microsoft.NET\Framework64\v2.0.50727 or C:\Windows\Microsoft.NET\Framework64\v4.0.30319 to the Reference paths depending on which framework version the project is using.
**Fuzzy part that I don't remember well: Remove the System.Data.OracleClient current reference and add the new reference from C:\Windows\Microsoft.NET\Framework64\v2.0.50727 or C:\Windows\Microsoft.NET\Framework64\v4.0.30319 to the Reference paths depending on which framework version the project is using.
See if the exception goes away.
FYI, Microsoft is dropping Oracle data provider (in ADO.NET) support in the near future. It currently works through .NET 4, but it is a good idea to start testing the native Oracle drivers.

Can I install postgresql8.2 via command prompt or running any batch or registry file?

Is it possible to install the entire database(postgresql8.2) via command prompt or batch file or registry file bypassing the trivial procedure for installation. But then to a question comes that, how can we supply default parameters such as name,password,language,default location of database? Currently I'm working on 'Windows XP' platform.
Thank you.
For 8.3 and lower the obvious answer is: http://pginstaller.projects.pgfoundry.org/ which supports or supported silent installations. For more recent versions, please read: http://forums.enterprisedb.com/posts/list/2135.page
Use of existing installers would simplify your life and be where I would start.
This being said there is no reason you can't generate a script to register dll's properly run initdb, etc. This will take some extra knowledge of both PostgreSQL and Windows, and will be mostly suitable for custom solutions (i.e. not cases where you merely are packaging software that runs with PostgreSQL). I don't think an complete answer can be given here because once you need such a solution you need to design your installation around if. Books could be written on that topic. The docs http://www.postgresql.org/docs/9.0/static/install-windows.html should get you started however since the only difference really between installing from source and installing from the precompiled source is just that you need to compile the source files first.
Failing that you could take a look at the binary zip packages. Typically these can be extracted and PostgreSQL can be run from inside them.

How come the unix locate command still shows files/folders that aren't there any more?

I recently moved my whole local web development area over to using MacPorts stuff, rather than using MAMP on my Mac. I've been getting into Python/Django and didn't really need MAMP any more.
Thing is, I have uninstalled MAMP from the Applications folder, with the preferences file too, but how come when I run the 'locate MAMP' command in the Terminal it still shows all my /Applications/MAMP/ stuff as if it's all still there? And when I 'cd' into /Applications/MAMP/ it doesn't exist?
Something to do with locate being a kind of index searching system, hence things these old filepaths are cached? Please explain why, and how to sort it so they don't show anymore.
You've got the right idea: locate uses a database called 'locatedb'. It's normally updated by system cron jobs (not sure which on OS X); you can force an update with the updatedb command. See http://linux-sxs.org/utilities/updatedb.html among others.
Also, if you don't find files which you expect to, note this important caveat from the BUGS section of OSX' locate(1) man-page:
The locate database is typically built by user ''nobody'' and the
locate.updatedb(8) utility skips directories which are not readable
for user ''nobody'', group ''nobody'', or world. For example, if your
HOME directory is not world-readable, none of your files are in the database.
The other answers are correct about needing to update the locate database. I've got this alias to update my locate DB:
alias update_locate='sudo /usr/libexec/locate.updatedb'
I actually don't use locate all that much anymore now that I've found mdfind. It uses the spotlight file index which OSX is much better at keeping up to date compared to the locatedb. It also has quite a bit more power in what it can search from the command line.
Indeed the locate command searches through an index, that's why it's pretty fast.
The index is generated by the updatedb command, which is usually run as a nightly
or weekly job.
So to update it manually, just run updatedb.
According to the man page, its database is updated once a week:
NAME
locate.updatedb -- update locate database
SYNOPSIS
/usr/libexec/locate.updatedb
DESCRIPTION
The locate.updatedb utility updates the database used by locate(1). It is typically run once a week by
the /etc/periodic/weekly/310.locate script.
Take a look at the locate man page
http://unixhelp.ed.ac.uk/CGI/man-cgi?locate+1
You'll see that locate searches a database, not your actual filesystem.
You can update that database by using the updatedb command.
Also, since it's a database, unless you do update it regularly, locate wouln't find files that are in your filesystem that arn't in the database.

Resources