Oracle and more – Amardeep Sidhu

Few days ago i posted about DBAzine being down. I was just checking to see if its back.

Its rocking now.

Welcome back DBAzine.com

Just finished upgrading to WordPress 2.5. Everything seems to be working fine.

Another issue I just came to know that wherever i am using syntaxhighlighter to format the code, it doesn’t display properly in Internet Explorer. May be something to do with the plugin. Will try to fix it. It works fine in Mozilla.

Today I was upgrading 10gR1 to 10gR2 (10.2.0.1) on Linux x86. The upgrade went almost fine (except that I had to install one package and change few kernel parameters) but while running DBUA to upgrade databases, it gave an error:

Could not get database version from the Oracle Server component. The CEP file rdbmsup.sql does not provide the version directive

and

Start of root element expected. Upgrade Configuration file
'C:\Oracle10g2\cfgtoollogs\dbua\test\upgrade5\upgrade.xml' is not a valid XML file.

I searched in the metalink and found that this all happens due to customized glogin.sql file which was there in my case also. And removing that customization made DBUA rock

You might want to check here, here and here.

I registered on Twitter and my page is http://twitter.com/amardeep_sidhu

Today I was running export of an Oracle 9.2.0.1 database. The export completed but with an ORA-600 error:

EXP-00008: ORACLE error 600 encountered
ORA-00600: internal error code, arguments: [xsoptloc2], [4], [4], [0], [], [], [], []
ORA-06512: in "SYS.DBMS_AW", line 347
ORA-06512: in "SYS.DBMS_AW", line 470
ORA-06512: in "SYS.DBMS_AW_EXP", line 270
ORA-06512: in line 1
EXP-00083: The previous problem occurred when calling SYS.DBMS_AW_EXP.schema_info_exp

I googled a bit and found that the problem is with applying some patchset. Then metalink confirmed the same. Somebody tried applying a patch to upgrade it to 9.2.0.5 but didn’t perform all the steps (missed post installation steps, to be precise). Metalink Note 300849.1 covers the issue and also gives the solution. In nutshell startup the database with startup migrate and run catpatch.sql.