Hola Miguel:

Gracias por el apoyo creo que ya resolvi el problema, lo que ahora quisiera saber como hacer con los parametros de inicialización de oracle 9i, es decir, que valores correspondientes seran en oracle 10g.

Saludos,

mpalacios_pe escribió:Hola

Al parecer pueden ser dos motivos. Tendras acceso a http://metalink.oracle.com?

1) Segun nota 332796.1

1. Edit OH/rdmbs/admin/utlu102x.sql and change:
IF ts_info(i).inc_by > 0 OR ts_info(i).addl > 0 THEN
IF ts_info(i).fauto = FALSE THEN
to
IF ts_info(i).inc_by > 0 OR ts_info(i).addl > 0 THEN
IF ts_info(i).fauto = FALSE AND ts_info(i).inc_by > 0 THEN

2. Rerun DBUA

2) Segun nota 360399.1

Cause
A possible cause for this is bug 4864648 which creates a problem for DBUA when the SYS user’s temporary tablespace is dictionary managed.

Solution
A fix for bug 4864648 will be included in the 10.2.0.3 patchset.
As long as this is not available 2 workarounds can be used, one to make the tool workaround the problem itself, the other one not to use the tool:

1. An easy workaround should be to create a locally managed temporary tablespace and assign this as the temp tablespace for the SYS user (in the original database), and then do the migration.
2. Do not use DBUA to do the migration but follow the manual steps as per documentation and/or metalink notes.

To implement the first workaround, and to verify if you indeed run into bug 4864648, you can use the following steps:

Verify which tablespace is the temporary tablespace of the SYS user (see the dba_users view)
Verify that this tablespace is indeed dictionary managed (see dba_tablespaces, column EXTENT_MANAGEMENT)
Create a new locally managed tablespace to be used as the temporary tablespace of the SYS user, and ALTER the sys user so that it indeed becomes this.
Retry the upgrade to 10.2 after these changes