当前位置: 首页 > news >正文

RU19.25 Standalone (GI和DB分开打)

参考文档:Patch 36916690 - GI Release Update 19.25.0.0.241015


2.1.1.1 OPatch Utility Information
12.2.0.1.42 or later 

2.1.1.2 Validation of Oracle Inventory
分别在GI和Oracle Home下执行

$ <ORACLE_HOME>/OPatch/opatch lsinventory -detail -oh <ORACLE_HOME>su - grid
/u01/app/19.0.0/grid/OPatch/opatch lsinventory -detail -oh /u01/app/19.0.0/gridsu - oracle
/u01/app/oracle/product/19.0.0/db_1/OPatch/opatch lsinventory -detail -oh /u01/app/oracle/product/19.0.0/db_1

2.1.1.4 Run OPatch Conflict Check

su - grid 
/u01/app/19.0.0/grid/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir /stage/36916690/36912597
/u01/app/19.0.0/grid/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir /stage/36916690/36917416
/u01/app/19.0.0/grid/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir /stage/36916690/36917397
/u01/app/19.0.0/grid/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir /stage/36916690/36940756
/u01/app/19.0.0/grid/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir /stage/36916690/36758186su - oracle 
/u01/app/oracle/product/19.0.0/db_1/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir /stage/36916690/36912597
/u01/app/oracle/product/19.0.0/db_1/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir /stage/36916690/36917416

2.1.1.5 Run OPatch System Space Check

su - grid 
cat /tmp/patch_list_gihome.txt/stage/36916690/36912597
/stage/36916690/36917416
/stage/36916690/36917397
/stage/36916690/36940756
/stage/36916690/36758186/u01/app/19.0.0/grid/OPatch/opatch prereq CheckSystemSpace -phBaseFile /tmp/patch_list_gihome.txtsu - oracle 
cat /tmp/patch_list_dbhome.txt/stage/36916690/36912597
/stage/36916690/36917416/u01/app/oracle/product/19.0.0/db_1/OPatch/opatch prereq CheckSystemSpace -phBaseFile /tmp/patch_list_dbhome.txt

2.1.4 OPatchAuto Out-of-Place Patching  

-- 一次性打GI和DB home的补丁

To patch the Grid home and all Oracle RAC database homes of the same version:
# opatchauto apply <UNZIPPED_PATCH_LOCATION>/36916690

-- 分开打GI和DB的补丁

To patch only the Grid home:
# opatchauto apply <UNZIPPED_PATCH_LOCATION>/36916690 -oh <GI_HOME>To patch one or more Oracle RAC database homes:
# opatchauto apply <UNZIPPED_PATCH_LOCATION>/36916690 -oh <oracle_home1_path>,<oracle_home2_path>su - root 
/u01/app/19.0.0/grid/OPatch/opatchauto apply /stage/36916690 -oh /u01/app/19.0.0/grid
/u01/app/oracle/product/19.0.0/db_1/OPatch/opatchauto apply /stage/36916690 -oh /u01/app/oracle/product/19.0.0/db_1

-- log

[root@asm19c 36916690]# /u01/app/19.0.0/grid/OPatch/opatchauto apply /stage/36916690 -oh /u01/app/19.0.0/gridOPatchauto session is initiated at Fri Oct 18 10:02:57 2024System initialization log file is /u01/app/19.0.0/grid/cfgtoollogs/opatchautodb/systemconfig2024-10-18_10-03-09AM.log.Session log file is /u01/app/19.0.0/grid/cfgtoollogs/opatchauto/opatchauto2024-10-18_10-03-17AM.log
The id for this session is NTZYExecuting OPatch prereq operations to verify patch applicability on home /u01/app/19.0.0/grid
Patch applicability verified successfully on home /u01/app/19.0.0/gridExecuting patch validation checks on home /u01/app/19.0.0/grid
Patch validation checks successfully completed on home /u01/app/19.0.0/gridPerforming prepatch operations on CRS - bringing down CRS service on home /u01/app/19.0.0/grid
Prepatch operation log file location: /u01/app/grid/crsdata/asm19c/crsconfig/hapatch_2024-10-18_10-13-39AM.log
CRS service brought down successfully on home /u01/app/19.0.0/gridStart applying binary patch on home /u01/app/19.0.0/grid
Binary patch applied successfully on home /u01/app/19.0.0/gridRunning rootadd_rdbms.sh on home /u01/app/19.0.0/grid
Successfully executed rootadd_rdbms.sh on home /u01/app/19.0.0/gridPerforming postpatch operations on CRS - starting CRS service on home /u01/app/19.0.0/grid
Postpatch operation log file location: /u01/app/grid/crsdata/asm19c/crsconfig/hapatch_2024-10-18_10-32-51AM.log
CRS service started successfully on home /u01/app/19.0.0/gridOPatchAuto successful.--------------------------------Summary--------------------------------Patching is completed successfully. Please find the summary as follows:Host:asm19c
SIHA Home:/u01/app/19.0.0/grid
Version:19.0.0.0.0
Summary:==Following patches were SKIPPED:Patch: /stage/36916690/36758186
Log: /u01/app/19.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2024-10-18_10-04-03AM_1.log
Reason: /stage/36916690/36758186 is not required to be applied to oracle home /u01/app/19.0.0/grid==Following patches were SUCCESSFULLY applied:Patch: /stage/36916690/36912597
Log: /u01/app/19.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2024-10-18_10-14-44AM_1.logPatch: /stage/36916690/36917397
Log: /u01/app/19.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2024-10-18_10-14-44AM_1.logPatch: /stage/36916690/36917416
Log: /u01/app/19.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2024-10-18_10-14-44AM_1.logPatch: /stage/36916690/36940756
Log: /u01/app/19.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2024-10-18_10-14-44AM_1.logOPatchauto session completed at Fri Oct 18 10:34:43 2024
Time taken to complete the session 31 minutes, 35 seconds
[root@asm19c 36916690]# 
[root@asm19c 36916690]# /u01/app/oracle/product/19.0.0/db_1/OPatch/opatchauto apply /stage/36916690 -oh /u01/app/oracle/product/19.0.0/db_1OPatchauto session is initiated at Fri Oct 18 10:38:35 2024System initialization log file is /u01/app/oracle/product/19.0.0/db_1/cfgtoollogs/opatchautodb/systemconfig2024-10-18_10-38-59AM.log.Session log file is /u01/app/oracle/product/19.0.0/db_1/cfgtoollogs/opatchauto/opatchauto2024-10-18_10-39-14AM.log
The id for this session is JWACExecuting OPatch prereq operations to verify patch applicability on home /u01/app/oracle/product/19.0.0/db_1
Patch applicability verification failed on home /u01/app/oracle/product/19.0.0/db_1Execution of [OPatchAutoBinaryAction] patch action failed, check log for more details. Failures:
Patch Target : asm19c->/u01/app/oracle/product/19.0.0/db_1 Type[sidb]
Details: [
---------------------------Patching Failed---------------------------------
Command execution failed during patching in home: /u01/app/oracle/product/19.0.0/db_1, host: asm19c.
Command failed:  /u01/app/oracle/product/19.0.0/db_1/OPatch/opatchauto  apply /stage/36916690 -oh /u01/app/oracle/product/19.0.0/db_1 -target_type oracle_database -binary -invPtrLoc /u01/app/oracle/product/19.0.0/db_1/oraInst.loc -jre /u01/app/oracle/product/19.0.0/db_1/OPatch/jre -persistresult /u01/app/oracle/product/19.0.0/db_1/opatchautocfg/db/sessioninfo/sessionresult_analyze_asm19c_sidb_2.ser -analyze -online -prepare_home
Command failure output: 
==Following patches FAILED in analysis for apply:Patch: /stage/36916690/36917416
Log: /u01/app/oracle/product/19.0.0/db_1/cfgtoollogs/opatchauto/core/opatch/opatch2024-10-18_10-40-00AM_1.log
Reason: Failed during Analysis: CheckSystemSpace Failed, [ Prerequisite Status: FAILED, Prerequisite output: 
The details are:
Required amount of space(9413.939MB) is not available.]Patch: /stage/36916690/36912597
Log: /u01/app/oracle/product/19.0.0/db_1/cfgtoollogs/opatchauto/core/opatch/opatch2024-10-18_10-40-00AM_1.log
Reason: Failed during Analysis: CheckSystemSpace Failed, [ Prerequisite Status: FAILED, Prerequisite output: 
The details are:
Required amount of space(9413.939MB) is not available.] After fixing the cause of failure start a new opatchauto session
]
OPATCHAUTO-68061: The orchestration engine failed.
OPATCHAUTO-68061: The orchestration engine failed with return code 1
OPATCHAUTO-68061: Check the log for more details.
OPatchAuto failed.OPatchauto session completed at Fri Oct 18 10:51:56 2024
Time taken to complete the session 12 minutes, 59 secondsopatchauto failed with error code 42
[root@asm19c 36916690]# 

-- 修复空间问题后,resume 

[root@asm19c 36916690]# /u01/app/oracle/product/19.0.0/db_1/OPatch/opatchauto resume
Session log file is /u01/app/oracle/product/19.0.0/db_1/cfgtoollogs/opatchauto/opatchauto2024-10-18_11-24-07AM.log
Resuming existing session with id JWACExecuting OPatch prereq operations to verify patch applicability on home /u01/app/oracle/product/19.0.0/db_1
Patch applicability verified successfully on home /u01/app/oracle/product/19.0.0/db_1Executing patch validation checks on home /u01/app/oracle/product/19.0.0/db_1
Patch validation checks successfully completed on home /u01/app/oracle/product/19.0.0/db_1Verifying SQL patch applicability on home /u01/app/oracle/product/19.0.0/db_1
SQL patch applicability verified successfully on home /u01/app/oracle/product/19.0.0/db_1Preparing to bring down database service on home /u01/app/oracle/product/19.0.0/db_1
Successfully prepared home /u01/app/oracle/product/19.0.0/db_1 to bring down database serviceBringing down database service on home /u01/app/oracle/product/19.0.0/db_1
Following database has been stopped and will be restarted later during the session: test
Database service successfully brought down on home /u01/app/oracle/product/19.0.0/db_1Start applying binary patch on home /u01/app/oracle/product/19.0.0/db_1
Binary patch applied successfully on home /u01/app/oracle/product/19.0.0/db_1Running rootadd_rdbms.sh on home /u01/app/oracle/product/19.0.0/db_1
Successfully executed rootadd_rdbms.sh on home /u01/app/oracle/product/19.0.0/db_1Starting database service on home /u01/app/oracle/product/19.0.0/db_1
Database service successfully started on home /u01/app/oracle/product/19.0.0/db_1Preparing home /u01/app/oracle/product/19.0.0/db_1 after database service restarted
No step execution required.........Trying to apply SQL patch on home /u01/app/oracle/product/19.0.0/db_1
SQL patch applied successfully on home /u01/app/oracle/product/19.0.0/db_1OPatchAuto successful.--------------------------------Summary--------------------------------Patching is completed successfully. Please find the summary as follows:Host:asm19c
SIDB Home:/u01/app/oracle/product/19.0.0/db_1
Version:19.0.0.0.0
Summary:==Following patches were SKIPPED:Patch: /stage/36916690/36917397
Reason: This patch is not applicable to this specified target type - "oracle_database"Patch: /stage/36916690/36758186
Reason: This patch is not applicable to this specified target type - "oracle_database"Patch: /stage/36916690/36940756
Reason: This patch is not applicable to this specified target type - "oracle_database"==Following patches were SUCCESSFULLY applied:Patch: /stage/36916690/36912597
Log: /u01/app/oracle/product/19.0.0/db_1/cfgtoollogs/opatchauto/core/opatch/opatch2024-10-18_11-39-15AM_1.logPatch: /stage/36916690/36917416
Log: /u01/app/oracle/product/19.0.0/db_1/cfgtoollogs/opatchauto/core/opatch/opatch2024-10-18_11-39-15AM_1.logOPatchauto session completed at Fri Oct 18 12:05:50 2024
Time taken to complete the session 41 minutes, 46 seconds
[root@asm19c 36916690]# 

-- 验证

[grid@asm19c ~]$ cd $ORACLE_HOME/OPatch 
[grid@asm19c OPatch]$ ./opatch lspatches
36940756;TOMCAT RELEASE UPDATE 19.0.0.0.0 (36940756)
36917416;OCW RELEASE UPDATE 19.25.0.0.0 (36917416)
36917397;ACFS RELEASE UPDATE 19.25.0.0.0 (36917397)
36912597;Database Release Update : 19.25.0.0.241015 (36912597)
36758186;DBWLM RELEASE UPDATE 19.0.0.0.0 (36758186)OPatch succeeded.
[grid@asm19c OPatch]$ 
[oracle@asm19c OPatch]$ ./opatch lspatches
36917416;OCW RELEASE UPDATE 19.25.0.0.0 (36917416)
36912597;Database Release Update : 19.25.0.0.241015 (36912597)OPatch succeeded.
[oracle@asm19c OPatch]$ 
SQL> set linesize 200
SQL> col action for a14
SQL> col status for a20
SQL> col description for a70
SQL> select action,status,description from dba_registry_sqlpatch;ACTION         STATUS               DESCRIPTION
-------------- -------------------- ----------------------------------------------------------------------
APPLY          SUCCESS              Database Release Update : 19.3.0.0.190416 (29517242)
APPLY          SUCCESS              Database Release Update : 19.7.0.0.200414 (30869156)
APPLY          SUCCESS              Database Release Update : 19.12.0.0.210720 (32904851)
APPLY          SUCCESS              Database Release Update : 19.24.0.0.240716 (36582781)
APPLY          SUCCESS              Database Release Update : 19.25.0.0.241015 (36912597)SQL> 

END

相关文章:

RU19.25 Standalone (GI和DB分开打)

参考文档&#xff1a;Patch 36916690 - GI Release Update 19.25.0.0.241015 2.1.1.1 OPatch Utility Information 12.2.0.1.42 or later 2.1.1.2 Validation of Oracle Inventory 分别在GI和Oracle Home下执行 $ <ORACLE_HOME>/OPatch/opatch lsinventory -detail -o…...

探索 Jupyter 核心:nbformat 库的神秘力量

文章目录 探索 Jupyter 核心&#xff1a;nbformat 库的神秘力量1. 背景介绍&#xff1a;为何选择 nbformat&#xff1f;2. nbformat 是什么&#xff1f;3. 如何安装 nbformat&#xff1f;4. 简单的库函数使用方法4.1 读取 Notebook 文件4.2 修改 Notebook 中的单元格4.3 添加 M…...

python+大数据+基于spark的短视频推荐系统【内含源码+文档+部署教程】

博主介绍&#xff1a;✌全网粉丝10W,前互联网大厂软件研发、集结硕博英豪成立工作室。专注于计算机相关专业毕业设计项目实战6年之久&#xff0c;选择我们就是选择放心、选择安心毕业✌ &#x1f345;由于篇幅限制&#xff0c;想要获取完整文章或者源码&#xff0c;或者代做&am…...

Elasticsearch字段数据类型

1. 前言 ES文档的每个字段都至少有一个数据类型&#xff0c;此类型决定了字段值如何被存储以及检索。例如&#xff0c;字符串类型可以定义为text或者keyword&#xff0c;前者用于全文检索&#xff0c;会经过分词后索引&#xff1b;后者用于精准匹配&#xff0c;值会保持原样被…...

简述RESTFul风格的API接口

目录 传统的风格API REST风格 谓词规范 URL命令规范 避免多级URL 幂等 CURD的接口设计 REST响应 响应成功返回的状态码 重定向 错误代码 客户端 服务器 RESTful的返回格式 返回格式 从上一篇文章我们已经初步知道了怎么在VS中创建一个webapi项目。这篇文章来探讨一…...

探索光耦:光耦——不间断电源(UPS)系统中的安全高效卫士

在现代社会&#xff0c;不间断电源&#xff08;UPS&#xff09;系统已成为保障关键设备和数据安全的关键设施&#xff0c;广泛应用于企业数据中心、家庭电子设备等场景。UPS能在电力中断或波动时提供稳定电力&#xff0c;确保设备持续运行。而在这套系统中&#xff0c;光耦&…...

at命令和cron命令

第一章 例行性工作 1、单一执行的例行性工作 单一执行的例行性工作&#xff1a;仅处理执行一次就结束了 . 1.1 at命令的工作过程 /etc/at.allow&#xff1a;里面的用户是可以使用at命令的 --- 但实际上这个allow文件不存在&#xff0c;所以指全部的人都可以使用该命令&#…...

搜维尔科技:使用Manus Primel Xsens数据手套直接在Xsens及其插件中捕获手指数据

使用Manus Primel Xsens数据手套直接在Xsens及其插件中捕获手指数据 搜维尔科技&#xff1a;使用Manus Primel Xsens数据手套直接在Xsens及其插件中捕获手指数据...

Avalonia UI获取Popup显示位置,可解决异常显示其他应用程序的左上角

1.通过 PlacementTarget 获取位置 如果 Popup 是相对于某个控件&#xff08;PlacementTarget&#xff09;显示的&#xff0c;你也可以获取该控件的位置&#xff0c;然后计算 Popup 的相对位置。 // 假设 popup 是你的 Popup&#xff0c;target 是你的目标控件&#xff08;Pla…...

新版Win32高级编程教程-学习笔记01:应用程序分类

互联网行业 算法研发工程师 目录 新版Win32高级编程教程-学习笔记01&#xff1a;应用程序分类 控制台程序 强烈注意 窗口程序 启动项 程序入口函数 库程序 静态库 动态库程序 几种应用程序的区别 控制台程序 本身没有窗口&#xff0c;其中的doc窗口&#xff0c;是管…...

无需编程知识 如何用自适应建站系统创建专业网站 带完整的安装代码包以及搭建部署教程

系统概述 自适应建站系统是一款功能强大、易于使用的建站工具。它采用了先进的技术和设计理念&#xff0c;旨在为用户提供一个简单、高效的建站平台。该系统支持多种语言和多种设备&#xff0c;能够自动适应不同屏幕尺寸和分辨率&#xff0c;确保网站在各种终端上都能呈现出最…...

萤石云服务支持云端视频AI自动剪辑生成

萤石视频云存储及媒体处理服务是围绕IoT设备云端存储场景下的音视频采集、媒体管理、视频剪辑和分发能力的一站式、专业云服务&#xff0c;并可面向广大开发者提供复杂设备存储场景下的完整技术方案。目前该服务新增了视频剪辑功能&#xff0c;支持将视频片段在云端进行裁剪并拼…...

Flink移除器Evictor

前言 在 Flink 窗口计算模型中&#xff0c;数据被 WindowAssigner 划分到对应的窗口后&#xff0c;再经过触发器 Trigger 判断窗口是否要 fire 计算&#xff0c;如果窗口要计算&#xff0c;会把数据丢给移除器 Evictor&#xff0c;Evictor 可以先移除部分元素再交给 ProcessFu…...

R语言实现多元线性回归高杠杠点,离群点分析

14a set.seed(1) x1 = runif(100) x2 = 0.5 * x1 + rnorm(100)/...

overfrp内网穿透:使用域名将内网http/https服务暴露到公网

项目地址&#xff1a;https://github.com/sometiny/overfrp 使用overfrp部署穿透服务器&#xff0c;绑定域名后&#xff0c;可使用域名访问内网的http/https服务。 用例中穿透服务器和内网机器之间的访问全链路加密&#xff0c;具有ssh2相当的安全级别。&#xff01;&#xf…...

springboot034在线商城系统设计与开发-代码(论文+源码)_kaic

毕 业 设 计&#xff08;论 文&#xff09; 题目&#xff1a;ONLY在线商城系统设计与实现 摘 要 现代经济快节奏发展以及不断完善升级的信息化技术&#xff0c;让传统数据信息的管理升级为软件存储&#xff0c;归纳&#xff0c;集中处理数据信息的管理方式。本ONLY在线商城系统…...

什么是第三范式(3NF)?为什么要遵守第三范式?

第三范式&#xff08;Third Normal Form, 3NF&#xff09;是数据库设计中的一个重要概念&#xff0c;它是对关系型数据库规范化的一种标准。 在数据库设计中&#xff0c;通过将数据表按照一定的规则进行分解&#xff0c;可以减少数据冗余和提高数据的一致性。 3NF 是建立在第…...

大数据比对,shell脚本与hive技术结合

需求描述 从主机中获取加密数据内容&#xff0c;解密数据内容&#xff08;可能会存在json解析&#xff09;插入到另一个库中&#xff0c;比对原始库和新库的相同表数据的数据一致性内容。 数据一致性比对实现 上亿条数据&#xff0c;如何比对并发现两个表数据差异 相关流程…...

【Linux安全基线】- CentOS 7/8安全配置指南

在企业业务的生产环境中&#xff0c;Linux服务器的安全性至关重要&#xff0c;尤其是对于具有超级用户权限的root账号。滥用或被入侵后&#xff0c;可能会造成数据泄露、系统损坏等严重安全问题。为了减少这种风险&#xff0c;本文将详细介绍如何通过一系列安全措施来增强CentO…...

PDF.js的使用及其跨域问题解决

目录 一、PDF.js 简介 二、使用配置和步骤 1.引入PDF.js 2.加载PDF文件 3.渲染PDF页面 三、在Vue中使用PDF.js示例 1.安装PDF.js 2.在Vue组件中使用 四、在原生js中使用PDF.js示例 1.加载PDF文件并渲染页面 五、解决跨域问题 1.服务器配置 2.使用代理服务器 下面介…...

Linux应用开发之网络套接字编程(实例篇)

服务端与客户端单连接 服务端代码 #include <sys/socket.h> #include <sys/types.h> #include <netinet/in.h> #include <stdio.h> #include <stdlib.h> #include <string.h> #include <arpa/inet.h> #include <pthread.h> …...

反向工程与模型迁移:打造未来商品详情API的可持续创新体系

在电商行业蓬勃发展的当下&#xff0c;商品详情API作为连接电商平台与开发者、商家及用户的关键纽带&#xff0c;其重要性日益凸显。传统商品详情API主要聚焦于商品基本信息&#xff08;如名称、价格、库存等&#xff09;的获取与展示&#xff0c;已难以满足市场对个性化、智能…...

3-11单元格区域边界定位(End属性)学习笔记

返回一个Range 对象&#xff0c;只读。该对象代表包含源区域的区域上端下端左端右端的最后一个单元格。等同于按键 End 向上键(End(xlUp))、End向下键(End(xlDown))、End向左键(End(xlToLeft)End向右键(End(xlToRight)) 注意&#xff1a;它移动的位置必须是相连的有内容的单元格…...

初探Service服务发现机制

1.Service简介 Service是将运行在一组Pod上的应用程序发布为网络服务的抽象方法。 主要功能&#xff1a;服务发现和负载均衡。 Service类型的包括ClusterIP类型、NodePort类型、LoadBalancer类型、ExternalName类型 2.Endpoints简介 Endpoints是一种Kubernetes资源&#xf…...

嵌入式学习笔记DAY33(网络编程——TCP)

一、网络架构 C/S &#xff08;client/server 客户端/服务器&#xff09;&#xff1a;由客户端和服务器端两个部分组成。客户端通常是用户使用的应用程序&#xff0c;负责提供用户界面和交互逻辑 &#xff0c;接收用户输入&#xff0c;向服务器发送请求&#xff0c;并展示服务…...

【Go语言基础【12】】指针:声明、取地址、解引用

文章目录 零、概述&#xff1a;指针 vs. 引用&#xff08;类比其他语言&#xff09;一、指针基础概念二、指针声明与初始化三、指针操作符1. &&#xff1a;取地址&#xff08;拿到内存地址&#xff09;2. *&#xff1a;解引用&#xff08;拿到值&#xff09; 四、空指针&am…...

排序算法总结(C++)

目录 一、稳定性二、排序算法选择、冒泡、插入排序归并排序随机快速排序堆排序基数排序计数排序 三、总结 一、稳定性 排序算法的稳定性是指&#xff1a;同样大小的样本 **&#xff08;同样大小的数据&#xff09;**在排序之后不会改变原始的相对次序。 稳定性对基础类型对象…...

Golang——7、包与接口详解

包与接口详解 1、Golang包详解1.1、Golang中包的定义和介绍1.2、Golang包管理工具go mod1.3、Golang中自定义包1.4、Golang中使用第三包1.5、init函数 2、接口详解2.1、接口的定义2.2、空接口2.3、类型断言2.4、结构体值接收者和指针接收者实现接口的区别2.5、一个结构体实现多…...

FFmpeg avformat_open_input函数分析

函数内部的总体流程如下&#xff1a; avformat_open_input 精简后的代码如下&#xff1a; int avformat_open_input(AVFormatContext **ps, const char *filename,ff_const59 AVInputFormat *fmt, AVDictionary **options) {AVFormatContext *s *ps;int i, ret 0;AVDictio…...

Kubernetes 节点自动伸缩(Cluster Autoscaler)原理与实践

在 Kubernetes 集群中&#xff0c;如何在保障应用高可用的同时有效地管理资源&#xff0c;一直是运维人员和开发者关注的重点。随着微服务架构的普及&#xff0c;集群内各个服务的负载波动日趋明显&#xff0c;传统的手动扩缩容方式已无法满足实时性和弹性需求。 Cluster Auto…...