Mon Jun 11 14:06:23 2018 Exception [type: SIGSEGV, SI_KERNEL(general_protection)] [ADDR:0x0] [PC:0xC9CCF40, rwsstd()+32] [flags: 0x0, count: 1] Errors in file /u01/app/oracle/diag/rdbms/salesstdydb/salesstdydb/trace/salesstdydb_p000_161906.trc (incident=600440) (PDBNAME=SALESPDB): ORA-07445: : תrwsstd()+32]
vi /u01/app/oracle/diag/rdbms/salesstdydb/salesstdydb/trace/salesstdydb_p000_161906.trc
Exception [type: SIGSEGV, SI_KERNEL(general_protection)] [ADDR:0x0] [PC:0xC9CCF40, rwsstd()+32] [flags: 0x0, count: 1] Incident 600440 created, dump file: /u01/app/oracle/diag/rdbms/salesstdydb/salesstdydb/incident/incdir_600440/salesstdydb_p000_161906_i600440.trc ORA-07445: ³öÏÖÒì³£´íÎó: ºËÐÄת´¢ [rwsstd()+32]
ssexhd: crashing the process... Shadow_Core_Dump = PARTIAL ksdbgcra: writing core file to directory '/u01/app/oracle/diag/rdbms/salesstdydb/salesstdydb/cdump'
~ ~
Description
This bug is only relevant when using Connect By / Hierarchical Queries A CONNECT BY query with filter/access predicates involving operators like DECODE, case expressions ,NVL with subqueries and columns from multiple tables might run into compilation errors and wrong results. Rediscovery Notes If a CONNECT BY query with subqueries in WHERE predicates fail during type checking phase then you might have encountered the same problem. Workaround alter session set "_connect_by_use_union_all" = false;
Please note: The above is a summary description only. Actual symptoms can vary. Matching to any symptoms here does not confirm that you are encountering this problem. For questions about this bug please consult Oracle Support. |
SQL> col name for a30
SQL> col description for a50
SELECT name,description from SYS.V$PARAMETER WHERE name LIKE '\_%' ESCAPE '\';
NAME DESCRIPTION
------------------------------ --------------------------------------------------
_undo_autotune enable auto tuning of undo_retention
_optimizer_use_feedback optimizer use feedback
日积月累
