11g Oracle TimesTen内存数据库错误消息与SNMP陷阱详解

oracle

需积分: 5 18 浏览量更新于2024-06-25 收藏 6.64MB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

资源详情

资源推荐

Errors 0 - 999

1-8 Oracle TimesTen In-Memory Database Error Messages and SNMP Traps

601 Checkpoint failure

Type of Message: Error

Cause: Checkpointing failed.

Impact: TimesTen cannot create the

checkpoint.

User Action: Check that there is sufficient

disk space and that database files are

writable, then retry.

602 Transaction already has a

pending fuzzy checkpoint

request

Type of Message: Error

Cause: A transaction attempted to perform a

checkpoint, but the transaction has a

pending checkpoint request.

Impact: TimesTen cannot perform the

checkpoint.

User Action: Commit or rollback the current

checkpoint transaction. Then, retry the

checkpoint operation in a new transaction,

using the

ttCkpt

built-in procedure. For

more information, see "ttCkpt" in the Oracle

TimesTen In-Memory Database Reference.

603 Transaction already has a

pending checkpoint request

Type of Message: Error

Cause: A transaction attempted to perform a

fuzzy checkpoint. However, the transaction

has a pending checkpoint request.

Impact: TimesTen cannot perform the fuzzy

checkpoint.

User Action: Commit or rollback the current

checkpoint transaction. Then, retry the fuzzy

checkpoint operation in a new transaction,

using the

ttCkpt

built-in procedure. For

more information, see "ttCkpt" in the Oracle

TimesTen In-Memory Database Reference.

604 Log missing record for

checkpoint file (lsn

log_file_number.log_file_

offset).

info

Type of Message: Error

Cause: The transaction log on disk may be

truncated or corrupted. The transaction log

may be missing log records related to the

specified checkpoint file.

Impact: TimesTen ignores the transaction log

on disk, moves any existing log files to the

specified directory, and recovers the database

from the checkpoint files.

User Action: None.

605 Checkpoint Log record

(number.number)

not present

Type of Message: Error

Cause: The specified log record is either

missing or corrupted. If the transaction log

on disk has been truncated or otherwise

corrupted, it may be missing log records

corresponding to the checkpoints on disk.

Impact: The database cannot be loaded into

memory.

User Action: Contact TimesTen Customer

Support.

Error

number Error or warning message Details

Errors 0 - 999

Warnings and Errors 1-9

606 Checkpoint cannot proceed

because another checkpoint

or backup is in progress

Type of Message: Error

Cause: TimesTen cannot execute a

checkpoint operation cannot because another

checkpoint or backup is in progress.

Impact: The current checkpoint operation

cannot begin.

User Action: Wait until the backup or

checkpoint has completed and retry the

checkpoint operation.

607 Backup cannot proceed

because another checkpoint

or backup is in progress

Type of Message: Error

Cause: TimesTen cannot execute a backup

operation because another checkpoint or

backup is in progress.

Impact: The current backup operation cannot

begin.

User Action: Wait until the backup or

checkpoint has completed and retry the

backup operation. If you attempted a

ttRepAdmin -duplicate

operation, retry the

operation.

608 Another connection

(# connection_id) has already

configured table table_name

for parallel insert

Type of Message: Error

Cause: This error message can only occur on

an Exalytics Business Intelligence server. The

ttParallelInsertBegin

built-in procedure

failed because another connection already

configured the specified table for parallel

insert mode.

Impact: The specified table cannot be

configured for parallel insert mode.

User Action: Wait and retry the operation.

Consider terminating the existing

ttParallelInsertBegin

built-in procedure

by using the

ttParallelInsertEnd

built-in

procedure.

609 Data store failed validity

check

Type of Message: Internal Error

Cause: TimesTen found an invalid database

block while performing a checkpoint.

Impact: The current checkpoint operation

cannot complete. If several checkpoints fail

in a row, the log files will start accumulating.

User Action: Retry the checkpoint operation.

If the problem persists, use the

ttAdmin

utility to unload and then reload the

database into memory. For more information

on the

ttAdmin

utility, see "ttAdmin" in the

Oracle TimesTen In-Memory Database Reference.

If this does not solve the error, contact

TimesTen Customer Support.

Error

number Error or warning message Details

Errors 0 - 999

1-10 Oracle TimesTen In-Memory Database Error Messages and SNMP Traps

610 End-checkpoint log record

not found

Type of Message: Internal Error

Cause: TimesTen cannot find a checkpoint

related log record while loading the database

into memory.

Impact: The database cannot be loaded into

memory.

User Action: Contact TimesTen Customer

Support.

611 Backup process died

Type of Message: Error

Cause: The

ttBackupStatus

built-in

procedure returns this error message when

an in-progress backup was killed or died

unexpectedly.

Impact: TimesTen cannot to create a backup

copy of the database.

User Action: Attempt to create another

backup of the database with the

ttBackup

utility. For more information on the

ttBackup

utility, see "ttBackup" in the Oracle TimesTen

In-Memory Database Reference. If this is a

recurrent error, contact TimesTen Customer

Support.

620 Another table (table_name) is

already configured for

parallel insert

Type of Message: Error

Cause: This error message can only occur on

an Exalytics Business Intelligence server. The

ttParallelInsertBegin

built-in procedure

failed because another table is already

configured for parallel insert mode. Only one

table is allowed to be in parallel insert mode

at any given time.

Impact: The table you specified cannot be

configured for parallel insert mode.

User Action: Wait and retry the operation.

Consider terminating the existing

ttParallelInsertBegin

built-in procedure

by using the

ttParallelInsertEnd

built-in

procedure.

621 Table table_name is already

configured for parallel

insert. To change

parallelism, call

ttParallelInsertEnd and then

ttParallelInsertBegin again.

Type of Message: Error

Cause: This error message can only occur on

an Exalytics Business Intelligence server. The

ttParallelInsertBegin

built-in procedure

failed because the specified table is already

configured for parallel insert mode. Only one

table is allowed to be in parallel insert mode

at any given time.

Impact: None.

User Action: None.

Error

number Error or warning message Details

剩余345页未读，继续阅读

weixin_40191861_zj

粉丝: 78
资源: 1万+

11g Oracle TimesTen内存数据库错误消息与SNMP陷阱详解

Oracle Enterprise Manager for Oracle TimesTen In-Memory Database

129255-oracle_timesten_in-memory_database

Oracle TimesTen In-Memory Database System Tables and Views Refer

oracle数据库有没有内存数据库

Oracle TimesTen 如何与oracle database数据同步

Java怎么集成Oracle TimesTen

mybatis操作Oracle TimesTen

Oracle TimesTen 如何安装

oracle数据库的发展历史

Timesten与MySQL数据交互方法步骤

Timesten与MySQL数据交互

timesten 11.2.2.8 linux8864 下载

‘shmget’ was not declared in this scope

高级数据库系统国内外研究现状

Oracle TimesTen In-Memory Database Troubleshooting Guide 11g Rel

Oracle TimesTen In-Memory Database Installation Guide 11g Releas

Oracle TimesTen In-Memory Database PL/SQL Developer's Guide 11g

Oracle TimesTen In-Memory Database Reference 11g Release 2 (11.2

Oracle TimesTen In-Memory Database TTClasses Guide 11g Release 2

Oracle TimesTen In-Memory Database Replication Guide 11g Release

最新资源