Database Upgrade Assistant DBUA

Im connected to sqlplus mode in 9i.
How do i invoke DBUA so that i can sheck what all needs to be done for the upgrade.
I need it to analyse my database. how do i do that?

Type;
dbua (at at a command prompt)
It will be probably located at $ORACLE_HOME/bin
You might also review the following links;
http://download.oracle.com/docs/cd/B10501_01/server.920/a96530/migprep.htm#1006935
http://download.oracle.com/docs/cd/B10501_01/server.920/a96530/upgrade.htm#1008982
Adith

Similar Messages

Database upgrade through DBUA cant detect database

Hi,
I have a HP UNix box . There are 7 instances 2 in 9.2.0.8 and 5 in 10.2.0.1 upgraded earlier than my joining. I want to upgrade one of the 9.2.0.8 databases.
The database to upgarde is up and running and can be connected through listener.
I login as the owner of ora10g and start dbua. It shows me all the 7 databases but when I select the database to upgrade it throws the following info :
The Upgrade Assistant Failed in bringing up the database xxxx. Oracle Home /oracle/9.2.0.8 obtained from /etc/oratab was used to connect to the database. Either the database is not running from Oracle Home /oracle/9.2.0.8 or correct Initialization pfile was not found.
It then asks for pfile. -----------------------------------
The database is up and running.The Oracle home is also correct in Oratab file.
I checked the sqls.log file
It has info like
set heading off
set pagesize 0
set feedback off
set linesize 2048
set sqlprompt 'SQL_ENGINE_END_OF_SQL'
show sqlprompt
set sqlprompt 'SQL>'
set sqlprompt 'SQL>';
set heading off
set pagesize 0
set feedback off
set linesize 2048
set sqlprompt 'SQL_ENGINE_END_OF_SQL'
show sqlprompt
set sqlprompt 'SQL>'
connect /****** as SYSDBA
select count(*) from v$instance;
set heading off
set pagesize 0
set feedback off
set linesize 2048
set sqlprompt 'SQL_ENGINE_END_OF_SQL'
show sqlprompt
set sqlprompt 'SQL>'
Please help on this issue . Y cant the DBUA see that database is up?

Are you able to start/stop instance by using the dbstart/dbshut command? If not, verify your oratab files has accurate information and it has the Y flag to let the admin scripts manage the instance.
~ Madrid.

Upgrade from 8i to 9i using Database Upgrade Assistant

Hi
I installed 9i on a server that already has an 8i database. I am trying to use the upgrade assistant in 9i to convert the database to 9i. After selecting the 8i db, I get dialog saying 'Getting databse information. Please wait..' then error 'ORA-12560: TNS:protocol adapter error'. I tried setting the 9i listener to a different port (1522) and restart listener, no luck. Any suggestions?
Thanx

You need to try the database forum, whose ID i think is 145
All Oracle database upgrade stuff will be handled there
Barry

Using Database Upgrade Assistant

I have one db installation with several (3) instances on.
Do I have to upgrade each instance or it is enough with one?
Best regards
Peråke

You have one ORACLE_HOME and 3 instances using it?
Then You have to for first upgrade ORACLE_HOME and then all 3 databases.
Only be a little bit more specific what kind of upgrade it is? Sometimes it's wiser to create a new ORACLE_HOME, upgrade it, then switch instances one by one to it and upgrade databases. Smaller downtime and in case of any failure much easier to rollback.

Setting up database upgrade assistant

Hi, I am trying to stetup the dbua on my desk top, after putting my ipaddress in the environmental variable, i get this error message.
DISPLAY=IPaddress:0.0; export DISPLAY
Exception in thread "main" java.lang.InternalError: Can't connect to X11 window server using '136.206.4.84:0.0' as the value of the DISPLAY variable.
Any ideas on wat i might be doin wrong?

http://www.google.com/search?hl=en&q=java.lang.InternalError%3A+Can%27t+connect+to+X11+window+server

Database Upgrade Agent not working for upgrading Oracle 9i DB to Oracle 10i

Hi All,
Presently I have completed my Oracle 10i installation on Solaris Server but I am facing an issue during the upgrade process of Oracle 9i to 10g. Whenever I try to upgrade the 9i databases to 10g using DBUA(Database Upgrade assistant) I am facing an issue that Data base not running from oracle home or pfile not found. The exact error message says:-
The upgrade assistant failed in bringing up the database XIPCOTS. Oracle Home /opt/apps/home/oracle9i/product/releases/92/92 obtained from file /var/opt/oracle/oratab was used to connect to the database. Either the database is not running from Oracle Home /opt/apps/home/oracle9i/product/releases/92/92 or the correct Initialisation parameter file (pfile) was not found. To start the database , Oracle needs the pfile. Provide the full path name of the init file for the database XIPCOTS.
In reality the XIPCOTS database is running fine in Oracle 9i and we can connect it using PL/SQL developer in windows.I have also provided the path of pfile but it is still not accepting the same.
Path of pfile I provided :- /XIP/ofaroot/XIPCOTS/pfile/initXIPCOTS.ora
Any help or suggestions would be greately appreciated.
Our both Oracle 9i and 10g are installed on same Solaris server where solaris version is 9
Installation path for 9i :- /opt/apps/home/oracle9i/product/releases/92/92
Installation path for 10g :- /opt/apps/home/oracle/product/releases/10201
Oracle 9i version :- 9.2.0.7
Oracle 10g version :- 10.2.01
Thanks in advance.
Best Regards,
Gourav Banerjee

Can you please mention the specific folder name under oracle home where we need to put this pfile because there are two folder dbs and ds I have allready tried putting it inside dbs its not working. And my home path is correct I hope and is set for oracle 9i directories in the .oraenv file do we need to set it for oracle 10g before the DBUA upgrade.

Database Upgrade from 10.2.0.3.0 to 10.2.0.4.0 for a EBS 12 database

Hi,
Is there any specific procedure like interoperability for upgrading an R12 database from 10.2.0.3.0 to 10.2.0.4.0.
Currently I have plans to upgrade database from 10.2.0.3.0 to 10.2.0.4.0 and then
upgrade apps from 12.0.4 to 12.0.6. Also I need to install Arabic language on the instance.
What would be the best sequence to do this ?
Ram

hi,
you can use the oracle 10.2.0.4 patchset(downloadable from metalink) to upgrade your database to this version,
just follow the OUI in the patch set and select the migrating oracle home ...
before migrating it will ask you to stop all the oracle services , once it migrated then you need to use DBUA (DATABASE upgrade assistant ) to upgrade its components ..
then you can check all the component versions vis
select * from dba_registry;
Regards,
Mohd Mehraj Hussain
http://mehrajdba.wordpress.com

Oracle database upgrade from express edition to standard edition

We purchased Oracle database 11g to upgrade our current primavera oracle database express edition (10g).When we are trying to upgrade through DBUA it getting error message
Please provide us a proper advise to solve this issue.

1008016 wrote:
Windows 7 64 bit, please find the below error message when I am trying to upgrade through Database Upgrade Assistant
"Could not get database version from the "oracle server" component.The "CEP" file "D:\app\usr\product\11.2.0\dbhome_1\rdbms\admin\rdbmsup.sql" does not provide the version directiveTo upgrade to 11gR2, you need to be at 10.2.0.2 - hence the error
11gR2 DBUA States "The CEP File does not provide the version directive" [ID 980693.1]
As noted by orafad, the easiest approach would be to perform a full export from 10gR2, install 11gR2 into a new ORACLE_HOME, create an empty 11gR2 database, then perform a full import into 11gR2. As also noted, you will have to follow any special directions related to Primavera.
http://docs.oracle.com/cd/E11882_01/server.112/e23633/expimp.htm
You will need Win 7 Professional or higher (Home versions are not supported for Oracle installs)
HTH
Srini

Database Upgrade to 10.2.0.4

Using Windows 2003 64-bit, 10.2.0.3 Standard Edition.
I clone the database to a spare server, shut it down immediate, and stopped all Oracle services. I installed the 10.2.0.4 patchset into the original Oracle Home without a problem. I then ran the Database Upgrade Assistant and it ran through to completion. However, it did declare a series of errors when upgrading the 'Data Mining' component:
Error ignored: ORA-29831: operator binding not found ORA-06553: PLS-306: wrong number or types of arguments in call to 'SDO_FILTER'
...and others like it. The report at the end of the process is saying the Oracle Server component is 'Successful *' -and the asterisk links to a list of the errors that I clicked 'ignore' to during the process. The one for 'data mining' says 'Skipped'.
I don't think I mind the errors about Data Mining, because as far as I know, we don't use that (are we even allowed to on an SE license?) When I look in V$OPTION, for example, we get:
OLAP Window Functions TRUE
Block Media Recovery FALSE
Fine-grained Auditing FALSE
Application Role FALSE
Enterprise User Security FALSE
Oracle Data Guard FALSE
Oracle Label Security FALSE
OLAP FALSE
Table compression FALSE
Join index FALSE
Trial Recovery FALSE
Data Mining                                                      FALSE
Online Redefinition FALSE
Streams Capture FALSE
File Mapping FALSE
So my question is: did the upgrade work properly or not?! Should I mind that the errors appeared when upgrading a component that doesn't even exist, as far as I know? Is there some way of knowing that all is as it should be?
I have logged onto the database after the upgrade and all looks fine, with queries working as expected and so on. But I just have a nagging doubt...

SQL> SELECT owner, object_type, COUNT(*)
2 FROM dba_objects
3 WHERE status = 'INVALID'
4 GROUP BY owner, object_type;
OWNER                          OBJECT_TYPE           COUNT(*)
MDSYS                          PACKAGE BODY                 1
ACC_GLOBAL                     PACKAGE BODY                 1The ACC_GLOBAL invalid is a known issue: I don't have the tnsnames.ora with the right alias for the resolution of a database link that package contains. MDSYS is not a schema we use, I think, and the package that's invalid is SDO_3GL which is the package I expected to be wrong as a result of the error messages received during the upgrade.
As for your second query:
COMP_NAME                                VERSION                        STATUS
Oracle interMedia                        10.2.0.4.0                     VALID
Oracle XML Database                      10.2.0.4.0                     VALID
Oracle Text                              10.2.0.4.0                     VALID
Oracle Data Mining                       10.2.0.3.0                     OPTION OFF
Oracle Expression Filter                 10.2.0.4.0                     VALID
Oracle Rule Manager                      10.2.0.4.0                     VALID
Oracle Workspace Manager                 10.2.0.4.3                     VALID
Oracle Database Catalog Views            10.2.0.4.0                     VALID
Oracle Database Packages and Types       10.2.0.4.0                     VALID
JServer JAVA Virtual Machine             10.2.0.4.0                     VALID
Oracle XDK                               10.2.0.4.0                     VALID
Oracle Database Java Packages            10.2.0.4.0                     VALIDDoesn't look a miserable failure to me, really. Data Mining doesn't look right, but we knew that already because of those error messages during the upgrade. Fact remains, we don't use it, it's not an option we've installed, etc etc.

Upgrade Assistant 11gR2

When will there be an Applications Database Upgrade Assistant for 11gR2?
I got to update several installations and somehow hoped that livepatch 2.18 would enhance that assistant.
Thanks :)

Martin - this path exists in Maintenance Wizard already for 11gR1 upgrades.
You could then do a manual upgrade to 11gR2 until we release the new db upgrade paths
Edited by: mybro62 on Jan 26, 2011 7:10 AM

Database upgrade using assistant

Hi
I installed 9i on a server that already has an 8i database. I am trying to use the upgrade assistant in 9i to convert the database to 9i. After selecting the 8i db, I get dialog saying 'Getting database information. Please wait..' then error 'ORA-12560: TNS:protocol adapter error'. I tried setting the 9i listener to a different port (1522) and restart listener, no luck. Any suggestions?
Thanx

HI Diaw65,
The best way to upgrade oracle db is line mode. The are few steps which you need to follow by executing some sql's tats is .
Cheers,
Kamalesh JK

Upgrade failure(dbua) from 8i to 10g on solaris

Hi,
current version is 8.1.7.4 and trying to upgrade to 10.2.0.1 which is already been installed.
I am running dbua from 10ghome/bin
I have changed the oracle_home to 10g also
when I am trying to install by using dbua, after clicking on the finish button
it is getting failed by throwing the error at pre upgrade step.
ORA-0178: failure in processing system parameters while upgrading
Please assist me
Regards,
RB

Hi User,
It seems to me that you just want the upgrade done as fast as you could without really putting enough thoughts and understanding of the whole upgrade process. What metalink note are you following? Did you check the "Database Upgrade Guide"?
There are two scripts to run to check all your settings before the upgrade. Please search metalink for "upgrade" procedures for the details.
The errors you are encountering are mostly caused by obsolete parameters used in 8i or new parameters in 10g not acceptable in 8i.
Please provide error log.
Regards,
ArtRed

Do you run Pre-Upgrade Assistant when migrate from 10.1 to 10.2

Hello,
I tried to upgrade from 10.1 to 10.2 on Windows. Base on installation guide, you have to install 10.2 in a separate ORACLE_HOME, then run utlu102i.sql through SQL before run DBUA. Since I installed 10.2 without create start database because SID is same as 10.1. How to run pre-upgrade assistant? Or should I setup new SID for 10.2 and change it back after migrate database from 10.1 to 10.2.
Your assistance will be appreciated,

I'd suggest to check the "manual upgrade/migration" method described in upgrade doc.
As a summary:
utlu102.sql is just a step to verify some prereqs needed before going to 10.2
You'll need to shutdown your 10.1 DB. Copy your .ora files from 10.1.to 10.2; adjust them appropriately.
Set your Oracle_home to 10.2; keep same SID. Startup upgrade, then run catpatch.sql (if i remember correctly).
All these steps are well described in the manual.

IDM/OID upgrade assistant (UA) failed in the examination - on 11.1.1.2

Does anyone have problem upgrading Oracle Identity Management/OID from 10.1.2.3 to 11.1.1.2 on Linux SUSE-10 64-bit?.
1. Upgrade Oracle seed DB 10.1.0.5 32-bit to 10.2.0.4 64-bit. Using DBUA - OK, no problem.
2. Started As 10.1.2.3 Infrastucture - IDM/OID/Metadata Repository and Middle Tier - Portal/Forms/Reports/Discoverers - OK, No problem.
3. Installed Weblogic 10.3.2 - OK, No problem.
4. Installed NEW 11.1.1.2 IDM/OID components OID and DIP only - OK, No problem.
5. Run ua (upgrade assistant) to upgrade OID to 11.1.1.2 and got error - Examination OID failed. UA stopped.
Installed 64-bit Fusion Middleware IDM/OID - Probably this is the problem?.
Have not tried the 32-bit Fusion Middleware IDM/OID yet.
Had a SR opened with Oracle Support and have no solution yet.
Follow the instructions from:
Oracle® Fusion Middleware Upgrade Guide for Oracle Identity Management
11g Release 1 (11.1.1)
Part Number E10129-02
***** Error in OID oidctl.log *****
[2010-04-28T13:15:24+00:00] [OID] [NOTIFICATION:16] [] [] [host: csnbia21] [pid: 16251] [tid: 0] OIDCTL:: Session ID = 540
[2010-04-28T13:15:24+00:00] [OID] [NOTIFICATION:16] [] [] [host: csnbia21] [pid: 16251] [tid: 0] OIDCTL:: OracleProcess ID = 16253
[2010-04-28T13:15:24+00:00] [OID] [NOTIFICATION:16] [] [] [host: csnbia21] [pid: 16251] [tid: 0] OIDCTL:: WARNING: Connected to incorrect OID base schema version, (version=10.1.2.3.0).
WARNING: OID server (version 11.1.1.2.0) is now operating in read_only mode
[2010-04-28T13:15:24+00:00] [OID] [NOTIFICATION:16] [] [] [host: csnbia21] [pid: 16251] [tid: 0] OIDCTL:: WARNING: Connected to incorrect OID base schema version, (version=OID 10.1.2.3.0).
WARNING: OID (version 11.1.1.2.0) is now operating in read_only mode
[2010-04-28T13:15:24+00:00] [OID] [NOTIFICATION:16] [] [] [host: csnbia21] [pid: 16251] [tid: 0] OIDCTL:: oidctl: Waiting for oidmon to start OIDLDAPD (instance=1)
[2010-04-28T13:15:34+00:00] [OID] [NOTIFICATION:16] [] [] [host: csnbia21] [pid: 16251] [tid: 0] OIDCTL:: oidctl: Waiting for oidmon to start OIDLDAPD (instance=1)
[2010-04-28T13:15:44+00:00] [OID] [NOTIFICATION:16] [] [] [host: csnbia21] [pid: 16251] [tid: 0] OIDCTL:: oidctl: Waiting for oidmon to start OIDLDAPD (instance=1)
[2010-04-28T13:15:54+00:00] [OID] [NOTIFICATION:16] [] [] [host: csnbia21] [pid: 16251] [tid: 0] OIDCTL:: oidctl: Waiting for oidmon to start OIDLDAPD (instance=1)
[2010-04-28T13:16:04+00:00] [OID] [NOTIFICATION:16] [] [] [host: csnbia21] [pid: 16251] [tid: 0] OIDCTL:: oidctl: Waiting for oidmon to start OIDLDAPD (instance=1)
[2010-04-28T13:16:14+00:00] [OID] [NOTIFICATION:16] [] [] [host: csnbia21] [pid: 16251] [tid: 0] OIDCTL:: oidctl: Waiting for oidmon to start OIDLDAPD (instance=1)
[2010-04-28T13:16:24+00:00] [OID] [NOTIFICATION:16] [] [] [host: csnbia21] [pid: 16251] [tid: 0] OIDCTL:: oidctl: Waiting for oidmon to start OIDLDAPD (instance=1)
[2010-04-28T13:16:34+00:00] [OID] [NOTIFICATION:16] [] [] [host: csnbia21] [pid: 16251] [tid: 0] OIDCTL:: oidctl: Waiting for oidmon to start OIDLDAPD (instance=1)
[2010-04-28T13:16:44+00:00] [OID] [NOTIFICATION:16] [] [] [host: csnbia21] [pid: 16251] [tid: 0] OIDCTL:: oidctl: Waiting for oidmon to start OIDLDAPD (instance=1)
[2010-04-28T13:16:54+00:00] [OID] [NOTIFICATION:16] [] [] [host: csnbia21] [pid: 16251] [tid: 0] OIDCTL:: oidctl: Waiting for oidmon to start OIDLDAPD (instance=1)
***********************************************************************************

Hi Milan,
take a look to "Oracle Database Data Cartridge Developer's Guide" [http://docs.oracle.com/cd/E11882_01/appdev.112/e10765/dom_idx.htm#autoId50] (here is the 11g rel2 version but is the same with 9i)
Domain Indexes and SQLLoader*
SQLLoader conventional path loads and direct path loads are supported for tables on which domain indexes are defined, with two limitations:
-The table must be heap-organized.
+-The domain index cannot be defined on a LOB column.+
To do a direct path load on a domain index defined on an IOT or on a LOB column, perform these tasks:
-Drop the domain index
-Do the direct path load in SQL*Loader.
-Re-create the domain indexes.
doesn't seem to be possible to use "direct path method" with spatial (domain) indexes
i hope for you that there is a workaround ...
good luck,
CarlT

Database Upgradation from oracle 9.2.0.8 to oracle11gR2

Hi
we are using AIX 5.3 TL 10 SP4 and we are upgrading DB from oracle9.2.0.8 to oracle 11.2.0.2
i am having some doubt from below pre-upgrade scripts out put.
oratst@ebsdevdb on /tmp # sqlplus "/as sysdba"
SQL*Plus: Release 9.2.0.8.0 - Production on Mon Jul 4 10:11:48 2011
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to:
Oracle9i Enterprise Edition Release 9.2.0.8.0 - 64bit Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.8.0 - Production
SQL> spool 11202_upgrade.txt
SQL> @utlu112i.sql
Oracle Database 11.2 Pre-Upgrade Information Tool 07-04-2011 10:17:06
Script Version: 11.2.0.2.0 Build: 001
Database:
--> name: EBSTEST
--> version: 9.2.0.8.0
--> compatible: 9.2.0
--> blocksize: 8192
--> timezone file: V1
Logfiles: [make adjustments in the current environment]
--> The existing log files are adequate. No changes are required.
Tablespaces: [make adjustments in the current environment]
--> SYSTEM tablespace is adequate for the upgrade.
.... minimum required size: 8546 MB
--> TOOLS tablespace is adequate for the upgrade.
.... minimum required size: 8 MB
--> TEMP tablespace is adequate for the upgrade.
.... minimum required size: 61 MB
--> AR_TABLE tablespace is adequate for the upgrade.
.... minimum required size: 33497 MB
--> FND_TABLE tablespace is adequate for the upgrade.
.... minimum required size: 45447 MB
--> AMVD tablespace is adequate for the upgrade.
.... minimum required size: 7 MB
--> ASOD tablespace is adequate for the upgrade.
.... minimum required size: 7 MB
--> CCTD tablespace is adequate for the upgrade.
.... minimum required size: 7 MB
--> IBUD tablespace is adequate for the upgrade.
.... minimum required size: 1 MB
--> IEMD tablespace is adequate for the upgrade.
.... minimum required size: 5 MB
--> IEOD tablespace is adequate for the upgrade.
.... minimum required size: 4 MB
--> JTFD tablespace is adequate for the upgrade.
.... minimum required size: 135 MB
--> OKCD tablespace is adequate for the upgrade.
.... minimum required size: 34 MB
--> XDPD tablespace is adequate for the upgrade.
.... minimum required size: 7 MB
--> XNPD tablespace is adequate for the upgrade.
.... minimum required size: 7 MB
--> APPS_UNDOTS1 tablespace is adequate for the upgrade.
.... minimum required size: 849 MB
Update Parameters: [Update Oracle Database 11.2 init.ora or spfile]
Note: Pre-upgrade tool was run on a lower version 64-bit database.
--> If Target Oracle is 32-Bit, refer here for Update Parameters:
WARNING: --> "compatible" must be set to at least 10.1.0
--> If Target Oracle is 64-Bit, refer here for Update Parameters:
WARNING: --> "compatible" must be set to at least 10.1.0
WARNING: --> "shared_pool_size" needs to be increased to at least 532 MB
WARNING: --> "java_pool_size" needs to be increased to at least 128 MB
Renamed Parameters: [Update Oracle Database 11.2 init.ora or spfile]
-- No renamed parameters found. No changes are required.
Obsolete/Deprecated Parameters: [Update Oracle Database 11.2 init.ora or spfile]
--> optimizer_max_permutations 10.1 OBSOLETE
--> row_locking 10.1 OBSOLETE
--> undo_suppress_errors 10.1 OBSOLETE
--> max_enabled_roles 10.1 DEPRECATED
--> enqueue_resources 10.2 OBSOLETE
--> sql_trace 10.2 DEPRECATED
--> background_dump_dest 11.1 DEPRECATED replaced by "diagnostic_dest"
--> user_dump_dest 11.1 DEPRECATED replaced by "diagnostic_dest"
Components: [The following database components will be upgraded or installed]
--> Oracle Catalog Views [upgrade] VALID
--> Oracle Packages and Types [upgrade] VALID
--> JServer JAVA Virtual Machine [upgrade] VALID
--> Oracle XDK for Java [upgrade] VALID
--> Real Application Clusters [upgrade] INVALID
--> Oracle Text [upgrade] VALID
--> Oracle XML Database [install]
--> Oracle Java Packages [upgrade] VALID
--> Oracle interMedia [upgrade] VALID
--> Spatial [upgrade] VALID
Miscellaneous Warnings
WARNING: --> Passwords exist in some database links.
.... Passwords will be encrypted during the upgrade.
.... Downgrade of database links with passwords is not supported.
WARNING: --> Deprecated CONNECT role granted to some user/roles.
.... CONNECT role after upgrade has only CREATE SESSION privilege.
WARNING: --> Database is using a timezone file older than version 14.
.... After the release migration, it is recommended that DBMS_DST package
.... be used to upgrade the 9.2.0.8.0 database timezone version
.... to the latest version which comes with the new release.
WARNING: --> Database contains INVALID objects prior to upgrade.
.... The list of invalid SYS/SYSTEM objects was written to
.... registry$sys_inv_objs.
.... The list of non-SYS/SYSTEM objects was written to
.... registry$nonsys_inv_objs.
.... Use utluiobj.sql after the upgrade to identify any new invalid
.... objects due to the upgrade.
.... USER ADWANIAH has 1 INVALID objects.
.... USER APPS has 34 INVALID objects.
.... USER CHAKKACHANSA has 1 INVALID objects.
.... USER FA_USER has 9 INVALID objects.
.... USER SYSSEL has 2 INVALID objects.
.... USER SYSTEM has 30 INVALID objects.
.... USER XXITDFINAD has 7 INVALID objects.
WARNING: --> SYSTEM schema default tablespace has been altered.
.... The SYSTEM schema default tablespace is currently set to TOOLS.
.... Prior to upgrading your database please reset the
.... SYSTEM schema default tablespace to SYSTEM using the command:
.... ALTER USER SYSTEM DEFAULT TABLESPACE SYSTEM;
WARNING: --> Database contains schemas with objects dependent on DBMS_LDAP package.
.... Refer to the 11g Upgrade Guide for instructions to configure Network ACLs.
.... USER APPS has dependent objects.
Recommendations
Oracle recommends gathering dictionary statistics prior to
upgrading the database.
To gather dictionary statistics execute the following commands
while connected as SYSDBA:
EXECUTE dbms_stats.gather_schema_stats('CTXSYS',options=>'GATHER'
,estimate_percent=>DBMS_STATS.AUTO_SAMPLE_SIZE
,method_opt=>'FOR ALL COLUMNS SIZE AUTO'
,cascade=>TRUE);
EXECUTE dbms_stats.gather_schema_stats('DBSNMP',options=>'GATHER'
,estimate_percent=>DBMS_STATS.AUTO_SAMPLE_SIZE
,method_opt=>'FOR ALL COLUMNS SIZE AUTO'
,cascade=>TRUE);
EXECUTE dbms_stats.gather_schema_stats('MDSYS',options=>'GATHER'
,estimate_percent=>DBMS_STATS.AUTO_SAMPLE_SIZE
,method_opt=>'FOR ALL COLUMNS SIZE AUTO'
,cascade=>TRUE);
EXECUTE dbms_stats.gather_schema_stats('ORDPLUGINS',options=>'GATHER'
,estimate_percent=>DBMS_STATS.AUTO_SAMPLE_SIZE
,method_opt=>'FOR ALL COLUMNS SIZE AUTO'
,cascade=>TRUE);
EXECUTE dbms_stats.gather_schema_stats('ORDSYS',options=>'GATHER'
estimate_percent=>DBMS_STATS.AUTO_SAMPLE_SIZE
,method_opt=>'FOR ALL COLUMNS SIZE AUTO'
,cascade=>TRUE);
EXECUTE dbms_stats.gather_schema_stats('OUTLN',options=>'GATHER'
,estimate_percent=>DBMS_STATS.AUTO_SAMPLE_SIZE
,method_opt=>'FOR ALL COLUMNS SIZE AUTO'
,cascade=>TRUE);
EXECUTE dbms_stats.gather_schema_stats('SYS',options=>'GATHER'
,estimate_percent=>DBMS_STATS.AUTO_SAMPLE_SIZE
,method_opt=>'FOR ALL COLUMNS SIZE AUTO'
,cascade=>TRUE);
EXECUTE dbms_stats.gather_schema_stats('SYSTEM',options=>'GATHER'
,estimate_percent=>DBMS_STATS.AUTO_SAMPLE_SIZE
,method_opt=>'FOR ALL COLUMNS SIZE AUTO'
,cascade=>TRUE);
Oracle recommends removing all hidden parameters prior to upgrading.
To view existing hidden parameters execute the following command
while connected AS SYSDBA:
SELECT name,description from SYS.V$PARAMETER WHERE name
LIKE '\_%' ESCAPE '\'
Changes will need to be made in the init.ora or spfile.
Oracle recommends reviewing any defined events prior to upgrading.
Changes will need to be made in the init.ora or spfile.
Oracle recommends reviewing any defined events prior to upgrading.
To view existing non-default events execute the following commands
while connected AS SYSDBA:
Events:
SELECT (translate(value,chr(13)||chr(10),' ')) FROM sys.v$parameter2
WHERE UPPER(name) ='EVENT' AND isdefault='FALSE'
Trace Events:
SELECT (translate(value,chr(13)||chr(10),' ')) from sys.v$parameter2
WHERE UPPER(name) = '_TRACE_EVENTS' AND isdefault='FALSE'
Changes will need to be made in the init.ora or spfile.
SYSAUX Tablespace:
[Create tablespace in the Oracle Database 11.2 environment]
--> New "SYSAUX" tablespace
.... minimum required size for database upgrade: 500 MB
From above output script
1)SYSTEM tablespace is adequate for the upgrade.
.... minimum required size: 8546 MB
From system tablespace minimum required size means free space from system tablespace or total size of system tablespace?
i am going to use dbua utility for upgrade means does it alter tablespace as per output of scripts or we need to manually alter tablespace size as per requirement?
2)WARNING: --> Database contains schemas with objects dependent on DBMS_LDAP package.
.... Refer to the 11g Upgrade Guide for instructions to configure Network ACLs.
.... USER APPS has dependent objects.
what is above warning and how can i configure ACL's for APPS User?
Thanks
With Regards
A-Z

Hi
oratst@ebsdevdb on /ebdbh/11g/data/cfgtoollogs/dbua/ebstest/upgrade1 # more Upgrade_Directive.log
Connected.
ODMA_DIRECTIVE:VERSION:9.2.0.8
ODMA_DIRECTIVE:MIGRATE_SID:
ODMA_DIRECTIVE:ORA:IGNORE:06512:
ODMA_DIRECTIVE:ORA:FATAL:00600:
ODMA_DIRECTIVE:ORA:FATAL:01012:
ODMA_DIRECTIVE:ORA:FATAL:01031:
ODMA_DIRECTIVE:ORA:FATAL:01034:
ODMA_DIRECTIVE:ORA:FATAL:01078:
ODMA_DIRECTIVE:ORA:FATAL:01092:
ODMA_DIRECTIVE:ORA:FATAL:01109:
ODMA_DIRECTIVE:ORA:FATAL:01119:
ODMA_DIRECTIVE:ORA:FATAL:01507:
ODMA_DIRECTIVE:ORA:FATAL:01722:
ODMA_DIRECTIVE:ORA:FATAL:03113:
ODMA_DIRECTIVE:ORA:FATAL:03114:
ODMA_DIRECTIVE:ORA:FATAL:07445:
ODMA_DIRECTIVE:ORA:FATAL:12560:
ODMA_DIRECTIVE:ORA:RECOVER_TBS:01650:
ODMA_DIRECTIVE:ORA:RECOVER_TBS:01651:
ODMA_DIRECTIVE:ORA:RECOVER_TBS:01652:
ODMA_DIRECTIVE:ORA:RECOVER_TBS:01653:
ODMA_DIRECTIVE:ORA:RECOVER_TBS:01654:
ODMA_DIRECTIVE:ORA:RECOVER_TBS:01655:
ODMA_DIRECTIVE:ORA:RECOVER_ROLL:01562:
ODMA_DIRECTIVE:ORA:RECOVER_INIT:04031:
ODMA_DIRECTIVE:SCRIPT:UPGRADE:rdbms/admin/catupgrd.sql:
ODMA_DIRECTIVE:BOUNCE_DATABASE:UPGRADE:
ODMA_DIRECTIVE:SCRIPT:UPGRADE:rdbms/admin/catuppst.sql:
ODMA_DIRECTIVE:SCRIPT:UPGRADE:sqlplus/admin/help/hlpbld.sql helpus.sql:
Thanks
With Regards
A-Z

Database Upgrade Assistant DBUA

Similar Messages

Maybe you are looking for