This discussion is archived
0 Replies Latest reply: Nov 25, 2012 5:36 PM by eli101 RSS

Ops Center EC upgrade error's with no DB table space

eli101 Newbie
Currently Being Moderated
Hi I am not a DBA so not sure what to do, all I know is the ASM disk group still has plenty of disk space,
I am trying to upgrade EC from 12.1.1.2076 to 12.1.2.2161, but the installer is exiting with an error of no DB space. below if the db error log,
-------------------------------
[..]snip
. estimated "OPSMONDB"."WINPM_REPORT_TEMPLATE_UPDATES" 0 KB
. estimated "OPSMONDB"."WINPM_TARGETS" 0 KB
. estimated "OPSMONDB"."WINPM_UPDATES" 0 KB
Total estimation using BLOCKS method: 8.515 GB
Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA
Processing object type SCHEMA_EXPORT/TYPE/TYPE_SPEC
Processing object type SCHEMA_EXPORT/SEQUENCE/SEQUENCE
Processing object type SCHEMA_EXPORT/TABLE/TABLE
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.CREATE_OBJECT_ROWS [TABLE]
TABLE:"OPSMONDB"."HD_PERSISTENT_MBEAN"
ORA-01691: unable to extend lob segment OPSMONDB.SYS_LOB0000096542C00045$$ by 128 in tablespace USERS
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 105
ORA-06512: at "SYS.KUPW$WORKER", line 9007
----- PL/SQL Call Stack -----
object line object
handle number name
40d69a598 20462 package body SYS.KUPW$WORKER
40d69a598 9028 package body SYS.KUPW$WORKER
40d69a598 7924 package body SYS.KUPW$WORKER
40d69a598 10810 package body SYS.KUPW$WORKER
40d69a598 2728 package body SYS.KUPW$WORKER
40d69a598 9697 package body SYS.KUPW$WORKER
40d69a598 1775 package body SYS.KUPW$WORKER
40d5191c8 2 anonymous block
Job "OPSMONDB"."SYS_EXPORT_SCHEMA_02" stopped due to fatal error at 17:18:12
-------
ASMCMD> lsdg
State Type Rebal Sector Block AU Total_MB Free_MB Req_mir_free_MB Usable_file_MB Offline_disks Voting_files Name
MOUNTED EXTERN N 512 4096 1048576 1048576 1004400 0 1004400 0 N DATA/
------
Not sure how to fix this issue, any help is greatly appreciated.
Eli

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points