If your fra disk or archivelog directory full, your db can not process any transaction. When you increase disk size, database does not recover itself. You have to do some process.
Error
Solution
Firstly, you have to increase FRA or archivelog disk area size. After you can implement below operations.
25,890 total views, 10 views today
I got an error like CRS-0184 on Oracle 11g RAC system, because of interconnect network is down. After network was up, CRS Daemon did not start. You can take these errors like CRS-0184, CRS-2674, CRS-4534, CRS-4530.. I resolved that problem with below operations.
CRS Stop and Start
[root@node2 ~] cd $GRID_HOME/bin
[root@node2 bin] ./crsctl stop cluster -all
[root@node2 bin] ./crsctl start cluster -all
Check CRS
[root@node2 bin] ./crsctl check crs
[root@node2 bin] ./crsctl check cluster -all
Note : All services have to be up.
Run root.sh
Note : If Cluster Virtual IPS not received, You can run root.sh
[root@node2 ~] cd $GRID_HOME
[root@node2 ~] ./root.sh
[root@node2 ~] cd $ORACLE_HOME
[root@node2 ~] ./root.sh
Various CRS Control Commands
crs_stat -t
crsctl stop has
crsctl start has
crsctl start resource
crsctl stop resource
crsctl status server
227,863 total views, 135 views today
Error
ORA-31634: job already exists
ORA-31664: unable to construct unique job name when defaulted
This error normally occurs when you do not specify a unique JOB_NAME for the DataPump job and for some reason that JOB_NAME already exists in the database, or else if you are running many jobs at the same time (more than 99 jobs) and DataPump cannot create a new job.
Solution
To fix this issue you have to cleanup the orphaned datapump jobs. You can obtain which has to drop tables with below query. After you can execute result set to drop tables.
SQL> SELECT ‘DROP TABLE ‘ || o.OWNER || ‘.’ || o.OBJECT_NAME || ‘ PURGE;’
FROM dba_objects o, dba_datapump_jobs j
WHERE o.owner=j.owner_name
AND o.object_name=j.job_name
AND j.state=’NOT RUNNING’;And execute result set.
1,352 total views, 15 views today
Oracle 11g Error Codes and Solution Suggestions from ORA-19700 to ORA-19900
45 total views, no views today
Oracle 11g Error Codes and Solution Suggestions from ORA-19900 to ORA-20000
60 total views, no views today
Oracle 11g Error Codes and Solution Suggestions from ORA-20000 to ORA-22000
15 total views, no views today
Oracle 11g Error Codes and Solution Suggestions from ORA-22000 to ORA-22300
20 total views, 10 views today
Oracle 11g Error Codes and Solution Suggestions from ORA-22300 to ORA-22700
10 total views, no views today
Oracle 11g Error Codes and Solution Suggestions from ORA-22800 to ORA-23000
10 total views, no views today
Oracle 11g Error Codes and Solution Suggestions from ORA-23300 to ORA-23400
10 total views, no views today
Oracle 11g Error Codes and Solution Suggestions from ORA-23400 to ORA-23500
10 total views, no views today
Oracle 11g Error Codes and Solution Suggestions from ORA-23500 to ORA-24000
10 total views, no views today
Error: Checkpoint not complete, Cannot Allocate New Log Warning
Thread 1 cannot allocate new log, sequence 125487
Checkpoint not complete
Solution: Checkpoint not complete messages are generated due to the logs are switching so fast that the checkpoint associated with the log switch isn’t complete. You should increase redo log file size and amount to resolve. Also, If you use archive_lag_target parameter as near zero for example like 1 or 2 minutes, you should change this parameter zero (no lag) or more than 10-15 min. Oracle recommends that redo log switch operation interval should be between 15-30 minutes.
Show and change archive_lag_target parameter
SQL> show parameter archive_lag_target;
SQL> alter system set archive_lag_target=0 scope=both;
or
SQL> alter system set archive_lag_target=1800 scope=both;
1800 is 15 minutes. Parameter value as second.
If your archive_lag_target parameter is normal and you get checkpoint not complete error, you have to look your redo log file size and amount.
Show Redo Log Files
SQL> select * from v$log;
SQL> select * from v$logfile;
If all redo log files status are ACTIVE and CURRENT, you may get checkpoint not complete warning and that is normal. You should see redo log files status as ACTIVE, CURRENT and INACTIVE.
Redo Log File Status Descriptions
UNUSED – Online redo log has never been written to. This is the state of a redo log that was just added, or just after a RESETLOGS, when it is not the current redo log.
CURRENT – Current redo log. This implies that the redo log is active. The redo log could be open or closed.
ACTIVE – Log is active but is not the current log. It is needed for crash recovery. It may be in use for block recovery. It may or may not be archived.
CLEARING – Log is being re-created as an empty log after an ALTER DATABASE CLEAR LOGFILE statement. After the log is cleared, the status changes to UNUSED.
CLEARING_CURRENT – Current log is being cleared of a closed thread. The log can stay in this status if there is some failure in the switch such as an I/O error writing the new log header.
INACTIVE – Log is no longer needed for instance recovery. It may be in use for media recovery. It might or might not be archived.
If your redo log file size is small or redo log file amount is too few for example two, you have to add new redo log file and increase size.
Add New Redo Log File
SQL> alter database add logfile size 200M;
You can drop small sized redo log files with group number while status is INACTIVE. You can check status with v$log;
Drop Redo Log File
SQL> alter database drop logfile group 3;
You have to check switch time of redo log files after add new redo logs. If switch interval is 15-30 minutes and do not see checkpoint not complete warning, you database redo log size and amount is suitable. You can set archive_lag_target to 15 minutes to force create archive log that is important for recovery operation. If you lose your redo logs, you have to use archived logs. Interval of create archive logs is important for RPO (Recover Point Objective) value.
516 total views, no views today
Oracle 12c R2 Error Codes and Solution Suggestions from ORA-07400 to ORA-07500
Cause: The name for the message file overflows internal buffer.
Action: Try making the complete path-name of the message file shorter by reorganizing the directory hierarchy.
Cause: The system failed to restore user exception handlers.
Action: Check errno and sercose[0] for the signal number that failed.
Cause: The system failed to restore user signal handlers.
Action: Check errno and sercose[0] for the signal number that failed.
Cause: The db_writers parameter in INIT.ORA exceeds the system-dependent maximum or is less than 0.
Action: Change the db_writers parameter in INIT.ORA.
Cause: The master database writer timed out waiting for a write or close to complete. One of the database writers may have stopped running.
Action: Check all database writer trace files. Shut down the database and try to warm start.
Cause: The system failed to setup an alternate signal stack.
Action: Check errno and sercose[0] for the location where it failed.
Cause: An impossible request for binary to decimal conversion was made.
Action: This conversion cannot be performed.
Cause: An impossible request for binary to decimal conversion was made
Action: This conversion cannot be performed.
Cause: An impossible request for binary to decimal conversion was made.
Action: This conversion cannot be performed.
Cause: An impossible request for decimal to binary conversion was made.
Action: This conversion cannot be performed.
Cause: An impossible request for decimal to binary conversion was made.
Action: This conversion cannot be performed.
Cause: The supplied buffer is not big enough to hold the full path name.
Action: The construction of the full path name cannot be performed.
Cause: One of the database writer processes could not locate its entry in the SGA.
Action: Contact customer support.
Cause: Malloc() failed to allocate buffer for storing ORACLE_PATH.
Action: System has run out of heap space. Additional information indicates errno.
Cause: The slpath routine is given a maximum length buffer to expand the name into. An overflow of this buffer occurred.
Action: Possible internal error. Check output buffer length stored in sercose[0] and constructed pathname length in sercose[1].
Cause: One or more of the database writer processes is no longer running.
Action: Check the trace files for the database writers. Shut down the database and try to warm start.
Cause: An error occurred when the database writer called the system timing function.
Action: Check the database writer trace file. Shut down database and try to warm start.
Cause: An error occurred when the database writer called the system timing function.
Action: Check the database writer trace file. Shut down database and try to warm start.
Cause: An oracle error occurred when translating the location of the dump file.
Action: Check the oracle error code.
Cause: An oracle error occurred when translating the location of the dbs directory.
Action: Check additional information for the error returned from sltln.
Cause: Chdir system call returned an error. Possible permission problems.
Action: Check additional information for the OS error code.
Cause: The server process was unable to fork a child process.
Action: Verify that there are enough system resources to support another process. The user or system process limit may have been exceeded, or the amount of free memory or swap space may be temporarily insufficient.
Cause: An attempt was made to make a process sleep when it was already sleeping. This platform does not support this capability.
Action: Try the SLEEP command when the process is not sleeping.
Cause: The wakeup monitor process died.
Action: Warm start instance.
Cause: An improperly aligned function address was specified.
Action: Use a properly aligned function address.
Cause: An invalid function address was specified.
Action: Use a valid function address.
Cause: A nonexistent or an invalid function name was specified.
Action: Use a valid function name.
Cause: An invalid function name/address was specified.
Action: Use a valid function name/address.
Cause: An operating system exception occurred which should result in the creation of a core file. This is an internal error.
Action: Visit My Oracle Support to access the ORA-07445 Lookup tool (reference Note 7445.1) for more information regarding the specific ORA-07445 error encountered. An Incident has been created for this error in the Automatic Diagnostic Repository (ADR). When logging a service request, use the Incident Packaging Service (IPS) from the Support Workbench or the ADR Command Interpreter (ADRCI) to automatically package the relevant trace information (reference My Oracle Support Note 411.1). The following information should also be gathered to help determine the root cause: – changes leading up to the error – events or unusual circumstances leading up to the error – operations attempted prior to the error – conditions of the operating system and databases at the time of the error Note: The cause of this message may manifest itself as different errors at different times. Be aware of the history of errors that occurred before this internal error.
Cause: The directory specified as the value for the stated parameter could not be used.
Action: Make sure the directory you have specified is a valid directory/file specification.
Cause: Oracle failed to create a shared arena file.
Action: Use sercerrno field to determine cause of failure.
Cause: Oracle attempted to create more shared arena files than permitted.
Action: Raise the value for max_arena in INIT.ORA.
Cause: Oracle failed to acquire a shared arena lock.
Action: Check result code in sercerrno to determine the cause of failure.
Cause: kstat library returned an error. Possible OS failure
Action: Check result code in sercose[0] for more information.
Cause: User tried to load a resource manager plan that does not exist.
Action: Use a resource manager plan that exists in the data dictionary.
Cause: User tried to load a resource manager plan schema that does not contain the OTHER_GROUPS group.
Action: Use a resource manager plan schema that contains the OTHER_GROUPS group.
Cause: User session queued for longer than maximum specified queue queue duration time for consumer group.
Action: Re-submit job at a later time or increase queue timeout.
Cause: User attempted to execute an operation whose estimated execution time exceeds the limit specified for the consumer group.
Action: Execute job on behalf of another group, or increase limit.
Cause: An attempt was made to turn on the Resource Manager when the database was closed.
Action: Open the database and try again.
Cause: An attempt was made to set the _INTERNAL_RESOURCE_MANAGER_PLAN parameter, however this failed because the current RESOURCE_MANAGER_PLAN has the FORCE prefix.
Action: Remove the FORCE prefix from the RESOURCE_MANAGER_PLAN parameter.
Cause: An attempt was made to set the RESOURCE_MANAGER_PLAN parameter, however, this failed because the database was quiesced.
Action: Unquiesce the database.
Cause: An attempt was made to internally restore the RESOURCE_MANAGER_PLAN parameter to the value before it was internally set. This failed because the current plan was set by the user and therefore did not need to be restored.
Action: No action needed.
Cause: An attempt was made to internally set the RESOURCE_MANAGER_PLAN parameter, however, this failed because the current RESOURCE_MANAGER_PLAN has the FORCE prefix.
Action: Remove the FORCE prefix from the RESOURCE_MANAGER_PLAN parameter.
Cause: The mset routine returned an error. Semaphore may not exist.
Action: Check result code in sercerrno. Semaphore number returned in sercose[0].
Cause: The mclear routine returned an error. Semaphore may not exist.
Action: Check result code in sercerrno. Semaphore number returned in sercose[0].
Cause: The cluster_status system call failed to get status information for the current cluster.
Action: Check result code in sercose[0]. Possible operating system failure.
Cause: Unable to expand out ?/dbs/sgadef@.dbf file name.
Action: Verify $(ORACLE_HOME) and $(ORACLE_SID) are properly set. Check error number returned from sltln in sercose[0].
Cause: open failed when opening the file ?/dbs/sgadef@.dbf
Action: Check errno. Possible permission problem. Verify that the file ?/dbs/sgadef@.dbf exists.
Cause: Read had an error when reading sgadef.dbf file.
Action: Check errno. Verify file exists, and is correct size.
Cause: An error occurred in close, while closing the file “?/dbs/sgadef@.dbf”
Action: Check errno. Possible operating system error.
Cause: The vm_statistics system call failed to get virtual memory statistics.
Action: Check result code in sercerrno. Possible operating system failure.
Cause: The vm_mapmem system call failed to get mapped memory statistics.
Action: Check result code in sercerrno. Possible operating system failure.
Cause: Lock manager must be initialized before converting locks.
Action: Check result code in sercerrno. Possible lock manager failure.
Cause: lm_stat_lock failed.
Action: Check result code in sercerrno. Possible lock manager failure.
Cause: lm_open or lm_open_convert failed.
Action: Check result code in sercerrno. Possible lock manager failure.
Cause: When creating an instance, snlmini could not change the permissions on ?/dbs/sgalm.dbf
Action: Contact your customer support representative.
Cause: lm_attach failed to attach to lock manager instance.
Action: Check result code in sercerrno. Possible lock manager failure.
Cause: lm_create failed to create lock manager instance.
Action: Check permissions on ?/dbs, and remove ?/dbs/sgalm.dbf if it exists, then retry.
Cause: lm_convert failed to convert(get) lock.
Action: Check result code in sercerrno. Possible lock manager failure.
Cause: lm_convert failed to put lock value.
Action: Check result code in sercerrno. Possible lock manager failure.
Cause: lm_open failed.
Action: Check result code in sercerrno. Possible lock manager failure.
Cause: lm_convert failed to get lock value.
Action: Check result code in sercerrno. Possible lock manager failure.
Cause: lm_create failed.
Action: Check result code in sercerrno. Possible lock manager failure.
Cause: Lock manager must be initialized before releasing locks.
Action: Check result code in sercerrno. Possible lock manager failure.
Cause: lm_stat_lock failed during lock release/cancel.
Action: Check result code in sercerrno. Possible lock manager failure.
Cause: lm_convert failed during lock release/cancel.
Action: Check result code in sercerrno. Possible lock manager failure.
Cause: lm_cancel failed during lock release/cancel.
Action: Check result code in sercerrno. Possible lock manager failure.
Cause: lm_close failed during lock release/cancel.
Action: Check result code in sercerrno. Possible lock manager failure.
Cause: An error was encountered releasing the lock.
Action: Check result code in sercerrno. Possible lock manager failure.
Cause: Unknown or unexpected error code.
Action: Check result code in sercerrno. Possible lock manager failure.
Cause: lm_wait failed.
Action: Check result code in sercerrno. Possible lock manager failure.
Cause: lm_post failed.
Action: Check result code in sercerrno. Possible lock manager failure.
Cause: 1. The trace file could not be created for writing. 2. The trace file is a symbolic link.
Action: 1. Check if the dump directory exists and whether it is writable. 2. Remove the symbolic link.
Cause: The rescheduling driver /dev/resched is not found or is not working properly.
Action: Check installation of the ORACLE rescheduling driver in the AIX kernel.
Cause: The rescheduling driver /dev/resched is not open. This is an internal error and should not occur.
Action: Contact your customer support representative.
55 total views, no views today
Oracle 12c R2 Error Codes and Solution Suggestions from ORA-07500 to ORA-07700
Cause: VMS system service $CANTIM returned an unexpected value
Action: Check for system error message and refer to VMS documentation
Cause: VMS system service $DEQ returned an unexpected value
Action: Check for system error message and refer to VMS documentation
Cause: VMS system service $ENQ returned an unexpected value
Action: Check for system error message and refer to VMS documentation
Cause: VMS system service $SETIMR returned an unexpected value
Action: Check for system error message and refer to VMS documentation
Cause: VMS system service $HIBER returned an unexpected value
Action: Check for system error message and refer to VMS documentation
Cause: VMS system service $ENQ returned an unexpected value
Action: Check for system error message and refer to VMS documentation
Cause: VMS system service $DEQ returned an unexpected value
Action: Check for system error message and refer to VMS documentation
Cause: A global locking system service returned an unexpected value.
Action: Check for system error message (if any) and refer to VMS documentation, or contact your customer support representative.
Cause: VMS system service $DEQ returned an unexpected value
Action: Check for system error message and refer to VMS documentation
Cause: VMS system service $DEQ returned an unexpected value
Action: Check for system error message and refer to VMS documentation
Cause: VMS system service $GETLKI returned an unexpected value
Action: Check for system error message and refer to VMS documentation
Cause: VMS system service $ENQ returned an unexpected value
Action: Check for system error message and refer to VMS documentation
Cause: VMS system service $ENQ returned an unexpected value
Action: Check for system error message and refer to VMS documentation
Cause: VMS system service $DEQ returned an unexpected value
Action: Check for system error message and refer to VMS documentation
Cause: VMS system service $DEQ returned an unexpected value
Action: Check for system error message and refer to VMS documentation
Cause: VMS system service $GETLKI returned an unexpected value
Action: Check for system error message and refer to VMS documentation
Cause: Too many test files open
Action: This is an internal error, please report to Oracle
Cause: VMS system service $OPEN failed
Action: Examine system error message and refer to VMS documentation
Cause: VMS system service $OPEN failed
Action: Examine system error message and refer to VMS documentation
Cause: VMS system service $CLOSE failed
Action: Examine system error message and refer to VMS documentation
Cause: VMS system service $GET failed
Action: Examine system error message and refer to VMS documentation
Cause: VMS system service $IDTOASC failed
Action: Examine system error message and refer to VMS documentation
Cause: An extension was found but it is of improper length
Action: This is an internal error, please report to Oracle
Cause: VMS system service $PARSE failed
Action: Examine system error message and refer to VMS documentation
Cause: A wildcard was used in the file name
Action: Reenter the file name completely
Cause: VMS system service $SEARCH failed
Action: Examine system error message and refer to VMS documentation
Cause: VMS system service $OPEN failed
Action: Examine system error message and refer to VMS documentation
Cause: VMS system service $CLOSE failed
Action: Examine system error message and refer to VMS documentation
Cause: VMS system service $IDTOASC failed
Action: Examine system error message and refer to VMS documentation
Cause: VMS system service $FIND_HELD failed
Action: Examine system error message and refer to VMS documentation
Cause: An OS role name was too long.
Action: Re-define the role name to be of correct length.
Cause: VMS system service LIB$SPAWN failed
Action: Examine system error message and refer to VMS documentation
Cause: VMS system service $GETUAI failed
Action: Examine system error message and refer to VMS documentation
Cause: VMS system service $GETJPIW failed
Action: Examine system error message and refer to VMS documentation
Cause: An attempt was made to set an INTERNAL password (for either DBA or OPER privilege), but the corresponding VMS account (either ORA_sid_DBA or ORA_sid_OPER) hasn’t been created yet.
Action: Add a VMS account for ORA_sid_DBA and/or ORA_sid_OPER before trying to set a password for them.
Cause: VMS system service $FIND_HELD failed
Action: Examine system error message and refer to VMS documentation
Cause: VMS system service $PARSE failed
Action: Examine system error message and refer to VMS documentation
Cause: VMS system service $GETJPIW failed
Action: Examine system error message and refer to VMS documentation
Cause: A background process did not have name of correct form
Action: If the job name was changed, restore it, otherwise this is an internal error, please report to Oracle.
Cause: The ORA_SID must exist and be less than 6 characters
Action: Consult the VMS Installation guide for information on setting the SID.
Cause: A logical name used to set a detached process quota value has an invalid value (probably non-numeric).
Action: Examine the values of these logical names, correct the one in error, and retry.
Cause: VMS system service $PARSE failed
Action: Examine system error message and refer to VMS documentation
Cause: VMS system service $SEARCH failed
Action: Examine system error message and refer to VMS documentation
Cause: VMS system service $CREPRC failed
Action: Examine system error message and refer to VMS documentation
Cause: VMS system service $GETJPIW failed
Action: Examine system error message and refer to VMS documentation
Cause: The logical name ORA_SID doesn’t translate to a valid value.
Action: Check the value of ORA_SID in the process that gets the error, and correct the installation or command procedures that caused ORA_SID to be set incorrectly.
Cause: VMS system service $DELPRC failed
Action: Examine system error message and refer to VMS documentation
Cause: VMS system service $GETJPIW failed
Action: Examine system error message and refer to VMS documentation
Cause: While obtaining needed privileges, an error was returned from SYS$SETPRV.
Action: This is an internal error. Please report to Oracle
Cause: While releasing privileges, an error was returned from SYS$SETPRV.
Action: This is an internal error. Please report to Oracle
Cause: VMS system service $GETJPIW failed
Action: Examine system error message and refer to VMS documentation
Cause: VMS system service $GETJPIW failed
Action: Examine system error message and refer to VMS documentation
Cause: VMS system service $GETJPIW failed
Action: Examine system error message and refer to VMS documentation
Cause: VMS system service $GETJPIW failed
Action: Examine system error message and refer to VMS documentation
Cause: VMS system service $GETJPIW failed
Action: Examine system error message and refer to VMS documentation
Cause: VMS system service $SCHDWK failed
Action: Examine system error message and refer to VMS documentation
Cause: VMS system service $GETSYIW failed
Action: Examine system error message and refer to VMS documentation
Cause: VMS system service $GETJPIW failed
Action: Examine system error message and refer to VMS documentation
Cause: VMS system service $GETJPIW failed
Action: Examine system error message and refer to VMS documentation
Cause: VMS system service $ASCTOID failed
Action: Examine system error message and refer to VMS documentation
Cause: VMS system service $CHKPRO failed
Action: Examine system error message and refer to VMS documentation
Cause: VMS system service $SNDOPR failed
Action: Examine system error message and refer to VMS documentation
Cause: VMS system service $GETUAI failed
Action: Examine system error message and refer to VMS documentation
Cause: VMS system service $HASH_PASSWORD failed
Action: Examine system error message and refer to VMS documentation
Cause: VMS system service $GETJPIW failed
Action: Examine system error message and refer to VMS documentation
Cause: VMS system service $GETUAI failed
Action: Examine system error message and refer to VMS documentation
Cause: VMS system service $GETJPIW failed
Action: Examine system error message and refer to VMS documentation
Cause: VMS system service $CHANGE_CLASS failed
Action: Examine system error message and refer to SEVMS documentation
Cause: VMS system service $CHANGE_CLASSS failed
Action: Examine system error message and refer to SEVMS documentation
Cause: VMS system service $CHANGE_CLASS failed
Action: Examine system error message and refer to SEVMS documentation
Cause: VMS system service $FORMAT_CLASS failed because the given binary classification was not valid.
Action: Examine system error message and refer to SEVMS documentation
Cause: VMS system service $IDTOASC failed while looking up the string representation in the rights database of a secrecy level.
Action: Define the entry in the rights database which the binary label you specified references.
Cause: VMS system service $IDTOASC failed while looking up the string representation in the rights database of an integrity level.
Action: Define the entry in the rights database which the binary label you specified references.
Cause: An illegal database block size was specified in the parameter file. It must be positive, a multiple of 512, and less than the maximum physical i/o data size.
Action: Change db_block_size in the parameter file to conform to these limits.
Cause: An illegal redo log buffer size was specified in the parameter file. It must be positive and a multiple of 512.
Action: Change log_buffer in the parameter file to conform to these limits.
Cause: While creating the system global area (SGA) backing file, VMS system service $CREATE failed.
Action: Examine the system error message and refer to VMS documentation.
Cause: While creating the system global area (SGA), VMS system service $CRMPSC failed.
Action: Examine the system error message and refer to VMS documentation.
Cause: While deleting the system global area (SGA), VMS system service $DGBLSC failed.
Action: Examine the system error message and refer to VMS documentation.
Cause: While mapping the system global area (SGA) during logon, VMS system service $MGBLSC failed. The usual reason is that Oracle has not been started up.
Action: Examine the system error message and refer to VMS documentation. Start up Oracle if it is not already started.
Cause: An attempt to map the SGA during logon failed because it was already mapped. This is an internal error.
Action: Exit your program and try again, and report this to your customer support representative.
Cause: While unmapping the system global area (SGA) during logoff, VMS system service $CRETVA failed.
Action: Examine the system error message and refer to VMS documentation.
Cause: An attempt to unmap the SGA during logoff failed because it was not mapped. This is an internal error.
Action: Exit your program and try again, and report this to your customer support representative.
Cause: While extending the program global area (PGA), VMS system service $EXPREG failed. This often happens when the virtual memory page count quota is exceeded.
Action: Examine the system error message and refer to VMS documentation.
Cause: While deleting the program global area (PGA) during logoff, VMS system service $DELTVA failed.
Action: Examine the system error message and refer to VMS documentation.
Cause: While creating or extending a context area, VMS system service $EXPREG failed. This often happens when the virtual memory page count quota is exceeded.
Action: Examine the system error message and refer to VMS documentation.
Cause: While deleting a context area, VMS system service $DELTVA failed.
Action: Examine the system error message and refer to VMS documentation.
Cause: The buffer debug function was called with an illegal value. This is an internal error.
Action: Contact your customer support representative.
Cause: While attempting to set protection in the database buffer debug mechanism, VMS system service $CRETVA failed.
Action: Contact your customer support representative.
Cause: While attempting to set protection in the database buffer debug mechanism, VMS system service $SETPRT failed.
Action: Contact your customer support representative.
Cause: While attempting to set protection in the database buffer debug mechanism, VMS system service $MGBLSC failed.
Action: Contact your customer support representative.
Cause: Trying to change the buffer protect mode when the SGA was not created with buffer protect debug option. This is an internal error.
Action: Contact your customer support representative.
Cause: An attempt was made to map an SGA with software in which the SGA pad area isn’t large enough.
Action: Create a smaller SGA, or relink the software with a larger pad.
Cause: An attempt was made to create an SGA with software in which the SGA pad area isn’t large enough.
Action: Create a smaller SGA, or relink the software with a larger pad.
Cause: An attempt was made to map to the SGA while it was being initialized.
Action: Wait until initialization is complete, and try again.
Cause: The system global area (SGA) backing file could not be allocated using the system pagefile because the system-wide limit on global pages has been exceeded.
Action: Either increase the VMS system parameter GBLPAGFIL or use a disk file as the SGA backing file.
Cause: While attempting to set the protection of a region of memory, an error was returned from the $CMKRNL system service.
Action: Examine the system error message and refer to VMS documentation.
Cause: an internal error
Action: Report this error to Oracle Support Services, provide your INIT.ORA file.
Cause: While attempting to set the label on a file, SEVMS service $CHANGE_CLASS failed.
Action: Examine the system message and refer to SEVMS system documentation.
Cause: While attempting to create a file, VMS system service $CREATE failed.
Action: Examine the system message and refer to VMS system documentation.
Cause: While attempting to reopen a file, VMS system service $OPEN failed.
Action: Examine the system message and refer to VMS system documentation.
Cause: While attempting to get the user’s terminal device name, user name, user program name, or process name during logon, VMS system service $GETJPIW failed.
Action: Examine the system error message and refer to VMS documentation.
Cause: While attempting to translate SYS$INPUT during a prompt for a password, VMS system service $TRNLOG failed.
Action: Examine the system error message and refer to VMS documentation.
Cause: While attempting to get device characteristics during a prompt for a password, VMS system service $GETDVI failed.
Action: Examine the system error message and refer to VMS documentation.
Cause: While prompting for a password, VMS system service $ASSIGN failed.
Action: Examine the system error message and refer to VMS documentation.
Cause: While prompting for a password, VMS system service $QIOW failed.
Action: Examine the system error message and refer to VMS documentation.
Cause: A VMS exception occurred while executing in the Oracle exception handler. The message includes the signal number, first and second signal arguments, and exception PC, PSL and R0. This is an internal error.
Action: Contact your customer support representative.
Cause: VMS system service $IDTOASC failed while looking up the string representation in the rights database of a secrecy category.
Action: Define the entry in the rights database which the binary label you specified references.
Cause: VMS system service $IDTOASC failed while looking up the string representation in the rights database of an integrity category.
Action: Define the entry in the rights database which the binary label you specified references.
Cause: SEVMS system service $PARSE_CLASS failed because the given string did not represent a valid classification.
Action: Examine system error message and refer to SEVMS documentation.
Cause: A call to the Oracle shared image entry point occurred from within the shared image. This is an internal error.
Action: Contact your customer support representative.
Cause: While attempting to set up the dispatch vectors for the shared image, an error occurred. This is an internal error.
Action: Contact your customer support representative.
Cause: During Oracle shared image entry, a dispatch to kernel mode failed.
Action: Make sure that your shared image is installed with the CMKRNL privilege, then contact your customer support representative.
Cause: During an attempt to restore user privileges at Oracle shared image exit, VMS system service $SETPRV failed. This is an internal error.
Action: Contact your customer support representative.
Cause: During an attempt to restore the supervisor-mode stack at Oracle shared image exit, VMS system service $SETSTK failed. This is an internal error.
Action: Contact your customer support representative.
Cause: During an attempt to set the Oracle supervisor-mode stack at Oracle shared image entry, VMS system service $SETSTK failed. This is an internal error.
Action: Contact your customer support representative.
Cause: An interrupt was received while archiving the logs
Action: Retry operation
40 total views, no views today
Oracle 12c R2 Error Codes and Solution Suggestions from ORA-07700 to ORA-08000
Cause: An interrupt was received while archiving the logs
Action: Retry operation
Cause: Overflow of buffer for parsing archive control text string
Action: This is an internal error, please report to Oracle
Cause: Unrecognized device type in archive text
Action: This is an internal error, please report to Oracle
Cause: The archive control text in the ARCHIVE command is invalid; the device type (to indicate a file or tape) must be followed by a ‘/’.
Action: Refer to the SQLDBA Guide for the proper syntax of the text.
Cause: The archive control text in the ARCHIVE command is invalid; the device name must be followed by a ‘:’.
Action: Refer to the SQLDBA Guide for the proper syntax of the text.
Cause: The buffer supplied for the device name is too small. This is an internal error.
Action: Contact your customer support representative.
Cause: The archive control text in the ARCHIVE command is invalid; the disk file name is missing.
Action: Refer to the SQLDBA Guide for the proper syntax of the text.
Cause: The archive control text in the ARCHIVE command is invalid; the tape label name is missing.
Action: Refer to the SQLDBA Guide for the proper syntax of the text.
Cause: The buffer supplied for the tape label is too small. This is an internal error.
Action: Contact your customer support representative.
Cause: The user specified a remote disk for archiving via DECnet.
Action: Archive to a disk on the local host.
Cause: The buffer supplied for the file name is too small. This is an internal error.
Action: Contact your customer support representative.
Cause: VMS system service SYS$MOUNT failed
Action: Examine system error message and refer to VMS documentation
Cause: VMS system service SYS$DISMNT failed
Action: Examine system error message and refer to VMS documentation
Cause: VMS system service SYS$GETDVI failed”
Action: Specify a valid device in ARCHIVE control string
Cause: VMS system service LIB$GET_VM failed”
Action: Examine system error message and refer to VMS documentation
Cause: VMS system service LIB$FREE_VM failed
Action: Examine system error message and refer to VMS documentation
Cause: A call to sys$enq returned an error indicating that the operating system lacked the resources necessary to create a lock. This is caused by the messages SS$_EXENQLM or SS$_INSFMEM.
Action: Free up some of the required resource to allow the creation of the required lock.
Cause: structures used for reading error message files do not match
Action: this is an internal error, please report to Oracle
Cause: VMS system service $OPEN failed
Action: Examine system error message and refer to VMS documentation
Cause: VMS system service $CONNECT failed
Action: Examine system error message and refer to VMS documentation
Cause: An error message file is of incorrect format
Action: Unless an error file has been changed, report this to Oracle
Cause: seal in passed in handle does not match correct value
Action: this is an internal error, please report to Oracle
Cause: VMS system service $CLOSE failed
Action: Check system error and refer to VMS documentation
Cause: seal in passed in handle does not match correct value
Action: this is an internal error, please report to Oracle
Cause: VMS system service $READ failed
Action: Check system error and refer to VMS documentation
Cause: An attempt to create a message file failed. This is an internal error.
Action: Contact your customer support representative.
Cause: An attempt to allocate a cache for a newly-created message file failed. This is an internal error.
Action: Contact your customer support representative.
Cause: An attempt to seek before writing a message file cache element failed. This is an internal error.
Action: Contact your customer support representative.
Cause: An attempt to write a message file cache element failed. This is an internal error.
Action: Contact your customer support representative.
Cause: An attempt to seek before reading a message file cache element failed. This is an internal error.
Action: Contact your customer support representative.
Cause: An attempt to read a message file cache element failed. This is an internal error.
Action: Contact your customer support representative.
Cause: The seal in a passed-in handle does not match correct value. This is an internal error.
Action: Contact your customer support representative.
Cause: The seal in a passed-in handle does not match correct value. This is an internal error.
Action: Contact your customer support representative.
Cause: The destination string provided to the function is too short This is an internal error.
Action: Contact your customer support representative.
Cause: the $open service failed. This is an internal error
Action: Contact your customer support representative.
Cause: An impossible request for binary to decimal conversion was made
Action: This conversion cannot be performed
Cause: An impossible request for binary to decimal conversion was made
Action: This conversion cannot be performed
Cause: An impossible request for binary to decimal conversion was made
Action: This conversion cannot be performed
Cause: An impossible request for decimal to binary conversion was made
Action: This conversion cannot be performed
Cause: An impossible request for decimal to binary conversion was made
Action: This conversion cannot be performed
Cause: An error was returned from the SYS$CRELNM function
Action: Check system error and refer to VMS documentation
Cause: An error was returned from the SYS$DELLNM function
Action: Check system error and refer to VMS documentation
Cause: An error was returned from the SYS$CREMBX function while trying to create the process dump mailbox.
Action: Check system error and refer to VMS documentation
Cause: An error was returned from $QIO while trying to queue a read to the process dump mailbox.
Action: Check system error and refer to VMS documentation
Cause: An error was returned from SYS$SETIMR while trying to queue a process spin-watch timer.
Action: Check system error and refer to VMS documentation
Cause: An error was returned from SYS$QIO while trying to read the process dump mailbox.
Action: Check system error and refer to VMS documentation
Cause: An error was returned from SYS$GETDVIW while trying to get information about the process dump mailbox.
Action: Check system error and refer to VMS documentation
Cause: An error was returned from LIB$GET_VM while attempting to allocate memory for an i/o vector.
Action: Check system error and refer to VMS documentation
Cause: An error was returned from SYS$OPEN while attempting to open the data file for reading
Action: Check system error and refer to VMS documentation
Cause: An error was returned from SYS$CLOSE while attempting to close the input data file
Action: Check system error and refer to VMS documentation
Cause: An error was returned from LIB$FREE_VM while attempting to free the memory for the i/o vector
Action: Check system error and refer to VMS documentation
Cause: An error was returned from LIB$GET_VM while attempting to allocate memory for data and index buffers
Action: Check system error and refer to VMS documentation
Cause: An error was returned from LIB$FREE_VM while attempting to free memory used by data and index buffers
Action: Check system error and refer to VMS documentation
Cause: The longest record in the file will not fit into the largest data buffer that can be allocated
Action: Modify the RMS file to have smaller records
Cause: An error was returned by SYS$CONNECT while attempting to open the data file
Action: Check system error and refer to VMS documentation
Cause: An error was returned by SYS$GET while attempting to read the data file
Action: Check system error and refer to VMS documentation
Cause: An error was returned by SYS$GET while attempting to skip records in the input file
Action: Check system error and refer to VMS documentation
Cause: You are using a bad option to loader Fixed= is one legal option. Check documentation for others.
Action: Check documentation
Cause: An error occurred while setting up the control interrupt handler
Action: This is an internal error. Contact your Oracle representative.
Cause: A list of all files open by this process could not be obtained.
Action: This is an internal error. Contact your customer support representative.
Cause: the sequence parent state objects for this session are all used
Action: an internal error; quit the session and begin a new one
50 total views, 5 views today
Oracle 12c R2 Error Codes and Solution Suggestions from ORA-08000 to ORA-08200
Cause: the sequence parent state objects for this session are all used
Action: an internal error; quit the session and begin a new one
Cause: sequence CURRVAL has been selected before sequence NEXTVAL
Action: select NEXTVAL from the sequence before selecting CURRVAL
Cause: The sequence was created with unsafe values for some of the parameters. The calculation of NEXTVAL cannot be made because it exceeds the legal represention size.
Action: Alter or recreate the sequence number with legal limits.
Cause: instantiating NEXTVAL would violate one of MAX/MINVALUE
Action: alter the sequence so that a new value can be requested
Cause: A row with the given rowid does not exist in any of the tables given
Action: check the query for misspellings of table names and the rowid
Cause: the row has been deleted by another user since the operation began
Action: re-try the operation
Cause: Max locks have been reached for this transaction in this block
Action: Commit changes
Cause: the shared instance being started does not have the same value for use_row_enqueues as already running instances
Action: ensure that all instances’ INIT.ORA files specify the same value for the parameter ‘use_row_enqueues’
Cause: Validate Index detected an inconsistency in its argument index
Action: Send trace file to your customer support representative
Cause: Internal error: possible inconsistency in index
Action: Send trace file to your customer support representative, along with information on reproducing the error
Cause: Internal error: possible inconsistency in index
Action: Send trace file to your customer support representative, along with information on reproducing the error
Cause: The object has been deleted by another user since the operation began, or a prior incomplete recovery restored the database to a point in time during the deletion of the object.
Action: Delete the object if this is the result of an incomplete recovery.
Cause: the index is being created or rebuild or waited for recovering from the online (re)build
Action: wait the online index build or recovery to complete
Cause: set this event only under the supervision of Oracle development
Action: debugging only
Cause: The online index builder could not create its journal table
Action: Rename the conflicting table or rerun the SQL statement. There * may be a concurrent online index rebuild on the same object. rename your table in conflict or rerun the SQL statement * there may be a concurrent online index rebuild on the same object.
Cause: only support normal index or IOT top-level index
Action: change your index type
Cause: may not specify nosort for online index build
Action: get rid of nosort in the index creation command
Cause: Oracle Kernel test only
Action: Donot set this event(for test only)
Cause: User attempted to coalesce a partitioned index using ALTER INDEX COALESCE statement, which is illegal
Action: Coalesce the index a (sub)partition at a time (using ALTER INDEX MODIFY (sub)PARTITION COALESCE)
Cause: User attempted to coalesce a composite partition
Action: Coalesce the index a subpartition at a time (using ALTER INDEX MODIFY SUBPARTITION COALESCE)
Cause: User attempted to compress a composite partition index
Action: create uncompressed composite partition index
Cause: User attempted to alter a fake index
Action: drop fake index
Cause: User attempted to create index type that online doesnot support
Action: use offline index create/rebuild command
Cause: User attempted to create index online without allowing DML Share lock
Action: allow DML share lock on the base table
Cause: Block maintenance forced the release of a block pin
Action: Contact your customer support representative
Cause: Deferred Foreign Key constraints cannot be enforced due to the index key being too big and built on a non-default DB_BLOCK_SIZE.
Action: First try to drop the Foreign Key and then the primary key.
Cause: Specifying the initrans need additional space to hold the index key which might make the index too big
Action: Try giving a smaller initrans value
Cause: Alter index Build/Rebuild online require existing of SYS.IND_ONLINE$ table.
Action: User/DBA needs to create sys.ind_online$ before alter the index /rdbms/admin/catcio.sql contains script to create ind_online$.
Cause: Too many indexes needed to be maintained. The limit is 2^16 indexes for each DML statement
Action: Make sure the index maintainance is online. If indexes need to be maintained offline, drop some indexes.
Cause: The online (re)build journal is inconsistent with ongoing DML and cannot be used successfully to complete the online index (re)build.
Action: Reissue the online (re)build operation, after performing any cleanup, if needed.
Cause: An attempt was made to perform an action that is not currently supported in a discrete transaction.
Action: Rollback the transaction, and retry it as a normal transaction.
Cause: Encountered data changed by an operation that does not generate rollback data : create index, direct load or discrete transaction.
Action: In read/write transactions, retry the intended operation. Read only transactions must be restarted.
Cause: Encountered data changed by an operation that occurred after the start of this serializable transaction.
Action: In read/write transactions, retry the intended operation or transaction.
Cause: Serializable mode is not supported for user INTERNAL.
Action: Reconnect as another user and retry the SET TRANSACTION command.
Cause: Encountered data changed by an operation that occurred after a specific snapshot. This is usually used to indicate that a particular cached copy of a datablock is stale. This is used for internal use for now.
Action: refresh the cached copy of the datablock and retry operation.
Cause: Could not match the time to an SCN from the mapping table.
Action: try using a larger time.
Cause: supplied scn was beyond the bounds of a valid scn.
Action: use a valid scn.
Cause: user tried to do dml or ddl while in Flashback mode
Action: disable Flashback and re-attempt the operation
Cause: user tried to do Flashback in the middle of a transaction
Action: do a commit
Cause: as stated above
Action: disable first before re-enabling
Cause: user logged on as SYS
Action: logon as a different (non SYS) user.
Cause: as stated above
Action: enter a valid timestamp
Cause: A snapshot expression using AS OF was specified when not allowed.
Action: Do not use the AS OF clause
Cause: An attempt was made to perform Flashback Table operation on a table for which row movement has not been enabled. Because the Flashback Table does not preserve the rowids, it is necessary that row movement be enabled on the table.
Action: Enable row movement on the table
Cause: An attempt was made to perform Flashback Table operation using a restore point from a different incarnation of the database
Action: Provide a restore point from the current database incarnation
Cause: An attempt was made to perform Flashback Table operation on a remote table. This is not permitted.
Action: Do not perform a Flashback Table operation on remote tables.
Cause: An attempt was made to perform Flashback Table operation on a fixed table. This is not permitted.
Action: Do not perform a Flashback Table operation on fixed tables.
Cause: An attempt was made to perform Flashback Table operation on a temporary table. This is not permitted.
Action: Do not perform a Flashback Table operation on temporary tables.
Cause: An attempt was made to perform Flashback Table operation on a materialized view. This is not permitted.
Action: Do not perform a Flashback Table operation on materialized views or snapshot logs.
Cause: An attempt was made to perform Flashback Table operation on a partition. This is not permitted.
Action: Do not perform a Flashback Table operation on partitions.
Cause: An attempt was made to perform Flashback Table operation on AQ tables. This is not permitted.
Action: Do not perform a Flashback Table operation on AQ tables.
Cause: An attempt was made to perform Flashback Table operation on a clustered table. This is not permitted.
Action: Do not perform a Flashback Table operation on clustered tables.
Cause: An attempt was made to perform Flashback Table operation on a object table or a nested table or a table with nested table column. This is not permitted.
Action: Do not perform a Flashback Table operation on such tables.
Cause: An attempt was made to perform Flashback Table operation on an object on which the operation is not supported.
Action: Do not perform a Flashback Table operation on such objects.
235 total views, no views today
Oracle 12c R2 Error Codes and Solution Suggestions from ORA-08200 to ORA-08400
Cause: The environment variable ORACLE_SID is not set.
Action: Set the ORACLE_SID environment variable.
Cause: Cannot translate $ORACLE_HOME/dbs/sgadef$ORACLE_SID.dbf.
Action: Ensure that ORACLE_HOME and ORACLE_SID are properly set.
Cause: The address file could not be opened.
Action: Check that ORACLE is up. Check that the file $(ORACLE_HOME)/dbs/sgadef$(ORACLE_SID).dbf exists and has correct permissions.
Cause: The address file could not be read.
Action: Check that the file $(ORACLE_HOME)/dbs/sgadef$(ORACLE_SID).dbf exists and contains a single line of text.
Cause: The System Commit Number has not yet been initialized.
Action: Contact your customer support representative.
Cause: Oracle requested that an I/O error be returned for this operation.
Action: This should not occur in normal Oracle operation. Contact support.
Cause: The n_core system call failed, maybe due to insufficient memory.
Action: Specify a smaller number of buffers. Check INIT.ORA parameters.
Cause: The process cannot attach to the SGA. This can happen if either the listener can’t attach, or the process cannot communicate with the listener.
Action: Verify that the instance is up and running. Contact your customer support representative.
Cause: Probably, the listener process has died.
Action: Contact your customer support representative.
Cause: The n_core system call failed while detaching from the SGA.
Action: Note nCX error returned; contact your customer support representative.
Cause: The instance listener address cannot be read from the sgadef file.
Action: Verify $(ORACLE_HOME) and $(ORACLE_SID) are set correctly. Additional information gives error return from ora_addr.
Cause: A process wishing to attach to the SGA is on a different node from its instance’s listener.
Action: Verify $(ORACLE_HOME) and $(ORACLE_SID) are set correctly. Contact your customer support representative.
Cause: The n_share call failed, probably because the listener has died.
Action: Check if the listener is running, and contact your customer support representative.
Cause: Attempting to attach to an SGA which has not yet been created.
Action: Verify that the instance is running. Contact your customer support representative.
Cause: The n_core system call failed while detaching from the SGA.
Action: Check nCX error, and contact your customer support representative.
Cause: A recursive operation requiring audit was attempted in the middle of an auditing operation or an audit table movement operation. The most likely reason is that space management operations needed to free up space in the audit tablespace or a SQL operation on dictionary tables directly or using database triggers which produced more audit records.
Action: Check space in the tablespace for SYS.AUD$ or SYS.FGA_LOG$ and correct the problem. Or, if the problem was recursively auditing SQL operations, remove the audit configuration on such objects or statements.
Cause: A process could not connect to the nameserver.
Action: Make sure the nameserver is up and running. Additional information gives nameserver’s returned status.
Cause: The listener nameserver entry for an instance could not be found.
Action: Make sure the nameserver is up and running. Additional information gives nameserver’s returned status.
Cause: The listener nameserver entry could not be freed
Action: Additional information gives nameserver’s returned status. Contact your customer support representative.
Cause: The connection to the nameserver could not be closed.
Action: Additional information gives nameserver’s returned status. Contact your customer support representative.
Cause: A process could not connect to the nameserver.
Action: Make sure the nameserver is up and running. Additional information gives nameserver’s returned status.
Cause: The listener’s addressing information could not be registered.
Action: Make sure the nameserver is up and running. Additional information gives nameserver’s returned status.
Cause: The connection to the nameserver could not be closed.
Action: Additional information gives nameserver’s returned status. Contact your customer support representative.
Cause: The connection to the nameserver could not be closed.
Action: Additional information gives nameserver’s returned status. Contact your customer support representative.
Cause: The listener’s addressing information could not be removed.
Action: Additional information gives nameserver’s returned status. Contact your customer support representative.
Cause: Archive files cannot be created with the given archival control string.
Action: Check that the volume exists
Cause: The given archival control string expands into too many characters.
Action: Reduce archive control string length.
Cause: There is insufficient memory to return the requested value
Action: Reduce memory usage and retry.
Cause: The requested environment variable is not set
Action: Ensure that the variable name requested is correct.
Cause: There is no room to record the pid for a background process
Action: Shutdown abort and restart the database.
Cause: There is insufficient memory to expand the environment.
Action: Reduce memory usage and retry.
Cause: Could not retrieve CPU times because n_stat failed.
Action: Contact customer support.
Cause: Oracle could not open a file.
Action: Check the Unix errno returned as additional information.
Cause: Oracle could not obtain information about an open file.
Action: Check the Unix errno returned as additional information.
Cause: An illegal value for the record size was specified.
Action: Specify a value for the recsize option that is greater than 0.
Cause: An illegal value for the maximum record size was specified.
Action: Specify a value for the maxrecsize option that is greater than 0.
Cause: An unrecognized processing option was specified.
Action: Check the Oracle for nCUBE 2 User’s Guide for valid options.
Cause: Memory for the load buffers could not be allocated.
Action: Reduce the maximum record size. Eliminate any unnecessary processes on your current node before running SQL*Loader again.
Cause: An error occurred trying to close a file.
Action: Check the Unix errno returned as additional information.
Cause: An error occurred trying to read from a file.
Action: Check the Unix errno returned as additional information.
Cause: The lseek system call returned an error.
Action: Check the Unix errno returned as additional information.
Cause: The lseek system call returned an error.
Action: Check the Unix errno returned as additional information.
Cause: An error occurred trying to read from a file.
Action: Check the Unix errno returned as additional information.
Cause: An error occurred trying to read from a file.
Action: Check the Unix errno returned as additional information.
Cause: An internal error
Action: Contact your customer support representative.
Cause: An internal error
Action: Contact your customer support representative.
Cause: A call to the lkmgr failed to open and convert the bias lock
Action: Check to make sure the lkmgr is up.
Cause: A call to the lkmgr failed to close the bias lock
Action: Check to make sure the lkmgr is up.
Cause: An attempt was made to automatically spool a file to the printer
Action: None
Cause: Oracle timed out waiting for an event
Action: Contact your Oracle support representative
Cause: (same as 1545)
Action: (same as 1545). Also, make sure you have created enough rollback segments for the number of instances you are trying to start.
Cause: An illegal command was executed for the nCUBE platform.
Action: There is no need to issue this command.
Cause: A command that can only be issued on instance 1 was issued elsewhere.
Action: Log on to instance 1 and repeat the command.
Cause: An error occurred trying to connect to the redo server.
Action: The OS specific error message should tell you what to do.
Cause: An error occurred trying to close the redo server connection.
Action: The OS specific error message should tell you what to do.
Cause: An error occurred trying to send redo to the redo server.
Action: The OS specific error message should tell you what to do.
30 total views, no views today
Oracle 12c R2 Error Codes and Solution Suggestions from ORA-08400 to ORA-08600
Cause: An invalid compiler name compname was passed to a UTL_PG conversion routine.
Action: Correct the compiler name parameter in the PL/SQL code that called the conversion routine.
Cause: An error occurred during execution of a PL/SQL code coverage procedure.
Action: Check the error stack for more details.
Cause: The WMSGBSIZ is the maximun size for warning message block, it is recommanded to be 1024 bytes to 8 kbytes.
Action: Defined WMSGBLK of size between 1k to 8k bytes and update the WMSGBSIZ to the sizeof(WMSGBLK).
Cause: An invalid compiler type is defined in format control block. The format control block is invalid.
Action: Check to be sure that the format parameter was built by MAKE_RAW_TO_NUMBER_FORMAT or MAKE_NUMBER_TO_RAW_FORMAT, and that it was not accidentally overwritten or modified by the PL/SQL procedure.
Cause: The function routine returned an error. Where routine may be: RAW_TO_NUMER NUMBER_TO_RAW RAW_TO_NUMBER_FORMAT NUMBER_TO_RAW_FORMAT MAKE_NUMBER_TO_RAW_FORMAT MAKE_RAW_TO_NUMBER_FORMAT
Action: This message will be preceded by messages providing details about the error. Check those messages to determine what action to take.
Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine contained invalid data. The picture mask parameter specified a digit, but the corresponding input from the raw data did not contain a valid digit.
Action: Either the input data is incorrect, or the picture mask is incorrect. Correct the appropriate item.
Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine had no leading sign, but the mask options parameter specified a leading sign.
Action: Correct the input raw data or the mask options so that they match.
Cause: The picture mask parameter passed to a UTL_PG RAW_TO_NUMBER conversion routine contained a zero, but the corresponding input from the raw data was not a zero.
Action: Either the input data is incorrect, or the picture mask is incorrect. Correct the appropriate item.
Cause: The input raw data passed to a UTL_PG RAW_TO_NUMBER conversion routine contained invalid floating point data.
Action: Correct the input raw data.
Cause: The picture mask parameter passed to a UTL_PG RAW_TO_NUMBER conversion routine contained non-numeric characters, but the conversion was to a numeric data type.
Action: Correct the picture mask parameter.
Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine had no trailing sign, but the mask options parameter specified a trailing sign.
Action: Correct the input raw data or the mask options so that they match.
Cause: The input MASK passed to a UTL_PG RAW_TO_NUMBER conversion routine had no leading sign, but the mask options parameter specified a leading sign.
Action: Correct the input raw data or the mask options so that they match.
Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine had an invalid sign digit in the position where the picture mask specified a sign.
Action: Correct the input raw data or the picture mask so that they match.
Cause: The picture mask parameter passed to a UTL_PG NUMBER_TO_RAW conversion routine contained non-numeric characters, but the conversion was to a numeric data type.
Action: Correct the picture mask parameter.
Cause: The output raw buffer passed to a UTL_PG NUMBER_TO_RAW conversion routine was not large enough to contain the results of the conversion based on the picture mask.
Action: Increase the raw buffer size to the size necessary to hold the entire result of the conversion.
Cause: A closed parenthesis was missing from the picture mask passed to a UTL_PG conversion routine.
Action: Correct the picture mask.
Cause: A syntax error was found in the BLANK WHEN ZERO clause in the mask options parameter passed to a UTL_PG conversion routine. Valid specifications are: BLANK ZERO BLANK ZEROS BLANK ZEROES BLANK WHEN ZERO BLANK WHEN ZEROS BLANK WHEN ZEROES
Action: Correct the mask options parameter.
Cause: A syntax error was found in the JUSTIFIED clause in the mask options parameter passed to a UTL_PG conversion routine. Valid specifications are: JUST JUST RIGHT JUSTIFIED JUSTIFIED RIGHT
Action: Correct the mask options parameter.
Cause: A syntax error was found in the SIGN clause in the mask options parameter passed to a UTL_PG conversion routine. Valid specifications are: SIGN LEADING SIGN LEADING SEPARATE SIGN LEADING SEPARATE CHARACTER SIGN TRAILING SIGN TRAILING SEPARATE SIGN TRAILING SEPARATE CHARACTER SIGN IS LEADING SIGN IS LEADING SEPARATE SIGN IS LEADING SEPARATE CHARACTER SIGN IS TRAILING SIGN IS TRAILING SEPARATE SIGN IS TRAILING SEPARATE CHARACTER
Action: Correct the mask options parameter.
Cause: A syntax error was found in the SYNCHRONIZED clause in the mask options parameter passed to a UTL_PG conversion routine. Valid specifications are: SYNC SYNC LEFT SYNC RIGHT SYNCHRONIZED SYNCHRONIZED LEFT SYNCHRONIZED RIGHT
Action: Correct the mask options parameter.
Cause: A syntax error was found in the USAGE clause in the mask options parameter passed to a UTL_PG conversion routine. Valid specifications are: USAGE DISPLAY USAGE COMP USAGE COMP-3 USAGE COMP-4 USAGE COMPUTATIONAL USAGE COMPUTATIONAL-3 USAGE COMPUTATIONAL-4 USAGE IS DISPLAY USAGE IS COMP USAGE IS COMP-3 USAGE IS COMP-4 USAGE IS COMPUTATIONAL USAGE IS COMPUTATIONAL-3 USAGE IS COMPUTATIONAL-4
Action: Correct the mask options parameter.
Cause: A syntax error was found in the DECIMAL-POINT environment clause parameter passed to a UTL_PG conversion routine. Valid specifications are: DECIMAL-POINT IS COMMA
Action: Correct the environment clause parameter.
Cause: An invalid numeric symbol was found in the picture mask parameter passed to a UTL_PG conversion routine.
Action: Correct the picture mask parameter.
Cause: The CR suffix was incorrectly specified in the picture mask parameter passed to a UTL_PG conversion routine. The CR suffix can only appear at the end of a picture mask.
Action: Correct the picture mask parameter.
Cause: The DB suffix was incorrectly specified in the picture mask parameter passed to a UTL_PG conversion routine. The DB suffix can only appear at the end of a picture mask.
Action: Correct the picture mask parameter.
Cause: The floating point exponent symbol ‘E’ was specified in the picture mask parameter passed to a UTL_PG conversion routine. The floating point data type is currently not supported by the UTL_PG conversion routines.
Action: Correct the picture mask parameter, and the data, if necessary.
Cause: The picture mask passed to a UTL_PG conversion routine contained more than one decimal point indicator (‘V’). Only one decimal point indicator is allowed in the picture mask.
Action: Correct the picture mask parameter.
Cause: The picture mask passed to a UTL_PG conversion routine contained more than one operational sign indicator (‘S’). Only one operational sign indicator is allowed in the picture mask.
Action: Correct the picture mask parameter.
Cause: A syntax error was found in the CURRENCY SIGN environment clause parameter passed to a UTL_PG conversion routine. Valid specifications are: CURRENCY SIGN IS x where x is a valid currency sign
Action: Correct the environment clause parameter.
Cause: The picture mask parameter passed to a UTL_PG conversion routine contained no sign symbol (‘S’, ‘+’, or ‘-‘), but the mask options parameter contained a SIGN clause. A sign symbol is required in the picture mask parameter when the mask options parameter contains a SIGN clause.
Action: Correct the picture mask parameter or the mask options parameter.
Cause: A syntax error was found in the SEPARATE CHARACTER option of the SIGN clause in the mask options parameter passed to a UTL_PG conversion routine. Valid specifications are: SEPARATE SEPARATE CHARACTER
Action: Correct the mask options parameter.
Cause: The format parameter passed to a UTL_PG conversion routine was invalid. The format parameter should have been built by a prior call to either MAKE_RAW_TO_NUMBER_FORMAT or MAKE_NUMBER_TO_RAW_FORMAT.
Action: Check to be sure that the format parameter was built by MAKE_RAW_TO_NUMBER_FORMAT or MAKE_NUMBER_TO_RAW_FORMAT, and that it was not accidentally overwritten or modified by the PL/SQL procedure.
Cause: The format parameter passed to a UTL_PG conversion routine was not the correct length. Format parameters must be 2048 bytes in length.
Action: Check to be sure that the format parameter was built by MAKE_RAW_TO_NUMBER_FORMAT or MAKE_NUMBER_TO_RAW_FORMAT, and that it was not accidentally overwritten or modified by the PL/SQL procedure.
Cause: The environment parameter passed to a UTL_PG conversion routine contained an unsupported or invalid environment clause. Only the CURRENCY SIGN and the DECIMAL-POINT IS COMMA environment clauses are supported.
Action: Correct the environment parameter.
Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine contains invalid decimal data.
Action: Correct the input data.
Cause: The output variable passed to a UTL_PG RAW_TO_NUMBER was not large enough to hold the Oracle number resulting from the input decimal number.
Action: Be sure that the input decimal number is valid, and besure that the output variable is large enough to hold the Oracle number value.
Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine contained more than 42 digits. This exceeds the maximum size of an Oracle number.
Action: Correct the raw input buffer.
Cause: The input mask passed to UTL_PG numeric conversion routine contained more the 32 characters.
Action: Correct the mask input buffer.
Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine was less than %s bytes long, but the picture mask parameter specified that %s bytes of input data were to be converted.
Action: Either the input data is incorrect, or the picture mask is incorrect. Correct the appropriate item.
Cause: An error occurred when converting an Oracle number to a COBOL type of: DISPLAY COMP-3 or character variable. The Oracle number was not in the correct format.
Action: Correct the call to the conversion routine. The input must be a valid Oracle number variable.
Cause: The mask option clause was passed to a UTL_PG conversion routine, but is not supported by UTL_PG. The clause can be: USAGE IS POINTER USAGE IS INDEX USAGE IS COMP-1 USAGE IS COMP-2 POINTER
Action: Remove the clause from the mask options parameter in the PL/SQL call to UTL_PG.
Cause: A signed numeric entry with DISPLAY usage was converted using a non-defaulted character set and its PICTURE character-string contains an S. In these circumstances, a SIGN IS SEPARATE clause must be specified in the mask options.
Action: Either specify a valid SIGN IS SEPARATE clause in the mask options, use the defaulted character set, or don’t specify an S in the PICTURE character-string.
Cause: Picture mask USAGE option was overridden by the picture mask.
Action: This is an informational message only. The message may be eliminated by changing the USAGE option to match the picture mask.
Cause: Picture mask options such as OCCUR, SYNC and others are not processed by the UTL_PG numeric conversion routines.
Action: This is an informational message only. The message may be eliminated by removing the unnecessary picture mask options from the parameter list passed to the UTL_PG routine.
55 total views, no views today
Oracle 12c R2 Error Codes and Solution Suggestions from ORA-09200 to ORA-09370
Cause: Could be out of disk space
Action: See OSD error accompanying this message
Cause: Block sizes may not match
Action: See OSD error accompanying this message
Cause: db_block_size specified in init.ora could be incorrect
Action: See OSD error accompanying this message
Cause: File attributes may have changed
Action: See OSD error accompanying this message
Cause: Incorrect path may have been specified for the file
Action: See OSD error accompanying this message
Cause: File may have been truncated or corrupted
Action: See OSD error accompanying this message
Cause: File may have been truncated or corrupted
Action: See OSD error accompanying this message
Cause: File may have been truncated or corrupted
Action: See OSD error accompanying this message
Cause: File may have been corrupted
Action: See OSD error accompanying this message
Cause: File may have been truncated or corrupted
Action: See OSD error accompanying this message
Cause: Incorrect path may have been specified for the file
Action: See OSD error accompanying this message
Cause: File may have been truncated or corrupted
Action: See OSD error accompanying this message
Cause: File may have been truncated or corrupted
Action: See OSD error accompanying this message
Cause: Filename may be too long
Action: See OSD error accompanying this message
Cause: File may have been truncated or corrupted
Action: See OSD error accompanying this message
Cause: File may have been truncated or corrupted
Action: See OSD error accompanying this message
Cause: The directory specified as the value for the stated parameter could not be used.
Action: Make sure the directory you have specified is a valid directory/file specification.
Cause: Could be out of disk space
Action: See OSD error accompanying this message
Cause: File may be corrupted or truncated
Action: See OSD error accompanying this message
Cause: Could be out of memory
Action: See OSD error accompanying this message
Cause: Could be out of memory
Action: See OSD error accompanying this message
Cause: SGA may not have been created (database not started)
Action: See OSD error accompanying this message
Cause: May be out of resources
Action: See OSD error accompanying this message
Cause: Could be out of resources
Action: See OSD error accompanying this message
Cause: Could be out of resources
Action: See OSD error accompanying this message
Cause: Could be out of memory
Action: See OSD error accompanying this message
Cause: Could be out of resources
Action: See OSD error accompanying this message
Cause: Could be out of resources
Action: See OSD error accompanying this message
Cause: Could be out memory
Action: See OSD error accompanying this message
Cause: Could be out of memory
Action: See OSD error accompanying this message
Cause: Username may be too long
Action: See OSD error accompanying this message
Cause: Remote os login attempted when not allowed.
Action: See OSD error accompanying this message
Cause: An OS error was returned when verifying the role name.
Action: See OSD error accompanying this message
Cause: An OS role name was too long.
Action: See OSD error accompanying this message
Cause: CONNECT INTERNAL is no longer supported for DBA connections.
Action: Please try to connect AS SYSDBA or AS SYSOPER.
Cause: A non-loopback bequeath connect string was supplied for a database link.
Action: Please use a connect string with a different transport protocol, or specify a loopback connect string (one that points to the instance for the current session) using “(PROGRAM=<this instance’s ORACLE_HOME>/bin/oracle)” and, optionally, “(ENVS=”ORACLE_SID=<this instance’s ORACLE_SID>”)”.
Cause: File may be corrupted
Action: See OSD error accompanying this message
Cause: Possibly incorrect path specified to the file
Action: See OSD error accompanying this message
Cause: File could be corrupted
Action: See OSD error accompanying this message
Cause: File could be corrupted
Action: See OSD error accompanying this message
Cause: malloc() system call returned an error. The system might have run out of heap space
Action: Check additional information for the OS error.
Cause: Processing option passed is of incorrect format
Action: Consult your IUG for permissible formats
Cause: Could be out of memory
Action: See OSD error accompanying this message
Cause: Unable to access directory
Action: Specify a valid device in ARCHIVE control string
Cause: Bad directory or format specified
Action: Specify a valid directory in ‘log_archive_format’ and a valid format string in ‘log_archive_format’ in init.ora
Cause: An error was returned while attempting to send a message to the console operator
Action: See OSD error accompanying this message
Cause: Unable to detect the presence of DPMI
Action: Restart Windows and retry
Cause: An attempt was made to connect to S: while in enhanced mode
Action: Restart Windows in standard mode
Cause: Internal error
Action: See OSD error accompanying this message
Cause: May be out of resources
Action: See OSD error accompanying this message
Cause: Could be out of resources
Action: See OSD error accompanying this message
Cause: May be out of resources
Action: See OSD error accompanying this message
Cause: Internal buffer may have overflowed
Action: See OSD error accompanying this message
Cause: Internal error
Action: See OSD error accompanying this message
Cause: OS roles may not be supported for this platform
Action: See OSD error accompanying this message
Cause: The password specified is invalid
Action: See OSD error accompanying this message
Cause: There might not be enough memory for the command or hosting out may not be supported on this platform
Action: See OSD error accompanying this message
Cause: The system time might be set incorrectly
Action: See OSD error accompanying this message
Cause: OS roles may not be supported on this platform
Action: See OSD error accompanying this message
Cause: internal error
Action: See OSD error accompanying this message
Cause: internal error
Action: See OSD error accompanying this message
Cause: A client workstation that is abnormally disconnected would cause Oracle to terminate that session after about a minute. This message also appears in the trace file if a shutdown abort is performed.
Action: n/a
Cause: ORACLE_SID must be at the most 4 alphanumeric characters.
Action: n/a
Cause: Another instance is currently mounting the database
Action: n/a
Cause: The user performed a shutdown abort.
Action: n/a
Cause: This function may not be implemented.
Action: n/a
Cause: See OSD error accompanying this message
Action: n/a
Cause: See OSD error accompanying this message
Action: n/a
Cause: See OSD error accompanying this message
Action: n/a
Cause: See OSD error accompanying this message
Action: n/a
Cause: See OSD error accompanying this message
Action: n/a
Cause: See OSD error accompanying this message
Action: n/a
Cause: See OSD error accompanying this message
Action: n/a
Cause: See OSD error accompanying this message
Action: n/a
Cause: See OSD error accompanying this message
Action: n/a
Cause: See OSD error accompanying this message
Action: n/a
Cause: See OSD error accompanying this message
Action: n/a
Cause: See OSD error accompanying this message
Action: n/a
Cause: See OSD error accompanying this message
Action: n/a
Cause: See OSD error accompanying this message
Action: n/a
Cause: See OSD error accompanying this message
Action: n/a
Cause: See OSD error accompanying this message
Action: n/a
180 total views, no views today
Follow