Oracle Point, Oracle Life.

Oracle DB version: 9.2.0.6
OS: SUN solaris 9 (SPARC 64 bit)

Pre-installation:

Note: These are pre-install steps that should be done just before the maintenance window starts

1. Make sure you have Perl 5.00503 (or later) by issuing command “perl -v”

2. You must use OPatch version 1.0.0.0.54 or later. (I used OPatch 1.0.0.55, available at
metalink with Patch#2617419) (version check by issuing “opatch version”)

(If not, install it. To the $ORACLE_HOME directory copy the
p2617419_10102_GENERIC.zip and unzip it:

cp p2617419_10102_GENERIC.zip $ORACLE_HOME/
mv $ORACLE_HOME/OPatch/ $ORACLE_HOME/OPatch.bak
cd $ORACLE_HOME
unzip p2617419_10102_GENERIC.zip)

Check again the current version and if it works:

$ORACLE_HOME/OPatch/opatch lsinventory

3. Before starting the installation check whether “java” and “jar” executables are present in
your Oracle Home. In a standard Oracle installation, “java” is available in
$ORACLE_HOME/jre//bin directory and “jar” is available in $ORACLE_HOME/jdk/bin
directory.

ls -l $ORACLE_HOME/jre/bin
ls -l $ORACLE_HOME/jdk/bin

If you don’t have a standard installation and these commands are not present, then invoke
the “opatch apply” command with the -jdk flag, specifying the full path to the JDK to be used.

4. Check if the following executables must be present in the $PATH: make, ar, ld, and nm.
Make sure the directory “/opt/SUNWspro/bin” and “/usr/ccs/bin” in $PATH

5. Copy the p4751921_9206_solaris64.zip file to your oracle’s home directory, unzip it there
and go to the 4751921 subdircetory.

unzip p4751923_92070_LINUX.zip
cd ~/4751923

Installation: NOTE: Service downtime starts here

1. Shutdown all instances and listeners associated to the ORACLE_HOME being updated:

lsnrctl stop
sqlplus “/ as sysdba”;
SQL> shutdown immediate;
SQL> exit;

2. Apply the CPU:

$ORACLE_HOME/OPatch/opatch apply

If you encounter any errors, please refer to the “Known issues” section of the 343384.1
document.

Post-Installation:

1. Start up all database instances running out of the ORACLE_HOME being patched and run a postinstallation script.

2. find invalide objects after patch installation

cd $ORACLE_HOME/cpu/CPUJan2006
sqlplus “/ as sysdba”;
SQL> startup;
SQL> select OBJECT_NAME from DBA_OBJECTS where status = ‘INVALID’;
SQL> @catcpu.sql;
SQL> exit;

Examin the log file. If you encounter any errors, please refer to the “Known issues” section
of the 343384.1 document.

3. If catcpu.sql reports any Invalid Objects, compile the invalid objects using the following:

cd $ORACLE_HOME/rdbms/admin
sqlplus “/ as sysdba”;
SQL> @utlrp.sql

Check again if invalid objects exist:

SQL> select OBJECT_NAME from DBA_OBJECTS where status = ‘INVALID’;
SQL> exit;

4. Start the listener:

lsnrctl start

DONE!!!!

Popularity: 3% [?]

Recently, we experienced a weird problem on using oracle discoverer.

Situation: Discoverer Client at version 4.1.37
Discoverer Administraion at version 9.0.4

Problem: Business Area changed on discoverer administration side will not applied in client side.

Solution:

1. Re-install Discoverer Administration Edition 4.1.37
2. Create a new Oracle account with SELECT on DDEF2000 tables
3. Log into the 4.1.37 Admin tool using the new account and create a new EUL
4. Reconnect as owner of the EUL and import the DDEF2000_DIST business area
5. Check the course level to make sure it is varchar
6. Give users’ access to the new EUL and the new business area
7. Get user to log on and use Tools/Options/EUL to set his EUL to the new EUL
8. Reconnect user and open a workbook to verify that his issues are fixed.

Note: It’s unbelivable that same software only with different version acts totally differently. There must be some significant changes on new version of oracle administration side. Also, experienced that new version didn’t accept importing of business area which is exported in version 4.1.37.

Popularity: 2% [?]