dbms_lob.write Failed with ORA-06502: PL/SQL: numeric or value error: invalid LOB locator specified: ORA-22275

Error Description:

PLSQL Block with dbms_lob.write command is getting failed with following error. Command: dbms_lob.write (tempblob,length(tempname), 1,utl_raw.cast_to_raw (substr(tempname,1,length(tempname))));

ORA-06502: PL/SQL: numeric or value error: raw variable length too long: Convert Varchar2 to Blob with utl_raw.cast_to_raw

Error Description:

Oracle datatype conversion from VARCHAR2 to BLOB using the function utl_raw.cast_to_raw  is getting failed with following error.

SQL>  update bl_test set TR_PIC=utl_raw.cast_to_raw(TR_NAME) WHERE LENGTH(TR_NAME)>2000;

Convert Oracle Varchar2 column to Blob data type Using utl_raw.cast_to_raw – Example

Here is the example for normal Oracle VARCHAR2 datatype to BLOB database.

In this example EMP is my sample table and I trying to convert ENAME column to blob.

Fix ORA-19870 ORA-19863: device block size 4186112 is larger than max allowed: 1048576

Error Description:

RMAN Duplicate database command failed with following error message.

RMAN-00571: ==============================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ==

RMAN-00571: ==============================================

RMAN-03002: failure of Duplicate Db command at 07/20/2012 09:50:30

RMAN-05501: aborting duplication of target database

HISTTIMEFORMAT: How to See the Linux commands History with Date and Time?

Linux command prompt provides history of all commands which got executed under that login. If you give normal history command it will not show the date and time for the command execution. But in many cases you would need the date and time of the command execution which we can easily get it by formatting the HISTTIMEFORMAT environment variable.

Siebel Error SBL-ODC-00105 ORA- 24345 A Truncation or null fetch error occurred

Error Description:

Siebel application screen is throwing the following error while querying.

SBL-ODC-00105 ORA- 24345 A Truncation or null fetch error occurred

Oracle EM Alert: Critical:DBNAME - There have been n failed login attempts in the last x minutes: Identify the LOGIN failure with 1017 returncode

This is an Oracle EM alert which says the database has n unsuccessful login attempts in x minutes.

In order to identify the login details which are getting failed you should have enable the database auding especially enable the “connect audit”.