stream pool設定過小導致impdp失敗
資料泵匯入時候遇到以下問題,
[oracle@justin pump]$ impdp justin/*** directory=pump dumpfile=justin_20110316.dmp
Import: Release 11.2.0.1.0 - Production on Thu Mar 31 12:32:35 2011
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, Oracle Label Security, OLAP, Data Mining,
Oracle Database Vault and Real Application Testing options
UDI-31623: operation generated ORACLE error 31623
ORA-31623: a job is not attached to this session via the specified handle
ORA-06512: at "SYS.DBMS_DATAPUMP", line 3263
ORA-06512: at "SYS.DBMS_DATAPUMP", line 4488
ORA-06512: at line 1
檢視metalink,有以下解釋
Cause
For submitting an export job with datapump utility, we use queues, streams and java objects.
SQL tracing confirms that.
If we see any component is not valid in the database, we will see these errors.
By querying dba_registry we find the different component and their status.
SELECT comp_name, status, version
FROM dba_registry;
Solution
We can validate different components in the database by running $ORACLE_HOME/rdbms/admin/catpatch.sql via SQL*Plus:
spool catpatch.log
connect / as sysdba
shutdown immediate
startup migrate
SELECT comp_name, version, status
FROM dba_registry;
spool off
If you are on 10g Release 2, then perform.:
connect / as sysdba
spool dictreload.log
startup restrict
alter system set shared_pool_size = 512M scope=spfile;
alter system set java_pool_size = 150M scope=spfile;
alter system set aq_tm_processes = 1 scope=spfile;
alter system set cluster_database = false scope=spfile; -- If on RAC
shutdown immediate
startup upgrade
spool off
alter system set cluster_database = true scope=spfile; -- If on RAC
shutdown immediate
startup
看了感覺完全不搭界,於是檢視alertlog,原來是streams pool設定過小造成的
ORA-04031: unable to allocate 56 bytes of shared memory ("streams pool","unknown object","streams pool","fixed allocation callback")
Incident details in: /oracle10g/diag/rdbms/justin/justin/incident/incdir_40167/justin_ora_10439_i40167.trc
檢視sga,只有最小的564M,該引數又不能直接透過alter命令修改
SQL> show parameter sga_ma
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
sga_max_size big integer 564M
SQL> ALTER SYSTEM set sga_max_size=1g;
ALTER SYSTEM set sga_max_size=1g
*
ERROR at line 1:
ORA-02095: specified initialization parameter cannot be modified
手工修改init檔案,將sga_max_size設定成2g,然後生成spfile,再次執行匯入成功
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/15480802/viewspace-691380/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- 又一次stream_pool不足導致的expdp失敗的解決
- 源設定導致Docker映象構建失敗Docker
- DML_LOCKS設定為0導致SHUTDOWN IMMEDIATE失敗
- /etc/fstab的錯誤設定導致系統啟動失敗
- file-max設定過小導致oracle資料庫hang住Oracle資料庫
- 一個耗時的小失誤:shell限制導致Oracle介質上傳失敗Oracle
- Filestream/Windows Share導致Alwayson Failover失敗WindowsAI
- 使用impdp不當導致的資料丟失問題
- 【shmmax】由於shmmax設定過小導致dbca建庫無法完成HMM
- 故障分析 | DDL 導致的 Xtrabackup 備份失敗
- 獲取導致匯入失敗的資料
- selinux導致sqlplus登入失敗LinuxSQL
- SQL Server 因設定最大記憶體過小導致無法啟動SQLServer記憶體
- 10203設定CURSOR_SHARING為SIMILAR導致物化檢視重新整理失敗MILA
- springboot衝突導致的發版失敗Spring Boot
- Docker 導致阿里雲 ECS 內網互通失敗Docker阿里內網
- sock鎖檔案導致的MySQL啟動失敗MySql
- 獲取導致匯入失敗的資料(五)
- 獲取導致匯入失敗的資料(四)
- 獲取導致匯入失敗的資料(三)
- 獲取導致匯入失敗的資料(二)
- 糟糕的範圍管理導致專案失敗(轉)
- pl/sql 過程中變數未初始化導致update語句失敗SQL變數
- MongoDB例項重啟失敗探究(大事務Redo導致)MongoDB
- 迴圈引用導致的json序列化失敗JSON
- 誤操作經歷,truncate導致閃回查詢失敗
- ROSE HA切換節點導致DG失敗、恢復ROS
- rman備份的時候讀取v$session_longops失敗導致備份失敗SessionGo
- oracle stream pool sizeOracle
- 企業使用ERP系統導致失敗的因素所在
- Linux主機名修改後導致mysql重啟失敗LinuxMySql
- RAC oracle 許可權更改導致 實力啟動失敗Oracle
- hibernate懶載入導致多表聯合查詢失敗
- 由於網路卡故障導致DATAGUARD傳輸檔案失敗
- 網路原因導致rac安裝過程中節點2跑root.sh失敗
- impdp時parallel=4導致的錯誤Parallel
- 資料庫連線設定失敗!資料庫
- ORACLE RAC 11.2.0.4 ASM加盤導致叢集重啟之ASM sga設定過小OracleASM