ORA-01466: unable to read data - table definition has changed
2014-07-01 20:11
246 查看
今天做基于时间戳的闪回查询,出现了错误:ORA-01466: unable to read data - table definition has changed
官方文档的解释:
ORA-01466: unable to read data - table definition has changed
Cause: Query parsed after tbl (or index) change, and executed w/old snapshot
Action: commit (or rollback) transaction, and re-execute
在网上找到一个
> Solution Description:
> =====================
>
> This is usually caused when some change has been made to the
> initialisation parameter FIXED_DATE or the system date. It can occur
> Under different circumstances.
>
> 1. When doing Date testing and the init.ora parameter FIXED_DATE
> has been set to a future date. When the database is started, then
> that date & TIME does not change.
>
> So any objects created will have exactly the same Date & Time
> stamp as the FIXED_DATE.
>
> Now When you come to run the EXPORT, it checks the SYSDATE
> and the creation dates for the objects.
>
> You need to modify the TIME in the FIXED_DATE parameter,
> i.e. add 1 hour or few minutes, etc and you will not
> encounter the error ORA-1466 anymore.
>
> 2. The Operating System was reinstalled because of the server crash.
> The system date was not set correctly. The year was set to 2001
> instead of 1997 when they reinstalled Oracle. After some DB
> activity
> they realized the date was incorrect and reset it to 1997 causing
> some
> objects to exist with future dates.
>
> Perform full database export without specifying consistent=y and
> recreate the database.- Òþ²Ø±»ÒýÓÃÎÄ×Ö -
引用自:http://www.orafaq.com/usenet/comp.databases.oracle.server/2007/03/31/1586.htm
解决方法:指定一下会话的时间格式,重新执行即可。
10:26:02 TYGER@ORCL>alter session set nls_date_format='yyyy-mm-dd hh24:mi:ss';
Session altered.
10:26:30 TYGER@ORCL>select sysdate from dual;
SYSDATE
-------------------
2014-03-14 10:26:38
10:27:12 TYGER@ORCL>select * from fb_tyger as of timestamp to_timestamp('2014-03-14 10:26:38','yyyy-mm-dd hh24:mi:ss');
DEPTNO DNAME LOC
---------- -------------- -------------
10 ACCOUNTING NEW YORK
20 RESEARCH DALLAS
30 SALES CHICAGO
40 OPERATIONS BOSTON
官方文档的解释:
ORA-01466: unable to read data - table definition has changed
Cause: Query parsed after tbl (or index) change, and executed w/old snapshot
Action: commit (or rollback) transaction, and re-execute
在网上找到一个
> Solution Description:
> =====================
>
> This is usually caused when some change has been made to the
> initialisation parameter FIXED_DATE or the system date. It can occur
> Under different circumstances.
>
> 1. When doing Date testing and the init.ora parameter FIXED_DATE
> has been set to a future date. When the database is started, then
> that date & TIME does not change.
>
> So any objects created will have exactly the same Date & Time
> stamp as the FIXED_DATE.
>
> Now When you come to run the EXPORT, it checks the SYSDATE
> and the creation dates for the objects.
>
> You need to modify the TIME in the FIXED_DATE parameter,
> i.e. add 1 hour or few minutes, etc and you will not
> encounter the error ORA-1466 anymore.
>
> 2. The Operating System was reinstalled because of the server crash.
> The system date was not set correctly. The year was set to 2001
> instead of 1997 when they reinstalled Oracle. After some DB
> activity
> they realized the date was incorrect and reset it to 1997 causing
> some
> objects to exist with future dates.
>
> Perform full database export without specifying consistent=y and
> recreate the database.- Òþ²Ø±»ÒýÓÃÎÄ×Ö -
引用自:http://www.orafaq.com/usenet/comp.databases.oracle.server/2007/03/31/1586.htm
解决方法:指定一下会话的时间格式,重新执行即可。
10:26:02 TYGER@ORCL>alter session set nls_date_format='yyyy-mm-dd hh24:mi:ss';
Session altered.
10:26:30 TYGER@ORCL>select sysdate from dual;
SYSDATE
-------------------
2014-03-14 10:26:38
10:27:12 TYGER@ORCL>select * from fb_tyger as of timestamp to_timestamp('2014-03-14 10:26:38','yyyy-mm-dd hh24:mi:ss');
DEPTNO DNAME LOC
---------- -------------- -------------
10 ACCOUNTING NEW YORK
20 RESEARCH DALLAS
30 SALES CHICAGO
40 OPERATIONS BOSTON
相关文章推荐
- ORA-01466: unable to read data - table definition has changed
- ORA-01466: unable to read data - table definition has changed
- ORA-01466: unable to read data - table definition has changed
- DBSPI40-1: Unable to fetch data from table 'V$SYSSTAT' [ORA-03135: connection lost contact]
- ORA-01653: unable to extend table FND_CONCURRENT_REQUESTS by 16 in tablespace APPS_TS_TX_DATA
- SQLException: ORA-01653: unable to extend table ... by 1024 in tablespace RISK_DATA
- 【hbase】Unable to read additional data from client sessionid 0x15c92bd1fca0003, likely client has closed socket
- EndOfStreamException: Unable to read additional data from client sessionid 0x0, likely client has cl
- Unable to read additional data from client sessionid 0x0, likely client has closed socket
- ORA-01652 : Unable to extend temp segment by 128 in tablespace temp
- ORA-00604: error occurred at recursive SQL level 1 ORA-01653: unable to extend table SYS.AUD$ by 8192 in tablespace SYSTEM
- ORA-01652:unable to extend temp segment by num in tablespace name
- form builder was unable to read the device settings from the datastore问题解决
- ora-01654 ORA-01654: unable to extend index HRERP.INDEX_DATE by 128 in tablespace
- ORA-1652错误 unable to extend temp segment by 128 in tablespace
- ORA-01653: unable to extend table string.string by string in tablespace string
- Oracle内部错误ORA-07445: [ACCESS_VIOLATION] [unable_to_trans_pc][UNABLE_TO_READ]
- ORA-1652: unable to extend temp segment by 128 in tablespace
- ORA-01652:unable to extend temp segment by num in tablespace name
- WARNING: failed to online diskgroup resource ora.DATA.dg (unable to communicate with CRSD/OHASD)