"Rman Backup Error du to "ORA-12269: client uses weak encryption/crypto-checksumming version
When Taking backup for Oracle data base I keep getting the below error: RMAN-00571: ====================================================== RMAN-00569: ============ ERROR MASSAGE STACK FOLLOWS ============= RMAN-00571: ====================================================== RMAN - 12001: Could not open channel ch02 RMAN-10008: Could not create channel context RMAN: unable to connect to target database ORA-12269: client uses weak encryption/crypto-checksumming version841Views0likes0CommentsEV Dashboard ASP site available for download.
Hi guys, Following on from the release of EVToolkit HTA. EV Dashboard ASP has been created. An ASPsite to run health checks against your EVinfrastructure, provide information on users, mailboxes, archives. An open source, community project is the goal here so participation is highly encouraged. Please post any questions, comments, suggestions, requests, issues, bugs to the evdiscuss.net forums. See the below url for some beta screenshots or head over to www.evdiscuss.net/download to get the full installation. Consult the documentation before proceeding to installation. https://www-secure.symantec.com/connect/forums/reporting-and-dashboard-tool-enterprise-vault jprknightSolved1.3KViews2likes8CommentsMbx Archiving State / Mbx Exchange State
Often the question of what is the different states of MbxArchivingState and MbxExchangeState in the ExchangeMailboxEntry table. The Archiving State translates as follows: 0 = Not Enabled 1 = Enabled 2 = Disabled 3 = Re-Link To view the Archiving State you can use the following:OpcCenter repository migrate to other DB engine
hi guys ! our OpcCenter is version 8.3, Opscenter Database is Sybase 17.0.10.616 running on Windows 2016. Can we migrate OpcCenter repository to other DB engine running on other machine Linux or Windows? how to do it? thank you1.5KViews0likes3CommentsUnable to connect to the database (Status 252) + 2505
Hello Veritas community, We're running a master server + media server (Linux versions) on NetBackup 8.1. NetBackup processes started failing with database connection errors. Our first step in trying to resolve this was to stop the NetBackup processes and restart them. Unfortunately, that did not resolve our issue. I have been digging through posts and found the common semaphore issue, but the values set seem to be ok (posted below). I'm also adding a few error logs from /var/log/messages. Any help or direction would be greatly appreciated. Thank you https://www.veritas.com/support/en_US/article.100023842 Semaphore settings output: sysctl -a | grep kernel.sem kernel.sem = 400 307200 128 1024 kernel.sem_next_id = -1 ============ /var/log/messages Apr 8 07:28:12 <master_hostname> bash: Error receiving command message: No data to receive from socket. # THIS BLOCK MAY BE RELEVANT (I replaced our actual hostname with master_hostname) Apr 7 09:25:45 <master_hostname> SQLAnywhere(nb_<master_hostname>): Opening dbspace 'EMM_DATA' in file '/usr/openv/db/data/EMM_DATA.db' for database 'NBDB' Apr 7 09:25:45 <master_hostname> SQLAnywhere(nb_<master_hostname>): Opening dbspace 'EMM_INDEX' in file '/usr/openv/db/data/EMM_INDEX.db' for database 'NBDB' Apr 7 09:25:45 <master_hostname> SQLAnywhere(nb_<master_hostname>): Opening dbspace 'DBM_DATA' in file '/usr/openv/db/data/DBM_DATA.db' for database 'NBDB' Apr 7 09:25:45 <master_hostname> SQLAnywhere(nb_<master_hostname>): Opening dbspace 'DBM_INDEX' in file '/usr/openv/db/data/DBM_INDEX.db' for database 'NBDB' Apr 7 09:25:45 <master_hostname> SQLAnywhere(nb_<master_hostname>): Opening dbspace 'DARS_DATA' in file '/usr/openv/db/data/DARS_DATA.db' for database 'NBDB' Apr 7 09:25:45 <master_hostname> SQLAnywhere(nb_<master_hostname>): Opening dbspace 'DARS_INDEX' in file '/usr/openv/db/data/DARS_INDEX.db' for database 'NBDB' Apr 7 09:25:45 <master_hostname> SQLAnywhere(nb_<master_hostname>): Opening dbspace 'JOBD_DATA' in file '/usr/openv/db/data/JOBD_DATA.db' for database 'NBDB' Apr 7 09:25:45 <master_hostname> SQLAnywhere(nb_<master_hostname>): Opening dbspace 'SLP_DATA' in file '/usr/openv/db/data/SLP_DATA.db' for database 'NBDB' Apr 7 09:25:45 <master_hostname> SQLAnywhere(nb_<master_hostname>): Opening dbspace 'SLP_INDEX' in file '/usr/openv/db/data/SLP_INDEX.db' for database 'NBDB' Apr 7 09:25:45 <master_hostname> SQLAnywhere(nb_<master_hostname>): This database is licensed for use with: Apr 7 09:29:33 <master_hostname> SQLAnywhere(nbappdb): Starting database "NBAPPDB" (/opt/NBUAppliance/db/data/NBAPPDB.db) at Wed Apr 07 2021 09:29 Apr 7 09:29:34 <master_hostname> SQLAnywhere(nbappdb): This database is licensed for use with: Apr 7 10:15:30 <master_hostname> SQLAnywhere(nbazdb): Starting database "NBAZDB" (/usr/openv/db/staging/NBAZDB.db) at Wed Apr 07 2021 10:15 Apr 7 10:15:33 <master_hostname> SQLAnywhere(nbdb): Starting database "NBDB" (/usr/openv/db/staging/NBDB.db) at Wed Apr 07 2021 10:15 Apr 7 10:15:33 <master_hostname> SQLAnywhere(nbdb): Opening dbspace 'EMM_DATA' in file '/usr/openv/db/staging/EMM_DATA.db' for database 'NBDB' # SAME BLOCK STARTS OVER AT THIS PIONT ============3.2KViews0likes7CommentsCan we limit Oracle backup retries in Netbackup 7.7.3?
Hi, Good day! Just wondering if we can limit or forego with automatic oracle backup retries? As experienced, everytime an oracle backup encounters errors, as long as it is still within the backup window, it will continue to rerun the job. Netbackup version: 7.7.3 Master server OS: AIX 6.1 Oracle version: 11G Thanks in advance! - alainSolved1.6KViews0likes4Comments