點(diǎn)擊上方“IT那活兒”公眾號(hào),關(guān)注后了解更多內(nèi)容,不管IT什么活兒,干就完了?。?!
Error reading descriptor from registry: Couldnt open encmap gbk.enc:
No such file or directory
at /u01/app/oracle/product/19.0.0/dbhome_1/perl/lib/site_perl/5.28.1/x86_64-linux-thread-multi/XML/Parser.pm line 187.
XML::Simple called at /u01/app/oracle/product/19.0.0/dbhome_1/sqlpatch/sqlpatch.pm line 7780.
那我們今天就來(lái)探討一下在做數(shù)據(jù)庫(kù)遷移、搭建ADG時(shí)什么才是真正的Oracle源環(huán)境與目標(biāo)環(huán)境保持一致。
alter session set container=PDB_NAME;
col PROPERTY_NAME for a25;
col PROPERTY_VALUE for a25;
select PROPERTY_NAME,PROPERTY_VALUE from database_properties where property_name=LOCAL_UNDO_ENABLED;
exec dbms_registry.OPTION_OFF(RAC);
column comp_id format a20
column comp_name format a30
column version format a20
column status format a15
set pagesize 500
set linesize 150
SELECT COMP_ID,SUBSTR(comp_name, 1, 30) comp_name, SUBSTR(version, 1, 20) version, status
FROM dba_registry
ORDER BY comp_name;
set linesize 170
set pagesize 5000
col con_id for 99
col con_name for a10
col comp_id for a15
col comp_name for a40
col status for a10
col version for a15;
SELECT a.con_id,
decode(a.con_id, 1, cdb$root, b.name) AS con_name,
comp_id,
comp_name,
status,
version
FROM cdb_registry a, v$pdbs b
WHERE a.con_id = b.con_id(+)
ORDER BY 1, 3;
Error reading descriptor from registry: Couldnt open encmap gbk.enc:
No such file or directory
at /u01/app/oracle/product/19.0.0/dbhome_1/perl/lib/site_perl/5.28.1/x86_64-linux-thread-multi/XML/Parser.pm line 187.
XML::Simple called at /u01/app/oracle/product/19.0.0/dbhome_1/sqlpatch/sqlpatch.pm line 7780.
set line 200
col action_time for a40
col status for a20
col description for a100
select patch_id,patch_type,action,status,action_time,description from dba_registry_sqlpatch;
set line 300
set pagesize 100
COL PLATFORM_NAME FOR a40
COL ENDIAN_FORMAT for a14
SELECT PLATFORM_ID, PLATFORM_NAME, ENDIAN_FORMAT
FROM V$TRANSPORTABLE_PLATFORM
3 ORDER BY PLATFORM_ID;
PLATFORM_ID PLATFORM_NAME ENDIAN_FORMAT
----------- ---------------------------------------- --------------
1 Solaris[tm] OE (32-bit) Big
2 Solaris[tm] OE (64-bit) Big
3 HP-UX (64-bit) Big
4 HP-UX IA (64-bit) Big
5 HP Tru64 UNIX Little
6 AIX-Based Systems (64-bit) Big
7 Microsoft Windows IA (32-bit) Little
8 Microsoft Windows IA (64-bit) Little
9 IBM zSeries Based Linux Big
10 Linux IA (32-bit) Little
11 Linux IA (64-bit) Little
12 Microsoft Windows x86 64-bit Little
13 Linux x86 64-bit Little
15 HP Open VMS Little
16 Apple Mac OS Big
17 Solaris Operating System (x86) Little
18 IBM Power Based Linux Big
19 HP IA Open VMS Little
20 Solaris Operating System (x86-64) Little
21 Apple Mac OS (x86-64) Little
22 Linux OS (S64) Big
21 rows selected.
特別要注意NLS_NCHAR_CHARACTERSET和NLS_CHARACTERSET這兩個(gè)參數(shù)。
set linesize 300 pagesize 100
col parameter for a40
col value for a50
select * from nls_database_parameters;
alter system set DB_16k_CACHE_SIZE=100M scope=both;
SGA_TARGET
CPU_COUNT
PGA_AGGREGATE_TARGET
PGA_AGGREGATE_LIMIT
SESSIONS
JOB_QUEUE_PROCESSES
文章版權(quán)歸作者所有,未經(jīng)允許請(qǐng)勿轉(zhuǎn)載,若此文章存在違規(guī)行為,您可以聯(lián)系管理員刪除。
轉(zhuǎn)載請(qǐng)注明本文地址:http://systransis.cn/yun/129190.html
摘要:留下幾個(gè)人監(jiān)控?cái)?shù)據(jù),其他人就散了,等遷移完成后再進(jìn)行后續(xù)工作。突發(fā)事故凌晨的夜晚比較困,當(dāng)我點(diǎn)起第三根煙的時(shí)候,負(fù)責(zé)遷移的這位程序員,急匆匆的跑過(guò)來(lái)找我了。這個(gè)事可大了如果在上午之前不搞定這個(gè)事情,那就完全是重大事故了。 有一個(gè)讀者問(wèn)我:你認(rèn)為一個(gè)程序員具備什么樣的能力,才算得上是厲害的程序員? 我答:擁有解決問(wèn)題的能力的程序員。 這個(gè)回答貌似有點(diǎn)抽象,不要緊看下面的文章你會(huì)慢慢有所了...
摘要:在公司的調(diào)查中,大約的組織如今使用私有云和公共云來(lái)承擔(dān)相同的工作量,另有的受訪者表示他們使用一種類型的云計(jì)算進(jìn)行生產(chǎn),而采用另一種類型進(jìn)行測(cè)試開(kāi)發(fā)備份或分析,這也被認(rèn)為是一種混合云策略。混合云的定義根據(jù)企業(yè)的要求而有所不同,但它總是涉及使用私有云和公共云,而企業(yè)需要一種策略。如果讓一些IT領(lǐng)導(dǎo)人定義混合云是什么,他們的答案可能會(huì)多樣化,并將會(huì)在混合云定義中描述公共云和企業(yè)數(shù)據(jù)中心中混合應(yīng)用程...
摘要:通過(guò)對(duì)一些客戶的跨云遷移過(guò)程進(jìn)行總結(jié),發(fā)現(xiàn)普遍存在的挑戰(zhàn)有三點(diǎn)數(shù)據(jù)完整性和一致性挑戰(zhàn)。簡(jiǎn)而言之,跨云遷移過(guò)程中的數(shù)據(jù)一致性主要就集中在存量數(shù)據(jù)的遷移如何保證一致。前言隨著互聯(lián)網(wǎng)業(yè)務(wù)發(fā)展對(duì)容災(zāi)以及對(duì)訪問(wèn)加速、多供應(yīng)商成本控制等需求的產(chǎn)生,互聯(lián)網(wǎng)公司的多云部署和跨云遷移逐漸成為剛需,而在此過(guò)程中,最困擾運(yùn)維和研發(fā)人員的就是數(shù)據(jù)的遷移和同步。俗語(yǔ)說(shuō) 上屋搬下屋,搬灑一籮谷 ,在業(yè)務(wù)的遷移過(guò)程中一旦...
摘要:很多人對(duì)是否真的適合企業(yè)環(huán)境還心存顧慮,所以我覺(jué)得有必要做個(gè)解釋。架構(gòu)或技術(shù)本身并沒(méi)有絕對(duì)的好壞之分,只有適不適合。沒(méi)有一個(gè)企業(yè)或應(yīng)用系統(tǒng)可以完美地解決所有的業(yè)務(wù)需要。 showImg(https://segmentfault.com/img/remote/1460000014841889?w=2269&h=1500); 本文是鋼哥的Oracle APEX系列文章中的第六篇,完整 Or...
閱讀 1357·2023-01-11 13:20
閱讀 1707·2023-01-11 13:20
閱讀 1215·2023-01-11 13:20
閱讀 1906·2023-01-11 13:20
閱讀 4165·2023-01-11 13:20
閱讀 2757·2023-01-11 13:20
閱讀 1402·2023-01-11 13:20
閱讀 3672·2023-01-11 13:20