|
Patches
|
|
|
|
 |
|
-----------------------------------------
MODPLSQL VERSION 3.0.9.8.5d ONE-OFF PATCH
-----------------------------------------
Date: August 18, 2004
o What is in this patch?
------------------------
-> This patch contains the following fix for Oracle Database
BUG#3559310 : 2004-S128E
BUG#3835940 : BACKPORT OF BUG 3559310 ON TOP OF VERSION 8.1.7
o What version can I apply this patch on?
-----------------------------------------
-> Oracle Database 8.1.7.x
o How to apply this patch?
-----------------------------------
1. Unzip the patch into a temporary directory. This directory will be referred
as %PATCH_DIR% in the rest of the steps.
2. Change your current working directory to %PATCH_DIR%
3. Identify the Oracle databases serviced by mod_plsql. You can get this
information by scanning the database connect strings defined inside your
Database Access Descriptors (DAD) for mod_plsql.
Here are the steps to get this information :
- Identify the setting for the environment variable WV_GATEWAY_CFG.
This information can be obtained by looking at the setting for
System environment variables inside the Windows Control Panel.
The default value for WV_GATEWAY_CFG is
<ORACLE_HOME>\Apache\modplsql\cfg\wdbsvr.app
- Open the file as pointed by this environment variable.
- Search for each unique occurrence of 'connect_string' and
use the database connection information to identify which database
instances need to be patched up.
- If a DAD does not explicitly specify a value for 'connect_string',
then identify the default database instance for your configuration.
4. For all such database instances,
a.) Verify that you can connect to the database
- Issue "sqlplus /nolog"
- At the SQL prompt, issue "conn sys/sys_password@conn_str as sysdba"
- Make sure that you can connect to the backend repository
NOTE:
The following Oracle database parameter settings could disallow
remote database connections as sysdba
- O7_DICTIONARY_ACCESSIBILITY = FALSE
- REMOTE_LOGIN_ PASSWORDFILE = NONE
If this is the case, either allow remote connections temporarily, or
upload the patch to the database machine and follow steps 1 through 4
to patch up the database.
For more details on these Oracle database parameters, refer to the
Oracle documentation.
b.) Invoke the following command to patch up the OWA packages in the SYS
schema
patch.cmd -m sysobjects -o <ORACLE_HOME> -c <conn_str> -p <sys_password>
5. Stop the Oracle HTTP Server
6. Issue the following command to patch up mod_plsql
patch.cmd -m midtier -o <ORACLE_HOME>
WARNING : The newer version of mod_plsql will not work against a
database which is not patched up as outlined in step 4.
7. Restart Oracle HTTP Server
o How to undo the patch?
-----------------------------------
The patch script backs up your older data under the following directory
<ORACLE_HOME>\Apache\modplsql\prepatch
If you run into problems while appyling the patch, you can revert back the
patch as follows:
1. Stop the Oracle HTTP Server
2. Undo the patch by recursively copying over the backed up files
Change your current directory to <ORACLE_HOME>\Apache\modplsql\prepatch
Issue the commands
xcopy /S * ..\
When prompted about Overwriting data, select "All"
copy bin\modplsql.dll <ORACLE_HOME>\bin
3. Restart Oracle HTTP Server
End.