SQL1116N A connection to or activation of database "TESTDB" cannot be made
[db2inst1@dporacle01 ~]$ db2 get db cfg for testdb | grep logretain
[db2inst1@dporacle01 ~]$ db2 get db cfg for testdb | grep -i logretain
Log retain for recovery enabled (LOGRETAIN) = OFF
[db2inst1@dporacle01 ~]$ db2 update db cfg for testdb using LOGRETAIN ON
DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.
[db2inst1@dporacle01 ~]$
[db2inst1@dporacle01 ~]$ db2 get db cfg for testdb | grep -i logretain
Log retain for recovery enabled (LOGRETAIN) = RECOVERY
First log archive method (LOGARCHMETH1) = LOGRETAIN
[db2inst1@dporacle01 ~]$
[db2inst1@dporacle01 ~]$ db2 backup db testdb to /tmp
Backup successful. The timestamp for this backup image is : 20201203080958
[db2inst1@dporacle01 ~]$ ls -l /tmp
total 164024
drwx------. 2 gdm gdm 4096 Dec 3 07:15 gconfd-gdm
drwx------ 2 root root 4096 Nov 26 09:25 gconfd-root
drwx------ 2 root root 4096 Dec 4 2020 keyring-1OuHkv
drwx------ 2 root root 4096 Feb 16 2019 keyring-a5G2O6
drwx------ 2 oracle oinstall 4096 Jun 6 12:33 keyring-Aq6gNH
drwx------ 2 root root 4096 Jul 19 2018 keyring-G1edTe
drwx------ 2 root root 4096 Oct 10 2019 keyring-gJAukV
drwx------ 2 oracle oinstall 4096 Feb 20 2020 keyring-GU3kqb
drwx------ 2 root root 4096 Nov 26 09:04 keyring-h1lbAS
drwx------ 2 root root 4096 Aug 5 2018 keyring-iEcUC2
drwx------. 2 root root 4096 Jul 19 2018 keyring-lwXAOj
drwx------ 2 root root 4096 Mar 19 2020 keyring-mlLOqW
drwx------ 2 root root 4096 Oct 25 2019 keyring-Ni4II5
drwx------ 2 root root 4096 Jun 21 18:11 keyring-nPtXlJ
drwx------ 2 root root 4096 Apr 3 2020 keyring-OD5mIk
drwx------ 2 root root 4096 May 19 2020 keyring-pYV2p1
drwx------ 2 oracle oinstall 4096 Dec 25 2018 keyring-sc8SLe
drwx------ 2 root root 4096 Dec 9 2020 keyring-teoFP4
drwx------ 2 root root 4096 Nov 7 13:21 keyring-ushTz4
drwx------ 2 root root 4096 May 13 2020 keyring-vSczY7
drwx------ 2 root root 4096 Apr 10 2020 keyring-ZypP2w
drwxr-xr-x 2 root sys 4096 Nov 25 2018 LOCAL_INSTALL
drwx------ 2 gdm gdm 4096 Dec 3 07:14 orbit-gdm
drwx------. 2 root root 4096 Nov 26 09:04 pulse-CPNFd1hkJpCg
drwx------. 2 gdm gdm 4096 Dec 3 07:14 pulse-XzWVToRk5SZc
drwx------ 2 oracle oinstall 4096 Jun 6 12:33 pulse-zza0ofGu5HpI
drwxrwxrwx 2 db2inst1 db2iadm1 4096 Dec 4 2020 SQLDIR.LK0
-rw------- 1 db2inst1 db2iadm1 167833600 Dec 3 08:10 TESTDB.0.db2inst1.NODE0000.CATN0000.20201203080958.001
drwx------ 2 root root 4096 Dec 4 2020 virtual-root.3BFjEo
drwx------ 2 root root 4096 Nov 26 09:04 virtual-root.9VVHWm
drwx------ 2 root root 4096 Dec 9 2020 virtual-root.kTnGBz
[db2inst1@dporacle01 ~]$ date
Thu Dec 3 08:10:15 CST 2020
[db2inst1@dporacle01 ~]$ db2 connect to testdb
Database Connection Information
Database server = DB2/LINUXX8664 9.7.0
SQL authorization ID = DB2INST1
Local database alias = TESTDB
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/8520577/viewspace-2744574/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- 請高手指點A connection to the database could not be madeDatabase
- Connection activation failed: Device not managed by NetworkManagerAIdev
- Error: Connection activation failed: Device not managed by NetworkManagerErrorAIdev
- cannot mount database in EXCLUSIVE modeDatabase
- be made of ,be made from , be made by , be made in 的區別
- Cannot get a connection, pool exhausted解決辦法
- Duplicating a Database Without Recovery Catalog or Target ConnectionDatabase
- 在AS中自定義字型庫報錯:java.lang.RuntimeException: native typeface cannot be made自定義字型JavaException
- 解決org.hibernate.exception.GenericJDBCException: Cannot open connectionExceptionJDBC
- Trace the connections being made to the Oracle database-客戶端跟蹤連線OracleDatabase客戶端
- Paxos Made Simple
- IDM-Activation-Script
- ORA-01102: cannot mount database in EXCLUSIVE modeDatabase
- 12C-ORA-65086: cannot open/close the pluggable databaseDatabase
- Msg 3702:Cannot drop the database 'gcard' because it is currently in use.DatabaseGC
- Fatal Error: TXK Install Service,Cannot install Oracle Database HomeErrorOracleDatabase
- ORA-01102 cannot mount database in EXCLUSIVE modeDatabase
- CDH5之Unexpected error.Unable to verify database connectionH5ErrorDatabase
- can close the database Connection before the JTA transaction commit or rollDatabaseMIT
- Enabling Database Resident Connection PoolingDatabaseIDE
- [Oracle] ORA-01102: cannot mount database in EXCLUSIVE modeOracleDatabase
- org.hibernate.exception.JDBCConnectionException: Cannot open connection 解決辦法ExceptionJDBC
- 關於ORA-01102: cannot mount database in EXCLUSIVE modeDatabase
- Oracle ORA-01102故障: cannot mount database in EXCLUSIVE modeOracleDatabase
- Error establishing a database connection 的解決方法(發現黑客入侵)ErrorDatabase黑客
- RAC 11.2.0.3 ORA-01102: cannot mount database in EXCLUSIVE mode”Database
- Error 945 Database cannot be opened due to inaccessible files or insufficient memory or disk spaceErrorDatabase
- SAP MM Vendor Master International Version ActivationAST
- Hadoop and net core a match made in dockerHadoopDocker
- Bug 12725963 - New database connection fails with ORA-12541 after vip failoverDatabaseAI
- 資料塊駐留管理池(Database Resident Connection Pooling)(1)DatabaseIDE
- 資料塊駐留管理池(Database Resident Connection Pooling)(2)DatabaseIDE
- 資料塊駐留管理池(Database Resident Connection Pooling)(3)DatabaseIDE
- Tomcat DBCP(Database Connection Pool) 資料庫連線池入門介紹TomcatDatabase資料庫
- Eclipse Auto Activation 自動提示設定Eclipse
- 資料庫駐留連線池(Database Resident Connection Pooling)(4)資料庫DatabaseIDE
- ORA-01102: cannot mount database in EXCLUSIVE mode 的解決辦法Database
- Oracle 11g RAC ORA-01102: cannot mount database in EXCLUSIVE modeOracleDatabase