Skip to Main Content

Oracle Database Discussions

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Errors from catupgrd

user13103775Jun 26 2014 — edited Jun 26 2014

Hi All,

I am in process of upgrading the 10.2.0.4.0 database to 11.2.0.4.0. during the run of catupgrd , I received and not sure , weather those can be ignored. Please put some light on this.

$> cat catupgrd_wmn1.log | grep ORA- | sort | uniq -c

   1   4   -- ignore error ORA-01920, happens if the script is re-run

   1   5   -- ORA-01920: user name 'ORDDATA' conflicts with another user or role name

   1  17    -- If the class does not exist an ORA-29532 (Uncaught Java

   1  19      -- ORA-01920: user name 'ORDDATA' conflicts with another user

   1  20    -- An ORA-30677 indicates that the requested session is already

   1  27    -- If the class does not exist, an ORA-29532 (Uncaught Java

   1  32    -- exist, an ORA-29532 (Uncaught Java exception) will occur.

   1  32  --   If a newRDT is not unique in the GeoRaster sysdata, ORA-13403 is raised.

   1  41    -- Likely errors to encounter here are ORA-00022, ORA-01031, ORA-30677,

   1  42    -- ORA-30681, ORA-30682, and ORA-30683.

   1  42    -- exist, an ORA-29532 (Uncaught Java exception) will occur.

   1  43    -- If the class does not exist an ORA-29532 (Uncaught Java

   1  48    --     can only connect itself.  ORA-00022 will be raised on attempts

   1  55    --     ORA-01031 will be raised otherwise.

   1  58    -- exist an ORA-29532 (Uncaught Java exception) will occur.

   1  59    -- If the class does not exist an ORA-29532 (Uncaught Java

   1  60    --     user; in such a case an ORA-01031 will be raised.

   1  74    -- exist an ORA-29532 (Uncaught Java exception) will occur.

   1  83    --   if an attempt without this option raised ORA-30677, then if the user

   1  88        -- extended processing sometimes results in a rollback error (ORA-01555)

   1  88  --      with an ORA-53068 error.

   1  96    -- An ORA-00022 exception may be raised here.

   2 .   ORA-00406: COMPATIBLE parameter needs to be 11.0.0.0.0 or greater ORA-00722:

   1 .   ORA-00722: Feature "Virtual columns" ORA-06512: at line 31

   1 .   ORA-00722: Feature "Virtual columns" ORA-06512: at line 43

   1 .   ORA-06512: at line 31

   1 .   ORA-06512: at line 43

   1 102    --     can only connect or disconnect itself.  ORA-00022 will be raised on

   1 1044  --   NO_RECOVERY_CATALOG (ORA-20300)

   1 1046  --   SEQUENCE_IS_NULL (ORA-20205)

   1 1048  --   LOG_MISSING (ORA-20206)

   1 108        -- extended processing sometimes results in a rollback error (ORA-01555)

   1 110      dbms_output.put_line('retrying because of ORA-01545');

   4 112    --   ORA-31001: Invalid resource handle or path name

   1 1283  --   TABLESPACE_DOES_NOT_EXIST (ORA-20202)

   1 1286  --   TRANSLATION_IN_PROGRESS (ORA-20203)

   1 1289  --   TRANSLATION_NOT_IN_PROGRESS (ORA-20204)

   1 131    --    ORA-23352

   1 1321  --   DATAFILE_DOES_NOT_EXIST (ORA-20201)

   1 1373  -- at a time until all rows are returned. Signal ORA-1403 (no-data-found)

   1 1462  --  NO_RECOVERY_CATALOG (ORA-20300)

   1 1466  --   TRANSLATION_IN_PROGRESS (ORA-20203)

   1 1469  --   TRANSLATION_NOT_IN_PROGRESS (ORA-20204)

   1 147    -- by this call.  ORA-30689 may also be raised.  Additionally, this call

   1 1471  --   THREAD_IS_NULL (ORA-20210)

   1 1475  --   UNTIL_TIME_IS_NULL (ORA-20212)

   1 1477  --   UNTIL_SCN_IS_NULL (ORA-20213)

   2 149      ORA-20000 - application error ( with an textile error stack)

   1 153            -- exceed 4000, otherwise it throws ORA-19011,

   4 159      -- ORA-31000: Resource '<name>' is not an XDB schema document

   1 1611  --   NO_RECOVERY_CATALOG (ORA-20300)

   1 164    --    ORA-23304 (malformedcall) if there is an defer_rpc_arg

   1 170                 -- ORA-25307: Enqueue rate too high, flow control enabled

   1 170      -- b.) resulted in ORA-6571 : ignore it

   1 1747  --   NO_RECOVERY_CATALOG (ORA-20300)

   1 1755  --   TRANSLATION_IN_PROGRESS (ORA-20203)

   1 1758  --   TRANSLATION_NOT_IN_PROGRESS (ORA-20204)

   2 187      ORA-20000 - application error ( with an textile error stack)

   1 1907  --   NO_RECOVERY_CATALOG (ORA-20300)

   1 1964  --   error ORA-13470 is raised.

   1 2023  --   If the point position is out of scope, ORA-13415 is raised.

   1 2078  --   NO_RECOVERY_CATALOG (ORA-20300)

   1 216    --    ORA-23304 (malformedcall) if the previous transaction

   2 217      ORA-20000 - application error (with a textile error stack)

   1 219    --    ORA-23319 Parameter value is not appropriate

   1 220    --    ORA-23352 Raised by dbms_defer.call if the node

   4 244    --   ORA-31001: Invalid resource handle or path name

   4 258    --   ORA-31001: Invalid resource handle or path name

   2 260      ORA-20000 - application error (with a textile error stack)

   1 2675  --   OFFLINE_RANGE_NOT_FOUND (ORA-20250)

   1 272    --    ORA-23304 (malformedcall) if the previous call not

   4 273    --   ORA-31001: Invalid resource handle or path name

   1 275    --    ORA-23319 Parameter value is not appropriate

   1 276    --    ORA-23352  If the destination list (specified by nodes or by a previous

   4 286    --   ORA-31001: Invalid resource handle or path name

   1 4885    --     signal error scf_not_in_bs (ORA-19695).

   1 611    -- If the java schema object does not exist an ORA-29532 (Uncaught Java

   1 929  --   DATABASE_NOT_FOUND (ORA-20001)

   1 932  --   DATABASE_INCARNATION_NOT_FOUND (ORA-20003)

   1 DOC>           ORA-06512: at "SYS.CHECK_EDITION_EXISTS", line 21

   1 DOC>           ORA-06512: at line 2

   1 DOC>           ORA-20000: Editioning view exists for non-edition enabled schema

   3 DOC>         ORA-01722: invalid number

   1 DOC>        The following statement will cause an "ORA-01722: invalid number"

   2 DOC>       The following PL/SQL block will cause an ORA-20000 error and

   3 DOC>       The following statement will cause an "ORA-01722: invalid number"

   1 DOC>       The following statements will cause an "ORA-01722: invalid number"

   3 DOC>   The following statement will cause an "ORA-01722: invalid number"

   2 ORA-00406: COMPATIBLE parameter needs to be 11.0.0.0.0 or greater

   2 ORA-00722: Feature "Virtual columns"

   2 ORA-06512: at line 31

   2 ORA-06512: at line 43

   3 SQL> ##   ORA-01476: divisor is equal to zero

   1 SQL> ##  ORA-29554: unhandled Java out of memory condition

   1 SQL> --  If this role exists, ORA-1921 is expected.

   1 SQL> -- Get utility functions, also compiles base types to avoid ORA-942 below

   1 SQL> -- ORA-942 errors and fail to compile if these types are invalid

   1 SQL> -- Suppress pre-existing object error ORA-00955

   1 SQL> -- avoid ORA-04068

   1 SQL> Rem                           avoid ORA-01425

   1 SQL> Rem                           needs to be cleared to avoid ORA-04068

   1 SQL> Rem      mode will result in ORA-39714.

   1 SQL> Rem     sdavidso   02/27/09 - bug 7567327: ORA-904 importing xmltype

   1 SQL> Rem    badeoti    05/13/09 - 8503519: handle ORA-30552 during index re-enabling

   1 SQL> Rem    sdavidso    02/27/09 - bug 7567327 - ORA-904 importing xmltype

   2 SQL> Rem    surman      06/01/09 - 8323978: Ignore ORA-4080 error

   1 SQL> Rem    tcruanes    06/10/06 - reset package state to avoid ORA-04068

   2 SQL> Rem The following clears the package state and avoids ORA-4068.

   1 SQL> rem   ORA-31604: invalid NAME parameter "PARSE" for object

Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Jul 24 2014
Added on Jun 26 2014
5 comments
3,751 views