ITPub博客

在工作中，使用sqlplus连接数据库SQL> conn system/oracle@depdb1ERROR:ORA-21561: OID generation failed出现该错误后，查看metalinkConnection Via 10.2.0.3 SQL*Net Fails With Error ORA-21561: OID Generation Failed [ID 559981.1]Cause Incorrect /etc/hosts mapping for the client machine or no mapping at all. Solution Check the client's /.../hosts file and verify that the local node is correctly identified with a mapping for both the short and fully qualified name of the host.同时检查自己的/etc/ho

SQL*Plus: Release 10.2.0.4.0 - Production on Mon Jun 9 14:32:37 2008Copyright (c) 1982, 2007, Oracle. All Rights Reserved.SQL> conn /as sysdbaConnected to an idle instance.SQL> STARTUPORA-27126: unable to lock shared memory segment in coreIBM AIX RISC System/6000 Error: 1: Not ownerChanges The Oracle Home binaries have been patched to 10.2.0.4.0. Cause "oracle" user does not have the required OS capabilities. When LOCK_SGA is set to TRUE in 10.2.0.4, "oracle" user

Applies to:Oracle Server - Enterprise Edition - Version: 10.2.0.3 to 11.1.0.7HP-UX ItaniumSymptomssyslog.16:Aug 16 16:55:46 s51uf33 vmunix: kthread: table is fullsyslog.16:Aug 16 16:56:09 s51uf33 vmunix: kthread: table is fullsyslog.16:Aug 16 16:58:46 s51uf33 vmunix: kkthread: table is fullsyslog.16:Aug 16 16:58:46 s51uf33 vmunix: kthread: tablket hirse afdu:l ltsyslog.16:Aug 16 16:58:46 s51uf33 vmunix: kthread: table is fullsyslog.16:Aug 16 16:58:46 s51uf33 vmunix: kthread: table is fullsyslog.

针对latch:library cache,首先我们先来看看具体这种等待事件的概念针对工作过程中最常见的library cache,针对其他的等待，在以后可以做实验模拟出来主要有library cachelibrary cache pinlibrary cache lock等我们这次主要讨论library cacheLIBRARY CACHE Library cache latch:The library cache latches protect the cached SQL statements and objects definitions held in the library cache within the shared pool. The library cache latch must be acquired in order toadd a new statement to the library cache. During a parse,

参考http://christianbilien.wordpress.com/2007/05/01/two-useful-hidden-parameters-_smm_max_size-and-_pga_max-size/9i (and probably 10gR1, which I did not test): _pga_max_size: default value is 200MB._smm_max_size : default value is the least of 5% of pga_aggregate_target and of 50% of _pga_max_size. A ceiling of 100MB also applies. The ceiling is hit when the pga_aggregate_target exceeds 2GB (5% of 2GB = 10MB) or when_pga_max_size is set to a higher value than the default AND pga_aggregate_target

TRACE_LEVEL_<listenername> = 16 TRACE_FILE_<listenername> = listenerTRACE_DIRECTORY_<listenername> = <any valid directory path> TRACE_TIMESTAMP_<listenername> = ON TRACE_FILELEN_listenername = 102400TRACE_FILENO_listenername = 2TRACE_LEVEL_LISTENER_SERVER1 = 16 TRACE_FILE_LISTENER_SERVER1 = LISTENER_SERVER1.trcTRACE_DIRECTORY_LISTENER_SERVER1 = /oracle/app/oracle/product/10.2.0/db_1/network/log/ TRACE_TIMESTAMP_LISTENER_SERVER1 = ON TRACE_FILELEN_LISTENER_SERVER1 =

Installing Csscan参考文档[ID 745809.1], [ID 754425.1]set oracle_sid=<your SID>sqlplus /nologSQL>conn / as sysdbaSQL>set TERMOUT ONSQL>set ECHO ONSQL>spool csminst.logSQL>@?/rdbms/admin/csminst.sqlnohup csscan system/sys FULL=y TOCHAR=zhs32gb18030 ARRAY=1024000 PROCESS=3 > csscan.log &生成下面几个文件，scan.txt,scan.out,scan.err，我们主要关注scan.err判断那些表数据在做字符集合转换过程中会出现乱码[@more@]

First of all the problem with the destination being stuck at the OS level should be resolved. Secondly you can change the above outlined archiver behavior, to make sure the local destination is archived first, causing the OPTIONAL destination to behave really optional. If the following parameter is set then the ARCH process will begin archiving to the local destination first. Once the redo log has been completely and successfully archived to at least one local destination. For 9iR2 (

Unicode Character Sets In The Oracle DatabaseOverview Oracle started supporting Unicode based character sets in Oracle7. Here is a summary of the Unicode character sets supported in Oracle:Characterset Name RDBMS version Unicode versionAL24UTFFSS 7.2-8.1 1.1UTF8 8.0-11g 2.1 (8.0-8.1.6) , 3.0 (8.1.7-11g) UTFE 8.0-11g 2.1 (8.0-8.1.6) , 3.0 (8.1.7-11g) AL32UTF8* 9.0-11g 3.0 (9.0), 3.1 (9.2), 3.2 (10.1), 4.01 (10.2), 5.0 (11.1).AL16UTF16** 9.0-11g 3.0 (9.0), 3.1

结合metalink文档454678.1 和在网上看到别人 How to deal with SYSAUX tablespace 100% full ?The statistics used by Oracle Optimizer inside the Oracle Database Unit (DBU) are updated daily and stored for 31 days by default. For large tables, the statistics can use a significant amount of space in the SYSAUX tablespace So you have to purge the data manually.but the purge procedure will fail in most of the situation .because during the period , it will use up t

一次做DATAGUARD的时候恢复数据文件restore database出现下列错误Restore and recovery returns error:RMAN-03002: failure of restore command at 08/24/2007 11:47:27ORA-01861: literal does not match format string单独回复前几个文件可以restore database 1,2,3但是在恢复第60个文件的时候还是同样的错误，考虑可能是文件头有问题做了下列操作dd if=/dev/zero of=/dev/....filename... bs=8k count=8 conv=notrunc再做restore ok[@more@]

Customer may receive the below error messages on Linux Machines ::SQL> connect sys as sysdbaEnter password:Connected to an idle instance.SQL> STARTUP NOMOUNT PFILE="/opt/oracle/admin/day/pfile/day2.ini";ORA-00845: MEMORY_TARGET not supported on this system Solution Increase the /dev/shm mountpoint size. For example:# mount -t tmpfs shmfs -o size=7g /dev/shmAlso, to make this change persistent across system restarts, add an entry in /etc/fstab similar to the following:shmfs /

create database with US7ASCII is created using DBCA , perform the following steps : SHUTDOWN IMMEDIATE; STARTUP MOUNT; ALTER SYSTEM ENABLE RESTRICTED SESSION; ALTER SYSTEM SET JOB_QUEUE_PROCESSES=0; ALTER SYSTEM SET AQ_TM_PROCESSES=0; ALTER DATABASE OPEN; ALTER DATABASE CHARACTER SET ZHS32GB18030;SHUTDOWN;Note 458122.1 about how to use CSSCANNote 306411.1[@more@]

oracle10g引入了mutexes的概念mutexes和latch有部分相似处latch 和 mutexes在机制上都是一个串行概念，但是mutex在使用上比latch更加轻量级别简单理解latch可以保护多个对象，当要访问latch保护的对象时，latch本身也有可能成为一个争用的对象mutexes相对来说处理比较灵活，在访问对应对象时，mutexes会衍生一个新的mutex针对要保护的对象多个session可以共享的使用一个mutex(Shared),单个session也可以独占的使用一个mutex(eXclusive)In 10.2, the only client of mutexes is kks (Kernel Kompile Shared) i.e. the shared cursor compon

[root@server ~]# lsof |grep 1521sendmail 1977 root mem REG 8,2 15216 225096 /usr/lib/sasl2/libcrammd5.so.2.0.19tnslsnr 3579 oracle 8u IPv4 9264 TCP server:1521 (LISTEN)tnslsnr 3579 oracle 11u IPv4 30797 TCP server:1521->server:37406 (ESTABLISHED)oracle 7637 oracle 16u IPv4 30796 TCP server:37406->server:1521 (ESTABLISHED)oracle 7686 oracle 12u IPv4 30953

备份users表空间RMAN> run {2> backup datafile 4;3> }Starting backup at 04-APR-09allocated channel: ORA_DISK_1channel ORA_DISK_1: sid=140 devtype=DISKchannel ORA_DISK_1: starting full datafile backupsetchannel ORA_DISK_1: specifying datafile(s) in backupsetinput datafile fno=00004 name=/u01/app/oracle/oradata/db10g/users01.dbfchannel ORA_DISK_1: starting piece 1 at 04-APR-09RMAN-00571: ===========================================================RMAN-00569: =============== ERROR MESSAGE STA

select file_id, block_id from dba_extents where segment_name = 'TEST' AND OWNER='APPS';FILE_ID BLOCK_ID4 336094 336174 336254 336334 336414 336494 336574 336654 336734 336814 336894 336974 337054 337134 337214 337294 338014 339294 340574 341854 34313bbed parfile=par.bbd blocksize=8192 copy file 2 block 17 to file 4 block 33617copy file 2 block 17 to file 4 block 33804[oracle@server ~]$ dbv file=/u01/app/oracle/oradata/db10g/use

cd $ORACLE_HOME/rdbms/lib make -f ins_rdbms.mk ikfedLinking KFED utility (kfed)rm -f /oracle/app/oracle/product/10.2.0/db_1/rdbms/lib/kfedgcc -o /oracle/app/oracle/product/10.2.0/db_1/rdbms/lib/kfed -L/oracle/app/oracle/product/10.2.0/db_1/rdbms/lib/ -L/oracle/app/oracle/product/10.2.0/db_1/lib/ -L/oracle/app/oracle/product/10.2.0/db_1/lib/stubs/ -L/usr/lib -lirc /oracle/app/oracle/product/10.2.0/db_1/lib/s0main.o /oracle/app/oracle/product/10.2.0/db_1/rdbms/lib/sskfeded.o /oracle/app/oracle/pr

CREATE DISKGROUP DSKGRP2 EXTERNAL REDUNDANCY DISK '/oracle/oradata/asmdisk03', '/oracle/oradata/asmdisk07'; create tablespace testasm datafile '+DSKGRP2' size 100M autoextend off extent management local uniform size 1M segment space management auto; RMAN> BACKUP FORMAT '/oracle/rman/bk_%s_%p_%t' tablespace testasm;Starting backup at 22-APR-09using channel ORA_DISK_1channel ORA_DISK_1: starting full datafile backupsetchannel ORA_DISK_1: specifying datafile(s) in backupsetinput data

下午装了一套10g RAC环境,装完后第二个节点ASM和数据库实例都可以通过srvctl正常启动，但是在第二个节点通过sqlplus死活连接不到数据库,连接直接出现下列提示Connected to idle instance后来检查第一个节点export ORACLE_HOME=/oracle/app/oracle/product/10g第二个节点export ORACLE_HOME=/oracle/app/oracle/product/10g/修改ORACLE_HOME，就是多了"/"惹的祸参考metalink doc 728895.1[@more@]