解决 oracle EXP-00091: Exporting questionable statistics. 问题

EXP-00091 Exporting questionable statistics
  
Cause: Export was able to export statistics, but the statistics may not be useable. The statistics are questionable because one or more of the following happened during export: a row error occurred, client character set or NCHARSET does not match with the server, a query clause was specified on export, only certain partitions or subpartitions were exported, or a fatal error occurred while processing a table.
  
Action: To export non-questionable statistics, change the client character set or NCHARSET to match the server, export with no query clause, or export complete tables. If desired, import parameters can be supplied so that only non-questionable statistics will be imported, and all questionable statistics will be recalculated.

解决:
linux下的oracle用户的环境变量语言集和oralce数据库中的环境变量语言集不相同。
查看oracle的环境变量语言集:
数据库服务器字符集:
select * from nls_database_parameters
客户端字符集:
select * from nls_instance_parameters

将oracle用户的环境变量语言集改成和数据库服务器字符集一样。
 export NLS_LANG=american_america.ZHS16GBK
2025-03-10T06:43:37.165038Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details). 2025-03-10T06:43:37.165092Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled 2025-03-10T06:43:37.165104Z 0 [Note] /usr/local/mysql/bin/mysqld (mysqld 5.7.18) starting as process 26836 ... 2025-03-10T06:43:37.169695Z 0 [Note] InnoDB: PUNCH HOLE support not available 2025-03-10T06:43:37.169704Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2025-03-10T06:43:37.169706Z 0 [Note] InnoDB: Uses event mutexes 2025-03-10T06:43:37.169708Z 0 [Note] InnoDB: GCC builtin __sync_synchronize() is used for memory barrier 2025-03-10T06:43:37.169709Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3 2025-03-10T06:43:37.169711Z 0 [Note] InnoDB: Using Linux native AIO 2025-03-10T06:43:37.169831Z 0 [Note] InnoDB: Number of pools: 1 2025-03-10T06:43:37.169878Z 0 [Note] InnoDB: Using CPU crc32 instructions 2025-03-10T06:43:37.170938Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M 2025-03-10T06:43:37.178293Z 0 [Note] InnoDB: Completed initialization of buffer pool 2025-03-10T06:43:37.179917Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2025-03-10T06:43:37.191665Z 0 [Note] InnoDB: Highest supported file format is Barracuda. 2025-03-10T06:43:37.195822Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables 2025-03-10T06:43:37.195863Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2025-03-10T06:43:37.209862Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2025-03-10T06:43:37.210297Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active. 2025-03-10T06:43:37.210301Z 0 [Note] InnoDB: 32 n
最新发布
03-11
### 解决 MySQL 启动时 TIMESTAMP 隐式默认值弃用警告 当声明 `TIMESTAMP` 列为 `NOT NULL` 并且没有显式的 `DEFAULT` 子句时,该列被视为没有默认值[^1]。对于不为此列指定显式值的插入行,在严格 SQL 模式下会导致错误;而在非严格模式下则会分配隐式默认值 “0000-00-00 00:00:00”,并发出警告。 为了避免这种警告,建议在定义表结构时明确提供 `DEFAULT CURRENT_TIMESTAMP` 或者其他合适的默认值: ```sql CREATE TABLE example ( id INT AUTO_INCREMENT PRIMARY KEY, create_date TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP COMMENT '创建日期' ); ``` 通过这种方式可以确保每次插入新记录而未指定 `create_date` 值时自动使用当前时间戳作为默认值,从而避免潜在的问题和警告消息。 ### 处理 --secure-file-priv 设置为 NULL 的问题 如果发现 `--secure-file-priv` 参数被设置为了 `NULL`,这表示不允许任何路径用于导入或导出数据文件的操作。要解决这个问题,可以通过修改配置文件来设定允许的数据目录位置。 编辑 MySQL 配置文件(通常是 my.cnf 或 my.ini),找到 `[mysqld]` 节点,并添加如下参数以指明安全访问的数据文件夹路径: ```ini [mysqld] secure_file_priv="/path/to/your/data/directory" ``` 重启 MySQL 服务使更改生效之后,就可以在这个指定的位置执行 LOAD DATA 和 SELECT ... INTO OUTFILE 等命令了。 另外需要注意的是,出于安全性考虑,应该只授予必要的权限给特定用户来进行这些敏感操作,并定期审查日志确保系统的安全性不受威胁。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

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

抵扣说明:

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

余额充值