cancel
Showing results for 
Search instead for 
Did you mean: 

Oracle 10g upgrade - DBUA DB is not started

Former Member
0 Kudos

Dear all,

I've finished Oracle Upgrade to 10.2.0.2 to our test system, which is homogenous system copy from the production. It's SAP R/3 4.6C with 4.6D_EXT supp. pack 2271, HP-UX 11.11 and Oracle 9.2.0.5.

Now, I'm performing the upgrade on QTS system.

I'm on the step <b>Starting the Database Upgrade Assistant</b> and I have one problem.

If I change the environment to 920_64 and in the sqlplus "/as sysdba" the DB is started.

But If I change the environment to 102_64 and sqlplus "/as sysdba" :

SQL*Plus: Release 10.2.0.2.0 - Production on Tue May 8 14:20:56 2007

Copyright (c) 1982, 2005, Oracle. All Rights Reserved.

<b>

Connected to an idle instance.</b>

I'm following the Upgrade Guide and at this point I've not copied the init.ora file yet.

Does anyone know what is the problem, and how I can proseed to start the DB inorder DBUA to see the started DB?

Many regards,

Ruzica

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

HI

<b>Connected to an idle instance</b>

means ur oracle DB instance is not up and running

Vinod

Message was edited by:

Vinod U

Former Member
0 Kudos

Hi

Yes I DB is not up and running with 10g environment

With the 920_64 environment I started the DB and is up and running

Many regards,

Ruzica

Former Member
0 Kudos

Hi,

Start it with location of init<sid>.ora or spfile<sid>.ora file by sql>startup command.

Vinod

Former Member
0 Kudos

Hi,

The problem is that in the Upgrade Guide you don't need to create the spfile before starting the DBUA. Then after the upgrade DBUA creates the spfile in the 10g environment.

I did the upgrade for my test instance and everything was OK. Now I don't understand why when I'm with the orasid user with 10g environment doesn't see that the DB (which is still 9.2.0.5) is started in 9i environment.

Many regards,

Ruzica

former_member204746
Active Contributor
0 Kudos

dbua should take care of changing necessary environment variables and wil lstart ORacle in the proper version it needs.

Former Member
0 Kudos

Hi,

I have DB started with orasid user when the ORACLE_HOME is 920_64.

Before starting the DBUA, I've changed the environment for the user on 102_64.

When I started DBUA everything seams to look fine. DBUA recognized the old DB that should be upgraded. All 6 steps where successfully configured.

But when the upgrade process started at 10% at Upgrading the Oracle Server, ORA - 00119: invalid specification for system parameter LOCAL_LISTENER,

ORA-00132: syntax error or unresolved network name 'LISTENER_TR2',

ORA-01078: failure in processing system parameters.

Then ORA-01034: Oracle not available.

What is the problem why DBUA does not see the DB started?

Why DBUA does not understand the LOCAL_LISTENER parameter?

Best regards,

Ruzica

Former Member
0 Kudos

'LISTENER_NAME' value used is NOT the listener name reflected in the listener.ora file but rather it is an alias stored in the tnsnames.ora file.

ALTER SYSTEM set LOCAL_LISTENER="(address=(protocol=tcp)(host...)(port...))" will allow actual address use and a more stable function for the database.

Former Member
0 Kudos

Hi Vinod,

What should I do?

Should I change the tnsnames.ora file?

my tnsnames.ora for TR2 instance which should be upgraded:

TR2.WORLD =

(DESCRIPTION =

(SDU = 32768)

(ADDRESS_LIST =

(ADDRESS = (COMMUNITY = SAP.WORLD)(PROTOCOL = TCP)(HOST = sap3n)(PORT = 3420))

)

(CONNECT_DATA =

(SID = TR2)

(GLOBAL_NAME = TR2.WORLD)

)

)

What should I do ?

Where should I change "ALTER SYSTEM set LOCAL_LISTENER...?

Thanks in advance.

Many regards,

Ruzica

Former Member
0 Kudos

sqlplus '/as sysdba'

sql>ALTER SYSTEM ..........

Former Member
0 Kudos

Hi,

I change the local_listener in the DB (started with 9i environment)

and again the same errors with the local_listener.

Why DBUA creates this parameter and then thinks it is a problem?

Ruzica

Former Member
0 Kudos

If a tnsnames.ora "alias" is used for the value of a database parameter LOCAL_LISTENER , and that alias is moved or changed to cause the

entry to be 'invalid' in any way, the database will not start.

Have this in 10 g Env....

Try this have Names.domain_name = "" in sqlnet.ora

Or

Add the parameter LOCAL_LISTENER = "" in init.ora and execute:

SQL> startup nomount pfile='/Oracle/init.ora';

create a new spfile

SQL> shutdown immediate;

SQL> startup

Message was edited by:

Vinod U

Former Member
0 Kudos

My tnsnames.ora in /oracle/TR2/102_64/network/admin:

LISTENER_TR2.WORLD =

(ADDRESS = (COMMUNITY = SAP.WORLD)(PROTOCOL = TCP)(HOST = sap3n)(PORT = 3420))

TR2.WORLD =

(DESCRIPTION =

(ADDRESS = (COMMUNITY = SAP.WORLD)(PROTOCOL = TCP)(HOST = sap3n)(PORT = 3420))

(CONNECT_DATA =

(SERVER = DEDICATED)

(SERVICE_NAME = TR2.WORLD)

)

)

The error in DBUA is about this LISTENER_TR2

In the summary window for parameters to be updated:

local_listener old value is "(address=(protocol=tcp)(host=sap3n)(port=3420))" and the new value he said will be LISTENER_TR2

Do you know where is my problem?

What should I change?

Thanks,

Ruzica

Former Member
0 Kudos

Any luck from any of the options ???

Former Member
0 Kudos

No NO LUCK

I tried with your's two option

1. change in sqlnet.ora

Names.domain_name = ""

and no luck

then

2. I enter the parameter local_listener="" in init.ora and start the DB

after starting the DBUA in the summary window local_listener has old value local_listener="" and it says that the new value will be LISTENER_TR2.

at 10% again ORA-00119 problem with LISTENER_TR2

Why DBUA needs to enter the name for the local_listener=LISTENER_TR2?

Many regards,

Ruzica

Former Member
0 Kudos

Hmmmmm.....

Listener have the same value for TNS_ADMIN ???

instance registration is to set the LOCAL_LISTENER parameter!!!

Former Member
0 Kudos

No I don't have set TNS_ADMIN in .dbenv_host.csh file

I tried to change the settings for the listener, I named it list_tr2, I also changed the settings in tnsnames like list_tr2 and again DBUA wants to set for local_listener LISTENER_TR2?

Former Member
0 Kudos

If you are going to use the syntax local_listener=dummy, you will have to have an alais configured in the TNSNAMES.ORA file for "dummy".

dummy=(ADDRESS=(PROTOCOL=tcp)(host=hostname)(port=1530)) or something simular. The parameter for hostname should represent the actual hostname of the database host, but the port number should be a port number that the listener is not configured to listen on.

Former Member
0 Kudos

In my initTR2.ora file I have entered

local_listener=""

I enter in the tnsnames ( like DBUA wants for local_listener to be LISTENER_TR2):

LISTENER_TR2 =

(ADDRESS = (COMMUNITY = SAP.WORLD)(PROTOCOL = TCP)(HOST = sap3n)(PORT = <b>3425</b>))

Like you said I entered the port 3425 even my real port is 3420 in the listener.ora

The listener.ora file:

LIST_TR2 =

(ADDRESS_LIST =

(ADDRESS=

(PROTOCOL=IPC)

(KEY= TR2.WORLD)

)

(ADDRESS=

(PROTOCOL=IPC)

(KEY= TR2)

)

(ADDRESS =

(COMMUNITY = SAP.WORLD)

(PROTOCOL = TCP)

(HOST = sap3n)

(PORT = <b>3420)</b>

)

)

STARTUP_WAIT_TIME_LIST_TR2 = 0

CONNECT_TIMEOUT_LIST_TR2 = 10

TRACE_LEVEL_LIST_TR2 = OFF

SID_LIST_LIST_TR2 =

(SID_LIST =

(SID_DESC =

(SDU = 32768)

(SID_NAME = TR2)

(ORACLE_HOME = /oracle/TR2/102_64)

)

)

Former Member
0 Kudos

Hi Vinod,

YES you were wright!!!!

When I put the port that listener is not listening on , the upgrade succeeded.

Thanks you very much for the effort of solving my problem

Many regards,

Ruzica

Answers (0)