Hadoop HDFS Short-Circuit Local Reads

本文固定链接:https://www.askmac.cn/archives/hdfs-short-circuit-local-reads.html

原文地址:http://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-hdfs/ShortCircuitLocalReads.html

 

1.本地读

1.1背景

在HDFS,读一般是通过DataNode。因此,当客户端请求DataNode来读取一个文件时,DataNode从磁盘读取文件,然后通过TCP socket发送给客户端。所谓的本地读(短路读),是通过DataNode ,允许客户端直接去读取文件。短路读为很多应用提供了优秀的性能。

 

[Read more…]

【MySQL学生手册】更多备份相关

本文地址:https://www.askmac.cn/archives/mysql-more-bk-related.html

 

 

11.5 备份日志和状态文件

 

除了备份数据库之外,你还应该备份以下文件:

 

  • 你的二进制日志文件。如果你不得不进行数据库恢复的话,binary log备份存储了你在备份之后的更新。
  • 由服务端所使用的配置项文件(cnf或my.ini文件),这些文件包含了在数据库发生奔溃后恢复所需的的配置信息。
  • Replication从库端(Slave)所建立的一个info文件,这个文件包含有所需连接的主库信息。以及relay-log.info文件,这个文件记录了当前处理relay日志的进度情况。
  • Replication从库在处理LOAD DATA INFILE语句时会建立数据临时文件。这些文件被放置在由slave_load_tmpdir系统变量所设置的目录位置下,此变量可以在服务端启动时通过 –slave-load-tmpdir项进行设置。当slave_load_tmpdir未被设置,那么文件就会被存放在操作系统变量tmpdir都指定的位置。其处理的文件会以SQL_LOAD- 打头。

 

为了备份以上这些文件,你可以使用一般的文件系统操作。静态文件如配置文件(option file)不需要特别的注意即可进行备份。动态文件如服务端正在运行且改变的日志文件,则需要停止服务端,然后进行备份。

[Read more…]

Hadoop C API libhdfs

本文固定链接:https://www.askmac.cn/archives/hadoop-c-api-libhdfs.html

原文地址:http://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-hdfs/LibHdfs.html

 

1介绍

Libhdfs 是一个在HDFS中JNI 基础的C API 。它提供了一个HDFS APIs的子集C APIs来操作HDFS文件和文件系统。Libhdfs

Libhdfs是Hadoop分布式的一部分,并且在$HADOOP_HDFS_HOME/lib/native/libhdfs.so中预编译。Libhdfs 兼容Winddows并且可以通过hadoop-hdfs-project/hadoop-hdf根目录下的mvn来编译。(www.askmac.cn)

 

 

2 APIs

Libhdfs apis 时 Hadoop 文件系统API的一个子集。

在$HADOOP_HDFS_HOME/include/hdfs.h中的头文件描述了每个API的详细详细。(www.askmac.cn)

[Read more…]

【MySQL学生手册】建立文本备份

本文地址:https://www.askmac.cn/archives/mysql-generate-text-backup.html

 

11.4 建立文本备份

 

11.4.1 通过SQL建立文件备份

 

SELECT命令可以和INTO OUTFILE语法一起使用来将返回结果直接写入文件中。在使用中,需要将INTO OUTFILE语法放在FROM语法之前。例如,将Country表中数据写入Country.txt文件中,执行以下语句:

 

mysql> select * from into outfile 'Country.txt' from Country;

 

 

其中文件名指定了你希望写入的位置,这里也可以写路径,如果没有写明路径,则是指当前会话登陆时所在位置下。

 

SELECT … INTO OUTFILE 使用时有以下特点:

 

  • 此语句可被用于本地或远程服务端。由于是服务端本身来写文件,因此生成的结果文件总是被建立在服务端。
  • 需要输出文件不能已经存在。
  • 语句可用于任何存储引擎。
  • 语句要求有FILE权限。
  • 输出格式可以通过使用语句项,定义其指定列和行分隔符,引用符和逃逸符来进行控制。

 

使用INTO OUTFILE可以在以下几个方面改变SELECT语句的操作:

 

  • 文件被写于服务端,而非通过网路将文件发送至客户端(文件名不能已经存在)。
  • 服务端会在其主机上写一个新文件(执行语句需要登录服务端并使用具有FILE权限的账号)
  • 被建立的文件具有文件系统访问权限,并为MySQL服务端所有,不过对所有用户开放可读。
  • 文件的包含的数据按查询语句返回结果中每条记录一行(默认,列值之间以tab制表符进行分隔,每行则在出现新记录时终止)

 

 

你可以像CSV格式一样建立以逗号分隔值,使用双引号括起值,并对行以回车换行符(Carriage Return:CR)结尾的格式文件。以这种格式来输出结果信息的话,可以使用以下SELECT … INTO OUTFILE语句:

 

 

SELECT * INTO OUTFILE '/tmp/data-out.txt'
FIELDS TERMINATED BY ',' ENCLOSED BY '"'
LINES TERMINATED BY '\r'
FROM t;

[Read more…]

【MySQL学生手册】建立binary备份

本文地址:https://www.askmac.cn/archives/mysql-generate-binary-bk.html

 

11.3.1 建立MyISAMBinary备份

为了对MyISAM表建立一份binary备份,可以拷贝对应表的.frm,.MYD和.MYI文件。当你这么做时,必须确保这些表在被拷贝时没有在被其它程序(包括服务端)所使用。如果你在拷贝表前就关停了服务端,那就没什么问题了。如果拷贝的时候服务端还在运行,那就需要使用适当的锁来避免服务端对这些表的访问。例如,拷贝world数据库中的Country表前,进行锁表并将有待永久保存的变更刷出内存操作:

mysql> use world;
mysql> lock tables Country read;
mysql> flush tables Country;

然后(在表被锁住的情况下)使用操作系统文件拷贝命令将表文件拷贝出来。

 

以MyISAM数据库表world.Country拷贝举例(这里假设Country表为MyISAM引擎表):

# cp /usr/local/mysql/data/world/Country.frm /var/backup/Countryfrm
# cp /usr/local/mysql/data/world/Country.MYI /var/backup/CountryMYI
# cp /usr/local/mysql/data/world/Country.MYD /var/backup/CountryMYD
# cp /usr/local/mysql/data/world/Country.TRN /var/backup/CountryTRN
# cp /usr/local/mysql/data/world/Country.TRG /var/backup/CountryTRG
# cp /usr/local/mysql/data/mysql/proc /var/backup/CountryROUTINES

在拷贝操作完成后,释放表锁:

mysql> unlock tables;

 

之前的方法可以用于Unix/Linux系统上的数据库文件备份。在Windows上,被服务端锁住的表文件则由于文件锁原因而不能被拷贝备份。在这样情况下,你就必须在拷贝表文件前关闭服务端。

 

另一种MyISAM二进制备份方式是使用mysqlhotcopy脚本工具,它可以帮你锁表并拷贝文件。

[Read more…]

APOUC 2016 上海 – 亚太用户组高峰会议小记

刚回到家,打开邮箱,就看见APOUC发来的会后反馈邮件,除了头疼以外,还不免有些脸红惭愧。(真不知道怎么评分啊~~~)

老汪本人由于多方面原因无奈未能准时到场,感冒导致状态不佳是其一,这更是时常导致会议时神游物外。除了代表SHOUG(上海Oracle用户组)进行了4 min pitch的发言,之后更多地是积极参与到和不同用户组代表以及Oracle技术大咖们的吹牛打P中去了。

是否让SHOUG的成员们有些小失望呢?虽说Oracle用户组高峰会上的主题内容仅能说出个大概,不过如果大家真的感兴趣的话,那么可以也去翻看下其它用户组代表们的官文,发现会场上直接做现场微报道的还真不少呢。

[Read more…]

MySQL ERROR CODE LIST

If you cannot recover data by yourself, ask Parnassusdata, the professional MySQL database recovery team for help.

Parnassusdata Software Database Recovery Team

Service Hotline:  +86 13764045638 E-mail: service@parnassusdata.com


MySQL error code 120: Didn't find key on read or update
MySQL error code 121: Duplicate key on write or update
MySQL error code 122: Internal (unspecified) error in handler
MySQL error code 123: Someone has changed the row since it was read (while the table was locked to prevent it)
MySQL error code 124: Wrong index given to function
MySQL error code 125: Undefined handler error 125
MySQL error code 126: Index file is crashed
MySQL error code 127: Record file is crashed
MySQL error code 128: Out of memory in engine
MySQL error code 129: Undefined handler error 129
MySQL error code 130: Incorrect file format
MySQL error code 131: Command not supported by database
MySQL error code 132: Old database file
MySQL error code 133: No record read before update
MySQL error code 134: Record was already deleted (or record file crashed)
MySQL error code 135: No more room in record file
MySQL error code 136: No more room in index file
MySQL error code 137: No more records (read after end of file)
MySQL error code 138: Unsupported extension used for table
MySQL error code 139: Too big row
MySQL error code 140: Wrong create options
MySQL error code 141: Duplicate unique key or constraint on write or update
MySQL error code 142: Unknown character set used in table
MySQL error code 143: Conflicting table definitions in sub-tables of MERGE table
MySQL error code 144: Table is crashed and last repair failed
MySQL error code 145: Table was marked as crashed and should be repaired
MySQL error code 146: Lock timed out; Retry transaction
MySQL error code 147: Lock table is full;  Restart program with a larger locktable
MySQL error code 148: Updates are not allowed under a read only transactions
MySQL error code 149: Lock deadlock; Retry transaction
MySQL error code 150: Foreign key constraint is incorrectly formed
MySQL error code 151: Cannot add a child row
MySQL error code 152: Cannot delete a parent row
MySQL error code 153: No savepoint with that name
MySQL error code 154: Non unique key block size
MySQL error code 155: The table does not exist in engine
MySQL error code 156: The table already existed in storage engine
MySQL error code 157: Could not connect to storage engine
MySQL error code 158: Unexpected null pointer found when using spatial index
MySQL error code 159: The table changed in storage engine
MySQL error code 160: There's no partition in table for the given value
MySQL error code 161: Row-based binlogging of row failed
MySQL error code 162: Index needed in foreign key constraint
MySQL error code 163: Upholding foreign key constraints would lead to a duplicate key error in some other table
MySQL error code 164: Table needs to be upgraded before it can be used
MySQL error code 165: Table is read only
MySQL error code 166: Failed to get next auto increment value
MySQL error code 167: Failed to set row auto increment value
MySQL error code 168: Unknown (generic) error from engine
MySQL error code 169: Record is the same
MySQL error code 170: It is not possible to log this statement
MySQL error code 171: The event was corrupt, leading to illegal data being read
MySQL error code 172: The table is of a new format not supported by this version
MySQL error code 173: The event could not be processed no other hanlder error happened
MySQL error code 174: Got a fatal error during initialzaction of handler
MySQL error code 175: File to short; Expected more data in file
MySQL error code 176: Read page with wrong checksum
MySQL error code 177: Too many active concurrent transactions
MySQL error code 178: Record not matching the given partition set
MySQL error code 179: Index column length exceeds limit
MySQL error code 180: Index corrupted
MySQL error code 181: Undo record too big
MySQL error code 182: Invalid InnoDB FTS Doc ID
MySQL error code 183: Table is being used in foreign key check
MySQL error code 184: Tablespace already exists
MySQL error code 185: Too many columns
MySQL error code 186: Row in wrong partition
MySQL error code 187: InnoDB is in read only mode
MySQL error code 188: FTS query exceeds result cache memory limit
MySQL error code 189: Temporary file write failure
MySQL error code 190: Operation not allowed when innodb_forced_recovery > 0
MySQL error code 191: Too many words in a FTS phrase or proximity search
MySQL error code 192: Foreign key cascade delete/update exceeds max depth
MySQL error code 193: Required Create option missing
MySQL error code 194: Out of memory in storage engine
MySQL error code 195: Table corrupted
MySQL error code 196: Query interrupted
MySQL error code 197: Tablespace cannot be accessed
MySQL error code 198: Tablespace is not empty
MySQL error code 199: Incorrect file name
MySQL error code 200: Operation is not allowed
MySQL error code 201: Compute generate value failed
MySQL error code 1000 (ER_HASHCHK): hashchk
MySQL error code 1001 (ER_NISAMCHK): isamchk
MySQL error code 1002 (ER_NO): NO
MySQL error code 1003 (ER_YES): YES
MySQL error code 1004 (ER_CANT_CREATE_FILE): Can't create file '%-.200s' (errno: %d - %s)
MySQL error code 1005 (ER_CANT_CREATE_TABLE): Can't create table '%-.200s' (errno: %d)
MySQL error code 1006 (ER_CANT_CREATE_DB): Can't create database '%-.192s' (errno: %d)
MySQL error code 1007 (ER_DB_CREATE_EXISTS): Can't create database '%-.192s'; database exists
MySQL error code 1008 (ER_DB_DROP_EXISTS): Can't drop database '%-.192s'; database doesn't exist
MySQL error code 1009 (ER_DB_DROP_DELETE): Error dropping database (can't delete '%-.192s', errno: %d)
MySQL error code 1010 (ER_DB_DROP_RMDIR): Error dropping database (can't rmdir '%-.192s', errno: %d)
MySQL error code 1011 (ER_CANT_DELETE_FILE): Error on delete of '%-.192s' (errno: %d - %s)
MySQL error code 1012 (ER_CANT_FIND_SYSTEM_REC): Can't read record in system table
MySQL error code 1013 (ER_CANT_GET_STAT): Can't get status of '%-.200s' (errno: %d - %s)
MySQL error code 1014 (ER_CANT_GET_WD): Can't get working directory (errno: %d - %s)
MySQL error code 1015 (ER_CANT_LOCK): Can't lock file (errno: %d - %s)
MySQL error code 1016 (ER_CANT_OPEN_FILE): Can't open file: '%-.200s' (errno: %d - %s)
MySQL error code 1017 (ER_FILE_NOT_FOUND): Can't find file: '%-.200s' (errno: %d - %s)
MySQL error code 1018 (ER_CANT_READ_DIR): Can't read dir of '%-.192s' (errno: %d - %s)
MySQL error code 1019 (ER_CANT_SET_WD): Can't change dir to '%-.192s' (errno: %d - %s)
MySQL error code 1020 (ER_CHECKREAD): Record has changed since last read in table '%-.192s'
MySQL error code 1021 (ER_DISK_FULL): Disk full (%s); waiting for someone to free some space... (errno: %d - %s)
MySQL error code 1022 (ER_DUP_KEY): Can't write; duplicate key in table '%-.192s'
MySQL error code 1023 (ER_ERROR_ON_CLOSE): Error on close of '%-.192s' (errno: %d - %s)
MySQL error code 1024 (ER_ERROR_ON_READ): Error reading file '%-.200s' (errno: %d - %s)
MySQL error code 1025 (ER_ERROR_ON_RENAME): Error on rename of '%-.210s' to '%-.210s' (errno: %d - %s)
MySQL error code 1026 (ER_ERROR_ON_WRITE): Error writing file '%-.200s' (errno: %d - %s)
MySQL error code 1027 (ER_FILE_USED): '%-.192s' is locked against change
MySQL error code 1028 (ER_FILSORT_ABORT): Sort aborted
MySQL error code 1029 (ER_FORM_NOT_FOUND): View '%-.192s' doesn't exist for '%-.192s'
MySQL error code 1030 (ER_GET_ERRNO): Got error %d from storage engine
MySQL error code 1031 (ER_ILLEGAL_HA): Table storage engine for '%-.192s' doesn't have this option
MySQL error code 1032 (ER_KEY_NOT_FOUND): Can't find record in '%-.192s'
MySQL error code 1033 (ER_NOT_FORM_FILE): Incorrect information in file: '%-.200s'
MySQL error code 1034 (ER_NOT_KEYFILE): Incorrect key file for table '%-.200s'; try to repair it
MySQL error code 1035 (ER_OLD_KEYFILE): Old key file for table '%-.192s'; repair it!
MySQL error code 1036 (ER_OPEN_AS_READONLY): Table '%-.192s' is read only
MySQL error code 1037 (ER_OUTOFMEMORY): Out of memory; restart server and try again (needed %d bytes)
MySQL error code 1038 (ER_OUT_OF_SORTMEMORY): Out of sort memory, consider increasing server sort buffer size
MySQL error code 1039 (ER_UNEXPECTED_EOF): Unexpected EOF found when reading file '%-.192s' (errno: %d - %s)
MySQL error code 1040 (ER_CON_COUNT_ERROR): Too many connections
MySQL error code 1041 (ER_OUT_OF_RESOURCES): Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap space
MySQL error code 1042 (ER_BAD_HOST_ERROR): Can't get hostname for your address
MySQL error code 1043 (ER_HANDSHAKE_ERROR): Bad handshake
MySQL error code 1044 (ER_DBACCESS_DENIED_ERROR): Access denied for user '%-.48s'@'%-.64s' to database '%-.192s'
MySQL error code 1045 (ER_ACCESS_DENIED_ERROR): Access denied for user '%-.48s'@'%-.64s' (using password: %s)
MySQL error code 1046 (ER_NO_DB_ERROR): No database selected
MySQL error code 1047 (ER_UNKNOWN_COM_ERROR): Unknown command
MySQL error code 1048 (ER_BAD_NULL_ERROR): Column '%-.192s' cannot be null
MySQL error code 1049 (ER_BAD_DB_ERROR): Unknown database '%-.192s'
MySQL error code 1050 (ER_TABLE_EXISTS_ERROR): Table '%-.192s' already exists
MySQL error code 1051 (ER_BAD_TABLE_ERROR): Unknown table '%-.100s'
MySQL error code 1052 (ER_NON_UNIQ_ERROR): Column '%-.192s' in %-.192s is ambiguous
MySQL error code 1053 (ER_SERVER_SHUTDOWN): Server shutdown in progress
MySQL error code 1054 (ER_BAD_FIELD_ERROR): Unknown column '%-.192s' in '%-.192s'
MySQL error code 1055 (ER_WRONG_FIELD_WITH_GROUP): '%-.192s' isn't in GROUP BY
MySQL error code 1056 (ER_WRONG_GROUP_FIELD): Can't group on '%-.192s'
MySQL error code 1057 (ER_WRONG_SUM_SELECT): Statement has sum functions and columns in same statement
MySQL error code 1058 (ER_WRONG_VALUE_COUNT): Column count doesn't match value count
MySQL error code 1059 (ER_TOO_LONG_IDENT): Identifier name '%-.100s' is too long
MySQL error code 1060 (ER_DUP_FIELDNAME): Duplicate column name '%-.192s'
MySQL error code 1061 (ER_DUP_KEYNAME): Duplicate key name '%-.192s'
MySQL error code 1062 (ER_DUP_ENTRY): Duplicate entry '%-.192s' for key %d
MySQL error code 1063 (ER_WRONG_FIELD_SPEC): Incorrect column specifier for column '%-.192s'
MySQL error code 1064 (ER_PARSE_ERROR): %s near '%-.80s' at line %d
MySQL error code 1065 (ER_EMPTY_QUERY): Query was empty
MySQL error code 1066 (ER_NONUNIQ_TABLE): Not unique table/alias: '%-.192s'
MySQL error code 1067 (ER_INVALID_DEFAULT): Invalid default value for '%-.192s'
MySQL error code 1068 (ER_MULTIPLE_PRI_KEY): Multiple primary key defined
MySQL error code 1069 (ER_TOO_MANY_KEYS): Too many keys specified; max %d keys allowed
MySQL error code 1070 (ER_TOO_MANY_KEY_PARTS): Too many key parts specified; max %d parts allowed
MySQL error code 1071 (ER_TOO_LONG_KEY): Specified key was too long; max key length is %d bytes
MySQL error code 1072 (ER_KEY_COLUMN_DOES_NOT_EXITS): Key column '%-.192s' doesn't exist in table
MySQL error code 1073 (ER_BLOB_USED_AS_KEY): BLOB column '%-.192s' can't be used in key specification with the used table type
MySQL error code 1074 (ER_TOO_BIG_FIELDLENGTH): Column length too big for column '%-.192s' (max = %lu); use BLOB or TEXT instead
MySQL error code 1075 (ER_WRONG_AUTO_KEY): Incorrect table definition; there can be only one auto column and it must be defined as a key
MySQL error code 1076 (ER_READY): %s: ready for connections.
MySQL error code 1077 (ER_NORMAL_SHUTDOWN): %s: Normal shutdown
MySQL error code 1078 (ER_GOT_SIGNAL): %s: Got signal %d. Aborting!
MySQL error code 1079 (ER_SHUTDOWN_COMPLETE): %s: Shutdown complete
MySQL error code 1080 (ER_FORCING_CLOSE): %s: Forcing close of thread %ld  user: '%-.48s'
MySQL error code 1081 (ER_IPSOCK_ERROR): Can't create IP socket
MySQL error code 1082 (ER_NO_SUCH_INDEX): Table '%-.192s' has no index like the one used in CREATE INDEX; recreate the table
MySQL error code 1083 (ER_WRONG_FIELD_TERMINATORS): Field separator argument is not what is expected; check the manual
MySQL error code 1084 (ER_BLOBS_AND_NO_TERMINATED): You can't use fixed rowlength with BLOBs; please use 'fields terminated by'
MySQL error code 1085 (ER_TEXTFILE_NOT_READABLE): The file '%-.128s' must be in the database directory or be readable by all
MySQL error code 1086 (ER_FILE_EXISTS_ERROR): File '%-.200s' already exists
MySQL error code 1087 (ER_LOAD_INFO): Records: %ld  Deleted: %ld  Skipped: %ld  Warnings: %ld
MySQL error code 1088 (ER_ALTER_INFO): Records: %ld  Duplicates: %ld
MySQL error code 1089 (ER_WRONG_SUB_KEY): Incorrect prefix key; the used key part isn't a string, the used length is longer than the key part, or the storage engine doesn't support unique prefix keys
MySQL error code 1090 (ER_CANT_REMOVE_ALL_FIELDS): You can't delete all columns with ALTER TABLE; use DROP TABLE instead
MySQL error code 1091 (ER_CANT_DROP_FIELD_OR_KEY): Can't DROP '%-.192s'; check that column/key exists
MySQL error code 1092 (ER_INSERT_INFO): Records: %ld  Duplicates: %ld  Warnings: %ld
MySQL error code 1093 (ER_UPDATE_TABLE_USED): You can't specify target table '%-.192s' for update in FROM clause
MySQL error code 1094 (ER_NO_SUCH_THREAD): Unknown thread id: %lu
MySQL error code 1095 (ER_KILL_DENIED_ERROR): You are not owner of thread %lu
MySQL error code 1096 (ER_NO_TABLES_USED): No tables used
MySQL error code 1097 (ER_TOO_BIG_SET): Too many strings for column %-.192s and SET
MySQL error code 1098 (ER_NO_UNIQUE_LOGFILE): Can't generate a unique log-filename %-.200s.(1-999)
MySQL error code 1099 (ER_TABLE_NOT_LOCKED_FOR_WRITE): Table '%-.192s' was locked with a READ lock and can't be updated
MySQL error code 1100 (ER_TABLE_NOT_LOCKED): Table '%-.192s' was not locked with LOCK TABLES
MySQL error code 1101 (ER_BLOB_CANT_HAVE_DEFAULT): BLOB, TEXT, GEOMETRY or JSON column '%-.192s' can't have a default value
MySQL error code 1102 (ER_WRONG_DB_NAME): Incorrect database name '%-.100s'
MySQL error code 1103 (ER_WRONG_TABLE_NAME): Incorrect table name '%-.100s'
MySQL error code 1104 (ER_TOO_BIG_SELECT): The SELECT would examine more than MAX_JOIN_SIZE rows; check your WHERE and use SET SQL_BIG_SELECTS=1 or SET MAX_JOIN_SIZE=# if the SELECT is okay
MySQL error code 1105 (ER_UNKNOWN_ERROR): Unknown error
MySQL error code 1106 (ER_UNKNOWN_PROCEDURE): Unknown procedure '%-.192s'
MySQL error code 1107 (ER_WRONG_PARAMCOUNT_TO_PROCEDURE): Incorrect parameter count to procedure '%-.192s'
MySQL error code 1108 (ER_WRONG_PARAMETERS_TO_PROCEDURE): Incorrect parameters to procedure '%-.192s'
MySQL error code 1109 (ER_UNKNOWN_TABLE): Unknown table '%-.192s' in %-.32s
MySQL error code 1110 (ER_FIELD_SPECIFIED_TWICE): Column '%-.192s' specified twice
MySQL error code 1111 (ER_INVALID_GROUP_FUNC_USE): Invalid use of group function
MySQL error code 1112 (ER_UNSUPPORTED_EXTENSION): Table '%-.192s' uses an extension that doesn't exist in this MySQL version
MySQL error code 1113 (ER_TABLE_MUST_HAVE_COLUMNS): A table must have at least 1 column
MySQL error code 1114 (ER_RECORD_FILE_FULL): The table '%-.192s' is full
MySQL error code 1115 (ER_UNKNOWN_CHARACTER_SET): Unknown character set: '%-.64s'
MySQL error code 1116 (ER_TOO_MANY_TABLES): Too many tables; MySQL can only use %d tables in a join
MySQL error code 1117 (ER_TOO_MANY_FIELDS): Too many columns
MySQL error code 1118 (ER_TOO_BIG_ROWSIZE): Row size too large. The maximum row size for the used table type, not counting BLOBs, is %ld. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs
MySQL error code 1119 (ER_STACK_OVERRUN): Thread stack overrun:  Used: %ld of a %ld stack.  Use 'mysqld --thread_stack=#' to specify a bigger stack if needed
MySQL error code 1120 (ER_WRONG_OUTER_JOIN): Cross dependency found in OUTER JOIN; examine your ON conditions
MySQL error code 1121 (ER_NULL_COLUMN_IN_INDEX): Table handler doesn't support NULL in given index. Please change column '%-.192s' to be NOT NULL or use another handler
MySQL error code 1122 (ER_CANT_FIND_UDF): Can't load function '%-.192s'
MySQL error code 1123 (ER_CANT_INITIALIZE_UDF): Can't initialize function '%-.192s'; %-.80s
MySQL error code 1124 (ER_UDF_NO_PATHS): No paths allowed for shared library
MySQL error code 1125 (ER_UDF_EXISTS): Function '%-.192s' already exists
MySQL error code 1126 (ER_CANT_OPEN_LIBRARY): Can't open shared library '%-.192s' (errno: %d %-.128s)
MySQL error code 1127 (ER_CANT_FIND_DL_ENTRY): Can't find symbol '%-.128s' in library
MySQL error code 1128 (ER_FUNCTION_NOT_DEFINED): Function '%-.192s' is not defined
MySQL error code 1129 (ER_HOST_IS_BLOCKED): Host '%-.64s' is blocked because of many connection errors; unblock with 'mysqladmin flush-hosts'
MySQL error code 1130 (ER_HOST_NOT_PRIVILEGED): Host '%-.64s' is not allowed to connect to this MySQL server
MySQL error code 1131 (ER_PASSWORD_ANONYMOUS_USER): You are using MySQL as an anonymous user and anonymous users are not allowed to change passwords
MySQL error code 1132 (ER_PASSWORD_NOT_ALLOWED): You must have privileges to update tables in the mysql database to be able to change passwords for others
MySQL error code 1133 (ER_PASSWORD_NO_MATCH): Can't find any matching row in the user table
MySQL error code 1134 (ER_UPDATE_INFO): Rows matched: %ld  Changed: %ld  Warnings: %ld
MySQL error code 1135 (ER_CANT_CREATE_THREAD): Can't create a new thread (errno %d); if you are not out of available memory, you can consult the manual for a possible OS-dependent bug
MySQL error code 1136 (ER_WRONG_VALUE_COUNT_ON_ROW): Column count doesn't match value count at row %ld
MySQL error code 1137 (ER_CANT_REOPEN_TABLE): Can't reopen table: '%-.192s'
MySQL error code 1138 (ER_INVALID_USE_OF_NULL): Invalid use of NULL value
MySQL error code 1139 (ER_REGEXP_ERROR): Got error '%-.64s' from regexp
MySQL error code 1140 (ER_MIX_OF_GROUP_FUNC_AND_FIELDS): Mixing of GROUP columns (MIN(),MAX(),COUNT(),...) with no GROUP columns is illegal if there is no GROUP BY clause
MySQL error code 1141 (ER_NONEXISTING_GRANT): There is no such grant defined for user '%-.48s' on host '%-.64s'
MySQL error code 1142 (ER_TABLEACCESS_DENIED_ERROR): %-.128s command denied to user '%-.48s'@'%-.64s' for table '%-.64s'
MySQL error code 1143 (ER_COLUMNACCESS_DENIED_ERROR): %-.16s command denied to user '%-.48s'@'%-.64s' for column '%-.192s' in table '%-.192s'
MySQL error code 1144 (ER_ILLEGAL_GRANT_FOR_TABLE): Illegal GRANT/REVOKE command; please consult the manual to see which privileges can be used
MySQL error code 1145 (ER_GRANT_WRONG_HOST_OR_USER): The host or user argument to GRANT is too long
MySQL error code 1146 (ER_NO_SUCH_TABLE): Table '%-.192s.%-.192s' doesn't exist
MySQL error code 1147 (ER_NONEXISTING_TABLE_GRANT): There is no such grant defined for user '%-.48s' on host '%-.64s' on table '%-.192s'
MySQL error code 1148 (ER_NOT_ALLOWED_COMMAND): The used command is not allowed with this MySQL version
MySQL error code 1149 (ER_SYNTAX_ERROR): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use
MySQL error code 1150 (ER_UNUSED1): Delayed insert thread couldn't get requested lock for table %-.192s
MySQL error code 1151 (ER_UNUSED2): Too many delayed threads in use
MySQL error code 1152 (ER_ABORTING_CONNECTION): Aborted connection %ld to db: '%-.192s' user: '%-.48s' (%-.64s)
MySQL error code 1153 (ER_NET_PACKET_TOO_LARGE): Got a packet bigger than 'max_allowed_packet' bytes
MySQL error code 1154 (ER_NET_READ_ERROR_FROM_PIPE): Got a read error from the connection pipe
MySQL error code 1155 (ER_NET_FCNTL_ERROR): Got an error from fcntl()
MySQL error code 1156 (ER_NET_PACKETS_OUT_OF_ORDER): Got packets out of order
MySQL error code 1157 (ER_NET_UNCOMPRESS_ERROR): Couldn't uncompress communication packet
MySQL error code 1158 (ER_NET_READ_ERROR): Got an error reading communication packets
MySQL error code 1159 (ER_NET_READ_INTERRUPTED): Got timeout reading communication packets
MySQL error code 1160 (ER_NET_ERROR_ON_WRITE): Got an error writing communication packets
MySQL error code 1161 (ER_NET_WRITE_INTERRUPTED): Got timeout writing communication packets
MySQL error code 1162 (ER_TOO_LONG_STRING): Result string is longer than 'max_allowed_packet' bytes
MySQL error code 1163 (ER_TABLE_CANT_HANDLE_BLOB): The used table type doesn't support BLOB/TEXT columns
MySQL error code 1164 (ER_TABLE_CANT_HANDLE_AUTO_INCREMENT): The used table type doesn't support AUTO_INCREMENT columns
MySQL error code 1165 (ER_UNUSED3): INSERT DELAYED can't be used with table '%-.192s' because it is locked with LOCK TABLES
MySQL error code 1166 (ER_WRONG_COLUMN_NAME): Incorrect column name '%-.100s'
MySQL error code 1167 (ER_WRONG_KEY_COLUMN): The used storage engine can't index column '%-.192s'
MySQL error code 1168 (ER_WRONG_MRG_TABLE): Unable to open underlying table which is differently defined or of non-MyISAM type or doesn't exist
MySQL error code 1169 (ER_DUP_UNIQUE): Can't write, because of unique constraint, to table '%-.192s'
MySQL error code 1170 (ER_BLOB_KEY_WITHOUT_LENGTH): BLOB/TEXT column '%-.192s' used in key specification without a key length
MySQL error code 1171 (ER_PRIMARY_CANT_HAVE_NULL): All parts of a PRIMARY KEY must be NOT NULL; if you need NULL in a key, use UNIQUE instead
MySQL error code 1172 (ER_TOO_MANY_ROWS): Result consisted of more than one row
MySQL error code 1173 (ER_REQUIRES_PRIMARY_KEY): This table type requires a primary key
MySQL error code 1174 (ER_NO_RAID_COMPILED): This version of MySQL is not compiled with RAID support
MySQL error code 1175 (ER_UPDATE_WITHOUT_KEY_IN_SAFE_MODE): You are using safe update mode and you tried to update a table without a WHERE that uses a KEY column. %s
MySQL error code 1176 (ER_KEY_DOES_NOT_EXITS): Key '%-.192s' doesn't exist in table '%-.192s'
MySQL error code 1177 (ER_CHECK_NO_SUCH_TABLE): Can't open table
MySQL error code 1178 (ER_CHECK_NOT_IMPLEMENTED): The storage engine for the table doesn't support %s
MySQL error code 1179 (ER_CANT_DO_THIS_DURING_AN_TRANSACTION): You are not allowed to execute this command in a transaction
MySQL error code 1180 (ER_ERROR_DURING_COMMIT): Got error %d during COMMIT
MySQL error code 1181 (ER_ERROR_DURING_ROLLBACK): Got error %d during ROLLBACK
MySQL error code 1182 (ER_ERROR_DURING_FLUSH_LOGS): Got error %d during FLUSH_LOGS
MySQL error code 1183 (ER_ERROR_DURING_CHECKPOINT): Got error %d during CHECKPOINT
MySQL error code 1184 (ER_NEW_ABORTING_CONNECTION): Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.64s' (%-.64s)
MySQL error code 1185 (ER_DUMP_NOT_IMPLEMENTED): The storage engine for the table does not support binary table dump
MySQL error code 1186 (ER_FLUSH_MASTER_BINLOG_CLOSED): Binlog closed, cannot RESET MASTER
MySQL error code 1187 (ER_INDEX_REBUILD): Failed rebuilding the index of  dumped table '%-.192s'
MySQL error code 1188 (ER_MASTER): Error from master: '%-.64s'
MySQL error code 1189 (ER_MASTER_NET_READ): Net error reading from master
MySQL error code 1190 (ER_MASTER_NET_WRITE): Net error writing to master
MySQL error code 1191 (ER_FT_MATCHING_KEY_NOT_FOUND): Can't find FULLTEXT index matching the column list
MySQL error code 1192 (ER_LOCK_OR_ACTIVE_TRANSACTION): Can't execute the given command because you have active locked tables or an active transaction
MySQL error code 1193 (ER_UNKNOWN_SYSTEM_VARIABLE): Unknown system variable '%-.64s'
MySQL error code 1194 (ER_CRASHED_ON_USAGE): Table '%-.192s' is marked as crashed and should be repaired
MySQL error code 1195 (ER_CRASHED_ON_REPAIR): Table '%-.192s' is marked as crashed and last (automatic?) repair failed
MySQL error code 1196 (ER_WARNING_NOT_COMPLETE_ROLLBACK): Some non-transactional changed tables couldn't be rolled back
MySQL error code 1197 (ER_TRANS_CACHE_FULL): Multi-statement transaction required more than 'max_binlog_cache_size' bytes of storage; increase this mysqld variable and try again
MySQL error code 1198 (ER_SLAVE_MUST_STOP): This operation cannot be performed with a running slave; run STOP SLAVE first
MySQL error code 1199 (ER_SLAVE_NOT_RUNNING): This operation requires a running slave; configure slave and do START SLAVE
MySQL error code 1200 (ER_BAD_SLAVE): The server is not configured as slave; fix in config file or with CHANGE MASTER TO
MySQL error code 1201 (ER_MASTER_INFO): Could not initialize master info structure; more error messages can be found in the MySQL error log
MySQL error code 1202 (ER_SLAVE_THREAD): Could not create slave thread; check system resources
MySQL error code 1203 (ER_TOO_MANY_USER_CONNECTIONS): User %-.64s already has more than 'max_user_connections' active connections
MySQL error code 1204 (ER_SET_CONSTANTS_ONLY): You may only use constant expressions with SET
MySQL error code 1205 (ER_LOCK_WAIT_TIMEOUT): Lock wait timeout exceeded; try restarting transaction
MySQL error code 1206 (ER_LOCK_TABLE_FULL): The total number of locks exceeds the lock table size
MySQL error code 1207 (ER_READ_ONLY_TRANSACTION): Update locks cannot be acquired during a READ UNCOMMITTED transaction
MySQL error code 1208 (ER_DROP_DB_WITH_READ_LOCK): DROP DATABASE not allowed while thread is holding global read lock
MySQL error code 1209 (ER_CREATE_DB_WITH_READ_LOCK): CREATE DATABASE not allowed while thread is holding global read lock
MySQL error code 1210 (ER_WRONG_ARGUMENTS): Incorrect arguments to %s
MySQL error code 1211 (ER_NO_PERMISSION_TO_CREATE_USER): '%-.48s'@'%-.64s' is not allowed to create new users
MySQL error code 1212 (ER_UNION_TABLES_IN_DIFFERENT_DIR): Incorrect table definition; all MERGE tables must be in the same database
MySQL error code 1213 (ER_LOCK_DEADLOCK): Deadlock found when trying to get lock; try restarting transaction
MySQL error code 1214 (ER_TABLE_CANT_HANDLE_FT): The used table type doesn't support FULLTEXT indexes
MySQL error code 1215 (ER_CANNOT_ADD_FOREIGN): Cannot add foreign key constraint
MySQL error code 1216 (ER_NO_REFERENCED_ROW): Cannot add or update a child row: a foreign key constraint fails
MySQL error code 1217 (ER_ROW_IS_REFERENCED): Cannot delete or update a parent row: a foreign key constraint fails
MySQL error code 1218 (ER_CONNECT_TO_MASTER): Error connecting to master: %-.128s
MySQL error code 1219 (ER_QUERY_ON_MASTER): Error running query on master: %-.128s
MySQL error code 1220 (ER_ERROR_WHEN_EXECUTING_COMMAND): Error when executing command %s: %-.128s
MySQL error code 1221 (ER_WRONG_USAGE): Incorrect usage of %s and %s
MySQL error code 1222 (ER_WRONG_NUMBER_OF_COLUMNS_IN_SELECT): The used SELECT statements have a different number of columns
MySQL error code 1223 (ER_CANT_UPDATE_WITH_READLOCK): Can't execute the query because you have a conflicting read lock
MySQL error code 1224 (ER_MIXING_NOT_ALLOWED): Mixing of transactional and non-transactional tables is disabled
MySQL error code 1225 (ER_DUP_ARGUMENT): Option '%s' used twice in statement
MySQL error code 1226 (ER_USER_LIMIT_REACHED): User '%-.64s' has exceeded the '%s' resource (current value: %ld)
MySQL error code 1227 (ER_SPECIFIC_ACCESS_DENIED_ERROR): Access denied; you need (at least one of) the %-.128s privilege(s) for this operation
MySQL error code 1228 (ER_LOCAL_VARIABLE): Variable '%-.64s' is a SESSION variable and can't be used with SET GLOBAL
MySQL error code 1229 (ER_GLOBAL_VARIABLE): Variable '%-.64s' is a GLOBAL variable and should be set with SET GLOBAL
MySQL error code 1230 (ER_NO_DEFAULT): Variable '%-.64s' doesn't have a default value
MySQL error code 1231 (ER_WRONG_VALUE_FOR_VAR): Variable '%-.64s' can't be set to the value of '%-.200s'
MySQL error code 1232 (ER_WRONG_TYPE_FOR_VAR): Incorrect argument type to variable '%-.64s'
MySQL error code 1233 (ER_VAR_CANT_BE_READ): Variable '%-.64s' can only be set, not read
MySQL error code 1234 (ER_CANT_USE_OPTION_HERE): Incorrect usage/placement of '%s'
MySQL error code 1235 (ER_NOT_SUPPORTED_YET): This version of MySQL doesn't yet support '%s'
MySQL error code 1236 (ER_MASTER_FATAL_ERROR_READING_BINLOG): Got fatal error %d from master when reading data from binary log: '%-.320s'
MySQL error code 1237 (ER_SLAVE_IGNORED_TABLE): Slave SQL thread ignored the query because of replicate-*-table rules
MySQL error code 1238 (ER_INCORRECT_GLOBAL_LOCAL_VAR): Variable '%-.192s' is a %s variable
MySQL error code 1239 (ER_WRONG_FK_DEF): Incorrect foreign key definition for '%-.192s': %s
MySQL error code 1240 (ER_KEY_REF_DO_NOT_MATCH_TABLE_REF): Key reference and table reference don't match
MySQL error code 1241 (ER_OPERAND_COLUMNS): Operand should contain %d column(s)
MySQL error code 1242 (ER_SUBQUERY_NO_1_ROW): Subquery returns more than 1 row
MySQL error code 1243 (ER_UNKNOWN_STMT_HANDLER): Unknown prepared statement handler (%.*s) given to %s
MySQL error code 1244 (ER_CORRUPT_HELP_DB): Help database is corrupt or does not exist
MySQL error code 1245 (ER_CYCLIC_REFERENCE): Cyclic reference on subqueries
MySQL error code 1246 (ER_AUTO_CONVERT): Converting column '%s' from %s to %s
MySQL error code 1247 (ER_ILLEGAL_REFERENCE): Reference '%-.64s' not supported (%s)
MySQL error code 1248 (ER_DERIVED_MUST_HAVE_ALIAS): Every derived table must have its own alias
MySQL error code 1249 (ER_SELECT_REDUCED): Select %u was reduced during optimization
MySQL error code 1250 (ER_TABLENAME_NOT_ALLOWED_HERE): Table '%-.192s' from one of the SELECTs cannot be used in %-.32s
MySQL error code 1251 (ER_NOT_SUPPORTED_AUTH_MODE): Client does not support authentication protocol requested by server; consider upgrading MySQL client
MySQL error code 1252 (ER_SPATIAL_CANT_HAVE_NULL): All parts of a SPATIAL index must be NOT NULL
MySQL error code 1253 (ER_COLLATION_CHARSET_MISMATCH): COLLATION '%s' is not valid for CHARACTER SET '%s'
MySQL error code 1254 (ER_SLAVE_WAS_RUNNING): Slave is already running
MySQL error code 1255 (ER_SLAVE_WAS_NOT_RUNNING): Slave already has been stopped
MySQL error code 1256 (ER_TOO_BIG_FOR_UNCOMPRESS): Uncompressed data size too large; the maximum size is %d (probably, length of uncompressed data was corrupted)
MySQL error code 1257 (ER_ZLIB_Z_MEM_ERROR): ZLIB: Not enough memory
MySQL error code 1258 (ER_ZLIB_Z_BUF_ERROR): ZLIB: Not enough room in the output buffer (probably, length of uncompressed data was corrupted)
MySQL error code 1259 (ER_ZLIB_Z_DATA_ERROR): ZLIB: Input data corrupted
MySQL error code 1260 (ER_CUT_VALUE_GROUP_CONCAT): Row %u was cut by GROUP_CONCAT()
MySQL error code 1261 (ER_WARN_TOO_FEW_RECORDS): Row %ld doesn't contain data for all columns
MySQL error code 1262 (ER_WARN_TOO_MANY_RECORDS): Row %ld was truncated; it contained more data than there were input columns
MySQL error code 1263 (ER_WARN_NULL_TO_NOTNULL): Column set to default value; NULL supplied to NOT NULL column '%s' at row %ld
MySQL error code 1264 (ER_WARN_DATA_OUT_OF_RANGE): Out of range value for column '%s' at row %ld
MySQL error code 1265 (WARN_DATA_TRUNCATED): Data truncated for column '%s' at row %ld
MySQL error code 1266 (ER_WARN_USING_OTHER_HANDLER): Using storage engine %s for table '%s'
MySQL error code 1267 (ER_CANT_AGGREGATE_2COLLATIONS): Illegal mix of collations (%s,%s) and (%s,%s) for operation '%s'
MySQL error code 1268 (ER_DROP_USER): Cannot drop one or more of the requested users
MySQL error code 1269 (ER_REVOKE_GRANTS): Can't revoke all privileges for one or more of the requested users
MySQL error code 1270 (ER_CANT_AGGREGATE_3COLLATIONS): Illegal mix of collations (%s,%s), (%s,%s), (%s,%s) for operation '%s'
MySQL error code 1271 (ER_CANT_AGGREGATE_NCOLLATIONS): Illegal mix of collations for operation '%s'
MySQL error code 1272 (ER_VARIABLE_IS_NOT_STRUCT): Variable '%-.64s' is not a variable component (can't be used as XXXX.variable_name)
MySQL error code 1273 (ER_UNKNOWN_COLLATION): Unknown collation: '%-.64s'
MySQL error code 1274 (ER_SLAVE_IGNORED_SSL_PARAMS): SSL parameters in CHANGE MASTER are ignored because this MySQL slave was compiled without SSL support; they can be used later if MySQL slave with SSL is started
MySQL error code 1275 (ER_SERVER_IS_IN_SECURE_AUTH_MODE): Server is running in --secure-auth mode, but '%s'@'%s' has a password in the old format; please change the password to the new format
MySQL error code 1276 (ER_WARN_FIELD_RESOLVED): Field or reference '%-.192s%s%-.192s%s%-.192s' of SELECT #%d was resolved in SELECT #%d
MySQL error code 1277 (ER_BAD_SLAVE_UNTIL_COND): Incorrect parameter or combination of parameters for START SLAVE UNTIL
MySQL error code 1278 (ER_MISSING_SKIP_SLAVE): It is recommended to use --skip-slave-start when doing step-by-step replication with START SLAVE UNTIL; otherwise, you will get problems if you get an unexpected slave's mysqld restart
MySQL error code 1279 (ER_UNTIL_COND_IGNORED): SQL thread is not to be started so UNTIL options are ignored
MySQL error code 1280 (ER_WRONG_NAME_FOR_INDEX): Incorrect index name '%-.100s'
MySQL error code 1281 (ER_WRONG_NAME_FOR_CATALOG): Incorrect catalog name '%-.100s'
MySQL error code 1282 (ER_WARN_QC_RESIZE): Query cache failed to set size %lu; new query cache size is %lu
MySQL error code 1283 (ER_BAD_FT_COLUMN): Column '%-.192s' cannot be part of FULLTEXT index
MySQL error code 1284 (ER_UNKNOWN_KEY_CACHE): Unknown key cache '%-.100s'
MySQL error code 1285 (ER_WARN_HOSTNAME_WONT_WORK): MySQL is started in --skip-name-resolve mode; you must restart it without this switch for this grant to work
MySQL error code 1286 (ER_UNKNOWN_STORAGE_ENGINE): Unknown storage engine '%s'
MySQL error code 1287 (ER_WARN_DEPRECATED_SYNTAX): '%s' is deprecated and will be removed in a future release. Please use %s instead
MySQL error code 1288 (ER_NON_UPDATABLE_TABLE): The target table %-.100s of the %s is not updatable
MySQL error code 1289 (ER_FEATURE_DISABLED): The '%s' feature is disabled; you need MySQL built with '%s' to have it working
MySQL error code 1290 (ER_OPTION_PREVENTS_STATEMENT): The MySQL server is running with the %s option so it cannot execute this statement
MySQL error code 1291 (ER_DUPLICATED_VALUE_IN_TYPE): Column '%-.100s' has duplicated value '%-.64s' in %s
MySQL error code 1292 (ER_TRUNCATED_WRONG_VALUE): Truncated incorrect %-.32s value: '%-.128s'
MySQL error code 1293 (ER_TOO_MUCH_AUTO_TIMESTAMP_COLS): Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clause
MySQL error code 1294 (ER_INVALID_ON_UPDATE): Invalid ON UPDATE clause for '%-.192s' column
MySQL error code 1295 (ER_UNSUPPORTED_PS): This command is not supported in the prepared statement protocol yet
MySQL error code 1296 (ER_GET_ERRMSG): Got error %d '%-.100s' from %s
MySQL error code 1297 (ER_GET_TEMPORARY_ERRMSG): Got temporary error %d '%-.100s' from %s
MySQL error code 1298 (ER_UNKNOWN_TIME_ZONE): Unknown or incorrect time zone: '%-.64s'
MySQL error code 1299 (ER_WARN_INVALID_TIMESTAMP): Invalid TIMESTAMP value in column '%s' at row %ld
MySQL error code 1300 (ER_INVALID_CHARACTER_STRING): Invalid %s character string: '%.64s'
MySQL error code 1301 (ER_WARN_ALLOWED_PACKET_OVERFLOWED): Result of %s() was larger than max_allowed_packet (%ld) - truncated
MySQL error code 1302 (ER_CONFLICTING_DECLARATIONS): Conflicting declarations: '%s%s' and '%s%s'
MySQL error code 1303 (ER_SP_NO_RECURSIVE_CREATE): Can't create a %s from within another stored routine
MySQL error code 1304 (ER_SP_ALREADY_EXISTS): %s %s already exists
MySQL error code 1305 (ER_SP_DOES_NOT_EXIST): %s %s does not exist
MySQL error code 1306 (ER_SP_DROP_FAILED): Failed to DROP %s %s
MySQL error code 1307 (ER_SP_STORE_FAILED): Failed to CREATE %s %s
MySQL error code 1308 (ER_SP_LILABEL_MISMATCH): %s with no matching label: %s
MySQL error code 1309 (ER_SP_LABEL_REDEFINE): Redefining label %s
MySQL error code 1310 (ER_SP_LABEL_MISMATCH): End-label %s without match
MySQL error code 1311 (ER_SP_UNINIT_VAR): Referring to uninitialized variable %s
MySQL error code 1312 (ER_SP_BADSELECT): PROCEDURE %s can't return a result set in the given context
MySQL error code 1313 (ER_SP_BADRETURN): RETURN is only allowed in a FUNCTION
MySQL error code 1314 (ER_SP_BADSTATEMENT): %s is not allowed in stored procedures
MySQL error code 1315 (ER_UPDATE_LOG_DEPRECATED_IGNORED): The update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been ignored.
MySQL error code 1316 (ER_UPDATE_LOG_DEPRECATED_TRANSLATED): The update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been translated to SET SQL_LOG_BIN.
MySQL error code 1317 (ER_QUERY_INTERRUPTED): Query execution was interrupted
MySQL error code 1318 (ER_SP_WRONG_NO_OF_ARGS): Incorrect number of arguments for %s %s; expected %u, got %u
MySQL error code 1319 (ER_SP_COND_MISMATCH): Undefined CONDITION: %s
MySQL error code 1320 (ER_SP_NORETURN): No RETURN found in FUNCTION %s
MySQL error code 1321 (ER_SP_NORETURNEND): FUNCTION %s ended without RETURN
MySQL error code 1322 (ER_SP_BAD_CURSOR_QUERY): Cursor statement must be a SELECT
MySQL error code 1323 (ER_SP_BAD_CURSOR_SELECT): Cursor SELECT must not have INTO
MySQL error code 1324 (ER_SP_CURSOR_MISMATCH): Undefined CURSOR: %s
MySQL error code 1325 (ER_SP_CURSOR_ALREADY_OPEN): Cursor is already open
MySQL error code 1326 (ER_SP_CURSOR_NOT_OPEN): Cursor is not open
MySQL error code 1327 (ER_SP_UNDECLARED_VAR): Undeclared variable: %s
MySQL error code 1328 (ER_SP_WRONG_NO_OF_FETCH_ARGS): Incorrect number of FETCH variables
MySQL error code 1329 (ER_SP_FETCH_NO_DATA): No data - zero rows fetched, selected, or processed
MySQL error code 1330 (ER_SP_DUP_PARAM): Duplicate parameter: %s
MySQL error code 1331 (ER_SP_DUP_VAR): Duplicate variable: %s
MySQL error code 1332 (ER_SP_DUP_COND): Duplicate condition: %s
MySQL error code 1333 (ER_SP_DUP_CURS): Duplicate cursor: %s
MySQL error code 1334 (ER_SP_CANT_ALTER): Failed to ALTER %s %s
MySQL error code 1335 (ER_SP_SUBSELECT_NYI): Subquery value not supported
MySQL error code 1336 (ER_STMT_NOT_ALLOWED_IN_SF_OR_TRG): %s is not allowed in stored function or trigger
MySQL error code 1337 (ER_SP_VARCOND_AFTER_CURSHNDLR): Variable or condition declaration after cursor or handler declaration
MySQL error code 1338 (ER_SP_CURSOR_AFTER_HANDLER): Cursor declaration after handler declaration
MySQL error code 1339 (ER_SP_CASE_NOT_FOUND): Case not found for CASE statement
MySQL error code 1340 (ER_FPARSER_TOO_BIG_FILE): Configuration file '%-.192s' is too big
MySQL error code 1341 (ER_FPARSER_BAD_HEADER): Malformed file type header in file '%-.192s'
MySQL error code 1342 (ER_FPARSER_EOF_IN_COMMENT): Unexpected end of file while parsing comment '%-.200s'
MySQL error code 1343 (ER_FPARSER_ERROR_IN_PARAMETER): Error while parsing parameter '%-.192s' (line: '%-.192s')
MySQL error code 1344 (ER_FPARSER_EOF_IN_UNKNOWN_PARAMETER): Unexpected end of file while skipping unknown parameter '%-.192s'
MySQL error code 1345 (ER_VIEW_NO_EXPLAIN): EXPLAIN/SHOW can not be issued; lacking privileges for underlying table
MySQL error code 1346 (ER_FRM_UNKNOWN_TYPE): File '%-.192s' has unknown type '%-.64s' in its header
MySQL error code 1347 (ER_WRONG_OBJECT): '%-.192s.%-.192s' is not %s
MySQL error code 1348 (ER_NONUPDATEABLE_COLUMN): Column '%-.192s' is not updatable
MySQL error code 1349 (ER_VIEW_SELECT_DERIVED_UNUSED): View's SELECT contains a subquery in the FROM clause
MySQL error code 1350 (ER_VIEW_SELECT_CLAUSE): View's SELECT contains a '%s' clause
MySQL error code 1351 (ER_VIEW_SELECT_VARIABLE): View's SELECT contains a variable or parameter
MySQL error code 1352 (ER_VIEW_SELECT_TMPTABLE): View's SELECT refers to a temporary table '%-.192s'
MySQL error code 1353 (ER_VIEW_WRONG_LIST): View's SELECT and view's field list have different column counts
MySQL error code 1354 (ER_WARN_VIEW_MERGE): View merge algorithm can't be used here for now (assumed undefined algorithm)
MySQL error code 1355 (ER_WARN_VIEW_WITHOUT_KEY): View being updated does not have complete key of underlying table in it
MySQL error code 1356 (ER_VIEW_INVALID): View '%-.192s.%-.192s' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them
MySQL error code 1357 (ER_SP_NO_DROP_SP): Can't drop or alter a %s from within another stored routine
MySQL error code 1358 (ER_SP_GOTO_IN_HNDLR): GOTO is not allowed in a stored procedure handler
MySQL error code 1359 (ER_TRG_ALREADY_EXISTS): Trigger already exists
MySQL error code 1360 (ER_TRG_DOES_NOT_EXIST): Trigger does not exist
MySQL error code 1361 (ER_TRG_ON_VIEW_OR_TEMP_TABLE): Trigger's '%-.192s' is view or temporary table
MySQL error code 1362 (ER_TRG_CANT_CHANGE_ROW): Updating of %s row is not allowed in %strigger
MySQL error code 1363 (ER_TRG_NO_SUCH_ROW_IN_TRG): There is no %s row in %s trigger
MySQL error code 1364 (ER_NO_DEFAULT_FOR_FIELD): Field '%-.192s' doesn't have a default value
MySQL error code 1365 (ER_DIVISION_BY_ZERO): Division by 0
MySQL error code 1366 (ER_TRUNCATED_WRONG_VALUE_FOR_FIELD): Incorrect %-.32s value: '%-.128s' for column '%.192s' at row %ld
MySQL error code 1367 (ER_ILLEGAL_VALUE_FOR_TYPE): Illegal %s '%-.192s' value found during parsing
MySQL error code 1368 (ER_VIEW_NONUPD_CHECK): CHECK OPTION on non-updatable view '%-.192s.%-.192s'
MySQL error code 1369 (ER_VIEW_CHECK_FAILED): CHECK OPTION failed '%-.192s.%-.192s'
MySQL error code 1370 (ER_PROCACCESS_DENIED_ERROR): %-.16s command denied to user '%-.48s'@'%-.64s' for routine '%-.192s'
MySQL error code 1371 (ER_RELAY_LOG_FAIL): Failed purging old relay logs: %s
MySQL error code 1372 (ER_PASSWD_LENGTH): Password hash should be a %d-digit hexadecimal number
MySQL error code 1373 (ER_UNKNOWN_TARGET_BINLOG): Target log not found in binlog index
MySQL error code 1374 (ER_IO_ERR_LOG_INDEX_READ): I/O error reading log index file
MySQL error code 1375 (ER_BINLOG_PURGE_PROHIBITED): Server configuration does not permit binlog purge
MySQL error code 1376 (ER_FSEEK_FAIL): Failed on fseek()
MySQL error code 1377 (ER_BINLOG_PURGE_FATAL_ERR): Fatal error during log purge
MySQL error code 1378 (ER_LOG_IN_USE): A purgeable log is in use, will not purge
MySQL error code 1379 (ER_LOG_PURGE_UNKNOWN_ERR): Unknown error during log purge
MySQL error code 1380 (ER_RELAY_LOG_INIT): Failed initializing relay log position: %s
MySQL error code 1381 (ER_NO_BINARY_LOGGING): You are not using binary logging
MySQL error code 1382 (ER_RESERVED_SYNTAX): The '%-.64s' syntax is reserved for purposes internal to the MySQL server
MySQL error code 1383 (ER_WSAS_FAILED): WSAStartup Failed
MySQL error code 1384 (ER_DIFF_GROUPS_PROC): Can't handle procedures with different groups yet
MySQL error code 1385 (ER_NO_GROUP_FOR_PROC): Select must have a group with this procedure
MySQL error code 1386 (ER_ORDER_WITH_PROC): Can't use ORDER clause with this procedure
MySQL error code 1387 (ER_LOGGING_PROHIBIT_CHANGING_OF): Binary logging and replication forbid changing the global server %s
MySQL error code 1388 (ER_NO_FILE_MAPPING): Can't map file: %-.200s, errno: %d
MySQL error code 1389 (ER_WRONG_MAGIC): Wrong magic in %-.64s
MySQL error code 1390 (ER_PS_MANY_PARAM): Prepared statement contains too many placeholders
MySQL error code 1391 (ER_KEY_PART_0): Key part '%-.192s' length cannot be 0
MySQL error code 1392 (ER_VIEW_CHECKSUM): View text checksum failed
MySQL error code 1393 (ER_VIEW_MULTIUPDATE): Can not modify more than one base table through a join view '%-.192s.%-.192s'
MySQL error code 1394 (ER_VIEW_NO_INSERT_FIELD_LIST): Can not insert into join view '%-.192s.%-.192s' without fields list
MySQL error code 1395 (ER_VIEW_DELETE_MERGE_VIEW): Can not delete from join view '%-.192s.%-.192s'
MySQL error code 1396 (ER_CANNOT_USER): Operation %s failed for %.256s
MySQL error code 1397 (ER_XAER_NOTA): XAER_NOTA: Unknown XID
MySQL error code 1398 (ER_XAER_INVAL): XAER_INVAL: Invalid arguments (or unsupported command)
MySQL error code 1399 (ER_XAER_RMFAIL): XAER_RMFAIL: The command cannot be executed when global transaction is in the  %.64s state
MySQL error code 1400 (ER_XAER_OUTSIDE): XAER_OUTSIDE: Some work is done outside global transaction
MySQL error code 1401 (ER_XAER_RMERR): XAER_RMERR: Fatal error occurred in the transaction branch - check your data for consistency
MySQL error code 1402 (ER_XA_RBROLLBACK): XA_RBROLLBACK: Transaction branch was rolled back
MySQL error code 1403 (ER_NONEXISTING_PROC_GRANT): There is no such grant defined for user '%-.48s' on host '%-.64s' on routine '%-.192s'
MySQL error code 1404 (ER_PROC_AUTO_GRANT_FAIL): Failed to grant EXECUTE and ALTER ROUTINE privileges
MySQL error code 1405 (ER_PROC_AUTO_REVOKE_FAIL): Failed to revoke all privileges to dropped routine
MySQL error code 1406 (ER_DATA_TOO_LONG): Data too long for column '%s' at row %ld
MySQL error code 1407 (ER_SP_BAD_SQLSTATE): Bad SQLSTATE: '%s'
MySQL error code 1408 (ER_STARTUP): %s: ready for connections.
MySQL error code 1409 (ER_LOAD_FROM_FIXED_SIZE_ROWS_TO_VAR): Can't load value from file with fixed size rows to variable
MySQL error code 1410 (ER_CANT_CREATE_USER_WITH_GRANT): You are not allowed to create a user with GRANT
MySQL error code 1411 (ER_WRONG_VALUE_FOR_TYPE): Incorrect %-.32s value: '%-.128s' for function %-.32s
MySQL error code 1412 (ER_TABLE_DEF_CHANGED): Table definition has changed, please retry transaction
MySQL error code 1413 (ER_SP_DUP_HANDLER): Duplicate handler declared in the same block
MySQL error code 1414 (ER_SP_NOT_VAR_ARG): OUT or INOUT argument %d for routine %s is not a variable or NEW pseudo-variable in BEFORE trigger
MySQL error code 1415 (ER_SP_NO_RETSET): Not allowed to return a result set from a %s
MySQL error code 1416 (ER_CANT_CREATE_GEOMETRY_OBJECT): Cannot get geometry object from data you send to the GEOMETRY field
MySQL error code 1417 (ER_FAILED_ROUTINE_BREAK_BINLOG): A routine failed and has neither NO SQL nor READS SQL DATA in its declaration and binary logging is enabled; if non-transactional tables were updated, the binary log will miss their changes
MySQL error code 1418 (ER_BINLOG_UNSAFE_ROUTINE): This function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)
MySQL error code 1419 (ER_BINLOG_CREATE_ROUTINE_NEED_SUPER): You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)
MySQL error code 1420 (ER_EXEC_STMT_WITH_OPEN_CURSOR): You can't execute a prepared statement which has an open cursor associated with it. Reset the statement to re-execute it.
MySQL error code 1421 (ER_STMT_HAS_NO_OPEN_CURSOR): The statement (%lu) has no open cursor.
MySQL error code 1422 (ER_COMMIT_NOT_ALLOWED_IN_SF_OR_TRG): Explicit or implicit commit is not allowed in stored function or trigger.
MySQL error code 1423 (ER_NO_DEFAULT_FOR_VIEW_FIELD): Field of view '%-.192s.%-.192s' underlying table doesn't have a default value
MySQL error code 1424 (ER_SP_NO_RECURSION): Recursive stored functions and triggers are not allowed.
MySQL error code 1425 (ER_TOO_BIG_SCALE): Too big scale %d specified for column '%-.192s'. Maximum is %lu.
MySQL error code 1426 (ER_TOO_BIG_PRECISION): Too-big precision %d specified for '%-.192s'. Maximum is %lu.
MySQL error code 1427 (ER_M_BIGGER_THAN_D): For float(M,D), double(M,D) or decimal(M,D), M must be >= D (column '%-.192s').
MySQL error code 1428 (ER_WRONG_LOCK_OF_SYSTEM_TABLE): You can't combine write-locking of system tables with other tables or lock types
MySQL error code 1429 (ER_CONNECT_TO_FOREIGN_DATA_SOURCE): Unable to connect to foreign data source: %.64s
MySQL error code 1430 (ER_QUERY_ON_FOREIGN_DATA_SOURCE): There was a problem processing the query on the foreign data source. Data source error: %-.64s
MySQL error code 1431 (ER_FOREIGN_DATA_SOURCE_DOESNT_EXIST): The foreign data source you are trying to reference does not exist. Data source error:  %-.64s
MySQL error code 1432 (ER_FOREIGN_DATA_STRING_INVALID_CANT_CREATE): Can't create federated table. The data source connection string '%-.64s' is not in the correct format
MySQL error code 1433 (ER_FOREIGN_DATA_STRING_INVALID): The data source connection string '%-.64s' is not in the correct format
MySQL error code 1434 (ER_CANT_CREATE_FEDERATED_TABLE): Can't create federated table. Foreign data src error:  %-.64s
MySQL error code 1435 (ER_TRG_IN_WRONG_SCHEMA): Trigger in wrong schema
MySQL error code 1436 (ER_STACK_OVERRUN_NEED_MORE): Thread stack overrun:  %ld bytes used of a %ld byte stack, and %ld bytes needed.  Use 'mysqld --thread_stack=#' to specify a bigger stack.
MySQL error code 1437 (ER_TOO_LONG_BODY): Routine body for '%-.100s' is too long
MySQL error code 1438 (ER_WARN_CANT_DROP_DEFAULT_KEYCACHE): Cannot drop default keycache
MySQL error code 1439 (ER_TOO_BIG_DISPLAYWIDTH): Display width out of range for column '%-.192s' (max = %lu)
MySQL error code 1440 (ER_XAER_DUPID): XAER_DUPID: The XID already exists
MySQL error code 1441 (ER_DATETIME_FUNCTION_OVERFLOW): Datetime function: %-.32s field overflow
MySQL error code 1442 (ER_CANT_UPDATE_USED_TABLE_IN_SF_OR_TRG): Can't update table '%-.192s' in stored function/trigger because it is already used by statement which invoked this stored function/trigger.
MySQL error code 1443 (ER_VIEW_PREVENT_UPDATE): The definition of table '%-.192s' prevents operation %.192s on table '%-.192s'.
MySQL error code 1444 (ER_PS_NO_RECURSION): The prepared statement contains a stored routine call that refers to that same statement. It's not allowed to execute a prepared statement in such a recursive manner
MySQL error code 1445 (ER_SP_CANT_SET_AUTOCOMMIT): Not allowed to set autocommit from a stored function or trigger
MySQL error code 1446 (ER_MALFORMED_DEFINER): Definer is not fully qualified
MySQL error code 1447 (ER_VIEW_FRM_NO_USER): View '%-.192s'.'%-.192s' has no definer information (old table format). Current user is used as definer. Please recreate the view!
MySQL error code 1448 (ER_VIEW_OTHER_USER): You need the SUPER privilege for creation view with '%-.192s'@'%-.192s' definer
MySQL error code 1449 (ER_NO_SUCH_USER): The user specified as a definer ('%-.64s'@'%-.64s') does not exist
MySQL error code 1450 (ER_FORBID_SCHEMA_CHANGE): Changing schema from '%-.192s' to '%-.192s' is not allowed.
MySQL error code 1451 (ER_ROW_IS_REFERENCED_2): Cannot delete or update a parent row: a foreign key constraint fails (%.192s)
MySQL error code 1452 (ER_NO_REFERENCED_ROW_2): Cannot add or update a child row: a foreign key constraint fails (%.192s)
MySQL error code 1453 (ER_SP_BAD_VAR_SHADOW): Variable '%-.64s' must be quoted with `...`, or renamed
MySQL error code 1454 (ER_TRG_NO_DEFINER): No definer attribute for trigger '%-.192s'.'%-.192s'. The trigger will be activated under the authorization of the invoker, which may have insufficient privileges. Please recreate the trigger.
MySQL error code 1455 (ER_OLD_FILE_FORMAT): '%-.192s' has an old format, you should re-create the '%s' object(s)
MySQL error code 1456 (ER_SP_RECURSION_LIMIT): Recursive limit %d (as set by the max_sp_recursion_depth variable) was exceeded for routine %.192s
MySQL error code 1457 (ER_SP_PROC_TABLE_CORRUPT): Failed to load routine %-.192s. The table mysql.proc is missing, corrupt, or contains bad data (internal code %d)
MySQL error code 1458 (ER_SP_WRONG_NAME): Incorrect routine name '%-.192s'
MySQL error code 1459 (ER_TABLE_NEEDS_UPGRADE): Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!
MySQL error code 1460 (ER_SP_NO_AGGREGATE): AGGREGATE is not supported for stored functions
MySQL error code 1461 (ER_MAX_PREPARED_STMT_COUNT_REACHED): Can't create more than max_prepared_stmt_count statements (current value: %lu)
MySQL error code 1462 (ER_VIEW_RECURSIVE): `%-.192s`.`%-.192s` contains view recursion
MySQL error code 1463 (ER_NON_GROUPING_FIELD_USED): Non-grouping field '%-.192s' is used in %-.64s clause
MySQL error code 1464 (ER_TABLE_CANT_HANDLE_SPKEYS): The used table type doesn't support SPATIAL indexes
MySQL error code 1465 (ER_NO_TRIGGERS_ON_SYSTEM_SCHEMA): Triggers can not be created on system tables
MySQL error code 1466 (ER_REMOVED_SPACES): Leading spaces are removed from name '%s'
MySQL error code 1467 (ER_AUTOINC_READ_FAILED): Failed to read auto-increment value from storage engine
MySQL error code 1468 (ER_USERNAME): user name
MySQL error code 1469 (ER_HOSTNAME): host name
MySQL error code 1470 (ER_WRONG_STRING_LENGTH): String '%-.70s' is too long for %s (should be no longer than %d)
MySQL error code 1471 (ER_NON_INSERTABLE_TABLE): The target table %-.100s of the %s is not insertable-into
MySQL error code 1472 (ER_ADMIN_WRONG_MRG_TABLE): Table '%-.64s' is differently defined or of non-MyISAM type or doesn't exist
MySQL error code 1473 (ER_TOO_HIGH_LEVEL_OF_NESTING_FOR_SELECT): Too high level of nesting for select
MySQL error code 1474 (ER_NAME_BECOMES_EMPTY): Name '%-.64s' has become ''
MySQL error code 1475 (ER_AMBIGUOUS_FIELD_TERM): First character of the FIELDS TERMINATED string is ambiguous; please use non-optional and non-empty FIELDS ENCLOSED BY
MySQL error code 1476 (ER_FOREIGN_SERVER_EXISTS): The foreign server, %s, you are trying to create already exists.
MySQL error code 1477 (ER_FOREIGN_SERVER_DOESNT_EXIST): The foreign server name you are trying to reference does not exist. Data source error:  %-.64s
MySQL error code 1478 (ER_ILLEGAL_HA_CREATE_OPTION): Table storage engine '%-.64s' does not support the create option '%.64s'
MySQL error code 1479 (ER_PARTITION_REQUIRES_VALUES_ERROR): Syntax error: %-.64s PARTITIONING requires definition of VALUES %-.64s for each partition
MySQL error code 1480 (ER_PARTITION_WRONG_VALUES_ERROR): Only %-.64s PARTITIONING can use VALUES %-.64s in partition definition
MySQL error code 1481 (ER_PARTITION_MAXVALUE_ERROR): MAXVALUE can only be used in last partition definition
MySQL error code 1482 (ER_PARTITION_SUBPARTITION_ERROR): Subpartitions can only be hash partitions and by key
MySQL error code 1483 (ER_PARTITION_SUBPART_MIX_ERROR): Must define subpartitions on all partitions if on one partition
MySQL error code 1484 (ER_PARTITION_WRONG_NO_PART_ERROR): Wrong number of partitions defined, mismatch with previous setting
MySQL error code 1485 (ER_PARTITION_WRONG_NO_SUBPART_ERROR): Wrong number of subpartitions defined, mismatch with previous setting
MySQL error code 1486 (ER_WRONG_EXPR_IN_PARTITION_FUNC_ERROR): Constant, random or timezone-dependent expressions in (sub)partitioning function are not allowed
MySQL error code 1487 (ER_NO_CONST_EXPR_IN_RANGE_OR_LIST_ERROR): Expression in RANGE/LIST VALUES must be constant
MySQL error code 1488 (ER_FIELD_NOT_FOUND_PART_ERROR): Field in list of fields for partition function not found in table
MySQL error code 1489 (ER_LIST_OF_FIELDS_ONLY_IN_HASH_ERROR): List of fields is only allowed in KEY partitions
MySQL error code 1490 (ER_INCONSISTENT_PARTITION_INFO_ERROR): The partition info in the frm file is not consistent with what can be written into the frm file
MySQL error code 1491 (ER_PARTITION_FUNC_NOT_ALLOWED_ERROR): The %-.192s function returns the wrong type
MySQL error code 1492 (ER_PARTITIONS_MUST_BE_DEFINED_ERROR): For %-.64s partitions each partition must be defined
MySQL error code 1493 (ER_RANGE_NOT_INCREASING_ERROR): VALUES LESS THAN value must be strictly increasing for each partition
MySQL error code 1494 (ER_INCONSISTENT_TYPE_OF_FUNCTIONS_ERROR): VALUES value must be of same type as partition function
MySQL error code 1495 (ER_MULTIPLE_DEF_CONST_IN_LIST_PART_ERROR): Multiple definition of same constant in list partitioning
MySQL error code 1496 (ER_PARTITION_ENTRY_ERROR): Partitioning can not be used stand-alone in query
MySQL error code 1497 (ER_MIX_HANDLER_ERROR): The mix of handlers in the partitions is not allowed in this version of MySQL
MySQL error code 1498 (ER_PARTITION_NOT_DEFINED_ERROR): For the partitioned engine it is necessary to define all %-.64s
MySQL error code 1499 (ER_TOO_MANY_PARTITIONS_ERROR): Too many partitions (including subpartitions) were defined
MySQL error code 1500 (ER_SUBPARTITION_ERROR): It is only possible to mix RANGE/LIST partitioning with HASH/KEY partitioning for subpartitioning
MySQL error code 1501 (ER_CANT_CREATE_HANDLER_FILE): Failed to create specific handler file
MySQL error code 1502 (ER_BLOB_FIELD_IN_PART_FUNC_ERROR): A BLOB field is not allowed in partition function
MySQL error code 1503 (ER_UNIQUE_KEY_NEED_ALL_FIELDS_IN_PF): A %-.192s must include all columns in the table's partitioning function
MySQL error code 1504 (ER_NO_PARTS_ERROR): Number of %-.64s = 0 is not an allowed value
MySQL error code 1505 (ER_PARTITION_MGMT_ON_NONPARTITIONED): Partition management on a not partitioned table is not possible
MySQL error code 1506 (ER_FOREIGN_KEY_ON_PARTITIONED): Foreign keys are not yet supported in conjunction with partitioning
MySQL error code 1507 (ER_DROP_PARTITION_NON_EXISTENT): Error in list of partitions to %-.64s
MySQL error code 1508 (ER_DROP_LAST_PARTITION): Cannot remove all partitions, use DROP TABLE instead
MySQL error code 1509 (ER_COALESCE_ONLY_ON_HASH_PARTITION): COALESCE PARTITION can only be used on HASH/KEY partitions
MySQL error code 1510 (ER_REORG_HASH_ONLY_ON_SAME_NO): REORGANIZE PARTITION can only be used to reorganize partitions not to change their numbers
MySQL error code 1511 (ER_REORG_NO_PARAM_ERROR): REORGANIZE PARTITION without parameters can only be used on auto-partitioned tables using HASH PARTITIONs
MySQL error code 1512 (ER_ONLY_ON_RANGE_LIST_PARTITION): %-.64s PARTITION can only be used on RANGE/LIST partitions
MySQL error code 1513 (ER_ADD_PARTITION_SUBPART_ERROR): Trying to Add partition(s) with wrong number of subpartitions
MySQL error code 1514 (ER_ADD_PARTITION_NO_NEW_PARTITION): At least one partition must be added
MySQL error code 1515 (ER_COALESCE_PARTITION_NO_PARTITION): At least one partition must be coalesced
MySQL error code 1516 (ER_REORG_PARTITION_NOT_EXIST): More partitions to reorganize than there are partitions
MySQL error code 1517 (ER_SAME_NAME_PARTITION): Duplicate partition name %-.192s
MySQL error code 1518 (ER_NO_BINLOG_ERROR): It is not allowed to shut off binlog on this command
MySQL error code 1519 (ER_CONSECUTIVE_REORG_PARTITIONS): When reorganizing a set of partitions they must be in consecutive order
MySQL error code 1520 (ER_REORG_OUTSIDE_RANGE): Reorganize of range partitions cannot change total ranges except for last partition where it can extend the range
MySQL error code 1521 (ER_PARTITION_FUNCTION_FAILURE): Partition function not supported in this version for this handler
MySQL error code 1522 (ER_PART_STATE_ERROR): Partition state cannot be defined from CREATE/ALTER TABLE
MySQL error code 1523 (ER_LIMITED_PART_RANGE): The %-.64s handler only supports 32 bit integers in VALUES
MySQL error code 1524 (ER_PLUGIN_IS_NOT_LOADED): Plugin '%-.192s' is not loaded
MySQL error code 1525 (ER_WRONG_VALUE): Incorrect %-.32s value: '%-.128s'
MySQL error code 1526 (ER_NO_PARTITION_FOR_GIVEN_VALUE): Table has no partition for value %-.64s
MySQL error code 1527 (ER_FILEGROUP_OPTION_ONLY_ONCE): It is not allowed to specify %s more than once
MySQL error code 1528 (ER_CREATE_FILEGROUP_FAILED): Failed to create %s
MySQL error code 1529 (ER_DROP_FILEGROUP_FAILED): Failed to drop %s
MySQL error code 1530 (ER_TABLESPACE_AUTO_EXTEND_ERROR): The handler doesn't support autoextend of tablespaces
MySQL error code 1531 (ER_WRONG_SIZE_NUMBER): A size parameter was incorrectly specified, either number or on the form 10M
MySQL error code 1532 (ER_SIZE_OVERFLOW_ERROR): The size number was correct but we don't allow the digit part to be more than 2 billion
MySQL error code 1533 (ER_ALTER_FILEGROUP_FAILED): Failed to alter: %s
MySQL error code 1534 (ER_BINLOG_ROW_LOGGING_FAILED): Writing one row to the row-based binary log failed
MySQL error code 1535 (ER_BINLOG_ROW_WRONG_TABLE_DEF): Table definition on master and slave does not match: %s
MySQL error code 1536 (ER_BINLOG_ROW_RBR_TO_SBR): Slave running with --log-slave-updates must use row-based binary logging to be able to replicate row-based binary log events
MySQL error code 1537 (ER_EVENT_ALREADY_EXISTS): Event '%-.192s' already exists
MySQL error code 1538 (ER_EVENT_STORE_FAILED): Failed to store event %s. Error code %d from storage engine.
MySQL error code 1539 (ER_EVENT_DOES_NOT_EXIST): Unknown event '%-.192s'
MySQL error code 1540 (ER_EVENT_CANT_ALTER): Failed to alter event '%-.192s'
MySQL error code 1541 (ER_EVENT_DROP_FAILED): Failed to drop %s
MySQL error code 1542 (ER_EVENT_INTERVAL_NOT_POSITIVE_OR_TOO_BIG): INTERVAL is either not positive or too big
MySQL error code 1543 (ER_EVENT_ENDS_BEFORE_STARTS): ENDS is either invalid or before STARTS
MySQL error code 1544 (ER_EVENT_EXEC_TIME_IN_THE_PAST): Event execution time is in the past. Event has been disabled
MySQL error code 1545 (ER_EVENT_OPEN_TABLE_FAILED): Failed to open mysql.event
MySQL error code 1546 (ER_EVENT_NEITHER_M_EXPR_NOR_M_AT): No datetime expression provided
MySQL error code 1547 (ER_OBSOLETE_COL_COUNT_DOESNT_MATCH_CORRUPTED): Column count of mysql.%s is wrong. Expected %d, found %d. The table is probably corrupted
MySQL error code 1548 (ER_OBSOLETE_CANNOT_LOAD_FROM_TABLE): Cannot load from mysql.%s. The table is probably corrupted
MySQL error code 1549 (ER_EVENT_CANNOT_DELETE): Failed to delete the event from mysql.event
MySQL error code 1550 (ER_EVENT_COMPILE_ERROR): Error during compilation of event's body
MySQL error code 1551 (ER_EVENT_SAME_NAME): Same old and new event name
MySQL error code 1552 (ER_EVENT_DATA_TOO_LONG): Data for column '%s' too long
MySQL error code 1553 (ER_DROP_INDEX_FK): Cannot drop index '%-.192s': needed in a foreign key constraint
MySQL error code 1554 (ER_WARN_DEPRECATED_SYNTAX_WITH_VER): The syntax '%s' is deprecated and will be removed in MySQL %s. Please use %s instead
MySQL error code 1555 (ER_CANT_WRITE_LOCK_LOG_TABLE): You can't write-lock a log table. Only read access is possible
MySQL error code 1556 (ER_CANT_LOCK_LOG_TABLE): You can't use locks with log tables.
MySQL error code 1557 (ER_FOREIGN_DUPLICATE_KEY_OLD_UNUSED): Upholding foreign key constraints for table '%.192s', entry '%-.192s', key %d would lead to a duplicate entry
MySQL error code 1558 (ER_COL_COUNT_DOESNT_MATCH_PLEASE_UPDATE): Column count of mysql.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please use mysql_upgrade to fix this error.
MySQL error code 1559 (ER_TEMP_TABLE_PREVENTS_SWITCH_OUT_OF_RBR): Cannot switch out of the row-based binary log format when the session has open temporary tables
MySQL error code 1560 (ER_STORED_FUNCTION_PREVENTS_SWITCH_BINLOG_FORMAT): Cannot change the binary logging format inside a stored function or trigger
MySQL error code 1561 (ER_NDB_CANT_SWITCH_BINLOG_FORMAT): The NDB cluster engine does not support changing the binlog format on the fly yet
MySQL error code 1562 (ER_PARTITION_NO_TEMPORARY): Cannot create temporary table with partitions
MySQL error code 1563 (ER_PARTITION_CONST_DOMAIN_ERROR): Partition constant is out of partition function domain
MySQL error code 1564 (ER_PARTITION_FUNCTION_IS_NOT_ALLOWED): This partition function is not allowed
MySQL error code 1565 (ER_DDL_LOG_ERROR): Error in DDL log
MySQL error code 1566 (ER_NULL_IN_VALUES_LESS_THAN): Not allowed to use NULL value in VALUES LESS THAN
MySQL error code 1567 (ER_WRONG_PARTITION_NAME): Incorrect partition name
MySQL error code 1568 (ER_CANT_CHANGE_TX_CHARACTERISTICS): Transaction characteristics can't be changed while a transaction is in progress
MySQL error code 1569 (ER_DUP_ENTRY_AUTOINCREMENT_CASE): ALTER TABLE causes auto_increment resequencing, resulting in duplicate entry '%-.192s' for key '%-.192s'
MySQL error code 1570 (ER_EVENT_MODIFY_QUEUE_ERROR): Internal scheduler error %d
MySQL error code 1571 (ER_EVENT_SET_VAR_ERROR): Error during starting/stopping of the scheduler. Error code %u
MySQL error code 1572 (ER_PARTITION_MERGE_ERROR): Engine cannot be used in partitioned tables
MySQL error code 1573 (ER_CANT_ACTIVATE_LOG): Cannot activate '%-.64s' log
MySQL error code 1574 (ER_RBR_NOT_AVAILABLE): The server was not built with row-based replication
MySQL error code 1575 (ER_BASE64_DECODE_ERROR): Decoding of base64 string failed
MySQL error code 1576 (ER_EVENT_RECURSION_FORBIDDEN): Recursion of EVENT DDL statements is forbidden when body is present
MySQL error code 1577 (ER_EVENTS_DB_ERROR): Cannot proceed because system tables used by Event Scheduler were found damaged at server start
MySQL error code 1578 (ER_ONLY_INTEGERS_ALLOWED): Only integers allowed as number here
MySQL error code 1579 (ER_UNSUPORTED_LOG_ENGINE): This storage engine cannot be used for log tables"
MySQL error code 1580 (ER_BAD_LOG_STATEMENT): You cannot '%s' a log table if logging is enabled
MySQL error code 1581 (ER_CANT_RENAME_LOG_TABLE): Cannot rename '%s'. When logging enabled, rename to/from log table must rename two tables: the log table to an archive table and another table back to '%s'
MySQL error code 1582 (ER_WRONG_PARAMCOUNT_TO_NATIVE_FCT): Incorrect parameter count in the call to native function '%-.192s'
MySQL error code 1583 (ER_WRONG_PARAMETERS_TO_NATIVE_FCT): Incorrect parameters in the call to native function '%-.192s'
MySQL error code 1584 (ER_WRONG_PARAMETERS_TO_STORED_FCT): Incorrect parameters in the call to stored function %-.192s
MySQL error code 1585 (ER_NATIVE_FCT_NAME_COLLISION): This function '%-.192s' has the same name as a native function
MySQL error code 1586 (ER_DUP_ENTRY_WITH_KEY_NAME): Duplicate entry '%-.64s' for key '%-.192s'
MySQL error code 1587 (ER_BINLOG_PURGE_EMFILE): Too many files opened, please execute the command again
MySQL error code 1588 (ER_EVENT_CANNOT_CREATE_IN_THE_PAST): Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation.
MySQL error code 1589 (ER_EVENT_CANNOT_ALTER_IN_THE_PAST): Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was not changed. Specify a time in the future.
MySQL error code 1590 (ER_SLAVE_INCIDENT): The incident %s occured on the master. Message: %s
MySQL error code 1591 (ER_NO_PARTITION_FOR_GIVEN_VALUE_SILENT): Table has no partition for some existing values
MySQL error code 1592 (ER_BINLOG_UNSAFE_STATEMENT): Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. %s
MySQL error code 1593 (ER_SLAVE_FATAL_ERROR): Fatal error: %s
MySQL error code 1594 (ER_SLAVE_RELAY_LOG_READ_FAILURE): Relay log read failure: %s
MySQL error code 1595 (ER_SLAVE_RELAY_LOG_WRITE_FAILURE): Relay log write failure: %s
MySQL error code 1596 (ER_SLAVE_CREATE_EVENT_FAILURE): Failed to create %s
MySQL error code 1597 (ER_SLAVE_MASTER_COM_FAILURE): Master command %s failed: %s
MySQL error code 1598 (ER_BINLOG_LOGGING_IMPOSSIBLE): Binary logging not possible. Message: %s
MySQL error code 1599 (ER_VIEW_NO_CREATION_CTX): View `%-.64s`.`%-.64s` has no creation context
MySQL error code 1600 (ER_VIEW_INVALID_CREATION_CTX): Creation context of view `%-.64s`.`%-.64s' is invalid
MySQL error code 1601 (ER_SR_INVALID_CREATION_CTX): Creation context of stored routine `%-.64s`.`%-.64s` is invalid
MySQL error code 1602 (ER_TRG_CORRUPTED_FILE): Corrupted TRG file for table `%-.64s`.`%-.64s`
MySQL error code 1603 (ER_TRG_NO_CREATION_CTX): Triggers for table `%-.64s`.`%-.64s` have no creation context
MySQL error code 1604 (ER_TRG_INVALID_CREATION_CTX): Trigger creation context of table `%-.64s`.`%-.64s` is invalid
MySQL error code 1605 (ER_EVENT_INVALID_CREATION_CTX): Creation context of event `%-.64s`.`%-.64s` is invalid
MySQL error code 1606 (ER_TRG_CANT_OPEN_TABLE): Cannot open table for trigger `%-.64s`.`%-.64s`
MySQL error code 1607 (ER_CANT_CREATE_SROUTINE): Cannot create stored routine `%-.64s`. Check warnings
MySQL error code 1608 (ER_NEVER_USED): Ambiguous slave modes combination. %s
MySQL error code 1609 (ER_NO_FORMAT_DESCRIPTION_EVENT_BEFORE_BINLOG_STATEMENT): The BINLOG statement of type `%s` was not preceded by a format description BINLOG statement.
MySQL error code 1610 (ER_SLAVE_CORRUPT_EVENT): Corrupted replication event was detected
MySQL error code 1611 (ER_LOAD_DATA_INVALID_COLUMN_UNUSED): Invalid column reference (%-.64s) in LOAD DATA
MySQL error code 1612 (ER_LOG_PURGE_NO_FILE): Being purged log %s was not found
MySQL error code 1613 (ER_XA_RBTIMEOUT): XA_RBTIMEOUT: Transaction branch was rolled back: took too long
MySQL error code 1614 (ER_XA_RBDEADLOCK): XA_RBDEADLOCK: Transaction branch was rolled back: deadlock was detected
MySQL error code 1615 (ER_NEED_REPREPARE): Prepared statement needs to be re-prepared
MySQL error code 1616 (ER_DELAYED_NOT_SUPPORTED): DELAYED option not supported for table '%-.192s'
MySQL error code 1617 (WARN_NO_MASTER_INFO): The master info structure does not exist
MySQL error code 1618 (WARN_OPTION_IGNORED): <%-.64s> option ignored
MySQL error code 1619 (ER_PLUGIN_DELETE_BUILTIN): Built-in plugins cannot be deleted
MySQL error code 1620 (WARN_PLUGIN_BUSY): Plugin is busy and will be uninstalled on shutdown
MySQL error code 1621 (ER_VARIABLE_IS_READONLY): %s variable '%s' is read-only. Use SET %s to assign the value
MySQL error code 1622 (ER_WARN_ENGINE_TRANSACTION_ROLLBACK): Storage engine %s does not support rollback for this statement. Transaction rolled back and must be restarted
MySQL error code 1623 (ER_SLAVE_HEARTBEAT_FAILURE): Unexpected master's heartbeat data: %s
MySQL error code 1624 (ER_SLAVE_HEARTBEAT_VALUE_OUT_OF_RANGE): The requested value for the heartbeat period is either negative or exceeds the maximum allowed (%s seconds).
MySQL error code 1625 (ER_NDB_REPLICATION_SCHEMA_ERROR): Bad schema for mysql.ndb_replication table. Message: %-.64s
MySQL error code 1626 (ER_CONFLICT_FN_PARSE_ERROR): Error in parsing conflict function. Message: %-.64s
MySQL error code 1627 (ER_EXCEPTIONS_WRITE_ERROR): Write to exceptions table failed. Message: %-.128s"
MySQL error code 1628 (ER_TOO_LONG_TABLE_COMMENT): Comment for table '%-.64s' is too long (max = %lu)
MySQL error code 1629 (ER_TOO_LONG_FIELD_COMMENT): Comment for field '%-.64s' is too long (max = %lu)
MySQL error code 1630 (ER_FUNC_INEXISTENT_NAME_COLLISION): FUNCTION %s does not exist. Check the 'Function Name Parsing and Resolution' section in the Reference Manual
MySQL error code 1631 (ER_DATABASE_NAME): Database
MySQL error code 1632 (ER_TABLE_NAME): Table
MySQL error code 1633 (ER_PARTITION_NAME): Partition
MySQL error code 1634 (ER_SUBPARTITION_NAME): Subpartition
MySQL error code 1635 (ER_TEMPORARY_NAME): Temporary
MySQL error code 1636 (ER_RENAMED_NAME): Renamed
MySQL error code 1637 (ER_TOO_MANY_CONCURRENT_TRXS): Too many active concurrent transactions
MySQL error code 1638 (WARN_NON_ASCII_SEPARATOR_NOT_IMPLEMENTED): Non-ASCII separator arguments are not fully supported
MySQL error code 1639 (ER_DEBUG_SYNC_TIMEOUT): debug sync point wait timed out
MySQL error code 1640 (ER_DEBUG_SYNC_HIT_LIMIT): debug sync point hit limit reached
MySQL error code 1641 (ER_DUP_SIGNAL_SET): Duplicate condition information item '%s'
MySQL error code 1642 (ER_SIGNAL_WARN): Unhandled user-defined warning condition
MySQL error code 1643 (ER_SIGNAL_NOT_FOUND): Unhandled user-defined not found condition
MySQL error code 1644 (ER_SIGNAL_EXCEPTION): Unhandled user-defined exception condition
MySQL error code 1645 (ER_RESIGNAL_WITHOUT_ACTIVE_HANDLER): RESIGNAL when handler not active
MySQL error code 1646 (ER_SIGNAL_BAD_CONDITION_TYPE): SIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATE
MySQL error code 1647 (WARN_COND_ITEM_TRUNCATED): Data truncated for condition item '%s'
MySQL error code 1648 (ER_COND_ITEM_TOO_LONG): Data too long for condition item '%s'
MySQL error code 1649 (ER_UNKNOWN_LOCALE): Unknown locale: '%-.64s'
MySQL error code 1650 (ER_SLAVE_IGNORE_SERVER_IDS): The requested server id %d clashes with the slave startup option --replicate-same-server-id
MySQL error code 1651 (ER_QUERY_CACHE_DISABLED): Query cache is disabled; restart the server with query_cache_type=1 to enable it
MySQL error code 1652 (ER_SAME_NAME_PARTITION_FIELD): Duplicate partition field name '%-.192s'
MySQL error code 1653 (ER_PARTITION_COLUMN_LIST_ERROR): Inconsistency in usage of column lists for partitioning
MySQL error code 1654 (ER_WRONG_TYPE_COLUMN_VALUE_ERROR): Partition column values of incorrect type
MySQL error code 1655 (ER_TOO_MANY_PARTITION_FUNC_FIELDS_ERROR): Too many fields in '%-.192s'
MySQL error code 1656 (ER_MAXVALUE_IN_VALUES_IN): Cannot use MAXVALUE as value in VALUES IN
MySQL error code 1657 (ER_TOO_MANY_VALUES_ERROR): Cannot have more than one value for this type of %-.64s partitioning
MySQL error code 1658 (ER_ROW_SINGLE_PARTITION_FIELD_ERROR): Row expressions in VALUES IN only allowed for multi-field column partitioning
MySQL error code 1659 (ER_FIELD_TYPE_NOT_ALLOWED_AS_PARTITION_FIELD): Field '%-.192s' is of a not allowed type for this type of partitioning
MySQL error code 1660 (ER_PARTITION_FIELDS_TOO_LONG): The total length of the partitioning fields is too large
MySQL error code 1661 (ER_BINLOG_ROW_ENGINE_AND_STMT_ENGINE): Cannot execute statement: impossible to write to binary log since both row-incapable engines and statement-incapable engines are involved.
MySQL error code 1662 (ER_BINLOG_ROW_MODE_AND_STMT_ENGINE): Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = ROW and at least one table uses a storage engine limited to statement-based logging.
MySQL error code 1663 (ER_BINLOG_UNSAFE_AND_STMT_ENGINE): Cannot execute statement: impossible to write to binary log since statement is unsafe, storage engine is limited to statement-based logging, and BINLOG_FORMAT = MIXED. %s
MySQL error code 1664 (ER_BINLOG_ROW_INJECTION_AND_STMT_ENGINE): Cannot execute statement: impossible to write to binary log since statement is in row format and at least one table uses a storage engine limited to statement-based logging.
MySQL error code 1665 (ER_BINLOG_STMT_MODE_AND_ROW_ENGINE): Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging.%s
MySQL error code 1666 (ER_BINLOG_ROW_INJECTION_AND_STMT_MODE): Cannot execute statement: impossible to write to binary log since statement is in row format and BINLOG_FORMAT = STATEMENT.
MySQL error code 1667 (ER_BINLOG_MULTIPLE_ENGINES_AND_SELF_LOGGING_ENGINE): Cannot execute statement: impossible to write to binary log since more than one engine is involved and at least one engine is self-logging.
MySQL error code 1668 (ER_BINLOG_UNSAFE_LIMIT): The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted.
MySQL error code 1669 (ER_UNUSED4): The statement is unsafe because it uses INSERT DELAYED. This is unsafe because the times when rows are inserted cannot be predicted.
MySQL error code 1670 (ER_BINLOG_UNSAFE_SYSTEM_TABLE): The statement is unsafe because it uses the general log, slow query log, or performance_schema table(s). This is unsafe because system tables may differ on slaves.
MySQL error code 1671 (ER_BINLOG_UNSAFE_AUTOINC_COLUMNS): Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly.
MySQL error code 1672 (ER_BINLOG_UNSAFE_UDF): Statement is unsafe because it uses a UDF which may not return the same value on the slave.
MySQL error code 1673 (ER_BINLOG_UNSAFE_SYSTEM_VARIABLE): Statement is unsafe because it uses a system variable that may have a different value on the slave.
MySQL error code 1674 (ER_BINLOG_UNSAFE_SYSTEM_FUNCTION): Statement is unsafe because it uses a system function that may return a different value on the slave.
MySQL error code 1675 (ER_BINLOG_UNSAFE_NONTRANS_AFTER_TRANS): Statement is unsafe because it accesses a non-transactional table after accessing a transactional table within the same transaction.
MySQL error code 1676 (ER_MESSAGE_AND_STATEMENT): %s Statement: %s
MySQL error code 1677 (ER_SLAVE_CONVERSION_FAILED): Column %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'
MySQL error code 1678 (ER_SLAVE_CANT_CREATE_CONVERSION): Can't create conversion table for table '%-.192s.%-.192s'
MySQL error code 1679 (ER_INSIDE_TRANSACTION_PREVENTS_SWITCH_BINLOG_FORMAT): Cannot modify @@session.binlog_format inside a transaction
MySQL error code 1680 (ER_PATH_LENGTH): The path specified for %.64s is too long.
MySQL error code 1681 (ER_WARN_DEPRECATED_SYNTAX_NO_REPLACEMENT): '%s' is deprecated and will be removed in a future release.
MySQL error code 1682 (ER_WRONG_NATIVE_TABLE_STRUCTURE): Native table '%-.64s'.'%-.64s' has the wrong structure
MySQL error code 1683 (ER_WRONG_PERFSCHEMA_USAGE): Invalid performance_schema usage.
MySQL error code 1684 (ER_WARN_I_S_SKIPPED_TABLE): Table '%s'.'%s' was skipped since its definition is being modified by concurrent DDL statement
MySQL error code 1685 (ER_INSIDE_TRANSACTION_PREVENTS_SWITCH_BINLOG_DIRECT): Cannot modify @@session.binlog_direct_non_transactional_updates inside a transaction
MySQL error code 1686 (ER_STORED_FUNCTION_PREVENTS_SWITCH_BINLOG_DIRECT): Cannot change the binlog direct flag inside a stored function or trigger
MySQL error code 1687 (ER_SPATIAL_MUST_HAVE_GEOM_COL): A SPATIAL index may only contain a geometrical type column
MySQL error code 1688 (ER_TOO_LONG_INDEX_COMMENT): Comment for index '%-.64s' is too long (max = %lu)
MySQL error code 1689 (ER_LOCK_ABORTED): Wait on a lock was aborted due to a pending exclusive lock
MySQL error code 1690 (ER_DATA_OUT_OF_RANGE): %s value is out of range in '%s'
MySQL error code 1691 (ER_WRONG_SPVAR_TYPE_IN_LIMIT): A variable of a non-integer based type in LIMIT clause
MySQL error code 1692 (ER_BINLOG_UNSAFE_MULTIPLE_ENGINES_AND_SELF_LOGGING_ENGINE): Mixing self-logging and non-self-logging engines in a statement is unsafe.
MySQL error code 1693 (ER_BINLOG_UNSAFE_MIXED_STATEMENT): Statement accesses nontransactional table as well as transactional or temporary table, and writes to any of them.
MySQL error code 1694 (ER_INSIDE_TRANSACTION_PREVENTS_SWITCH_SQL_LOG_BIN): Cannot modify @@session.sql_log_bin inside a transaction
MySQL error code 1695 (ER_STORED_FUNCTION_PREVENTS_SWITCH_SQL_LOG_BIN): Cannot change the sql_log_bin inside a stored function or trigger
MySQL error code 1696 (ER_FAILED_READ_FROM_PAR_FILE): Failed to read from the .par file
MySQL error code 1697 (ER_VALUES_IS_NOT_INT_TYPE_ERROR): VALUES value for partition '%-.64s' must have type INT
MySQL error code 1698 (ER_ACCESS_DENIED_NO_PASSWORD_ERROR): Access denied for user '%-.48s'@'%-.64s'
MySQL error code 1699 (ER_SET_PASSWORD_AUTH_PLUGIN): SET PASSWORD has no significance for users authenticating via plugins
MySQL error code 1700 (ER_GRANT_PLUGIN_USER_EXISTS): GRANT with IDENTIFIED WITH is illegal because the user %-.*s already exists
MySQL error code 1701 (ER_TRUNCATE_ILLEGAL_FK): Cannot truncate a table referenced in a foreign key constraint (%.192s)
MySQL error code 1702 (ER_PLUGIN_IS_PERMANENT): Plugin '%s' is force_plus_permanent and can not be unloaded
MySQL error code 1703 (ER_SLAVE_HEARTBEAT_VALUE_OUT_OF_RANGE_MIN): The requested value for the heartbeat period is less than 1 millisecond. The value is reset to 0, meaning that heartbeating will effectively be disabled.
MySQL error code 1704 (ER_SLAVE_HEARTBEAT_VALUE_OUT_OF_RANGE_MAX): The requested value for the heartbeat period exceeds the value of `slave_net_timeout' seconds. A sensible value for the period should be less than the timeout.
MySQL error code 1705 (ER_STMT_CACHE_FULL): Multi-row statements required more than 'max_binlog_stmt_cache_size' bytes of storage; increase this mysqld variable and try again
MySQL error code 1706 (ER_MULTI_UPDATE_KEY_CONFLICT): Primary key/partition key update is not allowed since the table is updated both as '%-.192s' and '%-.192s'.
MySQL error code 1707 (ER_TABLE_NEEDS_REBUILD): Table rebuild required. Please do "ALTER TABLE `%-.64s` FORCE" or dump/reload to fix it!
MySQL error code 1708 (WARN_OPTION_BELOW_LIMIT): The value of '%s' should be no less than the value of '%s'
MySQL error code 1709 (ER_INDEX_COLUMN_TOO_LONG): Index column size too large. The maximum column size is %lu bytes.
MySQL error code 1710 (ER_ERROR_IN_TRIGGER_BODY): Trigger '%-.64s' has an error in its body: '%-.256s'
MySQL error code 1711 (ER_ERROR_IN_UNKNOWN_TRIGGER_BODY): Unknown trigger has an error in its body: '%-.256s'
MySQL error code 1712 (ER_INDEX_CORRUPT): Index %s is corrupted
MySQL error code 1713 (ER_UNDO_RECORD_TOO_BIG): Undo log record is too big.
MySQL error code 1714 (ER_BINLOG_UNSAFE_INSERT_IGNORE_SELECT): INSERT IGNORE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on master and the slave.
MySQL error code 1715 (ER_BINLOG_UNSAFE_INSERT_SELECT_UPDATE): INSERT... SELECT... ON DUPLICATE KEY UPDATE is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are updated. This order cannot be predicted and may differ on master and the slave.
MySQL error code 1716 (ER_BINLOG_UNSAFE_REPLACE_SELECT): REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave.
MySQL error code 1717 (ER_BINLOG_UNSAFE_CREATE_IGNORE_SELECT): CREATE... IGNORE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on master and the slave.
MySQL error code 1718 (ER_BINLOG_UNSAFE_CREATE_REPLACE_SELECT): CREATE... REPLACE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave.
MySQL error code 1719 (ER_BINLOG_UNSAFE_UPDATE_IGNORE): UPDATE IGNORE is unsafe because the order in which rows are updated determines which (if any) rows are ignored. This order cannot be predicted and may differ on master and the slave.
MySQL error code 1720 (ER_PLUGIN_NO_UNINSTALL): Plugin '%s' is marked as not dynamically uninstallable. You have to stop the server to uninstall it.
MySQL error code 1721 (ER_PLUGIN_NO_INSTALL): Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.
MySQL error code 1722 (ER_BINLOG_UNSAFE_WRITE_AUTOINC_SELECT): Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave.
MySQL error code 1723 (ER_BINLOG_UNSAFE_CREATE_SELECT_AUTOINC): CREATE TABLE... SELECT...  on a table with an auto-increment column is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are inserted. This order cannot be predicted and may differ on master and the slave.
MySQL error code 1724 (ER_BINLOG_UNSAFE_INSERT_TWO_KEYS): INSERT... ON DUPLICATE KEY UPDATE  on a table with more than one UNIQUE KEY is unsafe
MySQL error code 1725 (ER_TABLE_IN_FK_CHECK): Table is being used in foreign key check.
MySQL error code 1726 (ER_UNSUPPORTED_ENGINE): Storage engine '%s' does not support system tables. [%s.%s]
MySQL error code 1727 (ER_BINLOG_UNSAFE_AUTOINC_NOT_FIRST): INSERT into autoincrement field which is not the first part in the composed primary key is unsafe.
MySQL error code 1728 (ER_CANNOT_LOAD_FROM_TABLE_V2): Cannot load from %s.%s. The table is probably corrupted
MySQL error code 1729 (ER_MASTER_DELAY_VALUE_OUT_OF_RANGE): The requested value %s for the master delay exceeds the maximum %u
MySQL error code 1730 (ER_ONLY_FD_AND_RBR_EVENTS_ALLOWED_IN_BINLOG_STATEMENT): Only Format_description_log_event and row events are allowed in BINLOG statements (but %s was provided)
MySQL error code 1731 (ER_PARTITION_EXCHANGE_DIFFERENT_OPTION): Non matching attribute '%-.64s' between partition and table
MySQL error code 1732 (ER_PARTITION_EXCHANGE_PART_TABLE): Table to exchange with partition is partitioned: '%-.64s'
MySQL error code 1733 (ER_PARTITION_EXCHANGE_TEMP_TABLE): Table to exchange with partition is temporary: '%-.64s'
MySQL error code 1734 (ER_PARTITION_INSTEAD_OF_SUBPARTITION): Subpartitioned table, use subpartition instead of partition
MySQL error code 1735 (ER_UNKNOWN_PARTITION): Unknown partition '%-.64s' in table '%-.64s'
MySQL error code 1736 (ER_TABLES_DIFFERENT_METADATA): Tables have different definitions
MySQL error code 1737 (ER_ROW_DOES_NOT_MATCH_PARTITION): Found a row that does not match the partition
MySQL error code 1738 (ER_BINLOG_CACHE_SIZE_GREATER_THAN_MAX): Option binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.
MySQL error code 1739 (ER_WARN_INDEX_NOT_APPLICABLE): Cannot use %-.64s access on index '%-.64s' due to type or collation conversion on field '%-.64s'
MySQL error code 1740 (ER_PARTITION_EXCHANGE_FOREIGN_KEY): Table to exchange with partition has foreign key references: '%-.64s'
MySQL error code 1741 (ER_NO_SUCH_KEY_VALUE): Key value '%-.192s' was not found in table '%-.192s.%-.192s'
MySQL error code 1742 (ER_RPL_INFO_DATA_TOO_LONG): Data for column '%s' too long
MySQL error code 1743 (ER_NETWORK_READ_EVENT_CHECKSUM_FAILURE): Replication event checksum verification failed while reading from network.
MySQL error code 1744 (ER_BINLOG_READ_EVENT_CHECKSUM_FAILURE): Replication event checksum verification failed while reading from a log file.
MySQL error code 1745 (ER_BINLOG_STMT_CACHE_SIZE_GREATER_THAN_MAX): Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.
MySQL error code 1746 (ER_CANT_UPDATE_TABLE_IN_CREATE_TABLE_SELECT): Can't update table '%-.192s' while '%-.192s' is being created.
MySQL error code 1747 (ER_PARTITION_CLAUSE_ON_NONPARTITIONED): PARTITION () clause on non partitioned table
MySQL error code 1748 (ER_ROW_DOES_NOT_MATCH_GIVEN_PARTITION_SET): Found a row not matching the given partition set
MySQL error code 1749 (ER_NO_SUCH_PARTITION__UNUSED): partition '%-.64s' doesn't exist
MySQL error code 1750 (ER_CHANGE_RPL_INFO_REPOSITORY_FAILURE): Failure while changing the type of replication repository: %s.
MySQL error code 1751 (ER_WARNING_NOT_COMPLETE_ROLLBACK_WITH_CREATED_TEMP_TABLE): The creation of some temporary tables could not be rolled back.
MySQL error code 1752 (ER_WARNING_NOT_COMPLETE_ROLLBACK_WITH_DROPPED_TEMP_TABLE): Some temporary tables were dropped, but these operations could not be rolled back.
MySQL error code 1753 (ER_MTS_FEATURE_IS_NOT_SUPPORTED): %s is not supported in multi-threaded slave mode. %s
MySQL error code 1754 (ER_MTS_UPDATED_DBS_GREATER_MAX): The number of modified databases exceeds the maximum %d; the database names will not be included in the replication event metadata.
MySQL error code 1755 (ER_MTS_CANT_PARALLEL): Cannot execute the current event group in the parallel mode. Encountered event %s, relay-log name %s, position %s which prevents execution of this event group in parallel mode. Reason: %s.
MySQL error code 1756 (ER_MTS_INCONSISTENT_DATA): %s
MySQL error code 1757 (ER_FULLTEXT_NOT_SUPPORTED_WITH_PARTITIONING): FULLTEXT index is not supported for partitioned tables.
MySQL error code 1758 (ER_DA_INVALID_CONDITION_NUMBER): Invalid condition number
MySQL error code 1759 (ER_INSECURE_PLAIN_TEXT): Sending passwords in plain text without SSL/TLS is extremely insecure.
MySQL error code 1760 (ER_INSECURE_CHANGE_MASTER): Storing MySQL user name or password information in the master info repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START SLAVE; see the 'START SLAVE Syntax' in the MySQL Manual for more information.
MySQL error code 1761 (ER_FOREIGN_DUPLICATE_KEY_WITH_CHILD_INFO): Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in table '%.192s', key '%.192s'
MySQL error code 1762 (ER_FOREIGN_DUPLICATE_KEY_WITHOUT_CHILD_INFO): Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in a child table
MySQL error code 1763 (ER_SQLTHREAD_WITH_SECURE_SLAVE): Setting authentication options is not possible when only the Slave SQL Thread is being started.
MySQL error code 1764 (ER_TABLE_HAS_NO_FT): The table does not have FULLTEXT index to support this query
MySQL error code 1765 (ER_VARIABLE_NOT_SETTABLE_IN_SF_OR_TRIGGER): The system variable %.200s cannot be set in stored functions or triggers.
MySQL error code 1766 (ER_VARIABLE_NOT_SETTABLE_IN_TRANSACTION): The system variable %.200s cannot be set when there is an ongoing transaction.
MySQL error code 1767 (ER_GTID_NEXT_IS_NOT_IN_GTID_NEXT_LIST): The system variable @@SESSION.GTID_NEXT has the value %.200s, which is not listed in @@SESSION.GTID_NEXT_LIST.
MySQL error code 1768 (ER_CANT_CHANGE_GTID_NEXT_IN_TRANSACTION): The system variable @@SESSION.GTID_NEXT cannot change inside a transaction.
MySQL error code 1769 (ER_SET_STATEMENT_CANNOT_INVOKE_FUNCTION): The statement 'SET %.200s' cannot invoke a stored function.
MySQL error code 1770 (ER_GTID_NEXT_CANT_BE_AUTOMATIC_IF_GTID_NEXT_LIST_IS_NON_NULL): The system variable @@SESSION.GTID_NEXT cannot be 'AUTOMATIC' when @@SESSION.GTID_NEXT_LIST is non-NULL.
MySQL error code 1771 (ER_SKIPPING_LOGGED_TRANSACTION): Skipping transaction %.200s because it has already been executed and logged.
MySQL error code 1772 (ER_MALFORMED_GTID_SET_SPECIFICATION): Malformed GTID set specification '%.200s'.
MySQL error code 1773 (ER_MALFORMED_GTID_SET_ENCODING): Malformed GTID set encoding.
MySQL error code 1774 (ER_MALFORMED_GTID_SPECIFICATION): Malformed GTID specification '%.200s'.
MySQL error code 1775 (ER_GNO_EXHAUSTED): Impossible to generate Global Transaction Identifier: the integer component reached the maximal value. Restart the server with a new server_uuid.
MySQL error code 1776 (ER_BAD_SLAVE_AUTO_POSITION): Parameters MASTER_LOG_FILE, MASTER_LOG_POS, RELAY_LOG_FILE and RELAY_LOG_POS cannot be set when MASTER_AUTO_POSITION is active.
MySQL error code 1777 (ER_AUTO_POSITION_REQUIRES_GTID_MODE_NOT_OFF): CHANGE MASTER TO MASTER_AUTO_POSITION = 1 cannot be executed because @@GLOBAL.GTID_MODE = OFF.
MySQL error code 1778 (ER_CANT_DO_IMPLICIT_COMMIT_IN_TRX_WHEN_GTID_NEXT_IS_SET): Cannot execute statements with implicit commit inside a transaction when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.
MySQL error code 1779 (ER_GTID_MODE_ON_REQUIRES_ENFORCE_GTID_CONSISTENCY_ON): GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.
MySQL error code 1780 (ER_GTID_MODE_REQUIRES_BINLOG): @@GLOBAL.GTID_MODE = ON or ON_PERMISSIVE or OFF_PERMISSIVE requires --log-bin and --log-slave-updates.
MySQL error code 1781 (ER_CANT_SET_GTID_NEXT_TO_GTID_WHEN_GTID_MODE_IS_OFF): @@SESSION.GTID_NEXT cannot be set to UUID:NUMBER when @@GLOBAL.GTID_MODE = OFF.
MySQL error code 1782 (ER_CANT_SET_GTID_NEXT_TO_ANONYMOUS_WHEN_GTID_MODE_IS_ON): @@SESSION.GTID_NEXT cannot be set to ANONYMOUS when @@GLOBAL.GTID_MODE = ON.
MySQL error code 1783 (ER_CANT_SET_GTID_NEXT_LIST_TO_NON_NULL_WHEN_GTID_MODE_IS_OFF): @@SESSION.GTID_NEXT_LIST cannot be set to a non-NULL value when @@GLOBAL.GTID_MODE = OFF.
MySQL error code 1784 (ER_FOUND_GTID_EVENT_WHEN_GTID_MODE_IS_OFF__UNUSED): Found a Gtid_log_event when @@GLOBAL.GTID_MODE = OFF.
MySQL error code 1785 (ER_GTID_UNSAFE_NON_TRANSACTIONAL_TABLE): Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.
MySQL error code 1786 (ER_GTID_UNSAFE_CREATE_SELECT): Statement violates GTID consistency: CREATE TABLE ... SELECT.
MySQL error code 1787 (ER_GTID_UNSAFE_CREATE_DROP_TEMPORARY_TABLE_IN_TRANSACTION): Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.
MySQL error code 1788 (ER_GTID_MODE_CAN_ONLY_CHANGE_ONE_STEP_AT_A_TIME): The value of @@GLOBAL.GTID_MODE can only be changed one step at a time: OFF <-> OFF_PERMISSIVE <-> ON_PERMISSIVE <-> ON. Also note that this value must be stepped up or down simultaneously on all servers. See the Manual for instructions.
MySQL error code 1789 (ER_MASTER_HAS_PURGED_REQUIRED_GTIDS): The slave is connecting using CHANGE MASTER TO MASTER_AUTO_POSITION = 1, but the master has purged binary logs containing GTIDs that the slave requires.
MySQL error code 1790 (ER_CANT_SET_GTID_NEXT_WHEN_OWNING_GTID): @@SESSION.GTID_NEXT cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.
MySQL error code 1791 (ER_UNKNOWN_EXPLAIN_FORMAT): Unknown EXPLAIN format name: '%s'
MySQL error code 1792 (ER_CANT_EXECUTE_IN_READ_ONLY_TRANSACTION): Cannot execute statement in a READ ONLY transaction.
MySQL error code 1793 (ER_TOO_LONG_TABLE_PARTITION_COMMENT): Comment for table partition '%-.64s' is too long (max = %lu)
MySQL error code 1794 (ER_SLAVE_CONFIGURATION): Slave is not configured or failed to initialize properly. You must at least set --server-id to enable either a master or a slave. Additional error messages can be found in the MySQL error log.
MySQL error code 1795 (ER_INNODB_FT_LIMIT): InnoDB presently supports one FULLTEXT index creation at a time
MySQL error code 1796 (ER_INNODB_NO_FT_TEMP_TABLE): Cannot create FULLTEXT index on temporary InnoDB table
MySQL error code 1797 (ER_INNODB_FT_WRONG_DOCID_COLUMN): Column '%-.192s' is of wrong type for an InnoDB FULLTEXT index
MySQL error code 1798 (ER_INNODB_FT_WRONG_DOCID_INDEX): Index '%-.192s' is of wrong type for an InnoDB FULLTEXT index
MySQL error code 1799 (ER_INNODB_ONLINE_LOG_TOO_BIG): Creating index '%-.192s' required more than 'innodb_online_alter_log_max_size' bytes of modification log. Please try again.
MySQL error code 1800 (ER_UNKNOWN_ALTER_ALGORITHM): Unknown ALGORITHM '%s'
MySQL error code 1801 (ER_UNKNOWN_ALTER_LOCK): Unknown LOCK type '%s'
MySQL error code 1802 (ER_MTS_CHANGE_MASTER_CANT_RUN_WITH_GAPS): CHANGE MASTER cannot be executed when the slave was stopped with an error or killed in MTS mode. Consider using RESET SLAVE or START SLAVE UNTIL.
MySQL error code 1803 (ER_MTS_RECOVERY_FAILURE): Cannot recover after SLAVE errored out in parallel execution mode. Additional error messages can be found in the MySQL error log.
MySQL error code 1804 (ER_MTS_RESET_WORKERS): Cannot clean up worker info tables. Additional error messages can be found in the MySQL error log.
MySQL error code 1805 (ER_COL_COUNT_DOESNT_MATCH_CORRUPTED_V2): Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corrupted
MySQL error code 1806 (ER_SLAVE_SILENT_RETRY_TRANSACTION): Slave must silently retry current transaction
MySQL error code 1807 (ER_DISCARD_FK_CHECKS_RUNNING): There is a foreign key check running on table '%-.192s'. Cannot discard the table.
MySQL error code 1808 (ER_TABLE_SCHEMA_MISMATCH): Schema mismatch (%s)
MySQL error code 1809 (ER_TABLE_IN_SYSTEM_TABLESPACE): Table '%-.192s' in system tablespace
MySQL error code 1810 (ER_IO_READ_ERROR): IO Read error: (%lu, %s) %s
MySQL error code 1811 (ER_IO_WRITE_ERROR): IO Write error: (%lu, %s) %s
MySQL error code 1812 (ER_TABLESPACE_MISSING): Tablespace is missing for table %s.
MySQL error code 1813 (ER_TABLESPACE_EXISTS): Tablespace '%-.192s' exists.
MySQL error code 1814 (ER_TABLESPACE_DISCARDED): Tablespace has been discarded for table '%-.192s'
MySQL error code 1815 (ER_INTERNAL_ERROR): Internal error: %s
MySQL error code 1816 (ER_INNODB_IMPORT_ERROR): ALTER TABLE %-.192s IMPORT TABLESPACE failed with error %lu : '%s'
MySQL error code 1817 (ER_INNODB_INDEX_CORRUPT): Index corrupt: %s
MySQL error code 1818 (ER_INVALID_YEAR_COLUMN_LENGTH): Supports only YEAR or YEAR(4) column.
MySQL error code 1819 (ER_NOT_VALID_PASSWORD): Your password does not satisfy the current policy requirements
MySQL error code 1820 (ER_MUST_CHANGE_PASSWORD): You must reset your password using ALTER USER statement before executing this statement.
MySQL error code 1821 (ER_FK_NO_INDEX_CHILD): Failed to add the foreign key constaint. Missing index for constraint '%s' in the foreign table '%s'
MySQL error code 1822 (ER_FK_NO_INDEX_PARENT): Failed to add the foreign key constaint. Missing index for constraint '%s' in the referenced table '%s'
MySQL error code 1823 (ER_FK_FAIL_ADD_SYSTEM): Failed to add the foreign key constraint '%s' to system tables
MySQL error code 1824 (ER_FK_CANNOT_OPEN_PARENT): Failed to open the referenced table '%s'
MySQL error code 1825 (ER_FK_INCORRECT_OPTION): Failed to add the foreign key constraint on table '%s'. Incorrect options in FOREIGN KEY constraint '%s'
MySQL error code 1826 (ER_FK_DUP_NAME): Duplicate foreign key constraint name '%s'
MySQL error code 1827 (ER_PASSWORD_FORMAT): The password hash doesn't have the expected format. Check if the correct password algorithm is being used with the PASSWORD() function.
MySQL error code 1828 (ER_FK_COLUMN_CANNOT_DROP): Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s'
MySQL error code 1829 (ER_FK_COLUMN_CANNOT_DROP_CHILD): Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s' of table '%-.192s'
MySQL error code 1830 (ER_FK_COLUMN_NOT_NULL): Column '%-.192s' cannot be NOT NULL: needed in a foreign key constraint '%-.192s' SET NULL
MySQL error code 1831 (ER_DUP_INDEX): Duplicate index '%-.64s' defined on the table '%-.64s.%-.64s'. This is deprecated and will be disallowed in a future release.
MySQL error code 1832 (ER_FK_COLUMN_CANNOT_CHANGE): Cannot change column '%-.192s': used in a foreign key constraint '%-.192s'
MySQL error code 1833 (ER_FK_COLUMN_CANNOT_CHANGE_CHILD): Cannot change column '%-.192s': used in a foreign key constraint '%-.192s' of table '%-.192s'
MySQL error code 1834 (ER_UNUSED5): Cannot delete rows from table which is parent in a foreign key constraint '%-.192s' of table '%-.192s'
MySQL error code 1835 (ER_MALFORMED_PACKET): Malformed communication packet.
MySQL error code 1836 (ER_READ_ONLY_MODE): Running in read-only mode
MySQL error code 1837 (ER_GTID_NEXT_TYPE_UNDEFINED_GROUP): When @@SESSION.GTID_NEXT is set to a GTID, you must explicitly set it to a different value after a COMMIT or ROLLBACK. Please check GTID_NEXT variable manual page for detailed explanation. Current @@SESSION.GTID_NEXT is '%s'.
MySQL error code 1838 (ER_VARIABLE_NOT_SETTABLE_IN_SP): The system variable %.200s cannot be set in stored procedures.
MySQL error code 1839 (ER_CANT_SET_GTID_PURGED_WHEN_GTID_MODE_IS_OFF): @@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_MODE = ON.
MySQL error code 1840 (ER_CANT_SET_GTID_PURGED_WHEN_GTID_EXECUTED_IS_NOT_EMPTY): @@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_EXECUTED is empty.
MySQL error code 1841 (ER_CANT_SET_GTID_PURGED_WHEN_OWNED_GTIDS_IS_NOT_EMPTY): @@GLOBAL.GTID_PURGED can only be set when there are no ongoing transactions (not even in other clients).
MySQL error code 1842 (ER_GTID_PURGED_WAS_CHANGED): @@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.
MySQL error code 1843 (ER_GTID_EXECUTED_WAS_CHANGED): @@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.
MySQL error code 1844 (ER_BINLOG_STMT_MODE_AND_NO_REPL_TABLES): Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT, and both replicated and non replicated tables are written to.
MySQL error code 1845 (ER_ALTER_OPERATION_NOT_SUPPORTED): %s is not supported for this operation. Try %s.
MySQL error code 1846 (ER_ALTER_OPERATION_NOT_SUPPORTED_REASON): %s is not supported. Reason: %s. Try %s.
MySQL error code 1847 (ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_COPY): COPY algorithm requires a lock
MySQL error code 1848 (ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_PARTITION): Partition specific operations do not yet support LOCK/ALGORITHM
MySQL error code 1849 (ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_FK_RENAME): Columns participating in a foreign key are renamed
MySQL error code 1850 (ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_COLUMN_TYPE): Cannot change column type INPLACE
MySQL error code 1851 (ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_FK_CHECK): Adding foreign keys needs foreign_key_checks=OFF
MySQL error code 1852 (ER_UNUSED6): Creating unique indexes with IGNORE requires COPY algorithm to remove duplicate rows
MySQL error code 1853 (ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_NOPK): Dropping a primary key is not allowed without also adding a new primary key
MySQL error code 1854 (ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_AUTOINC): Adding an auto-increment column requires a lock
MySQL error code 1855 (ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_HIDDEN_FTS): Cannot replace hidden FTS_DOC_ID with a user-visible one
MySQL error code 1856 (ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_CHANGE_FTS): Cannot drop or rename FTS_DOC_ID
MySQL error code 1857 (ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_FTS): Fulltext index creation requires a lock
MySQL error code 1858 (ER_SQL_SLAVE_SKIP_COUNTER_NOT_SETTABLE_IN_GTID_MODE): sql_slave_skip_counter can not be set when the server is running with @@GLOBAL.GTID_MODE = ON. Instead, for each transaction that you want to skip, generate an empty transaction with the same GTID as the transaction
MySQL error code 1859 (ER_DUP_UNKNOWN_IN_INDEX): Duplicate entry for key '%-.192s'
MySQL error code 1860 (ER_IDENT_CAUSES_TOO_LONG_PATH): Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.
MySQL error code 1861 (ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_NOT_NULL): cannot silently convert NULL values, as required in this SQL_MODE
MySQL error code 1862 (ER_MUST_CHANGE_PASSWORD_LOGIN): Your password has expired. To log in you must change it using a client that supports expired passwords.
MySQL error code 1863 (ER_ROW_IN_WRONG_PARTITION): Found a row in wrong partition %s
MySQL error code 1864 (ER_MTS_EVENT_BIGGER_PENDING_JOBS_SIZE_MAX): Cannot schedule event %s, relay-log name %s, position %s to Worker thread because its size %lu exceeds %lu of slave_pending_jobs_size_max.
MySQL error code 1865 (ER_INNODB_NO_FT_USES_PARSER): Cannot CREATE FULLTEXT INDEX WITH PARSER on InnoDB table
MySQL error code 1866 (ER_BINLOG_LOGICAL_CORRUPTION): The binary log file '%s' is logically corrupted: %s
MySQL error code 1867 (ER_WARN_PURGE_LOG_IN_USE): file %s was not purged because it was being read by %d thread(s), purged only %d out of %d files.
MySQL error code 1868 (ER_WARN_PURGE_LOG_IS_ACTIVE): file %s was not purged because it is the active log file.
MySQL error code 1869 (ER_AUTO_INCREMENT_CONFLICT): Auto-increment value in UPDATE conflicts with internally generated values
MySQL error code 1870 (WARN_ON_BLOCKHOLE_IN_RBR): Row events are not logged for %s statements that modify BLACKHOLE tables in row format. Table(s): '%-.192s'
MySQL error code 1871 (ER_SLAVE_MI_INIT_REPOSITORY): Slave failed to initialize master info structure from the repository
MySQL error code 1872 (ER_SLAVE_RLI_INIT_REPOSITORY): Slave failed to initialize relay log info structure from the repository
MySQL error code 1873 (ER_ACCESS_DENIED_CHANGE_USER_ERROR): Access denied trying to change to user '%-.48s'@'%-.64s' (using password: %s). Disconnecting.
MySQL error code 1874 (ER_INNODB_READ_ONLY): InnoDB is in read only mode.
MySQL error code 1875 (ER_STOP_SLAVE_SQL_THREAD_TIMEOUT): STOP SLAVE command execution is incomplete: Slave SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.
MySQL error code 1876 (ER_STOP_SLAVE_IO_THREAD_TIMEOUT): STOP SLAVE command execution is incomplete: Slave IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.
MySQL error code 1877 (ER_TABLE_CORRUPT): Operation cannot be performed. The table '%-.64s.%-.64s' is missing, corrupt or contains bad data.
MySQL error code 1878 (ER_TEMP_FILE_WRITE_FAILURE): Temporary file write failure.
MySQL error code 1879 (ER_INNODB_FT_AUX_NOT_HEX_ID): Upgrade index name failed, please use create index(alter table) algorithm copy to rebuild index.
MySQL error code 1880 (ER_OLD_TEMPORALS_UPGRADED): TIME/TIMESTAMP/DATETIME columns of old format have been upgraded to the new format.
MySQL error code 1881 (ER_INNODB_FORCED_RECOVERY): Operation not allowed when innodb_forced_recovery > 0.
MySQL error code 1882 (ER_AES_INVALID_IV): The initialization vector supplied to %s is too short. Must be at least %d bytes long
MySQL error code 1883 (ER_PLUGIN_CANNOT_BE_UNINSTALLED): Plugin '%s' cannot be uninstalled now. %s
MySQL error code 1884 (ER_GTID_UNSAFE_BINLOG_SPLITTABLE_STATEMENT_AND_GTID_GROUP): Cannot execute statement because it needs to be written to the binary log as multiple statements, and this is not allowed when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.
MySQL error code 1885 (ER_SLAVE_HAS_MORE_GTIDS_THAN_MASTER): Slave has more GTIDs than the master has, using the master's SERVER_UUID. This may indicate that the end of the binary log was truncated or that the last binary log file was lost, e.g., after a power or disk failure when sync_binlog != 1. The master may or may not have rolled back transactions that were already replicated to the slave. Suggest to replicate any transactions that master has rolled back from slave to master, and/or commit empty transactions on master to account for transactions that have been committed on master but are not included in GTID_EXECUTED.
MySQL error code 1886 (ER_MISSING_KEY): The table '%s.%s' does not have the necessary key(s) defined on it. Please check the table definition and create index(s) accordingly.
MySQL error code 1887 (WARN_NAMED_PIPE_ACCESS_EVERYONE): Setting named_pipe_full_access_group='%s' is insecure. Consider using a Windows group with fewer members.
MySQL error code 3000 (ER_FILE_CORRUPT): File %s is corrupted
MySQL error code 3001 (ER_ERROR_ON_MASTER): Query partially completed on the master (error on master: %d) and was aborted. There is a chance that your master is inconsistent at this point. If you are sure that your master is ok, run this query manually on the slave and then restart the slave with SET GLOBAL SQL_SLAVE_SKIP_COUNTER=1; START SLAVE;. Query:'%s'
MySQL error code 3002 (ER_INCONSISTENT_ERROR): Query caused different errors on master and slave. Error on master: message (format)='%s' error code=%d; Error on slave:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'
MySQL error code 3003 (ER_STORAGE_ENGINE_NOT_LOADED): Storage engine for table '%s'.'%s' is not loaded.
MySQL error code 3004 (ER_GET_STACKED_DA_WITHOUT_ACTIVE_HANDLER): GET STACKED DIAGNOSTICS when handler not active
MySQL error code 3005 (ER_WARN_LEGACY_SYNTAX_CONVERTED): %s is no longer supported. The statement was converted to %s.
MySQL error code 3006 (ER_BINLOG_UNSAFE_FULLTEXT_PLUGIN): Statement is unsafe because it uses a fulltext parser plugin which may not return the same value on the slave.
MySQL error code 3007 (ER_CANNOT_DISCARD_TEMPORARY_TABLE): Cannot DISCARD/IMPORT tablespace associated with temporary table
MySQL error code 3008 (ER_FK_DEPTH_EXCEEDED): Foreign key cascade delete/update exceeds max depth of %d.
MySQL error code 3009 (ER_COL_COUNT_DOESNT_MATCH_PLEASE_UPDATE_V2): Column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please use mysql_upgrade to fix this error.
MySQL error code 3010 (ER_WARN_TRIGGER_DOESNT_HAVE_CREATED): Trigger %s.%s.%s does not have CREATED attribute.
MySQL error code 3011 (ER_REFERENCED_TRG_DOES_NOT_EXIST): Referenced trigger '%s' for the given action time and event type does not exist.
MySQL error code 3012 (ER_EXPLAIN_NOT_SUPPORTED): EXPLAIN FOR CONNECTION command is supported only for SELECT/UPDATE/INSERT/DELETE/REPLACE
MySQL error code 3013 (ER_INVALID_FIELD_SIZE): Invalid size for column '%-.192s'.
MySQL error code 3014 (ER_MISSING_HA_CREATE_OPTION): Table storage engine '%-.64s' found required create option missing
MySQL error code 3015 (ER_ENGINE_OUT_OF_MEMORY): Out of memory in storage engine '%-.64s'.
MySQL error code 3016 (ER_PASSWORD_EXPIRE_ANONYMOUS_USER): The password for anonymous user cannot be expired.
MySQL error code 3017 (ER_SLAVE_SQL_THREAD_MUST_STOP): This operation cannot be performed with a running slave sql thread; run STOP SLAVE SQL_THREAD first
MySQL error code 3018 (ER_NO_FT_MATERIALIZED_SUBQUERY): Cannot create FULLTEXT index on materialized subquery
MySQL error code 3019 (ER_INNODB_UNDO_LOG_FULL): Undo Log error: %s
MySQL error code 3020 (ER_INVALID_ARGUMENT_FOR_LOGARITHM): Invalid argument for logarithm
MySQL error code 3021 (ER_SLAVE_CHANNEL_IO_THREAD_MUST_STOP): This operation cannot be performed with a running slave io thread; run STOP SLAVE IO_THREAD FOR CHANNEL '%s' first.
MySQL error code 3022 (ER_WARN_OPEN_TEMP_TABLES_MUST_BE_ZERO): This operation may not be safe when the slave has temporary tables. The tables will be kept open until the server restarts or until the tables are deleted by any replicated DROP statement. Suggest to wait until slave_open_temp_tables = 0.
MySQL error code 3023 (ER_WARN_ONLY_MASTER_LOG_FILE_NO_POS): CHANGE MASTER TO with a MASTER_LOG_FILE clause but no MASTER_LOG_POS clause may not be safe. The old position value may not be valid for the new binary log file.
MySQL error code 3024 (ER_QUERY_TIMEOUT): Query execution was interrupted, maximum statement execution time exceeded
MySQL error code 3025 (ER_NON_RO_SELECT_DISABLE_TIMER): Select is not a read only statement, disabling timer
MySQL error code 3026 (ER_DUP_LIST_ENTRY): Duplicate entry '%-.192s'.
MySQL error code 3027 (ER_SQL_MODE_NO_EFFECT): '%s' mode no longer has any effect. Use STRICT_ALL_TABLES or STRICT_TRANS_TABLES instead.
MySQL error code 3028 (ER_AGGREGATE_ORDER_FOR_UNION): Expression #%u of ORDER BY contains aggregate function and applies to a UNION
MySQL error code 3029 (ER_AGGREGATE_ORDER_NON_AGG_QUERY): Expression #%u of ORDER BY contains aggregate function and applies to the result of a non-aggregated query
MySQL error code 3030 (ER_SLAVE_WORKER_STOPPED_PREVIOUS_THD_ERROR): Slave worker has stopped after at least one previous worker encountered an error when slave-preserve-commit-order was enabled. To preserve commit order, the last transaction executed by this thread has not been committed. When restarting the slave after fixing any failed threads, you should fix this worker as well.
MySQL error code 3031 (ER_DONT_SUPPORT_SLAVE_PRESERVE_COMMIT_ORDER): slave_preserve_commit_order is not supported %s.
MySQL error code 3032 (ER_SERVER_OFFLINE_MODE): The server is currently in offline mode
MySQL error code 3033 (ER_GIS_DIFFERENT_SRIDS): Binary geometry function %s given two geometries of different srids: %u and %u, which should have been identical.
MySQL error code 3034 (ER_GIS_UNSUPPORTED_ARGUMENT): Calling geometry function %s with unsupported types of arguments.
MySQL error code 3035 (ER_GIS_UNKNOWN_ERROR): Unknown GIS error occured in function %s.
MySQL error code 3036 (ER_GIS_UNKNOWN_EXCEPTION): Unknown exception caught in GIS function %s.
MySQL error code 3037 (ER_GIS_INVALID_DATA): Invalid GIS data provided to function %s.
MySQL error code 3038 (ER_BOOST_GEOMETRY_EMPTY_INPUT_EXCEPTION): The geometry has no data in function %s.
MySQL error code 3039 (ER_BOOST_GEOMETRY_CENTROID_EXCEPTION): Unable to calculate centroid because geometry is empty in function %s.
MySQL error code 3040 (ER_BOOST_GEOMETRY_OVERLAY_INVALID_INPUT_EXCEPTION): Geometry overlay calculation error: geometry data is invalid in function %s.
MySQL error code 3041 (ER_BOOST_GEOMETRY_TURN_INFO_EXCEPTION): Geometry turn info calculation error: geometry data is invalid in function %s.
MySQL error code 3042 (ER_BOOST_GEOMETRY_SELF_INTERSECTION_POINT_EXCEPTION): Analysis procedures of intersection points interrupted unexpectedly in function %s.
MySQL error code 3043 (ER_BOOST_GEOMETRY_UNKNOWN_EXCEPTION): Unknown exception thrown in function %s.
MySQL error code 3044 (ER_STD_BAD_ALLOC_ERROR): Memory allocation error: %-.256s in function %s.
MySQL error code 3045 (ER_STD_DOMAIN_ERROR): Domain error: %-.256s in function %s.
MySQL error code 3046 (ER_STD_LENGTH_ERROR): Length error: %-.256s in function %s.
MySQL error code 3047 (ER_STD_INVALID_ARGUMENT): Invalid argument error: %-.256s in function %s.
MySQL error code 3048 (ER_STD_OUT_OF_RANGE_ERROR): Out of range error: %-.256s in function %s.
MySQL error code 3049 (ER_STD_OVERFLOW_ERROR): Overflow error error: %-.256s in function %s.
MySQL error code 3050 (ER_STD_RANGE_ERROR): Range error: %-.256s in function %s.
MySQL error code 3051 (ER_STD_UNDERFLOW_ERROR): Underflow error: %-.256s in function %s.
MySQL error code 3052 (ER_STD_LOGIC_ERROR): Logic error: %-.256s in function %s.
MySQL error code 3053 (ER_STD_RUNTIME_ERROR): Runtime error: %-.256s in function %s.
MySQL error code 3054 (ER_STD_UNKNOWN_EXCEPTION): Unknown exception: %-.384s in function %s.
MySQL error code 3055 (ER_GIS_DATA_WRONG_ENDIANESS): Geometry byte string must be little endian.
MySQL error code 3056 (ER_CHANGE_MASTER_PASSWORD_LENGTH): The password provided for the replication user exceeds the maximum length of 32 characters
MySQL error code 3057 (ER_USER_LOCK_WRONG_NAME): Incorrect user-level lock name '%-.192s'.
MySQL error code 3058 (ER_USER_LOCK_DEADLOCK): Deadlock found when trying to get user-level lock; try rolling back transaction/releasing locks and restarting lock acquisition.
MySQL error code 3059 (ER_REPLACE_INACCESSIBLE_ROWS): REPLACE cannot be executed as it requires deleting rows that are not in the view
MySQL error code 3060 (ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_GIS): Do not support online operation on table with GIS index
MySQL error code 3061 (ER_ILLEGAL_USER_VAR): User variable name '%-.100s' is illegal
MySQL error code 3062 (ER_GTID_MODE_OFF): Cannot %s when GTID_MODE = OFF.
MySQL error code 3063 (ER_UNSUPPORTED_BY_REPLICATION_THREAD): Cannot %s from a replication slave thread.
MySQL error code 3064 (ER_INCORRECT_TYPE): Incorrect type for argument %s in function %s.
MySQL error code 3065 (ER_FIELD_IN_ORDER_NOT_SELECT): Expression #%u of ORDER BY clause is not in SELECT list, references column '%-.192s' which is not in SELECT list; this is incompatible with %s
MySQL error code 3066 (ER_AGGREGATE_IN_ORDER_NOT_SELECT): Expression #%u of ORDER BY clause is not in SELECT list, contains aggregate function; this is incompatible with %s
MySQL error code 3067 (ER_INVALID_RPL_WILD_TABLE_FILTER_PATTERN): Supplied filter list contains a value which is not in the required format 'db_pattern.table_pattern'
MySQL error code 3068 (ER_NET_OK_PACKET_TOO_LARGE): OK packet too large
MySQL error code 3069 (ER_INVALID_JSON_DATA): Invalid JSON data provided to function %s: %s
MySQL error code 3070 (ER_INVALID_GEOJSON_MISSING_MEMBER): Invalid GeoJSON data provided to function %s: Missing required member '%s'
MySQL error code 3071 (ER_INVALID_GEOJSON_WRONG_TYPE): Invalid GeoJSON data provided to function %s: Member '%s' must be of type '%s'
MySQL error code 3072 (ER_INVALID_GEOJSON_UNSPECIFIED): Invalid GeoJSON data provided to function %s
MySQL error code 3073 (ER_DIMENSION_UNSUPPORTED): Unsupported number of coordinate dimensions in function %s: Found %u, expected %u
MySQL error code 3074 (ER_SLAVE_CHANNEL_DOES_NOT_EXIST): Slave channel '%s' does not exist.
MySQL error code 3075 (ER_SLAVE_MULTIPLE_CHANNELS_HOST_PORT): A slave channel '%s' already exists for the given host and port combination.
MySQL error code 3076 (ER_SLAVE_CHANNEL_NAME_INVALID_OR_TOO_LONG): Couldn't create channel: Channel name is either invalid or too long.
MySQL error code 3077 (ER_SLAVE_NEW_CHANNEL_WRONG_REPOSITORY): To have multiple channels, repository cannot be of type FILE; Please check the repository configuration and convert them to TABLE.
MySQL error code 3078 (ER_SLAVE_CHANNEL_DELETE): Cannot delete slave info objects for channel '%s'.
MySQL error code 3079 (ER_SLAVE_MULTIPLE_CHANNELS_CMD): Multiple channels exist on the slave. Please provide channel name as an argument.
MySQL error code 3080 (ER_SLAVE_MAX_CHANNELS_EXCEEDED): Maximum number of replication channels allowed exceeded.
MySQL error code 3081 (ER_SLAVE_CHANNEL_MUST_STOP): This operation cannot be performed with running replication threads; run STOP SLAVE FOR CHANNEL '%s' first
MySQL error code 3082 (ER_SLAVE_CHANNEL_NOT_RUNNING): This operation requires running replication threads; configure slave and run START SLAVE FOR CHANNEL '%s'
MySQL error code 3083 (ER_SLAVE_CHANNEL_WAS_RUNNING): Replication thread(s) for channel '%s' are already runnning.
MySQL error code 3084 (ER_SLAVE_CHANNEL_WAS_NOT_RUNNING): Replication thread(s) for channel '%s' are already stopped.
MySQL error code 3085 (ER_SLAVE_CHANNEL_SQL_THREAD_MUST_STOP): This operation cannot be performed with a running slave sql thread; run STOP SLAVE SQL_THREAD FOR CHANNEL '%s' first.
MySQL error code 3086 (ER_SLAVE_CHANNEL_SQL_SKIP_COUNTER): When sql_slave_skip_counter > 0, it is not allowed to start more than one SQL thread by using 'START SLAVE [SQL_THREAD]'. Value of sql_slave_skip_counter can only be used by one SQL thread at a time. Please use 'START SLAVE [SQL_THREAD] FOR CHANNEL' to start the SQL thread which will use the value of sql_slave_skip_counter.
MySQL error code 3087 (ER_WRONG_FIELD_WITH_GROUP_V2): Expression #%u of %s is not in GROUP BY clause and contains nonaggregated column '%-.192s' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_by
MySQL error code 3088 (ER_MIX_OF_GROUP_FUNC_AND_FIELDS_V2): In aggregated query without GROUP BY, expression #%u of %s contains nonaggregated column '%-.192s'; this is incompatible with sql_mode=only_full_group_by
MySQL error code 3089 (ER_WARN_DEPRECATED_SYSVAR_UPDATE): Updating '%s' is deprecated. It will be made read-only in a future release.
MySQL error code 3090 (ER_WARN_DEPRECATED_SQLMODE): Changing sql mode '%s' is deprecated. It will be removed in a future release.
MySQL error code 3091 (ER_CANNOT_LOG_PARTIAL_DROP_DATABASE_WITH_GTID): DROP DATABASE failed; some tables may have been dropped but the database directory remains. The GTID has not been added to GTID_EXECUTED and the statement was not written to the binary log. Fix this as follows: (1) remove all files from the database directory %-.192s; (2) SET GTID_NEXT='%-.192s'; (3) DROP DATABASE `%-.192s`.
MySQL error code 3092 (ER_GROUP_REPLICATION_CONFIGURATION): The server is not configured properly to be an active member of the group. Please see more details on error log.
MySQL error code 3093 (ER_GROUP_REPLICATION_RUNNING): The START GROUP_REPLICATION command failed since the group is already running.
MySQL error code 3094 (ER_GROUP_REPLICATION_APPLIER_INIT_ERROR): The START GROUP_REPLICATION command failed as the applier module failed to start.
MySQL error code 3095 (ER_GROUP_REPLICATION_STOP_APPLIER_THREAD_TIMEOUT): The STOP GROUP_REPLICATION command execution is incomplete: The applier thread got the stop signal while it was busy. The applier thread will stop once the current task is complete.
MySQL error code 3096 (ER_GROUP_REPLICATION_COMMUNICATION_LAYER_SESSION_ERROR): The START GROUP_REPLICATION command failed as there was an error when initializing the group communication layer.
MySQL error code 3097 (ER_GROUP_REPLICATION_COMMUNICATION_LAYER_JOIN_ERROR): The START GROUP_REPLICATION command failed as there was an error when joining the communication group.
MySQL error code 3098 (ER_BEFORE_DML_VALIDATION_ERROR): The table does not comply with the requirements by an external plugin.
MySQL error code 3099 (ER_PREVENTS_VARIABLE_WITHOUT_RBR): Cannot change the value of variable %s without binary log format as ROW.
MySQL error code 3100 (ER_RUN_HOOK_ERROR): Error on observer while running replication hook '%s'.
MySQL error code 3101 (ER_TRANSACTION_ROLLBACK_DURING_COMMIT): Plugin instructed the server to rollback the current transaction.
MySQL error code 3102 (ER_GENERATED_COLUMN_FUNCTION_IS_NOT_ALLOWED): Expression of generated column '%s' contains a disallowed function.
MySQL error code 3103 (ER_UNSUPPORTED_ALTER_INPLACE_ON_VIRTUAL_COLUMN): INPLACE ADD or DROP of virtual columns cannot be combined with other ALTER TABLE actions
MySQL error code 3104 (ER_WRONG_FK_OPTION_FOR_GENERATED_COLUMN): Cannot define foreign key with %s clause on a generated column.
MySQL error code 3105 (ER_NON_DEFAULT_VALUE_FOR_GENERATED_COLUMN): The value specified for generated column '%s' in table '%s' is not allowed.
MySQL error code 3106 (ER_UNSUPPORTED_ACTION_ON_GENERATED_COLUMN): '%s' is not supported for generated columns.
MySQL error code 3107 (ER_GENERATED_COLUMN_NON_PRIOR): Generated column can refer only to generated columns defined prior to it.
MySQL error code 3108 (ER_DEPENDENT_BY_GENERATED_COLUMN): Column '%s' has a generated column dependency.
MySQL error code 3109 (ER_GENERATED_COLUMN_REF_AUTO_INC): Generated column '%s' cannot refer to auto-increment column.
MySQL error code 3110 (ER_FEATURE_NOT_AVAILABLE): The '%-.64s' feature is not available; you need to remove '%-.64s' or use MySQL built with '%-.64s'
MySQL error code 3111 (ER_CANT_SET_GTID_MODE): SET @@GLOBAL.GTID_MODE = %-.64s is not allowed because %-.384s.
MySQL error code 3112 (ER_CANT_USE_AUTO_POSITION_WITH_GTID_MODE_OFF): The replication receiver thread%-.192s cannot start in AUTO_POSITION mode: this server uses @@GLOBAL.GTID_MODE = OFF.
MySQL error code 3113 (ER_CANT_REPLICATE_ANONYMOUS_WITH_AUTO_POSITION): Cannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.512s, position %lld.
MySQL error code 3114 (ER_CANT_REPLICATE_ANONYMOUS_WITH_GTID_MODE_ON): Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.512s, position %lld.
MySQL error code 3115 (ER_CANT_REPLICATE_GTID_WITH_GTID_MODE_OFF): Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.512s, position %lld.
MySQL error code 3116 (ER_CANT_SET_ENFORCE_GTID_CONSISTENCY_ON_WITH_ONGOING_GTID_VIOLATING_TRANSACTIONS): Cannot set ENFORCE_GTID_CONSISTENCY = ON because there are ongoing transactions that violate GTID consistency.
MySQL error code 3117 (ER_SET_ENFORCE_GTID_CONSISTENCY_WARN_WITH_ONGOING_GTID_VIOLATING_TRANSACTIONS): There are ongoing transactions that violate GTID consistency.
MySQL error code 3118 (ER_ACCOUNT_HAS_BEEN_LOCKED): Access denied for user '%-.48s'@'%-.64s'. Account is locked.
MySQL error code 3119 (ER_WRONG_TABLESPACE_NAME): Incorrect tablespace name `%-.192s`
MySQL error code 3120 (ER_TABLESPACE_IS_NOT_EMPTY): Tablespace `%-.192s` is not empty.
MySQL error code 3121 (ER_WRONG_FILE_NAME): Incorrect File Name '%s'.
MySQL error code 3122 (ER_BOOST_GEOMETRY_INCONSISTENT_TURNS_EXCEPTION): Inconsistent intersection points.
MySQL error code 3123 (ER_WARN_OPTIMIZER_HINT_SYNTAX_ERROR): Optimizer hint syntax error
MySQL error code 3124 (ER_WARN_BAD_MAX_EXECUTION_TIME): Unsupported MAX_EXECUTION_TIME
MySQL error code 3125 (ER_WARN_UNSUPPORTED_MAX_EXECUTION_TIME): MAX_EXECUTION_TIME hint is supported by top-level standalone SELECT statements only
MySQL error code 3126 (ER_WARN_CONFLICTING_HINT): Hint %s is ignored as conflicting/duplicated
MySQL error code 3127 (ER_WARN_UNKNOWN_QB_NAME): Query block name %s is not found for %s hint
MySQL error code 3128 (ER_UNRESOLVED_HINT_NAME): Unresolved name %s for %s hint
MySQL error code 3129 (ER_WARN_ON_MODIFYING_GTID_EXECUTED_TABLE): Please do not modify the %s table. This is a mysql internal system table to store GTIDs for committed transactions. Modifying it can lead to an inconsistent GTID state.
MySQL error code 3130 (ER_PLUGGABLE_PROTOCOL_COMMAND_NOT_SUPPORTED): Command not supported by pluggable protocols
MySQL error code 3131 (ER_LOCKING_SERVICE_WRONG_NAME): Incorrect locking service lock name '%-.192s'.
MySQL error code 3132 (ER_LOCKING_SERVICE_DEADLOCK): Deadlock found when trying to get locking service lock; try releasing locks and restarting lock acquisition.
MySQL error code 3133 (ER_LOCKING_SERVICE_TIMEOUT): Service lock wait timeout exceeded.
MySQL error code 3134 (ER_GIS_MAX_POINTS_IN_GEOMETRY_OVERFLOWED): Parameter %s exceeds the maximum number of points in a geometry (%lu) in function %s.
MySQL error code 3135 (ER_SQL_MODE_MERGED): 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
MySQL error code 3136 (ER_VTOKEN_PLUGIN_TOKEN_MISMATCH): Version token mismatch for %.*s. Correct value %.*s
MySQL error code 3137 (ER_VTOKEN_PLUGIN_TOKEN_NOT_FOUND): Version token %.*s not found.
MySQL error code 3138 (ER_CANT_SET_VARIABLE_WHEN_OWNING_GTID): Variable %-.192s cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.
MySQL error code 3139 (ER_SLAVE_CHANNEL_OPERATION_NOT_ALLOWED): %-.192s cannot be performed on channel '%-.192s'.
MySQL error code 3140 (ER_INVALID_JSON_TEXT): Invalid JSON text: "%s" at position %u in value for column '%-.200s'.
MySQL error code 3141 (ER_INVALID_JSON_TEXT_IN_PARAM): Invalid JSON text in argument %u to function %s: "%s" at position %u.%-.0s
MySQL error code 3142 (ER_INVALID_JSON_BINARY_DATA): The JSON binary value contains invalid data.
MySQL error code 3143 (ER_INVALID_JSON_PATH): Invalid JSON path expression. The error is around character position %u.%-.200s
MySQL error code 3144 (ER_INVALID_JSON_CHARSET): Cannot create a JSON value from a string with CHARACTER SET '%s'.
MySQL error code 3145 (ER_INVALID_JSON_CHARSET_IN_FUNCTION): Invalid JSON character data provided to function %s: '%s'; utf8 is required.
MySQL error code 3146 (ER_INVALID_TYPE_FOR_JSON): Invalid data type for JSON data in argument %u to function %s; a JSON string or JSON type is required.
MySQL error code 3147 (ER_INVALID_CAST_TO_JSON): Cannot CAST value to JSON.
MySQL error code 3148 (ER_INVALID_JSON_PATH_CHARSET): A path expression must be encoded in the utf8 character set. The path expression '%-.200s' is encoded in character set '%-.200s'.
MySQL error code 3149 (ER_INVALID_JSON_PATH_WILDCARD): In this situation, path expressions may not contain the * and ** tokens.
MySQL error code 3150 (ER_JSON_VALUE_TOO_BIG): The JSON value is too big to be stored in a JSON column.
MySQL error code 3151 (ER_JSON_KEY_TOO_BIG): The JSON object contains a key name that is too long.
MySQL error code 3152 (ER_JSON_USED_AS_KEY): JSON column '%-.192s' cannot be used in key specification.
MySQL error code 3153 (ER_JSON_VACUOUS_PATH): The path expression '$' is not allowed in this context.
MySQL error code 3154 (ER_JSON_BAD_ONE_OR_ALL_ARG): The oneOrAll argument to %s may take these values: 'one' or 'all'.
MySQL error code 3155 (ER_NUMERIC_JSON_VALUE_OUT_OF_RANGE): Out of range JSON value for CAST to %s%-.0s from column %s at row %ld
MySQL error code 3156 (ER_INVALID_JSON_VALUE_FOR_CAST): Invalid JSON value for CAST to %s%-.0s from column %s at row %ld
MySQL error code 3157 (ER_JSON_DOCUMENT_TOO_DEEP): The JSON document exceeds the maximum depth.
MySQL error code 3158 (ER_JSON_DOCUMENT_NULL_KEY): JSON documents may not contain NULL member names.
MySQL error code 3159 (ER_SECURE_TRANSPORT_REQUIRED): Connections using insecure transport are prohibited while --require_secure_transport=ON.
MySQL error code 3160 (ER_NO_SECURE_TRANSPORTS_CONFIGURED): No secure transports (SSL or Shared Memory) are configured, unable to set --require_secure_transport=ON.
MySQL error code 3161 (ER_DISABLED_STORAGE_ENGINE): Storage engine %s is disabled (Table creation is disallowed).
MySQL error code 3162 (ER_USER_DOES_NOT_EXIST): User %s does not exist.
MySQL error code 3163 (ER_USER_ALREADY_EXISTS): User %s already exists.
MySQL error code 3164 (ER_AUDIT_API_ABORT): Aborted by Audit API ('%-.48s';%d).
MySQL error code 3165 (ER_INVALID_JSON_PATH_ARRAY_CELL): A path expression is not a path to a cell in an array.
MySQL error code 3166 (ER_BUFPOOL_RESIZE_INPROGRESS): Another buffer pool resize is already in progress.
MySQL error code 3167 (ER_FEATURE_DISABLED_SEE_DOC): The '%s' feature is disabled; see the documentation for '%s'
MySQL error code 3168 (ER_SERVER_ISNT_AVAILABLE): Server isn't available
MySQL error code 3169 (ER_SESSION_WAS_KILLED): Session was killed
MySQL error code 3170 (ER_CAPACITY_EXCEEDED): Memory capacity of %llu bytes for '%s' exceeded. %s
MySQL error code 3171 (ER_CAPACITY_EXCEEDED_IN_RANGE_OPTIMIZER): Range optimization was not done for this query.
MySQL error code 3172 (ER_TABLE_NEEDS_UPG_PART): Partitioning upgrade required. Please dump/reload to fix it or do: ALTER TABLE `%-.192s`.`%-.192s` UPGRADE PARTITIONING
MySQL error code 3173 (ER_CANT_WAIT_FOR_EXECUTED_GTID_SET_WHILE_OWNING_A_GTID): The client holds ownership of the GTID %s. Therefore, WAIT_FOR_EXECUTED_GTID_SET cannot wait for this GTID.
MySQL error code 3174 (ER_CANNOT_ADD_FOREIGN_BASE_COL_VIRTUAL): Cannot add foreign key on the base column of indexed virtual column.
MySQL error code 3175 (ER_CANNOT_CREATE_VIRTUAL_INDEX_CONSTRAINT): Cannot create index on virtual column whose base column has foreign constraint.
MySQL error code 3176 (ER_ERROR_ON_MODIFYING_GTID_EXECUTED_TABLE): Please do not modify the %s table with an XA transaction. This is an internal system table used to store GTIDs for committed transactions. Although modifying it can lead to an inconsistent GTID state, if neccessary you can modify it with a non-XA transaction.
MySQL error code 3177 (ER_LOCK_REFUSED_BY_ENGINE): Lock acquisition refused by storage engine.
MySQL error code 3178 (ER_UNSUPPORTED_ALTER_ONLINE_ON_VIRTUAL_COLUMN): ADD COLUMN col...VIRTUAL, ADD INDEX(col)
MySQL error code 3179 (ER_MASTER_KEY_ROTATION_NOT_SUPPORTED_BY_SE): Master key rotation is not supported by storage engine.
MySQL error code 3180 (ER_MASTER_KEY_ROTATION_ERROR_BY_SE): Encryption key rotation error reported by SE: %s
MySQL error code 3181 (ER_MASTER_KEY_ROTATION_BINLOG_FAILED): Write to binlog failed. However, master key rotation has been completed successfully.
MySQL error code 3182 (ER_MASTER_KEY_ROTATION_SE_UNAVAILABLE): Storage engine is not available.
MySQL error code 3183 (ER_TABLESPACE_CANNOT_ENCRYPT): This tablespace can't be encrypted.
MySQL error code 3184 (ER_INVALID_ENCRYPTION_OPTION): Invalid encryption option.
MySQL error code 3185 (ER_CANNOT_FIND_KEY_IN_KEYRING): Can't find master key from keyring, please check in the server log if a keyring plugin is loaded and initialized successfully.
MySQL error code 3186 (ER_CAPACITY_EXCEEDED_IN_PARSER): Parser bailed out for this query.
MySQL error code 3187 (ER_UNSUPPORTED_ALTER_ENCRYPTION_INPLACE): Cannot alter encryption attribute by inplace algorithm.
MySQL error code 3188 (ER_KEYRING_UDF_KEYRING_SERVICE_ERROR): Function '%s' failed because underlying keyring service returned an error. Please check if a keyring plugin is installed and that provided arguments are valid for the keyring you are using.
MySQL error code 3189 (ER_USER_COLUMN_OLD_LENGTH): It seems that your db schema is old. The %s column is 77 characters long and should be 93 characters long. Please run mysql_upgrade.
MySQL error code 3190 (ER_CANT_RESET_MASTER): RESET MASTER is not allowed because %-.384s.
MySQL error code 3191 (ER_GROUP_REPLICATION_MAX_GROUP_SIZE): The START GROUP_REPLICATION command failed since the group already has 9 members.
MySQL error code 3192 (ER_CANNOT_ADD_FOREIGN_BASE_COL_STORED): Cannot add foreign key on the base column of stored column. 
MySQL error code 3193 (ER_TABLE_REFERENCED): Cannot complete the operation because table is referenced by another connection.
MySQL error code 3194 (ER_PARTITION_ENGINE_DEPRECATED_FOR_TABLE): The partition engine, used by table '%-.192s.%-.192s', is deprecated and will be removed in a future release. Please use native partitioning instead.
MySQL error code 3195 (ER_WARN_USING_GEOMFROMWKB_TO_SET_SRID_ZERO): %.192s(geometry) is deprecated and will be replaced by st_srid(geometry, 0) in a future version. Use %.192s(st_aswkb(geometry), 0) instead.
MySQL error code 3196 (ER_WARN_USING_GEOMFROMWKB_TO_SET_SRID): %.192s(geometry, srid) is deprecated and will be replaced by st_srid(geometry, srid) in a future version. Use %.192s(st_aswkb(geometry), srid) instead.
MySQL error code 3197 (ER_XA_RETRY): The resource manager is not able to commit the transaction branch at this time. Please retry later.
MySQL error code 3198 (ER_KEYRING_AWS_UDF_AWS_KMS_ERROR): Function %s failed due to: %s.
MySQL error code 3199 (ER_BINLOG_UNSAFE_XA): Statement is unsafe because it is being used inside a XA transaction. Concurrent XA transactions may deadlock on slaves when replicated using statements.
MySQL error code 3200 (ER_UDF_ERROR): %s UDF failed; %s
MySQL error code 3201 (ER_KEYRING_MIGRATION_FAILURE): Can not perform keyring migration : %s
MySQL error code 3202 (ER_KEYRING_ACCESS_DENIED_ERROR): Access denied; you need %-.128s privileges for this operation
MySQL error code 3203 (ER_KEYRING_MIGRATION_STATUS): Keyring migration %s.
MySQL error code 3204 (ER_PLUGIN_FAILED_TO_OPEN_TABLES): Failed to open the %s filter tables.
MySQL error code 3205 (ER_PLUGIN_FAILED_TO_OPEN_TABLE): Failed to open '%s.%s' %s table.
MySQL error code 3206 (ER_AUDIT_LOG_NO_KEYRING_PLUGIN_INSTALLED): No keyring plugin installed.
MySQL error code 3207 (ER_AUDIT_LOG_ENCRYPTION_PASSWORD_HAS_NOT_BEEN_SET): Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.
MySQL error code 3208 (ER_AUDIT_LOG_COULD_NOT_CREATE_AES_KEY): Could not create AES key. OpenSSL's EVP_BytesToKey function failed.
MySQL error code 3209 (ER_AUDIT_LOG_ENCRYPTION_PASSWORD_CANNOT_BE_FETCHED): Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.
MySQL error code 3210 (ER_AUDIT_LOG_JSON_FILTERING_NOT_ENABLED): Audit Log filtering has not been installed.
MySQL error code 3211 (ER_AUDIT_LOG_UDF_INSUFFICIENT_PRIVILEGE): Request ignored for '%s'@'%s'. SUPER_ACL needed to perform operation
MySQL error code 3212 (ER_AUDIT_LOG_SUPER_PRIVILEGE_REQUIRED): SUPER privilege required for '%s'@'%s' user.
MySQL error code 3213 (ER_COULD_NOT_REINITIALIZE_AUDIT_LOG_FILTERS): Could not reinitialize audit log filters.
MySQL error code 3214 (ER_AUDIT_LOG_UDF_INVALID_ARGUMENT_TYPE): Invalid argument type
MySQL error code 3215 (ER_AUDIT_LOG_UDF_INVALID_ARGUMENT_COUNT): Invalid argument count
MySQL error code 3216 (ER_AUDIT_LOG_HAS_NOT_BEEN_INSTALLED): audit_log plugin has not been installed using INSTALL PLUGIN syntax.
MySQL error code 3217 (ER_AUDIT_LOG_UDF_READ_INVALID_MAX_ARRAY_LENGTH_ARG_TYPE): Invalid "max_array_length" argument type.
MySQL error code 3218 (ER_AUDIT_LOG_UDF_READ_INVALID_MAX_ARRAY_LENGTH_ARG_VALUE): Invalid "max_array_length" argument value.
MySQL error code 3219 (ER_AUDIT_LOG_JSON_FILTER_PARSING_ERROR): %s
MySQL error code 3220 (ER_AUDIT_LOG_JSON_FILTER_NAME_CANNOT_BE_EMPTY): Filter name cannot be empty.
MySQL error code 3221 (ER_AUDIT_LOG_JSON_USER_NAME_CANNOT_BE_EMPTY): User cannot be empty.
MySQL error code 3222 (ER_AUDIT_LOG_JSON_FILTER_DOES_NOT_EXISTS): Specified filter has not been found.
MySQL error code 3223 (ER_AUDIT_LOG_USER_FIRST_CHARACTER_MUST_BE_ALPHANUMERIC): First character of the user name must be alphanumeric.
MySQL error code 3224 (ER_AUDIT_LOG_USER_NAME_INVALID_CHARACTER): Invalid character in the user name.
MySQL error code 3225 (ER_AUDIT_LOG_HOST_NAME_INVALID_CHARACTER): Invalid character in the host name.
MySQL error code 3226 (WARN_DEPRECATED_MAXDB_SQL_MODE_FOR_TIMESTAMP): With the MAXDB SQL mode enabled, TIMESTAMP is identical with DATETIME. The MAXDB SQL mode is deprecated and will be removed in a future release. Please disable the MAXDB SQL mode and use DATETIME instead.
MySQL error code 3227 (ER_XA_REPLICATION_FILTERS): The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replication slave.
MySQL error code 3228 (ER_CANT_OPEN_ERROR_LOG): Could not open file '%s' for error logging%s%s
MySQL error code 3229 (ER_GROUPING_ON_TIMESTAMP_IN_DST): Grouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.
MySQL error code 3230 (ER_CANT_START_SERVER_NAMED_PIPE): Can't start server : Named Pipe "%s" already in use.


Oracle视角:旁观某电信客户升级/迁移项目

作者为: 

SHOUG成员 – ORACLE ACS高级顾问罗敏

本文永久地址:https://www.askmac.cn/archives/oracle视角:旁观某电信客户升级迁移项目.html

 

 

  1. 不得已而为之的数据库升级和迁移项目

多年来,某省电信运营商虽然对其核心CRM系统进行了持续优化工作,但仍然满足不了业务高速发展需求,尤其是每月出账期系统压力越来越大,故障频频,以至于每当账期来临,局方各级领导、各业务部门和技术人员,以及应用开商和维护保障公司人员都是如坐针毡,甚至如临大敌。

在2015年下半年连续几个月账期均出现不稳定状况之后,各方一致认为数据库系统和应用软件优化工作已经持续了几年,优化空间已经非常有限了,是到了系统软硬件平台升级换代的时候了。

该系统现有硬件平台为HP PA-RISC小型机,数据库版本为10g R2,可见无论硬件还是系统软件都已经属于落后淘汰的技术了,现有硬件配置和性能甚至低于当下最新的X86服务器。作为Oracle公司服务部门,我们更是喋喋不休地讲述数据库升级到11g R2的必要性、可行性、方法论和风险控制策略等,特别是介绍了大量成功案例的实施经验。于是,领导终于下决心了!升级到11g R2并迁移到最高配置的X86服务器!项目实施周期确定为2个月,而且还横跨2016年春节!

本人无意点评领导决策的欠科学,甚至拍脑袋,其实我们深深理解领导的苦衷:已经连续优化这么长时间了,还是艰难度日,万一下个月账期系统彻底瘫痪,怎么办?

于是,尽管各方技术人员向领导和各业务部门力陈升级和迁移的难度和风险,但最后大家还是迫于业务压力,决定赶鸭子上架了!

 

  1. 麻雀虽小,五脏俱全

虽然项目实施周期非常短暂,但局方还是组建了由业务部门、应用开发商、运维团队等多方组成的项目组。在数据库迁移方面决定采用DSG公司的相关产品和技术,在应用测试方面也决定进行全面的功能和压力测试。喏,这就是该项目实施计划表的部分内容:

主要任务 序号 功能描述
准备工作 1 提供主机和数据库集成方案
2 梳理全场景测试方案
3 梳理系统所有的外围接口
4 统计梳理营业库中的所有表,按照表容量大小进行排名(刘书荣)。分析存储空间超过100m的表,若其为分区表,则继续细化到表空间,明确可以优先迁移的表。
5 梳理所有数据库主机的shell、C程序
6 梳理所有was主机的tns和数据源指向,提供上线时所有主机的tns和数据源修改方案。
7 梳理接口机的改造点。
8 梳理所有应用营业主机上部署的脚本,评估是否需要修改。
9 梳理所有应用账务主机上部署的脚本,评估是否需要修改。
10 梳理营业所有应用程序的配置文件和jar包,评估分析是否需要修改,包括BSS、爱营销(代理商)
11 梳理计费账务所有应用程序的配置文件和jar包,评估分析是否需要修改
12 梳理营业数据库所有配置表有无数据库IP指向,评估分析是否需要修改
13 梳理计费账务数据库所有配置表有无数据库IP指向,评估分析是否需要修改
14 梳理mq等内部接口改造点。
15 局方确认crm库上的job和dblink由应用开发商完成迁移
硬件部署 16 硬件到货
17 完成上架加电,达到可以交付实施集成标准
18 环境集成实施完毕,可以进行迁移工作
数据迁移 19 DSG队列规划,拆分复制同步范围
20 活动数据同步,活动数据部分,这里按照40%的数据量是静态数据估算,且按照6个并发任务估算,每小时能够导出的数据为250GB左右,CPU占用2个cpu,MEM为 1GB,IO资源估算为85MB/s。如果按现在CRM库的压力,我们建议使用1-2个通道来导出数据,可能时间上不能保障在2月14日前一定同步完成。
21 历史数据同步
测试环境应用搭建与联调 22 迁移应用开发商负责的数据库对象
23 数据库对象完整性核查
24 应用主机测试准备:将64主机从web页面群组拆下来,调整数据源和TNS指向,在主机上部署job、工作流、外围接口程序。
25 修改新搭建数据库内配置表
26 修改各个接口程序配置指向
27 在新搭建的数据库主机上部署shell、C程序进行测试;
28 调整测试环境MQ程序等内部接口配置指向;
29 调整账务测试环境dblink指向、账务主机TNS配置指向
30 协调oss、ocs配合测试
31 根据测试方案全流程测试
32 估算压力测试需要多少台主机,向局方提出申请,申请多台主机进行测试。

上述计划表由应用开发商主要从应用整体角度提出,尽管我们省略了原有表格中局方负责人、厂商负责人、预计完成时间等敏感信息,但大家还是一定能感受到升级/迁移项目的复杂性:硬件、网络、系统软件、数据库软件、应用软件… …面面俱到,一个也不能少,真是个庞大的系统工程。

数据由DSG迁移了,应用开发商负责应用功能和压力测试,作为Oracle服务团队的我们还能做什么呢?难道就是安装一下Linux平台的11g R2 RAC,然后提供一些现场技术支持吗?喏,这就是我们制定的Oracle服务计划:

 

序号 主要任务 功能描述
1 11g R2 RAC安装和配置检查和完善服务 负责2台新服务器的11.2.0.4 RAC软件安装,以及Oracle公司推荐的补丁安装,并基于Oracle最佳实践经验以及其它客户的实施经验,对数据库初始化参数和隐含参数进行检查和完善。
2 11g R2 RAC服务器的替换 通过RAC增加节点、删除节点操作,实现对RAC服务器的替换
3 性能优化和性能管理方案设计和测试 性能优化和性能管理方案设计,特别是11g SPA技术方案的设计和测试
4 正式环境上线前封装检查及性能基线收集 针对新建CRM系统,通过ORACHK等工具进行全面的配置检查和封版检查,并进行相应的完善,同时进行性能基线收集。
5 正式迁移和割接期间技术支持 新建CRM系统正式上线期间现场技术支持

 

可见,作为Oracle服务实施团队,我们的优势主要发挥在两个方面:第一就是在Oracle数据库环境安装和确保稳定性方面,包括11g R2 RAC专业化的安装、补丁分析和实施、初始化参数和隐含参数的设置等。第二个方面则是Oracle服务团队的另一个独特优势,因为我们深知升级和迁移项目最大的风险其实是来自于应用软件的性能衰减,而Oracle从11g开始推出了SPA工具,即通过该工具,可进行升级前后的应用性能对比分析,这样在测试阶段就能提前诊断出执行计划变化和性能衰减的SQL语句,并加以优化和改造,从而降低升级之后性能问题的出现概率,确保整个升级项目实施的成功。

各方不乏经验、方法论和人力资源投入,局方也提供了测试环境,但是大家都痛感最缺乏的只有一样东西:时间!时间!时间!在两个月的项目实施周期中,刨去春节假期,还有DSG的两次数据同步时间窗口(一次是将现有生产系统数据同步到测试环境,一次是正式割接前的数据同步),有效测试时间连一个月都不到!

 

  1. 艰难的测试过程

就在这一个月不到的时间里,各方要开展应用功能测试、应用压力测试,还有SPA测试。由于工期和项目计划组织问题,各项应用测试还与DSG的数据同步测试出现了时间上的重叠和冲突。于是,数据同步尚未完成,索引还未同步过去呢,压力测试和SPA测试就开始了,这些测试哪能跑得下去?于是,测试初期各方在不断磨合,尤其是解决各类数据同步问题,宝贵的测试时间又一点点流失掉了,真是欲速不达。经验啊!

测试期间正好横跨2016年春节,各方人员依然以饱满的工作激情、可贵的职业精神,协同作战,每天大家几乎都统一加班到晚上11:00,基本圆满完成了各类测试任务。作为Oracle服务团队,我们也第一次为该客户展现了SPA工具的价值:通过SPA测试,我们发现了若干条SQL语句出现了性能衰减,并加以有效解决,防止了这些问题在正式割接上线时爆发。

1个月的测试时间不知不觉就这么过去了。真是成也萧何,败也萧何。不久之后的正式割接期间的事实证明:大量的测试付出,的确有效地防范了各类问题的发生,但也正是因为测试时间太短,导致测试工作的不充分,尤其是当时对测试期间发现的问题没有深入探究,为正式割接埋下了深深的隐患!

 

  1. 惊心动魄的正式上线割接

大家在倾情投入了近两个月之后,终于以兴奋同时也是忐忑不安的心情,迎来了正式升级/迁移的割接上线日子。于是,各路神仙云集客户现场,本人作为旁观者也亲眼目睹了整个割接上线过程的跌宕起伏和惊心动魄。兴奋、刺激、纠结、无奈、痛苦、开心、喜悦、感慨,无数情感和心境在短短的2天多时间内不断变换,实乃精彩的人生写照!且听下面的娓娓到来。

上线第一天上午业务刚开始,似乎总体还算正常,但作为Oracle服务团队,包括我自己在内还是发现了一些SQL语句出现了性能衰减,好在我们已经有预案,例如多数语句的性能衰减是由于优化器改变为CBO之后出现的执行计划变化,于是我们采取了删除相关表统计数据,暂时回退到RBO的策略,留待事后再解决。事实证明,相比后面将要表述的系统层面问题,SQL语句问题仅仅是局部性问题而已。

就在第一天上午10:00多业务压力逐渐增加之后,我们首先获悉了前台应用反应非常慢的投诉,其次我们发现数据库服务器压力并不大,而在数据库和中间件层面均发现了网络问题,例如数据库服务器的公网延时居然达到了50ms!而私网也出现了丢包问题。由于硬件厂商网络工程师第一天晚上才能赶到现场,大家只能在等待、无奈、无助,甚至煎熬的心情中度过第一个白天,业务更是缓慢爬行了一整天。

事后我们回想起来,其实在压力测试阶段,大家已经发现了公网延时和私网丢包问题,甚至还导致了RAC宕机,但的确由于测试周期太短,这些问题都没有深入探究其根本原因,就这么带病上岗了。经验教训啊!

好在网络工程师第一天晚上赶到现场之后,很快诊断出网络问题,在调整、配置了几个网络参数之后,网络延时和丢包问题解决了。于是,大家又以轻松、期盼的心情迎来了第二天的业务。可是,这种愉悦的心情几乎是稍纵即逝,第二天上午随着业务高峰的来临,数据库服务器不堪重负,Top显示的Load居然达到500以上,IO Wait更是高达50%!经验告诉我们,IO Wait超过10%就不正常了,难道I/O压力很大,抑或存储系统I/O能力不够、配置不当?大家很快就否定了这些判断,而事实上数据库服务器中最消耗资源的根本不是Oracle进程,而是root用户下的CPU调度程序,这属于主机或操作系统层面问题,硬件厂商工程师在倾力分析和解决中,而第二天的业务比第一天更加艰难,全省CRM系统前端几乎完全瘫痪!

到了第二天日终,问题依然如故,领导终于做出了最简单,事后也证明是最有效的决策:换机器!于是,各方又开始通宵达旦地协同工作了,Oracle服务团队具体负责RAC环境下的删除节点、增加节点操作。我们的同事事后自我调侃道:我已经成了RAC增删节点的高手了!

第三天立竿见影了:一切都恢复正常!原来的数据库服务器硬件或操作系统到底出现了什么问题?我们作为旁观者,无权评述。但听局方系统工程师介绍,这是由于Linux处理中断机制跟UNIX不一样,大部分资源都消耗在处理中断上了,并发越大、处理越慢、越来越恶化。测试阶段是否出现过该问题呢?据了解,还真没有出现过,原因就是测试环境的硬件条件有限,没有模拟出生产系统的真实压力。经验啊!真实模拟测试的重要性!

 

  1. 更多的感慨

本人讲述完这个刚刚发生的惊心动魄的升级/迁移故事,无意渲染升级/迁移项目的高风险和难度,更不是要吓退那些对升级操作本来就心存疑虑和担忧的决策者们,而是试图通过这个真实案例的总结,大家来共同来感悟如下的经验教训:

  • Oracle数据库系统升级和迁移的确是一项机遇和风险并存的系统工程,战略上藐视,战术上重视是基本策略。也就是说升级/迁移项目肯定是能成功的,但科学的升级/迁移方法论指导、需求的全面分析、完备的技术方案和全面测试是项目成功的重要保障。
  • 我们虽然一直强调应用性能问题是升级过程中需要特别关注的问题,但相比主机、操作系统、网络等层面而言,SQL语句问题只是局部性问题,而系统层面问题却是全局性问题。任何一个全局性问题的爆发,都将是灾难性的。
  • 真实模拟测试、测试方法、测试手段的重要性,不要放过测试中出现的每一个问题。最后再重复一句名言:无论如何强调测试工作的重要性都不为过。

 

2016年3月27日于高铁上

Oracle RAC集群Grid Infrastructure 启动的五大问题(Doc ID 1526147.1)

适用于:

Oracle Database – Enterprise Edition – 版本 11.2.0.1 和更高版本
Oracle Database Cloud Schema Service – 版本 N/A 和更高版本
Oracle Database Exadata Cloud Machine – 版本 N/A 和更高版本
Oracle Cloud Infrastructure – Database Service – 版本 N/A 和更高版本
Oracle Database Cloud Exadata Service – 版本 N/A 和更高版本
本文档所含信息适用于所有平台

 

用途

本文档的目的是总结可能阻止 Grid Infrastructure (GI) 成功启动的 5 大问题。

 

 

适用范围

本文档仅适用于 11gR2 Grid Infrastructure。

 

要确定 GI 的状态,请运行以下命令:

 

1. $GRID_HOME/bin/crsctl check crs
2. $GRID_HOME/bin/crsctl stat res -t -init
3. $GRID_HOME/bin/crsctl stat res -t
4. ps -ef | egrep 'init|d.bin'

详细信息

 

问题 1:CRS-4639:无法连接 Oracle 高可用性服务,ohasd.bin 未运行或 ohasd.bin 虽在运行但无 init.ohasd 或其他进程

症状:

 

1. 命令“$GRID_HOME/bin/crsctl check crs”返回错误:

 

CRS-4639: Could not contact Oracle High Availability Services

 

 

2. 命令“ps -ef | grep init”不显示类似于如下所示的行:

 

root 4878 1 0 Sep12 ? 00:00:02 /bin/sh /etc/init.d/init.ohasd run

 

 

3. 命令“ps -ef | grep d.bin”不显示类似于如下所示的行:

 

root 21350 1 6 22:24 ? 00:00:01 /u01/app/11.2.0/grid/bin/ohasd.bin reboot


或者它只显示 "ohasd.bin reboot" 进程而没有其他进程

4. 日志 ohasd.log 中出现以下信息:

 

2013-11-04 09:09:15.541: [ default][2609911536] Created alert : (:OHAS00117:) : TIMED OUT WAITING FOR OHASD MONITOR

 

5. 日志 ohasOUT.log 中出现以下信息:

 

2013-11-04 08:59:14 Changing directory to /u01/app/11.2.0/grid/log/lc1n1/ohasd
OHASD starting Timed out waiting for init.ohasd script to start; posting an alert

 

 

6. ohasd.bin 一直处于启动状态,ohasd.log 信息:

 

2014-08-31 15:00:25.132: [  CRSSEC][733177600]{0:0:2} Exception: PrimaryGroupEntry constructor failed to validate group name with error: 0 groupId: 0x7f8df8022450 acl_string: pgrp:spec:r-x
2014-08-31 15:00:25.132: [  CRSSEC][733177600]{0:0:2} Exception: ACL entry creation failed for: pgrp:spec:r-x
2014-08-31 15:00:25.132: [    INIT][733177600]{0:0:2} Dump State Starting ...

 

 

7. 只有ohasd.bin运行,但是ohasd.log没有任何信息。 OS 日志/var/log/messages显示

 

2015-07-12 racnode1 logger: autorun file for ohasd is missing

 

可能的原因:

 

1. 文件“/etc/inittab”并不包含行(对于OL5/RHEL5以及以下版本,内容也会因版本的不同而不同)
h1:35:respawn:/etc/init.d/init.ohasd run >/dev/null 2>&1 </dev/null
2. 未达到运行级别 3,一些 rc3 脚本挂起
3. Init 进程 (pid 1) 并未衍生 /etc/inittab (h1) 中定义的进程,或 init.ohasd 之前的不当输入,如 xx:wait:<process> 阻碍了 init.ohasd 的启动
4. CRS 自动启动已禁用
5. Oracle 本地注册表 ($GRID_HOME/cdata/<node>.olr) 丢失或损坏(root用户执行命令检查 “ocrdump -local /tmp/olr.log”, 文件 /tmp/olr.log 应该包含所有GI进程有关信息,对比一个正常工作的集群环境)
6. root用户之前在”spec”组,但是现在”spec”组被删除,但是旧组仍然记录在OLR中,可以通过OLR dump验证。
7. 节点重启后当init.ohasd启动时 HOSTNAME 为空。


解决方案:

 

1. 将以下行添加至 /etc/inittab (对于OL5/RHEL5以及以下版本)
h1:35:respawn:/etc/init.d/init.ohasd run >/dev/null 2>&1 </dev/null
并以 root 用户身份运行“init q”。 对于Linux OL6/RHEL6, 请参考文档 note 1607600.1
2. 运行命令“ps -ef | grep rc”,并kill看起来受阻的所有 rc3 脚本。
3. 删除 init.ohasd 前的不当输入。如果“init q”未衍生“init.ohasd run”进程,请咨询 OS 供应商
4. 启用 CRS 自动启动:
# crsctl enable crs
# crsctl start crs
5. 以 root 用户身份从备份中恢复 OLR(Oracle 本地注册表):(参考Note 1193643.1)
# crsctl stop crs -f
# touch $GRID_HOME/cdata/<node>.olr
# chown root:oinstall $GRID_HOME/cdata/<node>.olr
# ocrconfig -local -restore$GRID_HOME/cdata/<node>/backup_<date>_<num>.olr
# crsctl start crs如果出于某种原因,OLR 备份不存在,要重建 OLR 就需要以 root 用户身份执行 deconfig 并重新运行 root.sh:
# $GRID_HOME/crs/install/rootcrs.pl -deconfig -force
# $GRID_HOME/root.sh

6. 需要重新初始化/创建OLR, 使用命令与前面创建OLR命令相同。

 

7. 重启init.ohasd进程或者在init.ohasd中添加”sleep 30″,这样允许在启动集群前输出hostname信息,参考Note 1427234.1.

 

8. 如果上面方法不能解决问题,请检查OS messages中有关ohasd.bin日志信息,按照OS message中提示信息,

设置LD_LIBRARY_PATH = <GRID_HOME>/lib,并且手动执行crswrapexece.pl命令。

 

问题 2:CRS-4530:联系集群同步服务守护进程时出现通信故障,ocssd.bin 未运行

 

症状:

 

1. 命令“$GRID_HOME/bin/crsctl check crs”返回错误:

CRS-4638: Oracle High Availability Services is online
CRS-4535: Cannot communicate with Cluster Ready Services
CRS-4530: Communications failure contacting Cluster Synchronization Services daemon
CRS-4534: Cannot communicate with Event Manager

 

2. 命令“ps -ef | grep d.bin”不显示类似于如下所示的行:

 

 

oragrid 21543 1 1 22:24 ? 00:00:01 /u01/app/11.2.0/grid/bin/ocssd.bin

 

3. ocssd.bin 正在运行,但在 ocssd.log 中显示消息“CLSGPNP_CALL_AGAIN”后又中止运行

 

4. ocssd.log 显示如下内容:

 

   2012-01-27 13:42:58.796: [ CSSD][19]clssnmvDHBValidateNCopy: node 1, racnode1, has a disk HB, but no network HB, DHB has rcfg 223132864, wrtcnt, 1112, LATS 783238209,
lastSeqNo 1111, uniqueness 1327692232, timestamp 1327693378/787089065

 

5. 对于 3 个或更多节点的情况,2 个节点形成的集群一切正常,但是,当第 3 个节点加入时就出现故障,ocssd.log 显示如下内容:

 

   2012-02-09 11:33:53.048: [ CSSD][1120926016](:CSSNM00008:)clssnmCheckDskInfo: Aborting local node to avoid splitbrain. Cohort of 2 nodes with leader 2, racnode2, is smaller than
cohort of 2 nodes led by node 1, racnode1, based on map type 2
2012-02-09 11:33:53.048: [ CSSD][1120926016]###################################
2012-02-09 11:33:53.048: [ CSSD][1120926016]clssscExit: CSSD aborting from thread clssnmRcfgMgrThread

 

6. 10 分钟后 ocssd.bin 启动超时

 

   2012-04-08 12:04:33.153: [    CSSD][1]clssscmain: Starting CSS daemon, version 11.2.0.3.0, in (clustered) mode with uniqueness value 1333911873
......
2012-04-08 12:14:31.994: [    CSSD][5]clssgmShutDown: Received abortive shutdown request from client.
2012-04-08 12:14:31.994: [    CSSD][5]###################################
2012-04-08 12:14:31.994: [    CSSD][5]clssscExit: CSSD aborting from thread GMClientListener
2012-04-08 12:14:31.994: [    CSSD][5]###################################
2012-04-08 12:14:31.994: [    CSSD][5](:CSSSC00012:)clssscExit: A fatal error occurred and the CSS daemon is terminating abnormally

 

 

7. alert<node>.log 显示:

 

 

2014-02-05 06:16:56.815
[cssd(3361)]CRS-1714:Unable to discover any voting files, retrying discovery in 15 seconds; Details at (:CSSNM00070:) in /u01/app/11.2.0/grid/log/bdprod2/cssd/ocssd.log
...
2014-02-05 06:27:01.707
[ohasd(2252)]CRS-2765:Resource 'ora.cssdmonitor' has failed on server 'bdprod2'.
2014-02-05 06:27:02.075
[ohasd(2252)]CRS-2771:Maximum restart attempts reached for resource 'ora.cssd'; will not restart.
>

 

可能的原因:

 

1. 表决磁盘丢失或无法访问
2. 多播未正常工作(对于版本11.2.0.2,这是正常的情况。对于 11.2.0.3 PSU5/PSU6/PSU7 和 12.1.0.1 版本,是由于Bug 16547309)
3. 私网未工作,ping 或 traceroute <private host> 显示无法访问目标。或虽然 ping/traceroute 正常工作,但是在私网中启用了防火墙
4. gpnpd 未出现,卡在 dispatch 线程中, Bug 10105195
5. 通过 asm_diskstring 发现的磁盘太多,或由于 Bug 13454354 导致扫描太慢(仅在 Solaris 11.2.0.3 上出现)


解决方案:

 

1. 通过检查存储存取性、磁盘权限等恢复表决磁盘存取。如果表决盘在 OS 级别无法访问,请敦促操作系统管理员恢复磁盘访问。
如果 OCR ASM 磁盘组中的 voting disk已经丢失,以独占模式启动 CRS,并重建表决磁盘:
# crsctl start crs -excl
# crsctl replace votedisk <+OCRVOTE diskgroup>
2. 请参考 Document 1212703.1 ,了解多播功能的测试及修正。对于版本 11.2.0.3 PSU5/PSU6/PSU7 和12.1.0.1, 您可以为集群私网启用多播或者应用补丁16547309 或最新的PSU。更多信息请参考Document 1564555.1
3. 咨询网络管理员,恢复私网访问或禁用私网防火墙(对于 Linux,请检查服务 iptables 状态和服务 ip6tables 状态)
4. 终止正常运行节点上的 gpnpd.bin 进程,请参考 Document 10105195.8
一旦以上问题得以解决,请重新启动 Grid Infrastructure。
如果 ping/traceroute 对私网均可用,但是问题发生在从 11.2.0.1 至 11.2.0.2 升级过程中,请检查Bug 13416559 获取解决方法。
5. 通过提供更加具体的 asm_diskstring,限制 ASM 扫描磁盘的数量,请参考 bug 13583387
对于 Solaris 11.2.0.3,请应用补丁 13250497,请参阅 Document 1451367.1.

 

问题 3:CRS-4535:无法与集群就绪服务通信,crsd.bin 未运行

 

症状:

 

1. 命令“$GRID_HOME/bin/crsctl check crs”返回错误:

 

CRS-4638: Oracle High Availability Services is online
CRS-4535: Cannot communicate with Cluster Ready Services
CRS-4529: Cluster Synchronization Services is online
CRS-4534: Cannot communicate with Event Manager

 

2. 命令“ps -ef | grep d.bin”不显示类似于如下所示的行:

 

root 23017 1 1 22:34 ? 00:00:00 /u01/app/11.2.0/grid/bin/crsd.bin reboot

 

3. 即使存在 crsd.bin 进程,命令“crsctl stat res -t –init”仍然显示:

 

ora.crsd
1    ONLINE     INTERMEDIATE

 

可能的原因:

 

1. ocssd.bin 未运行,或资源 ora.cssd 不在线
2. +ASM<n> 实例无法启动
3. OCR 无法访问
4. 网络配置已改变,导致 gpnp profile.xml 不匹配
5. Crsd 的 $GRID_HOME/crs/init/<host>.pid 文件已被手动删除或重命名,crsd.log 显示:“Error3 -2 writing PID to the file”
6. ocr.loc 内容与其他集群节点不匹配。crsd.log 显示:“Shutdown CacheLocal. my hash ids don’t match”
7.当巨帧(Jumbo Frame)在集群私网被启用时,节点私网能够通过“ping”命令互相联通,但是无法通过巨帧尺寸ping通(例如:ping -s 8900 <私网 ip>)或者
集群中的其他节点已经配置巨帧(MTU: 9000),而出现问题的节点没有配置巨帧(MTU:1500)。
8.对于平台 AIX 6.1 TL08 SP01 和 AIX 7.1 TL02 SP01,由于多播数据包被截断。

解决方案:

 

 

1. 检查问题 2 的解决方案,确保 ocssd.bin 运行且 ora.cssd 在线
2. 对于 11.2.0.2 以上版本,确保资源 ora.cluster_interconnect.haip 在线,请参考 Document 1383737.1 了解和HAIP相关的,ASM无法启动的问题。
3. 确保 OCR 磁盘可用且可以访问。如果由于某种原因丢失 OCR,请参考 Document 1062983.1 了解如何恢复OCR。
4. 恢复网络配置,与 $GRID_HOME/gpnp/<node>/profiles/peer/profile.xml 中定义的接口相同,请参考Document 283684.1 了解如何修改私网配置。
5. 请使用 touch 命令,在 $GRID_HOME/crs/init 目录下创建名为 <host>.pid 的文件。
对于 11.2.0.1,该文件归 <grid> 用户所有。
对于 11.2.0.2,该文件归 root 用户所有。
6. 使用 ocrconfig 命令修正 ocr.loc 内容:
例如,作为 root 用户:
# ocrconfig -repair -add +OCR2 (添加条目)
# ocrconfig -repair -delete +OCR2 (删除条目)
以上命令需要 ohasd.bin 启动并运行 。一旦以上问题得以解决,请通过以下命令重新启动 GI 或启动 crsd.bin:
# crsctl start res ora.crsd -init
7. 如果巨帧只是在网卡层面配置了巨帧,请敦促网络管理员在交换机层面启动巨帧。如果您不需要使用巨帧,请将集群中所有节点的私网MTU值设置为1500,之后重启所有节点。
8. 对于平台 AIX 6.1 TL08 SP01 和 AIX 7.1 TL02 SP01,根据下面的note应用对应的 AIX 补丁
Document 1528452.1 AIX 6.1 TL8 or 7.1 TL2: 11gR2 GI Second Node Fails to Join the Cluster as CRSD and EVMD are in INTERMEDIATE State

 

 

问题 4:Agent 或者 mdnsd.bin, gpnpd.bin, gipcd.bin 未运行

症状:

 

1. orarootagent 未运行. ohasd.log 显示:

2012-12-21 02:14:05.071: [    AGFW][24] {0:0:2} Created alert : (:CRSAGF00123:) :  Failed to start the agent process: /grid/11.2.0/grid_2/bin/orarootagent Category: -1 Operation: fail Loc: canexec2 OS error: 0 Other : no exe permission, file [/grid/11.2.0/grid_2/bin/orarootagent]
2. mdnsd.bin, gpnpd.bin 或者 gipcd.bin 未运行, 以下是 mdnsd log中显示的一个例子:
2012-12-31 21:37:27.601: [  clsdmt][1088776512]Creating PID [4526] file for home /u01/app/11.2.0/grid host lc1n1 bin mdns to /u01/app/11.2.0/grid/mdns/init/
2012-12-31 21:37:27.602: [  clsdmt][1088776512]Error3 -2 writing PID [4526] to the file []
2012-12-31 21:37:27.602: [  clsdmt][1088776512]Failed to record pid for MDNSD

或者

2012-12-31 21:39:52.656: [  clsdmt][1099217216]Creating PID [4645] file for home /u01/app/11.2.0/grid host lc1n1 bin mdns to /u01/app/11.2.0/grid/mdns/init/
2012-12-31 21:39:52.656: [  clsdmt][1099217216]Writing PID [4645] to the file [/u01/app/11.2.0/grid/mdns/init/lc1n1.pid]
2012-12-31 21:39:52.656: [  clsdmt][1099217216]Failed to record pid for MDNSD

3. oraagent 或 appagent 未运行, 日志crsd.log显示:

 

2012-12-01 00:06:24.462: [    AGFW][1164069184] {0:2:27} Created alert : (:CRSAGF00130:) :  Failed to start the agent /u01/app/grid/11.2.0/bin/appagent_oracle

 

 

可能的原因:

 

1. orarootagent 缺少执行权限
2. 缺少进程相关的 <node>.pid 文件或者这个文件的所有者/权限不对
3. GRID_HOME 所有者/权限不对


解决方案:

1. 和一个好的GRID_HOME比较所有者/权限,并做相应的改正,或者以root用户执行:
# cd <GRID_HOME>/crs/install
# ./rootcrs.pl -unlock
# ./rootcrs.pl -patch


这将停止集群软件,对需要的文件的所有者/权限设置为root用户,并且重启集群软件。
2. 如果对应的 <node>.pid 不存在, 就用touch命令创建一个具有相应所有者/权限的文件, 否则就按要求改正文件<node>.pid的所有者/权限, 然后重启集群软件.
这里是<GRID_HOME>下,所有者属于root:root 权限 644的<node>.pid 文件列表:

./ologgerd/init/<node>.pid
./osysmond/init/<node>.pid
./ctss/init/<node>.pid
./ohasd/init/<node>.pid
./crs/init/<node>.pid
所有者属于<grid>:oinstall,权限644
./mdns/init/<node>.pid
./evm/init/<node>.pid
./gipc/init/<node>.pid
./gpnp/init/<node>.pid3.
对第3种原因,请参考解决方案1

 

问题 5:ASM 实例未启动,ora.asm 不在线

症状:

1. 命令“ps -ef | grep asm”不显示 ASM 进程

2. 命令“crsctl stat res -t –init”显示:

 

ora.asm
1    ONLINE    OFFLINE


可能的原因:

 

1. ASM spfile 损坏
2. ASM discovery string不正确,因此无法发现 voting disk/OCR
3. ASMlib 配置问题
4. ASM实例使用不同的cluster_interconnect, 第一个节点 HAIP OFFLINE 导致第二个节点ASM实例无法启动


解决方案:

1. 创建临时 pfile 以启动 ASM 实例,然后重建 spfile,请参考 Document 1095214.1 了解更多详细信息。
2. 请参考 Document 1077094.1 以更正 ASM discovery string。
3. 请参考 Document 1050164.1 以修正 ASMlib 配置。
4. 请参考 Document 1383737.1 作为解决方案。请参考 Document 1210883.1 了解更多HAIP信息

 

要进一步调试 GI 启动问题,请参考 Document 1050908.1 Troubleshoot Grid Infrastructure Startup Issues.

诊断 Oracle RAC集群Grid Infrastructure 启动问题 (Doc ID 1623340.1)

适用于:

Oracle Database – Enterprise Edition – 版本 11.2.0.1 和更高版本
Oracle Database Cloud Schema Service – 版本 N/A 和更高版本
Oracle Database Exadata Cloud Machine – 版本 N/A 和更高版本
Oracle Cloud Infrastructure – Database Service – 版本 N/A 和更高版本
Oracle Database Backup Service – 版本 N/A 和更高版本
本文档所含信息适用于所有平台

 

 

用途

 

本文提供了诊断 11GR2 和 12C Grid Infrastructure 启动问题的方法。对于新安装的环境(root.sh 和 rootupgrade.sh 执行过程中)和有故障的旧环境都适用。针对 root.sh 的问题,我们可以参考 note 1053970.1 来获取更多的信息。

 

 

适用范围

 

本文适用于集群/RAC数据库管理员和 Oracle 支持工程师。

 

详细信息

 

启动顺序:

 

简而言之,操作系统负责启动 ohasd 进程,ohasd 进程启动 agents 用来启动守护进程(gipcd, mdnsd, gpnpd, ctssd, ocssd, crsd, evmd ,asm …) ,crsd 启动 agents 用来启动用户资源(database,SCAN,Listener 等)。

 

如果需要了解更详细的 Grid Infrastructure Cluster 启动顺序,请参阅 note 1053147.1。

 

集群状态

查询集群和守护进程的状态:

 

 

$GRID_HOME/bin/crsctl check crs

CRS-4638: Oracle High Availability Services is online

CRS-4537: Cluster Ready Services is online

CRS-4529: Cluster Synchronization Services is online

CRS-4533: Event Manager is online

$GRID_HOME/bin/crsctl stat res -t -init
--------------------------------------------------------------------------------
NAME           TARGET  STATE        SERVER                   STATE_DETAILS
--------------------------------------------------------------------------------
Cluster Resources
--------------------------------------------------------------------------------
ora.asm
1        ONLINE  ONLINE       rac1                  Started
ora.crsd
1        ONLINE  ONLINE       rac1
ora.cssd
1        ONLINE  ONLINE       rac1
ora.cssdmonitor
1        ONLINE  ONLINE       rac1
ora.ctssd
1        ONLINE  ONLINE       rac1                  OBSERVER
ora.diskmon
1        ONLINE  ONLINE       rac1
ora.drivers.acfs
1        ONLINE  ONLINE       rac1
ora.evmd
1        ONLINE  ONLINE       rac1
ora.gipcd
1        ONLINE  ONLINE       rac1
ora.gpnpd
1        ONLINE  ONLINE       rac1
ora.mdnsd
1        ONLINE  ONLINE       rac1

 

 

对于11.2.0.2 和以上的版本,会有以下两个额外的进程:

 

ora.cluster_interconnect.haip
1        ONLINE  ONLINE       rac1
ora.crf
1        ONLINE  ONLINE       rac1

 

 

对于11.2.0.3 以上的非EXADATA的系统,ora.diskmon会处于offline的状态,如下:

 

ora.diskmon
1        OFFLINE  OFFLINE       rac1

 

 

 

对于 12c 以上的版本, 会出现ora.storage资源:

 

ora.storage
1 ONLINE ONLINE racnode1 STABLE

 

 

如果守护进程 offline 我们可以通过以下命令启动:

 

$GRID_HOME/bin/crsctl start res ora.crsd -init

 

问题 1: OHASD 无法启动

 

由于 ohasd.bin 的责任是直接或者间接的启动集群所有的其它进程,所以只有这个进程正常启动了,其它的进程才能起来,如果 ohasd.bin 的进程没有起来,当我们检查资源状态的时候会报错 CRS-4639 (Could not contact Oracle High Availability Services); 如果 ohasd.bin 已经启动了,而再次尝试启时,错误 CRS-4640 会出现;如果它启动失败了,那么我们会看到以下的错误信息:

 

CRS-4124: Oracle High Availability Services startup failed.
CRS-4000: Command Start failed, or completed with errors.

自动启动 ohasd.bin 依赖于以下的配置:

1. 操作系统配置了正确的 run level:

OS 需要在 CRS 启动之前设置成指定的 run level 来确保 CRS 的正常启动。

我们可以通过以下方式找到 CRS 需要 OS 设置的 run level:

 

 

cat /etc/inittab|grep init.ohasd
h1:35:respawn:/etc/init.d/init.ohasd run >/dev/null 2>&1 </dev/null

注意:Oracle Linux 6 (OL6) 和 Red Hat Linux 6 (RHEL6) 上已经不使用inittab,init.ohasd已经被/etc/init/oracle-ohasd.conf替代,不过 /etc/init.d/init.ohasd run 应该仍然可用。Oracle Linux 7 (以及 Red Hat Linux 7) 使用 systemd 来启动/关闭服务 (比如: /etc/systemd/system/oracle-ohasd.service)

以上例子展示了,CRS 需要 OS 运行在 run level 3 或 5;请注意,由于操作系统的不同,CRS 启动需要的 OS 的 run level 也会不同。

找到当前 OS 正在运行的 run level:

 

who -r

 

 

2. “init.ohasd run” 启动

 

在 Linux/Unix 平台上,由于”init.ohasd run” 是配置在 /etc/inittab中,进程 init(进程id 1,linux,Solars和HP-UX上为/sbin/init ,Aix上为/usr/sbin/init)会启动并且产生”init.ohasd run”进程,如果这个过程失败了,就不会有”init.ohasd run”的启动和运行,ohasd.bin 也是无法启动的:

 

ps -ef|grep init.ohasd|grep -v grep
root      2279     1  0 18:14 ?        00:00:00 /bin/sh /etc/init.d/init.ohasd run

注意:Oracle Linux 6 (OL6) 和 Red Hat Linux 6 (RHEL6) 上已经不使用inittab,init.ohasd已经被/etc/init/oracle-ohasd.conf替代,不过 /etc/init.d/init.ohasd run 应该仍然可用。Oracle Linux 7 (以及 Red Hat Linux 7) 使用 systemd 来启动/关闭服务 (比如: /etc/systemd/system/oracle-ohasd.service)

如果任何 rc Snncommand 的脚本(在 rcn.d 中,如 S98gcstartup)在启动的过程中挂死,此时 init 的进程可能无法启动”/etc/init.d/init.ohasd run”;您需要寻求 OS 厂商的帮助,找到为什么 Snncommand 脚本挂死或者无法正常启动的原因;

错误”[ohasd(<pid>)] CRS-0715:Oracle High Availability Service has timed out waiting for init.ohasd to be started.” 可能会在 init.ohasd 无法在指定时间内启动后出现

如果系统管理员无法在短期内找到 init.ohasd 无法启动的原因,以下办法可以作为一个临时的解决办法:

 

cd <location-of-init.ohasd>
nohup ./init.ohasd run &

3. Clusterware 自动启动;–自动启动默认是开启的

默认情况下 CRS 自动启动是开启的,我们可以通过以下方式开启:

 

$GRID_HOME/bin/crsctl enable crs

 

检查这个功能是否被开启:

 

$GRID_HOME/bin/crsctl config crs

如果以下信息被输出在OS的日志中

 

Feb 29 16:20:36 racnode1 logger: Oracle Cluster Ready Services startup disabled.
Feb 29 16:20:36 racnode1 logger: Could not access /var/opt/oracle/scls_scr/racnode1/root/ohasdstr

原因是由于这个文件不存在或者不可访问,产生这个问题的原因一般是人为的修改或者是打 GI 补丁的过程中使用了错误的 opatch (如:使用 Solaris 平台上的 opatch 在 Linux 上打补丁)

4. syslogd 启动并且 OS 能够执行 init 脚本 S96ohasd

 

节点启动之后,OS 可能停滞在一些其它的 Snn 的脚本上,所以可能没有机会执行到脚本 S96ohasd;如果是这种情况,我们不会在 OS 日志中看到以下信息

 

Jan 20 20:46:51 rac1 logger: Oracle HA daemon is enabled for autostart.

如果在 OS 日志里看不到上面的信息,还有一种可能是 syslogd((/usr/sbin/syslogd)没有被完全启动。GRID 在这种情况下也是无法正常启动的,这种情况不适用于 AIX 的平台。

为了了解 OS 启动之后是否能够执行 S96ohasd 脚本,可以按照以下的方法修改该脚本:

 

From:

    case `$CAT $AUTOSTARTFILE` in
enable*)
$LOGERR "Oracle HA daemon is enabled for autostart."

To:

    case `$CAT $AUTOSTARTFILE` in
enable*)
/bin/touch /tmp/ohasd.start."`date`"
$LOGERR "Oracle HA daemon is enabled for autostart."

重启节点后,如果您没有看到文件 /tmp/ohasd.start.timestamp 被创建,那么就是说 OS 停滞在其它的 Snn 的脚本上。如果您能看到 /tmp/ohasd.start.timestamp 生成了,但是”Oracle HA daemon is enabled for autostart”没有写入到messages 文件里,就是 syslogd 没有被完全启动了。以上的两种情况,您都需要寻求系统管理员的帮助,从 OS 的层面找到问题的原因,对于后一种情况,有个临时的解决办法是“休眠”2分钟, 按照以下的方法修改 ohasd 脚本:

 

 

From:

    case `$CAT $AUTOSTARTFILE` in
enable*)
$LOGERR "Oracle HA daemon is enabled for autostart."

To:

    case `$CAT $AUTOSTARTFILE` in
enable*)
/bin/sleep 120
$LOGERR "Oracle HA daemon is enabled for autostart."


5.
 GRID_HOME 所在的文件系统在执行初始化脚本 S96ohasd 的时候在线;正常情况下一旦 S96ohasd 执行结束,我们会在 OS message 里看到以下信息:

 

Jan 20 20:46:51 rac1 logger: Oracle HA daemon is enabled for autostart.
..
Jan 20 20:46:57 rac1 logger: exec /ocw/grid/perl/bin/perl -I/ocw/grid/perl/lib /ocw/grid/bin/crswrapexece.pl /ocw/grid/crs/install/s_crsconfig_rac1_env.txt /ocw/grid/bin/ohasd.bin "reboot"

 

 

如果您只看到了第一行,没有看到最后一行的信息,很可能是 GRID_HOME 所在的文件系统在脚本 S96ohasd 执行的时候还没有正常挂载。

 

6. Oracle Local Registry  (OLR, $GRID_HOME/cdata/${HOSTNAME}.olr) 有效并可以正常读写

 

 

ls -l $GRID_HOME/cdata/*.olr
-rw------- 1 root  oinstall 272756736 Feb  2 18:20 rac1.olr

如果 OLR 是不可读写的或者损坏的,我们会在 ohasd.log 中看到以下的相关信息

 

..
2010-01-24 22:59:10.470: [ default][1373676464] Initializing OLR
2010-01-24 22:59:10.472: [  OCROSD][1373676464]utopen:6m':failed in stat OCR file/disk /ocw/grid/cdata/rac1.olr, errno=2, os err string=No such file or directory
2010-01-24 22:59:10.472: [  OCROSD][1373676464]utopen:7:failed to open any OCR file/disk, errno=2, os err string=No such file or directory
2010-01-24 22:59:10.473: [  OCRRAW][1373676464]proprinit: Could not open raw device
2010-01-24 22:59:10.473: [  OCRAPI][1373676464]a_init:16!: Backend init unsuccessful : [26]
2010-01-24 22:59:10.473: [  CRSOCR][1373676464] OCR context init failure.  Error: PROCL-26: Error while accessing the physical storage Operating System error [No such file or directory] [2]
2010-01-24 22:59:10.473: [ default][1373676464] OLR initalization failured, rc=26
2010-01-24 22:59:10.474: [ default][1373676464]Created alert : (:OHAS00106:) :  Failed to initialize Oracle Local Registry
2010-01-24 22:59:10.474: [ default][1373676464][PANIC] OHASD exiting; Could not init OLR

 

或者

 

..
2010-01-24 23:01:46.275: [  OCROSD][1228334000]utread:3: Problem reading buffer 1907f000 buflen 4096 retval 0 phy_offset 102400 retry 5
2010-01-24 23:01:46.275: [  OCRRAW][1228334000]propriogid:1_1: Failed to read the whole bootblock. Assumes invalid format.
2010-01-24 23:01:46.275: [  OCRRAW][1228334000]proprioini: all disks are not OCR/OLR formatted
2010-01-24 23:01:46.275: [  OCRRAW][1228334000]proprinit: Could not open raw device
2010-01-24 23:01:46.275: [  OCRAPI][1228334000]a_init:16!: Backend init unsuccessful : [26]
2010-01-24 23:01:46.276: [  CRSOCR][1228334000] OCR context init failure.  Error: PROCL-26: Error while accessing the physical storage
2010-01-24 23:01:46.276: [ default][1228334000] OLR initalization failured, rc=26
2010-01-24 23:01:46.276: [ default][1228334000]Created alert : (:OHAS00106:) :  Failed to initialize Oracle Local Registry
2010-01-24 23:01:46.277: [ default][1228334000][PANIC] OHASD exiting; Could not init OLR

 

或者

 

..
2010-11-07 03:00:08.932: [ default][1] Created alert : (:OHAS00102:) : OHASD is not running as privileged user
2010-11-07 03:00:08.932: [ default][1][PANIC] OHASD exiting: must be run as privileged user

 

或者

 

ohasd.bin comes up but output of "crsctl stat res -t -init"shows no resource, and "ocrconfig -local -manualbackup" fails

 

或者
..

2010-08-04 13:13:11.102: [   CRSPE][35] Resources parsed
2010-08-04 13:13:11.103: [   CRSPE][35] Server [] has been registered with the PE data model
2010-08-04 13:13:11.103: [   CRSPE][35] STARTUPCMD_REQ = false:
2010-08-04 13:13:11.103: [   CRSPE][35] Server [] has changed state from [Invalid/unitialized] to [VISIBLE]
2010-08-04 13:13:11.103: [  CRSOCR][31] Multi Write Batch processing...
2010-08-04 13:13:11.103: [ default][35] Dump State Starting ...

..

2010-08-04 13:13:11.112: [   CRSPE][35] SERVERS:

:VISIBLE:address{{Absolute|Node:0|Process:-1|Type:1}}; recovered state:VISIBLE. Assigned to no pool

------------- SERVER POOLS:
Free [min:0][max:-1][importance:0] NO SERVERS ASSIGNED

2010-08-04 13:13:11.113: [   CRSPE][35] Dumping ICE contents...:ICE operation count: 0
2010-08-04 13:13:11.113: [ default][35] Dump State Done.

 

 

解决办法就是使用下面的命令,恢复一个好的备份 “ocrconfig -local -restore <ocr_backup_name>”。

默认情况下,OLR 在系统安装结束后会自动的备份在 $GRID_HOME/cdata/$HOST/backup_$TIME_STAMP.olr 。

 

7. ohasd.bin可以正常的访问到网络的 socket 文件:

 

2010-06-29 10:31:01.570: [ COMMCRS][1206901056]clsclisten: Permission denied for (ADDRESS=(PROTOCOL=ipc)(KEY=procr_local_conn_0_PROL))

2010-06-29 10:31:01.571: [  OCRSRV][1217390912]th_listen: CLSCLISTEN failed clsc_ret= 3, addr= [(ADDRESS=(PROTOCOL=ipc)(KEY=procr_local_conn_0_PROL))]
2010-06-29 10:31:01.571: [  OCRSRV][3267002960]th_init: Local listener did not reach valid state

在 Grid Infrastructure 环境中,和 ohasd 有关的 socket 文件属主应该是 root 用户,但是在 Oracle Restart 的环境中,他们应该是属于 grid 用户的,关于更多的关于网络 socket 文件权限和属主,请参考章节”网络 socket 文件,属主和权限” 给出的例子.

 

8. ohasd.bin 能够访问日志文件的位置:

OS messages/syslog 显示以下信息:

 

Feb 20 10:47:08 racnode1 OHASD[9566]: OHASD exiting; Directory /ocw/grid/log/racnode1/ohasd not found.

 

请参考章节”日志位置, 属主和权限”部分的例子,并确定这些必要的目录是否有丢失的,并且是按照正确的权限和属主创建的。

 

9. 节点启动后,在 SUSE Linux 的系统上,ohasd 可能无法启动,此问题请参考 note 1325718.1 – OHASD not Starting After Reboot on SLES

 

10. OHASD 无法启动,使用 “ps -ef| grep ohasd.bin” 显示 ohasd.bin 的进程已经启动,但是 $GRID_HOME/log/<node>/ohasd/ohasd.log 在好几分钟之后都没有任何信息更新,使用 OS 的 truss 工具 可以看到该进程一致在循环的执行关闭从未被打开的文件句柄的操作:

 

 

..
15058/1:         0.1995 close(2147483646)                               Err#9 EBADF
15058/1:         0.1996 close(2147483645)                               Err#9 EBADF
..

通过 ohasd.bin 的 Call stack ,可以看到以下信息:

 

_close  sclssutl_closefiledescriptors  main ..

这是由于 bug 11834289 导致的, 该问题在 11.2.0.3 和之上的版本已经被修复,该 bug 的其它症状还有:集群的进程无法启动,而且做 call stack 和 truss 查看的时候也会看到相同的情况(循环的执行 OS 函数 “close”) . 如果该 bug 发生在启动其它的资源时,我们会看到错误信息: “CRS-5802: Unable to start the agent process” 提示。

 

11. 其它的一些潜在的原因和解决办法请参见 note 1069182.1 – OHASD Failed to Start: Inappropriate ioctl for device

 

12. ohasd.bin 正常启动,但是, “crsctl check crs” 只显示以下一行信息:

 

CRS-4638: Oracle High Availability Services is online

并且命令 “crsctl stat res -p -init” 无法显示任何信息

这个问题是由于 OLR 损坏导致的,请参考 note 1193643.1 进行恢复。

 

13. EL7/OL7上: note 1959008.1 – Install of Clusterware fails while running root.sh on OL7 – ohasd fails to start

 

14. 对于 EL7/OL7, patch 25606616 is needed: TRACKING BUG TO PROVIDE GI FIXES FOR OL7

 

15. 如果 ohasd 仍然无法启动,请参见 ohasd 的日志 <grid-home>/log/<nodename>/ohasd/ohasd.log 和 ohasdOUT.log 来获取更多的信息;

 

问题 2: OHASD Agents  未启动

 

OHASD.BIN 会启动 4 个 agents/monitors 来启动其它的资源:

 

oraagent: 负责启动  ora.asm, ora.evmd, ora.gipcd, ora.gpnpd, ora.mdnsd 等
orarootagent: 负责启动 ora.crsd, ora.ctssd, ora.diskmon, ora.drivers.acfs 等
cssdagent / cssdmonitor: 负责启动 ora.cssd(对应 ocssd.bin) 和 ora.cssdmonitor(对应 cssdmonitor)

如果 ohasd.bin 不能正常地启动以上任何一个 agents,集群都无法运行在正常的状态。

 

1. 通常情况下,agents 无法启动的原因是 agent 的日志或者日志所在的目录没有正确设置属主和权限。

关于日志文件和文件夹的权限和属主设置,请参见章节 “日志文件位置, 属主和权限” 中的介绍。

一个例子是在手工打补丁时忘记执行 “rootcrs.pl -patch/postpatch” 会导致agent启动失败:

 

2015-02-25 15:43:54.350806 : CRSMAIN:3294918400: {0:0:2} {0:0:2} Created alert : (:CRSAGF00123:) : Failed to start the agent process: /ocw/grid/bin/orarootagent Category: -1 Operation: fail Loc: canexec2 OS error: 0 Other : no exe permission, file [/ocw/grid/bin/orarootagent]

2015-02-25 15:43:54.382154 : CRSMAIN:3294918400: {0:0:2} {0:0:2} Created alert : (:CRSAGF00123:) : Failed to start the agent process: /ocw/grid/bin/cssdagent Category: -1 Operation: fail Loc: canexec2 OS error: 0 Other : no exe permission, file [/ocw/grid/bin/cssdagent]

2015-02-25 15:43:54.384105 : CRSMAIN:3294918400: {0:0:2} {0:0:2} Created alert : (:CRSAGF00123:) : Failed to start the agent process: /ocw/grid/bin/cssdmonitor Category: -1 Operation: fail Loc: canexec2 OS error: 0 Other : no exe permission, file [/ocw/grid/bin/cssdmonitor]

 

解决方案是执行缺失的步骤。

 

2. 如果 agent 的二进制文件(oraagent.bin 或者 orarootagent.bin 等)损坏, agent 也将无法启动,从而导致相关的资源也无法启动:

 

2011-05-03 11:11:13.189

[ohasd(25303)]CRS-5828:Could not start agent '/ocw/grid/bin/orarootagent_grid'. Details at (:CRSAGF00130:) {0:0:2} in /ocw/grid/log/racnode1/ohasd/ohasd.log.

2011-05-03 12:03:17.491: [    AGFW][1117866336] {0:0:184} Created alert : (:CRSAGF00130:) :  Failed to start the agent /ocw/grid/bin/orarootagent_grid
2011-05-03 12:03:17.491: [    AGFW][1117866336] {0:0:184} Agfw Proxy Server sending the last reply to PE for message:RESOURCE_START[ora.diskmon 1 1] ID 4098:403
2011-05-03 12:03:17.491: [    AGFW][1117866336] {0:0:184} Can not stop the agent: /ocw/grid/bin/orarootagent_grid because pid is not initialized
..
2011-05-03 12:03:17.492: [   CRSPE][1128372576] {0:0:184} Fatal Error from AGFW Proxy: Unable to start the agent process
2011-05-03 12:03:17.492: [   CRSPE][1128372576] {0:0:184} CRS-2674: Start of 'ora.diskmon' on 'racnode1' failed

..

2011-06-27 22:34:57.805: [    AGFW][1131669824] {0:0:2} Created alert : (:CRSAGF00123:) :  Failed to start the agent process: /ocw/grid/bin/cssdagent Category: -1 Operation: fail Loc: canexec2 OS error: 0 Other : no exe permission, file [/ocw/grid/bin/cssdagent]
2011-06-27 22:34:57.805: [    AGFW][1131669824] {0:0:2} Created alert : (:CRSAGF00126:) :  Agent start failed
..
2011-06-27 22:34:57.806: [    AGFW][1131669824] {0:0:2} Created alert : (:CRSAGF00123:) :  Failed to start the agent process: /ocw/grid/bin/cssdmonitor Category: -1 Operation: fail Loc: canexec2 OS error: 0 Other : no exe permission, file [/ocw/grid/bin/cssdmonitor]

 

解决办法: 您可以和正常节点上的 agent 文件进行比较,并且恢复一个好的副本回来。

 

3. Agent 可能会因为 bug 11834289 而启动失败,伴有错误 “CRS-5802: Unable to start the agent process”, 参考 “OHASD 无法启动”的第10条

4. 参考: note 1964240.1 – CRS-5823:Could not initialize agent framework

 

 

问题 3: OCSSD.BIN 无法启动

 

cssd.bin 的正常启动依赖于以下几个必要的条件:

1. GPnP profile 可正常读写 – gpnpd  需要完全正常启动来为profile服务。

如果 ocssd.bin 能够正常的获取 profile,通常情况下,我们会在 ocssd.log 中看到以下类似的信息:

 

2010-02-02 18:00:16.251: [    GPnP][408926240]clsgpnpm_exchange: [at clsgpnpm.c:1175] Calling "ipc://GPNPD_rac1", try 4 of 500...
2010-02-02 18:00:16.263: [    GPnP][408926240]clsgpnp_profileVerifyForCall: [at clsgpnp.c:1867] Result: (87) CLSGPNP_SIG_VALPEER. Profile verified.  prf=0x165160d0
2010-02-02 18:00:16.263: [    GPnP][408926240]clsgpnp_profileGetSequenceRef: [at clsgpnp.c:841] Result: (0) CLSGPNP_OK. seq of p=0x165160d0 is '6'=6
2010-02-02 18:00:16.263: [    GPnP][408926240]clsgpnp_profileCallUrlInt: [at clsgpnp.c:2186] Result: (0) CLSGPNP_OK. Successful get-profile CALL to remote "ipc://GPNPD_rac1" disco ""

 

 

否则,我们会看到以下信息显示在 ocssd.log 中。

 

2010-02-03 22:26:17.057: [    GPnP][3852126240]clsgpnpm_connect: [at clsgpnpm.c:1100] GIPC gipcretConnectionRefused (29) gipcConnect(ipc-ipc://GPNPD_rac1)
2010-02-03 22:26:17.057: [    GPnP][3852126240]clsgpnpm_connect: [at clsgpnpm.c:1101] Result: (48) CLSGPNP_COMM_ERR. Failed to connect to call url "ipc://GPNPD_rac1"
2010-02-03 22:26:17.057: [    GPnP][3852126240]clsgpnp_getProfileEx: [at clsgpnp.c:546] Result: (13) CLSGPNP_NO_DAEMON. Can't get GPnP service profile from local GPnP daemon
2010-02-03 22:26:17.057: [ default][3852126240]Cannot get GPnP profile. Error CLSGPNP_NO_DAEMON (GPNPD daemon is not running).
2010-02-03 22:26:17.057: [    CSSD][3852126240]clsgpnp_getProfile failed, rc(13)

解决方案是确保 gpnpd 是启动并且正常运行的。

 

2. Voting Disk 可以正常读写

 

在 11gR2 的版本中, ocssd.bin 通过 GPnP profile 中的记录获取 Voting disk 的信息, 如果没有足够多的选举盘是可读写的,那么 ocssd.bin 会终止掉自己。

 

2010-02-03 22:37:22.212: [    CSSD][2330355744]clssnmReadDiscoveryProfile: voting file discovery string(/share/storage/di*)
..
2010-02-03 22:37:22.227: [    CSSD][1145538880]clssnmvDiskVerify: Successful discovery of 0 disks
2010-02-03 22:37:22.227: [    CSSD][1145538880]clssnmCompleteInitVFDiscovery: Completing initial voting file discovery
2010-02-03 22:37:22.227: [    CSSD][1145538880]clssnmvFindInitialConfigs: No voting files found
2010-02-03 22:37:22.228: [    CSSD][1145538880]###################################
2010-02-03 22:37:22.228: [    CSSD][1145538880]clssscExit: CSSD signal 11 in thread clssnmvDDiscThread

 

如果所有节点上的 ocssd.bin 因为以下错误无法启动,这是因为 voting file 正在被修改:

 

2010-05-02 03:11:19.033: [    CSSD][1197668093]clssnmCompleteInitVFDiscovery: Detected voting file add in progress for CIN 0:1134513465:0, waiting for configuration to complete 0:1134513098:0

解决的办法是,参照 note 1364971.1 中的步骤,以 exclusive 模式启动 ocssd.bin。

 

如果选举盘的位置是非 ASM 的设备,它的权限和属主应该是如下显示:

 

-rw-r----- 1 ogrid oinstall 21004288 Feb  4 09:13 votedisk1

 

3. 网络功能是正常的,并且域名解析能够正常工作:

 

如果 ocssd.bin 无法正常的绑定到任何网络上,我们会在 ocssd.log 中看到以下类似的日志信息:

 

2010-02-03 23:26:25.804: [GIPCXCPT][1206540320]gipcmodGipcPassInitializeNetwork: failed to find any interfaces in clsinet, ret gipcretFail (1)
2010-02-03 23:26:25.804: [GIPCGMOD][1206540320]gipcmodGipcPassInitializeNetwork: EXCEPTION[ ret gipcretFail (1) ]  failed to determine host from clsinet, using default
..
2010-02-03 23:26:25.810: [    CSSD][1206540320]clsssclsnrsetup: gipcEndpoint failed, rc 39
2010-02-03 23:26:25.811: [    CSSD][1206540320]clssnmOpenGIPCEndp: failed to listen on gipc addr gipc://rac1:nm_eotcs- ret 39
2010-02-03 23:26:25.811: [    CSSD][1206540320]clssscmain: failed to open gipc endp

如果私网上出现了联通性的故障(包含多播功能关闭),我们会在 ocssd.log 中看到以下类似的日志信息:

 

 

2010-09-20 11:52:54.014: [    CSSD][1103055168]clssnmvDHBValidateNCopy: node 1, racnode1, has a disk HB, but no network HB, DHB has rcfg 180441784, wrtcnt, 453, LATS 328297844, lastSeqNo 452, uniqueness 1284979488, timestamp 1284979973/329344894
2010-09-20 11:52:54.016: [    CSSD][1078421824]clssgmWaitOnEventValue: after CmInfo State  val 3, eval 1 waited 0
..  >>>> after a long delay
2010-09-20 12:02:39.578: [    CSSD][1103055168]clssnmvDHBValidateNCopy: node 1, racnode1, has a disk HB, but no network HB, DHB has rcfg 180441784, wrtcnt, 1037, LATS 328883434, lastSeqNo 1036, uniqueness 1284979488, timestamp 1284980558/329930254
2010-09-20 12:02:39.895: [    CSSD][1107286336]clssgmExecuteClientRequest: MAINT recvd from proc 2 (0xe1ad870)
2010-09-20 12:02:39.895: [    CSSD][1107286336]clssgmShutDown: Received abortive shutdown request from client.
2010-09-20 12:02:39.895: [    CSSD][1107286336]###################################
2010-09-20 12:02:39.895: [    CSSD][1107286336]clssscExit: CSSD aborting from thread GMClientListener
2010-09-20 12:02:39.895: [    CSSD][1107286336]###################################

验证网络是否正常,请参见:note 1054902.1

如果在网络修改后CSSD不能启动,请使用 (“gpnptool get”) 检查gpnp profile里定义的cluster_interconnect和真正的网卡名字是否一致
在11.2.0.1上,如果私网不可用,ocssd.bin可能会使用公网

 

4. 第三方的集群管理软件是启动的 (如果使用了第三方 clusterware)

 

Grid Infrastructure 可以提供所有的集群功能,不需要安装第三方集群软件。但是如果在您的环境里GI是基于第三方的集群管理软件的,那么需要确保CRS启动前第三方的集群管理软件已经启动了,可以使用grid用户执行下面的命令来验证

 

$GRID_HOME/bin/lsnodes -n
racnode1    1
racnode1    0

如果第三方的集群管理软件没有完全正常启动,我们在 ocssd.log 中看到以下类似的日志信息:

 

2010-08-30 18:28:13.207: [    CSSD][36]clssnm_skgxninit: skgxncin failed, will retry
2010-08-30 18:28:14.207: [    CSSD][36]clssnm_skgxnmon: skgxn init failed
2010-08-30 18:28:14.208: [    CSSD][36]###################################
2010-08-30 18:28:14.208: [    CSSD][36]clssscExit: CSSD signal 11 in thread skgxnmon

未安装集群管理软件之前,请使用 grid 用户执行以下操作验证:

 

$INSTALL_SOURCE/install/lsnodes -v

hp-ux上的一个案例: note 2130230.1 – Grid infrastructure startup fails due to vendor Clusterware did not start (HP-UX Service guard)

 

5. 在错误的 GRID_HOME 下执行命令”crsctl”

 

命令”crsctl” 必须在正确的 GRID_HOME 下执行,才能正常启动其它进程,否则我们会看到以下的错误信息提示:

 

2012-11-14 10:21:44.014: [    CSSD][1086675264]ASSERT clssnm1.c 3248
2012-11-14 10:21:44.014: [    CSSD][1086675264](:CSSNM00056:)clssnmvStartDiscovery: Terminating because of the release version(11.2.0.2.0) of this node being lesser than the active version(11.2.0.3.0) that the cluster is at
2012-11-14 10:21:44.014: [    CSSD][1086675264]###################################
2012-11-14 10:21:44.014: [    CSSD][1086675264]clssscExit: CSSD aborting from thread clssnmvDDiscThread#

 

 

 

问题 4: CRSD.BIN 无法启动

 

 

如果”crsctl stat res -t -init”显示 ora.crsd 处于intermediate状态,并且另一个节点正在运行着,那么很可能原因是当前这个节点的crsd.bin无法和另一个节点的master crsd.bin通信。
此时,master crsd.bin很可能有异常,杀掉那个master crsd.bin很可能解决问题。
执行 “grep MASTER crsd.trc” 来找到master crsd.bin在哪个节点运行,杀掉那个节点的crsd.bin
之后crsd.bin会被自动启动,不过其它节点的crsd.bin会变成master crsd.bin

 

crsd.bin 的正常启动依赖于以下几个必要的条件:

 

1. ocssd 已经完全正常启动

如果 ocssd.bin 没有完全正常启动,我们会在 crsd.log 中看到以下提示信息:

 

 

2010-02-03 22:37:51.638: [ CSSCLNT][1548456880]clssscConnect: gipc request failed with 29 (0x16)
2010-02-03 22:37:51.638: [ CSSCLNT][1548456880]clsssInitNative: connect failed, rc 29
2010-02-03 22:37:51.639: [  CRSRTI][1548456880] CSS is not ready. Received status 3 from CSS. Waiting for good status ..

2. OCR 可以正常读写

 

如果 OCR 保存在 ASM 中,那么 ora.asm 资源(ASM 实例) 必须已经启动而且 OCR 所在的磁盘组必须已经被挂载,否则我们在 crsd.log 会看到以下的类似信息:

 

2010-02-03 22:22:55.186: [  OCRASM][2603807664]proprasmo: Error in open/create file in dg [GI]

[  OCRASM][2603807664]SLOS : SLOS: cat=7, opn=kgfoAl06, dep=15077, loc=kgfokge

ORA-15077: could not locate ASM instance serving a required diskgroup

2010-02-03 22:22:55.189: [  OCRASM][2603807664]proprasmo: kgfoCheckMount returned [7]
2010-02-03 22:22:55.189: [  OCRASM][2603807664]proprasmo: The ASM instance is down
2010-02-03 22:22:55.190: [  OCRRAW][2603807664]proprioo: Failed to open [+GI]. Returned proprasmo() with [26]. Marking location as UNAVAILABLE.
2010-02-03 22:22:55.190: [  OCRRAW][2603807664]proprioo: No OCR/OLR devices are usable
2010-02-03 22:22:55.190: [  OCRASM][2603807664]proprasmcl: asmhandle is NULL
2010-02-03 22:22:55.190: [  OCRRAW][2603807664]proprinit: Could not open raw device
2010-02-03 22:22:55.190: [  OCRASM][2603807664]proprasmcl: asmhandle is NULL
2010-02-03 22:22:55.190: [  OCRAPI][2603807664]a_init:16!: Backend init unsuccessful : [26]
2010-02-03 22:22:55.190: [  CRSOCR][2603807664] OCR context init failure.  Error: PROC-26: Error while accessing the physical storage ASM error [SLOS: cat=7, opn=kgfoAl06, dep=15077, loc=kgfokge
ORA-15077: could not locate ASM instance serving a required diskgroup] [7]

2010-02-03 22:22:55.190: [    CRSD][2603807664][PANIC] CRSD exiting: Could not init OCR, code: 26

 

 

注意:在11.2 的版本中 ASM 会比 crsd.bin 先启动,并且会把含有 OCR 的磁盘组自动挂载。

如果您的 OCR 在非 ASM 的存储中,该文件的属主和权限如下:

 

-rw-r----- 1 root  oinstall  272756736 Feb  3 23:24 ocr

 

 

如果 OCR 是在非 ASM 的存储中,并且不能被正常访问,在 crsd.log 会看到以下的类似信息

 

 

2010-02-03 23:14:33.583: [  OCROSD][2346668976]utopen:7:failed to open any OCR file/disk, errno=2, os err string=No such file or directory
2010-02-03 23:14:33.583: [  OCRRAW][2346668976]proprinit: Could not open raw device
2010-02-03 23:14:33.583: [ default][2346668976]a_init:7!: Backend init unsuccessful : [26]
2010-02-03 23:14:34.587: [  OCROSD][2346668976]utopen:6m':failed in stat OCR file/disk /share/storage/ocr, errno=2, os err string=No such file or directory
2010-02-03 23:14:34.587: [  OCROSD][2346668976]utopen:7:failed to open any OCR file/disk, errno=2, os err string=No such file or directory
2010-02-03 23:14:34.587: [  OCRRAW][2346668976]proprinit: Could not open raw device
2010-02-03 23:14:34.587: [ default][2346668976]a_init:7!: Backend init unsuccessful : [26]
2010-02-03 23:14:35.589: [    CRSD][2346668976][PANIC] CRSD exiting: OCR device cannot be initialized, error: 1:26

如果 OCR 是坏掉了,在 crsd.log 会看到以下的类似信息:

 

2010-02-03 23:19:38.417: [ default][3360863152]a_init:7!: Backend init unsuccessful : [26]
2010-02-03 23:19:39.429: [  OCRRAW][3360863152]propriogid:1_2: INVALID FORMAT
2010-02-03 23:19:39.429: [  OCRRAW][3360863152]proprioini: all disks are not OCR/OLR formatted
2010-02-03 23:19:39.429: [  OCRRAW][3360863152]proprinit: Could not open raw device
2010-02-03 23:19:39.429: [ default][3360863152]a_init:7!: Backend init unsuccessful : [26]
2010-02-03 23:19:40.432: [    CRSD][3360863152][PANIC] CRSD exiting: OCR device cannot be initialized, error: 1:26

如果您的 grid 用户的权限或者所在组发生了变化,尽管 ASM 还是可以访问的,在 crsd.log 会看到以下的类似信息:

 

 

2010-03-10 11:45:12.510: [  OCRASM][611467760]proprasmo: Error in open/create file in dg [SYSTEMDG]

[  OCRASM][611467760]SLOS : SLOS: cat=7, opn=kgfoAl06, dep=1031, loc=kgfokge

ORA-01031: insufficient privileges

2010-03-10 11:45:12.528: [  OCRASM][611467760]proprasmo: kgfoCheckMount returned [7]
2010-03-10 11:45:12.529: [  OCRASM][611467760]proprasmo: The ASM instance is down
2010-03-10 11:45:12.529: [  OCRRAW][611467760]proprioo: Failed to open [+SYSTEMDG]. Returned proprasmo() with [26]. Marking location as UNAVAILABLE.
2010-03-10 11:45:12.529: [  OCRRAW][611467760]proprioo: No OCR/OLR devices are usable
2010-03-10 11:45:12.529: [  OCRASM][611467760]proprasmcl: asmhandle is NULL
2010-03-10 11:45:12.529: [  OCRRAW][611467760]proprinit: Could not open raw device
2010-03-10 11:45:12.529: [  OCRASM][611467760]proprasmcl: asmhandle is NULL
2010-03-10 11:45:12.529: [  OCRAPI][611467760]a_init:16!: Backend init unsuccessful : [26]
2010-03-10 11:45:12.530: [  CRSOCR][611467760] OCR context init failure.  Error: PROC-26: Error while accessing the physical storage ASM error [SLOS: cat=7, opn=kgfoAl06, dep=1031, loc=kgfokge
ORA-01031: insufficient privileges] [7]

 

 

 

如果grid用户无法写ORACLE_BASE目录,以及GRID_HOME 下的 oracle 二进制文件的属主或者权限错误,尽管 ASM 正常启动并运行,在 crsd.log 会看到以下的类似信息:

 

 

2012-03-04 21:34:23.139: [  OCRASM][3301265904]proprasmo: Error in open/create file in dg [OCR]

[  OCRASM][3301265904]SLOS : SLOS: cat=7, opn=kgfoAl06, dep=12547, loc=kgfokge

2012-03-04 21:34:23.139: [  OCRASM][3301265904]ASM Error Stack : ORA-12547: TNS:lost contact

2012-03-04 21:34:23.633: [  OCRASM][3301265904]proprasmo: kgfoCheckMount returned [7]
2012-03-04 21:34:23.633: [  OCRASM][3301265904]proprasmo: The ASM instance is down
2012-03-04 21:34:23.634: [  OCRRAW][3301265904]proprioo: Failed to open [+OCR]. Returned proprasmo() with [26]. Marking location as UNAVAILABLE.
2012-03-04 21:34:23.634: [  OCRRAW][3301265904]proprioo: No OCR/OLR devices are usable
2012-03-04 21:34:23.635: [  OCRASM][3301265904]proprasmcl: asmhandle is NULL
2012-03-04 21:34:23.636: [    GIPC][3301265904] gipcCheckInitialization: possible incompatible non-threaded init from [prom.c : 690], original from [clsss.c : 5326]
2012-03-04 21:34:23.639: [ default][3301265904]clsvactversion:4: Retrieving Active Version from local storage.
2012-03-04 21:34:23.643: [  OCRRAW][3301265904]proprrepauto: The local OCR configuration matches with the configuration published by OCR Cache Writer. No repair required.
2012-03-04 21:34:23.645: [  OCRRAW][3301265904]proprinit: Could not open raw device
2012-03-04 21:34:23.646: [  OCRASM][3301265904]proprasmcl: asmhandle is NULL
2012-03-04 21:34:23.650: [  OCRAPI][3301265904]a_init:16!: Backend init unsuccessful : [26]
2012-03-04 21:34:23.651: [  CRSOCR][3301265904] OCR context init failure.  Error: PROC-26: Error while accessing the physical storage
ORA-12547: TNS:lost contact

2012-03-04 21:34:23.652: [ CRSMAIN][3301265904] Created alert : (:CRSD00111:) :  Could not init OCR, error: PROC-26: Error while accessing the physical storage
ORA-12547: TNS:lost contact

2012-03-04 21:34:23.652: [    CRSD][3301265904][PANIC] CRSD exiting: Could not init OCR, code: 26

 

 

正常的 GRID_HOME 下该文件的属主和权限应该是如下显示:

 

-rwsr-s--x 1 grid oinstall 184431149 Feb  2 20:37 /ocw/grid/bin/oracle

如果 OCR 文件或者它的镜像文件无法正常访问 (可能是 ASM 已经启动, 但是 OCR/mirror 所在的磁盘组没有挂载),在 crsd.log 会看到以下的类似信息:

 

 

2010-05-11 11:16:38.578: [  OCRASM][18]proprasmo: Error in open/create file in dg [OCRMIR]
[  OCRASM][18]SLOS : SLOS: cat=8, opn=kgfoOpenFile01, dep=15056, loc=kgfokge
ORA-17503: ksfdopn:DGOpenFile05 Failed to open file +OCRMIR.255.4294967295
ORA-17503: ksfdopn:2 Failed to open file +OCRMIR.255.4294967295
ORA-15001: diskgroup "OCRMIR
..
2010-05-11 11:16:38.647: [  OCRASM][18]proprasmo: kgfoCheckMount returned [6]
2010-05-11 11:16:38.648: [  OCRASM][18]proprasmo: The ASM disk group OCRMIR is not found or not mounted
2010-05-11 11:16:38.648: [  OCRASM][18]proprasmdvch: Failed to open OCR location [+OCRMIR] error [26]
2010-05-11 11:16:38.648: [  OCRRAW][18]propriodvch: Error  [8] returned device check for [+OCRMIR]
2010-05-11 11:16:38.648: [  OCRRAW][18]dev_replace: non-master could not verify the new disk (8)
[  OCRSRV][18]proath_invalidate_action: Failed to replace [+OCRMIR] [8]
[  OCRAPI][18]procr_ctx_set_invalid_no_abort: ctx set to invalid
..
2010-05-11 11:16:46.587: [  OCRMAS][19]th_master:91: Comparing device hash ids between local and master failed
2010-05-11 11:16:46.587: [  OCRMAS][19]th_master:91 Local dev (1862408427, 1028247821, 0, 0, 0)
2010-05-11 11:16:46.587: [  OCRMAS][19]th_master:91 Master dev (1862408427, 1859478705, 0, 0, 0)
2010-05-11 11:16:46.587: [  OCRMAS][19]th_master:9: Shutdown CacheLocal. my hash ids don't match
[  OCRAPI][19]procr_ctx_set_invalid_no_abort: ctx set to invalid
[  OCRAPI][19]procr_ctx_set_invalid: aborting...
2010-05-11 11:16:46.587: [    CRSD][19] Dump State Starting ...

 

 

3. crsd.bin 的进程号文件(<GRID_HOME>/crs/init/<节点名>.pid)存在,但是却指向其它的进程

如果进程号文件不存在,在日志 $GRID_HOME/log/$HOST/agent/ohasd/orarootagent_root/orarootagent_root.log 我们会看到以下的提示信息:

 

 

2010-02-14 17:40:57.927: [ora.crsd][1243486528] [check] PID FILE doesn't exist.
..
2010-02-14 17:41:57.927: [  clsdmt][1092499776]Creating PID [30269] file for home /ocw/grid host racnode1 bin crs to /ocw/grid/crs/init/
2010-02-14 17:41:57.927: [  clsdmt][1092499776]Error3 -2 writing PID [30269] to the file []
2010-02-14 17:41:57.927: [  clsdmt][1092499776]Failed to record pid for CRSD
2010-02-14 17:41:57.927: [  clsdmt][1092499776]Terminating process
2010-02-14 17:41:57.927: [ default][1092499776] CRSD exiting on stop request from clsdms_thdmai

解决办法,我们可以手工创建一个进程号文件:使用 grid 用户执行 “touch” 命令,然后重新启动 ora.crsd 资源。

如果进程号文件存在,但是记录的 PID 是指向了其它的进程,而不是 crsd.bin 的进程,在日志 $GRID_HOME/log/$HOST/agent/ohasd/orarootagent_root/orarootagent_root.log 我们会看到以下的提示信息:

 

 

2011-04-06 15:53:38.777: [ora.crsd][1160390976] [check] PID will be looked for in /ocw/grid/crs/init/racnode1.pid
2011-04-06 15:53:38.778: [ora.crsd][1160390976] [check] PID which will be monitored will be 1535                               >> 1535 is output of "cat /ocw/grid/crs/init/racnode1.pid"
2011-04-06 15:53:38.965: [ COMMCRS][1191860544]clsc_connect: (0x2aaab400b0b0) no listener at (ADDRESS=(PROTOCOL=ipc)(KEY=racnode1DBG_CRSD))
[  clsdmc][1160390976]Fail to connect (ADDRESS=(PROTOCOL=ipc)(KEY=racnode1DBG_CRSD)) with status 9
2011-04-06 15:53:38.966: [ora.crsd][1160390976] [check] Error = error 9 encountered when connecting to CRSD
2011-04-06 15:53:39.023: [ora.crsd][1160390976] [check] Calling PID check for daemon
2011-04-06 15:53:39.023: [ora.crsd][1160390976] [check] Trying to check PID = 1535
2011-04-06 15:53:39.203: [ora.crsd][1160390976] [check] PID check returned ONLINE CLSDM returned OFFLINE
2011-04-06 15:53:39.203: [ora.crsd][1160390976] [check] DaemonAgent::check returned 5
2011-04-06 15:53:39.203: [    AGFW][1160390976] check for resource: ora.crsd 1 1 completed with status: FAILED
2011-04-06 15:53:39.203: [    AGFW][1170880832] ora.crsd 1 1 state changed from: UNKNOWN to: FAILED
..
2011-04-06 15:54:10.511: [    AGFW][1167522112] ora.crsd 1 1 state changed from: UNKNOWN to: CLEANING
..
2011-04-06 15:54:10.513: [ora.crsd][1146542400] [clean] Trying to stop PID = 1535
..
2011-04-06 15:54:11.514: [ora.crsd][1146542400] [clean] Trying to check PID = 1535

在 OS 层面检查该问题:

 

 

ls -l /ocw/grid/crs/init/*pid
-rwxr-xr-x 1 ogrid oinstall 5 Feb 17 11:00 /ocw/grid/crs/init/racnode1.pid
cat /ocw/grid/crs/init/*pid
1535
ps -ef| grep 1535
root      1535     1  0 Mar30 ?        00:00:00 iscsid                  >> 注意:进程 1535 不是 crsd.bin

解决办法是,使用 root 用户,创建一个空的进程号文件,然后重启资源 ora.crsd:

 

 

# > $GRID_HOME/crs/init/<racnode1>.pid
# $GRID_HOME/bin/crsctl stop res ora.crsd -init
# $GRID_HOME/bin/crsctl start res ora.crsd -init

4. 网络功能是正常的,并且域名解析能够正常工作:

 

如果网络功能不正常,ocssd.bin 进程仍然可能被启动, 但是 crsd.bin 可能会失败,同时在 crsd.log 中会提示以下信息:

 

 

2010-02-03 23:34:28.412: [    GPnP][2235814832]clsgpnp_Init: [at clsgpnp0.c:837] GPnP client pid=867, tl=3, f=0
2010-02-03 23:34:28.428: [  OCRAPI][2235814832]clsu_get_private_ip_addresses: no ip addresses found.
..
2010-02-03 23:34:28.434: [  OCRAPI][2235814832]a_init:13!: Clusterware init unsuccessful : [44]
2010-02-03 23:34:28.434: [  CRSOCR][2235814832] OCR context init failure.  Error: PROC-44: Error in network address and interface operations Network address and interface operations error [7]
2010-02-03 23:34:28.434: [    CRSD][2235814832][PANIC] CRSD exiting: Could not init OCR, code: 44

 

 

或者:

 

 

2009-12-10 06:28:31.974: [  OCRMAS][20]proath_connect_master:1: could not connect to master  clsc_ret1 = 9, clsc_ret2 = 9
2009-12-10 06:28:31.974: [  OCRMAS][20]th_master:11: Could not connect to the new master
2009-12-10 06:29:01.450: [ CRSMAIN][2] Policy Engine is not initialized yet!
2009-12-10 06:29:31.489: [ CRSMAIN][2] Policy Engine is not initialized yet!

 

或者:

 

2009-12-31 00:42:08.110: [ COMMCRS][10]clsc_receive: (102b03250) Error receiving, ns (12535, 12560), transport (505, 145, 0)

关于网络和域名解析的验证,请参考:note 1054902.1

 

 

5. crsd 可执行文件(crsd.bin 和 crsd in GRID_HOME/bin) 的权限或者属主正确并且没有进行过手工的修改, 一个简单可行的检查办法是对比好的节点和坏节点的以下命令输出 “ls -l <grid-home>/bin/crsd <grid-home>/bin/crsd.bin”.

6. crsd可能因为下面的原因无法启动

 

 

note 1552472.1 -CRSD Will Not Start Following a Node Reboot: crsd.log reports: clsclisten: op 65 failed and/or Unable to get E2E port
note 1684332.1 - GI crsd Fails to Start: clsclisten: op 65 failed, NSerr (12560, 0), transport: (583, 0, 0)

 

7. 关于CRSD进程启动问题的进一步深入诊断,请参考 note 1323698.1 – Troubleshooting CRSD Start up Issue

问题 5: GPNPD.BIN 无法启动

 

1. 网络的域名解析不正常

gpnpd.bin 进程启动失败,以下信息提示在 gpnpd.log 中:

 

 

2010-05-13 12:48:11.540: [    GPnP][1171126592]clsgpnpm_exchange: [at clsgpnpm.c:1175] Calling "tcp://node2:9393", try 1 of 3...
2010-05-13 12:48:11.540: [    GPnP][1171126592]clsgpnpm_connect: [at clsgpnpm.c:1015] ENTRY
2010-05-13 12:48:11.541: [    GPnP][1171126592]clsgpnpm_connect: [at clsgpnpm.c:1066] GIPC gipcretFail (1) gipcConnect(tcp-tcp://node2:9393)
2010-05-13 12:48:11.541: [    GPnP][1171126592]clsgpnpm_connect: [at clsgpnpm.c:1067] Result: (48) CLSGPNP_COMM_ERR. Failed to connect to call url "tcp://node2:9393"

以上的例子,请确定当前节点能够正常的 ping 到“node2” ,并且确认两个节点之间没有任何防火墙。

2. bug 10105195

由于 bug 10105195, gpnp 的调度线程(dispatch thread)可能被阻断,例如:网络扫描。这个 bug 在 11.2.0.2 GI PSU2,11.2.0.3 及以上版本被修复,具体信息,请参见 note 10105195.8

 

问题 6: 其它的一些守护进程无法启动

 

常见原因:

1. 守护进程的日志文件或者日志所在的路径权限或者属主不正确。

如果日志文件或者日志文件所在的路径权限或者属主设置有问题,通常我们会看到进程尝试启动,但是日志里的信息却始终没有更新.

关于日志位置和权限属主的限制,请参见 “日志文件位置, 属主和权限” 获取更多的信息。

2. 网络的 socket 文件权限或者属主错误

这种情况下,守护进程的日志会显示以下信息:

 

2010-02-02 12:55:20.485: [ COMMCRS][1121433920]clsclisten: Permission denied for (ADDRESS=(PROTOCOL=ipc)(KEY=rac1DBG_GIPCD))

2010-02-02 12:55:20.485: [  clsdmt][1110944064]Fail to listen to (ADDRESS=(PROTOCOL=ipc)(KEY=rac1DBG_GIPCD))

 

3. OLR 文件损坏

这种情况下,守护进程的日志会显示以下信息(以下是个 ora.ctssd 无法启动的例子):

 

 

2012-07-22 00:15:16.565: [ default][1]clsvactversion:4: Retrieving Active Version from local storage.
2012-07-22 00:15:16.575: [    CTSS][1]clsctss_r_av3: Invalid active version [] retrieved from OLR. Returns [19].
2012-07-22 00:15:16.585: [    CTSS][1](:ctss_init16:): Error [19] retrieving active version. Returns [19].
2012-07-22 00:15:16.585: [    CTSS][1]ctss_main: CTSS init failed [19]
2012-07-22 00:15:16.585: [    CTSS][1]ctss_main: CTSS daemon aborting [19].
2012-07-22 00:15:16.585: [    CTSS][1]CTSS daemon aborting

解决办法,请恢复一个好的OLR的副本,具体办法请参见 note 1193643.1

4. 其它情况:

note 1087521.1 – CTSS Daemon Aborting With “op 65 failed, NSerr (12560, 0), transport: (583, 0, 0)”

 

问题 7: CRSD Agents 无法启动

 

 

CRSD.BIN 会负责衍生出两个 agents 进程来启动用户的资源,这两个 agents 的名字和 ohasd.bin 的 agents 的名字相同:

orarootagent: 负责启动 ora.netn.network, ora.nodename.vip, ora.scann.vip 和 ora.gns
oraagent: 负责启动 ora.asm, ora.eons, ora.ons, listener, SCAN listener, diskgroup, database, service 等资源

我们可以通过以下命令查看用户的资源状态:

 

 

$GRID_HOME/crsctl stat res -t

 

如果 crsd.bin 无法正常启动以上任何一个 agent,用户的资源都将无法正常启动.

1. 通常这些 agent 无法启动的常见原因是 agent 的日志或者日志所在的路径没有设置合适的权限或者属主。

请参见以下 “日志文件位置, 属主和权限” 部分关于日志权限的设置。

2. agent 可能因为 bug 11834289 无法启动,此时我们会看到 “CRS-5802: Unable to start the agent process”错误信息,请参见 “OHASD 无法启动”  #10 获取更多信息。

 

问题 8: HAIP 无法启动

 

HAIP 无法启动的原因有很多,例如:

[ohasd(891)]CRS-2807:Resource ‘ora.cluster_interconnect.haip’ failed to start automatically.

请参见 note 1210883.1 获取更多关于 HAIP 的信息。

 

 

网络和域名解析的验证

CRS 的启动,依赖于网络功能和域名解析的正常工作,如果网络功能或者域名解析不能正常工作,CRS 将无法正常启动。

关于网络和域名解析的验证,请参考: note 1054902.1

 

日志文件位置, 属主和权限

正确的设置 $GRID_HOME/log 和这里的子目录以及文件对 CRS 组件的正常启动是至关重要的。

 

在 Grid Infrastructure 的环境中:

我们假设一个 Grid Infrastructure 环境,节点名字为 rac1, CRS 的属主是 grid, 并且有两个单独的 RDBMS 属主分别为: rdbmsap 和 rdbmsar,以下是 $GRID_HOME/log 中正常的设置情况:

 

drwxrwxr-x 5 grid oinstall 4096 Dec  6 09:20 log
drwxr-xr-x  2 grid oinstall 4096 Dec  6 08:36 crs
drwxr-xr-t 17 root   oinstall 4096 Dec  6 09:22 rac1
drwxr-x--- 2 grid oinstall  4096 Dec  6 09:20 admin
drwxrwxr-t 4 root   oinstall  4096 Dec  6 09:20 agent
drwxrwxrwt 7 root    oinstall 4096 Jan 26 18:15 crsd
drwxr-xr-t 2 grid  oinstall 4096 Dec  6 09:40 application_grid
drwxr-xr-t 2 grid  oinstall 4096 Jan 26 18:15 oraagent_grid
drwxr-xr-t 2 rdbmsap oinstall 4096 Jan 26 18:15 oraagent_rdbmsap
drwxr-xr-t 2 rdbmsar oinstall 4096 Jan 26 18:15 oraagent_rdbmsar
drwxr-xr-t 2 grid  oinstall 4096 Jan 26 18:15 ora_oc4j_type_grid
drwxr-xr-t 2 root    root     4096 Jan 26 20:09 orarootagent_root
drwxrwxr-t 6 root oinstall 4096 Dec  6 09:24 ohasd
drwxr-xr-t 2 grid oinstall 4096 Jan 26 18:14 oraagent_grid
drwxr-xr-t 2 root   root     4096 Dec  6 09:24 oracssdagent_root
drwxr-xr-t 2 root   root     4096 Dec  6 09:24 oracssdmonitor_root
drwxr-xr-t 2 root   root     4096 Jan 26 18:14 orarootagent_root
-rw-rw-r-- 1 root root     12931 Jan 26 21:30 alertrac1.log
drwxr-x--- 2 grid oinstall  4096 Jan 26 20:44 client
drwxr-x--- 2 root oinstall  4096 Dec  6 09:24 crsd
drwxr-x--- 2 grid oinstall  4096 Dec  6 09:24 cssd
drwxr-x--- 2 root oinstall  4096 Dec  6 09:24 ctssd
drwxr-x--- 2 grid oinstall  4096 Jan 26 18:14 diskmon
drwxr-x--- 2 grid oinstall  4096 Dec  6 09:25 evmd
drwxr-x--- 2 grid oinstall  4096 Jan 26 21:20 gipcd
drwxr-x--- 2 root oinstall  4096 Dec  6 09:20 gnsd
drwxr-x--- 2 grid oinstall  4096 Jan 26 20:58 gpnpd
drwxr-x--- 2 grid oinstall  4096 Jan 26 21:19 mdnsd
drwxr-x--- 2 root oinstall  4096 Jan 26 21:20 ohasd
drwxrwxr-t 5 grid oinstall  4096 Dec  6 09:34 racg
drwxrwxrwt 2 grid oinstall 4096 Dec  6 09:20 racgeut
drwxrwxrwt 2 grid oinstall 4096 Dec  6 09:20 racgevtf
drwxrwxrwt 2 grid oinstall 4096 Dec  6 09:20 racgmain
drwxr-x--- 2 grid oinstall  4096 Jan 26 20:57 srvm

请注意,绝大部分的子目录都继承了父目录的属主和权限,以上仅作为一个参考,来判断 CRS HOME 中是否有一些递归的权限和属主改变,如果您已经有一个相同版本的正在运行的工作节点,您可以把该运行的节点作为参考。

 

在 Oracle Restart 的环境中:

这里显示了在 Oracle Restart 环境中 $GRID_HOME/log 目录下的权限和属主设置:

 

drwxrwxr-x 5 grid oinstall 4096 Oct 31  2009 log
drwxr-xr-x  2 grid oinstall 4096 Oct 31  2009 crs
drwxr-xr-x  3 grid oinstall 4096 Oct 31  2009 diag
drwxr-xr-t 17 root   oinstall 4096 Oct 31  2009 rac1
drwxr-x--- 2 grid oinstall  4096 Oct 31  2009 admin
drwxrwxr-t 4 root   oinstall  4096 Oct 31  2009 agent
drwxrwxrwt 2 root oinstall 4096 Oct 31  2009 crsd
drwxrwxr-t 8 root oinstall 4096 Jul 14 08:15 ohasd
drwxr-xr-x 2 grid oinstall 4096 Aug  5 13:40 oraagent_grid
drwxr-xr-x 2 grid oinstall 4096 Aug  2 07:11 oracssdagent_grid
drwxr-xr-x 2 grid oinstall 4096 Aug  3 21:13 orarootagent_grid
-rwxr-xr-x 1 grid oinstall 13782 Aug  1 17:23 alertrac1.log
drwxr-x--- 2 grid oinstall  4096 Nov  2  2009 client
drwxr-x--- 2 root   oinstall  4096 Oct 31  2009 crsd
drwxr-x--- 2 grid oinstall  4096 Oct 31  2009 cssd
drwxr-x--- 2 root   oinstall  4096 Oct 31  2009 ctssd
drwxr-x--- 2 grid oinstall  4096 Oct 31  2009 diskmon
drwxr-x--- 2 grid oinstall  4096 Oct 31  2009 evmd
drwxr-x--- 2 grid oinstall  4096 Oct 31  2009 gipcd
drwxr-x--- 2 root   oinstall  4096 Oct 31  2009 gnsd
drwxr-x--- 2 grid oinstall  4096 Oct 31  2009 gpnpd
drwxr-x--- 2 grid oinstall  4096 Oct 31  2009 mdnsd
drwxr-x--- 2 grid oinstall  4096 Oct 31  2009 ohasd
drwxrwxr-t 5 grid oinstall  4096 Oct 31  2009 racg
drwxrwxrwt 2 grid oinstall 4096 Oct 31  2009 racgeut
drwxrwxrwt 2 grid oinstall 4096 Oct 31  2009 racgevtf
drwxrwxrwt 2 grid oinstall 4096 Oct 31  2009 racgmain
drwxr-x--- 2 grid oinstall  4096 Oct 31  2009 srvm

 

对于12.1.0.2及以上版本,参考 note 1915729.1 – Oracle Clusterware Diagnostic and Alert Log Moved to ADR

 

网络socket文件的位置,属主和权限

网络的 socket 文件可能位于目录: /tmp/.oracle, /var/tmp/.oracle or /usr/tmp/.oracle 中。

当网络的 socket 文件权限或者属主设置不正确的时候,我们通常会在守护进程的日志中看到以下类似的信息:

 

2011-06-18 14:07:28.545: [ COMMCRS][772]clsclisten: Permission denied for (ADDRESS=(PROTOCOL=ipc)(KEY=racnode1DBG_EVMD))

2011-06-18 14:07:28.545: [  clsdmt][515]Fail to listen to (ADDRESS=(PROTOCOL=ipc)(KEY=lena042DBG_EVMD))
2011-06-18 14:07:28.545: [  clsdmt][515]Terminating process
2011-06-18 14:07:28.559: [ default][515] EVMD exiting on stop request from clsdms_thdmai

 

以下错误也有可能提示:

 

CRS-5017: The resource action "ora.evmd start" encountered the following error:
CRS-2674: Start of 'ora.evmd' on 'racnode1' failed
..

解决的办法:请使用 root 用户停掉 GI,删除这些 socket 文件,并重新启动 GI。

我们假设一个 Grid Infrastructure 环境,节点名为 rac1, CRS 的属主是 grid,以下是 socket 文件夹(../.oracle)正常的设置情况:

 

在 Grid Infrastructure cluster 环境中:

以下例子是集群环境中的例子:

 

 

drwxrwxrwt  2 root oinstall 4096 Feb  2 21:25 .oracle

./.oracle:
drwxrwxrwt 2 root  oinstall 4096 Feb  2 21:25 .
srwxrwx--- 1 grid oinstall    0 Feb  2 18:00 master_diskmon
srwxrwxrwx 1 grid oinstall    0 Feb  2 18:00 mdnsd
-rw-r--r-- 1 grid oinstall    5 Feb  2 18:00 mdnsd.pid
prw-r--r-- 1 root  root        0 Feb  2 13:33 npohasd
srwxrwxrwx 1 grid oinstall    0 Feb  2 18:00 ora_gipc_GPNPD_rac1
-rw-r--r-- 1 grid oinstall    0 Feb  2 13:34 ora_gipc_GPNPD_rac1_lock
srwxrwxrwx 1 grid oinstall    0 Feb  2 13:39 s#11724.1
srwxrwxrwx 1 grid oinstall    0 Feb  2 13:39 s#11724.2
srwxrwxrwx 1 grid oinstall    0 Feb  2 13:39 s#11735.1
srwxrwxrwx 1 grid oinstall    0 Feb  2 13:39 s#11735.2
srwxrwxrwx 1 grid oinstall    0 Feb  2 13:45 s#12339.1
srwxrwxrwx 1 grid oinstall    0 Feb  2 13:45 s#12339.2
srwxrwxrwx 1 grid oinstall    0 Feb  2 18:01 s#6275.1
srwxrwxrwx 1 grid oinstall    0 Feb  2 18:01 s#6275.2
srwxrwxrwx 1 grid oinstall    0 Feb  2 18:01 s#6276.1
srwxrwxrwx 1 grid oinstall    0 Feb  2 18:01 s#6276.2
srwxrwxrwx 1 grid oinstall    0 Feb  2 18:01 s#6278.1
srwxrwxrwx 1 grid oinstall    0 Feb  2 18:01 s#6278.2
srwxrwxrwx 1 grid oinstall    0 Feb  2 18:00 sAevm
srwxrwxrwx 1 grid oinstall    0 Feb  2 18:00 sCevm
srwxrwxrwx 1 root  root        0 Feb  2 18:01 sCRSD_IPC_SOCKET_11
srwxrwxrwx 1 root  root        0 Feb  2 18:01 sCRSD_UI_SOCKET
srwxrwxrwx 1 root  root        0 Feb  2 21:25 srac1DBG_CRSD
srwxrwxrwx 1 grid oinstall    0 Feb  2 18:00 srac1DBG_CSSD
srwxrwxrwx 1 root  root        0 Feb  2 18:00 srac1DBG_CTSSD
srwxrwxrwx 1 grid oinstall    0 Feb  2 18:00 srac1DBG_EVMD
srwxrwxrwx 1 grid oinstall    0 Feb  2 18:00 srac1DBG_GIPCD
srwxrwxrwx 1 grid oinstall    0 Feb  2 18:00 srac1DBG_GPNPD
srwxrwxrwx 1 grid oinstall    0 Feb  2 18:00 srac1DBG_MDNSD
srwxrwxrwx 1 root  root        0 Feb  2 18:00 srac1DBG_OHASD
srwxrwxrwx 1 grid oinstall    0 Feb  2 18:01 sLISTENER
srwxrwxrwx 1 grid oinstall    0 Feb  2 18:01 sLISTENER_SCAN2
srwxrwxrwx 1 grid oinstall    0 Feb  2 18:01 sLISTENER_SCAN3
srwxrwxrwx 1 grid oinstall    0 Feb  2 18:00 sOCSSD_LL_rac1_
srwxrwxrwx 1 grid oinstall    0 Feb  2 18:00 sOCSSD_LL_rac1_eotcs
-rw-r--r-- 1 grid oinstall    0 Feb  2 18:00 sOCSSD_LL_rac1_eotcs_lock
-rw-r--r-- 1 grid oinstall    0 Feb  2 18:00 sOCSSD_LL_rac1__lock
srwxrwxrwx 1 root  root        0 Feb  2 18:00 sOHASD_IPC_SOCKET_11
srwxrwxrwx 1 root  root        0 Feb  2 18:00 sOHASD_UI_SOCKET
srwxrwxrwx 1 grid oinstall    0 Feb  2 18:00 sOracle_CSS_LclLstnr_eotcs_1
-rw-r--r-- 1 grid oinstall    0 Feb  2 18:00 sOracle_CSS_LclLstnr_eotcs_1_lock
srwxrwxrwx 1 root  root        0 Feb  2 18:01 sora_crsqs
srwxrwxrwx 1 root  root        0 Feb  2 18:00 sprocr_local_conn_0_PROC
srwxrwxrwx 1 root  root        0 Feb  2 18:00 sprocr_local_conn_0_PROL
srwxrwxrwx 1 grid oinstall    0 Feb  2 18:00 sSYSTEM.evm.acceptor.auth

 

 

在 Oracle Restart 环境中:

以下是 Oracle Restart 环境中的输出例子:

 

drwxrwxrwt  2 root oinstall 4096 Feb  2 21:25 .oracle

./.oracle:
srwxrwx--- 1 grid oinstall 0 Aug  1 17:23 master_diskmon
prw-r--r-- 1 grid oinstall 0 Oct 31  2009 npohasd
srwxrwxrwx 1 grid oinstall 0 Aug  1 17:23 s#14478.1
srwxrwxrwx 1 grid oinstall 0 Aug  1 17:23 s#14478.2
srwxrwxrwx 1 grid oinstall 0 Jul 14 08:02 s#2266.1
srwxrwxrwx 1 grid oinstall 0 Jul 14 08:02 s#2266.2
srwxrwxrwx 1 grid oinstall 0 Jul  7 10:59 s#2269.1
srwxrwxrwx 1 grid oinstall 0 Jul  7 10:59 s#2269.2
srwxrwxrwx 1 grid oinstall 0 Jul 31 22:10 s#2313.1
srwxrwxrwx 1 grid oinstall 0 Jul 31 22:10 s#2313.2
srwxrwxrwx 1 grid oinstall 0 Jun 29 21:58 s#2851.1
srwxrwxrwx 1 grid oinstall 0 Jun 29 21:58 s#2851.2
srwxrwxrwx 1 grid oinstall 0 Aug  1 17:23 sCRSD_UI_SOCKET
srwxrwxrwx 1 grid oinstall 0 Aug  1 17:23 srac1DBG_CSSD
srwxrwxrwx 1 grid oinstall 0 Aug  1 17:23 srac1DBG_OHASD
srwxrwxrwx 1 grid oinstall 0 Aug  1 17:23 sEXTPROC1521
srwxrwxrwx 1 grid oinstall 0 Aug  1 17:23 sOCSSD_LL_rac1_
srwxrwxrwx 1 grid oinstall 0 Aug  1 17:23 sOCSSD_LL_rac1_localhost
-rw-r--r-- 1 grid oinstall 0 Aug  1 17:23 sOCSSD_LL_rac1_localhost_lock
-rw-r--r-- 1 grid oinstall 0 Aug  1 17:23 sOCSSD_LL_rac1__lock
srwxrwxrwx 1 grid oinstall 0 Aug  1 17:23 sOHASD_IPC_SOCKET_11
srwxrwxrwx 1 grid oinstall 0 Aug  1 17:23 sOHASD_UI_SOCKET
srwxrwxrwx 1 grid oinstall 0 Aug  1 17:23 sgrid_CSS_LclLstnr_localhost_1
-rw-r--r-- 1 grid oinstall 0 Aug  1 17:23 sgrid_CSS_LclLstnr_localhost_1_lock
srwxrwxrwx 1 grid oinstall 0 Aug  1 17:23 sprocr_local_conn_0_PROL

 

诊断文件收集

如果通过本文没有找到问题原因,请使用 root 用户,在所有的节点上执行 $GRID_HOME/bin/diagcollection.sh ,并上传在当前目录下生成所有的 .gz 压缩文件来做进一步诊断。

沪ICP备14014813号-2

沪公网安备 31010802001379号