ORA-1089 : opidrv aborting process P031 ospid (6914_1)Fri Aug 22 14:54:18 2008ORA-1089 : opidrv aborting process P025 ospid (6902_1)License high water mark = 88Fri Aug 22 14:54:18 2008ORA-1089 : opidrv aborting process unknown ospid (14203_1)Fri Aug 22 14:54:18 2008ORA-1089 : opidrv aborting process unknown ospid (5144_1)Fri Aug 22 14:54:18 2008ORA-1089 : opidrv aborting process unknown ospid (5362_1)Fri Aug 22 14:54:19 2008ORA-1089 : opidrv aborting process unknown ospi

在EM 里把数据库blackout 现在想end blackout 报错了Error stopping the blackout on "kpdbps01.jewelry.acn": ORA-20706: The blackout is already pending stop ORA-06512: at "SYSMAN.MGMT_BLACKOUT_ENGINE", line 3239 ORA-06512: at "SYSMAN.MGMT_BLACKOUT", line 74 ORA-06512: at "SYSMAN.MGMT_BLACKOUT_UI", line 1167 ORA-06512: at line 1 .

检查日志发现ORA-01555ORA-01555 caused by SQL statement below (SQL ID: b216nhn3aztwz, Query Duration=1220836370 sec, SCN: 0x000a.14e62847):Sun Sep7 21:12:50 2008SELECT * FROM RELATIONAL("FILENET_ADMIN"."INVOICE_SPOOL") SUBPARTITION ("INVOICE_SPOOL_M4_2008_S00059")但是RELATIONAL这个“函数”没玩过，不知道啥意思！然后SQL> select objecT_NAME ,OWNER FROM DBA_OBJECTS WHERE OBJECT_NAME ='RELATIONAL';no rows selectedSQL>select objecT_NAME ,OWNER FROM DBA_OBJECTS WHERE OBJEC

怎么区分是由于程序设计引起的死锁还是由于自己数据库表参数的设计的缺陷？

This deadlock has the following cause:If a data record is locked in the database, this lock information iswritten to the block. The space provided in the block header is used forthis. The space is defined when the table is created with the parametersINITRANS and maxtrans. If a block becomes too full, the database cannotallocate any more space to store this block and must wait for memory spacein the corresponding block. As a result, row level locking can become blocklevel locking

alter database backup controlfile to '/oracle/archlogs/lcca/cf02.bak' reuseCompleted: alter database backup controlfile to '/oracle/archWed May7 22:31:23 2008Errors in file /oracle/apps/admin/lcca/udump/lcca_ora_178414.trc:ORA-27037: unable to obtain file statusIBM AIX RISC System/6000 Error: 2: No such file or directoryAdditional information: 4Wed May7 22:31:23 2008Errors in file /oracle/apps/admin/lcca/udump/lcca_ora_187014.trc:ORA-27037: unable to obtain file status

Bug 2610353 - Dump / memory corruption possible from remote selectDescriptionDump / memory corruption can occur when doing a selectof a remote table if the remote table contains "hidden"columns (such as SYS_NC_OID$ , SYS_NC_ROWINFO$ etc).During select of remote table the local session performsa describe of the table then checks whether any indexesreference any columns of that table.Workaround:Remove the index/s on the table (may not be feasible)这个是在metali