I recently read a lot of claims that I could solve the problem that Oracle can't start normally after the shockpatch. I tried, I finally told the end of failure, so I made myself, combined some Oracle commands made a batch. Inside the startup group, this problem is solved. Let's introduce the production process in detail below:
System environment:
WINDOWS2000 PROFESSIONAL? ?? Oracle 8i
Specific implementation steps:
Step 1: Edit a batch file, I named qidong.bat.
The editorial content is as follows:
SQLPlus INTERNAL / ORACLE @ yxzdh @ a.sqlexit
content analysis:
This is a SQLPLUS that uses DOS mode YXZDH, (YXZDH is the Oracle instance I want to start), the meaning of using the interNal / Oracle login is to log in as DBA to perform subsequent operations.
@ a.sql: means executing a.sql script after login
EXIT ?????: Finally close the DOS window.
?
Step 2: Edit a SQL script (my a.sql).
The content is as follows:
Startup force pfile = d: /oracle/ora81/database/inityxzdh.oraexit
analysis:
STARTUP FORCE: Force startup instance.
Pfile = d: /oracle/ora81/database/inityxzdh.ora: Specify the instance to be started, note: You must find the path to the ORA file corresponding to the instance on your machine. This path is replaced.
Exit: Exit SQLPlus.
?
Step 3: Place the batch file (QIDONG.BAT) and the script file (a.sql) in the same directory (such a batch file can find a script file), then create a shortcut to the batch file (Qidong.bat) (Shortcut QIDONG), put this shortcut into the "Startup Group".
?
Ok, all things have been done, and you can see the results.
