RE: Upgrade from 11.2.0.4 to 12.1.0.2 using EM12c failed

From: Mark W. Farnham <mwf_at_rsiz.com>
Date: Wed, 30 Sep 2015 12:31:48 -0400
Message-ID: <000301d0fb9d$82568590$870390b0$_at_rsiz.com>



grrr. sb ….IF glogin.sql is not the problem….  

From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Mark W. Farnham Sent: Wednesday, September 30, 2015 12:17 PM To: pete.sharman_at_oracle.com; sethmiller.sm_at_gmail.com; alfredo.abate_at_gmail.com Cc: peter.schauss_at_ngc.com; 'Oracle-L Freelists' Subject: RE: Upgrade from 11.2.0.4 to 12.1.0.2 using EM12c failed  

I would also add that is glogin.sql is not the problem in any of its locations, you might also have something in login.sql.  

$SQLPATH of the user environment running the upgrade would be a clue about where to look if it is not in the common locations Seth mentioned.  

If push comes to shove and you can’t find it, tracing sqlplus will show you what files it is trying to open.  

A few host commands inserted into the upgrade process to puke the OS environment (and stop) might also be useful as a diagnostic.  

mwf  

From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Peter Sharman Sent: Tuesday, September 29, 2015 7:56 PM To: sethmiller.sm_at_gmail.com; alfredo.abate_at_gmail.com Cc: peter.schauss_at_ngc.com; Oracle-L Freelists Subject: RE: Upgrade from 11.2.0.4 to 12.1.0.2 using EM12c failed  

I would just add that all EM is doing is adding a wrapper around the upgrade process, so it probably would have failed for the same reason if you did it manually. That’s not to say there might not be bugs in EM as well, but the likelihood is that this is not an EM issue per se.  

Pete

Oracle logo

Pete Sharman
Database Architect, DBaaS / DBLM
Enterprise Manager Product Suite
33 Benson Crescent CALWELL ACT 2905 AUSTRALIA

Phone: <tel:+61262924095> +61262924095 | | Fax: <fax:+61262925183> +61262925183 | | Mobile: +61414443449 Email: <mailto:pete.sharman_at_oracle.com> pete.sharman_at_oracle.com Twitter: @SharmanPete LinkedIn: au.linkedin.com/in/petesharman Website: petewhodidnottweet.com


"Controlling developers is like herding cats."

Kevin Loney, Oracle DBA Handbook  

"Oh no, it's not, it's much harder than that!"

Bruce Pihlamae, long term Oracle DBA


 

From: Seth Miller [mailto:sethmiller.sm_at_gmail.com] Sent: Wednesday, September 30, 2015 7:37 AM To: alfredo.abate_at_gmail.com
Cc: peter.schauss_at_ngc.com; Oracle-L Freelists <oracle-l_at_freelists.org> Subject: Re: Upgrade from 11.2.0.4 to 12.1.0.2 using EM12c failed  

Peter,

login.sql and glogin.sql files can be in several places. Take a look at the default search paths in the documentation to see if there is one being picked up in another directory.

Seth Miller

On Sep 29, 2015 2:39 PM, "Alfredo Abate" <alfredo.abate_at_gmail.com> wrote:

Peter,  

I see several My Oracle Support documents referencing the glogin.sql file as causing problems with upgrades and even patching.  

Did the file exist in the QA database where the upgrade was successful? What happens if you follow their suggestion and just rename the file then continue with the upgrade?  

Alfredo  

On Tue, Sep 29, 2015 at 2:27 PM, Schauss, Peter (ESS) <peter.schauss_at_ngc.com> wrote:

My environment: 64 bit Linux release 6.7 Oracle 11.2.0.4 going to 12.1.0.2

I was able to upgrade my QA copy (running on my QA database server) using EM12c.

When I tried the same thing in production it failed with :

Unexpected error encountered in catconInit; exiting

Oracle support said that I should look for a file called glogin.sql in $ORACLE_HOME/sqlplus/admin and rename it. This file has no executable sql statements in it, only comments. Does this suggestion make sense? This is a production environment so my ability to test is limited and, of course, the error does not happen in QA.

Any ideas?

Thanks,
Peter

--
http://www.freelists.org/webpage/oracle-l

 





-- http://www.freelists.org/webpage/oracle-l
image001.jpg
Received on Wed Sep 30 2015 - 18:31:48 CEST

Original text of this message