Pavan DBA's Blog

The DBA Knowledge Store

Archive for the ‘upgradation’ Category

Error while applying patchset to 10g database

Posted by Pavan DBA on October 31, 2010

Hi Friends, its been quite long time that we talked about technical articles….(its just because i got busy with new responsibilities). From now i will make sure, i will post some helpful posts regularly

Today, lets discuss about an error that occurs on windows box when you try to install patchset…

As we all know whether it is windows or unix machine, we need to stop all services before installing patchset software. Recently i was doing this in one of my prod env (windows box) and all of a sudden during installation, i got below error

“Error in writing to file D:\Oracle\product\10.2.0.2.0\bin\oraevrus10.dll”

I ignored this error thinking nothing will happen…but its my biggest mistake (thats the reason DBA should never think, he should know…and that knowing comes only by practise or testing in test machines)

After i ignore that error, everything went fine and when i try to run any command like sqlplus, dbca etc..i got below error message in a popup window

The procedure entry point kglsim_cln could not be located in the dynamic link library orageneric10.dll

This will happen because of the error i ignored during installation and that error will occur because one of oracle service will not be stopped sometimes (thats why i hate oracle administration on windows box ;-) )

I fighted alot with that and finally came with an idea of re-installing the patchset again. But to do this, we need to reboot the server. I am having 3 more databases of other versions on the same machine, but i can’t proceed further without downtime which was even confirmed by oracle support.

I informed the client about this and to my luck i got downtime (please do remember, this might not happen always. so we need to very careful and whenever you are doing the same activity in future, make client aware that you may require downtime)

After reboot, i started OUI and reinstalled the files and it went successful….

Note: After installing patchset, don’t forget to upgrade your database

 

Posted in upgradation | Tagged: , , , | Leave a Comment »

problem with not setting COMPATIBLE parameter

Posted by Pavan DBA on June 28, 2010

Today i am trying to perform multiplexing one of my production database. My database is using pfile, so i created spfile using

SQL> create spfile from pfile;
File Created

After that i thought of bouncing database so as to make it use spfile and then change control_files parameter.

But to my surprise i got below error while shutdown

SQL> shutdown immediate
Database Closed
Database Dismounted
ORA-00600: internal error code, arguments: [kqrfrpo], [0x095FFA460], [8], [], [], [], [], []

so here you can see, instead of saying “Oracle Instance shutdown”, it throwed an error. Immediately i checked in alert log file for more details and i got “SQL statement not found” statement followed by some addresses of registries in trace file.

I started searching in My Oracle Support (earlier known as Metalink) and found that it is a bug in databases 9.2.0.4 and 9.2.0.6 and it is fixed in 9.2.0.7 patchset.

But my database is 9.2.0.8. really interesting, isn’t it? :-)

SQL> select * from v$version;

BANNER
—————————————————————-
Oracle9i Enterprise Edition Release 9.2.0.8.0 – 64bit Production
PL/SQL Release 9.2.0.8.0 – Production
CORE    9.2.0.8.0       Production
TNS for Linux: Version 9.2.0.8.0 – Production
NLSRTL Version 9.2.0.8.0 – Production

I got a doubt on my compatible parameter and i found as below

SQL> show parameter compatible

NAME                                 TYPE                             VALUE
———————————— ——————————– ——————————
compatible                           string                           9.2.0.0.0

so from this we can understand that, someone who applied the patchset, didn’t modified this parameter which is causing prolems. finally i modified it to latest version and its resolved.

I had also seen many instances from my collegues who forgot to change this parameter and landed into unresolved problems.

So, Guys don’t ever miss this change while upgrading database to higher versions…

Posted in upgradation | Tagged: | 1 Comment »

warning while upgrading to 9.2.0.4

Posted by Pavan DBA on June 28, 2010

DOC>#######################################################################
DOC>#######################################################################
DOC>  The following statement may cause an
DOC>  ORA-29554: unhandled Java out of memory condition
DOC>  error.
DOC>  If so, this is because there is insufficient system tablespace,
DOC>  shared or java pool size, or some other resource value is too small.
DOC>  An additional message describing the problem will be output by
DOC>  the statement.
DOC>#######################################################################
DOC>#######################################################################
DOC>*/

you may see above warning when upgrading 9.2.0.1 database to 9.2.0.4 at post installation script execution.

If you follow the upgrade document, you will see a note to have your SYSTEM tablespace left with atleast 10MB of free space and also shared and java pool with 150MB of size each.

If not, your script will fail here and don’t be panic. go back to your database and do the above mentioned modifications and re-ran the script.

Note: It is always preferred to follow upgrade document

Posted in upgradation | Tagged: | 2 Comments »

 
Follow

Get every new post delivered to your Inbox.

Join 1,477 other followers