ERROR Message:
ERROR at line 1:
ORA-03113: end-of-file on communication channel
Process ID: 12556
Session ID: 96 Serial number: 12509
ERROR:
ORA-03114: not connected to ORACLE
Log file info:
Incident 757262 created, dump file: /u01/app/oracle/database/diag/rdbms/prod/ORCL/incident/incdir_757262/ORCL_ora_12556_i757262.trc
ORA-07445: exception encountered: core dump [evaopn3()+125] [SIGSEGV] [ADDR:0x4] [PC:0x8AA42D1] [Address not mapped to object] []
this is a bug. Manipulate the sql to remove order by or group by or chagne date format might be a work-around.
Friday, July 27, 2012
rman backup cloud moduel for s3 error
error message:
RMAN> BACKUP DEVICE TYPE SBT AS COMPRESSED BACKUPSET CURRENT CONTROLFILE;
Starting backup at 27-JUL-12
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 07/27/2012 11:37:48
ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-27023: skgfqsbi: media manager protocol error
ORA-19511: Error received from media manager layer, error text:
KBHS-00715: HTTP error occurred 'client-error'
KBHS-00703: unable to connect to HTTP server oracle-sbt-license.s3.amazonaws.com; received ORA-12535
LFI-00108: Open expect the file [ewallet][p12] to exist.
This error was cleared by itself after 3 hours.
I cannot find out the cause.
to find out cloud moduel parameter
reference:
http://www.idevelopment.info/data/AWS/AWS_Tips/Oracle_on_AWS/ORAAWS_15.shtml
RMAN> BACKUP DEVICE TYPE SBT AS COMPRESSED BACKUPSET CURRENT CONTROLFILE;
Starting backup at 27-JUL-12
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 07/27/2012 11:37:48
ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-27023: skgfqsbi: media manager protocol error
ORA-19511: Error received from media manager layer, error text:
KBHS-00715: HTTP error occurred 'client-error'
KBHS-00703: unable to connect to HTTP server oracle-sbt-license.s3.amazonaws.com; received ORA-12535
LFI-00108: Open expect the file [ewallet][p12] to exist.
This error was cleared by itself after 3 hours.
I cannot find out the cause.
to find out cloud moduel parameter
strings $ORACLE_HOME/lib/libosbws12.so | grep '^OSB_' | sort
strings $ORACLE_HOME/lib/libosbws12.so | grep '^_OSB_' | sort
reference:
http://www.idevelopment.info/data/AWS/AWS_Tips/Oracle_on_AWS/ORAAWS_15.shtml
Wednesday, July 25, 2012
ORA-12514: TNS:listener does not currently know of service
issue:
database is tnspingable, but sqlplus will give below error when login:
database is tnspingable, but sqlplus will give below error when login:
ORA-12514: TNS:listener does not currently know of service
cause:
database service is not registered to the listener.
solution:
add service to listener and restart it.
listener entry:
in sid_list_listener:
add
| (SID_DESC = |
| (GLOBAL_DBNAME=myfubardb) |
| (ORACLE_HOME = /ora00/app/oracle/product/10.2.0/db_1) |
| (SID_NAME = fubar) |
| ) |
reference:
OALL8 is in an Inconsistent State
OALL8 is in an inconsistent state" is thrown when using the 10.2.0.3 JDBC thin driver to select non ascii characters from the database.
reference:
http://asanga-pradeep.blogspot.com/2008/06/oall8-is-in-inconsistent-state-with.html
reference:
http://asanga-pradeep.blogspot.com/2008/06/oall8-is-in-inconsistent-state-with.html
remove file extension in shell script
# name without extension
name=${file%\.*}
reference:
http://www.unix.com/shell-programming-scripting/40360-remove-file-extension.html
Monday, July 23, 2012
logical volume check
/dev/mapper/VolGroup00-LogVol00 is a logical volume managed by LVM
the logical volume is called LogVol00 belonging to volume group VolGroup00
below can be used to check LVM
lvdisplay -- logical volume list
vgdisplay -- volume group list
pvdisplay -- physical volume list
reference:
http://www.linuxquestions.org/questions/linux-newbie-8/what-is-dev-mapper-volgroup00-logvol00-and-what-does-it-stands-for-699073/
the logical volume is called LogVol00 belonging to volume group VolGroup00
below can be used to check LVM
lvdisplay -- logical volume list
vgdisplay -- volume group list
pvdisplay -- physical volume list
reference:
http://www.linuxquestions.org/questions/linux-newbie-8/what-is-dev-mapper-volgroup00-logvol00-and-what-does-it-stands-for-699073/
Thursday, July 19, 2012
set vncserver screen size
ISSUE:
when you start vncviewer, the terminal's last several lins might not be viewable in the screen.
Solution:
EDIT:
/etc/sysconfig/vncservers
ADD :
VNCSERVERS="2:oracle"
VNCSERVERARGS[2]="-geometry 1280x1024"
VNCSERVERARGS[2]="-geometry 1280x1024"
Tuesday, July 17, 2012
ORA-445 backgroup process didnt spawn.
error:
ORA-00445: background process "J000" did not start after 120 seconds
cause:
it should be resource issue.
solution:
check if this happens at peak time.
select * from v$resource_limit; to see if any limit is reached.
reference:
http://www.orafaq.com/forum/t/163934/0/
https://forums.oracle.com/forums/thread.jspa?threadID=2141050
ORA-00445: background process "J000" did not start after 120 seconds
cause:
it should be resource issue.
solution:
check if this happens at peak time.
select * from v$resource_limit; to see if any limit is reached.
reference:
http://www.orafaq.com/forum/t/163934/0/
https://forums.oracle.com/forums/thread.jspa?threadID=2141050
Monday, July 16, 2012
ora-28 session killed message in alert log
issue:
alert log displays error message:
opiodr aborting process unknown ospid (24094) as a result of ORA-28
Mon Jul 16 14:23:59 2012
opiodr aborting process unknown ospid (16788) as a result of ORA-28
explanation:
the ora-28 error is just message notifucation error. it is generated when privilege user kills session.
reference:
http://jzhil2004.blog.163.com/blog/static/2755850420111115293348/
alert log displays error message:
opiodr aborting process unknown ospid (24094) as a result of ORA-28
Mon Jul 16 14:23:59 2012
opiodr aborting process unknown ospid (16788) as a result of ORA-28
explanation:
the ora-28 error is just message notifucation error. it is generated when privilege user kills session.
reference:
http://jzhil2004.blog.163.com/blog/static/2755850420111115293348/
Wednesday, July 11, 2012
import failed by not null constraint in oracle
Prolblem: when you import data to the same table but with a new nut null constraint, Your import will failed because of the not null constraint.
Solution: remove the constraint. load data. update with default value and add constraint back.
sql:
alter table test modify column tttt datatype null;
update table test set tttt=default value;
alter table test modify column ttt datatype not null default x;
reference:
http://ss64.com/ora/table_a_cols.html
Solution: remove the constraint. load data. update with default value and add constraint back.
sql:
alter table test modify column tttt datatype null;
update table test set tttt=default value;
alter table test modify column ttt datatype not null default x;
reference:
http://ss64.com/ora/table_a_cols.html
connect failed to debugger on informatica
1. ERROR:
Error connecting to the DTM at [%s : %d]: [%s]
Server execution failed, forcing shutdown of the debugger...
Debugger shutdown complete.
2. CAUSE:
integration service use blocked port to initialize debugger connection back to client.
3. solution;
sepcify port range in integration service custom property
3.1 log into admin console
3.2 select integration service
3.3 click edit on "custom property"
3.4 add
DebuggerMinPort 6001
DebuggerMaxPort 6015
3.5 retry debugger, it should be fine.
reference:
Error connecting to the DTM at [%s : %d]: [%s]
Server execution failed, forcing shutdown of the debugger...
Debugger shutdown complete.
2. CAUSE:
integration service use blocked port to initialize debugger connection back to client.
3. solution;
sepcify port range in integration service custom property
3.1 log into admin console
3.2 select integration service
3.3 click edit on "custom property"
3.4 add
DebuggerMinPort 6001
DebuggerMaxPort 6015
3.5 retry debugger, it should be fine.
reference:
Subscribe to:
Posts (Atom)