Skip Headers

Oracle® Application Server High Availability Guide 10g Release 3 (10.1.3) B15977-01 |
| Home | Solution Area | Contents | Index

Previous | Next |

# B OracleAS Guard Error Messages

The following sections describe the OracleAS Guard error messages. Though not shown, OracleAS Guard error messages are preceded by an ASG prefix. Error messages are categorized into the following groups and subgroups:

- DGA Error Messages

  - LRO Error Messages

  - Undo Error Messages

  - Create Template Error Messages

  - Switchover Physical Standby Error Messages

- Duf Error Messages

  - Database Error Messages

  - Connection and Network Error Messages

  - SQL*Plus Error Messages

  - JDBC Error Messages

  - OPMN Error Messages

  - Net Services Error Messages

  - System Error Messages

  - Warning Error Messages

  - OracleAS Database Error Messages

  - OracleAS Topology Error Messages

  - OracleAS Backup and Restore Error Messages

  - OracleAS Guard Synchronize Error Messages

  - OracleAS Guard Instantiate Error Messages

## B.1 DGA Error Messages

The following are DGA error messages.

Note: The symbols {0}, {1}, and {2} are variables that will be replaced by the name of the object.

12001, Error while creating a DGA template.
  Cause: An error occurred while creating a template file.
  Action: See secondary error.

12500, Standby database instance {0} already exists on host {1}.
  Cause: The standby database instance specified already exists on target host.
  Action: Either select a new instance or remove the current instance.

### B.1.1 LRO Error Messages

The following are LRO error messages.

13000, Error during Create Physical Standby: Prepare-init.
  Cause: Error occurred during specified step.
  Action: See secondary error.

13001, Error during Create Physical Standby: Prepare-check standby.
  Cause: Error occurred during specified step.
  Action: See secondary error.

13002, Error during Create Physical Standby: Prepare-primary processing.
  Cause: Error occurred during specified step.
  Action: See secondary error.

13003, Error during Create Physical Standby: Prepare-standby processing.
  Cause: Error occurred during specified step.
  Action: See secondary error.

13004, Error during Create Physical Standby: Prepare-sqlnet configuration.
  Cause: Error occurred during specified step.
  Action: See secondary error.

13005, Error during Create Physical Standby: Copy-init.
  Cause: Error occurred during specified step.
  Action: See secondary error.

13006, Error during Create Physical Standby: Copy-validate standby.
  Cause: Error occurred during specified step.
  Action: See secondary error.

13007, Error during Create Physical Standby: Copy-file copy.
  Cause: Error occurred during specified step.
  Action: See secondary error.

13008, Error during Create Physical Standby: Finish-init.
  Cause: Error occurred during specified step.
  Action: See secondary error.

13009, Error during Create Physical Standby: Finish-prepare primary.
  Cause: Error occurred during specified step.
  Action: See secondary error.

13010, Error during Create Physical Standby: Finish-configure primary.
  Cause: Error occurred during specified step.
  Action: See secondary error.

13011, Error during Create Physical Standby: Finish-configure standby.
  Cause: Error occurred during specified step.
  Action: See secondary error.

### B.1.2 Undo Error Messages

The following are undo error messages.

13015, Error trying to Undo Create Physical Standby: Prepare.
  Cause: Error occurred during undo of the prepare task.
  Action: See secondary error.

13016, Error trying to Undo Create Physical Standby: Copy.
  Cause: Error occurred during undo of the copy task.
  Action: See secondary error.

13017, Error trying to Undo Create Physical Standby: Finish.
  Cause: Error occurred during undo of the finish task.
  Action: See secondary error.

### B.1.3 Create Template Error Messages

The following are create template error messages.

13020, Error during Create Template: init.
  Cause: Error occurred during specified step.
  Action: See secondary error.

13021, Error during Create Template: primary processing.
  Cause: Error occurred during specified step.
  Action: See secondary error.

13022, Error during Create Template: standby processing.
  Cause: Error occurred during specified step.
  Action: See secondary error.

13023, Error during Create Template: finish.
  Cause: Error occurred during specified step.
  Action: See secondary error.

### B.1.4 Switchover Physical Standby Error Messages

The following are switchover physical standby error messages.

13051, Error performing a physical standby switchover.
  Cause: Error occurred in performing a switchover.
  Action: See secondary error.

13052, The primary database is not in the proper state to perform a switchover.
  Cause: The switchover status of the primary database must be either "TO STANDBY" or "SESSIONS ACTIVE".
  Action: Make sure the SWITCHOVER_STATUS of the V$DATABASE table is either "TO STANDBY" or "SESSIONS ACTIVE".

13053, The standby database is not in the proper state to perform a switchover.
  Cause: The switchover status of the standby database must be either "TO PRIMARY" or "SWITCHOVER PENDING".
  Action: Make sure the SWITCHOVER_STATUS of the V$DATABASE table is either "TO PRIMARY" or "SWITCHOVER PENDING".

13504, Error switching the database role from primary to standby.
  Cause: Failed to switchover database role from primary to standby.
  Action: See secondary error.

13505, Error switching the database role from standby to primary.
  Cause: Failed to switchover database role from standby to primary.
  Action: See secondary error.

13061, Error failing over physical standby database.
  Cause: Error occurred in performing a failover of a standby database.
  Action: See secondary error.

## B.2 Duf Error Messages

The following are Duf error messages.

3000, Server error {0}.
  Cause: Invalid argument was supplied.
  Action: Pass in a valid argument.

3001, Invalid argument {0}.
  Cause: Invalid argument was supplied.
  Action: Pass in a valid argument.

3002, Invalid log path {0}.
  Cause: Invalid log path specification.
  Action: Specify a valid log path.

3003, Invalid command line value {0} specified.
  Cause: Invalid command line specification.
  Action: Correct the command line option and retry.

3004, Invalid command action {0} specified.
  Cause: Invalid command action specification.
  Action: Correct the command line action and retry.

3005, Invalid command argument {0} specified, commands must begin with a hyphen.
  Cause: Command argument did not start with a hyphen.
  Action: Enter a correct command line argument.

3006, Command line argument {0} missing a required value.
  Cause: Command argument missing a required value.
  Action: Enter a correct command line argument value.

3007, Command line argument {0} given an incorrect value {1}.
  Cause: Command argument value is incorrect.
  Action: Enter a correct command line argument value.

3008, Command line argument {0} is required but missing.
  Cause: Command argument value is missing.
  Action: Enter a correct command line argument value.

3009, Invalid session ID.
  Cause: The client passed an invalid session ID.
  Action: Enter a correct command line argument value.

3010, Duplicate session ID.
  Cause: The session ID is already in use.
  Action: Enter a correct command line argument value.

3011, Unsatisfied link error for {0} in library DufNatives.
  Cause: An attempt to make a call using the DufNatives library failed.
  Action: Make sure the DufNatives library is correctly installed.

3012, Checksum error in password.
  Cause: The login password has a checksum error.
  Action: Try to reconnect.

3013, Operation failed.
  Cause: The specified operation failed.
  Action: See secondary error.

3014, Invalid command line specified.
  Cause: Invalid command line specification.
  Action: Correct command line option and retry.

3015, Error getting local host name.
  Cause: Error trying to get local host name.
  Action: See secondary error.

3016, No encrypt key.
  Cause: No encrypt key supplied. Encryption requires an encrypt key.
  Action: This is an internal programming error.

3017, Error encrypting data.
  Cause: Failed to encrypt the given data.
  Action: See secondary error.

3018, Error missing plan for specified request {0}, cannot process.
  Cause: Could not find plan for specified request.
  Action: Either specify a valid request or supply valid plan.

3019, Server does not recognize application ID.
  Cause: Client specified an application ID that the server does not support.
  Action: Contact Oracle support.

3020, Failed to authenticate user {0}. Please enter the correct user name and password.
  Cause: Client supplied incorrect OS user name or password or both.
  Action: Make sure the correct OS user name and password are used.

3021, No user name and/or password are supplied for authentication.
  Cause: Client did not supply a user name or password or both through the "connect duf" command.
  Action: Make sure user issue a "connect duf" command before any other commands.

3022, Failed to authorize user {0}. User must have administrator privilege on the server system.
  Cause: The user name provided by the client to connect to DUF server must have administrator privilege on the server system. This error is applicable on Windows system only.
  Action: Make sure the user account belongs to the administrator group on the server system.

3023, Error: There is no connection to a DUF server.
  Cause: You must connect to DUF server before issues other commands.
  Action: Connect to the DUF server.

3024, Failed to authorize user {0}. The owner account of the Oracle Home must be used.
  Cause: The user name provided by the client to connect to DUF server must be the same user from which the Oracle home is installed. This error is applicable on UNIX system only.
  Action: Make sure the user account is the same as that of the Oracle home.

3025, The operation has been cancelled.
  Cause: The operation has been cancelled by either the user or the DUF internal software.
  Action: None.

3026, The {0} task must complete successfully before running the {1} task.
  Cause: An attempt was made to run the specified task before the required previous task has successfully completed.
  Action: Rerun the required previous task.

3027, Error while executing {0} at step - {1}.
  Cause: Error during specified step of specified operation.
  Action: Check secondary error.

3028, Failed to start DUF server on host {0}.
  Cause: Error during specified step of specified operation.
  Action: Check DUF log file for more information.

3029, Failed to start {0} server with exception.
  Cause: Error trying to start the server.
  Action: See secondary error.

3030, Error, cannot resolve host name {0}.
  Cause: Error trying to resolve specified host name.
  Action: Check that the host name is correctly specified.

3031, Error, Invalid user name {0}. Only {1} account can connect to a ASG server.
  Cause: Only ias_admin can connect to a ASG server.
  Action: Please use ias_admin to connect to a ASG server.

3032, Failed to start {0} server on host {1}. Start server on specified host and reconnect.
  Cause: Error trying to start the server on the specified host while trying to connect.
  Action: Start the server manually and retry the connect.

3033, Error, the server is shutting down.
  Cause: Error communicating with the server.
  Action: Retry the operation.

3034, Invalid command line specified: - {0}.
  Cause: Invalid command line specification.
  Action: Correct the command line option and retry.

3035, Failed to kill the OracleAS Guard (ASG) server process {0} with error {1}.
  Cause: OracleAS Guard client is unable to kill the OracleAS Guard (ASG) server process.
  Action: Use "kill -9 <pid>" command to kill the process from the command line prompt.

3100, Error reading file {0}.
  Cause: Error trying to read from file.
  Action: See secondary error.

3101, Error writing file {0}.
  Cause: Error trying to write file.
  Action: See secondary error.

3102, Error creating file {0}.
  Cause: Error trying to create specified file.
  Action: See secondary error.

3103, Error deleting file {0}.
  Cause: Error trying to delete a file.
  Action: See secondary error.

3104, Error opening file {0}.
  Cause: Error trying to open file.
  Action: See secondary error.

3105, File {0} not found.
  Cause: Error trying to open file.
  Action: See secondary error.

3106, No read access to file {0}.
  Cause: Error trying to open file.
  Action: See secondary error.

3107, No write access to file {0}.
  Cause: Error trying to open file.
  Action: See secondary error.

3108, File specification {0} must be absolute.
  Cause: Error trying to open file.
  Action: See secondary error.

3109, Error closing file {0}.
  Cause: Error trying to close the file.
  Action: See secondary error.

3110, Error creating dir {0}.
  Cause: Error trying to create specified directory.
  Action: See secondary error.

3111, Error deleting dir {0}.
  Cause: Error trying to delete specified directory.
  Action: See secondary error.

3112, Error expanding file wildcard specification {0}.
  Cause: Error trying to process file wildcard specification.
  Action: See secondary error.

3120, Error opening configuration file {0}.
  Cause: Error trying to open configuration file.
  Action: Make sure configuration file exists or specified correctly.

3121, Error creating zip file {0}.
  Cause: Error trying to create a zip file.
  Action: See secondary error.

3122, There are no files to be zipped.
  Cause: The directory to be zipped has no files in it.
  Action: Make sure the directory to be zipped has files in it.

3123, Error adding files in directory {0} to zip file.
  Cause: Error adding files in the given directory to zip file.
  Action: See secondary error.

3124, No zip file is specified.
  Cause: No zip file is specified.
  Action: Internal error.

3125, Error extracting files from zip file {0}.
  Cause: Error extracting files from a zip file.
  Action: See secondary error.

3400, Error processing XML document.
  Cause: Error processing XML document.
  Action: See secondary error.

3401, Error processing XML node.
  Cause: Error processing XML node.
  Action: See secondary error.

3402, Error parsing XML request message.
  Cause: There was an error parsing the XML request message.
  Action: Contact Oracle support.

3403, Error parsing XML response message.
  Cause: There was an error parsing the XML request message.
  Action: Contact Oracle support.

3404, Error parsing XML body string.
  Cause: There was an error parsing the XML body string.
  Action: Contact Oracle support.

3405, Error writing the body to an XML DOM.
  Cause: There was an error writing the XML body string.
  Action: Contact Oracle support.

3406, Error reading the body from an XML DOM.
  Cause: There was an error reading the XML body string.
  Action: Contact Oracle support.

3407, Error writing a work item to an XML DOM.
  Cause: There was an error reading the XML body string.
  Action: Contact Oracle support.

3408, Error reading a work item from an XML DOM.
  Cause: There was an error reading the XML body string.
  Action: Contact Oracle support.

3409, Error parsing an XML string.
  Cause: There was an error parsing the XML string.
  Action: Contact Oracle support.

3410, Error converting XML DOM to string.
  Cause: There was an error converting the DOM tree to a XML string.
  Action: Contact Oracle support.

3411, Error reading XML DOM tree.
  Cause: There was an error reading the XML DOM tree.
  Action: Contact Oracle support.

### B.2.1 Database Error Messages

The following are database error messages.

3501, Failed to initialize DufDb class.
  Cause: There was an error creating the DufDb class.
  Action: See secondary error.

3502, Failed to connect to database {0}.
  Cause: There was an error connecting to the database.
  Action: See secondary error.

3503, Failed to verify database {0}.
  Cause: There was an error verifying the database.
  Action: See secondary error.

3504, Failed to start database {0}.
  Cause: There was an error starting the database.
  Action: See secondary error.

3505, Failed to create pfile to include spfile.
  Cause: There was an error creating the given pfile.
  Action: See secondary error.

3506, Failed to turn on archivelog mode for the database.
  Cause: There was an error turning on archivelog mode.
  Action: See secondary error.

3507, Failed to create the standby database control file.
  Cause: There was an error creating the standby database control file.
  Action: See secondary error.

3508, Failed to create the pfile.
  Cause: There was an error creating the database init parameter file.
  Action: See secondary error.

3509, Failed to create the spfile.
  Cause: There was an error creating the database spfile.
  Action: See secondary error.

3510, Output reader thread for {0} terminated.
  Cause: The output reader thread is terminated.
  Action: Contact Oracle support.

3511, Error creating local worker on node {0}.
  Cause: This is an internal error.
  Action: Contact Oracle support.

3512, Error creating remote worker on node {0}.
  Cause: There is a problem communicating with the remote server.
  Action: Make sure that the remote server is accessible.

3513, Database is not started {0}.
  Cause: The specified database has not been started.
  Action: Start the specified database.

3514, Failed to stop database {0}.
  Cause: There was an error stopping the database.
  Action: See secondary error.

3515, Failed querying database to determine current archivelog mode.
  Cause: There was an error querying the database to determine current archive mode.
  Action: See secondary error.

3516, Failed to query redo log information for database.
  Cause: There was an error querying the database redo log information.
  Action: See secondary error.

3517, Failed to drop standby redo log for database.
  Cause: There was an error dropping the standby redo log.
  Action: See secondary error.

3518, Failed to start managed recovery for standby database.
  Cause: There was an error starting managed recovery for the standby database.
  Action: See secondary error.

3519, Failed to cancel managed recovery for standby database.
  Cause: There was an error cancelling managed recovery for the standby database.
  Action: See secondary error.

3520, Failed to determine the existence of database instance.
  Cause: There was an error determining the existence of the given database instance.
  Action: See secondary error.

3521, Invalid database instance {0} specified in the template file; DUF found instance {1}.
  Cause: The standby database instance specified in the template file is different from the one DUF found on the system.
  Action: Please either rerun the prepare and copy phases with the new standby instance or specify the correct standby database instance found on the system.

3522, The pfile {0} needed to generate an spfile is missing.
  Cause: A pfile needed to create the spfile used by the standby database is missing.
  Action: Please either rerun the prepare and copy phases to generate the pfile or manually create one with the correct values.

3523, The standby database cannot have the same service name as the primary database.
  Cause: The standby service name is the same as the primary.
  Action: Change the standby service name.

3524, Error: The primary database is not set.
  Cause: The primary database is not defined.
  Action: Set the primary database first.

3525, Error: The standby database is not set.
  Cause: The standby database is not defined.
  Action: Set the standby database first.

3526, Set the primary database before setting the standby database.
  Cause: The standby service name is the same as the primary on the same host.
  Action: Change the standby service name.

3527, The database tablespace map is NULL.
  Cause: This is an internal error.
  Action: Contact Oracle support.

3528, Error initializing init parameter file {0}.
  Cause: An error occurred trying to initialize the parameter file.
  Action: See secondary error.

3529, Error writing init parameter file {0}.
  Cause: An error occurred trying to write the parameter file.
  Action: See secondary error.

3530, Error in setting the protection mode for database {0}.
  Cause: An error occurred trying to set the protection mode.
  Action: See secondary error.

3531, Error opening database in read only mode for database {0}.
  Cause: An error occurred trying to open the database in read only mode.
  Action: See secondary error.

3532, Failed to get init parameter value from {0}.
  Cause: Error trying to get the parameter value from the init parameter file.
  Action: See secondary error.

3533, No user name and/or password is specified for database {0}.
  Cause: Error trying to get the parameter value from the init parameter file.
  Action: User must specify the user name and password to be used to connect to the database using "set primary database" or "set standby database" command.

3534, The standby database cannnot have the same host as the primary database.
  Cause: The standby host is the same as the primary.
  Action: Change the standby or primary database host name.

3535, Failed to create standby redo log.
  Cause: An error occurred trying to create a standby redo log.
  Action: See secondary error.

3536, Failed to get a list of standby database(s) from log archive destination.
  Cause: An error occurred trying to get a list of standby databases from the log archive destination parameters.
  Action: See secondary error.

3537, Failed to add standby database as a log archive destination.
  Cause: An error occurred trying to add a standby database as a log archive destination.
  Action: See secondary error.

3538, Failed to remove standby database as a log archive destination.
  Cause: An error occurred trying to remove a standby database as a log archive destination.
  Action: See secondary error.

3539, Error: The new primary database is not set.
  Cause: The new primary database is not defined.
  Action: Set the new primary database first.

3540, Error processing template file {0}.
  Cause: Error trying to process template file.
  Action: Correct protection and retry operation.

3541, Invalid database protection specified in template file {0}.
  Cause: Error trying to process protection value in template file.
  Action: Correct protection and retry operation.

3542, Failed to query database role.
  Cause: Error trying to query the database role.
  Action: See secondary error.

3543, Error processing command, must be connected to a OracleAS Guard server in the primary topology.
  Cause: User is connected to server on a topology that is not the primary topology.
  Action: Connect to primary topology node.

3544, Error processing command, must be connected to a OracleAS Guard server in the standby topology.
  Cause: User is connected to server on a topology that is not the standby topology.
  Action: Connect to primary topology node.

3545, Error trying to remove old passwd file %1 while creating new db.
  Cause: Could not delete the old password file as part of a delete database operation. This is a problem when trying to create a new database.
  Action: Delete the stale password file.

3546, Error, database SID was expected to have value but it is empty.
  Cause: The database SID was suppose to have a value but it is empty.
  Action: This is an internal error.

3547, Error storing DB Credentials in the clipboard of the server.
  Cause: Failed to store DB credentials in the clipboard on the specified server.
  Action: Internal error.

3548, Error storing DB info in the clipboard of the server.
  Cause: Failed to store DB information in the clipboard on the specified server.
  Action: Internal error.

3549, Error cleaning up the database on the standby host.
  Cause: Failed to clean up the database on the standby host.
  Action: See secondary error.

3550, Failed to find a valid Oracle Home.
  Cause: A valid Oracle home was not found for this operation.
  Action: Create a valid Oracle home.

3551, Oracle Data Guard Home must have the same owner as the database server home.
  Cause: The Oracle Data Guard Home is owned by a different user than the database server home.
  Action: Reinstall Oracle Data Guard user from the owner of Oracle database server.

3552, Specified Oracle Home {0} could not be found.
  Cause: The specified Oracle home could not be found.
  Action: Please specify a valid Oracle home.

3553, An error occurred getting the list of Oracle Homes on the system.
  Cause: The list of Oracle homes could not be read.
  Action: Make sure the Oracle inventory is valid.

3554, The Oracle home that contains SID {0} cannot be found.
  Cause: The Oracle home that contains a specific SID cannot be found.
  Action: Make sure the Oracle home inventory is valid.

3555, Error accessing the Oracle home inventory. Make sure the inventory file exists.
  Cause: The Oracle home inventory cannot be accessed.
  Action: Make sure the Oracle home inventory exists

3556, Error: Unable to find the Oracle home within path {0}.
  Cause: The Oracle home within the given path cannot be found.
  Action: Make sure the Oracle home inventory exists.

### B.2.2 Connection and Network Error Messages

The following are connection and network error messages.

3600, Error connecting to server: Unknown node {0}.
  Cause: The server host is unknown to the client.
  Action: Contact Oracle support.

3601, Error connecting to server node {0}.
  Cause: The client cannot connect to the server.
  Action: Contact Oracle support.

3602, File Copy protocol error.
  Cause: There was an internal protocol error while copying files.
  Action: Contact Oracle support

3603, Error sending data across network.
  Cause: There was a network error.
  Action: Retry operation.

3604, Error receiving data across network.
  Cause: There was a network error.
  Action: Retry operation.

3605, The file copy operation has been terminated.
  Cause: The copy aborted due to an error.
  Action: Retry operation.

3606, Error connecting to file copy server {0} on port {0}.
  Cause: The copy server is not running.
  Action: Contact Oracle support.

3607, Error opening file copy server socket on {0} with port {0}.
  Cause: The copy aborted due to an error.
  Action: Retry operation.

3608, Error connecting to clipboard.
  Cause: There is no connection to the clipboard server.
  Action: Retry operation.

3609, Error while copying {0} to {1}.
  Cause: Error occurred during a file copy.
  Action: See secondary error.

3610, Error starting online backup.
  Cause: Error occurred while putting tablespace in online backup mode.
  Action: See secondary error.

3611, Error ending online backup.
  Cause: Error occurred while restore tablespace from online backup mode.
  Action: See secondary error.

3612, Error listening on server port {0}.
  Cause: Error occurred while listening on port.
  Action: Check if server is already running.

3613, Network Buffer Overflow Detected.
  Cause: The network protocol detected a buffer overflow due to a bug or attack.
  Action: Call Oracle Support.

### B.2.3 SQL*Plus Error Messages

The following are SQL*Plus error messages.

3700, Failed in SQL*Plus executing SQL statement: {0}.
  Cause: Failed to execute the specified SQL statement.
  Action: See secondary error.

3701, Failed starting SQL*Plus : {0}.
  Cause: Failed to execute the specified SQL statement.
  Action: See secondary error.

### B.2.4 JDBC Error Messages

The following are JDBC error messages.

3751, Failed to register Oracle JDBC driver: oracle.jdbc.OracleDriver.
  Cause: Failed to register the Oracle JDBC driver.
  Action: Make sure that Oracle JDBC driver is installed on the local system.

3752, There is no JDBC connection to the database.
  Cause: There is no connection to the database server.
  Action: Connect to a database server first, then try the operation again.

3753, Failed to connect to the database.
  Cause: Unable to connect to the database server.
  Action: See secondary error.

3754, Failed to disconnect from the database.
  Cause: Unable to disconnect from the database server.
  Action: See secondary error.

3755, Failed to execute the SQL statement.
  Cause: Failed to execute the SQL statement.
  Action: See secondary error.

3756, Failed to run the SQL query.
  Cause: Failed to run the SQL query statement.
  Action: See secondary error.

3757, Failed to close the Oracle result set or the Statement object.
  Cause: Failed to close the Oracle result set or the Statement object.
  Action: See secondary error.

3758, This method can not be used to verify the physical standby database.
  Cause: This is a programming error.
  Action: Contact Oracle support.

3759, Verify DB query returned no data.
  Cause: Verify database query returned no data.
  Action: See secondary error.

3760, Failed to query the archive log destination information.
  Cause: Failed to query the archive log destination information.
  Action: See secondary error.

3761, Failed to query the redo log information.
  Cause: Failed to query the redo log information.
  Action: See secondary error.

3762, Failed to process the results from SQL statement.
  Cause: Failed to process the results from the SQL statement.
  Action: See secondary error.

3763, Failed to query the data files of the database.
  Cause: Failed to query the data files from the database.
  Action: See secondary error.

3764, Failed to query the log files used by the database.
  Cause: Failed to query the log files used by the database.
  Action: See secondary error.

3765, Failed to query table space information.
  Cause: Failed to query tablespace information from the database.
  Action: See secondary error.

### B.2.5 OPMN Error Messages

The following are OPMN error messages.

3800, Failed trying to connect to OPMN Manager.
  Cause: Error trying to connect to OPMN manager.
  Action: Make sure OPMN manager is started.

3801, Failed trying to get topology information from OPMN Manager on {0}.
  Cause: Error trying to get topology information from OPMN manager.
  Action: Make sure OPMN manager is started and working correctly.

3802, Failed trying to stop OPMN Component {0}.
  Cause: Failed trying to stop the specified OPMN component.
  Action: See secondary error.

3803, Failed trying to start OPMN Component {0}.
  Cause: Failed trying to start the specified OPMN component.
  Action: See secondary error.

3804, Failed trying to remove topology entry from {0}.
  Cause: Failed trying to remove topology entry from opmn.xml.
  Action: See secondary error.

3900, Error creating Oracle database service because the service has already been marked for deletion. Please exit the Windows Service Control Manager on node {0}. Would you like to retry?
  Cause: The user has the SCM open causing a service operation to fail.
  Action: User must exit SCM GUI.

### B.2.6 Net Services Error Messages

The following are Net Services error messages.

4000, Failed trying to get Net Services default domain for {0}.
  Cause: Failed trying to get the Net Services default domain.
  Action: See secondary error.

4001, Error trying to add net service name entry for {0}.
  Cause: Failed trying to add the specified service name.
  Action: See secondary error.

4002, Error trying to get net service name entry for {0}.
  Cause: Failed trying to get the specified service name.
  Action: See secondary error.

4003, Error trying to get host name from net service entry for {0}.
  Cause: Failed trying to get the host name from the net service entry.
  Action: See secondary error.

4004, Error trying to get host name from net service description.
  Cause: Failed trying to get the host name from the net service description.
  Action: See secondary error.

4005, Error trying to get net service listener information.
  Cause: Failed trying to get the net service listener information.
  Action: See secondary error.

4006, Error trying to create a net service default listener.
  Cause: Failed trying to create a default listener.
  Action: See secondary error.

4007, Error trying to add SID entry {0} to net service listener {1}.
  Cause: Failed trying to add a SID entry to the listener.
  Action: See secondary error.

4008, Error generating a command a script for the net service listener command: {0}.
  Cause: Failed generating a command script for the listener.
  Action: See secondary error.

4009, Error running the command script for the net service listener command: {0}.
  Cause: Failed running the command script for the listener.
  Action: See secondary error.

4010, Error adding the net service TNS entry for {0}.
  Cause: Failed adding a TNS entry.
  Action: See secondary error.

4011, Error trying to delete SID entry {0} to the net service listener {1}.
  Cause: Failed trying to delete the SID entry to the listener.
  Action: See secondary error.

4012, Error trying to save the listener configuration.
  Cause: Listener information was modified and an attempt to save information failed.
  Action: See secondary error.

4013, Error deleting net service TNS entry for {0}.
  Cause: Failed deleting a TNS entry.
  Action: See secondary error.

4014, Error starting the TNS listener using the lsnrctl command.
  Cause: Failed to start the TNS listener.
  Action: See secondary error.

4030, The command \"{0}\" failed due to timeout.
  Cause: Command timed out.
  Action: Increase timeout values in configuration file.

4031, Error getting environment variables using the env command.
  Cause: The env command does not work.
  Action: Make sure the `/bin` or `/usr/bin` directory contains the env executable.

4040, Error executing the external program or script.
  Cause: The execution of the specified command failed.
  Action: See secondary error.

4041, Failed to get the value of {0} from the TNS name descriptor {1}.
  Cause: Failed to get the value for the given parameter from the TNS name descriptor.
  Action: See secondary error.

4042, Failed to update the value of {0} for the TNS name descriptor {1}.
  Cause: Failed to update the value of a given parameter in the TNS name descriptor.
  Action: See secondary error.

4043, Failed to compare the TNS descriptor entry {0} with entry {1}.
  Cause: Failed to compare the two TNS entries.
  Action: See secondary error.

4044, Failed to generate a remote TNS name descriptor for the service name.
  Cause: Failed to generate a remote TNS name descriptor for the given local database.
  Action: See secondary error.

4045, Failed to get the remote TNS service name for the service name.
  Cause: Failed to get the remote TNS service name for the given local database.
  Action: See secondary error.

### B.2.7 LDAP or OID Error Messages

The following are LDAP or OID error messages.

4101, Failed to connect to OID server on host {0}, port {1}.
  Cause: Failed to the OID server on a given host and port.
  Action: See secondary error.

4102, Failed to connect to OID server via SSL on host {0}, port {1}.
  Cause: Failed to the OID server via SSL on a given host and port.
  Action: See secondary error.

4103, User must specify host, port, user name, and password for the OID server.
  Cause: User did not specify all the above parameters.
  Action: User must specify all the above parameters in order to access the OID server.

4104, Failed to get the value of attribute {0} from OID server.
  Cause: Failed to get the value of the given attribute.
  Action: See secondary error.

4105, Failed to get the attributes for DN {0} from OID server
  Cause: Failed to get the attributes of the given DN.
  Action: See secondary error.

4106, Failed to get Oracle Application Server instances from OID server
  Cause: Failed to get Oracle Application Server instances from the OID server.
  Action: See secondary error.

4107, Failed to get infrastructure databases from OID server.
  Cause: Failed to get infrastructure databases from the OID server.
  Action: See secondary error.

4110, Cannot set current topology to file {0} because the file does not exist.
  Cause: The topology file does not exist.
  Action: Specify a filename of a file that exists.

4111, The current topology file \"{0}\" does not exist. Use the "set topology" command to specify a valid topology file.
  Cause: The topology file does not exist.
  Action: Specify a filename of a file that exists in dsa.conf.

### B.2.8 System Error Messages

The following are system error messages.

4900, An exception occurred on the server.
  Cause: A server exception occurred.
  Action: See secondary error.

4901, A null pointer exception occurred on the server.
  Cause: Software error.
  Action: See secondary error.

4902, Object not found in clipboard for key {0}.
  Cause: Software error.
  Action: See secondary error.

4903, The minimum succeed value of {0} was not met for the workers in group {1}.
  Cause: A group of workers belonging to the same group requires that a minimum number of them succeed. That minimum succeed value was not met.
  Action: See secondary error.

4950, An error occurred on host {0} with IP {1} and port {2}.
  Cause: An error occurred on the server.
  Action: See secondary error.

### B.2.9 Warning Error Messages

The following are warning error messages.

15305, Warning: Problem gathering summary information for backup.
  Cause: Error during the gatherInfo step of the backup topology operation.
  Action: Check secondary error.

15306, Warning during undo processing.
  Cause: Error occurred during undo processing.
  Action: Check secondary error.

### B.2.10 OracleAS Database Error Messages

The following are OracleAS database error messages.

15604, Error finishing up creating the physical standby database.
  Cause: Failed to finish creating the standby database.
  Action: See secondary error.

15605, Error creating the physical standby database.
  Cause: Failed to the create the standby database.
  Action: See secondary error.

15606, Failed to perform a sync database operation on the primary topology.
  Cause: Failed to perform a sync database operation on the primary topology.
  Action: See secondary error.

15607, Failed to perform a sync database operation on the standby topology.
  Cause: Failed to perform a sync database operation on the standby topology.
  Action: See secondary error and log file for more information.

15608, Invalid backup mode specified in the template file {0}.
  Cause: Error trying to process a backup mode value in the template file.
  Action: Correct backup mode and retry the operation.

15609, Failed to get database backup files.
  Cause: Error trying to get the database backup files.
  Action: See secondary error.

### B.2.11 OracleAS Topology Error Messages

The following are OracleAS topology error messages.

15620, An Invalid Topology was specified.
  Cause: Error trying to process a topology object.
  Action: Retrieve a valid topology object.

15621, Error trying to verify topology {0}.
  Cause: The specified topology had an error during the verify operation.
  Action: See secondary error for more information.

15622, Error trying to verify instance {0}.
  Cause: The specified instance had an error during the verify operation.
  Action: See secondary error for more information.

15623, Topology {0} is not symmetrical with topology {1}.
  Cause: The specified topologies are not symmetrical.
  Action: See secondary error for more information.

15624, An Invalid Topology was specified. Topology {0} does not contain any valid instances.
  Cause: Error trying to process a topology object. Topology object did not contain a valid instance.
  Action: Retrieve a valid topology object with at least one instance.

15625, Could not find matching instance {0} in Topology {1}.
  Cause: Could not get matching instances. Topologies do not appear to be symmetrical.
  Action: Make the topologies symmetrical.

15626, Topologies are not symmetrical because topology name {0} is not the same as topology name {1}.
  Cause: Topology names are not the same and therefore topologies are not symmetrical.
  Action: Make the topologies symmetrical.

15627, Instance {0} is not symmetrical because of different Oracle Home names {1}.
  Cause: Instance Home names are not symmetrical in the specified topologies.
  Action: Make the topologies symmetrical.

15628, Instance {0} is not symmetrical because of different Oracle Home paths {1}.
  Cause: Instance Home paths are not symmetrical in the specified topologies.
  Action: Make the topologies symmetrical.

15629, Instance {0} is not symmetrical, because of different host names {1}, {2}.
  Cause: Instance host names are not symmetrical in the specified topologies.
  Action: Make the topologies symmetrical.

15630, The specified instance {0} could not be found.
  Cause: The specified instance information could not be found on this node.
  Action: Either the wrong instance name or host name was specified on the request to the server.

15631, The primary and standby topologies appear to be identical because both have instance {0} on host {1}.
  Cause: An instance can only be in a member of one topology, it appears that the primary and standby topologies are the same.
  Action: Specify a primary and separate standby topology.

15632, The Home that contains instance {0} could not be found.
  Cause: The specified instance could not be found in any Home on this node.
  Action: The Oracle home information on the system is incorrect.

15633, An Invalid Topology was specified. Topology contains a duplicate instance named {0}.
  Cause: Topology information obtained from OPMN contains a duplicate instance.
  Action: Check OPMN to ensure that the topology information listed is correct.

### B.2.12 OracleAS Backup and Restore Error Messages

The following are OracleAS backup and restore error messages.

15681, Must specify a backup directory.
  Cause: A backup directory must be specified for the operation to complete successfully.
  Action: Check secondary error.

15682, Failed to initialize configure file: {0}.
  Cause: Failed to initialize the configure file for backup script.
  Action: Check secondary error.

15683, The ha directory does not exist in Oracle Home {0}.
  Cause: The ha directory does not exist in the OracleAS Oracle home.
  Action: Make sure the ha directory which contains the backup and restore scripts is copied to the OracleAS Oracle home.

15684, Failed to generate the configuration file for the backup and restore script.
  Cause: Failed to generate the configure file for the backup and restore script.
  Action: Check secondary error.

15685, Failed to backup configuration data for instance {0}.
  Cause: Failed to backup configuration data for the specified instance.
  Action: Check secondary error.

15686, Failed to restore configuration data for instance {0}.
  Cause: Failed to restore configuration data for the specified instance.
  Action: Check secondary error.

15687, Failed to get the database backup files.
  Cause: Failed to get the database backup file names from the log.
  Action: Check secondary error.

15688, Error running the config script.
  Cause: Failed to run the config script.
  Action: Check the log file generated by the config script.

15689, Error running the backup script.
  Cause: Failed to run the backup script.
  Action: Check the log file generated by the backup script.

15690, Error running the restore script.
  Cause: Failed to run the restore script.
  Action: Check the log file generated by the restore script.

15691, No zip file was found.
  Cause: No zip file was found.
  Action: Make sure a successful backup has been performed.

15692, The config file {0} is empty.
  Cause: The specified configure file is empty.
  Action: Copy the original configure file from the "ha" directory where backup restore scripts are located.

15693, No zip file was specified.
  Cause: User did not specify a zip file for the unzip operation.
  Action: Internal error.

15694, Error executing step - {0} of Backup topology.
  Cause: Backup topology failed at the specified step.
  Action: Check secondary error.

15695, Error executing step - {0} of Restore topology.
  Cause: Restore topology failed at the specified step.
  Action: Check secondary error.

15696, Error initializing backup topology operation.
  Cause: Error initializing backup topology operation.
  Action: Check secondary error.

15697, Error during backup topology operation - backup step.
  Cause: Error during backup step processing of backup topology.
  Action: Check secondary error.

15698, Error during backup topology operation - copy step.
  Cause: Error during copy step processing of backup topology.
  Action: Check secondary error.

15699, Error initializing restore topology operation.
  Cause: Error initializing restore topology operation.
  Action: Check secondary error.

15700, No backup file was found.
  Cause: No backup file was found.
  Action: Make sure a successful backup has been performed.

15701, Failed to restore configuration with the DCM-resyncforce option for instance {0}.
  Cause: Failed to restore configuration with the DCM-resyncforce option.
  Action: Check secondary error.

15702, Error initializing the clone instance operation.
  Cause: Error initializing the clone instance operation.
  Action: Check the secondary error.

15703, Error initializing the clone topology operation.
  Cause: Error initializing the clone home operation.
  Action: Check the secondary error.

15704, Error: Oracle home of the instance to be cloned {0} already exists.
  Cause: Error cloning instance, the Oracle home already exists
  Action: Clean up the Oracle home and retry.

15705, cloning instance {0}. Cloning requires OPMN to be stopped, therefore the OracleAS Guard server must be started using asgctl .
  Cause: Cloning requires that OPMN be stopped, which will cause the OracleAS Guard server (ASG server process) to be stopped. This will cause the clone to fail.
  Action: Use opmnctl to stop the OracleAS Guard server (ASG server process). Then use the asgctl startup topology command to restart OracleAS Guard server for this instance.

15706, Stop the backup home image operation in response to the user's request.
  Cause: Stop the backup home operation because the user entered NO.
  Action: None.

15707, Stop the restore home image operation in response to the user's request.
  Cause: Stop the restore home operation because the user entered NO.
  Action: None.

### B.2.13 OracleAS Guard Synchronize Error Messages

The following are OracleAS Guard synchronize error messages.

15721, Failed to initialize a DUF database object.
  Cause: Failed to initialize a DufDb object.
  Action: Check secondary error.

15722, No topology information is available to perform the topology operation.
  Cause: No topology information is available to perform the topology operation.
  Action: Check secondary error.

15723, No instances are found in the topology's backup list.
  Cause: The topology's backup list is empty.
  Action: Check secondary error.

15724, Failed to get the standby host list.
  Cause: Failed to get the standby host list.
  Action: Check secondary error.

15725, Failed to backup OracleAS configuration data for topology {0}.
  Cause: Failed to backup OracleAS topology configuration data.
  Action: Check secondary error.

15726, Failed to restore OracleAS configuration data for topology.
  Cause: Failed to restore OracleAS topology configuration data.
  Action: Check secondary error.

15727, Failed to backup OracleAS infrastructure database {0}.
  Cause: Failed to backup OracleAS topology infrastructure database.
  Action: Check secondary error.

15728, Failed to restore OracleAS infrastructure database {0}.
  Cause: Failed to restore OracleAS topology infrastructure database.
  Action: Check secondary error.

15729, Failed to perform the sync topology operation.
  Cause: Failed to perform the sync topology operation.
  Action: Check secondary error.

### B.2.14 OracleAS Guard Instantiate Error Messages

The following are OracleAS Guard instantiate error messages.

15751, Error executing step {0} of instantiate topology operation.
  Cause: The instantiate topology operation failed at the specified step.
  Action: Check secondary error.

15752, Failed to load remote topology information.
  Cause: Failed to load remote topology information.
  Action: Make sure the user specified the correct host name for the topology and that the OPMN processes are running on the topologies.

15753, Error preparing to instantiate topology on host {0}.
  Cause: Error preparing to instantiate topology.
  Action: Check secondary error.

15754, Error instantiating database {0}.
  Cause: Error instantiating the database.
  Action: Check secondary error.

15755, Error finishing up instantiating database {0}.
  Cause: Error finishing up instantiating the database.
  Action: Check secondary error.

15756, Error initializing instantiate topology operation.
  Cause: Error initializing the instantiate topology operation.
  Action: Check secondary error.

15757, Error initializing switchover topology operation.
  Cause: Error initializing the switchover topology operation.
  Action: Check secondary error.

15770, The instance {0} specified in the topology file does not match the instance {1} in home {2}.
  Cause: The topology file is incorrect.
  Action: Run the "discover topology command" from asgctl.

15771, The topology file {0} is the wrong version Please delete the file and rediscover the topology.
  Cause: The topology file is incorrect.
  Action: Run the "discover topology command" from asgctl.

15772, The topology file {0} does not contain an entry for the discovery host {1}.
  Cause: The topology file is incorrect.
  Action: Run the "discover topology command" from asgctl.

15773, The standby topology does not contain a entry for the mandatory primary instance {0}.
  Cause: The topology file is incorrect.
  Action: Run the "discover topology command" from asgctl.

15774, The host name {0} in the standby topology net descriptor for database {1} resolves to a primary host address {2}.
  Cause: The topology file is incorrect.
  Action: Run the "discover topology command" from asgctl.

15775, The standby topology host name {0} for the instance {1} resolves to a primary host address.
  Cause: The topology file is incorrect.
  Action: Run the "discover topology command" from asgctl.

15776, Error accessing the OID server.
  Cause: Unable to access the OID server.
  Action: Specify the correct OID information and make sure the OID server is running.

15777, Error: OID information needed to access the server was not specified.
  Cause: Unable to access the OID server.
  Action: Specify the correct OID information.

15778, Error getting database information for SID {0} from host {1}. This instance will be excluded from the topology.xml file.
  Cause: Unable to get database information for the topology database.
  Action: None.

15779, Error getting instance information for instance {0} from host {1}. This instance will be excluded from the topology.xml file.
  Cause: Unable to get information for an instance.
  Action: None.

15780, Instance {0} cannot be found in the topology.
  Cause: The instance name does not exist in the topology file.
  Action: Perform the asgctl discover topology command.

15781, Warning: Unable to update topology file on host {0} in home {1}.
  Cause: The topology file cannot be written to the home.
  Action: Make sure the OracleAS Guard server is running in that home.

15782, Error: Instance {0} already exists in the topolgy.
  Cause: The instance already exists in the topology.
  Action: Remove the instance using asgctl.

15783, Error: OID host and port information needed to access the server was not specified.
  Cause: Unable to access the OID server.
  Action: Specify the correct OID information.