greenplum数据库集群异常FATAL","XX000","Number of freeTIDs 788079, do not match maximum free order numbe

最新推荐文章于 2022-08-06 17:19:39 发布
最新推荐文章于 2022-08-06 17:19:39 发布
阅读量3.9k 收藏
点赞数
分类专栏： 数据库 greenplum 文章标签： greenplum
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/Jun_ming/article/details/103214438
版权

    背景描述：greenplum生产集群晚上运行任务负载过高导致实例异常，集群资源繁忙无法正常登陆数据库无法进行恢复，清理部分任务进程后停库进行重启失败，64个实例29个失败。

    现象：重启异常：[ERROR]:-gpstart error: Do not have enough valid segments to start the array.

启动过程如下：

23:13:31:19:012428 gpstart:mas:gpadmin-[INFO]:-Starting gpstart with args: -a
23:13:31:19:012428 gpstart:mas:gpadmin-[INFO]:-Gathering information and validating the environment...
23:13:31:19:012428 gpstart:mas:gpadmin-[INFO]:-Greenplum Binary Version: 'postgres (Greenplum Database) 4.3.8.0 build 1'
23:13:31:19:012428 gpstart:mas:gpadmin-[INFO]:-Greenplum Catalog Version: '201310150'
23:13:31:19:012428 gpstart:mas:gpadmin-[INFO]:-Starting Master instance in admin mode
23:13:31:20:012428 gpstart:mas:gpadmin-[INFO]:-Obtaining Greenplum Master catalog information
23:13:31:20:012428 gpstart:mas:gpadmin-[INFO]:-Obtaining Segment details from master...
23:13:31:21:012428 gpstart:mas:gpadmin-[INFO]:-Setting new master era
23:13:31:21:012428 gpstart:mas:gpadmin-[INFO]:-Master Started...
23:13:31:21:012428 gpstart:mas:gpadmin-[INFO]:-Shutting down master
23:13:31:24:012428 gpstart:mas:gpadmin-[WARNING]:-Skipping startup of segment marked down in configuration: on seg02 directory /data1/pg_system/primary/gpseg4 <<<<<
23:13:31:24:012428 gpstart:mas:gpadmin-[WARNING]:-Skipping startup of segment marked down in configuration: on seg02 directory /data1/pg_system/primary/gpseg5 <<<<<
23:13:31:24:012428 gpstart:mas:gpadmin-[WARNING]:-Skipping startup of segment marked down in configuration: on seg02 directory /data2/pg_system/primary/gpseg6 <<<<<
23:13:31:24:012428 gpstart:mas:gpadmin-[WARNING]:-Skipping startup of segment marked down in configuration: on seg02 directory /data2/pg_system/primary/gpseg7 <<<<<
23:13:31:24:012428 gpstart:mas:gpadmin-[WARNING]:-Skipping startup of segment marked down in configuration: on seg03 directory /data1/pg_system/primary/gpseg8 <<<<<
23:13:31:24:012428 gpstart:mas:gpadmin-[WARNING]:-Skipping startup of segment marked down in configuration: on seg03 directory /data1/pg_system/primary/gpseg9 <<<<<
23:13:31:24:012428 gpstart:mas:gpadmin-[WARNING]:-Skipping startup of segment marked down in configuration: on seg03 directory /data2/pg_system/primary/gpseg10 <<<<<
23:13:31:24:012428 gpstart:mas:gpadmin-[WARNING]:-Skipping startup of segment marked down in configuration: on seg03 directory /data2/pg_system/primary/gpseg11 <<<<<
23:13:31:24:012428 gpstart:mas:gpadmin-[WARNING]:-Skipping startup of segment marked down in configuration: on seg04 directory /data1/pg_system/primary/gpseg12 <<<<<
23:13:31:24:012428 gpstart:mas:gpadmin-[WARNING]:-Skipping startup of segment marked down in configuration: on seg04 directory /data1/pg_system/primary/gpseg13 <<<<<
23:13:31:24:012428 gpstart:mas:gpadmin-[WARNING]:-Skipping startup of segment marked down in configuration: on seg04 directory /data2/pg_system/primary/gpseg14 <<<<<
23:13:31:24:012428 gpstart:mas:gpadmin-[WARNING]:-Skipping startup of segment marked down in configuration: on seg04 directory /data2/pg_system/primary/gpseg15 <<<<<
23:13:31:24:012428 gpstart:mas:gpadmin-[WARNING]:-Skipping startup of segment marked down in configuration: on seg05 directory /data1/pg_system/primary/gpseg16 <<<<<
23:13:31:24:012428 gpstart:mas:gpadmin-[WARNING]:-Skipping startup of segment marked down in configuration: on seg05 directory /data1/pg_system/primary/gpseg17 <<<<<
23:13:31:24:012428 gpstart:mas:gpadmin-[WARNING]:-Skipping startup of segment marked down in configuration: on seg05 directory /data2/pg_system/primary/gpseg18 <<<<<
23:13:31:24:012428 gpstart:mas:gpadmin-[WARNING]:-Skipping startup of segment marked down in configuration: on seg05 directory /data2/pg_system/primary/gpseg19 <<<<<
23:13:31:24:012428 gpstart:mas:gpadmin-[WARNING]:-Skipping startup of segment marked down in configuration: on seg06 directory /data1/pg_system/primary/gpseg20 <<<<<
23:13:31:24:012428 gpstart:mas:gpadmin-[WARNING]:-Skipping startup of segment marked down in configuration: on seg06 directory /data1/pg_system/primary/gpseg21 <<<<<
23:13:31:24:012428 gpstart:mas:gpadmin-[WARNING]:-Skipping startup of segment marked down in configuration: on seg06 directory /data2/pg_system/primary/gpseg22 <<<<<
23:13:31:24:012428 gpstart:mas:gpadmin-[WARNING]:-Skipping startup of segment marked down in configuration: on seg06 directory /data2/pg_system/primary/gpseg23 <<<<<
23:13:31:24:012428 gpstart:mas:gpadmin-[WARNING]:-Skipping startup of segment marked down in configuration: on seg07 directory /data1/pg_system/primary/gpseg24 <<<<<
23:13:31:24:012428 gpstart:mas:gpadmin-[WARNING]:-Skipping startup of segment marked down in configuration: on seg07 directory /data1/pg_system/primary/gpseg25 <<<<<
23:13:31:24:012428 gpstart:mas:gpadmin-[WARNING]:-Skipping startup of segment marked down in configuration: on seg07 directory /data2/pg_system/primary/gpseg26 <<<<<
23:13:31:24:012428 gpstart:mas:gpadmin-[WARNING]:-Skipping startup of segment marked down in configuration: on seg07 directory /data2/pg_system/primary/gpseg27 <<<<<
23:13:31:24:012428 gpstart:mas:gpadmin-[WARNING]:-Skipping startup of segment marked down in configuration: on seg01 directory /data1/pg_system/mirror/gpseg28 <<<<<
23:13:31:24:012428 gpstart:mas:gpadmin-[WARNING]:-Skipping startup of segment marked down in configuration: on seg01 directory /data1/pg_system/mirror/gpseg29 <<<<<
23:13:31:24:012428 gpstart:mas:gpadmin-[WARNING]:-Skipping startup of segment marked down in configuration: on seg01 directory /data2/pg_system/mirror/gpseg30 <<<<<
23:13:31:24:012428 gpstart:mas:gpadmin-[WARNING]:-Skipping startup of segment marked down in configuration: on seg01 directory /data2/pg_system/mirror/gpseg31 <<<<<
23:13:31:24:012428 gpstart:mas:gpadmin-[INFO]:-Commencing parallel primary and mirror segment instance startup, please wait...
................................................................................................................................................................................. 
23:13:34:21:012428 gpstart:mas:gpadmin-[INFO]:-Process results...
23:13:34:21:012428 gpstart:mas:gpadmin-[ERROR]:-No segment started for content: 8.
23:13:34:21:012428 gpstart:mas:gpadmin-[INFO]:-dumping success segments: ['seg02:/data2/pg_system/mirror/gpseg3:content=3:dbid=37:mode=s:status=u', 'seg02:/data2/pg_system/mirror/gpseg2:content=2:dbid=36:mode=s:status=u', 'seg02:/data1/pg_system/mirror/gpseg1:content=1:dbid=35:mode=s:status=u', 'seg02:/data1/pg_system/mirror/gpseg0:content=0:dbid=34:mode=s:status=u', 'seg06:/data1/pg_system/mirror/gpseg17:content=17:dbid=51:mode=c:status=u', 'seg06:/data1/pg_system/mirror/gpseg16:content=16:dbid=50:mode=c:status=u', 'seg06:/data2/pg_system/mirror/gpseg18:content=18:dbid=52:mode=c:status=u', 'seg06:/data2/pg_system/mirror/gpseg19:content=19:dbid=53:mode=c:status=u', 'seg03:/data1/pg_system/mirror/gpseg5:content=5:dbid=39:mode=c:status=u', 'seg03:/data1/pg_system/mirror/gpseg4:content=4:dbid=38:mode=c:status=u', 'seg03:/data2/pg_system/mirror/gpseg7:content=7:dbid=41:mode=c:status=u', 'seg03:/data2/pg_system/mirror/gpseg6:content=6:dbid=40:mode=c:status=u', 'seg07:/data2/pg_system/mirror/gpseg23:content=23:dbid=57:mode=c:status=u', 'seg07:/data2/pg_system/mirror/gpseg22:content=22:dbid=56:mode=c:status=u', 'seg07:/data1/pg_system/mirror/gpseg20:content=20:dbid=54:mode=c:status=u', 'seg07:/data1/pg_system/mirror/gpseg21:content=21:dbid=55:mode=c:status=u', 'seg05:/data2/pg_system/mirror/gpseg14:content=14:dbid=48:mode=c:status=u', 'seg05:/data2/pg_system/mirror/gpseg15:content=15:dbid=49:mode=c:status=u', 'seg05:/data1/pg_system/mirror/gpseg13:content=13:dbid=47:mode=c:status=u', 'seg05:/data1/pg_system/mirror/gpseg12:content=12:dbid=46:mode=c:status=u', 'seg04:/data2/pg_system/mirror/gpseg11:content=11:dbid=45:mode=c:status=u', 'seg04:/data2/pg_system/mirror/gpseg10:content=10:dbid=44:mode=c:status=u', 'seg04:/data1/pg_system/mirror/gpseg9:content=9:dbid=43:mode=c:status=u', 'seg08:/data2/pg_system/mirror/gpseg27:content=27:dbid=61:mode=c:status=u', 'seg08:/data2/pg_system/mirror/gpseg26:content=26:dbid=60:mode=c:status=u', 'seg08:/data1/pg_system/mirror/gpseg24:content=24:dbid=58:mode=c:status=u', 'seg08:/data1/pg_system/mirror/gpseg25:content=25:dbid=59:mode=c:status=u', 'seg08:/data2/pg_system/primary/gpseg30:content=30:dbid=32:mode=c:status=u', 'seg08:/data2/pg_system/primary/gpseg31:content=31:dbid=33:mode=c:status=u', 'seg08:/data1/pg_system/primary/gpseg28:content=28:dbid=30:mode=c:status=u', 'seg08:/data1/pg_system/primary/gpseg29:content=29:dbid=31:mode=c:status=u', 'seg01:/data1/pg_system/primary/gpseg1:content=1:dbid=3:mode=s:status=u', 'seg01:/data1/pg_system/primary/gpseg0:content=0:dbid=2:mode=s:status=u', 'seg01:/data2/pg_system/primary/gpseg2:content=2:dbid=4:mode=s:status=u', 'seg01:/data2/pg_system/primary/gpseg3:content=3:dbid=5:mode=s:status=u']
23:13:34:21:012428 gpstart:mas:gpadmin-[INFO]:-----------------------------------------------------
23:13:34:21:012428 gpstart:mas:gpadmin-[INFO]:-DBID:42  FAILED  host:'seg04' datadir:'/data1/pg_system/mirror/gpseg8' with reason:'Segment postmaster has exited; check segment logfile'
23:13:34:21:012428 gpstart:mas:gpadmin-[INFO]:-----------------------------------------------------
23:13:34:21:012428 gpstart:mas:gpadmin-[INFO]:-----------------------------------------------------
23:13:34:21:012428 gpstart:mas:gpadmin-[INFO]:-   Successful segment starts                                            = 35
23:13:34:21:012428 gpstart:mas:gpadmin-[WARNING]:-Failed segment starts                                                = 1    <<<<<<<<
23:13:34:21:012428 gpstart:mas:gpadmin-[WARNING]:-Skipped segment starts (segments are marked down in configuration)   = 28   <<<<<<<<
23:13:34:21:012428 gpstart:mas:gpadmin-[INFO]:-----------------------------------------------------
23:13:34:21:012428 gpstart:mas:gpadmin-[INFO]:-
23:13:34:21:012428 gpstart:mas:gpadmin-[INFO]:-Successfully started 35 of 36 segment instances, skipped 28 other segments <<<<<<<<
23:13:34:21:012428 gpstart:mas:gpadmin-[INFO]:-----------------------------------------------------
23:13:34:21:012428 gpstart:mas:gpadmin-[WARNING]:-Segment instance startup failures reported
23:13:34:21:012428 gpstart:mas:gpadmin-[WARNING]:-Failed start 1 of 36 segment instances <<<<<<<<
23:13:34:21:012428 gpstart:mas:gpadmin-[WARNING]:-Review /home/gpadmin/gpAdminLogs/gpstart_23.log
23:13:34:21:012428 gpstart:mas:gpadmin-[INFO]:-----------------------------------------------------
23:13:34:21:012428 gpstart:mas:gpadmin-[WARNING]:-****************************************************************************
23:13:34:21:012428 gpstart:mas:gpadmin-[WARNING]:-There are 28 segment(s) marked down in the database
23:13:34:21:012428 gpstart:mas:gpadmin-[WARNING]:-To recover from this current state, review usage of the gprecoverseg
23:13:34:21:012428 gpstart:mas:gpadmin-[WARNING]:-management utility which will recover failed segment instance databases.
23:13:34:21:012428 gpstart:mas:gpadmin-[WARNING]:-****************************************************************************
23:13:34:21:012428 gpstart:mas:gpadmin-[INFO]:-Commencing parallel segment instance shutdown, please wait...
23:13:34:25:012428 gpstart:mas:gpadmin-[ERROR]:-gpstart error: Do not have enough valid segments to start the array.
[gpadmin@mas ~]$ 

登陆节点seg04查看日志：

cd /data1/pg_system/mirror/gpseg8

日志记录关键报错信息如下：

 13:31:26.124568 CST,,,p32570,th497243936,,,,0,,,seg-1,,,,,"LOG","00000","end of transaction log location is 19D2/CF69C378",,,,,,,0,,"xlog.c",6988,
 13:31:26.776825 CST,,,p32570,th497243936,,,,0,,,seg-1,,,,,"FATAL","XX000","Number of freeTIDs 788079, do not match maximum free order number 78819
7, for 'gp_persistent_relation_node' (cdbpersistentstore.c:626)",,,,,,,0,,"cdbpersistentstore.c",626,"Stack trace:
1    0xb03bda postgres <symbol not found> (elog.c:502)
2    0xb05be8 postgres elog_finish (elog.c:1446)
3    0xcb2e14 postgres <symbol not found> (cdbpersistentstore.c:626)
4    0xcb3e17 postgres PersistentStore_InitScanUnderLock (cdbpersistentstore.c:659)
5    0xc9a19c postgres PersistentFileSysObj_StartupInitScan (cdbpersistentfilesysobj.c:673)
6    0x5643f5 postgres StartupXLOG (xlog.c:7171)
7    0x566616 postgres StartupProcessMain (xlog.c:10970)
8    0x5f6715 postgres AuxiliaryProcessMain (bootstrap.c:463)
9    0x8ede24 postgres <symbol not found> (postmaster.c:7589)
10   0x8ee04d postgres StartMasterOrPrimaryPostmasterProcesses (postmaster.c:1576)
11   0x90079f postgres doRequestedPrimaryMirrorModeTransitions (primary_mirror_mode.c:2087)
12   0x8f8ea2 postgres <symbol not found> (postmaster.c:2485)
13   0x8fa840 postgres PostmasterMain (postmaster.c:7589)
14   0x7fc8bf postgres main (main.c:206)
15   0x3e68e1ecdd libc.so.6 __libc_start_main (??:0)
16   0x4c4869 postgres <symbol not found> (??:0)
"
 13:31:26.789524 CST,,,p32539,th497243936,,,,0,,,seg-1,,,,,"LOG","00000","startup process (PID 32570) exited with exit code 1",,,,,,,0,,"postmaster
.c",5854,
 13:31:26.789566 CST,,,p32539,th497243936,,,,0,,,seg-1,,,,,"LOG","00000","aborting startup due to startup process failure",,,,,,,0,,"postmaster.c",
4706,
 13:31:26.983173 CST,,,p32562,th497243936,"127.0.0.1","56915", 13:31:25 CST,0,,,seg-1,,,,,"WARNING","01000","PrimaryMirrorTransitionReque
st (2) Result: Transition to primary/mirror mode PrimarySegment, data state InChangeTracking resulted in Error",,,,,,,0,,"primary_mirror_mode.c",1319,
[gpadmin@seg04 pg_log]$ 
[gpadmin@seg04 pg_log]$ 

解决措施：

在该节点（seg04）实例下修改参数文件postgresql.conf，在文件中添加参数：gp_persistent_skip_free_list=true，然后在进行启动数据库集群，集群启动成功，执行命令gprecoverseg进行恢复失败的实例。

greenplum数据库异常可参考资料较少，望对读者有所帮助！

 

白家二公子
关注
专栏目录
全志平台N3模块调试（3）视频图像异常调试
jzwjzw19900922的博客
08-17 3444
1. 概述 上篇已完成视频驱动通路的配置问题； 这里主要是解决图像异常问题 2. 查看控制器寄存器 问题： 按照上面改完之后不报任何错误，发现并没有产生任何CSI中断; 这样就可以看看控制器的寄存器是否有接收到数据 解决办法： 根据SDK中提供的SOC说明文档，可以查看一部分的寄存器状态 查询方法【寄存器地址查看文档】： echo 0x06601000，0x06601200 > /sys/class/sunxi_dump/dump cat /sys/class/sunxi_
greenplum的操作异常收集
jsjw18的专栏
09-09 4749
ERROR: could not write 3124 bytes to temporary file: No space left on device (buffile.c:405)
xx-Pixiv Spider
MoltenDivineCore的博客
04-19 2万+
import requests from lxml import etree import json import os # 缺陷 1：下载的是图片合集，会下载其他角色的图片 # 缺陷 2：不能存 gif，因为P站的 gif 图片用的是我还不懂的方式 #================================================ #设置一个 Session 保持会话 se = requests.session() # E:\\0-Picture\\3-明日方舟\\鞭刃\\ # E.
Building a 3D Game in XNA From Scratch - Free Video Tutorial Series Now Available!
0.5 Degree
02-07 23万+
 After far too many hours of learning, teaching, recording, testing, video editing, and other glorious activities, I am ready to make available my massive collection of video tutorials for creatin
SDI科普--- SD-SDI/HD-SDI/3G-SDI/12G-SDI
jzwjzw19900922的博客
11-24 2万+
SDI: 数字分量串行接口 HD-SDI：高清数字分量串行接口 1. SDI接口分类 SD-SDI(270Mbp，SMPTE259M) HD-SDI(1.485Gbps,SMPTE292M) 3G-SDI(2.97Gbps,SMPTE424M) 2. SDI各类标准数据 3. 概述 （1）SD-SDI SD-SDI(270Mbp，SMPTE259M) （2）HD-SDI 高清数字分量串行接口 HD-SDI是实时...
GreenPlum 数据库集群安装说明及使用手册v1.0.docx
06-07
### GreenPlum 数据库集群安装说明及使用手册关键知识点 #### 一、GreenPlum数据库简介 - **GreenPlum数据库概述**：GreenPlum是一款高性能的企业级数据仓库解决方案，由GreenPlum公司开发，专注于提供高效的大数据...
Greenplum 集群数据库部署
06-09
RHEL6.5 平台 Greenplum 4.3 集群数据库部署
Greenplum不同集群之间同步数据方法及性能1
08-04
在Greenplum数据库环境中，数据同步是常见的需求，尤其在多个集群或数据库之间。这可能出于备份、恢复、测试环境复制等目的。本文将详细介绍如何在Greenplum的不同集群之间同步数据，以及如何监控性能以确保过程的...
greenplum数据库jdbc驱动下载
11-04
绿盟（Greenplum）是一种基于MPP（大规模并行处理）架构的开源数据仓库系统，主要用于大数据分析和处理。JDBC（Java Database Connectivity）是Java编程语言中用于与各种数据库进行交互的一种标准接口。在Java应用...
GreenPlum数据库.ppt
06-16
与传统的实时应用集群（如Oracle RAC）不同，GreenPlum采用MPP架构，即所有数据库组件都是独立的，不共享硬件资源。这种架构使得GreenPlum能够横向扩展，通过增加更多Segment节点来提升处理能力和存储容量。 **2. ...
FreeXploiT HTML(Hacker Technology Mad Lead)
FreeXploiT
10-24 3948
首先我们得自己写一个搜索引擎 我觉得使用蠕虫最好 然后让蠕虫去搜索并把资料反馈到我们的肉鸡上面去 为了防止产生ddos 以及 资料丢失 我们可以采用多台肉鸡服务器 10－50台不等
HEAP: Free Heap block XXXXXXXX modified at XXXXXXXX after it was freed
热门推荐
mons_xujingtao的博客
07-11 104万+
在有关于内存分配和释放的代码中，容易发生这种问题。这个问题的描述就是内存已经被释放了，后面还继续使用举个例子：float* distance = new float [dimension]; for(int k=0;k&lt;10;k++) {     for(int i=0;i&lt;dimension;i++)     {     distance[i]=0;     } delete[] d...
GreenPlum 启动失败Failed to start Master instance in admin mode问题
csdn's blog
08-01 1万+
开发同事跟我说，测试环境的greenplun突然连接不上了，于是我登陆进去服务器，发现没有greenplun进程了，问开发同事是否有对greenplumn有过改动之类的，他们说没有动过，这就奇了怪了，咋回事呢？ 自己手动尝试下gpstart启动报错 [gpadmin@00_mdw ~]$ gpstart 20170517:10:53:59:017586 gpstart:00_mdw:gpa...
MYSQL:Unknown column ‘字段名‘ in ‘field list‘ 错误解决方案
qingmenghan的博客
10-12 5万+
当后台报这个错误的时候，说明实体类中的字段名出错了，解决方案： 1，检查数据库中的字段名与实体类中的字段名是否一致，特别要注意单词字母， 2，检查数据库中的字段是否与实体类中的字段一致。比如数据库中没有该字段，实体类中出现了就会报这个错（一般改别人写的代码会出现这个情况。） ...
10000 pcs free gift of chinese top grade brown film faced plywood
xvxonfl24的专栏
03-15 11万+
We LongDa Wood manufacture hardwood core 3 time hot press Brown film faced plywood. The core of this kind Brown film faced plywood is made from 13 layers for 18mm thickness plywood.  Brown film 
Greenplum初始化数据库时出现gpadmin-[ERROR]:-gpstart error: Do not have enough valid segments to start the arr
double_happiness的博客
10-18 3863
启动初始化greenplum数据库报错信息如下所示 [gpadmin@mdw gpAdminLogs]$ gpstart 20181018:01:09:27:043309 gpstart:mdw:gpadmin-[INFO]:-Starting gpstart with args: 20181018:01:09:27:043309 gpstart:mdw:gpadmin-[INFO]:-Ga...
修改或更新数据库，提示Data truncated for column ‘字段名‘ at row 1 的原因及解决方法
qq_43070236的博客
08-06 10万+
修改或更新数据库，提示Data truncated for column ‘字段名‘ at row 1 的原因及解决方法
Greenplum segment节点异常恢复
无锋剑
08-30 2588
Segment检测及故障切换机制 GP Master首先会检测Primary状态，如果Primary不可连通，那么将会检测Mirror状态，Primary/Mirror状态总共有4种： Primary活着，Mirror活着。GP Master探测Primary成功之后直接返回，进行下一个Segment检测； Primary活着，Mirror挂了。GP Master探测Primary成功之后，通...
小波变换db4进行四层分解及其信号重构—matlab分析及C语言实现
qq_46416934的博客
06-22 2039
本篇文章主要分析了matlab中关于小波变换的相关函数：wavedec（用于小波分解）和wrcoef（用于小波重构）。通过分析两个函数的实际动作，进一步用C语言实现小波变换的分解及重构。最后比较了matlab的结果与C语言的结果，结果一致，实现了C语言的小波变换。 （*ps：本文只针对db4小波，分析四层的小波变换。其他小波及不同层数的分解需要根据实际情况对程序进行改动。）wavedec函数是用于小波分解的函数，在matlab中使用时的基本格式如下： 输入：名称意义rawData需要分解的原始数据4分解的层
Greenplum数据库单集群与多节点安装详述
本文档详细介绍了如何在Linux服务器环境下安装Greenplum（GP）数据库，主要分为两个部分：单体安装和集群安装。首先，我们来概述一下这两个部分的主要内容。 **一、GP单节点安装** 1. **安装准备**：首先，你需要从...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值