国产xxxx99真实实拍_久久不雅视频_高清韩国a级特黄毛片_嗯老师别我我受不了了小说

資訊專欄INFORMATION COLUMN

oracle最佳連接方式之service簡介及創建(上)

IT那活兒 / 2712人閱讀
oracle最佳連接方式之service簡介及創建(上)
點擊上方“IT那活兒”公眾號,關注后了解更多內容,不管IT什么活兒,干就完了!??!
1

數據庫service概要

service是訪問數據庫的一種方式。可以通過service將不同的連接區分開來。service可以當做是一組客戶端或者應用的邏輯組合;每個多帶帶的service 可以設定其自己的屬性,以滿足不同的需要。
例如,為不同的應用、業務、PDB、instance創建不同的service,service的配置要在參數 service_names中設定,同時如果service 要在監聽中完成注冊,那么一個新建是service 才能夠正常使用從而可以將連接映射到不同的服務器上(集群環境)以進行區分。service具有高可用性和負載均衡性。
說明:只是service 漂移,并沒有vip漂移這樣一旦出現問題才能路由到新實例上新的sql 動作才能觸發漂移動作,否則服務器端是無法知道和那些和client 進行連接的。觸發連接遷移是客戶端有操作觸發才行。也就是重新執行SQL等操作。

傳統的TFA實現方式存在如下問題:

  • 連接串通過VIP的順序配置優先連接RAC的節點。
  • 連接串通常不會配置備庫的TNS,主備切換后需要調整TNS連接配置。
  • 需要人工維護配置文件tnsnames.ora,客戶端多的話,不利于維護。

簡單理解就是原始的TFA(Transparent Application Failover)是在客戶端的tnsnames.ora文件中配置,而數據庫的service是在服務端已經配置好了,客戶端無需維護tnsnames.ora文件。

2

service參數說明

RAC使用oracle用戶通過srvctl命令來創建數據庫的service,可以通過servctl add service –h 獲取參數幫助信息。
  • 11G 版本 srvctl add service Options 常見參數:

srvctl add service -d db_unique_name -s service_name {-r "preferred_list"
[-a "available_list"] [-P {BASIC | NONE | PRECONNECT}] | -g server_pool
[-c {UNIFORM | SINGLETON]} [-k network_number]
[-l [PRIMARY | PHYSICAL_STANDBY | LOGICAL_STANDBY | SNAPSHOT_STANDBY]
[-y {AUTOMATIC | MANUAL}] [-q {TRUE | FALSE}] [-x {TRUE | FALSE}]
[-j {SHORT | LONG}][-B {NONE | SERVICE_TIME | THROUGHPUT}]
[-e {NONE | SESSION | SELECT}] [-m {NONE | BASIC}] [-z failover_retries]
[-w failover_delay]

  • 19C 版本部分參數稍有改動:

srvctl add service -database db_unique_name -service service_name_list
[-pdb pluggable_database] [-eval]
[-preferred preferred_list] [-available available_list] [-failback {YES | NO}]
[-netnum network_number] [-tafpolicy {BASIC | NONE}]
[-edition edition_name]
[-role "[PRIMARY][,PHYSICAL_STANDBY][,LOGICAL_STANDBY][,SNAPSHOT_STANDBY]"
[-policy {AUTOMATIC | MANUAL}] [-notification {TRUE | FALSE}]
[-clbgoal {SHORT | LONG}] [-failovertype {NONE|SESSION|SELECT|TRANSACTION|AUTO}]
[-rlbgoal {NONE | SERVICE_TIME | THROUGHPUT}] [-dtp {TRUE | FALSE}]
[-failovermethod {NONE | BASIC}] [-failoverretry failover_retries]
[-drain_timeout timeout] [-stopoption {NONE|IMMEDIATE|TRANSACTIONAL}]
[-failover_restore {NONE|LEVEL1|AUTO}] [-failoverdelay failover_delay]
[-sql_translation_profile sql_translation_profile]
[-global {TRUE | FALSE}] [-maxlag max_lag_time] [-commit_outcome {TRUE|FALSE}]
[-retention retention_time] [-replay_init_time replay_initiation_time]
[-session_state {STATIC|DYNAMIC|AUTO}] [-force] [-verbose]
3

service 創建模版 DB11G MAA

注:備庫的service需要在主庫先創建,然后數據字典同步過去。

3.1 主庫創建備庫角色的兩個service

Create the service resource in primary cluster, for example, add service1 and service2

$ $ORACLE_HOME/bin/srvctl add service -d -s
-l physical_standby -r ","

$ $ORACLE_HOME/bin/srvctl add service -d -s
-l physical_standby -r ","
  • 在主庫執行:
    RAC DB_PRIMARY 是主庫的db_unique_name。
srvctl add service -d EMREP -s EMREP_RD_S1 -l physical_standby -r EMREP1 -a EMREP2
srvctl add service -d EMREP -s EMREP_RD_S2 -l physical_standby -r EMREP2 -a EMREP1
  • 檢查服務狀態:

[oracle@emrep01 dbs]$ srvctl status service -d EMREP
Service EMREP_RD_S1 is not running.
Service EMREP_RD_S2 is not running.

3.2 主庫啟動service并注冊到數據庫

主庫啟動service并注冊到數據庫通過日志傳輸給備庫:

$ $ORACLE_HOME/bin/srvctl start service -d 
這時候觀察主庫兩個節點的alert日志發現如下語句:
  • 主庫節點1 alert日志:

ALTER SYSTEM SET service_names=EMREP_RD_S1 SCOPE=MEMORY SID=EMREP1;
  • 主庫節點2 alert日志:

ALTER SYSTEM SET service_names=EMREP_RD_S2 SCOPE=MEMORY SID=EMREP2;

3.3 主庫停止service

$ $ORACLE_HOME/bin/srvctl stop service -d 
$ $ORACLE_HOME/bin/srvctl status service -d

Service service1 is not running.
Service service2 is not running.

srvctl stop service -d EMREP

這時候觀察主庫兩個節點的alert日志發現如下語句:

ALTER SYSTEM SET service_names=EMREP SCOPE=MEMORY SID=EMREP1;
ALTER SYSTEM SET service_names=EMREP SCOPE=MEMORY SID=EMREP2;
即使使用srvctl start database 重新啟動數據庫,它也不會啟動這個service服務,除非顯示的手動使用srvctl start service啟動!

3.4 確保備庫已經同步

set lines 400 pages 1000
select thread#, max(sequence#) as "last_applied_log"
from v$log_history
group by thread#;

3.5 在備庫創建服務

建議在MRP所在的啟動service。

$ $ORACLE_HOME/bin/srvctl add service -d  -s  -l physical_standby -r ","
$ $ORACLE_HOME/bin/srvctl add service -d -s -l physical_standby -r ","

#
 備庫創建,注意db_unique_name是備庫的
srvctl add service -d DGEMREP -s EMREP_RD_S1 -l physical_standby -r EMREP1 -a EMREP2
srvctl add service -d DGEMREP -s EMREP_RD_S2 -l physical_standby -r EMREP2 -a EMREP1

3.6 檢查service狀態

ora.dgEMREP.EMREP_rd_s1.svc
1   OFFLINE OFFLINE
ora.dgEMREP.EMREP_rd_s2.svc
1   OFFLINE OFFLINE
資源是OFFLINE狀態,因為還沒啟動。

3.7 備庫啟動service

備庫啟動service之后,會在備庫的監聽器中注冊該service。
$ $ORACLE_HOME/bin/srvctl start service -d 

$ $ORACLE_HOME/bin/srvctl status service -d

Service is running on instance(s) ,
Service is running on instance(s) ,

啟動備庫的service:

srvctl start service -d dgEMREP

這時候觀察主庫兩個節點的alert日志發現如下語句:

ALTER SYSTEM SET service_names=EMREP_RD_S1 SCOPE=MEMORY SID=EMREP1;
ALTER SYSTEM SET service_names=EMREP_RD_S2 SCOPE=MEMORY SID=EMREP2;

檢查服務狀態:

ora.dgEMREP.EMREP_rd_s1.svc
 ONLINE  ONLINE       emrep01
ora.dgEMREP.EMREP_rd_s2.svc
 ONLINE  ONLINE       emrep02

檢查service狀態:

[oracle@emrep02 ~]$ srvctl status service -d dgEMREP
Service EMREP_RD_S1 is running on instance(s) EMREP1
Service EMREP_RD_S2 is running on instance(s) EMREP2
查看備庫兩個節點的監聽:
  • 節點1

[grid@emrep01 ~]$ lsnrctl status

LSNRCTL for Linux: Version 11.2.0.4.0 - Production on 07-APR-2022 22:02:28

Copyright (c) 1991, 2013, Oracle. All rights reserved.

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER)))
STATUS of the LISTENER
------------------------
Alias LISTENER
Version TNSLSNR for Linux: Version 11.2.0.4.0 - Production
Start Date                07-APR-2022 20:33:54
Uptime 0 days 1 hr. 28 min. 34 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP OFF
Listener Parameter File   /u01/11.2.0/grid/network/admin/listener.ora
Listener Log File         /u01/11.2.0/grid/log/diag/tnslsnr/emrep01/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=LISTENER)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.25.140.184)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.25.140.186)(PORT=1521)))
Services Summary...
Service "+ASM" has 1 instance(s).
Instance "+ASM1", status READY, has 1 handler(s) for this service...
Service "EMREP_RD_S1" has 1 instance(s).
Instance "EMREP1", status READY, has 1 handler(s) for this service...
Service "dgEMREP" has 1 instance(s).
Instance "EMREP1", status READY, has 1 handler(s) for this service...
Service "EMREPXDB" has 1 instance(s).
Instance "EMREP1", status READY, has 1 handler(s) for this service...
The command completed successfully
  • 節點2
[grid@emrep02 ~]$ lsnrctl status

LSNRCTL for Linux: Version 11.2.0.4.0 - Production on 07-APR-2022 22:07:01

Copyright (c) 1991, 2013, Oracle. All rights reserved.

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER)))
STATUS of the LISTENER
------------------------
Alias LISTENER
Version TNSLSNR for Linux: Version 11.2.0.4.0 - Production
Start Date                07-APR-2022 20:34:14
Uptime 0 days 1 hr. 32 min. 47 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP OFF
Listener Parameter File   /u01/11.2.0/grid/network/admin/listener.ora
Listener Log File         /u01/11.2.0/grid/log/diag/tnslsnr/emrep02/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=LISTENER)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.25.140.185)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.25.140.187)(PORT=1521)))
Services Summary...
Service "+ASM" has 1 instance(s).
Instance "+ASM2", status READY, has 1 handler(s) for this service...
Service "EMREP_RD_S2" has 1 instance(s).
Instance "EMREP2", status READY, has 1 handler(s) for this service...
Service "dgEMREP" has 1 instance(s).
Instance "EMREP2", status READY, has 1 handler(s) for this service...
Service "EMREPXDB" has 1 instance(s).
Instance "EMREP2", status READY, has 1 handler(s) for this service...
The command completed successfully

3.8 檢查備庫service是否隨備庫啟動而啟動

$ $ORACLE_HOME/bin/srvctl stop database -d 
$ $ORACLE_HOME/bin/srvctl start database -d
$ $ORACLE_HOME/bin/srvctl status service -d
Service is running on instance(s) ,
Service is running on instance(s) ,
啟動數據庫:
srvctl start database -d dgEMREP
檢查資源狀態:
ora.dgEMREP.EMREP_rd_s1.svc
1  ONLINE  ONLINE       emrep01
ora.dgEMREP.EMREP_rd_s2.svc
 ONLINE  ONLINE       emrep01
隨著數據庫啟動而啟動了。

3.9 創建主庫的service

  • 主庫寫服務,在主庫執行:
srvctl add service -d EMREP -s EMREP_R_S1 -l PRIMARY -r EMREP1 -a EMREP2
srvctl add service -d EMREP -s EMREP_R_S2 -l PRIMARY -r EMREP2 -a EMREP1
觀察主庫兩個節點的alert日志并沒有同步給備庫。
  • 檢查資源狀態:
ora.EMREP.EMREP_r_s1.svc
     1 OFFLINE OFFLINE                                                  
ora.EMREP.EMREP_r_s2.svc
     1 OFFLINE OFFLINE                                                  
ora.EMREP.EMREP_rd_s1.svc
     1 OFFLINE OFFLINE                                                  
ora.EMREP.EMREP_rd_s2.svc
     1 OFFLINE OFFLINE
說明:此時資源的狀態是OFFLINE,因為還沒啟動。
注意千萬別把備庫的服務在主庫啟動了!

3.10 啟動主庫的service

注意:不要使用servctl start service –d xxx來啟動,這回把備庫的service啟動起來,需要制定-s參數,來啟動特定的service。
  • 只啟動主庫的service:
srvctl start service -d EMREP -s EMREP_r_s1
srvctl start service -d EMREP -s EMREP_r_s2
檢查狀態:
ora.EMREP.EMREP_r_s1.svc
1 ONLINE  ONLINE       emrep01
ora.EMREP.EMREP_r_s2.svc
1 ONLINE  ONLINE       emrep02
ora.EMREP.EMREP_rd_s1.svc
1 OFFLINE OFFLINE
ora.EMREP.EMREP_rd_s2.svc
1 OFFLINE OFFLINE
  • 檢查service狀態:
srvctl config service -d EMREP -s EMREP_r_s1
Service name: EMREP_R_S1
Service is enabled
Server pool: EMREP_EMREP_R_S1
Cardinality: 1
Disconnect: false
Service role: PRIMARY
Management policy: AUTOMATIC
DTP transaction: false
AQ HA notifications: false
Failover type: NONE
Failover method: NONE
TAF failover retries: 0
TAF failover delay: 0
Connection Load Balancing Goal: LONG
Runtime Load Balancing Goal: NONE
TAF policy specification: NONE
Edition:
Preferred instances: EMREP1
Available instances: EMREP2


srvctl config service -d EMREP -s EMREP_r_s2
Service name: EMREP_R_S2
Service is enabled
Server pool: EMREP_EMREP_R_S2
Cardinality: 1
Disconnect: false
Service role: PRIMARY
Management policy: AUTOMATIC
DTP transaction: false
AQ HA notifications: false
Failover type: NONE
Failover method: NONE
TAF failover retries: 0
TAF failover delay: 0
Connection Load Balancing Goal: LONG
Runtime Load Balancing Goal: NONE
TAF policy specification: NONE
Edition:
Preferred instances: EMREP2
Available instances: EMREP1
檢查監聽狀態:
  • 節點1

Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=LISTENER)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.25.140.180)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.25.140.166)(PORT=1521)))
Services Summary...
Service "+ASM" has 1 instance(s).
Instance "+ASM1", status READY, has 1 handler(s) for this service...
Service "EMREP_R_S1" has 1 instance(s).
Instance "EMREP1", status READY, has 1 handler(s) for this service...
Service "EMREP" has 1 instance(s).
Instance "EMREP1", status READY, has 1 handler(s) for this service...
Service "EMREPXDB" has 1 instance(s).
Instance "EMREP1", status READY, has 1 handler(s) for this service...
The command completed successfully
  • 節點2

Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=LISTENER)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.25.140.181)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.25.140.167)(PORT=1521)))
Services Summary...
Service "+ASM" has 1 instance(s).
Instance "+ASM2", status READY, has 1 handler(s) for this service...
Service "EMREP_R_S2" has 1 instance(s).
Instance "EMREP2", status READY, has 1 handler(s) for this service...
Service "EMREP" has 1 instance(s).
Instance "EMREP2", status READY, has 1 handler(s) for this service...
Service "EMREPXDB" has 1 instance(s).
Instance "EMREP2", status READY, has 1 handler(s) for this service...
The command completed successfully

3.11 備庫添加主庫的service

--備庫添加主庫的service
備庫上執行:
srvctl add service -d DGEMREP -s EMREP_R_S1 -l PRIMARY -r EMREP1 -a EMREP2
srvctl add service -d DGEMREP -s EMREP_R_S2 -l PRIMARY -r EMREP2 -a EMREP1
主備切換service變化,切換前:
  • 主庫service
  • 備庫service
主備切換service變化,切換后:
  • 新主庫service

  • 新備庫service

主備switch over之后,需要在主備庫啟動相應的service即可!
新主庫關閉之前備庫的service,啟用主庫的service,新備庫啟用備庫的service。

建議:切換之前可以考慮把主備庫的service先關閉,切換完成后再打開,不然原先連接備庫的service可能連到了主庫上面。

4

service 創建模版 DB19C MAA

4.1 主庫創建備庫的service

srvctl add service -db HBCMDB -pdb ORCL -service ORCL_RD_S1 
-role physical_standby -preferred orcl1 -available orcl2

srvctl add service -db HBCMDB -pdb ORCL -service ORCL_RD_S2
-role physical_standby -preferred orcl2 -available orcl1

4.2 主庫啟動service并注冊到數據庫

主庫啟動service并注冊到數據庫通過日志傳輸給備庫。

srvctl start service -d HBCMDB
4.3 主庫關閉service 
srvctl stop service -d HBCMDB

4.4 確保備庫已經同步

set lines 400 pages 1000
select thread#, max(sequence#) as "last_applied_log"
from v$log_history
group by thread#;

4.5 在備庫中創建service

srvctl add service -db DGORCL -pdb ORCL -service ORCL_RD_S1 
-role physical_standby -preferred orcl1 -available orcl2
srvctl add service -db DGORCL -pdb ORCL -service ORCL_RD_S2
-role physical_standby -preferred orcl1 -available orcl2

4.6 備庫啟動service

srvctl start service -d DGORCL
或者
srvctl start service -d DGORCL -s ORCL_rd_s1
srvctl start service -d DGORCL -s ORCL_rd_s2

4.7 備庫檢查service狀態

[oracle@server01 admin]$ srvctl config service -d DGORCL
Service name: ORCL_R_S1
Server pool:
Cardinality: 1
Service role: PRIMARY
Management policy: AUTOMATIC
DTP transaction: false
AQ HA notifications: false
Global: false
Commit Outcome: false
Failover type:
Failover method:
Failover retries:
Failover delay:
Failover restore: NONE
Connection Load Balancing Goal: LONG
Runtime Load Balancing Goal: NONE
TAF policy specification: NONE
Edition:
Pluggable database name: ORCL
Hub service:
Maximum lag time: ANY
SQL Translation Profile:
Retention: 86400 seconds
Replay Initiation Time: 300 seconds
Drain timeout:
Stop option:
Session State Consistency: DYNAMIC
GSM Flags: 0
Service is enabled
Preferred instances: orcl1
Available instances: orcl2

CSS critical: no


Service name: ORCL_R_S2
Server pool:
Cardinality: 1
Service role: PRIMARY
Management policy: AUTOMATIC
DTP transaction: false
AQ HA notifications: false
Global: false
Commit Outcome: false
Failover type:
Failover method:
Failover retries:
Failover delay:
Failover restore: NONE
Connection Load Balancing Goal: LONG
Runtime Load Balancing Goal: NONE
TAF policy specification: NONE
Edition:
Pluggable database name: ORCL
Hub service:
Maximum lag time: ANY
SQL Translation Profile:
Retention: 86400 seconds
Replay Initiation Time: 300 seconds
Drain timeout:
Stop option:
Session State Consistency: DYNAMIC
GSM Flags: 0
Service is enabled
Preferred instances: orcl2
Available instances: orcl1

CSS critical: no

Service name: ORCL_RD_S1
Server pool:
Cardinality: 1
Service role: PHYSICAL_STANDBY
Management policy: AUTOMATIC
DTP transaction: false
AQ HA notifications: false
Global: false
Commit Outcome: false
Failover type:
Failover method:
Failover retries:
Failover delay:
Failover restore: NONE
Connection Load Balancing Goal: LONG
Runtime Load Balancing Goal: NONE
TAF policy specification: NONE
Edition:
Pluggable database name: ORCL
Hub service:
Maximum lag time: ANY
SQL Translation Profile:
Retention: 86400 seconds
Replay Initiation Time: 300 seconds
Drain timeout:
Stop option:
Session State Consistency: DYNAMIC
GSM Flags: 0
Service is enabled
Preferred instances: orcl1
Available instances: orcl2

CSS critical: no
Service uses Java: false

Service name: ORCL_RD_S2
Server pool:
Cardinality: 1
Service role: PHYSICAL_STANDBY
Management policy: AUTOMATIC
DTP transaction: false
AQ HA notifications: false
Global: false
Commit Outcome: false
Failover type:
Failover method:
Failover retries:
Failover delay:
Failover restore: NONE
Connection Load Balancing Goal: LONG
Runtime Load Balancing Goal: NONE
TAF policy specification: NONE
Edition:
Pluggable database name: ORCL
Hub service:
Maximum lag time: ANY
SQL Translation Profile:
Retention: 86400 seconds
Replay Initiation Time: 300 seconds
Drain timeout:
Stop option:
Session State Consistency: DYNAMIC
GSM Flags: 0
Service is enabled
Preferred instances: orcl1
Available instances: orcl2

CSS critical: no
Service uses Java: false

4.8 主庫創建主庫的service

srvctl add service -db HBCMDB -pdb ORCL -service ORCL_R_S1 -
role primary -preferred orcl1 -available orcl2
srvctl add service -db HBCMDB -pdb ORCL -service ORCL_R_S2 -
role primary -preferred orcl2 -available orcl1

4.9 啟動主庫的service

srvctl start service -d HBCMDB -s ORCL_R_S1
srvctl start service -d HBCMDB -s ORCL_R_S2

4.10 備庫添加主庫的service

srvctl add service -db DGORCL -pdb ORCL -service ORCL_R_S1 -
role primary -preferred orcl1 -available orcl2
srvctl add service -db DGORCL -pdb ORCL -service ORCL_R_S2 -
role primary -preferred orcl2 -available orcl1

本文作者:王爾貴(上海新炬王翦團隊)

本文來源:“IT那活兒”公眾號

文章版權歸作者所有,未經允許請勿轉載,若此文章存在違規行為,您可以聯系管理員刪除。

轉載請注明本文地址:http://specialneedsforspecialkids.com/yun/129342.html

相關文章

  • Oracle最佳連接方式service最佳實踐測試(下)

    Oracle最佳連接方式之service最佳實踐及測試(下) img{ display:block; margin:0 auto !important; width:100%; } body{ width:75%...

    IT那活兒 評論0 收藏1656
  • 甲骨文通過創新技術擴展開放集成的云平臺

    摘要:年月日甲骨文今日發布了最新的集成產品,以幫助企業更便利地運用變革性技術。甲骨文提供下一代用戶體驗,包括基于個人角色使用所有功能,同時通過預先制作的集成模板加速產品上市時間,為企業創造更多的價值。2017年10月11日 –甲骨文今日發布了最新的集成PaaS產品,以幫助企業更便利地運用變革性技術。除了最新的自治數據管理云服務、大數據分析和人工智能功能之外,甲骨文宣布在其應用程序開發平臺、數據集成...

    lordharrd 評論0 收藏0
  • 【容器云UK8S】新手指導

    摘要:詳細請見產品價格產品概念使用須知名詞解釋漏洞修復記錄集群節點配置推薦模式選擇產品價格操作指南集群創建需要注意的幾點分別是使用必讀講解使用需要賦予的權限模式切換的切換等。UK8S概覽UK8S是一項基于Kubernetes的容器管理服務,你可以在UK8S上部署、管理、擴展你的容器化應用,而無需關心Kubernetes集群自身的搭建及維護等運維類工作。了解使用UK8S為了讓您更快上手使用,享受UK...

    Tecode 評論0 收藏0
  • FineReport連接多維數據庫示例操作

    摘要:描述連接多維數據庫,首先要通過數據連接將多維數據庫與連接起來,然后在數據連接的基礎上新建多維數據庫數據集,用于模板設計。詳細設置查看連接數據連接建立好之后,就可以添加多維數據庫數據集。 1. 描述FineReport連接多維數據庫,首先要通過數據連接將多維數據庫與FineReport連接起來,然后在數據連接的基礎上新建多維數據庫XMLA數據集,用于模板設計。2.XMLA數據連接2.1描...

    YFan 評論0 收藏0

發表評論

0條評論

IT那活兒

|高級講師

TA的文章

閱讀更多
最新活動
閱讀需要支付1元查看
<