ORA-00600: internal error code, arguments: [kksfbc-reparse-infinite-loop]

Hey i got this error code when execute query on java form

ORA-00600: internal error code, arguments: [kksfbc-reparse-infinite-loop], [0x290EB6C18], [], [], [], [], [], []
The solution is just simply re-compile source of the view that used.

Advertisements

ORA-09314: sltln: error translating logical name

Do anyone know how can this error means, how to prevent it ?

This is the result if i search over internet,

ORA-09314: sltln: error translating logical name
Cause: Internal buffer may have overflowed

Action: See OSD error accompanying this message

After all, i restart oracle service to fix this. But that is not a solution before i know what the cause of that.

database not open – redo log fail

database couldn’t open because i got the error,

ORA-00313: open failed for members of log group 1 of thread 1

ORA-00312: online log 1 thread 1: ‘E:\REDO\REDO01_01.ILG’

ORA-00312: online log 1 thread 1: ‘H:\REDO\REDO01_02.ILG’

i search some explanation about the error,

ora-00312: online log %s thread %s: ‘%s’

*Cause:  This message reports the filename for details of another message.

*Action: Other messages will accompany this message. See the

associated messages for the appropriate action to take.

ora-00313: open failed for members of log group %s of thread %s

*Cause:  The online log cannot be opened. May not be able to find file.

*Action: See accompanying errors and make log available.

so to open database, follow the step,

1)Using V$LOG, got the status of each group

In mount mode,

2) Clear the log groups which are not current,

ALTER DATABASE CLEAR UNARCHIVED LOGFILE GROUP 1

3) RECOVER DATABASE UNTIL CANCEL (This is what i missed and looking for the help)

4) ALTER DATABASE OPEN RESETLOGS;

OPEN RESETLOGS is valid whenever you make an incomplete recovery

ORA-06553: PLS-382: expression is of wrong type

CREATE OR REPLACE FUNCTION GET_BOOL
RETURN BOOLEAN
IS
BEGIN
RETURN TRUE;
END;

SELECT GET_BOOL() FROM DUAL;

ORA-06552: PL/SQL: Statement ignored
ORA-06553: PLS-382: expression is of wrong type

Cause :
There is BOOLEAN datatype is supported by PL/SQL and NOT supported by SQL
So you cannot use this function in a straight select statement.

However, this function work in another PL/SQL block

DECLARE
VBOOL BOOLEAN;
BEGIN
VBOOL := GET_BOOL();
IF( VBOOL = TRUE ) THEN
DBMS_OUTPUT.PUT_LINE( ‘TRUE’ );
END IF;
END;

So, we can change the function to return number(FALSE = 0, TRUE = 1)

CREATE OR REPLACE FUNCTION GET_BOOL
RETURN NUMBER
IS
BEGIN
IF TRUE THEN
RETURN 1;
ELSE
RETURN 0;
END IF;
END;

ORA-00257: archiver error. Connect internal only, until freed.

ORA-00257: archiver error. Connect internal only, until freed.
Cause: The archiver process received an error while trying to archive a redo log. If the problem is not resolved soon, the database will stop executing transactions. The most likely cause of this message is the destination device is out of space to store the redo log file.

Action: Check archiver trace file for a detailed description of the problem. Also verify that the device specified in the initialization parameter ARCHIVE_LOG_DEST is set up properly for archiving.

———————————-

I clear some archivelog that have fill up until server harddisk has no space anymore. After clear some archivelog, then automatically the message not display anymore.

ORA-00600: internal error code, arguments: [19004], [], [], [], [], []

ORA-00600: internal error code, arguments: [string], [string], [string], [string], [string], [string], [string], [string]
Cause: This is the generic internal error number for Oracle program exceptions. This indicates that a process has encountered an exceptional condition.
Action: Report as a bug – the first argument is the internal error number

—————————————————————————

ORA-00600 internal error code, arguments: [string], [string], [string], [string], [string], [string], [string], [string]

Cause: This is the generic internal error number for Oracle program exceptions. It indicates that a process has encountered a low-level, unexpected condition. Causes of this message include:

timeouts

file corruption

failed data checks in memory

hardware, memory, or I/O errors

incorrectly restored files

The first argument is the internal message number. Other arguments are various numbers, names, and character strings. The numbers may change meanings between different versions of Oracle.

Action: Report this error to Oracle Support Services after gathering the following information:

events that led up to the error

the operations that were attempted that led to the error

the conditions of the operating system and databases at the time of the error

any unusual circumstances that occurred before receiving the ORA-00600 message

contents of any trace files generated by the error

the relevant portions of the Alter files

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.
—————————————————————————

If you have receive this error, you could try to :

– analyze table,

analyze table mhs_suppliers delete statistics;

– rebuild table
If anybody have other solution, please leave a comment. ^_^

ORA-27101: shared memory realm does not exist

ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist

————————————————

Cause: Unable to locate shared memory realm
Action: Verify that the realm is accessible

Explanation:

you could be receive ORA-27101 because you tried to modify the database parameters such as SGA_MAX_SIZE size. You can try to bring back the original parameters.

C:\Documents and Settings\Administrator>sqplus /nolog

– SQL> conn / as sysdba;

– SQL> shutdown immediate;

– SQL> startup pfile=’D:\oracle\product\10.2.0\admin\wiapps\pfile\init.ora.112320071736′;

– SQL> create spfile from pfile;

– SQL> shutdown immediate;

– SQL> startup;

This logic is startup with pfile and copy oracle parameter in pfile to spfile, then startup with new spfile.