Oracle 11 issues?

[Former Member]

Hi all,

I have completed an upgrade from 10.2.0.4 to 11.2.0.2 in our development environment and am scheduled to do the same in our QA environment next week. We had a few minor issues with the database - needed to enable remote authentication and disable some Oracle-scheduled jobs in the database because they were causing errors.

We haven't seen anything at the user level that would cause us to delay this upgrade, but we haven't done (or planned) a full regression test either and thought this community might give us some insight into things we might include in the sample test to reduce our risk.

Have any of you completed a similar upgrade and had experience you could share?

Thanks, George

[Former Member]

Thanks for this help..

But the question I asked is very much open.. have any of YOU seen issues we should pay special attention to in our testing of this upgrade? We are planning only light regression testing before taking the Oracle upgrade into production.

Regards, George

[former_member213250]

Hello George..

Can you please explain wat sort of errors you are getting, and during which stage you are getting them errors..

Also are you getting these errors while running any specific transaction/jobs ..?

BR

Venkat

[Former Member]

Venkat,

I am not so worried about the errors I am seeing.. but those I am not seeing. Have you any to report?

What I did see are issues in the Oracle trace files. For instance:

ORA-06512: at "SYS.DBMS_FEATURE_USAGE_INTERNAL", line 276

and

msg=(@=0x2b29be56e6e0, fac=ORA, cod=16960, p1=ORA-16960: SQL Analyze could not reproduce the desired plan.)

and

ORA-06512: at "SYS.DBMS_SQL", line 1839

and

ORA-06512: at "SYS.DBMS_FEATURE_USAGE_INTERNAL", line 276

I am reasonably sure these errors are generated by the internal db jobs that come with Oracle 11, which I am working ot disable (per SAP recommendation.)

Thanks, George

[former_member213250]

Hello George

during DB upgrade these ORA erros are caused because setting few paramters

This known issue during DB upgrade from 10 to 11

Cause:

The Oracle RDBMS was recently upgraded from Oracle10g to Oracle11g.

The database initialization parameter aq_tm_processes has been set

to the value of 0 and as a result the process qmnc is not running.

References:

This issue is tracked in Oracle Bug 9471411.

Fixed in 11.2.0.1.1PSU and above.

For further information see My Oracle Support article 1083952.1.

Solution:

Un-set the database initialization parameter 'aq_tm_processes' and

restart the instance.

SQL> ALTER SYSTEM RESET AQ_TM_PROCESSES;

BR

Venkat