BlockRecover之ORA-00494

凌晨00:10左右接到监控电话,说库连接异常,随即起床登陆主机一看,库实例已然crash掉啦,查告警日志:
Mon Mar 23 20:45:24 2015
Thread 1 advanced to log sequence 234601 (LGWR switch)
  Current log# 3 seq# 234601 mem# 0: /dev/oravg/rgsinas_redo13
Mon Mar 23 20:48:28 2015
KCF: write/open error block=0x840 online=1
     file=204 /dev/vg01/rora_data207
     error=65535 txt: ''
Automatic datafile offline due to write error on
file 204: /dev/vg01/rora_data207
Mon Mar 23 21:16:30 2015
Errors in file /oracle/admin/jhdb/bdump/jhdb_lgwr_4176.trc:
ORA-00494: enqueue [CF] held for too long (more than 900 seconds) by 'inst 1, osid 4169'
Mon Mar 23 21:16:32 2015
System State dumped to trace file /oracle/admin/jhdb/bdump/jhdb_lgwr_4176.trc
Killing enqueue blocker (pid=4169) on resource CF-00000000-00000000
 by killing session 825.1
Mon Mar 23 21:21:42 2015
Errors in file /oracle/admin/jhdb/bdump/jhdb_lgwr_4176.trc:
ORA-00494: enqueue [CF] held for too long (more than 900 seconds) by 'inst 1, osid 4169'
Mon Mar 23 21:21:44 2015
System State dumped to trace file /oracle/admin/jhdb/bdump/jhdb_lgwr_4176.trc
Killing enqueue blocker (pid=4169) on resource CF-00000000-00000000
 by terminating the process
LGWR: terminating instance due to error 2103
Mon Mar 23 21:21:55 2015
Instance terminated by LGWR, pid = 4176


随即用dbv检查file 204发现:
Corrupt block relative dba: 0x33000840 (file 204, block 2112)
gsinas01[/oracle]$dbv file='/dev/vg01/rora_data207';
DBVERIFY: Release 10.2.0.4.0 - Production on Fri Mar 27 10:24:43 2015
Copyright (c) 1982, 2007, Oracle.  All rights reserved.
DBVERIFY - Verification starting : FILE = /dev/vg01/rora_data207
Page 2106 is influx - most likely media corrupt
Corrupt block relative dba: 0x3300083a (file 204, block 2112)
Fractured block found during dbv: 
Data in bad block:
 type: 6 format: 2 rdba: 0x3300083a
 last change scn: 0x0cd1.9978968d seq: 0x2 flg: 0x06
 spare1: 0x0 spare2: 0x0 spare3: 0x0
 consistency value in tail: 0x74ab0602
 check value in block header: 0x414f
 computed block checksum: 0x73bb
DBVERIFY - Verification complete
Total Pages Examined         : 1048575
Total Pages Processed (Data) : 1020
Total Pages Failing   (Data) : 0
Total Pages Processed (Index): 1145
Total Pages Failing   (Index): 0
Total Pages Processed (Other): 18
Total Pages Processed (Seg)  : 0
Total Pages Failing   (Seg)  : 0
Total Pages Empty            : 1046391
Total Pages Marked Corrupt   : 1
Total Pages Influx           : 1
Highest block SCN            : 2574816070 (3281.2574816070)
file为204,blk id为2112;

入库检查对应204 file为/dev/vg01/rora_data207,其状态如下:
select STATUS,name from v$datafile;
ONLINE  /dev/oravg/rora_data204
ONLINE  /dev/oravg/rora_data205
ONLINE  /dev/oravg/rora_data189
ONLINE  /dev/oravg/rora_data23
ONLINE  /dev/vg01/rora_data206
RECOVER /dev/vg01/rora_data207
ONLINE  /dev/vg01/rora_data208
ONLINE  /dev/vg01/rora_data209
ONLINE  /dev/vg01/rora_data210
ONLINE  /dev/vg01/rora_data211
SQL> SELECT segment_name,segment_type FROM dba_extents  WHERE file_id=204 AND 2112 BETWEEN block_id AND block_id + blocks -1;

SEGMENT_NAME                          SEGMENT_TYPE
--------------------------------------------------------------------------------- ------------------
IDX_CONSTRUCTIONCRM_SUCCFLAG 

SQL> select count(*) from inas.CONSTRUCTIONCRM;
select count(*) from inas.CONSTRUCTIONCRM
                          *
ERROR at line 1:
ORA-00376: file 204 cannot be read at this time
ORA-01110: data file 204: '/dev/vg01/rora_data207'

SQL> SELECT owner,segment_name,segment_type FROM dba_extents  WHERE file_id=204 AND 2112 BETWEEN block_id AND block_id + blocks -1;

OWNER                          SEGMENT_NAME                          SEGMENT_TYPE
------------------------------ --------------------------------------------------------------------------------- ------------------
INAS                           IDX_CONSTRUCTIONCRM_SUCCFLAG          INDEX
所幸的是对应坏块的是个应用索引。

果断进行块恢复:
SQL> host
$ rman target /
Recovery Manager: Release 10.2.0.4.0 - Production on Tue Mar 24 10:00:34 2015
Copyright (c) 1982, 2007, Oracle.  All rights reserved.
connected to target database: JHDB (DBID=923949890)
RMAN> 

RMAN> RUN {
2> ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE' parms='ENV=(NB_ORA_CLIENT=gsinas01,NB_ORA_POLICY=OSS_gsinas01_Oracle_Full_Backup)'; 
3> BLOCKRECOVER DATAFILE 204 BLOCK  2112;
4> }

released channel: ORA_DISK_1
allocated channel: ch00
channel ch00: sid=1491 devtype=SBT_TAPE
channel ch00: Veritas NetBackup for Oracle - Release 7.6 (2014042414)
Starting blockrecover at 24-MAR-15
channel ch00: restoring block(s)
channel ch00: specifying block(s) to restore from backup set
restoring blocks of datafile 00204
channel ch00: reading from backup piece bk_20333_1_874973991
channel ch00: restored block(s) from backup piece 1
piece handle=bk_20333_1_874973991 tag=HOT_DB_BK_LEVEL0
channel ch00: block restore complete, elapsed time: 00:05:55
starting media recovery
media recovery complete, elapsed time: 00:03:46

Finished blockrecover at 24-MAR-15
released channel: ch00
RMAN> 
RMAN>  backup validate datafile 204;

Starting backup at 24-MAR-15
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=1491 devtype=DISK
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00204 name=/dev/vg01/rora_data207
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:04
Finished backup at 24-MAR-15
RMAN> 

RMAN> recover datafile 204;

Starting recover at 24-MAR-15
using channel ORA_DISK_1

starting media recovery
archive log thread 1 sequence 234600 is already on disk as file /arch1/1_234600_704593860.dbf
archive log thread 1 sequence 234601 is already on disk as file /arch1/1_234601_704593860.dbf
archive log thread 1 sequence 234602 is already on disk as file /arch1/1_234602_704593860.dbf
archive log thread 1 sequence 234603 is already on disk as file /arch1/1_234603_704593860.dbf
archive log thread 1 sequence 234604 is already on disk as file /arch1/1_234604_704593860.dbf
archive log thread 1 sequence 234605 is already on disk as file /arch1/1_234605_704593860.dbf
archive log thread 1 sequence 234606 is already on disk as file /arch1/1_234606_704593860.dbf
archive log filename=/arch1/1_234600_704593860.dbf thread=1 sequence=234600
archive log filename=/arch1/1_234601_704593860.dbf thread=1 sequence=234601
archive log filename=/arch1/1_234602_704593860.dbf thread=1 sequence=234602
media recovery complete, elapsed time: 00:00:06
Finished recover at 24-MAR-15
RMAN> 
入库查询:
SQL> alter database datafile 204 online;
Database altered.
SQL> select count(*) from inas.CONSTRUCTIONCRM;
  COUNT(*)
----------
   1499634

STATUS  NAME
------- ------------------------------
ONLINE  /dev/oravg/rora_data204
ONLINE  /dev/oravg/rora_data205
ONLINE  /dev/oravg/rora_data189
ONLINE  /dev/oravg/rora_data23
ONLINE  /dev/vg01/rora_data206
ONLINE  /dev/vg01/rora_data207
ONLINE  /dev/vg01/rora_data208
ONLINE  /dev/vg01/rora_data209
ONLINE  /dev/vg01/rora_data210
ONLINE  /dev/vg01/rora_data211

再用dbv检查file情况:
$ dbv file='/dev/vg01/rora_data207';

DBVERIFY: Release 10.2.0.4.0 - Production on Tue Mar 24 10:14:30 2015
Copyright (c) 1982, 2007, Oracle.  All rights reserved.
DBVERIFY - Verification starting : FILE = /dev/vg01/rora_data207
DBVERIFY - Verification complete

Total Pages Examined         : 1048575
Total Pages Processed (Data) : 1020
Total Pages Failing   (Data) : 0
Total Pages Processed (Index): 1146
Total Pages Failing   (Index): 0
Total Pages Processed (Other): 18
Total Pages Processed (Seg)  : 0
Total Pages Failing   (Seg)  : 0
Total Pages Empty            : 1046391
Total Pages Marked Corrupt   : 0
Total Pages Influx           : 0
Highest block SCN            : 2567939499 (3281.2567939499)
$ 
无报错,都恢复正常。

原本的错误:
ORA-01110: 数据文件 204: '/dev/vg01/rora_data207'
ORA-06512: 在 "INASQM.P_BACK_UP_EWS_QM", line 16
ORA-06512: 在 line 1
Tue Mar 24 08:14:54 2015
Errors in file /oracle/admin/jhdb/bdump/jhdb_j000_10062.trc:
ORA-12012: 自动执行作业 425 出错
ORA-00376: 此时无法读取文件 204
ORA-01110: 数据文件 204: '/dev/vg01/rora_data207'
ORA-06512: 在 "INASQM.P_BACK_UP_EWS_QM", line 16
ORA-06512: 在 line 1

已经终止报错:

Tue Mar 24 10:46:50 2015
Thread 1 advanced to log sequence 234608 (LGWR switch)
  Current log# 2 seq# 234608 mem# 0: /dev/oravg/rgsinas_redo12
  
至此故障已经恢复,库恢复正常,无中断;然而之前的告警报错仍然有问题可循,以下供参考:

1 ORA-00494: enqueue [CF] held for too long (more than 900 seconds); LGWR:Terminating Instance Due to Error 2103 (文档 ID 1089733.1)

Applies to: 
 Oracle Database - Enterprise Edition - Version 10.2.0.4 and later
Information in this document applies to any platform.
Symptoms
You see the following issue in the alert.log:

KCF: write/open error block=0x9a989 online=1
file=7 /Oratemp/oradata/M6DTH/temp07.dbf
error=27063 txt: 'IBM AIX RISC System/6000 Error: 28: No space left on device
Additional information: -1
Additional information: 24576'
Automatic tempfile offline due to write error on
file 7: /Oratemp/oradata/M6DTH/temp07.dbf

ORA-00494: enqueue [CF] held for too long (more than 900 seconds) by 'inst 1, osid 2876448'

LGWR: terminating instance due to error 2103
ORA-02103: PCC: inconsistent cursor cache (out-of-range cuc ref)

Some or all of the following function codes may be found in the 'stack trace' portion of the associated trace file.:
------------- Call Stack ---------------
sskgpwwait
skgpwwait
ksliwat
kslwaitns_timed
kskthbwt
kslwait
kcbbpibr
kcfbsy
kcfbof
kcfofa
ksbabs
ksbrdp
opirip
opidrv
sou2o
opimai_real
main
__start() 

Cause

Bug 7600269 closed as a duplicate of  Bug:7411568
Bug:9273547 closed as a duplicate of Bug:7411568

Trace file/alert log matches that in the bug
1) Starts with space error and file offline
2) Sessions are waiting for CF enqueue
3) Arguments ksliwat   kslwaitns_timed  kskthbwt  kslwait... match that in the call stack of bug
4) There is a wait on kcbzps and occurs with DBWR

Solution
 Apply Patch 7411568
2 如果不打补丁用隐含参数也可以避免,但没有测试是否稳妥:

通过隐含参数禁止Oracle主动kill CF锁的持有进程,禁止Oracle去kill所有持有CF锁的进程:

_kill_controlfile_enqueue_blocker=false

也可以通过设置另外一个隐含参数禁止Oracle去kill持有锁的后台进程:

_kill_enqueue_blocker=1(默认为3)

进程请求CF enqueue的time out时间默认是900秒,这是由下面的参数控制的:

_controlfile_enqueue_timeout=900

进程持有CF enqueue的时间最长不能超过120秒:

_controlfile_enqueue_holding_time=120


3 网友惜分飞的不补充说明:
补充说明
1.在9i中使用blockrecover会在Archive destination中生产block的备份文件,类似469_519791_3063_2442393528.bkd(file 469 block 519791),需要注意Archive destination目录结尾需要”/”,不然可能出现直接写入和该目录并列的Archive destination+blockrecover产生文件;10g中不生成该文件;如果该block在9i中未备份,也不会在生产相关文件,而是利用归档恢复.
2.blockrecover需要还原从该block从备份之后的所有归档(如果被备份起来需要还原出来),如果缺少归档可能导致恢复失败,包括基于scn/seq/time的等
3.blockrecover在执行过程中或者执行异常终止,该block依然是坏块,不会对其他block产生影响.在使用blockrecover出现异常终止后的block修复,在后续blog中提供解决方法
4.对于不含事务的坏块,如果数据允许丢失可以通过设置event跳过坏块(特殊block除外),然后重建对象;对于含event的block 坏块,建议使用blockrecover处理或者直接恢复数据文件,如果没有备份,考试使用event跳过事务回滚,然后屏蔽坏块处理

  
         

来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/13750068/viewspace-1471545/,如需转载,请注明出处,否则将追究法律责任。

转载于:http://blog.itpub.net/13750068/viewspace-1471545/

大数据与宠物:健康监测数据分析 随着全球宠物市场规模的快速增长(2023年全球宠物产业规模已达3500亿美元),宠物健康管理需求呈现指数级上升。传统宠物医疗依赖定期体检和症状观察,存在滞后性和主观性缺陷。本文聚焦如何通过物联网(IoT)设备采集宠物生理数据(体温、心率、活动量等),利用大数据分析技术构建实时健康监测系统,实现宠物健康状态的动态评估、异常预警和疾病预测。研究范围涵盖数据采集技术、数据预处理方法、机器学习模型构建及实际应用场景落地。背景介绍:明确研究目的、目标读者及核心术语核心概念与联系。 阅读详情

相关推荐

泰森多面体Voronoi 3D-V5.0 功能介绍

Abaqus Voronoi3D

qq_34840441的博客 3366

oracle 数据库down,ORA-00494导致数据库down机

ORA-00494导致数据库down机数据库down机,以下是alter日志中的一段:Thu May 27 11:56:19 2010Errors in file /opt/oracle/admin/devpay2/bdump/devpay2_lgwr_17668.trc:ORA-00494: enqueue [CF] held for too long (more than 900 second...

weixin_42502345的博客 915

centos7部署mysql8.0.35,主从复制,主主集群

centos7 linux部署mysql,主从复制,主主模式

zaixiaqin的博客 1990

oracle导出报错936错误,【案例】Oracle报错ORA-00494产生原因和MOS官方解决办法

天萃荷净Oracle研究中心案例分析:运维DBA反映Oracle数据库出现异常并报错database crash with ora-00494,分析原因为CF锁异常导致。本站文章除注明转载外,均为本站原创: 转载自love wife & love life —Roger 的Oracle技术博客本文链接地址: database crash with ora-00494database cra...

weixin_34185033的博客 1116

用户行为数据分析 User Behavior Data from Taobao for Recommendation

一、提出问题 二、理解数据 数据来源 阿里云天池数据集:(https://tianchi.aliyun.com/dataset/dataDetail?dataId=649) 本文选取的数据集为UserBehavior.csv,共有5242880条数据。数据的具体类别如下表所示: 用户行为种类有四种,如下表所示 对于数据维度的说明如下: 在本文选取的2017年11月25日到2017年12月3日的时间范围内,不重复的用户数量为10202,不重复的商品ID数为412369,不重复的商品类目ID数为5859,

cccxxxqq的博客 5207

WRF-BEM相关参数说明

本参数适用于WRF-BEM模拟武汉市气候。

m0_60013472的博客 1896

ora-00494引起rac宕机的分析处理

1、问题分析 12月1日早上8:20,客户报障说数据库无法连接上,使用sqlplus连接也无法连上。我本人,通过远程工具连接上去,发现数据库好的,并且检查集群如下: [oracle@myrac1 ~]$ crs...

coujiongyong0208的博客 418

星空组网 vs 蒲公英 vs Tailscale:2024年国内免费异地组网工具横评(含实测数据)

本文对2024年国内主流免费异地组网工具星空组网、蒲公英和Tailscale进行了深度横向评测。基于实测数据,重点分析了三者在P2P成功率、中继延迟、传输速度及稳定性方面的表现,为中小企业、远程办公及个人开发者提供了清晰的选择指南。星空组网在国内网络环境下展现出优秀的平衡性。

weixin_29217235的博客 1448

ORA-00494: enqueue [CF] held for too long (more than 900 seconds) cause instance crash

故障现象:alert 日志 Restarting dead background process MMON Tue May 16 17:24:51 2017 Process 0x0x6b0f14da8 appears to be hung while dumping Current time = 465593890, process death time = 465533027 inter

Lixora's DB Home 2048

新能源场站必看:一次调频与AGC/AVC的协同控制逻辑解析(含典型拓扑图)

本文深度解析了新能源场站中一次调频与AGC/AVC的协同控制逻辑。针对电网频率与电压稳定需求,详细阐述了三者在响应时序、控制目标上的分工与配合,并重点剖析了以RCL-0923装置为核心的指令融合架构与典型拓扑,为场站实现高效、稳定的协同运行提供了清晰的实践指导。

brown的博客 1071

Nvidia AGX Xavier刷机指北

因为工作的关系,要在AGX上安装CUDA。nvidia官网上没找到适合AGX版本的CUDA,只能走刷机的路子。刷机过程中,也遇到一些坑,做个记录。 需要有一台ubuntu系统的电脑作为主机Host。我的主机系统为Ubuntu18.04 整个刷机过程为: 在Host上安装sdkmanager,整个刷机过程主要通过sdkmanager来操作。 在Host自动下载一些系统组件,各种deb包 Host上制作OS系统镜像,烧录到AGX中 Host上之前下载好的deb包,安装到AGX中。 完结,撒花 ...

sinat_38685124的博客 6296

oracle cf enqueue,ORA-00494,enqueue [CF]故障诊断

这次事故还要追述到2个月前,当时客户发现数据库宕机了,从客户发过来到截图可以看到数据库在hang死的时候报ORA-00494:enqueue[CF] held for too long(more than 900 seconds)错误,同时伴随着这个日志还有一个trace,可惜当时空间满了,这个trace被清理掉了.关于这次错误,也前前后后去了几个人去看了,因为没有那个trace文件,所以都无法断...

weixin_32297123的博客 551

基于Simulink的自适应控制(Adaptive Control)电励磁同步电动机

目录基于Simulink的自适应控制(Adaptive Control)电励磁同步电动机项目实例1. 项目背景2. 系统架构2.1 电励磁同步电动机模型2.2 三相逆变器模型2.3 自适应控制器(Adaptive Controller)2.4 系统框图3. 模型设计3.1 创建Simulink模型3.2 自适应控制(Adaptive Control)设计3.3 仿真环境搭建4. 参数优化4.1 自动调优5. 实际应用案例5.1 工业驱动系统5.2 风力发电系统6. 结论进一步优化建议需求分析电励磁同步电动机

MHD0815的博客 267

Oracle10204高负载触发ORA00494错误

原 Oracle 10.2.0.4 高负载 触发 ORA-00494 错误https://blog.youkuaiyun.com/tianlesoftware/article/details/6609276版权声明: https://blog.youkuaiyun.com/tianlesoftware/article/details/6609276 MOS 上有一篇文章专门介绍这个问题,参考:[ID 779552.1...

rede 665

数学建模模型总结

这是本人在两年内准备参加数学建模竞赛搜集到的模型资料,已经经过了本人的筛选和整理,希望能够对准备参加数学建模竞赛的学弟学妹们提供一些帮助!

复分析 阿尔福斯(Ahlfors) 第三版答案 英文

答案分为十章,有部分习题没有答案,全英文复分析阿尔福斯(Ahlfors) 第三版答案

ORA-00494 enqueue [CF] held for too long故障分析处理

今天接应用人员电话反应,一套备份数据库在加完表空间后出现异常,现象是数据库能查询,但是update很慢。 故障处理详细: 1、查看alert日志如下: Thread 1 advanced to log sequen...

905

IDEA的使用指南

IDEA基于java的使用手册,可以最快速的上手,在使用中不断的丰富自己的使用技巧.

Oracle-linux服务器的声卡依赖包导致数据库宕机

Linux的声卡文件导致数据库触发ORA-00494宕机

qqqyyy0422的博客 238

Data-Structures-and-Algorithm-Analysis-in-Java.pdf

作者: Weiss, Mark A. 出版社: Addison Wesley Data Structures and Algorithm Analysis in Java is an “advanced algorithms” book that fits between traditional CS2 and Algorithms Analysis courses. In the old ACM Curriculum Guidelines, this course was known as CS7. This text is for readers who want to learn good programming and algorithm analysis skills simultaneously so that they can develop such programs with the maximum amo...

ORA-00494: enqueue [CF] held for too long (more than 900 seconds)

近日某客户数据库凌晨5点左右crash,报如下错误: Fri Nov 11 03:17:51 2016 Thread 1 advanced to log sequence 583682 (LGWR switch) Cu...

cuizhi4718的博客 371

10gR2.0.4数据库压力较大,IO发生短暂停止响应的时候,可能导致数据库实例崩溃...

From:NingooOracle10.2.0.4中,如果数据库压力较大,IO发生短暂停止响应的时候,可能导致数据库实例崩溃。在alert中可以找到如下错误:Thu Apr 2 10:55:36 2009 Errors in...

conghai7026的博客 243

oracle cf enqueue,ORA-00494 enqueue [CF] held for too long故障分析处理

今天接应用人员电话反应,一套备份数据库在加完表空间后出现异常,现象是数据库能查询,但是update很慢。故障处理详细:1、查看alert日志如下:Thread 1 advanced to log sequence 16541 (LGWR switch)Current log# 1 seq# 16541 mem# 0: +DATA/racdb/onlinelog/group_1.262.792077...

weixin_29534463的博客 542

资源耗尽导致ORA-494错误

一个客户的STANDBY数据库出现了ORA-494的错误。 数据库服务器建立在IBM的POWER 7利用LPAR划分的逻辑分区上,目前上面只有一个备库在跑日志应用,前一天利用...

ckawt40802的专栏 674

ORA-00494: enqueue [CF] held for too long (more than 900 seconds) -RAC

客户的一台rac一个月hang死一次,上次重启机器后一切正常,这次必须一次性解决,生产库不可能老是重启赛。 ##############################################系统软件日志:syslog...

csdn0622的博客 411

oracle Database Crashes With ORA-00494

Call stackTEMP 76.57。

Lixora's DB Home 1244

下班收到的ora-00494

下班回家路上接到用户邮件,一个库意外crash。 回家

heavenmouse的专栏 867

Oracle 10.2.0.4 高负载 触发 ORA-00494 错误

MOS 上有一篇文章专门介绍这个问题,参考:[ID 779552.1]。   在Oracle 10.2.0.4版本中,alert log 可能出现如下错误:        ORA-00494:enqueue [CF] held for too long (m

小宝老豆的专栏 789

oracle cf enqueue,ORA-00494: enqueue [CF] held for too long (more than 900 seconds)

网上一个朋友遇到数据库启动不了,具体信息如下数据库版本: ORA 10G R2主机 HPUNIX现象: 当startup之后,数据库一直停留在 database mounted状态。一直Open不鸟~。alter log 文件(节选)如下:Fri Nov 11 09:31:01 2011Completed: ALTER DATABASE MOUNTFri Nov 11 09:31:08 201...

weixin_42132359的博客 368

ORA-00494: enqueue [CF…

tarting background process CJQ0 Sat Oct 13 06:57:49 2012 CJQ0 started with pid=96, OS id=8195 Sat Oct 13 07:18:04 2012 Suspending MMON slave action kewrmafsa_ for 82800 seconds Sat Oct 13 07:53:05 201

babymouse1212的博客 625
上一篇: How to create user for oracle10g/11g asm instance
下一篇: Drop Column之ORA-01732
cppg67031
博客等级 码龄12年 2粉丝 0原创
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符  | 博主筛选后可见
 
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付:10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值