FUNCTION DbReleaseNumber RETURN VARCHAR2 IS
VersionNumber VARCHAR2(20);
Compatibility VARCHAR2(20);
BEGIN
DBMS_UTILITY.Db_Version( VersionNumber, Compatibility);
RETURN VersionNumber;
EXCEPTION
WHEN OTHERS THEN
return(NULL);
END;
Note that not all patches leave their "footprint" in the versionnumber. For example, if you apply patch 8.1.7.1.2 to your database (after you have applied 8.1.7.1.1), you will still see 8.1.7.1.1 as your release everywhere.
Jurij Modic ASCII a stupid question, get a stupid ANSI
24 hours in a day .... 24 beer in a case .... coincidence?
Originally posted by sambavan To get this information you can check the oraInventory/Patches this would reveal you the patches that you have applied so far on to the database.
I stress again: this is true only if the pach has been applied through Universal Installer.
But some "minor" patches can not be applied like this - for them to be "installed" you simply has to copy bunch of exec and library files over the old ones. To keep track of such paches installed there is no other way than to have a good memory or good "document everything" habit.
And to answer jt: I don't think there would be a problem to reapply same patch again, unless it is lower than the highest patch allready applied. If the patch has to be installed by Oracle Universal Installer then the Installer will complain anyway.
Jurij Modic ASCII a stupid question, get a stupid ANSI
24 hours in a day .... 24 beer in a case .... coincidence?
Bookmarks