于2019-01-31 加入墨天轮
个人成就
发布0次内容
获得0次点赞
内容获得0次评论
获得0次收藏
回答了14次问答
动态
文章 ·0
数说 ·0
问答 ·14
文档 ·0
关注
留言板·0
ORA-12154: TNS: could not resolve the connect identifier specified
应用服务器telnet 端口 过去能通不嘛
提交回复于
2020-06-04
AWR报告中,read by other session ,如何解决?
应该尝试确定SQL中执行大量缓冲区获取和执行计划的语句,这些SQL中含有read by other session等待对应扫描的对象,通常这种执行时间都蛮长的,还要综合db file scattered read、db file sequential read相关的等待SQL去排查。
提交回复于
2020-05-25
expdp 导出表特别慢
If the table is partitioned, then there would be DataPump Worker processes active (where is the value of the parallel parameter), each unloading data from one of the table partitions.Include a where
提交回复于
2020-05-13
dblink连接提示密码错误
SOLUTIONEither:Create the link with no quotes around the username/password so that the credentials are interpreted in uppercase.SQL> create database link TARGET_DB CONNECT TO IDENTIFIED BY USING ‘TA
提交回复于
2020-05-08
dba_tablespace_usage_metrics中关于undo表空间使用率的问题
How to monitor Undo Tablespace Usage and the Free Space (Doc ID 1951400.1)The Undo Space once allocated wont be deallocated to the OS, by default. But the space can be reused by other transactions onc
提交回复于
2020-04-29
报错误:ora--1555 :快照过旧:回退段号 9(名称为 "_SYSSMU9_1650507775$")过小)
delete来处理你就不要想了,我觉得搞不出来,换个思维方式吧
提交回复于
2020-04-29
在集群环境中 nslookup scan_name 报;; conection timed out; no servers could be reached 正常吗?不是应该解释/etc/hosts里的IP吗
nslookup fails for normal users with error : connection timed out (Doc ID 1667077.1)
提交回复于
2019-12-24
rac其中一个节点一直刷Global Transaction Identifier Hash Collision Detected
这是12c中引入的,对hash算法进行了更改以适应PDB。Global Transaction Identifier hash collision risk with very similar Global Transaction ID (Doc ID 2016166.1)Global Transaction Identifier Hash Collision Detected MESSAGE I
提交回复于
2019-12-23
redo
不晓得这样可以解决问题不:1).找个非业务时段。2).创建另一个表B。3).将所需保留的数据INSERT(NOLOGGING)到新表B中。4).RENAME原始表A到A_BAK。5).RENAME表B为业务表。
提交回复于
2019-12-20
基于pdb搭建DG架构
提交回复于
2019-11-27