Wouldn’t it be nice to not have to manage user passwords in your Oracle Databases? Setting up Active Directory aka Kerberos Authentication is a way to avoid having to manage passwords and allows users to authenticate against your Active Directory. Below is a list of useful links and My Oracle references that were used when setting up this example: EDIT - This post gets a lot of hits so I will include some updated information. If you're on 12c you need to add kerberos5pre to your list of services. e.g. SQLNET.AUTHENTICATION_SERVICES= (beq,kerberos5pre,kerberos5) If you are an Oracle Support Customer check out How To Configure Kerberos Authentication In A 12c Database ( Doc ID 1996329.1 ). If not, here is a good 3rd party write up https://wiki.loopback.org/display/KB/Oracle+Database+12c+Kerberos+Configuration Master Note For Kerberos Authentication (Doc ID 1375853.1) Configuring ASO Kerberos Authentication with a Microsoft Windows 2008 R2 Active Directory KDC (Doc ...
Recently I was tasked to build out an OEM 13c instance to manage a few Oracle Database servers and their associated instances. As a part of the setup, I needed to generate a daily email report to confirm the backup status of all databases in the OEM inventory. Unfortunately, it seems Oracle has overlooked this in the default reports, so I had to create a custom report. Here's how this was accomplished. The EM Repository database keeps track of the last database backup timestamp for each database. This is shown on the home page for any database. We can use this information to create a daily report and confirm that each database has been backed up in the last 24 hours. Login the BI publisher site https://oemserver.yourdomain:9851/xmlpserver with your account or sysman. Near the top right corner click “catalog”. In the tree on the left create a new folder under “Shared Folders” called custom reports. Within the custom reports folder create a new folder called “custom d...
I seem to be on the Oracle Enterprise manager kick lately, so why not one more post on it. Recently I hit the 85% mark on the Fast Recovery Area due to archive log bloat and did not see any alerts triggered in OEM. Well as I discovered, part of the reason for this is that according to MOS, "If using Fast Recovery Area (FRA) for the archive destination and the destination is set to USE_DB_RECOVERY_FILE_DEST, then the Archive Area % Used metric will not trigger anymore." Well that is annoying. However, I did find that the alert does trigger, but it is buried and doesn't show up on any main pages. To see it, go to the target database home page. Then navigate to Oracle Database->Monitoring->All Metrics . In the left pane you can scroll down to “ Recovery Area->Recovery Area Free Space ”. There you will see your alert if active. When viewing the All Metrics page, click on the alerts icon to see active alerts. If you want to see it triggered just temporaril...
Comments
Post a Comment