MySQL 報Row size too large 65535 原因與解決方案MySQL報錯資訊:Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535向MySQL的表外掛程式一個欄位
ORA-28000 the account is locked錯誤類比錯誤資訊如下:OCI-Call Error sql code 28000,the account is lockedSQL> !oerr ora 2800028000, 00000, "the account is locked"// *Cause: The user has entered wrong password consequently for maximum//
RMAN參數常用設定查看RMAN所有配置RMAN> show all;RMAN configuration parameters for database with db_unique_name Oracle007 are:CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
關於新參數DB_UNRECOVERABLE_SCN_TRACKING,unrecoverablefaultDB_UNRECOVERABLE_SCN_TRACKING這個參數是從11.2.0.2才有的,看官方文檔介紹如下:Default valuetrueModifiableALTER SESSION, ALTER SYSTEMRange of valuestrue | falseBasicNoOracle RACMultiple instances must have the
ORA-30009: CONNECT BY 操作記憶體不足,ora-30009connect 今天在11g的環境上製造資料碰到ORA-30009: CONNECT BY 操作記憶體不足,10g開始支援XML後,改為xmltable就可以了。SQL> drop table t_range purge;SQL> create table t_range (id number not null PRIMARY KEY, test_date date) partition by
mysql 的load data infile的用法,mysqlinfileLOAD DATA INFILE語句從一個文字檔中以很高的速度讀入一個表中。1、基本文法LOAD DATA [LOW_PRIORITY | CONCURRENT] [LOCAL] INFILE 'file_name.txt' [REPLACE | IGNORE] INTO TABLE tbl_name [FIELDS [TERMINATED BY 'string']
今天是2014-06-18,在複製資料的時候出現如下錯誤:RMAN-05537: DUPLICATE without TARGET connection when auxiliary instance is started with spfile cannot use SPFILE clause操作過程如下:[oracle@dg1 dbs]$ rman target sys/root@dg1 auxiliary sys/root@dg2Recovery Manager: