|
Code
|
Class
|
Type
|
Description
|
|---|---|---|---|
|
10002
|
Database
|
Error
|
Operation failed.
Meaning: The connect operation failed with an unexpected error. Most likely, the servers are not properly synchronized.
|
|
10013
|
Database
|
Error
|
Transaction is read-only.
Meaning: You have tried to write inside a transaction that is set read-only, or the server is temporarily set to read-only mode, for example during the state switch. Updatable transactions are not allowed.
|
|
10019
|
Database
|
Error
|
Backup is already active.
Meaning: You have tried to start a backup or copy when one is already in progress.
|
|
10024
|
Database
|
Error
|
Illegal backup directory “directory_name”.
Meaning: The backup or copy directory is either an empty string or a dot indicating that the backup or copy will be created in the current directory.
|
|
10030
|
Database
|
Error
|
Backup or copy directory 'directory_name' does not exist.
Meaning: Backup or copy directory is not found. Check the name of the backup or copy directory.
|
|
10045
|
Database
|
Error
|
This operation cannot be executed on a HotStandby Secondary server.
Meaning: This operation cannot be executed on a HotStandby Secondary server.
In order for the requested operation to succeed, the server must be a Primary.
|
|
10046
|
Database
|
Error
|
Operation failed, data dictionary operation is active. Meaning: A data dictionary operation is currently in progress.
|
|
10047
|
Database
|
Error
|
Replicated transaction is aborted.
Meaning: Transactions are aborted, for example, in a state switch. When the server state is switched from Primary to Secondary, all active transactions are aborted.
|
|
10048
|
Database
|
Error
|
Replicated transaction contains data dictionary changes, normal update operations are not allowed.
Meaning: HotStandby mode restricts data dictionary operations; for example, CREATE TABLE cannot be mixed with normal update operations.
This message is obsolete in version 4.1 and later, which allow you to mix DML and DDL operations within a transaction while using HSB.
|
|
10049
|
Database
|
Error
|
The remote server is not a secondary server.
Meaning: The server that you specified in the command is not in a SECONDARY state.
|
|
10050
|
Database
|
Error
|
Replicated operation updated BLOB columns.
Meaning: BLOB columns cannot be replicated to the Secondary server.
|
|
10078
|
Database
|
Error
|
User rolled back the transaction.
|
|
10079
|
Database
|
Error
|
Cannot remove filespec. File is already in use.
|
|
10080
|
Database
|
Error
|
HotStandby Secondary server can not execute operation received from Primary server.
Meaning: A possible cause for this error is that the database did not originate from the Primary server using HotStandby copy or netcopy command.
|
|
10081
|
Database
|
Error
|
The database file is incomplete or corrupt.
Meaning: If the file is on a hot standby secondary server, use the hotstandby copy or hotstandby netcopy command to send the file from the primary server again.
|
|
10082
|
Database
|
Error
|
Backup aborted.
|
|
10083
|
Database
|
Error
|
Failed to abort HSB transaction because commit is already sent to secondary.
|
|
10084
|
Database
|
Error
|
Table is not locked.
|
|
10085
|
Database
|
Error
|
Checkpointing is disabled.
|
|
10087
|
Database
|
Error
|
HotStandby not allowed for main memory tables.
|
|
10088
|
Database
|
Error
|
Specified lock timeout is too large.
|
|
10089
|
Database
|
Error
|
Operation failed, server is in HSB primary uncertain mode.
|