"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 version
Unable 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 ============
Symantec Exec 12 unable to backup some idb files By: Ricky Yau
Hi, I used Symantec Exec 12to backup a database server but I found that it has more exceptions (over 100 idb files can't be backup). It will affected the server restoration. How to setup the backup job for backup db server (idb files)? Unable to open the item \\xxxx11IDB02b\[ROOT]/data/accdb/SYS_ACCCMDVERBTBL.ibd - skipped. Unable to open the item \\xxxx11IDB02b\[ROOT]/data/accdb/ENTP_QUOTATBL.ibd - skipped. Unable to open the item \\xxxx11IDB02b\[ROOT]/data/accdb/SYS_ROLEACCTBL.ibd - skipped. Unable to open the item \\xxxx11IDB02b\[ROOT]/data/accdb/system_servertbl.ibd - skipped. Unable to open the item \\xxxx11IDB02b\[ROOT]/data/accdb/system_server_iptbl.ibd - skipped.Restoring emails from backup Exec 2010 fails
I have been tasked to recover some emails from an old tape based backup created with Backup Exec 2010. I have spun up a VM of SBS 2003 as this was what the backups were created on. I've set it up with the same domain details as the original server (that no longer exists). I've loaded up backup exec 2010 R3, inventoried and catalogued the tapes. Tested restore of files from drives stored in the backupsand all is fine. Restore completes without issue. Ican see the microsoft exchange mailboxes in question on the backup. One of the mailboxes in the backup has a warning x symbol on it and its status is 'corrupt or contains corrupt items'. All the other mailboxes appear with the status 'normal'. It is one of these 'normal' mailboxes that i want to recover some emails from. I start a restore job, select the emails, Set the settings in backup exec under 'exchange' to automatically recreate user accounts and mailboxes', dismount the database before restore and commit and mount database after restore. I then start the restore. The job then fails with the following error: 'A checksum of the data has failed.' I am wondering if the whole exchange database is corrupt in the backup. My question is, how can i get the exchange database 'out' of the backup, so i can try and run some utilities on it to recover the emails? Many thanks Matthew
