| latest Microsoft patches and Oracle 8i [message #61382] |
Mon, 19 April 2004 16:13  |
JOHN
Messages: 182
Registered: April 1998
|
Senior Member |
|
|
Ok here's the setup:
Windows 2000 Server (all patched up)
Oracle 8i
There are two servers with that setup and everything has been working fine. Last Wednesday, April 14, Microsoft released some new security patches which were put on the servers on Thursday when I wasn't at work. So I found out Friday that no one can connect to either of the Oracle databases.
Tried a reboot still nothing working. When I'd try to connect from SQL Plus I'd get ORA-01034: ORACLE not available. So I checked the Services in Administrative Tools and noticed that the OracleServicedbname was at to Starting and it wouldn't say Started. Its startmode is set to Automatic and had been fine in the past. I can't stop, pause, or start the service. So the Oracle db isn't starting up.
So on one server I go to the command prompt and do svrmgrl then type connect internal then startup and everything fine for now for server 1. Everyone can connect to it unless it gets rebooted somehow. The second server (which I have nothing to do with really) has the same problem so I go in and do svrmgrl again, connect internal, (got prompted for a password which I wasn't given until today), and then I get ORA-12560: TNS: protocol adapter error, but it doesn't stop me from doing typing startup and then I get LCC-00161: Message 161 not found; product=RDBMS; facility=MGR.
I don't know a whole lot about Oracle DBs, I haven't delt with this server much in the past. I really think something in the lastest MS patches broke Oracle somehow. Well one DB I was able to get back running but the other I wasn't. Has anyone else had this happening from the latest MS patches? Can someone please help me out? I'm not sure what to do other than try uninstalling the patches and hoping that everything works again.
|
|
|
|
| Re: latest Microsoft patches and Oracle 8i [message #61384 is a reply to message #61382] |
Mon, 19 April 2004 20:33  |
JOHN
Messages: 182
Registered: April 1998
|
Senior Member |
|
|
Various error messages I have found in various logfiles:
TNS-12641: Authentication service failed to initialize
TNS-12631: Username retrieval failed
TNS-12638: Credential retrieval failed
TNS-4294967Message -1 not found; product=NETWORK; facility=TNS
TNS-12560: TNS:protocol adapter error
TNS-00530: Protocol adapter error
TNS-12514: TNS:listener could not resolve SERVICE_NAME given in connect descriptor
I'm assuming most of them are a result of the Oracle database not starting. I did uninstall a certain MS patch from the last batch that I thought would affect Oracle the most and the OracleServicedbname does start now correctly but still the database is not available. Any help would be really appreciated.
|
|
|
|
|
|
|
|
| Re: latest Microsoft patches and Oracle 8i [message #61465 is a reply to message #61445] |
Mon, 26 April 2004 12:46 |
Tony Newcome
Messages: 2
Registered: April 2004
|
Junior Member |
|
|
I also am receiving this problem. I have isolated it to the following:
My problem began after installing the Critical Microsoft security update: KB 835732.
I uninstalled this update, and Oracle is once again functional.
We are temporarily running without the critical update applied, but I am sure that this is not going to be a good long term solution...
|
|
|
|
| Re: latest Microsoft patches and Oracle 8i [message #61478 is a reply to message #61382] |
Wed, 28 April 2004 00:57 |
G. LAKSHMI NARAYANA
Messages: 1
Registered: April 2004
|
Junior Member |
|
|
I had Oracle 8i CD.
When I install that CD some components are not installed (Net 8 Assistent).Thus i had a problem of connecting through "scott/tiger".
The error is "TNS Protocol Adapter Error".
Would u please send me the details regarding the error inorder to overcome that situation.
|
|
|
|
|
|
|
|
|
|
| Re: latest Microsoft patches and Oracle 8i [message #61665 is a reply to message #61447] |
Fri, 14 May 2004 05:49 |
YvesJ
Messages: 1
Registered: May 2004
|
Junior Member |
|
|
Microsoft has published a Support Bulletin about MS Security Update MS04-011 conflicting with the automatic startup of Oracle databases version 8.1.6. at http://support.microsoft.com/default.aspx?kbid=841180
See also the following Oracle Metalink Support Notes:
620554.995 Re : ORADIM never finnishes on startup
514691.996 Re : MGPSVC.exe fails with Error 1067
Here are the different solutions:
1/ I found some indications that applying the highest Oracle patch (8.1.6.3) then Oracle patch 1963261 (see Oracle note 620554.995) might work.
These indications came late in the game for us, and I did not have a chance to verify this.
2/ Uninstall the specific update KB835732: (I’m sure you already knew this)
from Control Panel > Add/Remove Programs > Windows components > KB835732 > Remove
We decided against this because of corporate policies, and the Sasser infection made an even
more compelling case of “not going without proper protection”!
3/ Upgrade database to 8.1.7 or 9.2
8.1.7 is still supported (in the US) until the end of the year 2004.
Oracle Support was not very active in helping because 8.1.6 has been unsupported for 2 years.
Upgrading to 9.2 is our long term choice.
4/ Start the database manually.
Even though Services report OracleServiceSID as “starting”, the service is properly started, but the instance is not.
You can use SVRMGRL or SQLPLUS (as SYSDBA) to start the database manually, or automatically like below.
This is our short term choice.
Here are the instructions I sent to my plant DBA's
a- On the server, make the startup type of the Oracle Service MANUAL - Open a DOS prompt box and run:
oradim –edit –sid MySID –startmode manual (replace "MySID" with your own value)
Do not shortcut and change the startup type from the Services GUI. It won’t work properly!
b- Save the following script at the root of the C: drive, and name it start_db.bat
On line 2, substitute the SID and the password for your SYSDBA account
If Windows authentication is used (more secure), "/@MySID as sysdba" will suffice
Also change the PFILE referenced on line 3 to point to the correct location
@echo off
(set sql=sqlplus -s "sys/sysPassword@MySID as sysdba") &REM -- must be SYSDBA
(set pfile=C:OracleadminMySIDpfileinitMySID.ora) &REM -- Location init.ora
if not "%1"=="" (echo select * from session_privs where privilege like 'SYS%%';|%sql%)&goto:EOF
ping localhost -n 16 -w 1000 >nul & oradim -startup -sid laborsys -starttype srvc
ping localhost -n 16 -w 1000 >nul & echo startup pfile=%pfile%|%sql%
c- Test the connection privileges: (1) open a DOS prompt box, (2) run “CD”, and (3) run “start_db test”
If successful, the test will list the privileges for the session, and SYSDBA should be one of them
If it fails, it will report “ORACLE not available” or similar
This test is harmless, and can be run while in production.
d- Go to Control Panel > Scheduled Tasks, and double-click “Add Scheduled Task”
Browse to the start_db.bat file saved in step (b-), and click “Open”
Select scheduling option “When my computer starts”
Enter the local administrator credentials (or an Oracle DBA account) when prompted
Reboot - The database should start fine now
To check if the database is up, you can rerun the test in step (c-)
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
