RMAN-08137: WARNING archived log not deleted, needed for standby or upstream capture process
When he tried deleting archivelog manually with RMAN on primary db host, he got following warning:
“归档日志未删除, 因为备用或上游捕获进程需要它”
Memory Notification: Heap size nnnnK exceeds notification threshold (51200K)
Memory Notification: Library Cache Object loaded into SGA
Heap size 106084K exceeds notification threshold (51200K)
KGL object name …
goldengate update collisions
Total updates 12.00
Total deletes 0.00
Total discards 0.00
Total operations 13.00
Total update collisions 12.00
sqlplus autotrace sql Statistics value全部为0
0 db block gets
0 consistent gets
0 physical reads
0 redo size
0 bytes sent via SQL*Net to client
0 bytes received via SQL*Net from client
0 SQL*Net roundtrips to/from client
0 sorts (memory)
0 sorts (disk)
62 rows processed
ora-600 [kcbgcur_9] internal error when ALTER DATABASE ADD SUPPLEMENTAL LOG DATA
SQL> ALTER DATABASE ADD SUPPLEMENTAL LOG DATA;
ALTER DATABASE ADD SUPPLEMENTAL LOG DATA
*
ERROR at line 1:
ORA-00600: internal error code, arguments: [kcbgcur_9], [8388681], [25],
[100663296], [33554432], [], [], []
计算controlfile size,dd 迁移raw device中的controlfile
Control Seq=53995=0xd2eb, File size=594=0x252
File Number=0, Blksiz=16384, File Type=1 CONTROL
Logical block number 1 (header block)
How to list all events?(oracle事件列表)
其中有两个编号段比较特殊
1,错误编号-10000到-10999 不是真正的错误,是保留下来用于debug使用
2,错误编号-20000到-20999是自定义异常,错误信息最大2048B
hanganalyze 分析 dbms_ijob.broken无效的问题
HANG ANALYSIS:
==============
Open chains found:
Chain 1 : :
<0/1777/32406/0x5275fca0/13913/SQL*Net message from client>
— <0/1477/37455/0x5275e4e8/16043/enq: TX - row lock contention>
ora-600 [3708] [910] internal error issue
SQL> shutdown immediate
ORA-00600: internal error code, arguments: [3708], [910], [], [], [], [], [], []
Basically this error is raised because LGWR timmed out.
ORA-00600 [keltnfy-ldmInit] internal error issue
ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [keltnfy-ldmInit], [46], [1], [], [], [], [], []
impdp network_link 在11201中导入分区表时行记录为0 rows?
. . imported “WEEJAR”.”HASH_OBJ”:”SYS_P23″ 0 rows
. . imported “WEEJAR”.”HASH_OBJ”:”SYS_P24″ 0 rows
. . imported “WEEJAR”.”HASH_OBJ”:”SYS_P21″ 0 rows
. . imported “WEEJAR”.”HASH_OBJ”:”SYS_P22″ 0 rows
10g r2 audit_trail db_extended 的错误提示
ORA-00096: invalid value db,extended for parameter audit_trail, must be from among extended, xml, db_extended, false, true, none, os, db
ORA-01078: failure in processing system parameters when srvctl start instance
[grid@znode1 ~]$ srvctl start instance -d rac -i rac1
PRCR-1013 : Failed to start resource ora.rac.db
PRCR-1064 : Failed to start resource ora.rac.db on node znode1
CRS-5017: The resource action “ora.rac.db start” encountered the following error:
ORA-01078: failure in processing system parameters
11203 RAC addNode.sh 遇PRKC-PRCF-2015 PRCF-2023
PRCF-2023 : The following contents are not transferred as they are non-readable.
Files:
1) /u01/app/11.2.0/grid/OCRDUMPFILE
2) /u01/app/11.2.0/grid/locr.lst
10gGridControl failed to start a managed process after the maximum retry limit
[oracle@dbserver1 bin]$ ./opmnctl startall
failed to start a managed process after the maximum retry limit
[error 13079] [ecid: -] No matching CACHE element found in
after OS reboot ,11g RAC asm not automatic startup ORA-27102
[ohasd(4507)]CRS-2807:Resource ‘ora.asm’ failed to start automatically.
SQL> startup nomount
ORA-27102: out of memory
OEL5.8 Install RAC Grid 11203 PRVF-5184 : Check of following Udev attributes failed
PRVF-5184 : Check of following Udev attributes of “rac2:/dev/asm-diskc” failed: “[Owner: Found=’root’ Expected=’grid’, Group: Found=’root’ Expected=’asmadmin’, Permissions: Found=’0600′ Expected=’0660′]”
11gr2 install database加大AMM内存时INS-35171
Oracle Error :: INS-35171
Target database memory (stringMB) exceeds at least one of the selected nodes available shared memory (string MB).
rac 11203 grid 安装PRVF-5636 : The DNS response time for an unreachable node exceeded “15000” ms
OUI默认是带域名的名称如znode1.anbob.com/znode1-vip.anbob.com,去掉改为了znode1/znode1-vip 新增加的znode2/znode2-vip,再下一步到检查的时,检查通过。
Never bind peeking or Wrong execution plan?
注意当用veriable变量绑定时sqlplus autotrace有可能显示的执行计划不是实际的,用dbms_xplan.display_cursor查看