ROLE:*CATALOG_ROLE

最新推荐文章于 2022-06-29 10:42:51 发布
转载 最新推荐文章于 2022-06-29 10:42:51 发布 · 244 阅读 · 0
文章标签：

#数据库

本文介绍了Oracle8中新增的角色权限，包括DELETE_CATALOG_ROLE、SELECT_CATALOG_ROLE和EXECUTE_CATALOG_ROLE。这些角色分别允许用户删除审计记录、查询数据字典以及执行数据字典中的过程和函数。
DELETE_CATALOG_ROLE角色：是Oracle8新增加的，如果授予用户这个角色，用户就可以从表
sys.aud$中删除记录，sys.aud$表中记录着审计后的记录，
使用这个角色可以简化审计踪迹管理。
SELECT_CATALOG_ROLE角色：具有从数据字典查询的权利，
EXECUTE_CATALOG_ROLE角色：具有从数据字典中执行部分过程和函数的权利。[@more@]

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

转载于:http://blog.itpub.net/10599713/viewspace-1001548/

cneo2012
关注
ORA-00600:[kcratr_nab_less_than_odr], 分析解决
ZSY老司机的博客
11-13 1908
今天，在测试库测试时，在alter database open 时发现报： ORA-00600: 内部错误代码, 参数: [kcratr_nab_less_than_odr], [1], [290], [8227],[10276], [], [], [], [], [], [], [] 导致原因：这可能是由于控制文件的缺失，或者在线日志文件在实例恢复时不完整 尝试以下操作均未成功： ...
oracle select_catalog_role,*_CATALOG_ROLE 简述
weixin_35665083的博客
04-06 1979
今天犯了一个傻，有一个人抄了一个小纸条，上面写道 catalog_role，问我这个视图是干嘛用的，我也不知道，没有针对某些普通用户受过这个角色，后来他问我，catalog是干嘛的，那我当然知道了，catalog是rman可以用到的资料库，于是我的方向就错了，后来上网查了一下，呵呵，纠正了自己的错误：1. SELECT_CATALOG_ROLEThis role can be granted to...
*_CATALOG_ROLE 简述
cr147369的博客
08-18 206
今天犯了一个傻，有一个人抄了一个小纸条，上面写道 catalog_role，问我这个视图是干嘛用的，我也不知道，没有针对某些普通用户受过这个角色，后来他问我，catalog是干嘛的，那我当然知道了，catalog是rman可以用...
Oracle权限管理详解(原创)
czmmiao的专栏
12-11 1366
Oracle 权限 权限允许用户访问属于其它用户的对象或执行程序，ORACLE系统提供三种权限：Object 对象级、System 系统级、Role 角色级。这些权限可以授予给用户、特殊用户public或角色，如果授予一个权限给特殊用户"Public"（用户public是oracle预定义的，每个用户享有这个用户享有的权限）,那么就意味作将该权限授予了该数据库的所有用户。 对管理权限而...
【OCP学习1z0-052记录11】 SELECT_CATALOG_ROLE
viviliving的专栏
03-13 1304
68: View the Exhibit to observe the roles assigned to the SL_REP user. Which statement is true about the assignment of the SELECT_CATALOG_ROLE role to the SL_REP user?A.The user must enable the role e...
工作中，我们经常用到哪些SQL语句呢？
再小的帆也能远航，把分享变成一种习惯
01-09 1358
工作中我们基本上每天都要与数据库打交道，数据库的知识点呢也特别多，全部记住呢也是不可能的，也没必要把所有的记住（有些语句命令可能我们一辈子都用不到）。 所以呢在工作之余，把工作中经常用到的一些语句整理出来，忘记的时候可以当做字典来查。 个人在工作中用Oracle数据库比较多，就以关系型数据库Oracle为例进行整理，后面可能会整理一些非关系型数据库，如mogodb之类的。 如果你觉得有所价值可以参考。如果有不全或者错误的也欢迎大家指正。 一、DDL部分（create、drop、alte...
XDG_SESSION_ID=15 HOSTNAME=controller SELINUX_ROLE_REQUESTED= TERM=vt100 SHELL=/bin/bash HISTSIZE=1000 SSH_CLIENT=192.168.100.1 50232 22 SELINUX_USE_CURRENT_RANGE= SSH_TTY=/dev/pts/1 OS_USER_DOMAIN_NAME=default USER=rootLS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=01;05;37;41:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.axv=01;35:*.anx=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=01;36:*.au=01;36:*.flac=01;36:*.mid=01;36:*.midi=01;36:*.mka=01;36:*.mp3=01;36:*.mpc=01;36:*.ogg=01;36:*.ra=01;36:*.wav=01;36:*.axa=01;36:*.oga=01;36:*.spx=01;36:*.xspf=01;36:OS_PROJECT_NAME=admin MAIL=/var/spool/mail/root PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin OS_IDENTITY_API_VERSION=3 PWD=/root OS_PASSWORD=000000 LANG=en_US.UTF-8 SELINUX_LEVEL_REQUESTED= OS_AUTH_URL=http://controller:5000/v3 HISTCONTROL=ignoredups OS_USERNAME=admin SHLVL=1 HOME=/root LOGNAME=root SSH_CONNECTION=192.168.100.1 50232 192.168.100.10 22 LESSOPEN=||/usr/bin/lesspipe.sh %s XDG_RUNTIME_DIR=/run/user/0 _=/usr/bin/env
最新发布
11-11
> `Could not find requested endpoint in Service Catalog` --- ### ✅ 正确的环境变量设置应包含以下内容： ```bash export OS_USERNAME=admin export OS_PASSWORD=000000 export OS_PROJECT_NAME=admin export...
page.get_by_role("button", name="CT 增配标准保养-享 配置主机 IB信息 IB 数量：0").click() page.get_by_label("CT 增配标准保养-享 配置主机 IB信息IB 数量：0确定").get_by_role("row", name="Catalog Name Description").locator("span").nth(1).click() page.get_by_role("button", name="CT 增配探测器保用-享 配置主机 IB信息 IB 数量：").click() page.get_by_label("CT 增配探测器保用-享 配置主机 IB信息IB 数量：0").get_by_role("row", name="Catalog Name Description").locator("span").nth(1).click(); try: page.wait_for_timeout(3000) # 获取页面中所有的文本内容 page_text = page.text_content('body') print(f"📄 页面文本长度: {len(page_text)} 字符") # 查找所有APM开头的项目 import re apm_pattern = r'APM\d+' apm_matches = re.findall(apm_pattern, page_text) print(f"🔍 找到APM开头的数据: {apm_matches}") # 查找所有Intervention开头的项目 inter_pattern = r'Intervention\d+' inter_matches = re.findall(inter_pattern, page_text) print(f"🔍 找到Intervention开头的数据: {inter_matches}") # 查找所有FI开头的项目 fi_pattern = r'FI\d+' fi_matches = re.findall(fi_pattern, page_text) print(f"🔍 找到FI开头的数据: {fi_matches}") # 查找所有NM开头的项目 nm_pattern = r'NM\d+' nm_matches = re.findall(nm_pattern, page_text) print(f"🔍 找到NM开头的数据: {nm_matches}") # 查找所有MI开头的项目 mi_pattern = r'MI\d+' mi_matches = re.findall(mi_pattern, page_text) print(f"🔍 找到MI开头的数据: {mi_matches}") # 查找所有DI开头的项目 di_pattern = r'DI\d+' di_matches = re.findall(di_pattern, page_text) print(f"🔍 找到DI开头的数据: {di_matches}") # 查找所有US开头的项目 us_pattern = r'US\d+' us_matches = re.findall(us_pattern, page_text) print(f"🔍 找到US开头的数据: {us_matches}") # 查找所有探头保修开头的项目 ttbx_pattern = r'探头保修\d+' ttbx_matches = re.findall(ttbx_pattern, page_text) print(f"🔍 找到探头保修开头的数据: {ttbx_matches}") # 查找所有限额备件人工合同开头的项目 xebj_pattern = r'限额备件人工合同\d+' xebj_matches = re.findall(xebj_pattern, page_text) print(f"🔍 找到限额备件人工合同开头的数据: {xebj_matches}") # 查找所有Parts Sales开头的项目 ps_pattern = r'Parts Sales\d+' ps_matches = re.findall(ps_pattern, page_text) print(f"🔍 找到Parts Sales开头的数据: {ps_matches}") # 查找所有DXR开头的项目 dxr_pattern = r'DXR\d+' dxr_matches = re.findall(dxr_pattern, page_text) print(f"🔍 找到DXR开头的数据: {dxr_matches}") # 查找所有Surgery开头的项目 sur_pattern = r'Surgery\d+' sur_matches = re.findall(sur_pattern, page_text) print(f"🔍 找到Surgery开头的数据: {sur_matches}") # 查找所有单次开头的项目 dc_pattern = r'单次\d+' dc_matches = re.findall(dc_pattern, page_text) print(f"🔍 找到单次开头的数据: {dc_matches}") # 查找所有定制化培训开头的项目 dzh_pattern = r'定制化培训\d+' dzh_matches = re.findall(dzh_pattern, page_text) print(f"🔍 找到定制化培训开头的数据: {dzh_matches}") # 查找所有CT开头的项目 ct_pattern = r'CT\d+' ct_matches = re.findall(ct_pattern, page_text) print(f"🔍 找到CT开头的数据: {ct_matches}") # 查找所有MR开头的项目 mr_pattern = r'MR\d+' mr_matches = re.findall(mr_pattern, page_text) print(f"🔍 找到MR开头的数据: {mr_matches}") # 查找所有CN开头的项目 cn_pattern = r'CN\d+' cn_matches = re.findall(cn_pattern, page_text) print(f"🔍 找到CN开头的数据: {cn_matches}") # 查找所有TUS开头的项目 tus_pattern = r'TUS\d+' tus_matches = re.findall(tus_pattern, page_text) print(f"🔍 找到TUS开头的数据: {tus_matches}") # 查找所有智爱养护开头的项目 zayh_pattern = r'智爱养护\d+' zayh_matches = re.findall(zayh_pattern, page_text) print(f"🔍 找到智爱养护开头的数据: {zayh_matches}") # 查找所有PCB开头的项目 pcb_pattern = r'PCB\d+' pcb_matches = re.findall(pcb_pattern, page_text) print(f"🔍 找到PCB开头的数据: {pcb_matches}") # 提取apm_name print("9.2 提取apm_name...") if apm_matches: apm_name = apm_matches[0] # 取第一个apm_name print(f"✅ 成功提取apm_name: {apm_name}") else: apm_name = None print("❌ 未找到apm_name") # 提取inter_name print("9.3 提取inter_name") if inter_matches: inter_name = inter_matches[0] # 取第一个inter_name print(f"✅ 成功提取inter_name: {inter_name}") else: inter_name = None print("❌ 未找到inter_name") # 提取fi_name print("9.3 提取fi_name") if fi_matches: fi_name = fi_matches[0] # 取第一个fi_name print(f"✅ 成功提取fi_name: {fi_name}") else: fi_name = None print("❌ 未找到fi_name") # 提取nm_name print("9.3 提取nm_name") if nm_matches: nm_name = nm_matches[0] # 取第一个nm_name print(f"✅ 成功提取nm_name: {nm_name}") else: nm_name = None print("❌ 未找到nm_name") # 提取mi_name print("9.3 提取mi_name") if mi_matches: mi_name = mi_matches[0] # 取第一个mi_name print(f"✅ 成功提取mi_name: {mi_name}") else: mi_name = None print("❌ 未找到mi_name") # 提取di_name print("9.3 提取di_name") if di_matches: di_name = di_matches[0] # 取第一个di_name print(f"✅ 成功提取di_name: {di_name}") else: di_name = None print("❌ 未找到di_name") # 提取us_name print("9.3 提取us_name") if us_matches: us_name = us_matches[0] # 取第一个us_name print(f"✅ 成功提取us_name: {us_name}") else: us_name = None print("❌ 未找到us_name") # 提取ttbx_name print("9.3 提取ttbx_name") if ttbx_matches: ttbx_name = ttbx_matches[0] # 取第一个ttbx_name print(f"✅ 成功提取ttbx_name: {ttbx_name}") else: ttbx_name = None print("❌ 未找到ttbx_name") # 提取xebj_name print("9.3 提取xebj_name") if xebj_matches: xebj_name = xebj_matches[0] # 取第一个xebj_name print(f"✅ 成功提取xebj_name: {xebj_name}") else: xebj_name = None print("❌ 未找到xebj_name") # 提取ps_name print("9.3 提取ps_name") if ps_matches: ps_name = ps_matches[0] # 取第一个ps_name print(f"✅ 成功提取ps_name: {ps_name}") else: ps_name = None print("❌ 未找到ps_name") # 提取dxr_name print("9.3 提取dxr_name") if dxr_matches: dxr_name = dxr_matches[0] # 取第一个dxr_name print(f"✅ 成功提取dxr_name: {dxr_name}") else: dxr_name = None print("❌ 未找到dxr_name") # 提取sur_name print("9.3 提取sur_name") if sur_matches: sur_name = sur_matches[0] # 取第一个sur_name print(f"✅ 成功提取sur_name: {sur_name}") else: sur_name = None print("❌ 未找到sur_name") # 提取dc_name print("9.3 提取dc_name") if dc_matches: dc_name = dc_matches[0] # 取第一个dc_name print(f"✅ 成功提取dc_name: {dc_name}") else: dc_name = None print("❌ 未找到dc_name") # 提取dzh_name print("9.3 提取dzh_name") if dzh_matches: dzh_name = dzh_matches[0] # 取第一个dzh_name print(f"✅ 成功提取dzh_name: {dzh_name}") else: dzh_name = None print("❌ 未找到dzh_name") # 提取ct_name print("9.3 提取ct_name") if ct_matches: ct_name = ct_matches[0] # 取第一个ct_name print(f"✅ 成功提取ct_name: {ct_name}") else: ct_name = None print("❌ 未找到ct_name") # 提取mr_name print("9.3 提取mr_name") if mr_matches: mr_name = mr_matches[0] # 取第一个mr_name print(f"✅ 成功提取mr_name: {mr_name}") else: mr_name = None print("❌ 未找到mr_name") # 提取cn_name print("9.3 提取cn_name") if cn_matches: cn_name = cn_matches[0] # 取第一个cn_name print(f"✅ 成功提取cn_name: {cn_name}") else: cn_name = None print("❌ 未找到cn_name") # 提取tus_name print("9.3 提取tus_name") if tus_matches: tus_name = tus_matches[0] # 取第一个tus_name print(f"✅ 成功提取tus_name: {tus_name}") else: tus_name = None print("❌ 未找到tus_name") # 提取zayh_name print("9.3 提取zayh_name") if zayh_matches: zayh_name = zayh_matches[0] # 取第一个zayh_name print(f"✅ 成功提取zayh_name: {zayh_name}") else: zayh_name = None print("❌ 未找到zayh_name") # 提取pcb_name print("9.3 提取pcb_name") if pcb_matches: pcb_name = pcb_matches[0] # 取第一个pcb_name print(f"✅ 成功提取pcb_name: {pcb_name}") else: pcb_name = None print("❌ 未找到pcb_name") except Exception as e: print(f"❌ 获取页面数据失败: {e}") apm_name = None inter_name = None fi_name = None nm_name = None mi_name = None di_name = None us_name = None ttbx_name = None xebj_name = None ps_name = None dxr_name = None sur_name = None dc_name = None dzh_name = None ct_name = None mr_name = None cn_name = None tus_name = None zayh_name = None pcb_name = None 这两段代码结合，改成从页面识别到CT开头的数据，点击该数据，并且勾选它
10-14
page.get_by_label("CT 增配标准保养-享 配置主机 IB信息IB 数量：0确定").get_by_role("row", name="Catalog Name Description").locator("span").nth(1).click() page.get_by_role("button", name="CT 增配探测器...
2025-09-22 11:11:37.538: watchdog pid 902555: DEBUG: sending watchdog packet to socket:7, type:[M], command ID:24557, data Length:124 2025-09-22 11:11:37.539: watchdog pid 902555: DEBUG: received watchdog packet type:I 2025-09-22 11:11:37.539: watchdog pid 902555: DEBUG: reading packet type I of length 369 2025-09-22 11:11:37.539: watchdog pid 902555: DEBUG: STATE MACHINE INVOKED WITH EVENT = PACKET RECEIVED Current State = LEADER 2025-09-22 11:11:37.539: watchdog pid 902555: DEBUG: received packet, watchdog node:[192.168.1.72:9999 Linux localhost.localdomain] command id:[24557] type:[NODE INFO] state:[LEADER] 2025-09-22 11:11:37.539: watchdog pid 902555: DEBUG: packet I with command ID 24557 is reply to the command M 2025-09-22 11:11:37.539: watchdog pid 902555: DEBUG: Watchdog node "192.168.1.72:9999 Linux localhost.localdomain" has replied for command id 24557 2025-09-22 11:11:37.539: watchdog pid 902555: DEBUG: command I with command id 24557 is finished with COMMAND_FINISHED_ALL_REPLIED 2025-09-22 11:11:37.539: watchdog pid 902555: DEBUG: STATE MACHINE INVOKED WITH EVENT = COMMAND FINISHED Current State = LEADER 2025-09-22 11:11:37.539: watchdog pid 902555: DEBUG: I am the cluster leader node command finished with status:[ALL NODES REPLIED] 2025-09-22 11:11:37.539: watchdog pid 902555: DETAIL: The command was sent to 1 nodes and 1 nodes replied to it 2025-09-22 11:11:37.548: watchdog pid 902555: DEBUG: received watchdog packet type:d 2025-09-22 11:11:37.549: watchdog pid 902555: DEBUG: reading packet type d of length 62 2025-09-22 11:11:37.549: watchdog pid 902555: DEBUG: STATE MACHINE INVOKED WITH EVENT = PACKET RECEIVED Current State = LEADER 2025-09-22 11:11:37.549: watchdog pid 902555: DEBUG: received packet, watchdog node:[192.168.1.72:9999 Linux localhost.localdomain] command id:[24954] type:[DATA REQUEST FOR LEADER] state:[LEADER] 2025-09-22 11:11:37.549: watchdog pid 902555: DEBUG: sending packet, watchdog node:[192.168.1.72:9999 Linux localhost.localdomain] command id:[24954] type:[DATA] state:[LEADER] 2025-09-22 11:11:37.549: watchdog pid 902555: DEBUG: sending watchdog packet to socket:7, type:[D], command ID:24954, data Length:110 2025-09-22 11:11:37.924: health_check1 pid 902636: DEBUG: health check: clearing alarm 2025-09-22 11:11:37.924: health_check1 pid 902636: DEBUG: SSL is requested but SSL support is not available 2025-09-22 11:11:37.926: health_check1 pid 902636: DEBUG: authenticate kind = 10 2025-09-22 11:11:37.935: health_check1 pid 902636: DEBUG: SCRAM authentication successful for user:pgpool 2025-09-22 11:11:37.935: health_check1 pid 902636: DEBUG: authenticate backend: key data received 2025-09-22 11:11:37.935: health_check1 pid 902636: DEBUG: authenticate backend: transaction state: I 2025-09-22 11:11:37.935: health_check1 pid 902636: DEBUG: health check: clearing alarm 2025-09-22 11:11:37.935: health_check1 pid 902636: DEBUG: health check: clearing alarm 2025-09-22 11:11:38.969: heart_beat_sender pid 902601: DEBUG: watchdog heartbeat: send heartbeat signal to 192.168.1.72:9694 2025-09-22 11:11:40.969: heart_beat_sender pid 902601: DEBUG: watchdog heartbeat: send heartbeat signal to 192.168.1.72:9694 2025-09-22 11:11:42.544: watchdog pid 902555: DEBUG: new IPC connection received 2025-09-22 11:11:42.544: watchdog pid 902555: DEBUG: sending watchdog packet to socket:9, type:[7], command ID:0, data Length:34 2025-09-22 11:11:42.544: sr_check_worker pid 903049: DEBUG: watchdog status: 4 2025-09-22 11:11:42.544: watchdog pid 902555: DEBUG: new IPC connection received 2025-09-22 11:11:42.544: watchdog pid 902555: DEBUG: received the get data request from local pgpool-II on IPC interface 2025-09-22 11:11:42.544: watchdog pid 902555: DEBUG: sending watchdog packet to socket:9, type:[7], command ID:0, data Length:0 2025-09-22 11:11:42.544: sr_check_worker pid 903049: DEBUG: 1:0: Unexpected 2025-09-22 11:11:42.545: watchdog pid 902555: DEBUG: new IPC connection received 2025-09-22 11:11:42.545: watchdog pid 902555: DEBUG: sending watchdog packet to socket:9, type:[7], command ID:0, data Length:34 2025-09-22 11:11:42.545: sr_check_worker pid 903049: DEBUG: quorum: 1 node_count: -1 2025-09-22 11:11:42.545: sr_check_worker pid 903049: DEBUG: pool_acquire_follow_primary_lock: lock was not held by anyone 2025-09-22 11:11:42.545: sr_check_worker pid 903049: DEBUG: pool_acquire_follow_primary_lock: succeeded in acquiring lock 2025-09-22 11:11:42.545: sr_check_worker pid 903049: DEBUG: SSL is requested but SSL support is not available 2025-09-22 11:11:42.547: sr_check_worker pid 903049: DEBUG: authenticate kind = 10 2025-09-22 11:11:42.555: sr_check_worker pid 903049: DEBUG: SCRAM authentication successful for user:rep 2025-09-22 11:11:42.555: sr_check_worker pid 903049: DEBUG: authenticate backend: key data received 2025-09-22 11:11:42.555: sr_check_worker pid 903049: DEBUG: authenticate backend: transaction state: I 2025-09-22 11:11:42.555: sr_check_worker pid 903049: DEBUG: do_query: extended:0 query:"SELECT pg_catalog.pg_is_in_recovery()" 2025-09-22 11:11:42.556: sr_check_worker pid 903049: DEBUG: verify_backend_node_status: there's no primary node 2025-09-22 11:11:42.556: sr_check_worker pid 903049: DEBUG: node status[0]: 0 2025-09-22 11:11:42.556: sr_check_worker pid 903049: DEBUG: node status[1]: 2 2025-09-22 11:11:42.556: sr_check_worker pid 903049: DEBUG: pool_release_follow_primary_lock called 2025-09-22 11:11:42.935: health_check1 pid 902636: DEBUG: health check: clearing alarm 2025-09-22 11:11:42.936: health_check1 pid 902636: DEBUG: SSL is requested but SSL support is not available 2025-09-22 11:11:42.938: health_check1 pid 902636: DEBUG: authenticate kind = 10 2025-09-22 11:11:42.946: health_check1 pid 902636: DEBUG: SCRAM authentication successful for user:pgpool 2025-09-22 11:11:42.947: health_check1 pid 902636: DEBUG: authenticate backend: key data received 2025-09-22 11:11:42.947: health_check1 pid 902636: DEBUG: authenticate backend: transaction state: I 2025-09-22 11:11:42.947: health_check1 pid 902636: DEBUG: health check: clearing alarm 2025-09-22 11:11:42.947: health_check1 pid 902636: DEBUG: health check: clearing alarm 2025-09-22 11:11:42.969: heart_beat_sender pid 902601: DEBUG: watchdog heartbeat: send heartbeat signal to 192.168.1.72:9694 2025-09-22 11:11:44.969: heart_beat_sender pid 902601: DEBUG: watchdog heartbeat: send heartbeat signal to 192.168.1.72:9694 2025-09-22 11:11:46.970: heart_beat_sender pid 902601: DEBUG: watchdog heartbeat: send heartbeat signal to 192.168.1.72:9694 2025-09-22 11:11:47.550: watchdog pid 902555: DEBUG: STATE MACHINE INVOKED WITH EVENT = TIMEOUT Current State = LEADER 2025-09-22 11:11:47.550: watchdog pid 902555: DEBUG: sending packet, watchdog node:[192.168.1.72:9999 Linux localhost.localdomain] command id:[24558] type:[IAM COORDINATOR] state:[LEADER] 2025-09-22 11:11:47.550: watchdog pid 902555: DEBUG: sending watchdog packet to socket:7, type:[M], command ID:24558, data Length:124 2025-09-22 11:11:47.551: watchdog pid 902555: DEBUG: received watchdog packet type:I 2025-09-22 11:11:47.551: watchdog pid 902555: DEBUG: reading packet type I of length 369 2025-09-22 11:11:47.551: watchdog pid 902555: DEBUG: STATE MACHINE INVOKED WITH EVENT = PACKET RECEIVED Current State = LEADER 2025-09-22 11:11:47.551: watchdog pid 902555: DEBUG: received packet, watchdog node:[192.168.1.72:9999 Linux localhost.localdomain] command id:[24558] type:[NODE INFO] state:[LEADER] 2025-09-22 11:11:47.551: watchdog pid 902555: DEBUG: packet I with command ID 24558 is reply to the command M 2025-09-22 11:11:47.551: watchdog pid 902555: DEBUG: Watchdog node "192.168.1.72:9999 Linux localhost.localdomain" has replied for command id 24558 2025-09-22 11:11:47.551: watchdog pid 902555: DEBUG: command I with command id 24558 is finished with COMMAND_FINISHED_ALL_REPLIED 2025-09-22 11:11:47.551: watchdog pid 902555: DEBUG: STATE MACHINE INVOKED WITH EVENT = COMMAND FINISHED Current State = LEADER 2025-09-22 11:11:47.551: watchdog pid 902555: DEBUG: I am the cluster leader node command finished with status:[ALL NODES REPLIED] 2025-09-22 11:11:47.551: watchdog pid 902555: DETAIL: The command was sent to 1 nodes and 1 nodes replied to it 2025-09-22 11:11:47.560: watchdog pid 902555: DEBUG: received watchdog packet type:d 2025-09-22 11:11:47.560: watchdog pid 902555: DEBUG: reading packet type d of length 62 2025-09-22 11:11:47.560: watchdog pid 902555: DEBUG: STATE MACHINE INVOKED WITH EVENT = PACKET RECEIVED Current State = LEADER 2025-09-22 11:11:47.560: watchdog pid 902555: DEBUG: received packet, watchdog node:[192.168.1.72:9999 Linux localhost.localdomain] command id:[24955] type:[DATA REQUEST FOR LEADER] state:[LEADER] 2025-09-22 11:11:47.560: watchdog pid 902555: DEBUG: sending packet, watchdog node:[192.168.1.72:9999 Linux localhost.localdomain] command id:[24955] type:[DATA] state:[LEADER] 2025-09-22 11:11:47.560: watchdog pid 902555: DEBUG: sending watchdog packet to socket:7, type:[D], command ID:24955, data Length:110 2025-09-22 11:11:47.947: health_check1 pid 902636: DEBUG: health check: clearing alarm 2025-09-22 11:11:47.948: health_check1 pid 902636: DEBUG: SSL is requested but SSL support is not available 2025-09-22 11:11:47.949: health_check1 pid 902636: DEBUG: authenticate kind = 10 2025-09-22 11:11:47.958: health_check1 pid 902636: DEBUG: SCRAM authentication successful for user:pgpool 2025-09-22 11:11:47.958: health_check1 pid 902636: DEBUG: authenticate backend: key data received 2025-09-22 11:11:47.958: health_check1 pid 902636: DEBUG: authenticate backend: transaction state: I 2025-09-22 11:11:47.958: health_check1 pid 902636: DEBUG: health check: clearing alarm 2025-09-22 11:11:47.958: health_check1 pid 902636: DEBUG: health check: clearing alarm 2025-09-22 11:11:48.970: heart_beat_sender pid 902601: DEBUG: watchdog heartbeat: send heartbeat signal to 192.168.1.72:9694 2025-09-22 11:11:50.971: heart_beat_sender pid 902601: DEBUG: watchdog heartbeat: send heartbeat signal to 192.168.1.72:9694 2025-09-22 11:11:52.557: watchdog pid 902555: DEBUG: new IPC connection received 2025-09-22 11:11:52.557: watchdog pid 902555: DEBUG: sending watchdog packet to socket:9, type:[7], command ID:0, data Length:34 2025-09-22 11:11:52.557: sr_check_worker pid 903049: DEBUG: watchdog status: 4 2025-09-22 11:11:52.557: watchdog pid 902555: DEBUG: new IPC connection received 2025-09-22 11:11:52.557: watchdog pid 902555: DEBUG: received the get data request from local pgpool-II on IPC interface 2025-09-22 11:11:52.557: watchdog pid 902555: DEBUG: sending watchdog packet to socket:9, type:[7], command ID:0, data Length:0 2025-09-22 11:11:52.557: sr_check_worker pid 903049: DEBUG: 1:0: Unexpected 2025-09-22 11:11:52.557: watchdog pid 902555: DEBUG: new IPC connection received 2025-09-22 11:11:52.557: watchdog pid 902555: DEBUG: sending watchdog packet to socket:9, type:[7], command ID:0, data Length:34 2025-09-22 11:11:52.557: sr_check_worker pid 903049: DEBUG: quorum: 1 node_count: -1 2025-09-22 11:11:52.558: sr_check_worker pid 903049: DEBUG: pool_acquire_follow_primary_lock: lock was not held by anyone 2025-09-22 11:11:52.558: sr_check_worker pid 903049: DEBUG: pool_acquire_follow_primary_lock: succeeded in acquiring lock 2025-09-22 11:11:52.558: sr_check_worker pid 903049: DEBUG: SSL is requested but SSL support is not available 2025-09-22 11:11:52.560: sr_check_worker pid 903049: DEBUG: authenticate kind = 10 2025-09-22 11:11:52.569: sr_check_worker pid 903049: DEBUG: SCRAM authentication successful for user:rep 2025-09-22 11:11:52.569: sr_check_worker pid 903049: DEBUG: authenticate backend: key data received 2025-09-22 11:11:52.569: sr_check_worker pid 903049: DEBUG: authenticate backend: transaction state: I 2025-09-22 11:11:52.569: sr_check_worker pid 903049: DEBUG: do_query: extended:0 query:"SELECT pg_catalog.pg_is_in_recovery()" 2025-09-22 11:11:52.570: sr_check_worker pid 903049: DEBUG: verify_backend_node_status: there's no primary node 2025-09-22 11:11:52.570: sr_check_worker pid 903049: DEBUG: node status[0]: 0 2025-09-22 11:11:52.570: sr_check_worker pid 903049: DEBUG: node status[1]: 2 2025-09-22 11:11:52.570: sr_check_worker pid 903049: DEBUG: pool_release_follow_primary_lock called 2025-09-22 11:11:52.959: health_check1 pid 902636: DEBUG: health check: clearing alarm 2025-09-22 11:11:52.960: health_check1 pid 902636: DEBUG: SSL is requested but SSL support is not available 2025-09-22 11:11:52.961: health_check1 pid 902636: DEBUG: authenticate kind = 10 2025-09-22 11:11:52.970: health_check1 pid 902636: DEBUG: SCRAM authentication successful for user:pgpool 2025-09-22 11:11:52.970: health_check1 pid 902636: DEBUG: authenticate backend: key data received 2025-09-22 11:11:52.970: health_check1 pid 902636: DEBUG: authenticate backend: transaction state: I 2025-09-22 11:11:52.970: health_check1 pid 902636: DEBUG: health check: clearing alarm 2025-09-22 11:11:52.970: health_check1 pid 902636: DEBUG: health check: clearing alarm 2025-09-22 11:11:52.971: heart_beat_sender pid 902601: DEBUG: watchdog heartbeat: send heartbeat signal to 192.168.1.72:9694 2025-09-22 11:11:54.971: heart_beat_sender pid 902601: DEBUG: watchdog heartbeat: send heartbeat signal to 192.168.1.72:9694 2025-09-22 11:11:56.972: heart_beat_sender pid 902601: DEBUG: watchdog heartbeat: send heartbeat signal to 192.168.1.72:9694 2025-09-22 11:11:57.563: watchdog pid 902555: DEBUG: STATE MACHINE INVOKED WITH EVENT = TIMEOUT Current State = LEADER 2025-09-22 11:11:57.563: watchdog pid 902555: DEBUG: sending packet, watchdog node:[192.168.1.72:9999 Linux localhost.localdomain] command id:[24559] type:[IAM COORDINATOR] state:[LEADER] 2025-09-22 11:11:57.563: watchdog pid 902555: DEBUG: sending watchdog packet to socket:7, type:[M], command ID:24559, data Length:124 2025-09-22 11:11:57.564: watchdog pid 902555: DEBUG: received watchdog packet type:I 2025-09-22 11:11:57.564: watchdog pid 902555: DEBUG: reading packet type I of length 369 2025-09-22 11:11:57.564: watchdog pid 902555: DEBUG: STATE MACHINE INVOKED WITH EVENT = PACKET RECEIVED Current State = LEADER 2025-09-22 11:11:57.564: watchdog pid 902555: DEBUG: received packet, watchdog node:[192.168.1.72:9999 Linux localhost.localdomain] command id:[24559] type:[NODE INFO] state:[LEADER] 2025-09-22 11:11:57.564: watchdog pid 902555: DEBUG: packet I with command ID 24559 is reply to the command M 2025-09-22 11:11:57.564: watchdog pid 902555: DEBUG: Watchdog node "192.168.1.72:9999 Linux localhost.localdomain" has replied for command id 24559 2025-09-22 11:11:57.564: watchdog pid 902555: DEBUG: command I with command id 24559 is finished with COMMAND_FINISHED_ALL_REPLIED 2025-09-22 11:11:57.564: watchdog pid 902555: DEBUG: STATE MACHINE INVOKED WITH EVENT = COMMAND FINISHED Current State = LEADER 2025-09-22 11:11:57.564: watchdog pid 902555: DEBUG: I am the cluster leader node command finished with status:[ALL NODES REPLIED] 2025-09-22 11:11:57.564: watchdog pid 902555: DETAIL: The command was sent to 1 nodes and 1 nodes replied to it 2025-09-22 11:11:57.573: watchdog pid 902555: DEBUG: received watchdog packet type:d 2025-09-22 11:11:57.573: watchdog pid 902555: DEBUG: reading packet type d of length 62 2025-09-22 11:11:57.573: watchdog pid 902555: DEBUG: STATE MACHINE INVOKED WITH EVENT = PACKET RECEIVED Current State = LEADER 2025-09-22 11:11:57.573: watchdog pid 902555: DEBUG: received packet, watchdog node:[192.168.1.72:9999 Linux localhost.localdomain] command id:[24956] type:[DATA REQUEST FOR LEADER] state:[LEADER] 2025-09-22 11:11:57.573: watchdog pid 902555: DEBUG: sending packet, watchdog node:[192.168.1.72:9999 Linux localhost.localdomain] command id:[24956] type:[DATA] state:[LEADER] 2025-09-22 11:11:57.573: watchdog pid 902555: DEBUG: sending watchdog packet to socket:7, type:[D], command ID:24956, data Length:110 2025-09-22 11:11:57.971: health_check1 pid 902636: DEBUG: health check: clearing alarm 2025-09-22 11:11:57.971: health_check1 pid 902636: DEBUG: SSL is requested but SSL support is not available 2025-09-22 11:11:57.973: health_check1 pid 902636: DEBUG: authenticate kind = 10 2025-09-22 11:11:57.981: health_check1 pid 902636: DEBUG: SCRAM authentication successful for user:pgpool 2025-09-22 11:11:57.981: health_check1 pid 902636: DEBUG: authenticate backend: key data received 2025-09-22 11:11:57.981: health_check1 pid 902636: DEBUG: authenticate backend: transaction state: I 2025-09-22 11:11:57.981: health_check1 pid 902636: DEBUG: health check: clearing alarm 2025-09-22 11:11:57.981: health_check1 pid 902636: DEBUG: health check: clearing alarm 2025-09-22 11:11:58.972: heart_beat_sender pid 902601: DEBUG: watchdog heartbeat: send heartbeat signal to 192.168.1.72:9694 2025-09-22 11:12:00.972: heart_beat_sender pid 902601: DEBUG: watchdog heartbeat: send heartbeat signal to 192.168.1.72:9694 2025-09-22 11:12:02.570: watchdog pid 902555: DEBUG: new IPC connection received 2025-09-22 11:12:02.570: watchdog pid 902555: DEBUG: sending watchdog packet to socket:9, type:[7], command ID:0, data Length:34 2025-09-22 11:12:02.570: sr_check_worker pid 903049: DEBUG: watchdog status: 4 2025-09-22 11:12:02.570: watchdog pid 902555: DEBUG: new IPC connection received 2025-09-22 11:12:02.571: watchdog pid 902555: DEBUG: received the get data request from local pgpool-II on IPC interface 2025-09-22 11:12:02.571: watchdog pid 902555: DEBUG: sending watchdog packet to socket:9, type:[7], command ID:0, data Length:0 2025-09-22 11:12:02.571: sr_check_worker pid 903049: DEBUG: 1:0: Unexpected 2025-09-22 11:12:02.571: watchdog pid 902555: DEBUG: new IPC connection received 2025-09-22 11:12:02.571: watchdog pid 902555: DEBUG: sending watchdog packet to socket:9, type:[7], command ID:0, data Length:34 2025-09-22 11:12:02.571: sr_check_worker pid 903049: DEBUG: quorum: 1 node_count: -1 2025-09-22 11:12:02.571: sr_check_worker pid 903049: DEBUG: pool_acquire_follow_primary_lock: lock was not held by anyone 2025-09-22 11:12:02.571: sr_check_worker pid 903049: DEBUG: pool_acquire_follow_primary_lock: succeeded in acquiring lock 2025-09-22 11:12:02.571: sr_check_worker pid 903049: DEBUG: SSL is requested but SSL support is not available 2025-09-22 11:12:02.572: sr_check_worker pid 903049: DEBUG: authenticate kind = 10 2025-09-22 11:12:02.581: sr_check_worker pid 903049: DEBUG: SCRAM authentication successful for user:rep 2025-09-22 11:12:02.581: sr_check_worker pid 903049: DEBUG: authenticate backend: key data received 2025-09-22 11:12:02.581: sr_check_worker pid 903049: DEBUG: authenticate backend: transaction state: I 2025-09-22 11:12:02.581: sr_check_worker pid 903049: DEBUG: do_query: extended:0 query:"SELECT pg_catalog.pg_is_in_recovery()" 2025-09-22 11:12:02.581: sr_check_worker pid 903049: DEBUG: verify_backend_node_status: there's no primary node 2025-09-22 11:12:02.581: sr_check_worker pid 903049: DEBUG: node status[0]: 0 2025-09-22 11:12:02.581: sr_check_worker pid 903049: DEBUG: node status[1]: 2 2025-09-22 11:12:02.581: sr_check_worker pid 903049: DEBUG: pool_release_follow_primary_lock called 2025-09-22 11:12:02.972: heart_beat_sender pid 902601: DEBUG: watchdog heartbeat: send heartbeat signal to 192.168.1.72:9694 2025-09-22 11:12:02.981: health_check1 pid 902636: DEBUG: health check: clearing alarm 2025-09-22 11:12:02.982: health_check1 pid 902636: DEBUG: SSL is requested but SSL support is not available 2025-09-22 11:12:02.983: health_check1 pid 902636: DEBUG: authenticate kind = 10 2025-09-22 11:12:02.992: health_check1 pid 902636: DEBUG: SCRAM authentication successful for user:pgpool 2025-09-22 11:12:02.992: health_check1 pid 902636: DEBUG: authenticate backend: key data received 2025-09-22 11:12:02.992: health_check1 pid 902636: DEBUG: authenticate backend: transaction state: I 2025-09-22 11:12:02.992: health_check1 pid 902636: DEBUG: health check: clearing alarm 2025-09-22 11:12:02.992: health_check1 pid 902636: DEBUG: health check: clearing alarm 2025-09-22 11:12:04.973: heart_beat_sender pid 902601: DEBUG: watchdog heartbeat: send heartbeat signal to 192.168.1.72:9694 2025-09-22 11:12:06.973: heart_beat_sender pid 902601: DEBUG: watchdog heartbeat: send heartbeat signal to 192.168.1.72:9694根据pgpool日志，排除错误，写出详细故障处理步骤
09-23
1. **SSL支持缺失**：多处出现 `SSL is requested but SSL support is not available` 2. **主节点缺失**：`verify_backend_node_status: there's no primary node` 3. **节点状态异常**：`node status[0]: 0`（DOWN...
【C#高级技术应用】：***数据保护实战演练指南
# 1. C#中的数据保护概念 数据保护在软件开发中是至关重要的，尤其是在处理敏感信息如用户凭证、个人信息以及...- **加密和解密**：通过特定算法将可读的明文数据转换为不可读的密文，以防止未授权访问。解密则是将密
mysql select_catalog_role_catalog.sql脚本介绍
weixin_39604598的博客
01-19 344
前面介绍了如何通过手工创建数据库，在创建数据库之后执行了脚本$ORACLA_HOME/rdbms/admin/catalog.sql脚本，这里着重介绍一下该脚本的作用。该脚本用户创建oracle动态性能视图，比如v$session,v$session_wait,v$transactoin等。这类性能视图主要用于监控oracle实例运行的状态，脚本文件开始时的注释已经说明其作用：Rem NAMERe...
sys通过授予select_catalog_role角色给用户，使用户有权限查询数据字典。
sustwct的专栏
12-04 5016
sys通过授予select_catalog_role角色给用户，使用户有权限查询数据字典。 引：深入解析Oracle：DBA入门、进阶与诊断案例
oracle11 分配表权限,Oracle11g权限--角色
weixin_30601893的博客
04-02 870
角色: 是具有名称的一组相关权限的组合，即将不同权限组合在一起就形成了角色。可以使用角色为用户授权，同样也可以从用户中回收角色。一个角色集合了多种权限，所以为用户授予某个角色时，相当于为用户授予多种权限。使用角色的特点和优点1> 并不是一次一个地将权限直接授予一个用户，而是先创建角色，想该角色授予一些权限，然后在将该角色授予多个用户。2> 在增加或者删除一个角色的权限时，被授予该角色的...
Oracle 体系结构（24）—— Oracle 的权限管理与角色（role）
睿思达DBA
08-29 1910
Oracle 体系结构（24）—— Oracle 的权限管理与角色（role） 角色（role）是一组权限的集合，将角色赋给一个用户，这个用户就拥有了这个角色中的所有权限。 一、系统预定义角色 预定义角色是在数据库安装后，系统自动创建的一些常用的角色。查询角色所包含的权限可以使用以下语句： SQL> select * from role_sys_privs where role='RESOURCE'; ROLE PRIVILEGE ADM ------------------
oracle设置默认角色,Oracle之管理角色
weixin_31563557的博客
04-02 605
预定义角色是oracle提供的角色,这些角色是在建立数据库,安装数据字典视图何PL/SQL包时建立的,并且每种角色都用于执行一些特定管理任务.1,CONNECT角色CONNECT角色时在建立数据库时,oracle执行脚本SQL.BSQ自动建立的角色,该角色具有应用开发人员所需的多数权限.CONNECT角色具有的所有系统权限如下:ALTER SESSION 修改会话参数设置CREATE CLUSTE...
ORACLE权限角色全集
weixin_42955647的博客
09-07 618
ORACLE权限、角色全集 角色 CONNECT 数据库连接角色，用于连接数据库，具有创建簇、数据库链接、序列、同义词、表和视图，以及修改会话的权利   DBA 数据库管理员角色，具有所有使用ADMIN选项创建的系统权限，可以将系统权限授予其他用户或角色   DELETE_CATALOG_ROLE 删除目录角色，可以删除或重建数据字典   EXECUTE_CATALOG_ROLE 执行目录角色，能够执行所有系统包   EXP_FULL_DATABASE 能够使用导出程序执行数据库的完全和增量导出   IMP
OEM连接数据库 权限不足的解决办法
weixin_33895516的博客
07-17 328
建立一个普通用户，只有connect 角色，通过oem或者远程sqlplus连接不了数据库，报权限不足 主要原因是进OEM，不只是连接，还要操作数据字典，所以我们还要给用户附上关于数据字典的权限。 grant SELECT_CATALOG_ROLE tobt32User ; grant select any dictionary to bt32User; ...
Oracle 实验十二：用户与角色管理
不服输的小乌龟
06-29 872
Oracle 实验十二：用户与角色管理
oracle创建删除用户
A_Bear_Big的博客
11-20 532
一、创建用户 语法[创建用户]： create user 用户名 identified by 口令[即密码]； 例子： create user test identified by test; 语法[更改用户]: alter user 用户名 identified by 口令[改变的口令]; 例子： alter user test identified by 123456; 二、删除用户 语法：drop user 用户名; 例子：drop user test; 若用户拥有对象，则不能直接删除，否则将返回一个
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值