ORA-39360: Table string was skipped due to transportable import and TSLTZ issues resulting from time zone mismatch. ORACLE 报错 故障修复 远程处理

文档解释

ORA-39360: Table string was skipped due to transportable import and TSLTZ issues resulting from time zone mismatch.

Cause: The time zone of the source database is different than the time zone of the target database and this table contains TIMESTAMP WITH LOCAL TIME ZONE data.

Action: Convert the target database to the same time zone as the source database or use Oracle Data Pump with conventional data movement to export then import this table.

这是由于时区不匹配所引起的数据传输问题,Oracle 数据库服务器与客户机/源实例的时区不同时会抛出 ORA-39360 错误。

官方解释

ORA-39360:表 string 被跳过,由于在可迁移的导入过程中,TSLTZ 时区问题导致时区不匹配。

常见案例

当尝试通过 transpotable 导入时,源和目标实例的时区必须完全匹配才能进行彻底的数据复制。如果不匹配,可能会出现 ORA-39360 错误,并且某些表无法被迁移出来,打印的报错信息如下:

ORA-39360: Table string was skipped due to transportable import and TSLTZ issues resulting from time zone mismatch.

一般处理方法及步骤

要解决 ORA-39360 的报错,首先要确保源和目标实例的时区完全匹配。为此,可以使用如下 SQL 语句检查源和目标实例的时区是否一致:

SELECT SOURCE_DB_TIMEZONE, DEST_DB_TIMEZONE FROM V$TRANSPORTABLE_PLATFORM;

如果时区不匹配,可以考虑重新设置时区:

ALTER DATABASE SET TIME_ZONE=’source_time_zone’;

然后再尝试可迁移导出。


数据运维技术 » ORA-39360: Table string was skipped due to transportable import and TSLTZ issues resulting from time zone mismatch. ORACLE 报错 故障修复 远程处理