Oracle Database Errors or Warnings from Error ORA-31639 to ORA-31650

SQLServerF1

ORA-31639: unexpected data found
Cause: The Master Table or Data Pump file contents appear invalid. The table or file may not have been produced by a Data Pump job, or they may have been corrupted.
Action: Select a different job name (Master Table) or replace the table or file with one produced by Data Pump.
ORA-31640: unable to open dump file “string” for read
Cause: Import was unable to open the export file for reading. This message is usually followed by device messages from the operating system.
Action: Take appropriate action to restore the device.
ORA-31641: unable to create dump file “string”
Cause: Export was unable to create the specified file with write enabled.
Action: Check the file name and file system for the source of the error.

ORA-31642: the following SQL statement fails: string
Cause: An internal error was generated from package DBMS_METADATA.
Action: Contact Oracle Customer Support and report the error.
ORA-31643: unable to close dump file “string”
Cause: Export or Import was unable to close the dump file. This message is usually followed by device messages from the operating system.
Action: Take appropriate action to restore the device.
ORA-31644: unable to position to block number string in dump file “string”
Cause: Export or Import was unable to position its file pointer to a specific block within the dump file. This message is usually followed by device messages from the operating system.
Action: Take appropriate action based on the device messages.

ORA-31645: unable to read from dump file “string”
Cause: Import could not read from the dumpfile, probably because of a device error. This message is usually followed by a device message from the operating system.
Action: Take appropriate action to restore the device.
ORA-31648: Timeout before master process string finished initialization.
Cause: The master process whose name is listed started up but did not finish its initialization within the allowed time limit.
Action: Refer to any following error messages for possible actions. Check the trace log for the failed process to see if there is any information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.
ORA-31649: Master process string violated startup protocol.
Cause: The master process whose name is listed started up but then exited before notifying the creating process that it was finished with initialization.
Action: Refer to any following error messages for possible actions. Check the trace log for the failed process to see if there is any information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.
ORA-31650: timeout waiting for master process response
Cause: After creating the job infrastructure and sending the initial message to the master process, it failed to respond in the allotted time and most likely aborted during startup.
Action: Retry the open or attach request. Contact Oracle Customer Support if the problem persists.

Above are list of Oracle Database Errors or Warnings from Error ORA-31639 to ORA-31650 received while performing certain operation against Oracle Database or related products.

What are atOracle Database Error Messages?

Oracle Error Messages may be returned while using products which are part of Oracle Database. Each Oracle Dabase Error or Warning Message mentioned above contains the Warning or Error Message Statement, a short explanation of the probable causes of the Error message, and a recommended action.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Oracle Database Error Messages or Warning Messages on Windows and Linux Operating Systems.

 

Oracle Database Errors or Warnings from Error ORA-31629 to ORA-31638

SQLServerF1

ORA-31629: unable to allocate additional memory
Cause: A dynamic memory allocation failure occurred.
Action: Report this problem to a database administrator.
ORA-31630: a job name is required to attach a job for user string
Cause: No job name was supplied for an attach and the user has either no jobs executing or mutiple jobs executing.
Action: Provide a job name for attach to use in selecting an executing job, or to use for restarting a stopped job.
ORA-31631: privileges are required
Cause: The necessary privileges are not available for operations such as: restarting a job on behalf of another owner, using a device as a member of the dump file set, or ommiting a directory object associated with any of the various output files. Refer to any following error messages for additional information.
Action: Select a different job to restart, try a different operation, or contact a database administrator to acquire the needed privileges.

ORA-31632: master table “string.string” not found, invalid, or inaccessible
Cause: A Master Table is required but no such table exists, or the content is not consistent with that of a valid Master Table, or the table is not accessible. Refer to any following error messages for clarification.
Action: Make sure a valid Master Table exists, and eliminate any problems indicated by the following error messages.
ORA-31633: unable to create master table “string.string”
Cause: Job creation failed because a Master Table and its indexes could not be created, most commonly due to the pre-existance of a table with the same name (job name) in the user schema. Refer to any following error messages for clarification.
Action: Select a different job name, DROP the existing table, or eliminate any problems indicated by the following error messages.
ORA-31634: job already exists
Cause: Job creation or restart failed because a job having the selected name is currently executing. This also generally indicates that a Master Table with that job name exists in the user schema. Refer to any following error messages for clarification.
Action: Select a different job name, or stop the currently executing job and re-try the operation (may require a DROP on the Master Table).

ORA-31635: unable to establish job resource synchronization
Cause: A lock used in synchronizing Data Pump resources during job creation and deletion could not be obtained during job creation. This indicates that a process for some other Data Pump job has not released the lock due to an internal error.
Action: Eliminate the processes for any failed Data Pump job and try to create the new job again. If the error continues to occur, contact Oracle Customer Support and report the error.
ORA-31636: session is already attached to job string for user string
Cause: The session executing the attach is already attached to the specified job.
Action: Select a different job or create a new session.
ORA-31637: cannot create job string for user string
Cause: Unable to create or restart a job. Refer to any following or prior error messages for clarification.
Action: Eliminate the problems indicated.
ORA-31638: cannot attach to job string for user string
Cause: Unable to attach a job to a session. Refer to any following or prior error messages for clarification.
Action: Eliminate the problems indicated.

Above are list of Oracle Database Errors or Warnings from Error ORA-31629 to ORA-31638 received while performing certain operation against Oracle Database or related products.

What are atOracle Database Error Messages?

Oracle Error Messages may be returned while using products which are part of Oracle Database. Each Oracle Dabase Error or Warning Message mentioned above contains the Warning or Error Message Statement, a short explanation of the probable causes of the Error message, and a recommended action.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Oracle Database Error Messages or Warning Messages on Windows and Linux Operating Systems.

 

Oracle Database Errors or Warnings from Error ORA-31617 to ORA-31628

SQLServerF1

ORA-31617: unable to open dump file “string” for write
Cause: Export was unable to open the export file for writing. This message is usually followed by device messages from the operating system.
Action: Take appropriate action to restore the device.
ORA-31618: dump file size too small
Cause: The value specified for the FILESIZE parameter or the VOLUMESIZE parameter was too small to hold the header information for the export file, plus any data.
Action: Increase the value of the FILESIZE or VOLUMESIZE parameter.
ORA-31619: invalid dump file “string”
Cause: Either the file was not generated by Export or it was corrupted.
Action: If the file was indeed generated by Export, report this as an Import bug and submit the export file to Oracle Customer Support.

ORA-31620: file or device “string” cannot be specified for string operation
Cause: There was an inappropriate use of file or device in the current operation.
Action: Correct operation or job setup.
ORA-31621: error creating master process
Cause: Setup to create a master process failed.
Action: Refer to any following error messages for possible actions. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.
ORA-31623: a job is not attached to this session via the specified handle
Cause: An attempt to reference a job using a handle which is invalid or no longer valid for the current session.
Action: Select a handle corresponding to a valid active job or start a new job.
ORA-31624: A job cannot be modified after it has started.
Cause: The user attempted to change the definition of a Data Pump job through filters, transforms or parameters after it had started. These changes can only be made while defining a job.
Action: Stop the current job and rerun it with the correct definition.

ORA-31625: Schema string is needed to import this object, but is unaccessible
Cause: An error occurred when attempting to import objects. The schema specified is needed to import this object, but access to this schema is not available.
Action: Refer to any following error messages for possible actions. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.
ORA-31626: job does not exist
Cause: An invalid reference to a job which is no longer executing, is not executing on the instance where the operation was attempted, or that does not have a valid Master Table. Refer to any following error messages for clarification.
Action: Start a new job, or attach to an existing job that has a valid Master Table.
ORA-31627: API call succeeded but more information is available
Cause: The user specified job parameters that yielded informational messages.
Action: Call DBMS_DATAPUMP.GET_STATUS to retrieve additional information.
ORA-31628: error getting worker process exception
Cause: Attempt to get a worker process exception failed.
Action: Refer to any following error messages for possible actions. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

Above are list of Oracle Database Errors or Warnings from Error ORA-31617 to ORA-31628 received while performing certain operation against Oracle Database or related products.

What are atOracle Database Error Messages?

Oracle Error Messages may be returned while using products which are part of Oracle Database. Each Oracle Dabase Error or Warning Message mentioned above contains the Warning or Error Message Statement, a short explanation of the probable causes of the Error message, and a recommended action.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Oracle Database Error Messages or Warning Messages on Windows and Linux Operating Systems.

 

Oracle Database Errors or Warnings from Error ORA-31606 to ORA-31616

SQLServerF1

ORA-31606: XML context number does not match any previously allocated context
Cause: A method in package UTL_XML was called with an invalid XML context handle. All handles must have previously been allocated by UTL_XML.XMLINIT.
Action: Always call XMLINIT before any other methods in pkg. UTL_XML.
ORA-31607: function string is inconsistent with transform.
Cause: Either (1) FETCH_XML was called when the “DDL” transform was specified, or (2) FETCH_DDL was called when the “DDL” transform was omitted.
Action: Correct the program.
ORA-31608: specified object of type string not found
Cause: The specified object was not found in the database.
Action: Correct the object specification and try the call again.

ORA-31609: error loading file “string” from file system directory “string”
Cause: The installation script initmeta.sql failed to load the named file from the file system directory into the database.
Action: Examine the directory and see if the file is present and can be read.
ORA-31610: cannot call this function from a non-master process
Cause: Called a Data Pump process model function from a process which is not a master process.
Action: Create a master process first. Then call the function from the master process. If this error occurs from a Data Pump client (e.g. expdp or impdp), try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.
ORA-31612: Allocation of process descriptor failed.
Cause: During creation of a master process or a worker process, a failure occurred allocating a process descriptor for the process.
Action: Try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-31613: Master process string failed during startup.
Cause: The master process whose name is listed failed during startup.
Action: Refer to any following error messages for possible actions. Check the trace log for the failed process to see if there is any information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.
ORA-31614: routine string received this error from string: string
Cause: The call to the specified routine failed and the specific error text is included in this error message (the last %s string).
Action: Correct inputs to the specified routine.
ORA-31615: routine string received this error: string
Cause: The specified routine failed and the specific error text is included in this error message (the last %s string).
Action: Correct inputs to the specified routine.
ORA-31616: unable to write to dump file “string”
Cause: Export was unable to write to the export file, probably because of a device error. This message is usually followed by a device message from the operating system.
Action: Take appropriate action to restore the device.

Above are list of Oracle Database Errors or Warnings from Error ORA-31606 to ORA-31616 received while performing certain operation against Oracle Database or related products.

What are atOracle Database Error Messages?

Oracle Error Messages may be returned while using products which are part of Oracle Database. Each Oracle Dabase Error or Warning Message mentioned above contains the Warning or Error Message Statement, a short explanation of the probable causes of the Error message, and a recommended action.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Oracle Database Error Messages or Warning Messages on Windows and Linux Operating Systems.

 

Informix Error Messages and Error Codes From Error 33071 to 33083

SQLServerF1

Informix Error Code -33071 The statement id statement_ID has already been used.
This warning message indicates that you have used two PREPARE statement identifiers with the same name. For example:
exec sql prepare stmt_id from “select * from tab”;
exec sql prepare stmt_id from “insert into tab values(1)”;

Informix Error Code -33074 Explicit cast, either with CAST keyword or (::) operator, is not allowed in client collections.
You cannot use explicit casts in client collections. For example, the following example is not allowed:
$client collection list(row( a udt_1, b list(int))) mylist; $insert into table (:mylist) values (CAST(1 AS udt_1), list{1,2,3}); $insert into table (:mylist) values (1::udt_1, list{1,2,3});
When you enter esql -e client.ec, you get the following errors:
esqlc: “client.ec”, line 2: Error -33074: Cannot use CAST in client collections.
esqlc: “client.ec”, line 3: Error -33074: Cannot use CAST in client collections.

Informix Error Code -33075 Cannot use user-defined routines in client collection/row constructors.
The user has tried to call a user-defined routine function in a ROW or COLLECTION constructor for a client collection or row host variable. Check the syntax of the statement and change the statement so that it does not call a user-defined routine. User-defined routines can be executed only on the server.
Informix Error Code -33083 Cannot open file file_name because of too many open files.
The preprocessor cannot open the file because too many files are open. Check your system resources to see if you can increase the number of file handles (descriptors). Close unnecessary open files. Also check for mistakes that might cause recursive file inclusion.

Above are list of Informix Error Messages and Errors Codes or Status Codes or Exit Codes along with Error and Warning messages received while performing certain operation against Informix applications or related products.

What are Informix Error Messages?
All Informix messages returned by the Informix server are assigned an error code.

In general, each Informix error contains the following information:
• The Informix Error Code or Informix Error status
• The message text. This text is usually returned with the Error code. Some messages employ word substitution, where the word substituted represents the system-replacement of a term more specific to the occurrence.
• An explanation of how the error may have occurred.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Informix Error Codes or Status Codes or Exit Codes and Error Messages on Windows, Linux Operating Systems.

 

Informix Error Messages and Error Codes From Error 33065 to 33070

SQLServerF1

Informix Error Code -33065 Cursor/statement id name is too long when prefixed by module name.
This message is a warning only. When you use the -local preprocessing option, cursor names and statement names are prefixed with a unique tag generated from the module name. (On UNIX systems, the inode number of the source program is used as the unique tag.) The combined length of the cursor or statement name and the unique tag should not exceed 18 characters, but in the case of name, it does. As a result, if the same name is used in a different source module, the two names might not be distinct as the -local option requests.

Informix Error Code -33066 Cursor/statement ids id1 and id2 are not unique in first 18 characters when prefixed by module name.
When you use the -local preprocessing option, cursor names and statement IDs are prefixed with a unique tag that is generated from the module name. (On UNIX systems, the inode number of the source program is used as the unique tag.) In this case, id1 and id2 are at least 14 characters long, and their first 13 characters do not differ. As a result, they are the same when the tag is added and the result is trimmed to 18 characters. Change the two names to avoid name collision and try again.

Informix Error Code -33067 ELIF without IFDEF.
An IFDEF or IFNDEF statement does not precede this ELIF statement. Review the source lines that precede this point. The preceding statement was omitted, or it might not have been recognized due to an earlier error.
Informix Error Code -33068 ELIF after ELSE.
The ESQL preprocessor ELSE statement indicates the last part of an IFDEF or IFNDEF statement; another ELIF part might not follow. Review the contents of this IFDEF or IFNDEF statement and put its parts in order.
Informix Error Code -33070 Stack overflow occurred during statement parse.
This message, which indicates that the parser stack has overflowed, rarely occurs. It might occur, for example, if your embedded-language statement (SELECT, INSERT, UPDATE, DELETE, and so on) contains an extremely large or complicated clause (WHERE, MATCHES, LIKE, and so on) that the parser is trying to process. In that case, break up the clause and try again.

Above are list of Informix Error Messages and Errors Codes or Status Codes or Exit Codes along with Error and Warning messages received while performing certain operation against Informix applications or related products.

What are Informix Error Messages?
All Informix messages returned by the Informix server are assigned an error code.

In general, each Informix error contains the following information:
• The Informix Error Code or Informix Error status
• The message text. This text is usually returned with the Error code. Some messages employ word substitution, where the word substituted represents the system-replacement of a term more specific to the occurrence.
• An explanation of how the error may have occurred.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Informix Error Codes or Status Codes or Exit Codes and Error Messages on Windows, Linux Operating Systems.

 

Informix Error Messages and Error Codes From Error 33057 to 33064

SQLServerF1

Informix Error Code -33057 Cannot open error log file errorfile.
You specified the log preprocessor option to have error and warning messages sent to errorfile rather than to standard output. However, the preprocessor cannot open errorfile because not enough disk space is available, or you do not have file-system permission to open the file. If insufficient disk space is available, delete files to make space available in the file system, or select another disk. If you do not have file-system permission to open errorfile, specify another directory or login with the required permission.
Informix Error Code -33058 Option-name is not a valid default option for the column definition.
See the Informix Guide to SQL: Syntax for the valid DEFAULT clause options in a column definition.

Informix Error Code -33060 Invalid expression.
The specified expression is incorrect. Refer to the Informix Guide to SQL: Syntax for the correct syntax and usage for this expression.
Informix Error Code -33061 Unable to expand recursive macro macro-name.
The preprocessor cannot fully expand the macro-name macro because a loop exists in the defined macros. Correct the macro and try again.
Informix Error Code -33062 Missing ENDIF.
An IFDEF or IFNDEF statement has no matching ENDIF statement prior to the end of the source file. Work upward from the end of the file, and check that each IFDEF and IFNDEF statement is paired with a matching ENDIF. Possibly the ENDIF was not recognized due to another error.

Informix Error Code -33063 Already within BEGIN DECLARE SECTION.
This message is a warning only. An EXEC SQL BEGIN DECLARE SECTION statement is inside another BEGIN/END DECLARE block. This statement is ignored. However, the warning might indicate a mix-up in the structure of your program. Check that all the declaration sections are properly delimited.
Informix Error Code -33064 variable-name has appeared before with a different case. ESQL/language-name is case-insensitive.
This message is a warning only. The specified variable appears more than once with different combinations of uppercase and lowercase letters. Because this product is not case sensitive, all these names are treated as one. If you intended these names to indicate different variables, change the name (not merely the case) of one of the variable declarations and recompile.

Above are list of Informix Error Messages and Errors Codes or Status Codes or Exit Codes along with Error and Warning messages received while performing certain operation against Informix applications or related products.

What are Informix Error Messages?
All Informix messages returned by the Informix server are assigned an error code.

In general, each Informix error contains the following information:
• The Informix Error Code or Informix Error status
• The message text. This text is usually returned with the Error code. Some messages employ word substitution, where the word substituted represents the system-replacement of a term more specific to the occurrence.
• An explanation of how the error may have occurred.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Informix Error Codes or Status Codes or Exit Codes and Error Messages on Windows, Linux Operating Systems.

 

Informix Error Messages and Error Codes From Error 33051 to 33056

SQLServerF1

Informix Error Code -33051 Syntax error on identifier or symbol symbol-name.
An error in syntax was found at or near symbol-name. Check the Informix Guide to SQL: Syntax for the proper use of identifiers and the appropriate embedded-language manual for the proper use of other symbols.
Informix Error Code -33052 Unmatched ELSE.
A matching IFDEF or IFNDEF statement does not precede this ELSE statement. Review the source lines that precede this point; the preceding statement was omitted or might not have been recognized due to an earlier error.

Informix Error Code -33053 Unmatched ENDIF.
An IFDEF or IFNDEF statement does not precede this ENDIF statement. Review the source lines that precede this point; the preceding statement was omitted or might not have been recognized due to an earlier error.
Informix Error Code -33054 Updates are not allowed on a scroll cursor.
This UPDATE statement refers to a cursor that was declared with the SCROLL keyword. The UPDATE statement requires a cursor that has been declared FOR UPDATE to ensure that the proper level of locking is applied to the rows that will be updated. See the DECLARE statement in the Informix Guide to SQL: Syntax for more information on the correct use of cursors.

Informix Error Code -33055 The name id-name has already been used.
The SQL identifier id-name has already been declared. Check the spelling of names and the declarations in the current name scope.
Informix Error Code -33056 Error errno during output.
The error errno occurred during output. Check that sufficient disk space is available for the output file and that you have the necessary file-system permissions for the file location. Look up errno in the host operating-system manual (or see the list that begins on page 3) for the specific cause of the problem and the appropriate corrective action.

Above are list of Informix Error Messages and Errors Codes or Status Codes or Exit Codes along with Error and Warning messages received while performing certain operation against Informix applications or related products.

What are Informix Error Messages?
All Informix messages returned by the Informix server are assigned an error code.

In general, each Informix error contains the following information:
• The Informix Error Code or Informix Error status
• The message text. This text is usually returned with the Error code. Some messages employ word substitution, where the word substituted represents the system-replacement of a term more specific to the occurrence.
• An explanation of how the error may have occurred.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Informix Error Codes or Status Codes or Exit Codes and Error Messages on Windows, Linux Operating Systems.

 
1 2 3 18